Hi
My application has a bootloader which runs in the K60 internal flash, then jumps to an entry routine in an external flash bank.
I can debug the bootloader perfectly, but as the transition to loading the external flash code is proving tricky, I'm looking for a more straightforward approach to debugging the external flash code, which I think might be achieved by the 'attach to running program' option.
I'm using a 'default' jdebug project (haven't commented anything in/out), and am seeing the 'Target Connection Lost' message (see attached) following the attempt to connect Ozone to the running target- Any ideas as to what might cause this issue?
Many thanks
David
My application has a bootloader which runs in the K60 internal flash, then jumps to an entry routine in an external flash bank.
I can debug the bootloader perfectly, but as the transition to loading the external flash code is proving tricky, I'm looking for a more straightforward approach to debugging the external flash code, which I think might be achieved by the 'attach to running program' option.
I'm using a 'default' jdebug project (haven't commented anything in/out), and am seeing the 'Target Connection Lost' message (see attached) following the attempt to connect Ozone to the running target- Any ideas as to what might cause this issue?
Many thanks
David