I currently use IAR workbench and a Segger JLINK ULTRA+ to run simple test routines on the m4 side of the i.mx8 processor. This works.
I am now attempting to use JLINK commander to do the same, but have running into difficulties. The same code compilation is being used for the IAR build, however, IAR uses a *.out file whereas the Jlink only accepts the *.bin version of the compiled file. The IAR workbench is setup to generate both file types.
So far I am able to use JLINK to connect to the device, write the binary file to RAM and verify the binary is stored in the correct location. When I attempt to run the program , however, it appears to not execute properly.
Here is the commander script that I have been using:
device MIMX8MM3_M4
speed 4000
si jtag
rsettype 0
h
setpc 1ffe0000
loadfile c:/mc_code/raw_test_code.bin 1FFE0000
verifybin c:/mc_code/raw_test_code.bin 1FFE0000
r
At this point, if I type "go" at the command prompt, I should see a message from my program out the com port, but instead see nothing. If I halt the program, the program counter stops at memory address 1FFE4786.
If I rerun the script, and then step through the code line by line, I get a "T-BIT of XPSR is 0 but should be 1. Changed to 1" response. The screen capture attached is of what I observe when I start stepping through the code.
After this point, the program counter seems to go to address 0x000000 which is outside the range of RAM addressing. Shortly after that, it winds up at 1FFE4786.
So I am now pulling my hair out as to why it is doing this.
Please help to straighten this out for me if you can.
I am now attempting to use JLINK commander to do the same, but have running into difficulties. The same code compilation is being used for the IAR build, however, IAR uses a *.out file whereas the Jlink only accepts the *.bin version of the compiled file. The IAR workbench is setup to generate both file types.
So far I am able to use JLINK to connect to the device, write the binary file to RAM and verify the binary is stored in the correct location. When I attempt to run the program , however, it appears to not execute properly.
Here is the commander script that I have been using:
device MIMX8MM3_M4
speed 4000
si jtag
rsettype 0
h
setpc 1ffe0000
loadfile c:/mc_code/raw_test_code.bin 1FFE0000
verifybin c:/mc_code/raw_test_code.bin 1FFE0000
r
At this point, if I type "go" at the command prompt, I should see a message from my program out the com port, but instead see nothing. If I halt the program, the program counter stops at memory address 1FFE4786.
If I rerun the script, and then step through the code line by line, I get a "T-BIT of XPSR is 0 but should be 1. Changed to 1" response. The screen capture attached is of what I observe when I start stepping through the code.
After this point, the program counter seems to go to address 0x000000 which is outside the range of RAM addressing. Shortly after that, it winds up at 1FFE4786.
So I am now pulling my hair out as to why it is doing this.
Please help to straighten this out for me if you can.