Part Number: PROCESSOR-SDK-AM64X
Other Parts Discussed in Thread: SYSCONFIG
MCU SDK: mcu_plus_sdk_am64x_08_05_00_24
Linux SDK: ti-processor-sdk-linux-rt-am64xx-evm-08.06.00.42
Ospi Disk Layout
0x0 - sbl_ospi_linux.tiimage-hs_FS
0x100000 - linux.appimage-hs_FS (built with mcu_plus_sdk_am64x_08_05_00_24/linuxAppimageGen & ti-processor-sdk-linux-rt-am64xx-evm-08.06.00.42 prebuilt-images)
0x300000 - u-boot.img
project sbl_ospi_linux.tiimage-hs_FS:
- I removed code that makes transition to eMMC mode from sbl_ospi_linux project.
- I changed Bootloader offsets with sysconfig which flash_mcu: 0x80000 flash_linux: 0x100000
I am unable to boot my custom board with above configuration
My intent is booting linux.appimage_hs-FS and u-boot from OSPI
But it stuck after SBL
How can I find the problem? (It works with non-custom AM64 GPEVM SR1 with SDK version 08.04)
DMSC Firmware Version 8.5.3--v08.05.03 (Chill Capybar DMSC Firmware revision 0x8 DMSC ABI revision 3.1 [BOOTLOADER_PROFILE] Boot Media : undefined [BOOTLOADER_PROFILE] Boot Image Size : 0 KB [BOOTLOADER_PROFILE] Cores present : m4f0-0 [BOOTLOADER PROFILE] System_init : 26843us [BOOTLOADER PROFILE] Drivers_open : 764668us [BOOTLOADER PROFILE] Board_driversOpen : 0us [BOOTLOADER PROFILE] App_loadImages : 487016us [BOOTLOADER_PROFILE] SBL Total Time Taken : 1438589us Image loading done, switching to application ... Starting linux and RTOS/Baremetal applications

