PROCESSOR-SDK-AM437X: USB boot issue

Hi,

Is this on TI AM437x EVM or your custom board?

Which version of the Processor SDK do you use?

How do you get the u-boot prompt as in your above post if the USB boot failed?

Does the UART console prints any message when USB boot failed?

Please note that MLO and u-boot.img have to be built with am43xx_evm_usbhost_boot_defconfig when boot from USB device. This defconfig is different from other boot methods, such as MMC boot.

Thanks for your quick support.

Is this on TI AM437x EVM or your custom board? - Custom board

Which version of the Processor SDK do you use? - Currently No SDK available [Compiling with direct U-boot source]

How do you get the u-boot prompt as in your above post if the USB boot failed? For cross verifying usb detection, we tried by booting from NAND flash

Does the UART console prints any message when USB boot failed? From USB boot no prints came.

Please note that MLO and u-boot.img have to be built with am43xx_evm_usbhost_boot_defconfig when boot from USB device. This defconfig is different from other boot methods, such as MMC boot. - Tried with am43xx_evm_usbhost_boot_defconfig, with that we were able to start boot from USB but we are facing the following issue

BOOT LOGS:

Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Nov 15 2018, 20:18:47.
Port /dev/ttyUSB0, 12:21:21

Press CTRL-A Z for help on special keys

                                        
U-Boot SPL 2016.05-00230-g5bf448d-dirty (Nov 21 2019 - 12:07:05)
Trying to boot from USB                 
USB0:   Register 2000440 NbrPorts 2     
Starting the controller                 
USB XHCI 1.00                           
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!      
reading u-boot.img                      
reading u-boot.img

u-boot.img is not been loaded.

Trials:
We have tried by flashing the u-boot.img compiled with  am43xx_evm_ethboot_defconfig  defconfig file

And I could see the u-boot logs in this case (U-bbot image is been loaded)

Issue : It stops at this point. Please provide us inputs to proceed further.

Thanks for your reply.

We tried applying above patches in uboot-ver16( which we are using) ,facing undefined reference issues during compilation and we are trying to sort it out.
Can you please tell us, for USB  boot do we have to add any USB related configuration in spl.c or any other files (except the using usb_defconfig as you said above).

During usb boot,booting fails at this function static int spl_fit_select_fdt(const void *fdt, int images, int *fdt_offsetp)(under common/spl/spl_fit.c) though the 437x-gp-evm device tree is been been enabled (in uboot) 

I tried adding some debug prints under the function,please do find the following logs with debug prints
 
Read name 437x-gp-evm 
spl_fit_select_fdt match failed -- This is the one which is used by us but it  fails

Read name am437x-sk-evm 
spl_fit_select_fdt match failed

Read name am43x-epos-evm 
spl_fit_select_fdt match failed

Read name am437x-idk-evm 

board_fit_config_name_match return value 0

 VVDN spl_fit_select_fdt match failed
No matching DT out of these options:
   <NULL>
   <NULL>
   <NULL>
   <NULL>
spl_load_image_fat: error reading image u-boot.img, err - -2
Error loading from USB device
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board hang() ###

and upon printing the  ti_common_eeprom ep->name from the function( *ep = TI_EEPROM_DATA) am getting junk values as below(debug logs)

ep->name-->  S��.;k�"<[+��H�G��4����#�uK�:I��>��`�/s�3$��U�V1�:�F*Aȅ�
 name_tag-->  AM43__GP

Kindly share your ideas on resolving the issue.

Please do find the defconfig used.

CONFIG_ARM=y
CONFIG_AM43XX=y
CONFIG_TARGET_AM43XX_EVM=y
CONFIG_DM_SERIAL=y
CONFIG_DM_SPI=y
CONFIG_DM_SPI_FLASH=y
CONFIG_DM_GPIO=y
CONFIG_SPL_STACK_R_ADDR=0x82000000
CONFIG_DEFAULT_DEVICE_TREE="am437x-gp-evm"
CONFIG_SPL=y
CONFIG_SPL_STACK_R=y
CONFIG_ISW_ENTRY_ADDR=0x40300350
CONFIG_SYS_EXTRA_OPTIONS="SERIAL1,CONS_INDEX=1,NAND,SPL_USB_HOST_SUPPORT"
CONFIG_HUSH_PARSER=y
CONFIG_CMD_BOOTZ=y
# CONFIG_CMD_IMLS is not set
CONFIG_CMD_ASKENV=y
# CONFIG_CMD_FLASH is not set
CONFIG_CMD_MMC=y
CONFIG_CMD_SF=y
CONFIG_CMD_SPI=y
CONFIG_CMD_I2C=y
CONFIG_CMD_USB=y
CONFIG_CMD_DFU=y
CONFIG_CMD_GPIO=y
# CONFIG_CMD_SETEXPR is not set
CONFIG_CMD_DHCP=y
CONFIG_CMD_MII=y
CONFIG_CMD_PING=y
CONFIG_CMD_EXT2=y
CONFIG_CMD_EXT4=y
CONFIG_CMD_EXT4_WRITE=y
CONFIG_CMD_FAT=y
CONFIG_CMD_FS_GENERIC=y
CONFIG_SPI_FLASH=y
CONFIG_SPI_FLASH_BAR=y
CONFIG_SPI_FLASH_MACRONIX=y
CONFIG_SYS_NS16550=y
CONFIG_TI_QSPI=y
CONFIG_USB=y
CONFIG_USB_DWC3=y
CONFIG_USB_DWC3_GADGET=y
CONFIG_USB_DWC3_OMAP=y
CONFIG_USB_DWC3_PHY_OMAP=y
CONFIG_USB_GADGET=y
CONFIG_OF_CONTROL=y
CONFIG_DM=y
CONFIG_DMA=y
CONFIG_DM_MMC=y
CONFIG_TIMER=y
CONFIG_OMAP_TIMER=y
CONFIG_FIT=y
CONFIG_SPL_OF_LIBFDT=y
CONFIG_SPL_LOAD_FIT=y
CONFIG_OF_LIST="am437x-gp-evm am437x-sk-evm am43x-epos-evm am437x-idk-evm"
CONFIG_USB_GADGET_DOWNLOAD=y
CONFIG_G_DNL_MANUFACTURER="Texas Instruments"
CONFIG_G_DNL_VENDOR_NUM=0x0403
CONFIG_G_DNL_PRODUCT_NUM=0xbd00
CONFIG_OF_LIBFDT=y
CONFIG_CMD_TIME=y

And Upon disabling CONFIG_SPL_LOAD_FIT am facing the following issue(From log I could see uboot.img from usb storage  is been loaded successfully )

usb_read: udev 0

usb_read: dev 0 startblk 6832, blccnt 1 buffer 81fff240
read10: start 6832 blocks 1
COMMAND phase
dev=80a015e0, pipe=c0010203, buffer=81fff1a0, length=31
EP STATE RUNNING.
DATA phase
dev=80a015e0, pipe=c0008283, buffer=81fff240, length=512
EP STATE RUNNING.
STATUS phase
dev=80a015e0, pipe=c0008283, buffer=81fff160, length=13
EP STATE RUNNING.
usb_read: end startblk 6833, blccnt 1 buffer 81fff440
Size: 513496, got: 513496
Jumping to U-Boot
loaded - jumping to U-Boot....image changed  0x808000000

Can you please help us to resolve one among the above two approaches.

HI Bin,

We are using the u-boot version which is been fetched form TI site and this is the u-boot version been used u-boot-2016.05.

Can you please share us the SDK/u-boot version link which resolves USB boot issue as you mentioned in the redirected link(redirected link which has the solution).

Hi,

We are using TI SDK 3.00.00.04 version,can you please help us to find usb boot is possible with this version TI 3.00.00.04 of SDK.