MAX32630FTHR cannot flash firmware via DAPLink FAIL.TXT: transfer timed out

Mbed OS
, ,
1

Hello everyone,

I am using a MAX32630FTHR board with a MAX32625PICO / DAPLink adapter to flash firmware through the 10-pin SWD/JTAG ribbon cable.

My setup is:

  • Board: MAX32630FTHR

  • Programmer: MAX32625PICO / DAPLink

  • Connection: PC → DAPLink adapter → 10-pin ribbon cable → MAX32630FTHR

  • MAX32630FTHR is powered separately by USB/battery

  • VTref on J4 pin 1 to GND measures about 1.8V

  • DAPLINK drive appears normally on Windows

The problem is that every time I drag and drop a .bin firmware file to the DAPLINK drive, it creates a FAIL.TXT file with this error:

error: The transfer timed out.
type: transient, user

I tried flashing:

  • blinky_max32630fthr.bin

  • MAX86150EVSYS firmware .bin

  • A .bin compiled from Keil Studio Cloud for target max32630fthr

All give the same “transfer timed out” error.

I also tried:

  • Checking the 10-pin ribbon cable direction

  • Checking that the cable is not loose or shifted

  • Powering the MAX32630FTHR by USB

  • Pressing SW1 before flashing

  • Trying another DAPLink adapter

  • Measuring VTref on J4 pin 1, which is 1.8V

At the beginning, the MAX32630FTHR LED was lighting/blinking. After several failed flashing attempts, the LED stopped lighting. I also noticed that the 1.8V pin has voltage, but the 3.3V pin does not show voltage.

My questions are:

  1. Does VTref = 1.8V mean the MAX32630FTHR should still be programmable through SWD?

  2. Is “transfer timed out” usually caused by SWD communication failure, target reset issue, or DAPLink firmware mismatch?

  3. Is there a recommended recovery method for MAX32630FTHR, such as connect-under-reset or mass erase?

  4. Could the missing 3.3V rail be normal if the firmware/PMIC is not running, or does it indicate a hardware problem?

  5. If drag-and-drop DAPLink flashing fails, what is the recommended next step to recover the board?

Thank you very much for your help.