On Thu, Jan 24, 2013 at 10:21:15AM +0100, Lino - Andrea wrote:
> On Wed, Jan 23, 2013 at 03:14:59PM +0100, Øyvind Harboe wrote:
> >I would like to work on e300/e500 cores, but the debug interface
> >seems to be
> >non-documented for practical purposes.
> 
> I am interested to work on ST SPC560B and SPC560P devices. Assuming
> that I have all the documentation, you think it's possible to extend
> the OpenOCD compatibility?

Yes.

> Mainly, where to start?

Look at the ARM and MIPS targets - MIPS is newer but a bit less mature than
ARM.

However, first work on getting the complete documentation for the debug
access: that might or might not be a problem.

when creating the new target, keep in mind that not all PowerPC chips are
the same: there are different cores, and SOCs using different debug
interfaces, so the structure should allow for these variations, even if the
code only handles one such variant.

> The idea is to use a debugger based on the FT2232 chip with a new
> development board based on PPC device. Moreover, I'm looking for a
> collaboration, so I am ready to provide some board with this device.

The chip uses JTAG, so any JTAG adapter supported by OpenOCD *should* work. 
What is interesting is that they claim NEXUS compatibility for the debug
interface, so there might be a chance to get documentation (the Freescale
devices I work with use COP, and the documentation is quite closed).

I work on MPC8314 and P1010 (Freescale), so I am afraid I won't be able to
help much.

cu
Michael

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to