Search found 131 matches
- Mon Sep 18, 2023 11:05 am
- Forum: Q&A
- Topic: update.xml: error: no '<' before the end of file
- Replies: 2
- Views: 6333
Re: update.xml: error: no '<' before the end of file
Yes, we've had the same problem running "xburn -l". However, "xflash -l" works fine and our full programming xburn command works fine too, probably because we use the --no-version-check argument so it's probably worth trying that.
- Sat Jul 22, 2023 8:38 pm
- Forum: Projects
- Topic: Weekend project - spectrum analyser
- Replies: 4
- Views: 12556
Re: Weekend project - spectrum analyser
It's probably possible in a single thread with a combination of quadrature mirror filters and elliptic bandpass filters, then pass the filtered outputs to a second thread to do the ballistics.MaximLiadov wrote: ↑Fri Jul 21, 2023 10:45 pm Amazing project! True 1/3 octave filters without FFT working entirely on one core would be nice.
- Fri Mar 12, 2021 3:53 pm
- Forum: Development Tools and Programming
- Topic: Detecting processor type
- Replies: 3
- Views: 2974
Re: Detecting processor type
That's a good idea. I was looking for a common register to read in both XL232 and XE232, but maybe the USB register will read differently or not at all on an XL232. I'll give it a try.
- Fri Mar 12, 2021 12:53 pm
- Forum: Development Tools and Programming
- Topic: Detecting processor type
- Replies: 3
- Views: 2974
Detecting processor type
Is there any way to programmatically determine which processor variant code is being run on? The reason I ask is because I have code which seems to run with no problems on both an XL232 and XE232 chip with no changes to the XN file (which is configured for the XL232). It would be a useful to be able...
- Mon Mar 08, 2021 9:43 pm
- Forum: Development Tools and Programming
- Topic: xflash - 2 questions
- Replies: 3
- Views: 2448
Re: xflash - 2 questions
Thanks, that's helpful. I thought that was the case, and my experiments seem to confirm that, but couldn't find anything definitive in the documentation (actually I'm not sure the --no-compression flag is documented at all)
- Fri Mar 05, 2021 3:41 pm
- Forum: Development Tools and Programming
- Topic: xflash - 2 questions
- Replies: 3
- Views: 2448
xflash - 2 questions
Two questions for somebody who understands xflash better than me : 1. We have a board which uses 3 x XL232. However, due to current lead-time issues we can't get hold of any of those, but we can get XE232. I've built a couple of boards using XE232 instead of XL232 and they run and program with no ch...
- Tue Feb 23, 2021 6:06 pm
- Forum: Development Tools and Programming
- Topic: xburn: locking device failed
- Replies: 8
- Views: 4083
Re: xburn: locking device failed
No, I'm pretty confident the XN file is fine. We've built several hundred of these boards and had only a couple like this.
Looks like replacing the XL216 devices, which is fiddly...
Looks like replacing the XL216 devices, which is fiddly...
- Tue Feb 23, 2021 4:23 pm
- Forum: Development Tools and Programming
- Topic: xburn: locking device failed
- Replies: 8
- Views: 4083
Re: xburn: locking device failed
Yes, possible. Though it's not a great piece of design if it can fail in a way that bricks the board. Yes, it's a 3 x XL216 design. I'm fairly resigned to having to replace the XL216 that's booting, as I believe that's the only one that gets it's OTP programmed with the AES key - can anyone confirm ...
- Tue Feb 23, 2021 10:24 am
- Forum: Development Tools and Programming
- Topic: xburn: locking device failed
- Replies: 8
- Views: 4083
Re: xburn: locking device failed
Yes, xburn -l works reliably every time.
xburn --read works fine as well, but I've got no idea how to interpret the output.
xburn --read works fine as well, but I've got no idea how to interpret the output.
- Mon Feb 22, 2021 1:11 pm
- Forum: Development Tools and Programming
- Topic: xburn: locking device failed
- Replies: 8
- Views: 4083
Re: xburn: locking device failed
Can you try dropping the jtag speed? It may be a marginal timing/signal integrity problem. For example: --jtag-speed 2 Good idea, but same result "locking device failed". It would help if there was a clue in the error message, but even adding --verbose doesnt give any more information.