31
NXPTM M522XX, KINETIS and i.MX RT / Re: Service Pack 6 and CodeWarrior 7.0
« on: March 01, 2008, 07:35:06 AM »
Hi, Mark.
Sorry to have been silent for the last couple of days, but other projects intruded.
I've now got SP6 and CW 7.0 working together as expected -- but I can't be sure what it is that I did that made this happen. My best guess is that wiping out the data directory, ...\Applications\uTaskerV1.3\CodeWarrior_M5223X\uTaskerV1.3\uTaskerV1.3_Data, and then restarting CW 7.0 may have been what did the trick. But I also spent a bit of time with a new project, staring at its startup code, trying to decide whether I needed to prepend an underscore to the start label in Startup.s; i.e., trying to decide if start or _start was the right value for the Entry point in the linker options (I decided it should be start). Maybe my manipulation of the linker options reset something. As you might be able to tell, I'm grasping at straws and don't know what fixed the problem.
Now, when the debugger starts, it shows .debug_frame +0x00000005 and DummyFn1. I can single step as expected, and if I let the program run and then stop it using "break", it ends up in a reasonable place in the program, not still stuck at the top.
I don't yet have the code I wrote working as it did with SP5 and CW6.4, but now I can work on that problem.
Best regards,
Richard
Sorry to have been silent for the last couple of days, but other projects intruded.
I've now got SP6 and CW 7.0 working together as expected -- but I can't be sure what it is that I did that made this happen. My best guess is that wiping out the data directory, ...\Applications\uTaskerV1.3\CodeWarrior_M5223X\uTaskerV1.3\uTaskerV1.3_Data, and then restarting CW 7.0 may have been what did the trick. But I also spent a bit of time with a new project, staring at its startup code, trying to decide whether I needed to prepend an underscore to the start label in Startup.s; i.e., trying to decide if start or _start was the right value for the Entry point in the linker options (I decided it should be start). Maybe my manipulation of the linker options reset something. As you might be able to tell, I'm grasping at straws and don't know what fixed the problem.
Now, when the debugger starts, it shows .debug_frame +0x00000005 and DummyFn1. I can single step as expected, and if I let the program run and then stop it using "break", it ends up in a reasonable place in the program, not still stuck at the top.
I don't yet have the code I wrote working as it did with SP5 and CW6.4, but now I can work on that problem.
Best regards,
Richard