I'm trying to do a DFU update from Windows 7 and I'm getting the following errors:
From the GUI app:
------------------------------
Device opened.
Ready for firmware update.
Entering upgrade mode...
TUSBAUDIO_GetDfuStatus: Function failed with error code 0xEE000003.
Firmware upgrade failed!
From the command line app:
-------------------------------------
C:\Program Files\Thesycon\TUSBAudio_Driver>dfucons info
Available devices:
Index VID PID REV Serial DFU supported USB mode
00 0x1B12 0x0026 0x06F2 yes APP
C:\Program Files\Thesycon\TUSBAudio_Driver>dfucons download myprog_v1.bin
Downloading myprog_v1.bin to target 0 ...
State 6 (Failed), 0 of 32512 bytes downloaded ...oaded ...
Download failed, completionStatus=0xEF000011
How can I determine what these error codes mean? I don't have source code for these apps or an SDK.
Thanks,
Jim
DFU Programming Errors
-
- Member
- Posts: 11
- Joined: Thu Apr 07, 2016 8:10 pm
-
- XCore Legend
- Posts: 1913
- Joined: Thu Jun 10, 2010 11:43 am
Try using different USB ports on your computer (ie. USB 2.0 ports = usually black insulator inside the USB connector) or even a different PC to perform the upgrade and post your results.
https://lhlabs.com/force/geekout/2093-f ... de-failure
https://lhlabs.com/force/geekout/2093-f ... de-failure
-
- Member
- Posts: 11
- Joined: Thu Apr 07, 2016 8:10 pm
I tried multiple ports (both USB3 and USB2) and multiple machines and I get exactly the same errors.
I noticed that dfucons info does not report a Serial number. Could that have something to do with it?
From the linked-to discussion, it seems that no one seems to know why the updater fails and just try things until it mysteriously works. It would be nice to know what the error codes mean and/or get the source code so I could debug it.
-Jim
I noticed that dfucons info does not report a Serial number. Could that have something to do with it?
From the linked-to discussion, it seems that no one seems to know why the updater fails and just try things until it mysteriously works. It would be nice to know what the error codes mean and/or get the source code so I could debug it.
-Jim
-
- XCore Legend
- Posts: 1913
- Joined: Thu Jun 10, 2010 11:43 am
Not an audio developer but review the following threads and post your results...
http://www.xcore.com/viewtopic.php?t=3031
http://www.xcore.com/viewtopic.php?t=4214
http://www.xcore.com/viewtopic.php?f=26&t=5570
http://www.xcore.com/viewtopic.php?t=3031
http://www.xcore.com/viewtopic.php?t=4214
http://www.xcore.com/viewtopic.php?f=26&t=5570
-
- Member
- Posts: 11
- Joined: Thu Apr 07, 2016 8:10 pm
It turns out that the problem had to do with the lack of sample clocks driving the XCORE-200 during an update.
Our hardware disables the sample-rate clocks on the TDM streams in update mode, which seems to cause problems for the XMOS software. Keeping these clocks running while performing a DFU update solves the problem.
Our hardware disables the sample-rate clocks on the TDM streams in update mode, which seems to cause problems for the XMOS software. Keeping these clocks running while performing a DFU update solves the problem.
-
- XCore Addict
- Posts: 188
- Joined: Tue Jan 17, 2017 9:25 pm
Hello, I think I am having the same issue. Did you just keep deliver() going in audio.xc instead of dummy_deliever()?