• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 2529 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Getting started with CCS v5 and Beagleboard xM

rich cagley
Intellectual 290 points
Other Parts Discussed in Thread: DM3730

I've started to play around with CCS  Version: 5.1.0.06000. I have an XDS100v2 JTAG adapter.

Does anyone have any advice on how to get started for either the C64x+ or the Cortex A8 processors on the board. I've tried to make hello world projects with target configurations for either part with no success. It seems to be a big fan of throwing errors like this when I try to debug. I have the Beagleboard xM powered and the SD card removed. I must be doing something really obviously wrong. I did notice this version of CCS doesn't support the DM3730 so I told it the target is an DM3603 for what it's worth.

 

Error connecting to the target:

(Error -1178 @ 0x6D)

Device functional clock appears to be off. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).

(Release 5.0.429.0)

 

 

  • TI__Guru**** 171104 points

    Rich,

    Can you check the CCSv5 Getting Started Guide? It contains a step-by-step procedure on how to create a project, build and debug your code in CCSv5.

    In the procedure to create your target configuration you should select OMAP3630 (DM3730's sister device) and add a script (GEL file) to properly initialize the Beagleboard xM. I am not sure if there is a specific one for this board, but you can try to use the DM3730 EVM GEL file downloadable from the OMAP and Sitara CCS support page. The Getting Started Guide above has a page that talks about how to add these files to a target configuration.

    Also, during the project creation you will need a linker command file - one for DM3730 is available at this page.

    To debug the DSP core you will have to release it from reset from the Cortex core - details are also shown in the section Connecting to Slave Cores of SoC devices of the Getting Started Guide above.

    The connection issues to ARM cores sometimes are solved by setting the emulator to use Adaptive clocking. Check the short clip Changing the Target Configuration Properties of the Quick Tips page.

    Hope this helps,

    Rafael