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

Original question:

TDA4VM: QSPI booting for device part number IS25WP256 from ISSI

TDA4VM: address_in_ram

Huang Jian
Intellectual 770 points
Part Number: TDA4VM

Hi,

I have  seen the FAQ - e2e.ti.com/.../950919 to load remote core firmware from OSPI.I try to load R5F firmwares  MCU1_0 and MCU2_0.But I don't know what address_in_ram should be in "sf read <address_in_ram> <offset_in_flash> <length_in_bytes_to_be_copied>".Can you help me solve it?

Regards!

HJ

  • 0
    TI__Guru* 77754 points

    Hi HJ,

    You can mention any DDR address which you are not using.

    A safe option would be 0x90000000.

    rproc init
rproc load <core_id> 0x90000000 0x${length_in_bytes_to_be_copied}
rproc start <core_id>

    Regards,

    Karan

  • 0 in reply to Karan Saxena
    Intellectual 770 points

    Hi Karan ,

    I load R5F firmwares  MCU1_0 and MCU2_0 from OSPI and test it with an application named my_app_linux_arm.But the application run incorrectly and I will post the log below.Can you help me solve it?

    Regards!

    HJ

    1643.boot_log.txt

  • 0 in reply to Huang Jian
    TI__Guru* 77754 points

    Hi HJ,

    Please see https://e2e.ti.com/support/processors/f/791/t/915474 , this tell you what are the differences and care abouts when loading firmware from R5 SPL and A72 u-boot.

    By default the MCU1_0 and MCU2_0 (core 0s of the R5 Subsystems) are loaded by R5 SPL and hence they have a different memory map. Using the same firmwares you can not load them using u-boot. Reason (as mentioned in the pointed FAQ) is that in u-boot ATCM is enabled and hence you need to boot from ATCM. (this is a R5F specification).

    So default MCU1_0 and MCU2_0 firmwares can not be directly loaded from OSPI flash (as we are loading them via u-boot.

    I would suggest that you try to load SDK firmware for MCU2_1 from OSPI using u-boot first.

    Please try two things, to get the first things right:

    1. Please make sure that from the flash when you are reading the firmware, you are reading the exact size of the firmware (here you use 0x50000 for both firmwares, please make sure that is correct).

    2. The firmwares which are not being loaded from SD card, rename them in the rootfs/lib/firmware. Keeping then in /lib/firmware will trigger their load from R5 SPL or u-boot.

    Regards,

    Karan