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
no, confound it there has been quite a few posts lately where 'ARM' has been used as an identifier for device dependent parameters, it is getting old for every post having to ask "WHAT?" about some missing detail. "0xFFFF0000 (start of ARM local RAM)" is blatantly false. Also, the OPs reaction to this was (horray) to identify what he was using and state the actual problems (that he had managed to work through).
you stoopid n00b I posted no such thing, I even gave an example of what it should be.
That some are so fragile that they can not handle corrections is not my problem.
Erik
@Silly Sausage, you know, i really do come across as a pain, thank you for pointing that out,
0xFFFF0000 is the start of arm local ram in the am1707 device-dependent memory map, so it was a miscommunication that i should have tried to clear up instead of posting a cryptic "you are wrong"
i should really look into this stuff first before posting
I did NOT post the above although it states "Author erik malund"
^^^ zomg this guy is impersonating ME, how did he do that??? i did NOT write the post saying "I did NOT post the above although it states "Author erik malund"
Erik"