Hi,

SBL from SDK7.3 can load application on mcu1_0. we have tested it with PDK applications, so could you try using SBL for loading autosar example? 

Regards,

Brijesh

HI. Brijesh

I need u-boot. SBL can't start u-boot yet.

Hi gj y,

i think it supports booting uboot, let me check and get back to you.

Regards,

Brijesh

Hi gj y,

In order to boot uboot from SBL, please follow below steps.

1. Generated PDK libraries using "make -s -j4 BOARD=j721e_evm CORE=mcu1_0 BUILD_PROFILE=release pdk_libs"
2. Generate SBL using "make -s -j4 BOARD=j721e_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_mmcsd_img_hlos"
3. Open file "ti-processor-sdk-rtos-j721e-evm-07_03_00_07\pdk_jacinto_07_03_00_29\packages\ti\boot\sbl\tools\combined_appimage\config.mk" file and change below 
   1. HLOS_BOOT to development
   2. HLOS_BIN_PATH to PSDKLA/board-support/prebuilt-images folder
   3. Build uboot from PSDKLA top level folder using "make u-boot"
   4. Add below line, after KERNEL_IMG. It essentially points to A72 SPL. 
      1. SPL_IMG    ?= load_only,$(HLOS_BIN_PATH)/../u-boot_build/a72/spl/u-boot-spl.bin,0x80080000,0x80080000
4. Goto ti-processor-sdk-rtos-j721e-evm-07_03_00_07\pdk_jacinto_07_03_00_29\packages\ti\boot\sbl\tools\combined_appimage\ folder and run "make"
5. Now copy below files in SD Card BOOT partition.
   1. ti-processor-sdk-rtos-j721e-evm-07_03_00_07\pdk_jacinto_07_03_00_29\packages\ti\boot\sbl\binary\j721e_evm\mmcsd\bin\sbl_mmcsd_img_hlos_mcu1_0_release.tiimage as tiboot3.bin
   2. ti-processor-sdk-rtos-j721e-evm-07_03_00_07\pdk_jacinto_07_03_00_29\packages\ti\drv\sciclient\soc\V1\tifs.bin 
   3. ti-processor-sdk-rtos-j721e-evm-07_03_00_07\pdk_jacinto_07_03_00_29\packages\ti\boot\sbl\tools\combined_appimage\bin\j721e_evm\combined.appimage as app

Now reboot the board in SD boot mode and you should uboot prints on main domain uart console.. 

Regards,

Brijesh

If you start SBL from OSPI, SBL starts u-boot. SBL starts AUTOSAR. You only need to change it to build_ PROFILE=release sbl_ ospi_ img_ hlos ？ 

Have you integrated sciserver with the autosar? 

If no, can you follow https://www.ti.com/lit/an/spracy6/spracy6.pdf Application for this integration.

If it is already integrated, you could replace ipc_echo test app ie IMG1 with your autosar image.

Regards,

Brijesh

HI. Brijesh

     Thank you for your support .

    I use OSPI startup mode ,

     sbl is  sbl_cust_img_mcu1_0_release.tiimage

     sbl  boot  enet_nimu_example_mcu1_0_release.appimage.

     enet_nimu_example_mcu1_0_release.appimage   boot   multicore_MCU2_0_MCU2_1_stage1  atf_optee.appimage            tikernelimage_linux.appimage. 

Hi gj y,

Can you us sbl_ospi_img_hlos, instead of cust SBL? OSPI img supports loading of hlos images, cust does not support.

Yes, SBL OSPI HLOS will load ATF and uboot on A72 and then A72 will load Linux kernel image.  

If enet_numu_example has integrated SciServer, you could replace ipc_echo_testb binary in IMG1 with enet_nimu binary and generate app.. 

Regards,

Brijesh

HI. Brijesh 

       sbl_ospi_img_hlos_mcu1_0_release.tiimage  Write to OSPI 0 address .  sbl boot  mcu1-0 boot_app(Write to OSPI 0x100000 address) ,  boot_app can boot ATF appimage and ti-uboot-spl.appimage.

      When I use the combined.appimage generated by ipc_echo_testb_mcu1_0_release_strip  instead of boot_ app.appimage 

      sbl_ospi_img_hlos_mcu1_0_release.tiimage  cannot start ATF and ti-u-boot-spl.appimage.

     Which address should atf.appimage and ti-u-boot-spl.appimage write to OSPI? 

      In OSPI startup mode. ipc_echo_testb_mcu1_0_release_strip instead of boot_app, how do I boot ATF and uboot SPL from SBL?

Hi gj y,

You just need to flash

• sbl_ospi_img_hlos_mcu1_0_release.tiimage at the offset 0x0
• tifs.bin at the offset 0x80000
• app at offset 0x100000
• u-boot.img at the offset 0x280000

In this method, bootapp is really not required. 

Regards,

Brijesh

HI. Brijesh 

• sbl_ospi_img_hlos_mcu1_0_release.tiimage at the offset 0x0
• tifs.bin at the offset 0x80000
• ipc_echo_testb_mcu1_0_release.appimage at offset 0x100000
• u-boot-spl.appimage at the offset 0x280000
• MCU dbug UART only outputs the following log:
• SBL Revision: 01.00.10.00 (Aug 24 2021 - 14:04:50)
  TIFS ver: 21.1.1--v2021.01a (Terrific Lla 

Hi gj y,

Can you please check main domain uart? 

Yes, on mcu domain uart, you will just see print related to SBL and TIFS version. 

Regards,

Brijesh

HI ,Brijesh 

main domain  UART is no problem .

Hi gj y,

Do you mean you are seeing uboot messages on main domain uart?

Then you are able to boot uboot from SBL.

Regards,

Brijesh

Hi gj y,

Are you trying it on EVM? 

Regards,

Brijesh

Hi, Brijesh

    yes,  EVM  used.

Hi gj y,

Can you try attached binaries? Copy them into BOOT sector of the SD card and boot. Also keep mcu and main domain uart open.

/cfs-file/__key/communityserver-discussions-components-files/791/hlos.zip

Regards,

Brijesh

Hi. Brijesh

    Can you try booting u-boot-spl by starting SBL with OSP?

Sure, let me check and get back to you.

Hi,

I am also able to boot Linux from OSPI SBL.

Please use attached binaries and flash them at

1, offset 0 for sbl_ospi_img_hlos_mcu1_0_release.tiimage

2, offset 0x80000 for tifs.bin

3, offset 0x100000 for app

4, offset 0x1500000 for u-image.bin

5, offset 0x3fe0000 for tuning_data.bin

Now switch boot mode to OSPI and boot. You will see Linux booting in few seconds.. 

I would suggest to keep filesystem in the SD card, so create SD card as explained in the PSDKRA and keep it inserted in the board.

/cfs-file/__key/communityserver-discussions-components-files/791/7506.hlos.zip

Regards,

Brijesh