Hi there. I am refering to https://lists.berlios.de/pipermail/openocd-development/2011-June/019532.html and https://lists.berlios.de/pipermail/openocd-development/2011-June/019533.html
I also try to get the Freescale Kinetis KwikStik (and later a K60N512) working with openocd, but have not been successful yet. Are there anywhere config files for the board or the chip? Marcelo Politzer, did you get it working? j. m. norris, how did you test? I tried using config files for a Cortex-M3 board and started with "-f interface/jlink.cfg -f board/stm3210e_eval.cfg", but realized soon that the board will not work in my configuration. So I started to write my own board/kinetis_kwikstik.cfg and target/k40.cfg (see below). Right now I am stuck with an "JTAG-DP STICKY ERROR" on the KwikStik: Open On-Chip Debugger 0.4.0 (2011-06-17-09:45) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html 1000 kHz Info : J-Link initialization started / target CPU reset initiated Info : J-Link Lite-FSL V1 compiled Jan 31 2011 11:00:51 Info : JLink caps 0xb8ea7a3b Info : JLink hw version 9010000 Info : JLink max mem block 9096 Info : Vref = 3.141 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0 Info : J-Link JTAG Interface ready Info : clock speed 1000 kHz Info : JTAG tap: k40.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4) Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000012, MEM_AP_TAR 0xe0002000 Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000012, MEM_AP_TAR 0xe0002000 Warn : Block read error address 0xe0002000, count 0x1 Info : k40.cpu: hardware has 0 breakpoints, 4 watchpoints Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000042, MEM_AP_TAR 0xe000edf0 Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000042, MEM_AP_TAR 0xe000edf0 Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000042, MEM_AP_TAR 0xe000edf0 Error: JTAG-DP STICKY ERROR Error: MEM_AP_CSW 0x23000002, MEM_AP_TAR 0xe000edf0 Error: JTAG-DP STICKY ERROR [repeating] (On the K60, I get a different error: Error: jlink_usb_message failed with result=255) Error: jlink_tap_execute, wrong result -107 (expected 1) But I think I can ignore this for now, because this board does not have an onboard J-Link like the KwikStik, so I need to use a different J-Link hardware there.) Can anyone help me to get the KwikStik running? Is it right that I need my own config files? Regards, K. Dohmann === board/kinetis_kwikstik.cfg === source [find target/k40.cfg] === EOF === === target/k40.cfg === # script for k40 # based on script for stm32 if { [info exists CHIPNAME] } { set _CHIPNAME $CHIPNAME } else { set _CHIPNAME k40 } if { [info exists ENDIAN] } { set _ENDIAN $ENDIAN } else { set _ENDIAN little } # Work-area is a space in RAM used for flash programming # By default use 16kB if { [info exists WORKAREASIZE] } { set _WORKAREASIZE $WORKAREASIZE } else { set _WORKAREASIZE 0x4000 } # JTAG speed should be <= F_CPU/6. F_CPU after reset is 8MHz, so use F_JTAG = 1MHz #jtag_khz 1000 jtag_khz 1000 #jtag_nsrst_delay 100 #jtag_ntrst_delay 100 #jtag scan chain if { [info exists CPUTAPID ] } { set _CPUTAPID $CPUTAPID } else { # See STM Document RM0008 # Section 26.6.3 set _CPUTAPID 0x4ba00477 } jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID if { [info exists BSTAPID ] } { # FIXME this never gets used to override defaults... set _BSTAPID $BSTAPID } else { set _BSTAPID 0x000000ff } ##jtag newtap $_CHIPNAME bs -irlen 5 -expected-id $_BSTAPID #jtag newtap $_CHIPNAME bs -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_BSTAPID set _TARGETNAME $_CHIPNAME.cpu target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNAME $_TARGETNAME configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0 #set _FLASHNAME $_CHIPNAME.flash #flash bank $_FLASHNAME stm32x 0 0 0 0 $_TARGETNAME # For more information about the configuration files, take a look at: # openocd.texi === EOF === _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
