tcl/target/ti_k3: Remove args from m3 and m4_up
args serve no purpose, so drop them. Signed-off-by: Nishanth Menon <nm@ti.com> Change-Id: I136394307016453d576cf524b0f02227ba26ef8a Reviewed-on: https://review.openocd.org/c/openocd/+/6626 Tested-by: jenkins Reviewed-by: Antonio Borneo <borneo.antonio@gmail.com>
This commit is contained in:
parent
4906176c77
commit
2b17a12884
|
@ -152,7 +152,7 @@ cti create $_CTINAME.m3 -dap $_CHIPNAME.dap -ap-num 7 -baseaddr [lindex $CM3_CTI
|
||||||
target create $_TARGETNAME.m3 cortex_m -dap $_CHIPNAME.dap -ap-num 7 -defer-examine
|
target create $_TARGETNAME.m3 cortex_m -dap $_CHIPNAME.dap -ap-num 7 -defer-examine
|
||||||
$_TARGETNAME.m3 configure -event reset-assert { }
|
$_TARGETNAME.m3 configure -event reset-assert { }
|
||||||
|
|
||||||
proc m3_up { args } {
|
proc m3_up {} {
|
||||||
# To access M3, we need to enable the JTAG access for the same.
|
# To access M3, we need to enable the JTAG access for the same.
|
||||||
# Ensure Power-AP unlocked
|
# Ensure Power-AP unlocked
|
||||||
$::_CHIPNAME.dap apreg 3 [lindex $::_m3_ap_unlock_offsets 0] 0x00190000
|
$::_CHIPNAME.dap apreg 3 [lindex $::_m3_ap_unlock_offsets 0] 0x00190000
|
||||||
|
@ -245,7 +245,7 @@ if { $_mcu_m4_cores != 0 } {
|
||||||
target create $_TARGETNAME.m4 cortex_m -dap $_CHIPNAME.dap -ap-num 8 -defer-examine
|
target create $_TARGETNAME.m4 cortex_m -dap $_CHIPNAME.dap -ap-num 8 -defer-examine
|
||||||
$_TARGETNAME.m4 configure -event reset-assert { }
|
$_TARGETNAME.m4 configure -event reset-assert { }
|
||||||
|
|
||||||
proc m4_up { args } {
|
proc m4_up {} {
|
||||||
# To access M4, we need to enable the JTAG access for the same.
|
# To access M4, we need to enable the JTAG access for the same.
|
||||||
# Ensure Power-AP unlocked
|
# Ensure Power-AP unlocked
|
||||||
$::_CHIPNAME.dap apreg 3 [lindex $::_m4_ap_unlock_offsets 0] 0x00190000
|
$::_CHIPNAME.dap apreg 3 [lindex $::_m4_ap_unlock_offsets 0] 0x00190000
|
||||||
|
|
Loading…
Reference in New Issue