On 11/09/2010 06:37 PM, David Brownell wrote:
--- On Tue, 11/9/10, 韦东山<ds...@ustc.edu> wrote:
From: 韦东山<ds...@ustc.edu>
Yes, it can't enable the Cortex core. I delete this line in
the cofigration file:
" jtag configure $_CHIPNAME.jrc -event setup "jtag
tapenable $_CHIPNAME.dap" "
and run "jtag tapenable omap3530.dap" in the telnet
windows, the output is the same:
And after you broke the configuration, you were for
some reason surprised that it didn't work????
I don't recall specifically what I did to bring
up a Beagle last time, "reset init" was about the
level of complexity required, though. A routine
operation to kick off the various events which
bring up the CPU via ICEPick and other ops.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
韦东山,
When I was setting up the beagleboard XM I was getting those sticky
messages also. I am not sure of their significance, but you can still
debug after seeing those. As David Said, you should just have to do a
reset which will indirectly run "omap3_dbginit" to debug the MPU (Cortex
A8).
"omap3_dbginit" is the function you need to call either direct, or
indirect (with reset). This enables invasive debugging and will allow
you to set breakpoints and halt the processor among other things.
If you would like to setup invasive debugging without resetting the
processor just run "omap3_dbginit omap3530.cpu".
One thing to note: Older revisions of the openocd tools did not have
"mww phys" in the dbginit for the omap3530 configuration scripts. If
you have an older revision you might want to check out the latest since
that has been fixed. The last line of "omap_dbginit" in omap3530.cfg
should read as follows:
$target mww phys 0x5401d030 0x00002000
There is another ARM processor in the device which is part of the IVA.
If you are trying to debug that you will need to modify the
configuration files. I am not sure what exactly you would need to do
offhand since I have not worked on debugging that processor.
-Karl
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
