On Thu, May 10, 2012 at 7:18 PM, Andreas Fritiofson
<[email protected]> wrote:
> I wish I could find a configuration that didn't work.
>
> Regarding the segfault, I think there's a bug somewhere in the
> handling of signals that are requested to be tri-stated even though
> they are specified as push-pull only. You can try to make sure that
> reset_config includes srst_push_pull, because srst isn't open drain in
> your eval board. I'll investigate more later.
Great! This seems to work fine, tested under Ubuntu 12.04. Thanks
for the insight.
In terms of flash write performance, mpsse version is only about
10% faster than the git version. But the mpsse version seems to dump
much faster.
Also I can push adapter_khz to 6000 in the mpsse version (even
though it does not help the flash write speed) but the vanilla
git version is only up to 3000.
Vanilla git (latest)
mcuee@GX620Ubuntu:~/Desktop/build/openocd/lm3s1968$ openocd -f
board/ek-lm3s1968.cfg
Open On-Chip Debugger 0.6.0-dev-00549-g47cf0aa (2012-05-10-21:06)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
500 kHz
Info : clock speed 500 kHz
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
500 kHz
cortex_m3 reset_config sysresetreq
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00001330 msp: 0x20000100
3000 kHz (note: I give adapter_khz 4000 command)
dumped 262144 bytes in 6.511652s (39.314 KiB/s)
verified 262144 bytes in 2.455823s (104.242 KiB/s)
auto erase enabled
wrote 262144 bytes from file demo3.bin in 3.893619s (65.749 KiB/s)
Info : dropped 'telnet' connection
mpsse version:
mcuee@GX620Ubuntu:~/Desktop/build/openocd/lm3s1968$ ~/bin/bin/openocd
-f board/ek-lm3s1968_mpsse.cfg
Open On-Chip Debugger 0.6.0-dev-00448-g39810bc-dirty (2012-05-10-21:03)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.sourceforge.net/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
500 kHz
none separate
Info : clock speed 500 kHz
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : accepting 'telnet' connection from 4444
500 kHz
cortex_m3 reset_config sysresetreq
Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg:
0x23b, part: 0xba00, ver: 0x3)
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00001330 msp: 0x20000100
flash 'stellaris' found at 0x00000000
3000 kHz
dumped 262144 bytes in 2.345896s (109.127 KiB/s)
verified 262144 bytes in 2.357886s (108.572 KiB/s)
auto erase enabled
wrote 262144 bytes from file demo2.bin in 3.446741s (74.273 KiB/s)
Info : dropped 'telnet' connection
Working config file for the mpsse version, using your modified luminary.cfg
and modified board file.
mcuee@GX620Ubuntu:~/bin/share/openocd/scripts$ cat interface/ftdi/luminary.cfg
#
# Luminary Micro Stellaris Evaluation Kits
#
# http://www.luminarymicro.com/products/evaluation_kits.html
#
# There are a number of evaluation kits for Stellaris Cortex-M3 chips.
# Currently they all bundle ftdi based debug support. When that is
# used (instead of an external adapter), use this config file in one
# of these two modes:
#
# - Eval board debug ... debug of the Stellaris chip via port A.
#
# - Other board debug ... same thing, but the board acts as a debug
# adapter for another board (using a standard ARM JTAG connector).
# The Stellaris chip stays in reset.
#
# Those support both JTAG and SWD. SWD is an ARM-only two-wire debug
# protocol; in 2009, OpenOCD does not support SWD.
#
# Port B of the ftdi chip is normally used as a serial link to the
# Stellaris chip. On most boards (but not older LM3S811 eval boards),
# when SWD is used Port B may instead be used to read low-bandwidth
# "SWO trace" data, including so-called "printf style" output from
# firmware via the ITM module as well as profile data.
#
interface ftdi
ftdi_device_desc "Stellaris Evaluation Board"
ftdi_vid_pid 0x0403 0xbcd9
ftdi_layout_init 0x0088 0x00eb
ftdi_layout_signal nSRST -data 0x0020
mcuee@GX620Ubuntu:~/bin/share/openocd/scripts$ cat board/ek-lm3s1968_mpsse.cfg
#
# TI/Luminary Stellaris LM3S1968 Evaluation Kits
#
# http://www.luminarymicro.com/products/lm3s1968_evaluation_kits.html
# NOTE: to use J-Link instead of the on-board interface,
# you may also need to reduce adapter_khz to be about 1200.
# source [find interface/jlink.cfg]
# include the FT2232 interface config for on-board JTAG interface
# NOTE: using the on-board FT2232 JTAG/SWD/SWO interface is optional!
# so is using in JTAG mode, as done here.
source [find interface/ftdi/luminary.cfg]
# include the target config
set WORKAREASIZE 0x2000
set CHIPNAME lm3s1968
source [find target/stellaris.cfg]
reset_config srst_push_pull
--
Xiaofan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
