On Fri, Jun 3, 2011 at 5:06 PM, Tom Schouten <t...@zwizwa.be> wrote: > On 06/03/2011 05:04 PM, Tom Schouten wrote: > my bad, it's here: > > http://openocd.berlios.de/doc/html/Architecture-and-Core-Commands.html > 16.6 Software Debug Messages and Tracing
Yes, you found it ;). As a hint of implementation in your software you can take a look at ARM Linux sources. I tried similar thing and I can confirm that it works - I was able to receive serial Low Level debug messaged over JTAG, printed on the Minicom... Turn on Low Level debugging compilation macro, look here :http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=arch/arm/kernel/head.S;h=278c1b0ebb2ee340fcb0e4f4b010c80e535c9308;hb=1fa7b6a29c61358cc2ca6f64cef4aa0e1a7ca74c for the lines like this : #ifdef CONFIG_DEBUG_LL 223 #ifndef CONFIG_DEBUG_ICEDCC 224 /* 225 * Map in IO space for serial debugging. 226 * This allows debug messages to be output 227 * via a serial console before paging_init. 228 */ 229 addruart r7, r3 230 231 mov r3, r3, lsr #20 232 mov r3, r3, lsl #2 233 234 add r0, r4, r3 235 rsb r3, r3, #0x4000 @ PTRS_PER_PGD*sizeof(long) 236 cmp r3, #0x0800 @ limit to 512MB 237 movhi r3, #0x0800 238 add r6, r0, r3 239 mov r3, r7, lsr #20 240 ldr r7, [r10, #PROCINFO_IO_MMUFLAGS] @ io_mmuflags 241 orr r3, r7, r3, lsl #20 242 1: str r3, [r0], #4 243 add r3, r3, #1 << 20 244 teq r0, r6 245 bne 1b 246 247 #else /* CONFIG_DEBUG_ICEDCC */ Hope that helps. BR, Drasko _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
