I have read through every thread I can find on the topic of iMX6SoloX M4 debugging and have not found a solution yet for Eclipse. We have successfully single-step debugged the M4 on a Sabre-SD Evaluation board using IAR and DS-5 with the JLINK, but with Eclipse Neon we have only been able to load the image into RAM but not execute nor single-step.
1) We have installed the GNU/ARM plug-in for the Segger JLINK, and this seems to be working OK
2) The JLINK connects and a simple hello world program linked for the tightly coupled memory seems to write and be verified correctly according to the console output; we manually stop the A9 during boot and execute the recommended UBOOT commands to setup the vector table, enable the M4 core and take it out of reset.
3) We are using the recommend JLINKSCRIPT for the M4 found on this forum
3) The initial breakpoint does not seem to be set correctly, and any attempt to run/single-step or stop execution seems to always be 'stuck' at a single location. The program never seems to execute properly as we never see any expected debug output on the serial port. If we manually load the image into RAM via UBOOT and execute it works as expected - it also works with IAR workbench and DS-5, but not Eclipse.
Some potential issues:
1) what device should we be using? I have tried cortex-m4 and several imx6 variations, and I seem to get different results with the setting of the program counter depending on which I use. The register tab in the Eclipse debugger doesn't look correct to me regardless of what device I choose, so maybe I am missing something?
2) I read a similar issue on the forum with cache being enabled, maybe this is the issue?
3) I am not too sure if we need to modify/re-compile, or supply the GDB Client 'setup' (as Eclipse calls it) with some architecture specific information?
I am wondering if anyone has successfully single-step debugged from Eclipse Neon on the M4?
thanks,
Jeremy
1) We have installed the GNU/ARM plug-in for the Segger JLINK, and this seems to be working OK
2) The JLINK connects and a simple hello world program linked for the tightly coupled memory seems to write and be verified correctly according to the console output; we manually stop the A9 during boot and execute the recommended UBOOT commands to setup the vector table, enable the M4 core and take it out of reset.
3) We are using the recommend JLINKSCRIPT for the M4 found on this forum
3) The initial breakpoint does not seem to be set correctly, and any attempt to run/single-step or stop execution seems to always be 'stuck' at a single location. The program never seems to execute properly as we never see any expected debug output on the serial port. If we manually load the image into RAM via UBOOT and execute it works as expected - it also works with IAR workbench and DS-5, but not Eclipse.
Some potential issues:
1) what device should we be using? I have tried cortex-m4 and several imx6 variations, and I seem to get different results with the setting of the program counter depending on which I use. The register tab in the Eclipse debugger doesn't look correct to me regardless of what device I choose, so maybe I am missing something?
2) I read a similar issue on the forum with cache being enabled, maybe this is the issue?
3) I am not too sure if we need to modify/re-compile, or supply the GDB Client 'setup' (as Eclipse calls it) with some architecture specific information?
I am wondering if anyone has successfully single-step debugged from Eclipse Neon on the M4?
thanks,
Jeremy
The post was edited 1 time, last by jmcclintock ().