3e6f9e8d1e
The semantics of "-work-area-virt 0" (or phys) changed with the patch to require specifying physical or virtrual work area addresses. Specifying zero was previously a NOP. Now it means that address zero is valid. This patch addresses three related issues: - MMU-less processors should never specify work-area-virt; remove those specifications. Such processors include ARM7TDMI, Cortex-M3, and ARM966. - MMU-equipped processors *can* specify work-area-virt... but zero won't be appropriate, except in mischievous contexts (which hide null pointer exceptions). Remove those specs from those processors too. If any of those mappings is valid, someone will need to submit a patch adding it ... along with a comment saying what OS provides the mapping, and in which context. Example, say "works with Linux 2.6.30+, in kernel mode". (Note that ARM Linux doesn't map kernel memory to zero ...) - Clarify docs on that "-virt" and other work area stuff. Seems to me work-area-virt is quite problematic; not every operating system provides such static mappings; if they do, they're not in every MMU context... Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
50 lines
1.5 KiB
INI
50 lines
1.5 KiB
INI
# Atmel AT91rm9200
|
|
# http://atmel.com/products/at91/
|
|
|
|
reset_config trst_and_srst
|
|
|
|
if { [info exists CHIPNAME] } {
|
|
set _CHIPNAME $CHIPNAME
|
|
} else {
|
|
set _CHIPNAME at91rm9200
|
|
}
|
|
|
|
if { [info exists ENDIAN] } {
|
|
set _ENDIAN $ENDIAN
|
|
} else {
|
|
set _ENDIAN little
|
|
}
|
|
|
|
if { [info exists CPUTAPID ] } {
|
|
set _CPUTAPID $CPUTAPID
|
|
} else {
|
|
set _CPUTAPID 0x05b0203f
|
|
}
|
|
|
|
# Never allow the following!
|
|
if { $_CPUTAPID == 0x15b0203f } {
|
|
echo "-------------------------------------------------------"
|
|
echo "- ERROR: -"
|
|
echo "- ERROR: TapID 0x15b0203f is wrong for at91rm9200 -"
|
|
echo "- ERROR: The chip/board has a JTAG select pin/jumper -"
|
|
echo "- ERROR: -"
|
|
echo "- ERROR: In one position (0x05b0203f) it selects the -"
|
|
echo "- ERROR: ARM CPU, in the other position (0x1b0203f) -"
|
|
echo "- ERROR: it selects boundry-scan not the ARM -"
|
|
echo "- ERROR: -"
|
|
echo "-------------------------------------------------------"
|
|
}
|
|
|
|
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID
|
|
|
|
# Create the GDB Target.
|
|
set _TARGETNAME $_CHIPNAME.cpu
|
|
target create $_TARGETNAME arm920t -endian $_ENDIAN -chain-position $_TARGETNAME
|
|
|
|
# AT91RM9200 has a 16K block of sram @ 0x0020.0000
|
|
$_TARGETNAME configure -work-area-phys 0x00200000 \
|
|
-work-area-size 0x4000 -work-area-backup 1
|
|
|
|
# This chip has a DCC ... use it
|
|
arm7_9 dcc_downloads enable
|