• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 125 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-AM57X: SDK 9.03 default image fails to boot

Job Sava
Prodigy 215 points
Part Number: PROCESSOR-SDK-AM57X
Other Parts Discussed in Thread: BEAGLEBOARD-X15

Tool/software:

Hello,

I am currently using the following SDK 9.03 supported platform: AM574x Industrial Development Kit. I flashed a 32 GB sd card with the tisdk-default-image-am57xx-evm.wic.xz image provided here: https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM57X/09.03.06.05

In the logs below show u-boot resetting after failing to find the boot.scr and device tree files.

Fullscreen SDK9_03-AM574x-idk.log Download 
U-Boot SPL 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)
DRA762-GP ES1.0 ABZ package
no pinctrl state for default mode
Firmware loading failed for ipu2
Trying to boot from MMC1
Loading Environment from FAT... no pinctrl state for default mode
*** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Loading Environment from MMC... OK


U-Boot 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)

CPU  : DRA762-GP ES1.0 ABZ package
Model: TI AM5748 IDK
Board: AM574x IDK REV 1.0B
DRAM:  2 GiB
ti_emmc_boardid_get failed -5
Core:  77 devices, 27 uclasses, devicetree: separate
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Loading Environment from MMC... OK
am57x_idk_lcd_detect: Failed to get I2C device 0/56 (ret -121)
Net:
Warning: ethernet@48484000 MAC addresses don't match:
Address in ROM is               b0:7e:11:34:83:ea
Address in environment is       70:ff:76:1c:2e:d7
eth2: ethernet@48484000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
Failed to load 'boot.scr'
This will not be a case any time
This will not be a case any time
574 bytes read in 28 ms (19.5 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc0 ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
This will not be a case any time
This will not be a case any time
7930368 bytes read in 370 ms (20.4 MiB/s)
Failed to load '/boot/am574x-idk.dtb'
This will not be a case any time
This will not be a case any time
Kernel image @ 0x82000000 [ 0x000000 - 0x790200 ]
Working FDT set to 0
FDT and ATAGS support not compiled in

▒esetting ...

I also tried running SDK 6.03's am57xx-evm-linux-06.03.00.106.img.zip image, and it booted to linux without any issues.

Is this something your team has seen before or is able to replicate?

Best regards,

-Job

  • 0
    TI__Mastermind 32295 points

    Job,

    See the following: 

    Failed to load '/boot/am574x-idk.dtb'

    Please make sure you have the correct dtb under the folder mentioned in the rootfs/boot folder.

    -Josue

  • +1 in reply to Josue Zamitiz-Ayala
    Prodigy 215 points

    Hi Josue,

    The default image Ti provides installs the device tree files in /root/boot/dtb. Is there a reason why the am574x-idk doesn't load the device tree files from that location, but other boards like the am57x beagleboard-x15 does. 

    These are the logs for the beagleboard u-boot with xtrace enabled. I used the exact same sd card and software image:

    Fullscreen u-boot-beagleboard.log Download 
    U-Boot SPL 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)
DRA752-GP ES2.0
no pinctrl state for default mode
Firmware loading failed for ipu2
Trying to boot from MMC1
Loading Environment from FAT... no pinctrl state for default mode
*** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Loading Environment from MMC... *** Warning - bad CRC, using default environment



U-Boot 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)

CPU  : DRA752-GP ES2.0
Model: TI AM5728 BeagleBoard-X15 rev C
Board: BeagleBoard X15 REV C.00
DRAM:  2 GiB
ti_emmc_boardid_get failed -5
Core:  70 devices, 24 uclasses, devicetree: separate
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Loading Environment from MMC... *** Warning - bad CRC, using default environment

Net:   eth2: ethernet@48484000
Hit any key to stop autoboot:  0
=> setenv xtrace 1
=> boot
+ boot
+ test 0 -eq 1
+ test 0 -eq 1
+ run findfdt
+ test beagle_x15_revc = omap5_uevm
+ test beagle_x15_revc = dra7xx
+ test beagle_x15_revc = dra72x-revc
+ test beagle_x15_revc = dra72x
+ test beagle_x15_revc = dra71x
+ test beagle_x15_revc = dra76x_acd
+ test beagle_x15_revc = beagle_x15
+ test beagle_x15_revc = beagle_x15_revb1
+ test beagle_x15_revc = beagle_x15_revc
+ setenv fdtfile am57xx-beagle-x15-revc.dtb
+ test beagle_x15_revc = am5729_beagleboneai
+ test beagle_x15_revc = am572x_idk
+ test beagle_x15_revc = am574x_idk
+ test beagle_x15_revc = am57xx_evm
+ test beagle_x15_revc = am57xx_evm_reva3
+ test beagle_x15_revc = am571x_idk
+ test am57xx-beagle-x15-revc.dtb = undefined
+ run finduuid
+ part uuid mmc 0:2 uuid
+ run distro_bootcmd
+ run bootcmd_ti_mmc
+ run get_name_kern
+ test 0 -eq 1
+ setenv bootfile zImage
+ run mmcboot
+ mmc dev 0
switch to partitions #0, OK
mmc0 is current device
+ mmc rescan
+ echo SD/MMC found on device 0
SD/MMC found on device 0
+ run loadimage
+ load mmc 0:2 0x82000000 /boot/zImage
This will not be a case any time
This will not be a case any time
7930368 bytes read in 371 ms (20.4 MiB/s)
+ run args_mmc
+ run finduuid
+ part uuid mmc 0:2 uuid
+ setenv bootargs console=ttyS2,115200n8 root=PARTUUID=5b351111-02 rw rootfstype=ext4 rootwait
+ test 0 -eq 1
+ run mmcloados
+ test try = yes
+ test try = try
+ run loadfdt
+ load mmc 0:2 0x88000000 /boot/dtb/am57xx-beagle-x15-revc.dtb
This will not be a case any time
This will not be a case any time
216847 bytes read in 39 ms (5.3 MiB/s)
+ run get_overlay_mmc
+ fdt address 0x88000000
Working FDT set to 88000000
+ fdt resize 0x100000
+ bootz 0x82000000 - 88000000
This will not be a case any time
This will not be a case any time
Kernel image @ 0x82000000 [ 0x000000 - 0x790200 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 8fec8000, end 8fffffff ... OK
Working FDT set to 8fec8000
ft_fixup_clocks failed for DSP voltage domain: <valid offset/length>

    I copied the am574x-idk.dtb to /root/boot and was able to successfully boot to linux. These are the u-boot logs:

    Fullscreen u-boot-574x-idk.log Download 
    U-Boot SPL 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)
DRA762-GP ES1.0 ABZ package
no pinctrl state for default mode
Firmware loading failed for ipu2
Trying to boot from MMC1
Loading Environment from FAT... no pinctrl state for default mode
*** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Loading Environment from MMC... OK


U-Boot 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)

CPU  : DRA762-GP ES1.0 ABZ package
Model: TI AM5748 IDK
Board: AM574x IDK REV 1.0B
DRAM:  2 GiB
ti_emmc_boardid_get failed -5
Core:  77 devices, 27 uclasses, devicetree: separate
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

Loading Environment from MMC... OK
am57x_idk_lcd_detect: Failed to get I2C device 0/56 (ret -121)
Net:
Warning: ethernet@48484000 MAC addresses don't match:
Address in ROM is               b0:7e:11:34:83:ea
Address in environment is       70:ff:76:1c:2e:d7
eth2: ethernet@48484000
Hit any key to stop autoboot:  0
=> setenv xtrace 1
=> boot
+ boot
+ test 0 -eq 1
+ test 0 -eq 1
+ run findfdt
+ test am574x_idk = omap5_uevm
+ test am574x_idk = dra7xx
+ test am574x_idk = dra72x-revc
+ test am574x_idk = dra72x
+ test am574x_idk = dra71x
+ test am574x_idk = dra71x
+ test am574x_idk = dra76x_acd
+ test am574x_idk = beagle_x15
+ test am574x_idk = beagle_x15_revb1
+ test am574x_idk = beagle_x15_revc
+ test am574x_idk = am5729_beagleboneai
+ test am574x_idk = am572x_idk
+ test am574x_idk = am572x_idk
+ test am574x_idk = am572x_idk
+ test am574x_idk = am574x_idk
+ test no = no
+ setenv fdtfile am574x-idk.dtb
+ test am574x_idk = am574x_idk
+ test no = osd101t2587
+ test am574x_idk = am57xx_evm
+ test am574x_idk = am57xx_evm_reva3
+ test am574x_idk = am571x_idk
+ test am574x_idk = am571x_idk
+ test am574x_idk = am571x_idk
+ test am574x-idk.dtb = undefined
+ run envboot
+ mmc dev 0
switch to partitions #0, OK
mmc0 is current device
+ mmc rescan
+ echo SD/MMC found on device 0
SD/MMC found on device 0
+ run loadbootscript
+ load mmc 0 0x82000000 boot.scr
Failed to load 'boot.scr'
+ run loadbootenv
+ fatload mmc 0 0x82000000 uEnv.txt
This will not be a case any time
This will not be a case any time
574 bytes read in 28 ms (19.5 KiB/s)
+ echo Loaded env from uEnv.txt
Loaded env from uEnv.txt
+ run importbootenv
+ echo Importing environment from mmc0 ...
Importing environment from mmc0 ...
+ env import -t 0x82000000 23e
+ test -n
+ run mmcboot
+ mmc dev 0
switch to partitions #0, OK
mmc0 is current device
+ setenv devnum 0
+ setenv devtype mmc
+ mmc rescan
+ echo SD/MMC found on device 0
SD/MMC found on device 0
+ run loadimage
+ load mmc 0:2 0x82000000 /boot/zImage
This will not be a case any time
This will not be a case any time
7930368 bytes read in 371 ms (20.4 MiB/s)
+ test 0 -eq 1
+ run mmcloados
+ run args_mmc
+ run finduuid
+ part uuid mmc 0:2 uuid
+ setenv bootargs console=ttyS2,115200n8 root=PARTUUID=5b351111-02 rw rootfstype=ext4 rootwait
+ test try = yes
+ test try = try
+ run loadfdt
+ load mmc 0:2 0x88000000 /boot/am574x-idk.dtb
This will not be a case any time
This will not be a case any time
216623 bytes read in 38 ms (5.4 MiB/s)
+ bootz 0x82000000 - 0x88000000
This will not be a case any time
This will not be a case any time
Kernel image @ 0x82000000 [ 0x000000 - 0x790200 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 8ffc8000, end 8ffffe2e ... OK
Working FDT set to 8ffc8000
ft_fixup_clocks failed for DSP voltage domain: <valid offset/length>

    Thank you for the help.

    Best regards

    -Job

  • 0 in reply to Job Sava
    TI__Mastermind 32295 points

    Job,

    Not exactly sure why this happened, but I am glad you were able to get it working.

    -Josue