1 # TI/Luminary Stellaris LM3S chip family
3 # Luminary chips support both JTAG and SWD transports.
4 # Adapt based on what transport is active.
5 source [find target/swj-dp.tcl]
7 # For now we ignore the SPI and UART options, which
8 # are usable only for ISP style initial flash programming.
10 if { [info exists CHIPNAME] } {
11 set _CHIPNAME $CHIPNAME
16 # CPU TAP ID 0x1ba00477 for early Sandstorm parts
17 # CPU TAP ID 0x2ba00477 for later SandStorm parts, e.g. lm3s811 Rev C2
18 # CPU TAP ID 0x3ba00477 for Cortex-M3 r1p2 (on Fury, DustDevil)
19 # CPU TAP ID 0x4ba00477 for Cortex-M3 r2p0 (on Tempest)
20 # ... we'll ignore the JTAG version field, rather than list every
21 # chip revision that turns up.
22 if { [info exists CPUTAPID ] } {
23 set _CPUTAPID $CPUTAPID
25 set _CPUTAPID 0x0ba00477
28 # SWD DAP, and JTAG TAP, take same params for now;
29 # ... even though SWD ignores all except TAPID, and
30 # JTAG shouldn't need anything more then irlen. (and TAPID).
31 swj_newdap $_CHIPNAME cpu -irlen 4 -irmask 0xf \
32 -expected-id $_CPUTAPID -ignore-version
34 if { [info exists WORKAREASIZE ] } {
35 set _WORKAREASIZE $WORKAREASIZE
37 # default to 8K working area
38 set _WORKAREASIZE 0x2000
41 jtag newtap $_CHIPNAME cpu -irlen 4 -irmask 0xf \
42 -expected-id $_CPUTAPID -ignore-version
44 set _TARGETNAME $_CHIPNAME.cpu
45 target create $_TARGETNAME cortex_m3 -chain-position $_CHIPNAME.cpu
47 # 8K working area at base of ram, not backed up
49 # NOTE: you may need or want to reconfigure the work area;
50 # some parts have just 6K, and you may want to use other
51 # addresses (at end of mem not beginning) or back it up.
52 $_TARGETNAME configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE
54 # JTAG speed ... slow enough to work with a 12 MHz RC oscillator;
55 # LM3S parts don't support RTCK
57 # NOTE: this may be increased by a reset-init handler, after it
58 # configures and enables the PLL. Or you might need to decrease
59 # this, if you're using a slower clock.
62 source [find mem_helper.tcl]
64 $_TARGETNAME configure -event reset-start {
68 # When nRST is asserted on most Stellaris devices, it clears some of
69 # the debug state. The ARMv7M and Cortex-M3 TRMs say that's wrong;
70 # and OpenOCD depends on those TRMs. So we won't use SRST on those
71 # chips. (Only power-on reset should affect debug state, beyond a
72 # few specified bits; not the chip's nRST input, wired to SRST.)
74 # REVISIT current errata specs don't seem to cover this issue.
75 # Do we have more details than this email?
76 # https://lists.berlios.de/pipermail
77 # /openocd-development/2008-August/003065.html
80 set device_class [expr (([mrw 0x400fe000] >> 16) & 0xff)]
81 if {$device_class == 0 || $device_class == 1 || $device_class == 3} {
82 # Sandstorm, Fury and DustDevil are able to use NVIC SYSRESETREQ
83 cortex_m3 reset_config sysresetreq
85 # Tempest and newer default to using NVIC VECTRESET
86 # this does mean a reset-init event handler is required to reset
88 cortex_m3 reset_config vectreset
92 # flash configuration ... autodetects sizes, autoprobed
93 flash bank $_CHIPNAME.flash stellaris 0 0 0 0 $_TARGETNAME