CCS/TDA2SX: early boot late attach run abornal

by the way, I use the vision sdk3.06,not the GLSDK, PSDKLA or Android SDK.The version is below:

Kernel 4.4/u-boot 2016.05

Hi Jason,

There is one issue related to late-attach of DSP2

PSDKLA-5023 : Late attach for DSP2 is not functional

Search for this in the release notes

https://processors.wiki.ti.com/index.php/Processor_SDK_Linux_Automotive_Release_Notes#Known_Issues

but this was with the default ipc firmwares (not with the visionSDK firmwares) on some boards specifically J6Plus or TDA2PX.

The kernel log will show 

[ 13.968910] remoteproc remoteproc3: crash detected in 41000000.dsp: type watchdog
[ 13.976962] remoteproc remoteproc3: handling crash #1 in 41000000.dsp
[ 13.983463] remoteproc remoteproc3: recovering 41000000.dsp

if DSP2 is crashed but in your case DSP2 is not crashed. 

With VisionSDK firmwares issue was never observed if you have followed the VisionSDK linux userGuide.

Are you able to see early capture video on display?

I will close the duplicate thread

https://e2e.ti.com/support/processors/f/791/t/883973

Thanks

Ram

Hi Ram,

       I follow <Vision SDK(v03.06.00)Linux User Guide>chapter 3.4 and 3.5, the run the early_capture_late_weston usecase, I am able to see early capture video on display, but when it prints "Starting kernel ...", and the display is gone.

Hi Ram,

        I don't know why the early-boot-update.sh do the cmd :cp $LINUX_TARGETFS/boot/dra7-evm-infoadas.dtb $BOOT/single-stage-boot.dtb,

but the single-stage-boot.dtb doesn't used by the uboot or MLO it seems when I see the print during uboot loading the dra7-dsp1-fw.lzop,dra7-dsp2-fw.lzop and dra7-ipu2-fw.lzop files.

shall we use the Falcon-Boot mode?because the MLO needs to load the single-stage-boot.dtb?why there is a single-stage-boot.dtb file here?

Hi jason,

early-boot-update.sh scripts removes u-boot.img from the boot partition and copies all lzop firmwares, uImage and single-stage-boot.dtb to boot partition.

This is for falcon mode boot.

 {
 chosen {
 bootargs = "console=ttyO0,115200n8 elevator=noop root=/dev/mmcblk1p2 rw rootwait earlyprintk fixrtc omapdrm.num_crtc=2 consoleblank=0 cma=64M rootf
 };
};

This command is used as the bootArgs from single-stage-boot.dtb. In u-boot source code the dtb file is hardcoded as single-stage-boot.dtb in /include/configs/ti_armv7_common.h

so it expects in same name.

Thanks

Ram

so the earlyboot default running in the falcon mode?Could it run in normal mode, for I need to run u-boot.img to start kernel, not the MLO start kernel directly.

I can't see anything about this(early-boot needs falcon boot mode) in Vision SDK(v03.06.00)Linux User Guide, I just follow chapter3.4&3.5 to run the early_capture_late_weston, it seems default not use the falcon boot mode.Couldn't the early-boot run in normal mode?

what step to valid the the falcon boot mode?I can't see in the use guide chapter3.4&3.5

Hi Jason,

It is not mentioned here in the link 

https://processors.wiki.ti.com/index.php/Early_Boot_and_Late_Attach_in_Linux

somehow I am not able to see the picture.

Early boot means it is always expected to be falcon boot so that it minimizes the initialization time.

Why do you need normal kernel boot with early boot?

we just want to display the Rear view camera within 3s when the board is power-on, so we do the early boot. But we also need to run u-boot.img to modify the bootargs by the uenv.txt sometimes, but the MLO seems can't modify the bootargs when it's running.

so I need to additionally do by http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_U-Boot.html#sd-emmc-or-usb-storage chapter 3.1.1.6.9. Booting from SD/eMMC from SPL (Single stage or Falcon mode)?

Hi Jason,

--- a/board/ti/dra7xx/evm.c
+++ b/board/ti/dra7xx/evm.c
@@ -1279,8 +1279,6 @@ int spl_start_uboot(void)
if (serial_tstc() && serial_getc() == 'c')
return 1;

- if ((get_sysboot_value() & SYSBOOT_TYPE_MASK) == SYSBOOT_TYPE_PROD)
- return 0;

#ifdef CONFIG_SPL_ENV_SUPPORT
env_init();

This change should avoid falcon mode in u-boot.

Can you try?

OK. I will try that. I mean, if I follow useguide chapter3.4&3.5, I need to additionally do by http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_U-Boot.html#sd-emmc-or-usb-storage chapter 3.1.1.6.9. Booting from SD/eMMC from SPL (Single stage or Falcon mode) so it can run earlyboot usecase nornal during the kernel is starting?

Hi Ram,

         I try to do below: 

- if ((get_sysboot_value() & SYSBOOT_TYPE_MASK) == SYSBOOT_TYPE_PROD)
- return 0;

         It didn't work, I do "env default -a;setenv boot_os 0;saveenv;", it can run u-boot.img and read the file "uenv.txt"(being in normal mode), but when it printfs “Starting kernel ...”, the display is gone again, it seems the earlyboot mode's usecase can't run in normal mode?It must be run in falcon mode?

        It seems we need to load the file dra7-evm-infoadas.dtb when the kernel is starting, but the kernel now didn't load it, is it something wrong?

Regards

Jason

Hi Ram,

       I know that, but I need to modify bootargs in real time, for example, the emmc has three partitions:boot, rootfs, rootfsBak.In normal, we start fs from rootfs partition, so the bootargs must be:"console=ttyO0,115200n8 elevator=noop root=/dev/mmcblk0p2 rw rootwait earlyprintk fixrtc omapdrm.num_crtc=2 consoleblank=0 cma=64M rootf;When we need to start the bak partition, so we need to change the bootargs:

console=ttyO0,115200n8 elevator=noop root=/dev/mmcblk0p3 rw rootwait earlyprintk fixrtc omapdrm.num_crtc=2 consoleblank=0 cma=64M rootf;

If then we insert an SD card for driving record, we need to change the bootargs:

console=ttyO0,115200n8 elevator=noop root=/dev/mmcblk1p3 rw rootwait earlyprintk fixrtc omapdrm.num_crtc=2 consoleblank=0 cma=64M rootf;

so sometimes the bootargs must be changed, but we need the earlyboot, so how could I do?

Hi Jason,

Is there an option to keep two dtb files for this ?

Thanks

RamPrasad