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.

Problems Running NDK Client example on TMS320C6678

Other Parts Discussed in Thread: SYSBIOS

I have the TMDSEVM6678LE, and have configured the DIP switches for a static IP. I can access the HUA demo that shipped with the dev kit.

I imported the CCS Eclipse Project called "client_evmc6678l", and it builds OK. When I run it on the 6678 dev kit, I get this output:

[C66xx_0] QMSS successfully initialized
[C66xx_0] CPPI successfully initialized
[C66xx_0] PA successfully initialized
[C66xx_0]
[C66xx_0] TCP/IP Stack Example Client
[C66xx_0] PASS successfully initialized
[C66xx_0] Ethernet subsystem successfully initialized
[C66xx_0] Ethernet eventId : 48 and vectId (Interrupt) : 7
[C66xx_0] Timeout waiting for reply from PA to Pa_addMac command
[C66xx_0] ti.sysbios.heaps.HeapMem: line 354: assertion failure: A_invalidFree: Invalid free
[C66xx_0] xdc.runtime.Error.raise: terminating execution

I have looked at the code, and stepped through execution, but I can't figure out what is happening with the "Timeout waiting for reply from PA to Pa_addMac command".

Here are the versions of everything involved:

CCS: 5.2.1.00018

MCSDK: 2.1.2.6

PDK C6678: 1.1.2.6

NDK: 2.21.1.38

 

Does anyone have any idea what I should be looking at to make this work?

Mike van Lammeren

  • Hi Mike van Lammeren,

    Can you please try:

    1) System reset (it's on the drop down menu, next to the Restart button)

    2) Re-run the global default script from the GEL file

    3) Reload client_evmc6678l.out and run the EVM

    Let me know if this helps.

    -Ivan

  • Hi Ivan,

    Yes, that worked, but I have no idea what I just did! I can connect to the 6678 over Telnet now.

    Step 2 gave this output:

    C66xx_0: GEL: Warning loading file 'C:\ti\mcsdk_2_01_02_06\examples\ndk\client\evmc6678l\Debug\configPkg\package\cfg\client_xe66.gel', line 2: the function 'GEL_ProjectLoad' is not supported.
    C66xx_0: GEL: Warning loading file 'C:\ti\mcsdk_2_01_02_06\examples\ndk\client\evmc6678l\Debug\configPkg\package\cfg\client_xe66.gel', line 3: the function 'GEL_ProjectLoad' is not supported.
    C66xx_0: GEL: Warning loading file 'C:\ti\mcsdk_2_01_02_06\examples\ndk\client\evmc6678l\Debug\configPkg\package\cfg\client_xe66.gel', line 4: the function 'GEL_ProjectSetActive' is not supported.
    C66xx_0: GEL: Warning loading file 'C:\ti\mcsdk_2_01_02_06\examples\ndk\client\evmc6678l\Debug\configPkg\package\cfg\client_xe66.gel', line 7: the function 'GEL_ProjectClose' is not supported.
    C66xx_0: GEL: Warning loading file 'C:\ti\mcsdk_2_01_02_06\examples\ndk\client\evmc6678l\Debug\configPkg\package\cfg\client_xe66.gel', line 8: the function 'GEL_ProjectClose' is not supported.

    How has this fixed my problem?

  • Hi Mike,

    For Step 2, I was referring to the platform's GEL file. The default path should be C:\ti\ccsv5\ccs_base\emulation\boards\evmc6678l\gel\evmc6678l.gel

    You probably have already loaded this file, or configured to load it on your Target Configuration .ccxml file. The global default setup function is here:

    The main fix for your problem is the system reset. The demos and examples we have were designed to have a system reset between runs, so as to reset the peripherals used. Without this reset, your Packet Accelerator and Multicore Navigator were configured by the previous run and the error comes in when trying to re-configure them.

    If you are interested, I have posted a way to bypass the system reset here http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/247150/921455.aspx#921455

    -Ivan

  • Hi Iwan,

    Thank you very much for your reply. I really appreciate the explanation. I will check out your previous post on bypassing the system reset.