• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 101 subscribers
  • Views 331 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TDA4VM: Boot mode supported in Linux SDK and RTOS SDK?

AnBer
Mastermind 29705 points
Part Number: TDA4VM

Team,

-The PDK 7.x docs does list the boot mode supported by the SBL:
https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_02_00_06/exports/docs/pdk_jacinto_07_01_05_14/docs/userguide/jacinto/boot/boot_k3.html#boot-modes
Are there plan to add support for more boot mode in the SBL?

-I saw the below note in the release notes about SBL:
https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_02_00_06/exports/docs/pdk_jacinto_07_01_05_14/docs/userguide/jacinto/release_notes/release_notes_07_01_00.html#sbl
Does it means that the "Optimized Boot flow" (ie with SBL using both R5F-0 and R5F-1 for the further steps of boot flow)  is already implemented in the current SBL?

-Do we have a SDK roadmap available to understand the SW features that will be added over time?

Thanks in advance,

A.

  • 0
    TI__Guru* 77074 points

    Hi A,

    AnBer said:
    -The PDK 7.x docs does list the boot mode supported by the SBL:
    https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_02_00_06/exports/docs/pdk_jacinto_07_01_05_14/docs/userguide/jacinto/boot/boot_k3.html#boot-modes
    Are there plan to add support for more boot mode in the SBL?

    No boot mode can not work with any bootloader as in no boot mode - ROM code doesn't run and hence no image will be directly picked up from the boot media.

    No boot mode can hence only be used with a JTAG where you have some scripts to initialize the SoC.

    AnBer said:
    -I saw the below note in the release notes about SBL:
    https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/07_02_00_06/exports/docs/pdk_jacinto_07_01_05_14/docs/userguide/jacinto/release_notes/release_notes_07_01_00.html#sbl
    Does it means that the "Optimized Boot flow" (ie with SBL using both R5F-0 and R5F-1 for the further steps of boot flow)  is already implemented in the current SBL?

    Can you please elaborate on the Optimized boot flow as booting both R5Fs is supported currently also.

    AnBer said:
    -Do we have a SDK roadmap available to understand the SW features that will be added over time?

    Can you please send me an email? I will share the SDK roadmap over there.

    Regards,

    Karan Saxena

  • 0 in reply to Karan Saxena
    Expert 1251 points

    Hi Karan,

    Karan Saxena said:
    No boot mode can not work with any bootloader as in no boot mode - ROM code doesn't run and hence no image will be directly picked up from the boot media.

    I think the initial question was not about "No Boot Mode", but about wether there are plans to add more boot media than the currently used ones (MMC/SD, eMMC, OSPI, UART), so maybe UFS or something else? 

    For additional clarification: The term boot medium refers to a medium, which as able to hold the corresponding boot files (tiboot3.bin, sysfw.itb, tispl.bin, u-boot.img) and can be accessed during boot?

    Which media can be used to store the Linux Kernel /Root Filesystem?

    Thanks for your help and best regards,

    Felix

  • 0 in reply to felix_123
    TI__Guru* 77074 points

    Hi Felix,

    I think I miss-read that statement then. We currently do not plan to add more boot modes, but UART and OSPI are supported along with MMCSD.

    felix_123 said:
    For additional clarification: The term boot medium refers to a medium, which as able to hold the corresponding boot files (tiboot3.bin, sysfw.itb, tispl.bin, u-boot.img) and can be accessed during boot?

    Yes, this is correct. Essentially the place from where the ROM code can pick the tiboot3.bin.

    NOTE: Here I see you talking about the u-boot, SPL etc.. Which are the Linux bootloader and different from SBL. Just wanted to explicitly mention that so that there is no confusion.

    felix_123 said:
    Which media can be used to store the Linux Kernel /Root Filesystem?

    You can store it in eMMC / SD card or have a NFS (network file system). OSPI will not be enough to hold a full file system.

    Regards,

    Karan

  • 0 in reply to Karan Saxena
    Expert 1251 points

    Hi Karan,

    thanks for your reply. I was explicitly refering to the Linux boot.

    Karan Saxena said:
    but UART and OSPI are supported along with MMCSD.

    So eMMC is not supported as a boot medium?

    Karan Saxena said:
    Essentially the place from where the ROM code can pick the tiboot3.bin

    So for sysfw.itb, tispl,bin and u-boot.img I am not restricted to UART, OSPI or MMC/SD?

    Thanks again for your help and best regards,

    Felix

  • 0 in reply to felix_123
    TI__Guru* 77074 points

    Hi Felix,

    felix_123 said:
    So eMMC is not supported as a boot medium?

    My apologies if I missed mentioning eMMC, eMMC boot is supported. There were a few bootmodes which were broken in the release you mentioned but these are getting fixed in the latest release SDK7.3 coming out next week.

    felix_123 said:
    So for sysfw.itb, tispl,bin and u-boot.img I am not restricted to UART, OSPI or MMC/SD?

    By default we mention need to have these images too in the media where tiboot3.bin is present but I think the bootloader code can be changed to pick them up from another media too. But note this is not there by default.

    Regards,

    Karan