CCS/TDA3XEVM: dcan caused startup failure

Hi,

did you had any other modifications in the cfg.mk?

Also are there any errors in the console log?

Regards,

Yordan

Hi,

Other modifications in the cfg.mk.

IPU1_0 / IPU1_1 / DSP1 set yes.
DSP2 / EVE1 set no.

The teraterm log is completely absent when the exception occurs
CCS console log is below:

Thanks in advance.

Hi,

Are you able to send few CAN messages successfully to TDA3x prior to failure?

Can you try putting breakpoint in 'Utils_dcanInt1Isr()' and when it is hit can you try to step through the code and see where exactly is failing? It is needed to pin-point the location of the failure.

Thanks & Regards,
Vivek Dhande.

Texas Instruments (India) Pvt Ltd

Hi,

I putting breakpoint in 'Utils_dcanInt1Isr()' and it is hit.
But none cause failing when step through the code.

Should I delay the initial of dcan?

Thanks in advance.

Hi,

Yes, you can try that and see if it helps.

Are you able to send a few CAN messages successfully to TDA3x prior to failure?

Thanks & Regards,
Vivek Dhande.

Texas Instruments (India) Pvt Ltd

Hi,

I can see the app log when delay the initial of dcan.

But there will be a high chance that the following error will occur.
[IPU1-1] 7.074330 s: Assertion @ Line: 407 in C:/PROCESSOR_SDK_VISION_03_04_00_00/vision_sdk/apps/src/rtos/modules/dcan/utils_dcan.c: status == 0 : failed !!!
[IPU1-1] 7.074544 s:
[IPU1-1] 7.074574 s: ### XDC ASSERT - ERROR CALLBACK START ###
[IPU1-1] 7.074635 s:
[IPU1-1] 7.074757 s: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details.
[IPU1-1] 7.074849 s:
[IPU1-1] 7.074910 s: ### XDC ASSERT - ERROR CALLBACK END ###
[IPU1-1] 7.074971 s:
[IPU1-1] 7.075245 s: ti.sysbios.gates.GateMutex: line 99: ti.sysbios.gates.GateMutex: line 99: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details.
[IPU1-1] 7.075459 s: xdc.runtime.Error.raise: terminating execution

Could you please provide some guide on these questions?

Thanks in advance.

Hi,

Can you please step through the function which is returning 'status == 0'(statement before line no.407 in 'utils_dcan.c') which causes this assertions?

Step through the above function and see where exactly it is returning the error.

How did you exactly delay the initial of DCAN?

Thanks & Regards,
Vivek Dhande.

Texas Instruments (India) Pvt Ltd

Hi,

Statement before line no.407 in 'utils_dcan.c'

status = Utils_queGet(handle,(Ptr *)msgPtr,1, BIOS_NO_WAIT); (Utils_dcanQueGet)
UTILS_assert(status == 0);

Track results: status = SYSTEM_LINK_STATUS_EFAIL;

Did not modify the original position of 'System_dcanInit'.
Mark 'PlatformDCAN1SetPinMux', wait for the app to start and then execute.

Thanks in advance.

Hi,

    Can you please step through the 'Utils_queGet()' function and see why it is returning 'SYSTEM_LINK_STATUS_EFAIL'?

Thanks & Regards,
Vivek Dhande.

Texas Instruments (India) Pvt Ltd