-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Debugging NuMaker-M2351 not working #14
Comments
Hi, Sincerely, |
Hi Mr. Oliveira: Try to create a M2351 secure project from New Project Wizard. Then build it and download the binary to the target chip. Sincerely, |
Hi Mr. Oliveira: Sincerely, |
Everything running smoothly. |
Hi,
I recently started to familiarize with the NuMaker-M2351 board. Since I normally prioritize open-source tools, I was glad to see that Nuvoton had a fork of OpenOCD that I could use to flash and debug the platform. However, I have been facing some issues which I hope you can help me to solve.
I start the openocd bridge by executing the following command:
./src/openocd -f tcl/interface/nulink.cfg -f tcl/target/numicroM23_NS.cfg
Then I start the gdb session, connect to the openocd port, specify the binary and perform a reset
(gdb) target remote :3333
(gdb) file /path/to/file.elf
(gdb) monitor reset init
After I query OpenOCD to list the flash module:
(gdb) monitor flash banks
Ouput:
0 APROM: 512KB
1 actualy I don't know what region is this.
2 LDROM: 4KB
3 CONFIG-BLK: 32B
This are my binary file to be loaded section headers:

After I erase the flash:
(gdb) monitor numicro M2351_erase
Then I try to load the binary:
(gdb) load
I place a hardware breakpoint on the address of the first instruction of the Reset_Handler and execute the command continue
(gdb) hb *0x000102bd
What I would expected now is that the program to be debugged from now on, but it seems that the CPU is locked at least from the ouput from gdb:

Can you help me to figure out what is going on?
The text was updated successfully, but these errors were encountered: