**** BEGIN LOGGING AT Wed Jun 05 02:59:58 2013 **** BEGIN LOGGING AT Wed Jun 05 13:15:45 2013 **** BEGIN LOGGING AT Wed Jun 05 13:36:47 2013 **** BEGIN LOGGING AT Wed Jun 05 14:29:27 2013 **** BEGIN LOGGING AT Wed Jun 05 15:48:29 2013 **** BEGIN LOGGING AT Wed Jun 05 15:56:07 2013 **** BEGIN LOGGING AT Wed Jun 05 19:31:19 2013 Jun 05 19:42:01 Hello. I'm Marco and I'm new to debugging software with a development board and Jtag (though I'm familiar with gdb). I have some questions concerning debugging code using a Segger J-link plugged in a Freescale i.MX53 (Cortex A8). Please excuse me if I'm not asking this in the right place, but it seems to stem in either me not being familiar with debugging with a jtag or maybe some inconsistency in my environment. Jun 05 19:43:20 The board is currently booting u-boot from an sd card. I'd like to (a) write the code i'd like to debug into memory and (b) make u-boot jump to it, so I can debug it. Jun 05 19:44:16 Currently, I'm waiting for the board to get to the u-boot command line, strike CTRL+C on gdb to stop, load a binary to memory using "restore binary 0x70000000", set a breakpoint to my binary's _start (addr 0x70000000) and continue u-boot execution by typing "continue" on gdb Jun 05 19:45:30 After this, I get a SIGTRAP ("Trace/Breakpoint Trap") but not at 0x70000000, but at 0x00000070 Jun 05 19:46:18 Am I doing something wrong? The only breakpoint is set at 0x70000000. What could be happening? Jun 05 19:52:52 #edev might be better for this Jun 05 19:53:30 disasm the instruction, see what it is Jun 05 20:04:40 Hey roxfan, thanks, I'll ask there too. Jun 05 20:05:10 did a disas at 0x00000070, nothing that I recognise there :-/ Jun 05 20:13:19 how would one normally load a binary to memory? Is it really with restore? **** BEGIN LOGGING AT Wed Jun 05 21:22:53 2013 **** ENDING LOGGING AT Thu Jun 06 02:59:58 2013