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.

TMS320C6678: StairstepEthernet_6678 project

Part Number: TMS320C6678
Other Parts Discussed in Thread: SYSBIOS

Hi,

CCSV9.3

Customer built stairstepEthernet_6678 from processors.wiki.ti.com/index.php/TMS320C6678L_Build_Configuration successfully. But the project get stuck when running and prompts:

[C66xx_0]
System Analyzer Tutorial 4C
QMSS successfully initialized
CPPI successfully initialized
PA successfully initialized
EVM in StaticIP mode at 192.168.2.100
Set IP address of PC to 192.168.2.101
PASS successfully initialized
Ethernet subsystem successfully initialized
Ethernet eventId : 48 and vectId (Interrupt) : 7
Registration of the EMAC Successful, waiting for link up ..
Network Added: If-1:192.168.2.100
ti.uia.runtime.ServiceMgr: line 88: assertion failure: A_invalidProcessCallbackFxn: Callback cannot be NULL
xdc.runtime.Error.raise: terminating execution
or
CPPI successfully initialized
PA successfully initialized
EVM in StaticIP mode at 192.168.2.100
Set IP address of PC to 192.168.2.101
PASS successfully initialized
Ethernet subsystem successfully initialized
Ethernet eventId : 48 and vectId (Interrupt) : 7
Timeout waiting for reply from PA to Pa_addMac command
ti.sysbios.heaps.HeapMem: line 446: assertion failure: A_invalidFree: Invalid free
xdc.runtime.Error.raise: terminating execution
There is a detailed solution in below link. But where is System Analyzer Welcome option in ccsv9? and how to solve the error above?
  • Hi,

    What is this StairstepEthernet_6678 project? It doesn't like anything in the Processor SDK RTOS C6678 package. Inside the TI package, there is PA examples that can be built:  

    Can customer make sure this example can be built and run successively? Then, what is the difference between this StairstepEthernet_6678 and TI example? 

    For the run time error, was that caused by a different build environment: like CCS version, SYSBIOS and XDC tool? Did that work before? I read through the  

    and it is about system analyzer. I don't see how it is related to the PA failure. In CCS 9, tools---------->System Analyzer, if this is what you are looking for. This is we typically collected CPU load, task, swi, hwi switch, etc. 

    So I still suggest you refer to the PA example inside PRSDK RTOS C6678, and compare the difference with your example. Maybe some changes in the .cfg caused it. In the application, if the API call sequences and parameters are the same, it should work.

    Regards, Eric