> Presently, I would like to hear about the perceived status > of Cortex-A8,
It gets through OMAP3 bringup. The ROM table scanning embeds various assumptions; see the comments in the ARM ADI_V5.c file. I'm not sure whether it's good to assume DAP 0 is used, as one of the examples, of which MEM-AP to use. The MX51 is a bit different than OMAP. I don't know about other chips using A8 cores... or, A9. > as one of my initial goals will be to "validate" that > support. If you > are using OpenOCD on a Cortex-A8 platform, what problems do > you face? > What features still need work? And contributors of this > support: are > there any horrible blemishes remaining in this code? I've tried to leave comments in the code re any open issues I observed. Historically, the A8 code evolved from the M3 code, at least for the ROM table scanning (not debug). The v7a (Cortex-A) debug support is ISTR not all there, but it's not too bad. ARM did good things by having v6 and v7a use the same model (DPM), so what OpenOCD needs to do is jut fill in various missing bits. Again, read code comments. Also, cross-check against the ARM-v7AR TRM. > ________________________________________ > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
