On Thu, Jul 30, 2009 at 10:23 PM, Xiaofan Chen<[email protected]> wrote: > I have to change the following line in the target config file from the > following website. > http://www.kunen.org/node/105 > What is the correct configuration about this LM3S1968? >
I am also having problem with J-Link with the EK-LM3S1968. It is not able to flash the flash. I've tried V3 and V6 IAR OEM version of J-Link. Take note the on-board ftdi interface works fine with the same svn version 2570. mc...@ubuntu904:~/Desktop/build/openocd/lm3s1968$ openocd -f interface/jlink.cfg -f lm3s1968.cfg Open On-Chip Debugger 0.3.0-in-development (2009-07-30-20:45) svn:2570 $URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS 1000 kHz (dropped to 500KHz does not help) jtag_speed: 6 (with or without this it failed) jtag_nsrst_delay: 100 jtag_ntrst_delay: 100 Info : J-Link initialization started / target CPU reset initiated Info : J-Link compiled Feb 20 2006 18:20:20 -- Update -- Info : JLink caps 0x3 Info : JLink hw version 30000 Info : Vref = 3.288 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 255 Info : J-Link JTAG Interface ready Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Info : JTAG Tap/device matched Info : accepting 'telnet' connection from 0 Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) Info : JTAG Tap/device matched target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc auto erase enabled Info : Algorithm flash write 1710 words to 0x0, 1710 remaining Error: timed out while waiting for target halted Error: error executing stellaris flash write algorithm Error: flash writing failed with CRIS: 0x0 Error: error writing to flash at address 0x00000000 at offset 0x00000000 (-902) mc...@ubuntu904:~$ telnet localhost 4444 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger > init > reset halt JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3) JTAG Tap/device matched target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc > flash write_image erase > ./StellarisWare/boards/ek-lm3s1968/graphics/gcc/graphics.bin auto erase enabled Algorithm flash write 1710 words to 0x0, 1710 remaining timed out while waiting for target halted error executing stellaris flash write algorithm flash writing failed with CRIS: 0x0 error writing to flash at address 0x00000000 at offset 0x00000000 (-902) called at file "command.c", line 469 called at file "embedded:startup.tcl", line 89 called at file "embedded:startup.tcl", line 91 called at file "embedded:startup.tcl", line 93 # Script for luminary lm3s1968 if { [info exists CHIPNAME] } { set _CHIPNAME $CHIPNAME } else { set _CHIPNAME lm3s1968 } if { [info exists ENDIAN] } { set _ENDIAN $ENDIAN } else { # this defaults to a little endian set _ENDIAN little } if { [info exists CPUTAPID ] } { set _CPUTAPID $CPUTAPID } else { # force an error till we get a good number set _CPUTAPID 0x3ba00477 } # jtag speed jtag_khz 1000 jtag_speed 6 jtag_nsrst_delay 100 jtag_ntrst_delay 100 #LM3S1968 Evaluation Board has only srst reset_config srst_only #jtag scan chain jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 1 -irmask 0xf -expected-id $_CPUTAPID # the luminary variant causes a software reset rather than asserting SRST # this stops the debug registers from being cleared # this will be fixed in later revisions of silicon set _TARGETNAME [format "%s.cpu" $_CHIPNAME] target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNAME -variant lm3s # 4k working area at base of ram $_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x20000000 -work-area-size 0x4000 -work-area-backup 0 #flash configuration flash bank stellaris 0 0 0 0 0 -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
