Dear Sir/Madam,
I tried to run prox_reporter on the basic kit compatible board.
I used Keil's debug menu to run the code. To my surprise, the monitor can't find it. Looks like the advertisement is stopped.
I burned the code into the flash of the board. After the reset, the monitor can scan and connect to the prox_reporter without any issue.
Why does the JLink debug has the different behaviour compare to execution from flash?
Thanks!
Regards,
Simon
Keywords:
Device:
Hi xixixihaha,
If you use debugger to download the prox_reporter code into target board, you have to stop the debug before the code can run. Means after downloading, just kick start/stop debug button on keil.
Regards!
PY
Yes PY. I know how to run it.
The issue is - if you run it with debugger. The monitor can't find it. But if you burn it into flash and power cycle it. The monitor can find and connect to it.
Hi xixixihaha,
As I said, you HAVE TO STOP debugger before the code can release and go. Have you done this?
Regards!
PY
Hi xixixihaha,
Let me give you more details, the procedure to run proximity report with debugger:
1. compile&link the code and download it into your IC with JTAG debugger
2. kick run and let the program go;
3. kick stop debugger to release the debugger.
Note the step No. 3 is a must when you run code with low power mode.
Regards!
PY
Hi PY,
Thanks so much! I got your point.