• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 408 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.

TDA2SX: uboot: using falcon mode, failed to to boot uImage in ext4

Wenjiang Chen
Prodigy 150 points

Part Number: TDA2SX

Hi,

I use SD card to boot my board. My SD card  has a FAT & an EXT4 filesystem. 

In normal mode, this process is OK: MLO( in FAT)-> u-boot.img(in FAT)->kernel&DTB(in EXT4).

In falcon mode, this process also is OK: MLO(in FAT)->kernel & falcon_args(in FAT).

When the kernel & falcon_args are moved to EXT4, MLO could access falcon_args successfullly, but failed to read uImage.

I followed the source code, found it failed in function read_allocated_block(fs/ext4/ext4_common.c), this function failed to call zmalloc to allocate 4096 Bytes memory.

I have got stuck for a while.

Version of uboot is 2019.01.

  • +1
    TI__Guru**** 171110 points

    Hi,

    Apologies for the delay in answering. Which SDK are you using? Falcon mode from FAT might be the only supported mode.

    Suggest to check the steps in 3.7 VSDK: e2e.ti.com/.../faq-compiler-tda2e-the-steps-to-enable-the-early-boot-late-attach-use-case-in-vision-sdk-3-7-linux 

    - Keerthy

  • 0 in reply to Keerthy J
    Prodigy 150 points

    Hi,

    Thank you for your response!

    I fix my problem by changing value of CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN to 0x1000000.

     I found in source code that the function of ext4 used zalloc but FAT didn't, So I try to change the micro value about malloc, it works when changing CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN.