Firmware upgrade, keep getting the same error, not getting a

[mon2]

Hi. Sorry for the quick post and delete - wrote some wrong info.

Which version of the M8 software do you have currently on your box ? The application should display this when you run the program.

Review this thread which is very much on topic:

http://www.xcore.com/forum/viewtopic.php?f=8&t=3031

Based on this information, it is very possible that the firmware you have currently on your box is preventing you from further upgrading to a more current release. That is what is being discussed on the above thread.

From this thread, you may get lucky with some PC and allow you to skip over this buggy firmware:

http://lhlabs.com/force/geekout/2093-fi ... de-failure

Specifically:

http://lhlabs.com/force/geekout/2081-ge ... rades-and-...

Some general talk:

a) you may consider to keep trying different computers and operating systems and may get lucky and work around the bug that appears to be present on some of these DFU releases (see the above thread on versions)

b) if not - are you a hardware person ? Or do you know one ? The idea here is that pretty sure I saw a view of the internal circuit board and to the top right of the PCB (near the USB connector) is a surface mount 8 pin IC which is very likely the flash IC that holds the code for your widget. First, this must be confirmed and you can do this by reviewing the part markings on the little guy. Next, you could in theory, remove the contents of the firmware from a working / current box or perhaps even the image file you have (need to do some homework to find the true contents - can check locally) and then implant the contents using a very simple / low cost USB to SPI tool. The flash IC is a SPI interface.

We are designing some products with XMOS and 110% covering our bases so that such issues as yours do not surface - we do not wish to be responsible for shipping from around the world. We always have methods to "resurrect dead boards" as a Plan B.

Write back if you wish to continue this dialog but believe it should be possible. The binary file should contain all that you need to directly write to the target flash device. You will have to be patient but should be very possible to fix. In the process, good idea to backup the current contents of the firmware.

From assorted readings, you are not alone with this issue. Do post the version of the firmware and will ask our local XMOS FAE for advice. Also on one of the documents on the xmos.com website is the file structure on how DFU works.

Where are you located ? US ? Europe ? Canada ?

===================

Update:

Review the USB ports being used on your PC for this update. Is it a blue color insulator in the connector = USB 3.0 ?

If yes, insert your USB cable into a different (non blue) USB connector = USB 2.0. The use of a USB 2.0 connector has also been reported to fix this issue.

===================

Update # 2:

Do you have the dfucons.exe program ? This is a console based flash programming utility and is available from this download:

https://www.xmos.com/published/usb-audi ... er-windows

Download and extract this package. The dfucons.exe program is posted inside the following folder (after you run the download):

C:\Thesycon\TUSBAudio_v2.23.0\EvaluationKit\utilities

Copy the dfucons.exe program and paste into the following folder:

C:\Thesycon\TUSBAudio_v2.23.0\EvaluationKit\DriverPackages\XMOS_EVAL_KITS_DEMO\DriverSetup\release

This is because when you run the dfucons.exe program, the application will search for the supporting dll files to launch.

Once you have done this, enter the dos prompt (aka Command Prompt - admin) and enter the following commands:

cd\ <ENTER> ; to take you to the root folder on your hard drive

cd C:\Thesycon\TUSBAudio_v2.23.0\EvaluationKit\DriverPackages\XMOS_EVAL_KITS_DEMO\DriverSetup\release

to enter the folder with the dfucons.exe program.

Then type:

dfucons info <ENTER>

What do you see from this command ? If the USB based M8 is docked then it should be listed with this utility.

Then try:

dfucons download firmware_filename.bin   <ENTER>

Change the firmware_filename.bin to suit the file the vendor sent to you. Be sure the binary file is also copied into the same folder as you are in and then run the above command. Does that work for you ?

[pas]

I am in the US, Colorado. I have tried USB 2.0 and 3.0. I will take a look at the thread above  and see what I can find. 6.6 is firmware on the machine.

[pas]

I will try it tomorrow, I am at work now. I appreciate all of the time and effort you have given to me. Thank you!

[pas]

Please explain your last paragraph in greater detail, I don't quite understand.

[mon2]

Does your M8 box function ok as-is ? Believe you must run some device drivers on Windows and then use with Windows programs to stream you audio ? Or is it defective ?

Does the graphical flash utility that reports the error list the firmware version of your box ? If yes, what is the firmware version ?

From other posts on this subject, if you can view the firmware version, you should be able to reflash the box but may take some attempts using USB 2.0 ports and an older Windows operating system. This is due to some coding bug in the DFU and also how Windows treats USB 3.0 ports.

There are some buggy USB 3.0 controller ICs on the market so for that reason you should seek out the use of USB 2.0 controllers / ports.

It should be very possible to reflash the SPI flash chip (8 pin device) located near the XMOS CPU on the M8 box. From the (not clear) PCB photo on the internet, looks to be between the XMOS CPU & the USB connector (top right to the XMOS CPU). Appears to be the "Winbond" brand. That is, if this part is reflashed or removed from the design and then reflashed with factory firmware, you will have effectively injected the same binary file directly to this memory device. However, this procedure will take some effort and care - of course best to make a backup of the current contents of this SPI flash memory device. The Winbond and similar SPI memory devices are not copy protected so they can be easily read or written to using some very low cost tools.

The most sane approach is to keep testing the supplied reflash program on different boxes / operating systems. Perhaps works with a local and friendly computer shop on this task. Will ask our local FAE on why dfucons is reporting no devices found. Wondering if the dfucons utility is only searching for specific USB Vendor and product IDs - not sure at this time of writing. That is, if your box is operational and the graphical program reports the proper version then in theory you should be able to reflash the code - unless the vendor has removed the DFU code which does not appear logical since others are reporting success after some toying with the widget. Once you have the most current DFU firmware, you should be able to work around the current bug moving forward. That is at least how we understand this issue.

 

[mon2]

Does your M8 box function ok as-is ?

Does the program that reports the error list the firmware version ? If yes, what is the firmware version ?

From other posts on this subject, if you can view the firmware version, you should be able to reflash the box but may take some attempts using USB 2.0 ports and an older Windows operating system. This is due to some coding bug in the DFU and also how Windows treats USB 3.0 ports.

It should be very possible to reflash the SPI flash chip (8 pin device) located near the XMOS CPU on the M8 box. From the (not clear) PCB photo on the internet, looks to be between the XMOS CPU & the USB connector (top right to the XMOS CPU). Appears to be the "Winbond" brand. That is, if this part is reflashed or removed from the design and then reflashed with factory firmware, you will have effectively injected the same binary file directly to this memory device. However, this procedure will take some effort and care - of course best to make a backup of the current contents of this SPI flash memory device. The Winbond and similar SPI memory devices are not copy protected so they can be easily read or written to using some very low cost tools.

The most sane approach is to keep testing the supplied reflash program on different boxes / operating systems. Will ask our local FAE on why dfucons is reporting no devices found. That is, if your box is operational and the graphical program reports the proper version then you should be able to reflash the code. That is, unless the vendor has removed the DFU code which does not appear logical since others are reporting success after some toying with the widget.

 

[pas]

The unit functions fine, the only two issues I have are that it turns off automatically after five minutes of inactivity and the DSD channels are reversed.

[pas]

Firmware version 6.60

[evert]

Hi,
can some one please sent me the firmware v6.60?
the link to the download is not working.

thank you