The xCORE-USB sliceKITxCORE-USB sliceKIT contains everything you need to start developing USB applications on xCORE multicore microcontrollers. The xCORE-USB sliceKITxCORE-USB sliceKIT features our 16 core High Speed USB device which delivers the deterministic, responsive processing required to handle a variety of peripheral interfaces, data processing and control tasks.
The kit includes the USB sliceCARD with USB A and USB B connectors which works with xCORE-USB integrated High Speed USB 2.0 PHY. Our sliceKIT product range includes a wide variety of other slice I/O cards, making it easy to rapidly develop systems.
Kit Contents
Core board with 16 core xCORE-USB multicore microcontroller
USB A/B sliceCARD
Mixed Signal sliceCARD
xTAG-2 debug adaptor
Power supply
Product Video
You don't have permission to edit metadata of this video.
Testers will be selected on the basis of quality of applications: we expect a full and complete description of why you want to test this particular product.
Testers are required to produce a full, comprehensive and well thought out review within 2 months of receipt of the product.
Failure to provide this review within the above timescale will result in the enrolee being excluded from future RoadTests.
I am familiar with the task-to-task interface procedures (certainly am no expert) but I've not had a need to use the [[guarded]] modifier so far. As I understand, usage of the task-to-task interface should be no different with the [[guarded]] modifier, it just (a) provides the ability to 'filter out' some IPC, for example if a message has been received and is currently being processed and no additional such message is to be handled until the processing is complete, and (b) also provides the ability to create an interface that doesn't need to be fully used in select statements until you want to do so. This is all theoretical understanding - as mentioned, I've not used the [[guarded]] bit so far.
Is that what you're trying to do? Does your comms work without the modifier, but not with? What issue are you seeing?
Top Comments
I have been working with the XMOS General Purpose Slice Kit for a couple months now. There is a learning curve involved due to the "xc" language extensions and the hybrid architecture XMOS uses. I spent…
Hi Linas,
The clock is 500MHz, and there is a pipeline type structure (in this case 4 stages), meaning that the throughput will vary (e.g. due to pipeline stalls or intentionally due to instructions or…
When you write question, you should supply all information.
FFT from 500Hz samplig can teke anywhere from 1ns to 10 years, question is sample size, or resolution of your FFT in Hz
With STM32F407 i was able…