Hi all, I want to port eCos to an epon onu chip which has a MIPS 4KEc core and using openocd v0.4.0 + wiggler for debugging. Gdb seems ok(ctrl_c and continue commands ok) but breakpoint.
Then I try telnet command without gdb: ***************** telnet console ****************************************** [zhouxiaoc...@lemon ~]$ telnet localhost 4444 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. Open On-Chip Debugger > halt target state: halted target halted in MIPS32 mode due to debug-request, pc: 0x81f861b8 > mdw 0x80000000 0x80000000: ee000010 > bp 0x80000000 4 breakpoint set at 0x80000000 > bp 0x80000000, 0x4, 20, 0x0E > mdw 0x80000000 0x80000000: 7000003f > resume ***************** uboot console ****************************************** Uboot > go 80000000 ## Starting application at 0x80000000 ... Buffers = a00bb6f0 sr=0x10008400 Entering twothreads' cyg_user_start() function Beginning execution; thread data is 0 Beginning execution; thread data is 1 Thread 0: and now a delay of 239 clock ticks Thread 1: and now a delay of 230 clock ticks ***************** telnet console ****************************************** > halt target state: halted target halted in MIPS32 mode due to debug-request, pc: 0x80009db4 > mdw 0x80000000 0x80000000: ee000010 It seems breakboint does not trigged at 0x8000000 and the software breakpoint instrument "0x7000003f" is restored when app run. Can any one give some advices? Thanks! Xiaochen Zhou Below is the configure file: parport.cfg: interface parport parport_port 0 parport_cable wiggler product.cfg: (using ar71xx.cfg as template) # Atheros AR71xx MIPS 24Kc SoC. # tested on PB44 refererence board jtag_nsrst_delay 100 jtag_ntrst_delay 100 reset_config trst_and_srst set CHIPNAME ar71xx jtag newtap $CHIPNAME cpu -irlen 5 -ircapture 0x1 -irmask 0x1f -expected-id 1 set TARGETNAME $CHIPNAME.cpu target create $TARGETNAME mips_m4k -endian big -chain-position $TARGETNAME # setup working area somewhere in RAM $TARGETNAME configure -work-area-phys 0xa0600000 -work-area-size 0x20000 _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
