2 # Target configuration for the Silicon Labs EM357 chips
6 # em357 family supports JTAG and SWD transports
8 source [find target/swj-dp.tcl]
10 if { [info exists CHIPNAME] } {
11 set _CHIPNAME $CHIPNAME
16 # Work-area is a space in RAM used for flash programming
18 if { [info exists WORKAREASIZE] } {
19 set _WORKAREASIZE $WORKAREASIZE
21 set _WORKAREASIZE 0x1000
24 if { [info exists CPUTAPID] } {
25 set _CPUTAPID $CPUTAPID
28 set _CPUTAPID 0x3ba00477
30 set _CPUTAPID 0x1ba00477
34 if { [info exists BSTAPID] } {
37 set _BSTAPID 0x069a962b
40 if { [info exists CHIPNAME] } {
41 set _CHIPNAME $CHIPNAME
46 if { [info exists FLASHSIZE] } {
47 set _FLASHSIZE $FLASHSIZE
49 set _FLASHSIZE 0x30000
52 swj_newdap $_CHIPNAME cpu -irlen 4 -expected-id $_CPUTAPID
53 dap create $_CHIPNAME.dap -chain-position $_CHIPNAME.cpu
55 swj_newdap $_CHIPNAME bs -irlen 4 -expected-id $_BSTAPID -ircapture 0xe -irmask 0xf
58 set _TARGETNAME $_CHIPNAME.cpu
59 target create $_TARGETNAME cortex_m -endian little -dap $_CHIPNAME.dap
61 $_TARGETNAME configure -work-area-phys 0x20000000 -work-area-size $_WORKAREASIZE -work-area-backup 0
63 set _FLASHNAME $_CHIPNAME.flash
64 flash bank $_FLASHNAME em357 0x08000000 $_FLASHSIZE 0 0 $_TARGETNAME
67 # according to errata, we need to use vectreset rather than sysresetreq to avoid lockup
68 # There is a bug in the chip, which means that when using external debuggers the chip
69 # may lock up in certain CPU clock modes. Affected modes are operating the CPU at
70 # 24MHz derived from the 24MHz crystal, or 12MHz derived from the high frequency RC
71 # oscillator. If an external debugger tool asserts SYSRESETREQ, the chip will lock up and
72 # require a pin reset or power cycle.
74 # for details, refer to:
75 # http://www.silabs.com/Support%20Documents/TechnicalDocs/EM35x-Errata.pdf
76 cortex_m reset_config vectreset