Cannot flash XM125 module any more

I am trying to use the XM125 pulsed radar breakout board.
Initially, I managed to flash the Acconeer Exploration Tool binary to the board from the STM32CubeProgrammer tool.
Hoever, the Exploration Tool itself gave me a timeout on the serial connection (as others are reporting too in different discussions).
I then flashed the Exploration Tool binary again, from within the Exploration Tool itself. This also seemed successful. However, the tool still gave the timeout error.

However, ever since, I am unable to flash the module again.
Both from STM32CubeProgrammer and from the Explorer Tool, I get an error saying that it cannot connect to the board in boot mode. The error message from STM32CubeProgrammer is:

Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again…

From the Explorer Tool the error message is:

synchronization failed for ‘COM13’, make sure device is in DFU mode

I am pretty sure I am pressing the button in the right way and order and that the USB driver is OK.

I have tried it also on different PCs with the same result.
I am stuck on what to try next.

Any suggestions would be welcome.

First I would try a different known-good usb cable

Make sure you follow the correct button sequence and uart baud settings Flashing Firmware to the XM125 - SparkFun Qwiic Pulsed Coherent Radar Sensor Breakout - Acconeer XM125 Hookup Guide

It also might be worth trying the other tool (python exploration tool)…there are instructions @ the links on the left side of the page

Hi @mgeilen
Any luck on the issue?
(I’ve just bought the board and can’t flash eveon once.)

Dear Support
The below is a screenshot from serial port monitoring. Does it mean there’s a communication between PC and board?

Please advise.
Thank you

Does a COM port appear when plugged in? Test using alternate cables & ports if necessary

Mine turned out to be broken.
At least, I replaced it and the replacement worked fine.

Dear @TS-Russell
The com port appears in the windows device manager. As suggested, I’ve tested other data cables (usb-a to sub-c, usb-c to usb-c) on different pc’s with no luck. Is there a way to check if the board is in the correct boot mode using multimeter or in any other way?
Thank you

ps. This is my session in STM32CubeProrammer:
16:10:27:149 : UR connection mode is defined with the HWrst reset mode
16:10:27:151 : RTS low
16:10:27:151 : DTR low
16:10:27:157 : Serial Port COM8 is successfully opened.
16:10:27:157 : Port configuration: parity = even, baudrate = 115200, data-bit = 8, stop-bit = 1.0, flow-control = off
16:10:27:157 : No Init bits value is : 0
16:10:27:157 : Sending init command:
16:10:27:159 : byte 0x7F sent successfully to target
16:10:29:159 : Wait ends after 1 loop, dataready = 0, delay = 2001
16:10:29:159 : Timeout error occured while waiting for acknowledgement.
16:10:29:159 : No response from target received
16:10:29:159 : Retrying UART init connection…
16:10:29:159 : byte 0x7F sent successfully to target
16:10:29:259 : Wait ends after 1 loop, dataready = 0, delay = 101
16:10:29:259 : Timeout error occured while waiting for acknowledgement.
16:10:29:259 : No response from target received
16:10:29:259 : Error: Activating device: KO. Please, verify the boot mode configuration and check the serial port configuration. Reset your device then try again…
16:10:29:295 : UART PORT CLOSE

Hi
I did one more check. I called
./python -m acconeer.exptool.flash flash XM125 --port COM4 --image acc_exploration_server_a121.bin

The result:

Traceback (most recent call last):
File “runpy.py”, line 197, in _run_module_as_main
File “runpy.py”, line 87, in run_code
File “D:\radar\portable_exploration_tool\tools\python-3.9.10-embed-amd64\lib\site-packages\acconeer\exptool\flash_main.py”, line 7, in
main()
File “D:\radar\portable_exploration_tool\tools\python-3.9.10-embed-amd64\lib\site-packages\acconeer\exptool\flash_flasher.py”, line 406, in main
_flash(args)
File “D:\radar\portable_exploration_tool\tools\python-3.9.10-embed-amd64\lib\site-packages\acconeer\exptool\flash_flasher.py”, line 313, in _flash
flash_image(
File “D:\radar\portable_exploration_tool\tools\python-3.9.10-embed-amd64\lib\site-packages\acconeer\exptool\flash_flasher.py”, line 101, in flash_image
bootloader.flash(flash_device, serial_device_name, image_path, progress_callback)
File “D:\radar\portable_exploration_tool\tools\python-3.9.10-embed-amd64\lib\site-packages\acconeer\exptool\flash_stm32uart_stm32flasher.py”, line 56, in flash
flasher.sync()
File “D:\radar\portable_exploration_tool\tools\python-3.9.10-embed-amd64\lib\site-packages\acconeer\exptool\flash_stm32uart_stm32flasher.py”, line 182, in sync
raise Stm32FlashException(msg)
acconeer.exptool.flash._stm32uart._stm32flasher.Stm32FlashException: DFU synchronization failed for ‘COM4’, make sure device is in DFU mode
Please advise.
Thank you

Hardware Overview - SparkFun Qwiic Pulsed Coherent Radar Sensor Breakout - Acconeer XM125 Hookup Guide Has a bit of advice

Have you made any progress while I was out?

I reported an issue to your distributor, technical support checked the unit, and it turned out to be faulty. I’m now waiting for a replacement.
Thank you for your help.

Did you remove the firmware by any chance?

No, just followed the official docs
Flashing Firmware to the XM125 - SparkFun Qwiic Pulsed Coherent Radar Sensor Breakout - Acconeer XM125 Hookup Guide

I received another (replaced) unit which works fine.
Best Regards

Good to hear! Happy hacking!

hello all.
I have the same situation as topic starter.
I have ordered via DigiKey this module - SparkFun Qwiic Pulsed Coherent Radar Sensor - Acconeer XM125 (Qwiic)SEN-24540

I was able (or rather, used to be able) to flash the new firmware (acc_exploration_server_a121.bin) using the STM tool, but I could not connect to it through the Exploration Tool.

After trying several times, I came across a suggestion here about “flipping the USB-C cable.” After doing that, I noticed that the module started getting very hot.

Since then, I have no longer been able to flash the firmware.

I investigated the area that was overheating and found that a small capacitor appears to have become desoldered due to the high temperature. There is also a nearby, slightly larger capacitor that no longer seems to be properly attached to its pads and may come loose soon as well.

this was new module - just unpacked it and tried to connect to Exploration tool via this manual

I think I need replace this module but how to do it?
Please advice..

Darn; You’ll just need to contact DK for a replacement RMA and they should send you a new board ASAP - link to your post/this thread if you’d like :slight_smile:

Thank you for your reply.

It seems that I am not eligible for the replacement procedure, as I ordered the item on February 9 and it is now outside the 30-day warranty period.

I received the following response from support:

This part is outside the manufacturer warranty.

In that case, I have another question.

Would it be possible to provide the specifications or values of these capacitors? I would like to check whether I can replace them and repair the board myself.

Certain items (mostly the expensive stuff) have a 1-year warranty for defects; I’m not sure if the xm125 is one of those or not but I will check and let you know (DK honors our policies, sometimes with nudging)

It looks like the capacitor values are listed in the xe125 datasheet (xm125 is our product number indicating the additional red PCB to the xe125 module)…based on the photo I’d replace C7 (4.7uF, 1005 package?) and C8 (100 nF, 0603 package)

If you can de-solder and re-solder those it’d likely be a lot faster than an RMA

thank you!
need to find this tiny C7 and check how to install it.
will keep you posted)

but of course - if it possible to replace the board- would be much better..