Jun 20, 2009 8:53 PM
Using Symphony Studio to debug on-target?
-
Like (0)
Is it possible to use Symphony Studio (Eclipse) to debug DSP code running on target? I was hoping to find something more efficient than ouputing to the read-from-DSP variables.
I couldn't find anything in the manuals about this. I did see that there's a JTAG tap on the DSP core. How are other people debugging? Using the simulator? Any tips here would be appreciated.
Hi ToneCore users,
Yes it is possible to use the Symphony Studio Debugging environment.
There is a GNU Debugger with the Compiler that is really not useful on the DSP56364 due to too small memory footprint.
Also there is support for the Macraigor Wiggler to the JTAG interface on the DSP. I am not sure if the connector is on the ToneCore board or not.
But it is possible to interface to the OnCE interface on the Chip with a Wiggler and tools. Domain Technologies also builds a really great tool but is not cheap.
The Debug port on the SoundBite board could also be used if you are clever enough to build a small proto board.
Are any of you Hackers interested in that Debugger interface I would be happy to put it up on a site for you to get access to.
regards,
RVHA50
Yes, can you describe this debug port? I didn't find reference to it in the hardware guide. I assume it's something we can write words to and could wire up to a logic analyzer? That could be handy.
The DSP56364 has a JTAG-OnCE port that can be used to connect to the Suite56 DSP tools or Symphony Studio.
I am not sure that the ToneCore pedal has this port brought out to a connector, but it is in the documentation on the DSP56364 Data Sheet.
All Freescale DSP device have this port for low-level code debugging.
Macraigor & Domain Technologies are suppliers of this interface tool and what many DSP engineers use with Freescale and Altium Tools for product development.
One may also use the DSP simulator to debug the code as it is an accurate reference of the DSP design. Many DSP code developers also use this approach when Hardware platforms do not have a Debug port pinned out.
I have attached material relevant to your question and hope that it answers your questions. For another approach to Code debugging, you could buy a Freescale DoundBite board and do some work on that platorm as it is about the same price as the Wiggler approx. $150 for SoundBite board.
regards,
RVHA50
Per the TCDDK schematic, the DSP JTAG signals are not connected to anything. It may be possible to solder some leads onto the relevant pins if someone were sufficiently motivated.
It has just been a while that this topic came up. To solve the issue "DSP code size limitations" I added a Once Interface to the ToneCore Programmer Dock. On page 8 in the TCDDK Hardware Guide you can see a photo of the opened ToneCore Programmer Dock. Above the DSP you see a six pin connector that is not populated in series production. The 9V battery cable is glued here. If you remove this cautiously you can use the pads to add an OnCE interface cable.I checked the signals to the DSP (see page 30 in the TCDDK Hardware Guide). The signals are from left to right:
1.) Ground
2.) /Reset
3.) TDI
4.) TMS
5.) TCK
6.) TDO
I attached a ribbon cable to the pads to connect the cable to the Debug interface (see the document DSPCOMMPARALLELUM.pdf and the pictures taken from the home brewn connection). You may use Symphony Studio as well as Suite56 for debugging the target now, see:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=CW-SUITE56
Best regards
Christian
I've youst forgot one detail: The OnCE debug interface needs +3.3V power supply. I took this from a capacitor next to the DSP. See the attached picture for detail view.
After using this OnCE interface to solve my problem I glued the cable to use it permanetly and filed a slot into the housing to close it. I guess I've lost warranty now ;-).
Best regards
Christian
Debugging the pedal, eh?
Be aware that reverse engineering anyone else's code is an international criminal copyright violation.
There's no code on the pedal from anyone else than me. I'm just following Angelo's recommendation to locate a bug in my own program. All other codes I can load into the ToneCore pedal are available as source code. So why worry?
Best regards
Christian
Stay in the mix and in the know.
Latest offers, special deals and insider updates.