Linux/TDA2: For the Development Boot Mode

user3378603

Part Number: TDA2

Tool/software: Linux

For the Development Boot Mode

We have learned that TDA's QSPI Development Boot Mode requires the resources of MMC/SD . As the following information:
Only MLO and u-boot.img are stored in QSPI flash memory.
DTB & uImage are stored in MMC/SD boot parition.
The rootfs is mounted from MMC/SD partition 2

Please tell us whether NorFLASH or Nandflash Development Boot Mode also needs to possess MMC/SD resources? Where can I find this information?

If we do not want to use the MMC/SD hardware to store booting-related content, how can we solve it?

over 7 years ago

0 Former Member over 7 years ago

Hi,
Can you please check the following links if you haven't checked it already?

processors.wiki.ti.com/.../Processor_SDK_Linux_Automotive_Software_Developers_Guide
processors.wiki.ti.com/.../Processor_SDK_Linux_Automotive_Software_Developers_Guide
processors.wiki.ti.com/.../Processor_SDK_Linux_Automotive_Software_Developers_Guide
processors.wiki.ti.com/.../Processor_SDK_Linux_Automotive_Software_Developers_Guide

By default in our SDK, we don't support NOR boot mode on TI EVM h/w.

Please refer processors.wiki.ti.com/.../Linux_Core_U-Boot_User's_Guide
Also note that NAND bot mode is currently supported for DRA71x EVM. The Linux software on DRA71x EVM is portable on TDA2Ex EVM.

Let me know if you have any follow-up questions?

Regards,
Somnath

0 user3378603 over 7 years ago in reply to Former Member

Intellectual 1000 points

Hi，

For The Development Boot Mode,
The QSPI Development Boot Mode linked on the following page mentions that boot needs to use MMC/SD. Why can't it all be stored in QSPI?
We use the TDA2S series。If We can't use QSPI storage alone, do you recommend independent storage with NAND flash or NOR flash?

processors.wiki.ti.com/index.php

0 Former Member over 7 years ago in reply to user3378603

Hi,
The main reason why we use the production boot mode is when we need a faster kernel + App boot time.
We get better throughput from a QSPI flash, if the kernel is stored there and also bypass the second stage of the boot process.

However, this requires a bigger flash (bigger cost) depending upon the size of all the binaries you want to store in QSPI and what you want to quick start.

You can store the Linux Fs in eMMC flash. And have your initial binaries (BL+ Kernel + f/w mages) stored in QSPI.
Does that address your question?

Regards,
Somnath

0 user3378603 over 7 years ago in reply to Former Member

Intellectual 1000 points

Our Linux Fs and initial binaries (BL+ Kernel + f/w mages) probably only need less than 30MB capacity, so we think it would be enough to choose a 64MB QSPI FLASH.

In addition, if we use TI's vision library on a SOC like Parking line detection and MOD function, will it take up more resources of FLASH?

0 Shiju Sivasankaran over 7 years ago in reply to user3378603

TI__Genius 13395 points

yes, if you add more libs (like Parking line detection and MOD function) it will increases your firmware size, depends on the the code/data and const used in the libs

Processors

Processors forum

Linux/TDA2: For the Development Boot Mode