On Dec 18, 2008, at 6:47 AM, Øyvind Harboe wrote:
U-boot has a lot of configuration files for BDI: http://www.denx.de/wiki/view/DULG/WhereCanIFindBDI2000ConfigurationFiles ftp://ftp.denx.de/pub/BDI2000/I would assume that these can be converted to OpenOCD speak without running afoul any licensing issues. The document where the links are found is GPL....-- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
Having looked at this for the beagleboard, converting a BDI config file to our target infrastructure isn't all that easy. I have a few ideas of how to rearrange the ARM targets so the actual target is a much smaller amount of code that is similar to what the BDI config files are doing. I'm still reading up on the ADIv5, but I think we can restructure the target code in terms of the address maps that are exposed (APB, AHB) and have all of the ADIv5 targets share a common code base otherwise.
I want to investigate this _after_ 1.0. -- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
