• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 102 subscribers
  • Views 446 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: How to load CDD IPC - Demo example with SD-CARD on MCU1_0/MCU1_1 ?

sam verghese
Prodigy 150 points
Part Number: TDA4VM


We are developing a custom application using the CDD IPC demo example provided, on MCU1_0 or MCU1_1.
we are not able to load the firmware onto the particular core, would like to know the steps to be followed to load the firmware onto the MCU cores on the MCU domain of Jacinto 7 EVM.

we tried replacing the DM_BOOT= / path to the new firmware and we ran the build to create tiboot3.bin, tispl.bin and u-boot.img(a_72).

6. Rebuild SPL and u-boot
6.1 cd PSDKLA_INTALL_PATH
6.2 make u-boot-r5_clean
6.3 make u-boot-a72_clean
6.4 make u-boot-r5
6.5 u-boot-a72
6.6 Replace the tiboot3.bin, tispl.bin and u-boot.img in the SD card BOOT/

after which we replaced these files on the SD card, unfortunately, the card doesn't boot up with the new files.

 

  • 0
    Prodigy 150 points

    Hi, 

    we tried the same method of implementation on SDK version 7.3 and 7.2 but resulting in boot failure.

    requesting your assistance in taking this forward. 

  • 0 in reply to sam verghese
    TI__Guru* 80275 points

    Hi Sam,

    What is the size of your MCU1_0 ELF firmware image? Have you stripped your firmware image before combining it into tispl.bin? 

    I am also checking internally if CDD IPC firmware images have been validated with Linux after the SYSFW re-archictecture.

    Would you be able to try the Cdd IPC on a different core other than MCU1_0?

    regards

    Suman

  • 0 in reply to Suman Anna
    Prodigy 150 points

    The stripped xer5f size is 90kb.(ipc_echo_test_mcu3_0_release_strip.xer5f).

    we have pointed to the stripped  version in the make file.
    we are able to run the firmware in other cores like MCU1_0, MCU2_0.

  • 0 in reply to sam verghese
    TI__Guru* 80275 points

    Hi Sam,

    MCU1_0 is a special processor running the DM firmware, and needs to run an SciServer. The CDD IPC firmware for MCU1_0 has not been validated after the SYSFW re-architecture. 

    Please see a related FAQ TDA4VM: MCUSW demo on CAN along side Linux on A72 that allows the MCUSW CAN demo application to run with Linux. See if you can follow the similar steps outlined in that FAQ to run the Cdd IPC example with Linux.  

    regards

    Suman

  • 0 in reply to Suman Anna
    Prodigy 150 points

    Hi Suman,

    We tried following the steps mentioned in the FAQ unfortunately we are facing boot failure without any error logs. 

  • 0 in reply to sam verghese
    TI__Guru* 80275 points

    Hi Sam,

    Did you try the above on 7.3 SDK or the latest SDK? 

    I am checking with the author of that FAQ to see what might have gone wrong and if there are any known quirks.

    regards

    Suman

  • +1 in reply to Suman Anna
    TI__Guru* 75212 points

    Hi Sam,

    -1-

    From the 1st image you have in the post (also attached below), you are pointing to the ipc_echo_test_mcu1_0_release_strip.xer5f.

    At SPL the ATCM of the MCU R5 (MCU1_0) is not enabled and hence you need a special version of the application ipc_echo_testb_mcu1_0_release_strip.xer5f instead.

    -2-

    sam verghese said:
    The stripped xer5f size is 90kb.(ipc_echo_test_mcu3_0_release_strip.xer5f).

    Here you mention the image for mcu3_0, can you confirm what is the image you are running on MCU1_0? Please note the R5F images are not interchangeable, an image built for MCU3_0 will not run on MCU1_0.

    Regards

    Karan

  • +1 in reply to Karan Saxena
    Prodigy 150 points

    Hi Karan,

    1- We have now rebuilt the application using the following make command 

     make -s -j BUILD_PROFILE=release BOARD=j721e_evm CORE=mcu1_0 ipc_echo_testb

    as ipc_echo_testb_mcu1_0_release_strip.xer5f and we are able to load it without issues.


    2- we are trying to run mcu1_0 image on MCU1_0 itself as mentioned in the document. 

    Thank you for the support.