From 3e6f9e8d1e65c4da505ff78481d54a115520d3d1 Mon Sep 17 00:00:00 2001 From: David Brownell Date: Sun, 8 Nov 2009 08:52:40 -0800 Subject: target.cfg: remove "-work-area-virt 0" 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 --- tcl/target/str750.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tcl/target/str750.cfg') diff --git a/tcl/target/str750.cfg b/tcl/target/str750.cfg index 74f26642..22d87f87 100644 --- a/tcl/target/str750.cfg +++ b/tcl/target/str750.cfg @@ -43,7 +43,7 @@ $_TARGETNAME configure -event gdb-flash-erase-start { flash protect 1 0 1 off } -$_TARGETNAME configure -work-area-virt 0 -work-area-phys 0x40000000 -work-area-size 0x4000 -work-area-backup 0 +$_TARGETNAME configure -work-area-phys 0x40000000 -work-area-size 0x4000 -work-area-backup 0 #flash bank flash bank str7x 0x20000000 0x00040000 0 0 0 STR75x -- cgit v1.2.3