Search found 129 matches
- Fri Nov 15, 2019 10:27 pm
- Forum: General Questions
- Topic: Notifications on multiple interface instances
- Replies: 2
- Views: 13483
Re: Notifications on multiple interface instances
I reported a bug on notifications years ago. It was an issue of the order they are defined/implemented, can't remember which. I think it was order in the select so you basically need to mess around moving it up and down to get it to work, possible that there is no usable order. I stick to one notifi...
- Sat Oct 05, 2019 8:25 pm
- Forum: Q&A
- Topic: measuring the execution time on multicore application
- Replies: 3
- Views: 4724
Re: measuring the execution time on multicore application
Typically it's simple math but the second cores interact and ports are involved all bets are off since they run independently. That's why you typically look at timing of functions. If you really want to time it running I'd just use 1 port per core and toggle high at begin, low at end, measure the +p...
- Thu Aug 15, 2019 6:24 am
- Forum: General Questions
- Topic: When will there be SliceKits available?
- Replies: 14
- Views: 38995
Re: When will there be SliceKits available?
It's sort of a tough situation. Many of their products are not carried by mainstream vendors, and sometimes when they are you are required to order a large quantity which is annoying for prototypes. Years ago when I started using XMOS products I thought it'd get better. There have been ups and downs...
- Fri Mar 15, 2019 4:11 pm
- Forum: Development Tools and Programming
- Topic: xCORE-XA , Is it available?
- Replies: 2
- Views: 1817
Re: xCORE-XA , Is it available?
I'm pretty sure they were discontinued. I've been making boards with ARM processors and xmos ones connected via UART, I²C, or SPI. Sending ARM config data at startup and a basic data logging program. I'd recommend you do a similar thing for your application. You could even flash the ARM image onto X...
- Mon Mar 11, 2019 5:20 pm
- Forum: Q&A
- Topic: xTimeComposer: Importing a project that has not been exported
- Replies: 1
- Views: 1577
Re: xTimeComposer: Importing a project that has not been exported
You could just start a new project and add the files. I'd recommend using GitHub or an equivalent to backup your project every time you finish working on it. I've never had issues specifically importing, and done it many times so that's my only suggestion.
- Wed Dec 19, 2018 6:10 pm
- Forum: Q&A
- Topic: compiling library
- Replies: 3
- Views: 40059
Re: compiling library
Make sure you include the relevant headers and select/add the lib to your makefile.
- Mon Dec 10, 2018 7:37 pm
- Forum: Q&A
- Topic: What is XTAG3 UART used for?
- Replies: 1
- Views: 25764
Re: What is XTAG3 UART used for?
I think that's just a carry over from old stuff. Now you'd want to use a link and print through xscope if possible. I believe xtag3 still supports it though so if you had no links avail but can sacrifice 1 or 2 pins for uart you can use them. Better than jtag, worse than xscope for performance.
- Mon Dec 03, 2018 5:55 pm
- Forum: Q&A
- Topic: defining interfaces outside of main.xc
- Replies: 2
- Views: 35502
Re: defining interfaces outside of main.xc
One server and multiple clients requires an array of them. One per client. Also your interface can't be of type interface, needs to be led_if or some other type. Use a typedef struct name {} name; syntax for it. Then you declare it as name myled_if[3]. myled_if goes to server, individuals go to clie...
- Sat Nov 10, 2018 7:59 pm
- Forum: XMOS Devices
- Topic: Response time
- Replies: 9
- Views: 63746
Re: Response time
Last time I checked it was also faster to handle storing current value yourself instead of letting the select handle it (":> enc") that's likely where the reduced latency is coming from. I don't know what your program is but setting it thread fast mode on to reduce event latency response. ...
- Sun Jul 29, 2018 5:37 pm
- Forum: Development Tools and Programming
- Topic: Using [[distributable]] task in a [[combine]] par
- Replies: 5
- Views: 3805
Re: Using [[distributable]] task in a [[combine]] par
No, it's not actually combinable at all. It doesn't require its own cycles. Basically calling a function where the calling thread uses its cycles to run the code. I think the combinable requirement comes from the fact that all the code a thread runs when using distributable calls is not placed there...