On Thu, Jan 24, 2013 at 10:21 AM, Lino - Andrea <mfcir...@tin.it> 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?
> Mainly, where to start?
> 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.

Then you need to add new Target, name it PowerPC, you can start from
ARM or MIPS as reference.

Target is responsible for reading/writing target memory bus, access port, etc.

On top of your Target functions you can build perihperals access,
memory access, etc.

If you want to use FT2232 device, use new MPSSE interface driver in
OpenOCD, it already gives you the JTAG access.

Right now its a bit mixed, but looking on how ARM or MIPS is
implemented will be a good starting point.

If you have lots of spare boards I can take a look at one of them and
the documentation just for curiosity :-) However if you want to have
this implemented with a priority please consider hiring someone
developer from the group willing to do the job or assist you :-)

Best regards :-)
Tomek

-- 
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info

------------------------------------------------------------------------------
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