ReSpeaker Mic Array v2.0, can not find DFU Device

Products & Technology ReSpeaker
1

Hi All,
After flashing with:

sudo python dfu.py --download MicArrayV3_firmware/6_channels_dfu_4.0.0_firmware.bin

my device no longer enumerates in DFU mode. How can I recover/force it back into DFU? I’m considering reflashing with:

sudo python dfu.py --download 6_channels_firmware.bin

Is this the correct firmware and procedure to restore DFU detection?

Thanks

2

I ran into the same problem, put it into recovery mode per the docs by holding down either btn A or reset then plug into the USB C port (not the ESP32) then it should work fine.

3

@Michael_Arthur
Could you provide the documentation? Also, I don’t see a reset button on the board. Thanks.

4

Actually can you grab dfu-util and type in dfu-util -l and see if the xmos chip shows up for a start, I actually got confused with this one and the vxf3800

Could also double check your cable is a data cable if its micro USB, ran into this issue many times with other devices

5

I purchased the product from the following link.

When I run dfu-util -l, the only thing that appears is: found runtime: [2886:0018] ver=0400, devnum=32, cfg=1, intf=4, path=“3-1”, alt=0, name=“SEED DFU”, serial=“UNKNOWN”.

6

Any solution? I have the same model and can’t get it in DFU mode to update the firmware

7

I had the same problem; have you solved it yet?

8

I think the problem may be that you initially put the MicArray V3 firmware on a V2 device, and that bricked the device. The V3 here is referring to the hardware version, not the software version. There does not seem to be any way to recover from this, that I have found.

9

I reported this issue to the seeedstudio techsupport email address and when I hear back I will post again here.

1 Like
10

I received a response from SeeedStudio tech support. They said that since this was an error on my part (likely true in my case) they will not cover it for free. They said they could fix the hardware for a cost with internal tools but that would likely exceed the cost of purchasing a new unit. It is a shame to waste perfectly good hardware, but I understand the economics. I think this is a fair response. I think the Seeedstudio hardware is generally excellent and the prices are reasonable. However:

  1. The firmware should contain a checksum that includes the hardware version so that an incompatible firmware CANNOT be written to any device that will be bricked!

  2. The firmware labeling is confusing with hardware and software versions being mixed.

They have apparently addressed this bricking problem with the newer ReSpeaker XVF3800 which always retain an ability to revert to a failsafe configuration. Our older ReSpeaker XVF3000 V2 units do not contain any way to truly revert to a failsafe configuration (the --revertfactory option in dfu.py tool does NOT do this).

Since I expected that my XVF3000 V2 ReSpeaker would not be recoverable, I ordered an XVF3800 ReSpeaker (USB) a few weeks ago. I have been using it since then. It seems to be excellent when it works, however with the current firmware (2.0.7) the XVF3800 USB ReSpeaker locks up after the host computer reboots! This makes it very difficult to work with for now unless you have physical access to the machine to reset it when necessary. Warm rebooting the computer does not bring it back! Only hard power cycling will bring the ReSpeaker back. Other applications using I2C may not have this problem; I am using the USB version.

Hopefully there will be a new firmware for the USB XVF3800 ReSpeaker that will be able to work after the host computer reboots.