• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 161 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.

PROCESSOR-SDK-J721E: J721EXSOMG01EVM

KAMEL GHALGAOUI
Prodigy 210 points
Part Number: PROCESSOR-SDK-J721E

Hello TI Team,

SDK version used: 08_06_01_03

We are trying to start the the BIST Example under the SDL with SBL bootloader:

1- We have generated the app file using the k3ImageGen.sh from output: bist_example_app_r5f_baremetal_debug.appimage.

2- We copied the SBL file into SD Card sbl_mmcsd_img_mcu1_0_release.tiimage and rename it tiboot3.bin.

3- We also copied tifs.bin to the card and the app generated with K3Imagegen and rename it app.

once we boot the J721e from sd card we see that SBL boots and loads tifs but the BIST example doesnt show anything and we receive the following: 

the same happens when we replace BIST example with an app that has already worked with spl bootloader

what are we doing wrong?

could you provide a working example with BIST?

Also when calling K3ImageGen.sh we give the core id 4 as shown in the User Manual. However in case we oped that file we see that the ID4 is an MPU and not the MCU.

Is the documentation under User manual incorrect or the list in K3ImageGen.sh?


Best.

KAMEL.

  • 0
    TI__Mastermind 40966 points

    Hi Kamel,

    Could you trying building the app image using make bist_example in the SDK/sdl/ directory? Then load the bist_example_app_r5f_baremetal_multicore_image.appimage as app in the SD card instead of bist_example_app_r5f_baremetal_debug.appimage.

    Thanks,

    Josiitaa

  • 0 in reply to Josiitaa RL
    Prodigy 210 points

    Hello Josiitaa,

    we successfull start  the BIST  example while using bist_example_app_r5f_baremetal_multicore_image.appimage instead of bist_example_app_r5f_baremetal_debug.appimage with some fails.

    Why bist_example_app_r5f_baremetal_multicore_image.appimage starts and bist_example_app_r5f_baremetal_debug.appimage not ? what's the difference ? 

    Why we got staring failure on some tests ? 

     

    Best. 

    KAMEL.

  • 0 in reply to KAMEL GHALGAOUI
    TI__Mastermind 40966 points

    Hi Kamel,

    KAMEL GHALGAOUI said:
    Why bist_example_app_r5f_baremetal_multicore_image.appimage starts and bist_example_app_r5f_baremetal_debug.appimage not ? what's the difference ? 
    In SDK 8.6 sysfw changed to boot MCU R5F core in non-secure mode. SDL could no longer access the CLEC for configuration of the interrupts needed by few PBIST modules. A C7x app is needed that would boot and clear the secure claim bit so that MCU R5F core could then program the CLEC for it’s needs. The BIST being run from MCU R5F, which is now demoted to non-secure, was not able to run the tests on C7x core. Hence, the multicore appimage is needed.
    I am checking internally regarding the test failure. I will get back to you when I have some updates.
    Thanks,
    Josiitaa