TDA4AL-Q1: MCUSS Demo Application : CAN Profiling Application operate in Tx only or External Loopback and Polling mode or interrupt mode all failure.

Shine

Part Number: TDA4AL-Q1
Other Parts Discussed in Thread: J721S2XSOMXEVM

Hello Champs,

SDK: ti-processor-sdk-rtos-j721s2-evm-08_06_01_03, ti-processor-sdk-linux-j721s2-evm-08_06_01_02

Development board: J721S2XSOMXEVM

Customer is studying the MCUSS Demo Application : CAN Profiling Application, and do the follow six test, please check it and help to fix the Questions(Q1, Q2, Q3, Q4).

Test 1. operate in internal loop-back and interrupt mode by default : Run OK.

step1: build

hduser@J721S2:~/ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw/build$ sudo make can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos -sj

step2: use the CCS to load and run the can_profile_app_freertos_mcu1_0_release.xer5f on MCU_Cortex_R5_0.

Step3: Read the UART log, and we can find it works ok.

[2023-07-06 15:52:45.797] CAN Profile App:Variant - Pre Compile being used !!!
[2023-07-06 15:52:45.797] CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN0!!!
[2023-07-06 15:52:45.877] CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN1!!!
[2023-07-06 15:52:45.941] CAN Profile App:Will Transmit & Receive (Internal-loopback) 10000 Messages, 2 times
[2023-07-06 15:52:49.493] CAN Profile App:NOTE : Operating in interrupt mode!
[2023-07-06 15:52:49.541] CAN Profile App:Transmit & Receive (Internal-loopback) 10000 packets 2 times
[2023-07-06 15:52:49.621] CAN Profile App:Average of 86.20032 usecs per packet
[2023-07-06 15:52:49.669] CAN Profile App:Average of 11560 packets in 1 second with CPU Load 0.000000%
[2023-07-06 15:52:49.749] CAN Profile App:Packets sent: 20000, Packets recv: 20000 in total time: 3460032 us
[2023-07-06 15:52:49.845] CAN Profile App:Measured Load: Total CPU: 100.000000%, TSK: 0.000000%
[2023-07-06 15:52:49.910] CAN Profile App:Message Id Received c00000c0 Message Length is 64
[2023-07-06 15:52:49.989] CAN Profile App:Test completed for 0 instance
[2023-07-06 15:52:50.036]
[2023-07-06 15:52:50.036] CAN Profile App: 2744 bytes used for stack
[2023-07-06 15:52:50.085] CAN Profile App:Profiling completes sucessfully!!!

Test 2. operate in internal loop-back and polling mode : Run OK.

step1: According to the MCUSW: CAN Profiling Application shows, update related codes to configure the can profiling application operate in internal loop-back and polling mode.

admin:///media/sf_J721S2TDA4Share/Polling%20mode.PNG

step2: build

hduser@J721S2:~/ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw/build$ sudo make can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos -sj

step3: use the CCS to load and run the can_profile_app_freertos_mcu1_0_release.xer5f on MCU_Cortex_R5_0.

Step4: Read the UART log, and we can find it works ok.

[2023-07-06 16:09:47.631] CAN Profile App:Variant - Pre Compile being used !!!
[2023-07-06 16:09:47.647] CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN0!!!
[2023-07-06 16:09:47.710] CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN1!!!
[2023-07-06 16:09:47.775] CAN Profile App:Will Transmit & Receive (Internal-loopback) 10000 Messages, 2 times
[2023-07-06 16:11:07.866] CAN Profile App:NOTE : Operating in polling mode!
[2023-07-06 16:11:07.913] CAN Profile App:NOTE : Batch processing enabled!
[2023-07-06 16:11:07.961] CAN Profile App:Transmit & Receive (Internal-loopback) 10000 packets 2 times
[2023-07-06 16:11:08.041] CAN Profile App:Average of 250.34 usecs per packet
[2023-07-06 16:11:08.106] CAN Profile App:Average of 3999 packets in 1 second with CPU Load 0.000000%
[2023-07-06 16:11:08.185] CAN Profile App:Packets sent: 160000, Packets recv: 160000 in total time: 80000034 us
[2023-07-06 16:11:08.265] CAN Profile App:Measured Load: Total CPU: 100.000000%, TSK: 0.000000%
[2023-07-06 16:11:08.345] CAN Profile App:Message Id Received c00000c0 Message Length is 64
[2023-07-06 16:11:08.409] CAN Profile App:Test completed for 0 instance
[2023-07-06 16:11:08.456]
[2023-07-06 16:11:08.456] CAN Profile App: 2744 bytes used for stack
[2023-07-06 16:11:08.505] CAN Profile App:Profiling completes sucessfully!!!

Test 3. operate in TX Only and polling mode : Run Failed

step1: According to the MCUSW: CAN Profiling Application shows, update related codes to configure the can profiling application operate in Tx Only and polling mode.

admin:///media/sf_J721S2TDA4Share/Tx%20only.PNG

step2: build

hduser@J721S2:~/ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw/build$ sudo make can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos -sj

step3: use the CCS to load and run the can_profile_app_freertos_mcu1_0_release.xer5f on MCU_Cortex_R5_0.

Step4: Read the UART log, and we can find it shows CAN Test Failed!!!.

Q1: What other actions should I do if I want to run the can profiling application operate in Tx Only and polling mode?

Test 4. operate in TX Only and interrupt mode : Run Failed

step1: According to the MCUSW: CAN Profiling Application shows, update related codes to configure the can profiling application operate in Tx Only and interrupt mode.

admin:///media/sf_J721S2TDA4Share/Interrupt%20mode.PNG

step2: build

hduser@J721S2:~/ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw/build$ sudo make can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos -sj

step3: use the CCS to load and run the can_profile_app_freertos_mcu1_0_release.xer5f on MCU_Cortex_R5_0.

Step4: Read the UART log, and we can find it stop after "CAN Profile App:Will Transmit 10000 Messages", according to the code, it seems stop at "SemaphoreP_pend(CanIf_TxConfirmationSemaphore,SemaphoreP_WAIT_FOREVER);"

Q2: What other actions should I do if I want to run the can profiling application operate in Tx Only and interrupt mode?

Test 5. operate in External Loopback and interrupt mode : Run Failed

step1: According to the MCUSW: CAN Profiling Application shows, update related codes to configure the can profiling application operate in External Loopback and interrupt mode.

admin:///media/sf_J721S2TDA4Share/External%20Loopback.PNG

step2: build

hduser@J721S2:~/ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw/build$ sudo make can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos -sj

step3: Loop these two header J31,J30 with jumper wire. MCU_MCAN0_H <- Jumper Wire ->MCU_MCAN1_H AND MCU_MCAN0_L <- Jumper Wire ->MCU_MCAN1_L

admin:///media/sf_J721S2TDA4Share/External%20Loopback%20wire.PNG

step4: use the CCS to load and run the can_profile_app_freertos_mcu1_0_release.xer5f on MCU_Cortex_R5_0.

Step5: Read the UART log, and we can find it stop after "CAN Profile App:Will Transmit & Receive (External-loopback) 10000 Message, 2 times", according to the code, it seems stop at "SemaphoreP_pend(CanIf_TxConfirmationSemaphore,SemaphoreP_WAIT_FOREVER);"

Q3: What other actions should I do if I want to run the can profiling application operate in External Loopback and interrupt mode?

Test 6. operate in External Loopback and polling mode : Run Failed

step1: According to the MCUSW: CAN Profiling Application shows, update related codes to configure the can profiling application operate in External Loopback and polling mode.

admin:///media/sf_J721S2TDA4Share/Polling%20mode.PNG

step2: build

hduser@J721S2:~/ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw/build$ sudo make can_profile_app BOARD=j721s2_evm SOC=j721s2 BUILD_PROFILE=release CORE=mcu1_0 BUILD_OS_TYPE=freertos -sj

step3: Loop these two header J31,J30 with jumper wire. MCU_MCAN0_H <- Jumper Wire ->MCU_MCAN1_H AND MCU_MCAN0_L <- Jumper Wire ->MCU_MCAN1_L

admin:///media/sf_J721S2TDA4Share/External%20Loopback%20wire.PNG

step4: use the CCS to load and run the can_profile_app_freertos_mcu1_0_release.xer5f on MCU_Cortex_R5_0.

Step5: Read the UART log,and we can find it shows CAN Test Failed!!!.

CAN Profile App:Variant - Pre Compile being used !!!
CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN0!!!
CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN1!!!
CAN Profile App:Will Transmit & Receive (External-loopback) 10000 Messages, 2 times
CAN Profile App:NOTE : Operating in polling mode!
CAN Profile App:NOTE : Batch processing enabled!
CAN Profile App:Transmit & Receive (External-loopback) 10000 packets 2 times
CAN Profile App:Average of 500.03 usecs per packet
CAN Profile App:Average of 2000 packets in 1 second with CPU Load 0.000000%
CAN Profile App:Packets sent: 160000, Packets recv: 0 in total time: 80000003 us
CAN Profile App:Measured Load: Total CPU: 100.000000%, TSK: 0.000000%
CAN Profile App:CanApp_ProfileStatus = E_NOT_OK at line566.
CAN Profile App: 2744 bytes used for stack
CAN Profile App:CAN Test Failed!!!

Q4: What other actions should I do if I want to run the can profiling application operate in External Loopback and polling mode?

Thanks
Regards
Shine

over 2 years ago

0 Tarun Mukesh Puvvada over 2 years ago

TI__Guru 52876 points

Hello,

Thanks for writing .

Sorry i am unable to see the images attached.

As far as i inferred from the description , customer are facing issues with Tx only mode and External loop back mode.

Along with the changes done in source code. customer need to connect external hardware (Ex:PEAK CAN tool etc...) to the respective MCAN Pins for running Tx only mode or Rx only mode.

Shine said:
CAN Profile App:Variant - Pre Compile being used !!!
CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN0!!!
CAN Profile App: Successfully Enabled CAN Transceiver MCU MCAN1!!!
CAN Profile App:Will Transmit 10000 Messages, 2 times

In this case EVM is trying to send data but couldn't find the external device and failed to transmit.

Please see steps under "TX Only mode" regarding PEAK CAN connection mentioned below in the CAN profiling User guide.

In case of external loop back ,

While running on MCU1_0 it transmits on MCU MCAN0 and receive on MCU MCAN1. Additional setup is needed, connect CANH <-> CANH, CANL <-> CANL and GND <-> GND of the respective CANs. i.e. while running on MCU1_0, MCU MCAN0 and MCU MCAN1 should be connected

Regards

Tarun Mukesh

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

hi，Tarun Mukesh

Thanks for your suggestion.

In fact, In Tx only with interrupt mode case, I have connect a CANalyzer, and CANalyzer did not receive any messages.

In External loopback with interrupt mode case, I did the addtional setup that connect CANH <-> CANH, CANL <-> CANL and GND <-> GND of J31 and J30 in development board.

Both the two modes, the project stops at the source code "SemaphoreP_pend(CanIf_TxConfirmationSemaphore,SemaphoreP_WAIT_FOREVER);" in "can_profile.c" after running.

The following link in TI E2E forums seems meet the same question, but not share the detail solution. Please check it and share the detail solution.

DRA829V: Semaphore _Pend() in can_profile application waiting forever after first can_write() - Processors forum - Processors - TI E2E support forums

Regards

Shuai Feng

0 Tarun Mukesh Puvvada over 2 years ago in reply to Shuai Feng

TI__Guru 52876 points

Hello,

Can you please verify whether you are able to run example mcusw/mcal_drv/mcal/examples/Can/soc/j721s2/mcu1_0/CanApp_Startup.c successfully in your test setup? for both Tx and External loop back

Please follow http://downloads.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/ug_can_top.html

This will help me in identifying the issue.

Regards

Tarun Mukesh

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

hi,

Can you please verify whether you are able to run example mcusw/mcal_drv/mcal/examples/Can/soc/j721s2/mcu1_0/CanApp_Startup.c successfully in your test setup? for both Tx and External loop back

-->I do the follw actions, please check it. If it not meets your expect, please show me detailed development steps, Thank you.

Step1: Use make command "make -s can_app BOARD=j721s2_evm CORE=mcu1_0" to generate "can_app_mcu1_0_release.xer5f"

Step2: Make the pcb board work on No Boot Mode, and power on.

Step3: Setting the loadSciserverFlag from 1 to 0 in launch.js file so that to develop and debug on MCU1_0.

Step4: Running CCS and launch Selected Configuration

Step5: LoadJSFile in CCS

Step6: Load Program On MCU_Cortex_R5_0

Step7: Resume MCU_Cortex_R5_0

Step8: Check the UART Log of MCU R5F

[2023-07-11 11:18:21.825] SBL Revision: 01.00.10.01 (Jun 29 2023 - 10:37:24)
[2023-07-11 11:18:22.052] TIFS  ver: 8.6.3--1-g2249f (Chill Capybara
[2023-07-11 11:18:22.338] CAN_APP: Sample Application - STARTS !!!
[2023-07-11 11:18:22.370] CAN_APP: Variant - Pre Compile being used !!!
[2023-07-11 11:18:22.417] DET Error reported. Module ID:120  Api ID:1  Error ID:10 
[2023-07-11 11:18:22.482] DET Error reported. Module ID:120  Api ID:0  Error ID:10 
[2023-07-11 11:18:22.546] CAN_APP: Error in Enabling CAN Transceiver MCU MCAN0!!!
[2023-07-11 11:18:22.593] CAN_APP: Successfully Enabled CAN Transceiver MCU MCAN1!!!
[2023-07-11 11:18:22.658] CAN_APP: Message Id Received 400000a0 Message Length is 64	 
[2023-07-11 11:18:22.721] CAN_APP: Can Controller Instance MCAN 0                   Internal LoopBack Mode Test Passed
[2023-07-11 11:18:22.816] CAN_APP: Message Id Received c00000b0 Message Length is 64	 
[2023-07-11 11:18:22.881] CAN_APP: Can Controller Instance MCAN 1                   Internal LoopBack Mode Test Passed
[2023-07-11 11:18:22.978] CAN_APP: Message Id Received 400000c0 Message Length is 64	 
[2023-07-11 11:18:23.041] CAN_APP: Can Controller Instance MCAN 2                   Internal LoopBack Mode Test Passed
[2023-07-11 11:18:23.137] 
[2023-07-11 11:18:23.137] CAN_APP: Safety Diagnostic API functionality test for controller MCAN 0 
[2023-07-11 11:18:23.217] CAN_APP: Can_EnableIntr() API test
[2023-07-11 11:18:23.250] CAN_APP: Successfully Enabled TOO interrupt 
[2023-07-11 11:18:23.298] CAN_APP: Successfully Enabled PEA interrupt 
[2023-07-11 11:18:23.349] CAN_APP: Can_GetIntrStatus() API test
[2023-07-11 11:18:23.377] CAN_APP: No error event occured
[2023-07-11 11:18:23.414] CAN_APP: Can_ClearIntrStatus() API test
[2023-07-11 11:18:23.457] CAN_APP: Interrupt Status Clear Successful
[2023-07-11 11:18:23.505] CAN_APP: Can_DisableIntr() API test
[2023-07-11 11:18:23.537] CAN_APP: Successfully Disable TOO interrupt
[2023-07-11 11:18:23.588] CAN_APP: Successfully Disable PEA interrupt
[2023-07-11 11:18:23.632] CAN_APP: Can_RegisterReadback() API test
[2023-07-11 11:18:23.681] CAN_APP: Can_RegisterReadback Successful
[2023-07-11 11:18:23.730] 
[2023-07-11 11:18:23.730] CAN_APP: Safety Diagnostic API functionality test for controller MCAN 1 
[2023-07-11 11:18:23.793] CAN_APP: Can_EnableIntr() API test
[2023-07-11 11:18:23.841] CAN_APP: Successfully Enabled TOO interrupt 
[2023-07-11 11:18:23.889] CAN_APP: Successfully Enabled PEA interrupt 
[2023-07-11 11:18:23.937] CAN_APP: Can_GetIntrStatus() API test
[2023-07-11 11:18:23.969] CAN_APP: No error event occured
[2023-07-11 11:18:24.000] CAN_APP: Can_ClearIntrStatus() API test
[2023-07-11 11:18:24.050] CAN_APP: Interrupt Status Clear Successful
[2023-07-11 11:18:24.102] CAN_APP: Can_DisableIntr() API test
[2023-07-11 11:18:24.130] CAN_APP: Successfully Disable TOO interrupt
[2023-07-11 11:18:24.179] CAN_APP: Successfully Disable PEA interrupt
[2023-07-11 11:18:24.226] CAN_APP: Can_RegisterReadback() API test
[2023-07-11 11:18:24.259] CAN_APP: Can_RegisterReadback Successful
[2023-07-11 11:18:24.306] 
[2023-07-11 11:18:24.307] CAN_APP: Safety Diagnostic API functionality test for controller MCAN 2 
[2023-07-11 11:18:24.386] CAN_APP: Can_EnableIntr() API test
[2023-07-11 11:18:24.418] CAN_APP: Successfully Enabled TOO interrupt 
[2023-07-11 11:18:24.466] CAN_APP: Successfully Enabled PEA interrupt 
[2023-07-11 11:18:24.515] CAN_APP: Can_GetIntrStatus() API test
[2023-07-11 11:18:24.561] CAN_APP: No error event occured
[2023-07-11 11:18:24.594] CAN_APP: Can_ClearIntrStatus() API test
[2023-07-11 11:18:24.625] CAN_APP: Interrupt Status Clear Successful
[2023-07-11 11:18:24.674] CAN_APP: Can_DisableIntr() API test
[2023-07-11 11:18:24.728] CAN_APP: Successfully Disable TOO interrupt
[2023-07-11 11:18:24.771] CAN_APP: Successfully Disable PEA interrupt
[2023-07-11 11:18:24.802] CAN_APP: Can_RegisterReadback() API test
[2023-07-11 11:18:24.849] CAN_APP: Can_RegisterReadback Successful
[2023-07-11 11:18:24.897] CAN Stack Usage: 2908 bytes
[2023-07-11 11:18:24.931] CAN_APP: CAN Test Passed!!!

As we know, because the macro CAN_LOOPBACK_ENABLE is defined with "STD_ON" by default, and the function "Can_TestLoopBackModeEnable" will be called, the can work on internal loopback mode.

In order to make the can_app demo work on tx mode, I redefine the macro CAN_LOOPBACK_ENABLE with STD_OFF in mcal_drv\mcal\examples_config\Can_Demo_Cfg\output\generated\soc\j721s2\mcu1_0\include\Can_Cfg.h.

And connect a CANalyzer, then do the Step1 ~ Step7 described above and check the UART Log of MCU R5F.

CAN_APP: Sample Application - STARTS !!!
CAN_APP: Variant - Pre Compile being used !!!
DET Error reported. Module ID:120  Api ID:1  Error ID:10
DET Error reported. Module ID:120  Api ID:0  Error ID:10
CAN_APP: Error in Enabling CAN Transceiver MCU MCAN0!!!
CAN_APP: Successfully Enabled CAN Transceiver MCU MCAN1!!!

According to the log, we can find the project seems blocking somewhere after running.

And the CANalyzer receive nothing.

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

Hello，

The follow link seems meet the same issue, but no detailed solution.

TDA4VM: CAN profile App Demo in RTOS SDK(ti-processor-sdk-rtos-j721e-evm-08_00_00_12) run failed with External Loopback mode - Processors forum - Processors - TI E2E support forums

0 Tarun Mukesh Puvvada over 2 years ago in reply to Shuai Feng

TI__Guru 52876 points

Hello,

Thanks for the details.

I see few errors in the log of Can_app example .May i know below details from you ?

1. Are you running this on the TDA4 EVM or a custom board?

2. Please post the changes you made to the default SDK before running, I will try to run it on my side.

Regards

Tarun Mukesh

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

hello,

1. Are you running this on the TDA4 EVM or a custom board?

-->

SDK: ti-processor-sdk-rtos-j721s2-evm-08_06_01_03, ti-processor-sdk-linux-j721s2-evm-08_06_01_02

Development board: J721S2XSOMXEVM

Please check the follow link for detaild which I am running.

J721S2XSOMXEVM Evaluation board | TI.com

2. Please post the changes you made to the default SDK before running, I will try to run it on my side.

-->

[2023-07-11 11:18:21.825] SBL Revision: 01.00.10.01 (Jun 29 2023 - 10:37:24)
[2023-07-11 11:18:22.052] TIFS  ver: 8.6.3--1-g2249f (Chill Capybara
[2023-07-11 11:18:22.338] CAN_APP: Sample Application - STARTS !!!
[2023-07-11 11:18:22.370] CAN_APP: Variant - Pre Compile being used !!!
[2023-07-11 11:18:22.417] DET Error reported. Module ID:120  Api ID:1  Error ID:10 
[2023-07-11 11:18:22.482] DET Error reported. Module ID:120  Api ID:0  Error ID:10 
[2023-07-11 11:18:22.546] CAN_APP: Error in Enabling CAN Transceiver MCU MCAN0!!!
[2023-07-11 11:18:22.593] CAN_APP: Successfully Enabled CAN Transceiver MCU MCAN1!!!
[2023-07-11 11:18:22.658] CAN_APP: Message Id Received 400000a0 Message Length is 64	 
[2023-07-11 11:18:22.721] CAN_APP: Can Controller Instance MCAN 0                   Internal LoopBack Mode Test Passed
[2023-07-11 11:18:22.816] CAN_APP: Message Id Received c00000b0 Message Length is 64	 
[2023-07-11 11:18:22.881] CAN_APP: Can Controller Instance MCAN 1                   Internal LoopBack Mode Test Passed
[2023-07-11 11:18:22.978] CAN_APP: Message Id Received 400000c0 Message Length is 64	 
[2023-07-11 11:18:23.041] CAN_APP: Can Controller Instance MCAN 2                   Internal LoopBack Mode Test Passed
[2023-07-11 11:18:23.137] 
[2023-07-11 11:18:23.137] CAN_APP: Safety Diagnostic API functionality test for controller MCAN 0 
[2023-07-11 11:18:23.217] CAN_APP: Can_EnableIntr() API test
[2023-07-11 11:18:23.250] CAN_APP: Successfully Enabled TOO interrupt 
[2023-07-11 11:18:23.298] CAN_APP: Successfully Enabled PEA interrupt 
[2023-07-11 11:18:23.349] CAN_APP: Can_GetIntrStatus() API test
[2023-07-11 11:18:23.377] CAN_APP: No error event occured
[2023-07-11 11:18:23.414] CAN_APP: Can_ClearIntrStatus() API test
[2023-07-11 11:18:23.457] CAN_APP: Interrupt Status Clear Successful
[2023-07-11 11:18:23.505] CAN_APP: Can_DisableIntr() API test
[2023-07-11 11:18:23.537] CAN_APP: Successfully Disable TOO interrupt
[2023-07-11 11:18:23.588] CAN_APP: Successfully Disable PEA interrupt
[2023-07-11 11:18:23.632] CAN_APP: Can_RegisterReadback() API test
[2023-07-11 11:18:23.681] CAN_APP: Can_RegisterReadback Successful
[2023-07-11 11:18:23.730] 
[2023-07-11 11:18:23.730] CAN_APP: Safety Diagnostic API functionality test for controller MCAN 1 
[2023-07-11 11:18:23.793] CAN_APP: Can_EnableIntr() API test
[2023-07-11 11:18:23.841] CAN_APP: Successfully Enabled TOO interrupt 
[2023-07-11 11:18:23.889] CAN_APP: Successfully Enabled PEA interrupt 
[2023-07-11 11:18:23.937] CAN_APP: Can_GetIntrStatus() API test
[2023-07-11 11:18:23.969] CAN_APP: No error event occured
[2023-07-11 11:18:24.000] CAN_APP: Can_ClearIntrStatus() API test
[2023-07-11 11:18:24.050] CAN_APP: Interrupt Status Clear Successful
[2023-07-11 11:18:24.102] CAN_APP: Can_DisableIntr() API test
[2023-07-11 11:18:24.130] CAN_APP: Successfully Disable TOO interrupt
[2023-07-11 11:18:24.179] CAN_APP: Successfully Disable PEA interrupt
[2023-07-11 11:18:24.226] CAN_APP: Can_RegisterReadback() API test
[2023-07-11 11:18:24.259] CAN_APP: Can_RegisterReadback Successful
[2023-07-11 11:18:24.306] 
[2023-07-11 11:18:24.307] CAN_APP: Safety Diagnostic API functionality test for controller MCAN 2 
[2023-07-11 11:18:24.386] CAN_APP: Can_EnableIntr() API test
[2023-07-11 11:18:24.418] CAN_APP: Successfully Enabled TOO interrupt 
[2023-07-11 11:18:24.466] CAN_APP: Successfully Enabled PEA interrupt 
[2023-07-11 11:18:24.515] CAN_APP: Can_GetIntrStatus() API test
[2023-07-11 11:18:24.561] CAN_APP: No error event occured
[2023-07-11 11:18:24.594] CAN_APP: Can_ClearIntrStatus() API test
[2023-07-11 11:18:24.625] CAN_APP: Interrupt Status Clear Successful
[2023-07-11 11:18:24.674] CAN_APP: Can_DisableIntr() API test
[2023-07-11 11:18:24.728] CAN_APP: Successfully Disable TOO interrupt
[2023-07-11 11:18:24.771] CAN_APP: Successfully Disable PEA interrupt
[2023-07-11 11:18:24.802] CAN_APP: Can_RegisterReadback() API test
[2023-07-11 11:18:24.849] CAN_APP: Can_RegisterReadback Successful
[2023-07-11 11:18:24.897] CAN Stack Usage: 2908 bytes
[2023-07-11 11:18:24.931] CAN_APP: CAN Test Passed!!!

For the first log show as above, No changes to default SDK before running.

For the second log show as follow, Only changes the macro CAN_LOOPBACK_ENABLE from STD_ON to STD_OFF in "mcusw\mcal_drv\mcal\examples_config\Can_Demo_Cfg\output\generated\soc\j721s2\mcu1_0\include\Can_Cfg.h" before running.

CAN_APP: Sample Application - STARTS !!!
CAN_APP: Variant - Pre Compile being used !!!
DET Error reported. Module ID:120  Api ID:1  Error ID:10
DET Error reported. Module ID:120  Api ID:0  Error ID:10
CAN_APP: Error in Enabling CAN Transceiver MCU MCAN0!!!
CAN_APP: Successfully Enabled CAN Transceiver MCU MCAN1!!!

0 Tarun Mukesh Puvvada over 2 years ago in reply to Shuai Feng

TI__Guru 52876 points

Hello,

Shuai Feng said:
J721S2XSOMXEVM

I do understand you are using J721S2 SOM but are you using it on top of J7 Common processor board of TI or any other custom board?

Let us go back to Can_Profile_app and let me know the changes done for Tx only mode first

Regards

Tarun Mukesh

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

Hello,

1. Using J72S2SOM on top of J7X Common processor board of TI.

2. Can_Profile_app changes done for Tx only mode:

0 Tarun Mukesh Puvvada over 2 years ago in reply to Shuai Feng

TI__Guru 52876 points

ok Thanks.

Allow me to test this at my end and i will get back to you.

Thanks

Tarun Mukesh

0 Tarun Mukesh Puvvada over 2 years ago in reply to Tarun Mukesh Puvvada

TI__Guru 52876 points

Hello,

I have faced similar issue at my end and i have raised internal query on this.Let me get back to you after the reply.

Regards

Tarun Mukesh

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

Hello,

Please also check the Rx Only mode and External Loopback mode with interrupt mode.

0 Tarun Mukesh Puvvada over 2 years ago in reply to Shuai Feng

TI__Guru 52876 points

Hello Team,

I have added the patch to fix the issue.

Steps to apply the patch and see the files changed in Linux machine :

1) Download the attached patch into local directory.

2) Go into ti-processor-sdk-rtos-j721s2-evm-08_06_01_03/mcusw path

3) git init

4) git add .

5) git commit -asm "Original SDK 8.6"

6) git apply (path to patch in local directory)/(patch_name).patch

7) git status

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/0001_2D00_Patch_2D00_to_2D00_fix_2D00_Can_2D00_Profiling_2D00_J721S2_2D00_SDK_2D00_8.6.patch

Regards

Tarun Mukesh

0 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

Hello,

Appreciate your support, I will download the patch and follow your steps, then testing and give you a feedback.

Regards

Shuai Feng

+1 Shuai Feng over 2 years ago in reply to Tarun Mukesh Puvvada

Prodigy 150 points

Hello,

After merging the patch, the CAN demo works well at my bench.

Thanks for your support.

Regards

Shuai Feng