**** BEGIN LOGGING AT Wed Apr 29 02:59:59 2015
Apr 29 18:34:35 <eddyp> ka6sox, I have jtag on my board, the chip is identified but I can't 'halt
Apr 29 18:34:41 <eddyp> in openocd
Apr 29 18:36:53 <eddyp> I have used an Olimex ARM-USB-OCD
Apr 29 18:37:32 <eddyp> and I also have access to a high end debugger, but the result is the same, can't break/halt it
Apr 29 18:41:25 <eddyp> I $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f board/linksys_nslu2.cfg
Apr 29 18:41:25 <eddyp> Open On-Chip Debugger 0.8.0 (2015-04-14-09:12)
Apr 29 18:41:25 <eddyp> Licensed under GNU GPL v2
Apr 29 18:41:25 <eddyp> For bug reports, read
Apr 29 18:41:25 <eddyp>     http://openocd.sourceforge.net/doc/doxygen/bugs.html
Apr 29 18:41:25 <eddyp> Info : only one transport option; autoselect 'jtag'
Apr 29 18:41:27 <eddyp> adapter speed: 300 kHz
Apr 29 18:41:29 <eddyp> Info : ixp42x.cpu: hardware has 2 breakpoints and 2 watchpoints
Apr 29 18:41:31 <eddyp> 0
Apr 29 18:41:33 <eddyp> Info : clock speed 300 kHz
Apr 29 18:41:37 <eddyp> Info : JTAG tap: ixp42x.cpu tap/device found: 0x29277013 (mfg: 0x009,
Apr 29 18:41:39 <eddyp> part: 0x9277, ver: 0x2)
Apr 29 18:41:41 <eddyp> $ telnet localhost 4444
Apr 29 18:41:43 <eddyp> Trying ::1...
Apr 29 18:41:45 <eddyp> Trying 127.0.0.1...
Apr 29 18:41:47 <eddyp> Connected to localhost.
Apr 29 18:41:49 <eddyp> Escape character is '^]'.
Apr 29 18:41:51 <eddyp> Open On-Chip Debugger
Apr 29 18:41:53 <eddyp> > halt
Apr 29 18:41:55 <eddyp> target was in unknown state when halt was requested
Apr 29 18:41:57 <eddyp> in procedure 'halt'
Apr 29 18:41:59 <eddyp> > poll
Apr 29 18:42:01 <eddyp> background polling: on
Apr 29 18:42:03 <eddyp> TAP: ixp42x.cpu (enabled)
Apr 29 18:42:07 <eddyp> target state: unknown
Apr 29 18:43:12 <eddyp> My end goal is to automatically netboot a NetBSD on the device
Apr 29 18:44:12 <eddyp> I already have a hacked version of the Apex bootloader which calls RedBoot to simulate manually entered commands
Apr 29 18:47:17 <eddyp> I flashed this version of Apex in the Kernel partition, but the problem is that the 'exec 0x1d00000' does not leave the NSLU in the same state as a 'go 0x1d00000' so when Apex calls RedBoot functions execution never returns
Apr 29 18:48:41 <eddyp> so I am tempted to change the RedBoot default command to be 'boot;go 0x1d00000', but since I don't have confirmed JTAG flashing capability I am afraid I could brick the board.
Apr 29 19:00:42 <ka6sox> eddyp, I'm working currently but i'll look in a few hours
Apr 29 19:01:19 <eddyp> thanks a lot
**** ENDING LOGGING AT Thu Apr 30 02:59:58 2015