Why is it that after I dragged and burned the daplink firmware in bootloader mode, it succeeded, but when I disconnected and reconnected, it changed to bootloader mode.
Open
- Dominant language
- C
- Stars
- 2.8k
- Forks
- 1.1k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Description
Why is it that after I dragged and burned the daplink firmware in bootloader mode, it succeeded, but when I disconnected and reconnected, it changed to bootloader mode.
Contributor guide
Research direction
The issue only identifies DAPLink firmware and bootloader mode; no source file, test, board, or firmware version is named. Start by reproducing the drag-and-flash, disconnect, and reconnect sequence, then inspect the bootloader and firmware startup paths to determine why the device remains in bootloader mode. Done means identifying the cause and confirming a reliable normal-boot result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100