The following patch removes the Comments Duane added in the s3c2440
about not trusting the given tapid. It enables the tapid again as I was able to
test it on given soc.
I believe the file should be renamed so samsung_s3c2440.cfg to match
other configurations but
As far as the linux kernel goes I think s3c and samsung are the same
and the term s3c is used in the platform code
the patch is agains r1237 (an other reason to have only openocd in the svn)
greetings
Index: src/target/target/s3c2440.cfg
===================================================================
--- src/target/target/s3c2440.cfg (revision 1237)
+++ src/target/target/s3c2440.cfg (working copy)
@@ -1,9 +1,7 @@
# Target configuration for the Samsung 2440 system on chip
-# Tested on a S3C2440 Evaluation board
+# Tested on a S3C2440 Evaluation board by keesj
# Processor : ARM920Tid(wb) rev 0 (v4l)
-# Info: JTAG device found: 0x0032409d (Manufacturer: 0x04e, Part: 0x0324, Version: 0x0)
-# [Duane Ellis 27/nov/2008: Above 0x0032409d appears to be copy/paste from other places]
-# [and I do not believe it to be accurate, hence the 0xffffffff below]
+# Info: JTAG tap: s3c2440.cpu tap/device found: 0x0032409d (Manufacturer: 0x04e, Part: 0x0324, Version: 0x0)
if { [info exists CHIPNAME] } {
set _CHIPNAME $CHIPNAME
@@ -22,7 +20,7 @@
set _CPUTAPID $CPUTAPID
} else {
# force an error till we get a good number
- set _CPUTAPID 0xFFFFFFFF
+ set _CPUTAPID 0x0032409d
}
#jtag scan chain
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
