TDA4VM: Early CAN response can_boot_app_mcu_rtos Linux cannot boot.

Wall-E

Part Number: TDA4VM

Hi,

Follow Karan's suggest. I have tried method 3 Boot App and the CAN application boot up really quickly. It handshake with vichi controller successfully.

But I meet another problem. The linux kernel start up failed. I pasted the log here.

Mcu uart print.

CAN Profile App:Variant - Pre Compile being used !!!
CAN_APP: Successfully Enabled CAN Transceiver MCU MCAN0!!!
CAN_APP: Successfully Enabled CAN Transceiver MCU MCAN1!!!
enter can_receive_task
OSPI flash left configured in Legacy SPI mode.

 OSPI NOR device ID: 0x5b1a, manufacturer ID: 0x2c 
Boot App: Started at 15612 usec
Boot App: Total Num booted cores = 8
Boot App: Booted Core ID #6 at 308723 usecs
Boot App: Booted Core ID #7 at 309000 usecs
Boot App: Booted Core ID #8 at 320999 usecs
Boot App: Booted Core ID #9 at 321274 usecs
Boot App: Booted Core ID #10 at 321601 usecs
Boot App: Booted Core ID #11 at 321921 usecs
Boot App: Booted Core ID #12 at 322360 usecs
Boot App: Booted Core ID #0 at 627022 usecs

MCU Boot Task started at 15611 usecs and finished at 2174588 usecs

Main uart print - /cfs-file/__key/communityserver-discussions-components-files/791/20657.log.txt

The kernel is printing circularly.It seems some conflict with qspi. Please give me some help.

Thanks.

Regards.

over 5 years ago

0 Karan Saxena over 5 years ago

TI__Guru* 77985 points

Hi,

As I suggested in my reply in https://e2e.ti.com/support/processors/f/791/p/937373/3464157#3464157

So you can run an application in 3 ways:

SPL/uboot method: Put the ELF format image in /lib/firmware and then the SPL (for mcu1_0 and mcu2_0 cores) or u-boot (for the rest of the core) will pick that image up and load it.
SBL method: Use the SBL, sysfw and the appimage format to boot the cores. With SBL you can load all core but can NOT boot linux.
Boot App: in this SBL loads boot_app and then boot_app has 2 tasks. In one it runs a CAN applivation and the other task boots linux.

The intention for 3 was to enable early CAN response. But there is a known issue with this in SDK7.0 where the Linux doesn't boot to file system (due to resource conflict with RTOS core). You can see that at http://downloads.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/mcusw/mcal_drv/docs/drv_docs/demo_boot_app_mcu_rtos_top.html#demo_boot_app_mcu_rtos_known_issues

I remember the eMMC boot route, you were not able to get the desired boot time, is this why you went to this method?

Regards,

Karan

0 Wall-E over 5 years ago in reply to Karan Saxena

Expert 1706 points

Hi Karan,

Yep, eMMC boot is too slow to handshake with vehicle controller unit.

So is there a way to solve this known issue ?

PS. I need to use vision_app in Linux.

Thanks.

Regards.

0 Karan Saxena over 5 years ago in reply to Wall-E

TI__Guru* 77985 points

Hi,

This is being worked on but it is a big change of aligning the resources between Linux and RTOS and I'm afraid this will be available only with the next release

SDK7.01 in November. But that being said, I will try to run some experiments, by disabling QSPI from Linux to see if that works.

1. What is the boot time requirement for you? (in ms)

2. Also, have you explored possibility of default boot for linux from OSPI?

Regards,

Karan

0 Wall-E over 5 years ago in reply to Karan Saxena

Expert 1706 points

Hi Karan,

Waiting for your good news.

I got some advise from a local FAE. He said mcusw's memory map is different with vision_apps. That means even Linux can boot up, I am also unable to use vision_apps. So I think disabling qspi in Linux is not a good idea.

Actually I don't know the exact time what I need either. But I can sure early can response boot up time can meet my requirement. I expect the boot time can be same as early can response.

Yes, I'm trying boot Linux from OSP now. But it seems there no documents tell me how to do it. Could you provide some suggest ?

Regards.

0 Karan Saxena over 5 years ago in reply to Wall-E

TI__Guru* 77985 points

Hi,

The memory map can be adjusted based on what gets reserved in the Linux kernel for different cores. This is mentioned in http://downloads.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/psdk_rtos_auto/docs/user_guide/developer_notes_memory_map.html

I looked at https://e2e.ti.com/support/processors/f/791/t/930518 where the same discussion is happening and seems like there is no easy fix to this known issue. I would suggest to wait for SDK7.1 when the fix will officially come. Do you have any concerns on this?

Regards,

Karan

0 Wall-E over 5 years ago in reply to Karan Saxena

Expert 1706 points

Hi Karan,

There's no better way. Waiting for good news.

Regards,

0 Karan Saxena over 5 years ago in reply to Wall-E

TI__Guru* 77985 points

Hi,

So should I close the thread till the SDK is available?

Regards,

Karan

0 Wall-E over 5 years ago in reply to Karan Saxena

Expert 1706 points

Hi Karan,

Sure, if you like.

Regards.

Processors

Processors forum

TDA4VM: Early CAN response can_boot_app_mcu_rtos Linux cannot boot.