Gary Carlson wrote:
> I can now see that I left off a critical detail! :)
>
> Yes, you most certainly can use a TCL set command to accomplish this. The
> only issue is you have to spend an inordinate amount of time entering the
> values by hand. That in itself is another source for errors -- especially
> on processors with large configuration register sets.
>
No - you should be able to - by design - in our OpenOCD.CFG file do this:
(for your chip, this example - atmel at91 series)
source [find chip/atmel/at91/at91sam7x256.tcl]
[See note below.]
One person does this work, and adds it to OpenOCD... an we all get the
benefit.
I did *QUITE* a lot for the at91sam7 chips a when we first introduced
TCL to openocd.
I also did some more for the STM32 chip.
Would you care to create one for *YOUR* chip?
And submit it for inclusion in OpenOCD?
-Duane.
NOTE:
=====
Sadly, that example is "crusty" a while ago the TCL code needs a quick
patch, which I will take care of shortly.
Meanwhile... in that file, change:
FROM: [find tcl/FILENAME.tcl]
TO: [find FILENAME.tcl] [remove the TCL/ prefix]
TOTAL: 8 locations.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
