Contributed by WangChong, curated by Ai-Thinker

Hello everyone, I finally found how to debug BL6xx chips with CKLink. The link is below.

https://bl-mcu-sdk.readthedocs.io/zh-cn/latest/get_started/eclipse.html#eclipse-gcc

Currently supported chips:

Unfortunately, the Ai-M61-32S dev board that most of you have does not support this debugging, because some of its pins are NC (I have tried it). Currently, the only one I can confirm works for debugging is the Ai-M61-32S-DU (which brings out all the IO pins).

Also, this debugging is not like a traditional reset that re-runs the code from the beginning. Here, the MCU is NOT reset — the previous code is still running, and then the code is re-executed.

When entering debug mode, all three LEDs are on. When debugging reaches the point in the figure above, one goes out and the color becomes purple.

I'd like to make a suggestion: I hope Ai-Thinker's next product PCB design can bring out all the pins that exist, to make debugging convenient. Otherwise, even with this dev board, debugging is impossible. Also, for modules, you could refer to how other STM32 download ports are done and bring them out separately at the head of the board, so users don't have to search everywhere. For boards like the Xiao An Pai S1, I hope a debug socket can be added. Add a chicken leg for me, boss @幼儿园园长

Have questions?

For other questions, please visit the unified discussion area: Ai-Thinker Discussions