Hi!
I'm trying to get debugging working on a K60 based-system, and it's proving harder than I expected. I'm using Segger's Jlink plus probe with their Ozone debugger. Essentially, the system consists of a K60 with an external CFI flash device. I have some initialisation code running in the K60's internal flash, which finally jumps to the main application code in external flash.
The bootloader code runs fine in the debugger, and I am able to use both hard and soft/flash breakpoints without any difficulty. I am also able to halt and run the code within the main application. The difficulty comes when Jlink attempts to modify the external flash during debugging (e.g setting breapoints), at which point I see '1 over 0' programming errors or 'failed to identify CFI device' amongst other messages.
I've been assuming this is an issue with Jlink, but I'm wanting to see if anyone here has experience of something similar which was ultimately down to a configuration issue on the target device- For example, is there anything that could be set during initialisation that would interfere with Jlink's ability to access external flash during debugging (LMEM caching perhaps)?? Incidentally, I am able to get Jlink to write the application code to external flash at the start of the debug session, the problem only manifests itself once the initialisation routine has run and execution is in ext flash.
I'd be very grateful for any advice/suggestions.
David
