Is CanTrcv SN65HVD230 is compatible with AM62x MCU_MCAN0?

Hi Nihar,
Thanks for your feedback.
Now we are able to build the MCAL SDK can_app but below error message is reported while flashing the executable:

Could you please provide your feedback on this?

BR,
Shubham

Hello Shubham,

Which boot mode are you using? 

Have followed the steps to initialize the SoC mentioned in the link below?

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_01_00_39/exports/docs/api_guide_am62x/EVM_SETUP_PAGE.html

Regards,

Nihar Potturu.

Hi Nihar,

We have followed the steps to initialize the SoC mentioned in the above link but still same error is observed.

Can we have a debug session to check and fix it?

BR,

Shubham

Hello Shubham, 

Shubham Goel said:

We have followed the steps to initialize the SoC mentioned in the above link but still same error is observed.

Did you follow the steps mentioned below while loading the binary?

https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_02_01_06/exports/docs/api_guide_am62x/CCS_LAUNCH_PAGE.html#:~:text=Configuration%20After%20Launch-,Load%20and%20run%20example%20binaries,-POWER%2DON%20the

This is a fairly straightforward method and it should work directly. Please recheck your boot mode settings and check if you are able to see the boot logs in UART terminal as expected as shown in the link I attached.

Regards,

Nihar Potturu.

Hello Nihar, Hello Krithika,

As our next planned technical session is still a month away, is it possible to have a small debug session together to help us resolve the problem. As the team is currently blocked with the issue,

Regards,

Naveen

Hello Naveen,

Nihar is out of office currently.

Can you confirm if you are seeing the logs on UART after flashing SBL NULL, as seen in link posted by Nihar?

Starting NULL Bootloader ...

  SYSFW Firmware Version 9.2.7--v09.02.07 (Kool Koala)
  SYSFW Firmware revision 0x9
  SYSFW ABI revision 3.1


  INFO: Bootloader_runCpu:176: CPU m4f0-0 is initialized to 400000000 Hz !!!
  INFO: Bootloader_runCpu:176: CPU a530-0 is initialized to 1400000000 Hz !!!
  INFO: Bootloader_runCpu:176: CPU a530-1 is initialized to 1400000000 Hz !!!
  INFO: Bootloader_runCpu:176: CPU a531-0 is initialized to 1400000000 Hz !!!
  INFO: Bootloader_runCpu:176: CPU a531-1 is initialized to 1400000000 Hz !!!
  INFO: Bootloader_loadSelfCpu:229: CPU r5f0-0 is initialized to 400000000 Hz !!!
  INFO: Bootloader_JumpSelfCpu:248: All done, jumping self ...

Regards,
Krithika

Hi Krithika,

We are getting error while running below command to flash the SOC initialization binary to the EVM:

cd ${SDK_INSTALL_PATH}/tools/boot
python uart_uniflash.py -p COM<x> --cfg=sbl_prebuilt/am62x-sk/default_sbl_null.cfg

Error:


It is expecting sbl_uart_uniflash_stage2.release.appimage and ipc_rpmsg_echo_linux.release.appimage which is not present inside mcu_plus_sdk_am62x_09_01_00_39.

BR,
Shubham

Hi Shubham,

Step1: Please check if your board is GP or HS-FS, in order to use the correct config file and images:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1228618/faq-am6xx-how-to-check-if-device-type-is-hs-se-hs-fs-or-gp 
C:\ti\mcu_plus_sdk_am62x_09_02_01_06\tools\boot\sbl_prebuilt\am62x-sk\default_sbl_null.cfg [For GP board]
C:\ti\mcu_plus_sdk_am62x_09_02_01_06\tools\boot\sbl_prebuilt\am62x-sk\default_sbl_ospi_hs_fs.cfg [For HS-FS board]

Step2: Ensure all the images used in the .cfg file are available in their respective paths.
The appimages are not available in the prebuilt folder, they need to be built from the respective examples. Please build the below examples and use the appimage generated:
https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/08_06_00_18/exports/docs/api_guide_am62x/GETTING_STARTED_BUILD.html

C:\ti\mcu_plus_sdk_am62x_09_02_01_06\examples\drivers\boot\sbl_uart_uniflash_multistage\sbl_uart_uniflash_stage2\am62x-sk\r5fss0-0_nortos\ti-arm-clang
C:\ti\mcu_plus_sdk_am62x_09_02_01_06\examples\drivers\ipc\ipc_rpmsg_echo_linux\am62x-sk\r5fss0-0_freertos\ti-arm-clang

Regards,
Krithika

Hi Krithika,

Step-1: As per https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1228618/faq-am6xx-how-to-check-if-device-type-is-hs-se-hs-fs-or-gp, we are using GP board and default_sbl_null.cfg.

Step-2: Below error message is reported while building "hello world example" using makefiles with mentioned command:

Command: cd ${SDK_INSTALL_PATH}
gmake -s -C examples/hello_world/am62x-sk/r5fss0-0_freertos/ti-arm-clang

Error: 

BR,

Shubham

Hi Shubham,

Please ensure you have installed the right versions of the Syscfg and other tools installed:
https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_01_00_39/exports/docs/api_guide_am62x/SDK_DOWNLOAD_PAGE.html#autotoc_md12 

Regards,
Krithika

Hi Krithika,

We are using all the required tools as per https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_01_00_39/exports/docs/api_guide_am62x/SDK_DOWNLOAD_PAGE.html#autotoc_md12.

MCAL: MCAL_SitaraMPU_09.01.00

MCU+SDK: mcu_plus_sdk_am62x_09_01_00_39

CCS: ccs1250

Toolchain: ti-cgt-armllvm_3.2.0.LTS

SysConfig: sysconfig_1.18.0

Python: 3.9.1

Please let me know if we are missing something.

BR,

Shubham

Hello Shubham,

Can you please provide the exact path of Sysconfig install directory?

Is it exact same as C:\ti\sysconfig_1.18.0?

Please provide screenshot of the path where sysconfig tool is installed.

Please refer below screenshot.

Regards,

Tushar

Hi Tushar,

sysconfig_1.18.0 is used from default path of CCS as below:

BR,

Shubham

Hello Shubham,

This is the cause of the issue.

As you can see the sysconfig tool is inside the CCS root directory not under C:\ti.

The gmake tool is trying to find the sysconfig tool at location C:\ti which it is unable to locate and giving errors as shown above.

Please install sysconfig v1.18 from sysconfig-1.18.0_3266-setup.exe at location C:\ti.

Regards,

Tushar

Hi Tushar,

Thanks for your feedback.

Above error is fixed by configuring sysconfig v1.18 at location C:\ti.

Another error is observed during Generating certificate for hello_world.release.appimage.

I have installed "Win64 OpenSSL v3.3.1 Light" from https://slproweb.com/products/Win32OpenSSL.html at location C:\Program Files\OpenSSL-Win64 and configured C:\Program Files\OpenSSL-Win64\bin as PATH of environment variable.

BR,

Shubham

Hello Shubham,

Can you please check once is the path to OPENSSL is added correctly in the system?

Please check are you able to run the below commands from any directory?

openssl version
openssl

Are you able to see below outputs?

Regards,

Tushar

Hi Tushar,

I have installed version "Win64 OpenSSL v3.3.1 Light" and console output is as below:

BR,

Shubham

Hello Shubham,

I can see that you have the OPENSSL installed in your system and path is also added correctly.

Can you please try building the example once in a new/fresh command prompt windows and close all the other instance that are open already?

It should work without any error, please try to build in a new instance of command prompt and let us know the results. 

Regards,

Tushar

Hi Tushar,

Thanks for your inputs.

Now we are able to build the required appimages and flash the CAN APP in internal loopback mode.

For external loopback mode we updated the CAN APP as per https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1329465/faq-sk-am62x-sk-am62a-lp-testing-mcan-external-loopback-example-using-external-transceiver-tcan1042d 

App_mcanConfig(TRUE) --> App_mcanConfig(FALSE) in mcan_loopback_interrupt.c and mcan_loopback_polling.c

But no frames are observed on PCAN.

We are trying to test CAN Communication for MCAN0 instance.

Can you please let us know the steps to test MCAN0 instance CAN Communication for external loopback mode.

BR,

Shubham

Hello Shubham,

Shubham Goel said:

App_mcanConfig(TRUE) --> App_mcanConfig(FALSE) in mcan_loopback_interrupt.c and mcan_loopback_polling.c

Based on the logs, it looks like you are running the MCAL application. 

Did you disable the Can_testloopBackModeEnable parameter from EB Tresos tool and regenerated the config files? The App_mcanConfig is for the MCU+SDK MCAN example. If you are running the MCAL example the parameter will not be applicable.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/09_02_00_05/exports/docs/mcusw/mcal_drv/docs/drv_docs/ug_can_top.html#:~:text=E_OK%2C%20E_NOT_OK-,Can_TestLoopBackModeEnable,-This%20service%20will

Regards,

Nihar Potturu. 

Hi Nihar,

Yes.. we are running MCAL Application.

After updating Can_testloopBackModeEnable parameter to disable, we are able to see one frame on PCAN for MCU_MCAN0 (mcu header) Instance.

But no frame is observed for MCAN0 (user expansion) Instance.

Could you please let us know if any additional steps need to be taken care for testing MCAN0 Instance?

BR,

Shubham

Hi Nihar,

Could you please provide your feedback on this?

BR,

Shubham

Hi Nihar,

Could you please provide your feedback on this?

BR,

Shubham

Hello Nihar, Hello Krithika,

Request you to please provide the feedback of Shubham's request as currently we are blocked and might impact our release dates.

Regards,

Naveen

Shubham Goel said:

we are able to see one frame on PCAN for MCU_MCAN0 (mcu header) Instance

Could you verify from the example code, to check how many frames are being sent over? If this is an external loopback you might need to send back CAN messages for the test to pass.

Shubham Goel said:

But no frame is observed for MCAN0 (user expansion) Instance.

MCAN0 is not routed to main R5, hence it is not possible to test this. You can use the MCU_MCAN1 instance from MCU header as well.

Main domain CAN instances are routed to A53 core.

Regards,
Aparna

Hi Aparna,

As per AM62x TRM.. Section 10.1.9 Interrupt Connections for R5FSS, mcan0 Interrupt can be mapped to R5FSS.

is there any other possible way to map MCAN0 Instance to R5 Core?

BR,

Shubham

Hello Team,
Could you please provide your feedback on this?

BR,
Shubham

Hello Team,
Could you please provide your feedback on this.. as this is a blocker for us?

BR,
Shubham

Hello Shubham,

Can we schedule a meeting tomorrow at 3pm for further discussion?

Regards,
Aparna