I bought the MR60FDA2 and tested it. Results for Fall Detection was not great. Then I saw that an update exists, so I updated it, but results were not much better.
I then realized that the MR60BHA2 was the same hardware and so I tried to flash the firmware and since then, I can’t do anything anymore, it seems like it keeps sending the same information, but I can’t flash it anymore. What can I do now to restore it, or is it bricked??
Hi there,
And Welcome here…,
SO more than likely it is Bricked if you wrote Firmware not Partitioned for the correct device, they are NOT the Same one is an early release. Heartbeat , Fall and Breathm, the other is just Fall and presence detection.
If you wrote just the Xiao firmware , sure you can un-brick it, If you change the Radar firmware , I don’t think it can be. So I would enter Bootloader Mode and see if anything is alive . If so reflash with the Proper firmware and test it again, Are you using the correct Baud Rate? the Default is 115200 ?
HTH
GL 
PJ 
Hi and thanks for your quick response.
The Xiao works well and is programmed with the passthrough mode program. But I can reprogram it with any other program, that’s not a problem.
I programmed the radar firmware first with MR60FDA2_eeprom_v4.0.18.bin and then with MR60BHA2_eeprom_1.6.4.bin. Now it keeps sending on the OTA upgrade tool the information on my screenshot but doesn’t go in to update mode to receive a new firmware.
And yes, I used 115200 Baud Rate, but I also tried changing it to see if something happens, but there is nothing happening…
1 Like
Hi there,
Yes, I was afraid of that… No method exist AFAIK, maybe Seeed can Comment. There may be some Power UP , force Flash LOAD process with Radar only that is possible. However it may require connection to the bottom pads for SWI.?
HTH
GL PJ
Yes, as PJ_Glasso mentioned. Although the hardware is the same, the software is completely different. Using different firmware across devices is not allowed, as it may cause damage to the radar.
OK, so what do I do now? The hardware is not damaged, it sends regularly information (as seen in my screenshot above), but I can’t “Request Update” anymore.
How can I reprogram it now? I really hope it is possible, otherwise I find it crazy that such expensive hardware not only doesn’t work properly but also can’t be reprogrammed…
SO I asked around , and here is what I can offer. I don’t have a unit to test so I’m limited to Theories … YMMV 
a classic case of cross-flashing incompatible firmware between radar modules — MR60FDA2 and MR60BHA2 have different hardware configurations and EEPROM mappings. Flashing the wrong .bin can mess up the EEPROM header or boot logic, which is why it’s stuck sending malformed packets or stuck in a loop and won’t enter proper update mode.
Here’s how a user can try to recover it:
Option 1: Force Reflash via Seeed OTA Upgrade Tool
- Disconnect the radar module.
- Hold the BOOT or RST button (if present) on the radar module (or short the BOOT pin if the module supports it).
- While holding the button, reconnect the USB or power.
- Open the Seeed OTA upgrade tool immediately.
- Try flashing the correct firmware:
- For MR60BHA2, use:
MR60BHA2_eeprom_1.6.4.bin - Uncheck any automatic detection if the tool supports manual override.
- If the tool sees the COM port but fails the firmware check, try toggling “Force Upgrade” (if visible) or select a recovery mode.
Option 2: Use UART Flashing with a USB-to-TTL Serial Adapter
If the device doesn’t show up as a COM port anymore:
- Connect RX/TX/GND of a USB-to-Serial adapter to the module.
- Set baud rate to 115200 or try 921600 depending on module.
- Try using a terminal like TeraTerm or RealTerm to catch any boot messages.
- If it spits out any data, try entering a break sequence or use a tool like XCOM from Seeed.
- Use the flashing utility from Seeed or any provided
flash_tool_xxx.exeto reflash over serial.
Option 3: EEPROM Reset (if you have access to the EEPROM)
If there’s an I2C EEPROM chip or config block (rare), and if you’ve backed up the original EEPROM contents, you can:
- Manually write back a working
eeprom_vx.x.x.binusing a tool like CH341A programmer or similar.
If none of the above works:
- Reach out to Seeed support and mention:
- The exact model (MR60BHA2)
- That an MR60FDA2 firmware was mistakenly flashed.
- Include screenshots of the OTA tool’s output.
- They may provide a special recovery image or guide you to a deeper UART recovery process.
Pro Tip:
Going forward, always double-check the module label and firmware compatibility. The names are similar, but the hardware is not. MR60BHA2 is usually respiration/heart monitoring, whereas FDA2 is for different radar detection functions.
Let me know what COM port or message the module is sending during power-up — I can decode it for clues.
HTH
GL PJ
I also “asked around” and ChatGPT gave me almost exactly the same answer.
Unfortunately, it is completely useless because:
- The MR60FDA2 only has a Reset button
- The MR60FDA2 has a USB-C port which can only be used for powering, not programming the EEPROM
- There is no “Force Upgrade” or “recovery mode” buttons on the tool
- The MR60FDA2 is used (and programmed) using an XIAO- ESP32-C6, and there should be a way to program the EEPROM through RX/TX or I2C using the XIAO.
So by writing in to this forum, I was hoping to get the last part of ChatGPT’s answer, that is: They may provide a special recovery image or guide you to a deeper UART recovery process.
So is there anyone from Seeed that can help here, or do I need to contact the support outside of this forum?
I would really appreciate if someone from Seeed could give me an answer!
Hi there,
So your reply sounded a TAD salty 
, for trying to help…
I’ll ask plainly did you even understand any of it ? did you try it, any of it. ? You don’t want to answer that’s fine too, but YOU are the one who wrote the wrong file to it, so if you know something more how these devices work as I do, be glad I replied at all. 
GL PJ
for example, Hold the reset button and plug in usb ?
I bet you didn’t…because you would have said so. 
Also now after looking at the schematic , I would wager IT CAN be restored using an external Probe easily. The pins are there the bin file is also and Now I see in the pic, They are on the bottom. 
The more I look at it, hell you may not even need the probe…
That is to say… You only bricked or looped the OTA.
I have tried pulling BOOT1 to ground and to VCC while powering the XIAO and nothing happens.
I don’t have a USB-to-Serial adapter, but as the XIAO is anyways connected to it, it could flash it, if I had the right program to do it.
I’m going to contact Seeed support directly, as this is going nowhere here.
Hi there,
LOL, WHy "Boot1 to GND, it’s already pulled low.
can you read a schematic? Maybe you should have b4 you wrote the WRONG bin file to it. You will still need to read and follow directions and provide answers, So you will end up in the same place AFAIK.
GL PJ