GDB56300 Source - as documentation for DSP56725 once usage

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

GDB56300 Source - as documentation for DSP56725 once usage

Jump to solution
1,411 Views
mjd_bishop
Contributor II

I'm looking for guidance on the cookery required to implement debugging via once / JTAG - all the BSDL / JTAG logic pre-exists.  Specifically, for code examples for basic debugger functions : save / restore contaxt, peek/poke DSP registers/memory (I have read AN1839 / AN2074); eg GDB56300 source.

As context, I have DSP56301 boards which are happy to talk JTAG to an FTDI2232H on TCK/TMS/TDI/TDO and a back catalog of software I'm may re-host on a DSP56725.

https://openocd-devel.narkive.com/2LMHqcDx/opment-moin-my-dsp563-plans indicates that the source is GPL and releasable.

Martin

0 Kudos
Reply
1 Solution
703 Views
mjd_bishop
Contributor II

Hi @julie856batson  if you are not an AI bot, my thanks for your observations.

This thread can now be closed down, as I established some time ago that:

- the current OpenOCD sources contain the 56300 support files, so they are available - if somewhat opaque

- the best documentation of the JTAG / Once / DSP56300 interface is in the DSP56300FM, the family manual, Ch 10 & 11

And, I have successfully performed proof of concept experiments to test the JTAG / Once / 56300 data path.  A basic debug capability remains XFU.

Best Regards

Martin

View solution in original post

0 Kudos
Reply
3 Replies
718 Views
julie856batson
Contributor I

Hello @mjd_bishop,
For DSP56301 JTAG debugging via OnCE, use AN1839 and AN2074 as your base—they detail entering debug mode, saving pipeline state, and accessing memory via JTAG. FTDI2232H works well with MPSSE for JTAG emulation. For peek/poke and context save/restore, refer to GDB56300 source if available—though NXP doesn’t officially distribute it. You may find community forks on GitHub or contact posters from the OpenOCD thread you linked.

Best Regards,
Julie Batson

0 Kudos
Reply
704 Views
mjd_bishop
Contributor II

Hi @julie856batson  if you are not an AI bot, my thanks for your observations.

This thread can now be closed down, as I established some time ago that:

- the current OpenOCD sources contain the 56300 support files, so they are available - if somewhat opaque

- the best documentation of the JTAG / Once / DSP56300 interface is in the DSP56300FM, the family manual, Ch 10 & 11

And, I have successfully performed proof of concept experiments to test the JTAG / Once / 56300 data path.  A basic debug capability remains XFU.

Best Regards

Martin

0 Kudos
Reply
1,363 Views
Celeste_Liu
NXP Employee
NXP Employee

Hello @mjd_bishop ,

Thanks for your post.

Since the DSP56301 is a very old product, I'll try my best to find some useful documents for you.

The DSP56301ADM User’s Manual is attached.

You can also refer to dsp56k/README.md at main · jmamma/dsp56k · GitHub.

As for GDB56300 source,frankly speaking, TIC is not the proper channel to distribute source code to anyone, because we have neither the souce code of gdb56300 nor the right to distribute it or sign any agreement to protect NXP IP or copyright.

Or you can find some relevant information on GitHub or other forums. You can contact the posters to see if they can provide it.

Sorry for the inconvenience caused.

[Openocd-development] Moin / my DSP563 plans

Symphony Studio IDE支持DSP56321吗? - NXP Community

 

Best regards,

celeste

0 Kudos
Reply