I wonder if this might be a better option for debugging? ( assuming I don’t have a memory issue )
Debugging Embedded projects with PyOCD – VisualGDB Tutorials.
https://visualgdb.com/tutorials/arm/openocd/
If pyOCD is the problem it might by nice to use OpenOCD if possible… ??
Thoughts?
Should I create a new thread now that the problem has changed?
I think that would help others when searching for issues/solutions.
If pyOCD is the problem it might by nice to use OpenOCD if possible… ??
To be honest I don’t use the Mbed Studio because I was not able to debug on my favorite boards. For more about my developing environment see
That allows me use both pyOCD and OpenOCD to debug depending on the actual board.
I’ll look into Mbed CLI.
Do you think my code with no optimizations for debugging is too large to fit into memory? To me it seems like there should be plenty of both flash and RAM. But honestly, I’m not an expert yet with linker files etc as I’ve never really had to deal with them.
Thanks again @hudakz
I’m also not an expert and I was wrong when I said that 0x01E00000 bytes is about 30kBytes. It is actually about 30 720 kBytes! So I think your board has plenty of RAM and flash (significantly more than others).
That’s kind of the conclusion that I came to. Seems odd that gdb /pyOCD is complaining about something.