So close yet so far...
Hardware: TI AM1707 EVM - ARM926EJ-S microprocessor (not MCU, so not officially supported in the device database)
Debugger: Segger J-Link
Application: GNU compiler toolchain + working LED code
When loaded with J-Link + GDB, the LEDs light up correctly
When loaded by J-Link + uVision, the debugger SEEMS to give me access to the board, but the application doesn't run correctly (starts near 0xFFFF0000, which is on-chip local ram)...
Am I missing something totally basic here? Any help would be greatly appreciated!!
-Jonathan
Correction, led.hex has to be manually loaded using "LOAD build\led.hex"
i don't know what's going on now, but then again i never did..
ok, previously opcodes were corrupted due to my confused testing
the command "load build\led.hex" had to be issued manually and then set PC to 0xc1080000. maybe this can be done in the initialization script? in any case my blinky example is up and running now
is this really the normal workflow for this $5000 compiler?? gdb is starting to look more and more bang for the buck
is this really the normal workflow for this $5000 compiler??
no, it is not, I, and all I know, do not have any such problems.
Bring up the IDE, load the project [change device} [change debugger settings] and GO
had to be issued manually and then set PC to 0xc1080000 sounds as if you have selected the wrong device.
Erik