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.

How to Debug the C674x DSP in DM8168?

Other Parts Discussed in Thread: SYSBIOS

Hi,

  I managed to run a SYS/BIOS Hello example on C674x DSP in DM8168.  Having got an EVM8168 board, I download the GEL file from this site:

    http://support.spectrumdigital.com/boards/evm816x/revg

  Then, I search the wiki and find a post which seems plausible:

    http://processors.wiki.ti.com/index.php/Connecting_to_DSP_on_C6A8168,_DM8168,_DM8148

  By following this wiki, I tried to build an SYS/BIOS Hello Example via CCSv5.3 in Ubuntu 10.04 LTS.

1.Create a new project.

2.Compile project.(template hello)

3. Set the Target Configuration File (*.ccxml)

[TargetConfigurations]
Selected tools: XDS100v2 + DM8168
Launch selected Configration by right clicking the file and selecting "launch" item.

4.CortexA8 connect-target

5.Load GEL file
Load evm8168x.gel (spectrumdigital)

----- console ------
CortexA8: Output: PRCM for C674x is in Progress, Please wait.....
CortexA8: Output: C674x L2 RAM Accesses are PASSED
CortexA8: Output: User Can Connect to C674x
--------------------

6.Menu options Scripts -> TI816X CPU BRINGUPS, and select c674x

7.C674X_0 connect-target
8.Run-Load Program
Load program hello.out

  I thought there would be a "hello world!" info in the console window just like what was happening in the videoclip. (http://software-dl.ti.com/trainingTTO/trainingTTO_public_sw/bios_1day_videos/LAB_2A_Intro_to_CCS/LAB_2A_Intro_to_CCS.mp4)  However, once the program was loaded, it never halted at the entry of the main.  Instead, the program never stoped and printed nothing to the console.  Anyway, it seems that the program ran into a dead loop! 

  I don't know how to slove this problem.  As far as I know, the debug session would be pause automatically when the *.out is loaded into the DSP successfully.  It allows debugger to start the program manually by cliking the "resume" button.  By the contrast, I never got such a chance to push the button.  Even if I set some break points in the main, the program runs as well.

  How can I solve this problem?  Could you give me a hand?  Shall I find some link file which indicates the memmap of the system?

  I am sincerely looking forward to your reply.

Naroah

Aug/06/2013

The Debug session runs automatically and never stops.  Besides, there is no "Hello World" printed in the console.

  • Hello,

    Can you attach your example out file? I'd like to analyze it.

    Thanks

    ki

  • Hi Ki,

      Thank you for your reply.  Actually, I have this problem sloved.

      To deal with this problem, referring to the wiki and forum, I have to modify the GEL file which I download from Spectrum(evm816x.gel).  I added a hotmenu function named "enableTimers" to enable the dmtimer manually after the DSP was brought up by Cortex_A8.  As a result, I could get the debugging session work.

      Here is my hello.out which is built as an ELF (not COFF).

      Besides, although it seems no necessity to declare the inFreq value of "dmtimer" explicitly, I also added something in the *.cfg file:

    var Timer = xdc.useModule('ti.sysbios.timers.dmtimer.Timer' );
    //Timer.checkFrequency = false;
    Timer.intFreq.hi = 0;
    Timer.intFreq.lo = 32768;

      According to Scott's words:  http://e2e.ti.com/support/embedded/bios/f/355/p/267580/936372.aspx

      and Karl's words http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/250375.aspx

      There seems to be some bugs in the SYS/BIOS packages, since we can get a workaround only by changing a third-party's GEL.  I don't regard it as a good idea.  Have these bugs been sloved?  I am looking forward some newly released packages which enables me to config the dmtimer simply by modifing the *.cfg file.

    Naroah

    Aug/08/2013

    7041.Hello.out.txt

  • Good to hear that you have found a solution. Thank you for the update

    Regarding the bugs in the SYS/BIOS packages, it is best to inquire about them in the BIOS forums. They can best answer any questions regarding them

    ki