I downloaded OCD Commander. From what I can tell it doesn't work with the wiggler
interface? Otherwise it seems to be the perfect tool for the job? (examine juicebox
environment, try out code snippets).
Newell, could you give a more detailed description of your setup? At this point, I still haven't figured out how to put small code pieces into Juicebox and execute them.
I'm using the latest OCD Commander under win2k with a generic, non-Macraigor wiggler (I think it's the Olimex arm-jtag http://olimex.com/dev/arm-jtag.html). Not all wigglers have pins 8 & 15 tied together, so you might need to make that mod before recent versions of OCD Commander will recogonize the wiggler. I don't think OCD Commander supports a wiggler under Linux. Any debug setup should work as long as you can read/write memory, halt, go, and download. (Does gdb support a parallel port wiggler, under Linux or windows? Source level debug would be really nice in the very near future, as the programs become more intricate.)
The makefile, linker config, startup code, and test code on now on the Wiki. I would have stuck an .elf or s-record file up too, but I don't yet know how to do a file attachment to the Wiki. Let me know what image format your debuggers support and I'll put together some compiled demos. (I put a cpu register header file up as well, but I've switched to a bunch of #define statements instead, so I need to update that.)
To test code, I first cross-compile (using the RTEMS ARM toolchain) on my win2k box. Then I start the JB, let it run a little bit to init the CPU registers, and halt it with the debugger. I like to set CPSR to turn off interrupts, but that's probably not required. The debugger can then be used to download the code (in my case, a .elf file) into sdram. Set the PC (OCD Commander will do this automatically as part of the download) and it's ready to go.
If you could explain in more detail the trouble you're having with running code on the JB, I could try to be more helpful.