Search found 69 matches
- Tue Oct 04, 2011 11:40 am
- Forum: Development Tools and Programming
- Topic: Problem connecting two XS1-L2A
- Replies: 13
- Views: 10682
Re: Problem connecting two XS1-L2A
This is an 'issue with the current tools' and we are working to address it.
- Thu May 26, 2011 6:29 am
- Forum: Development Tools and Programming
- Topic: Problem with custom Bootloader
- Replies: 2
- Views: 4607
Re: Problem with custom Bootloader
The functions in the loader are subject to the same link-time requirements as other XC programs: unlike C, functions signatures must match at link time. In this case the signature of your implementation of recordCandidateImage seems to be different to that expected. Try changing the return type to v...
- Mon May 23, 2011 11:51 am
- Forum: Development Tools and Programming
- Topic: Problem with reboot during DFU
- Replies: 5
- Views: 5585
Re: Problem with reboot during DFU
Resetting an N-L1 system is tricky. I'm guessing from the name of the function write_sswitch_reg_blind() that you're not waiting for responses to the switch register writes. Is this correct? If so, it may be that the second (local) reset is being received and acted-on by the local switch before mess...
- Sun Apr 24, 2011 2:39 pm
- Forum: Development Tools and Programming
- Topic: How to force location of variable in memory
- Replies: 3
- Views: 4128
Re: How to force location of variable in memory
The linker can't do that. You can use the assembler to force things onto particular boundaries but not to specific addresses.
Why 0x14000?
Why 0x14000?
- Wed Apr 20, 2011 5:02 pm
- Forum: Development Tools and Programming
- Topic: Ehancing stack for a core?
- Replies: 5
- Views: 6219
Re: Ehancing stack for a core?
If you're looking for a breakdown of memory usage when something is too big to fit then the linker's --map option is also a good bet. To use, add this to the compile line: "-Xmapper --map -Xmapper mapfile". After a link (even a failed link) you get a file called "mapfile" which c...
- Wed Apr 20, 2011 2:50 pm
- Forum: Development Tools and Programming
- Topic: Ehancing stack for a core?
- Replies: 5
- Views: 6219
Re: Ehancing stack for a core?
The stack space isn't of fixed size. Starting from the lowest memory address and working upwards there is text (code), initialised data, bss (uninitialised data), heap (malloc-able memory) and finally stack (which value abuts the highest usable address in memory). The size of text, data and bss are ...
- Tue Apr 12, 2011 9:50 am
- Forum: General Questions
- Topic: Several questions about XMOS
- Replies: 54
- Views: 48037
Re: Several questions about XMOS
Still not having any luck changing SystemFrequency of ReferenceFrequency in the .xn file. The first thing to check is that you can successfully alter them independently - try flashing LEDs using first instruction cycles then a timer to check that the flash speed changes when you change the appropri...
- Mon Apr 11, 2011 3:15 pm
- Forum: Other XMOS Development Kits
- Topic: Xlink between 2 XC-1As
- Replies: 10
- Views: 10491
Re: Xlink between 2 XC-1As
So would the only way to work out why its failing be to scope what's happening over the link? The method described in the links above works for suitably configured boards; I reconfirmed it myself a couple of weeks ago with pairs of XC-1s and XC-2s. Unfortunately the G4 links are almost completely o...
- Mon Apr 11, 2011 1:51 pm
- Forum: Other XMOS Development Kits
- Topic: Xlink between 2 XC-1As
- Replies: 10
- Views: 10491
Re: Xlink between 2 XC-1As
Code below. A value of 0x00 runs the switch at the maximal clock rate, 0xff at the lowest. Some XC-1 firmwares seem to program it to 0x80. #include <platform.h> #include <xs1.h> #include <stdio.h> int main() { par { on stdcore[0]: { unsigned int val; read_sswitch_reg( 0, XS1_SSWITCH_CLK_DIVIDER_NUM,...
- Mon Apr 11, 2011 10:20 am
- Forum: Other XMOS Development Kits
- Topic: Xlink between 2 XC-1As
- Replies: 10
- Views: 10491
Re: Xlink between 2 XC-1As
I can't imagine that this could be caused by the xlink failing to connect so is it likely to be a problem with the way I am doing the splitting? Experience suggests that it is most probably caused by the xlinks failing to connect. The G4 links are tetchy and problems are difficult to diagnose witho...