• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 834 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DRA726: Early boot late attach

Michel Catudal
Genius 3825 points

Part Number: DRA726

I tried to follow the instructions on



U-Boot 2019.01

Please apply this patch http://processors.wiki.ti.com/index.php/File:0001-u-boot-configs-Enable-configs-for-Early-boot-support.zip on U-boot repository in board-support to enable Early Boot of remoteproc cores.

and rebuild u-boot using the configuration dra7xx_evm_config.

That file doesn't exist

Michel Catudal

ACTIA Corp

  • 0
    TI__Mastermind 30480 points

    Hi Michael,

    Yes , the location is missing for some reason. Please use the patch

    8561.0001-u-boot-configs-Enable-configs-for-Early-boot-support.zip

    Thanks

    Ram

  • 0 in reply to Ramprasad
    Genius 3825 points

    Ram,

    Thank you. I have updated my kernel for it but could not update u-boot without this

    Michel Catudal

    ACTIA Corp

  • 0 in reply to Ramprasad
    Genius 3825 points

    Ram,

    That patch covers the configuration file only.

    In the documentation it says to modify board/ti/dra7xx/lateattach.c which doesn't exist

    Also it says the following, there is no such item in common/spl/spl.c

    For our system I don't want it to try to try to load DSP2 firmware or search for firmware for DSP2 since there is no DSP2

    Do I just add this part or is there some other missing stuff?

    Choosing the cores to early boot

    The array cores_to_boot in the file common/spl/spl.c:board_init_r() controls which cores are loaded by MLO.

    <source lang="c">#ifdef CONFIG_LATE_ATTACH

       u32 cores_to_boot[] = { IPU2, DSP1, DSP2, IPU1 };
    1. endif</source>

    This array can be modified to specify the cores to loaded from MLO and the order in which the cores should be loaded. This is applicable for Uboot 2016.05.

    In case of u-boot 2019.01, MLO will always look for all the four firmwares, if they exist in boot partition, MLO tries to load and configures.

     

    Michel Catudal

    ACTIA Corp

  • 0 in reply to Michel Catudal
    TI__Mastermind 30480 points

    Hi Michael,

    This link on early boot late attach is to demonstrate this with PSDKLA and not visionsdk.

    For visionsdk, you need to apply patches on uboot from

    ti_components/os_tools/linux/kernel/linux-kernel-addon/earlyboot-lateattach-patches/u-boot

    and kernel

    ti_components/os_tools/linux/kernel/linux-kernel-addon/earlyboot-lateattach-patches/kernel

    and rebuild

    and create SD card followed by early-boot-sd script as mentioned in the VisionSDK_ Linux_userguide.

    Ram

  • 0 in reply to Ramprasad
    Genius 3825 points

    Ram,

    My yocto is using the PSDKLA u-boot. I was told that all linux stuff was done with yocto.

    I was looking at using yocto to do my rootfs. When I setup the Vision SDK it downloads an already compiled rootfs.

    I want a custom rootfs, I have several libraries, also I don't want more than can fit on the 4G of emmc.

    Would that work if I just replace the kernel and u-boot in yocto with those of the vision sdk?

    I have a few patches that need to be added to both u-boot and the kernel.

    When I compared both u-boot I didn't see very many differences, the vision one use compressed file for the firmware.

    So if I do have to use the vision sdk, are there any instructions on removing and adding patches for u-boot, kernel

    Removing and adding packages for the rootfs.

    For example the ti wifi keeps my custom wifi from working so I have to remove every trace of it.

    Thanks and stay healthy

    Michel Catudal

    ACTIA Corp

  • 0 in reply to Ramprasad
    Genius 3825 points

    Ram,

    It is a little more complicated than what you are explaining. I did find what I was looking for in the VisionSDK_Linux_UserGuide.pdf

    Reading the whole documents tend to be useful. I missed that part earlier. (Page 16 of 26)

    From what I read, I have to patch yocto and use the kernel and u-boot from that SDK.

    I already have a patched yocto, I will need to check to see if weston and SGX version have to be changed or modified.

    I will then need to customize that SDK a bit more since our board is quite different than the ones supported.

    I already have the ACTIA System M4 package modified to support the DRA726.

    Michel Catudal

    ACTIA Corp