AM625: Probe DSS in uboot

BTW, By studying this:

           https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/10_00_07_04/exports/docs/linux/Foundational_Components/U-Boot/UG-Splash-Screen.html?highlight=splash

My cust has change the DDR and they are using the Serial Nand flash.

           So, some questions:

               Q1. Do they need to change the DDR of this?

                           #DDR address to load image from boot media

                           splashimage=0x80200000

               Q2. Do they need to change the element in this array?

                          static struct splash_location default_splash_locations[] = {

BR RioThanks.

Are there any errors they are getting?

Hi Divyansh:

Here is the cust's log.

#1. They are using 512MBytes DDR4.

#2. There is no error on this address: ==> (loadaddr=0x82000000):

#3. How to fix this?

BR Rio

NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty

NOTICE:  BL31: Built : 04:20:32, Nov  1 2024

U-Boot 2024.04-dirty (Sep 30 2025 - 10:34:51 +0800)

SoC:   AM62X SR1.0 HS-FS

Model: Texas Instruments AM625 SK

EEPROM not available at 0x50, trying to read at 0x51

Reading on-board EEPROM at 0x51 failed -121

DRAM:  475 MiB (effective 512 MiB)

Core:  80 devices, 33 uclasses, devicetree: separate

NAND:  0 MiB

MMC:   mmc@fa00000: 1

Loading Environment from MMC... MMC Device 0 not found

*** Warning - No MMC card found, using default environment

In:    serial

Out:   serial

Err:   serial

EEPROM not available at 0x50, trying to read at 0x51

Reading on-board EEPROM at 0x51 failed -121

Setting bus to 1

0000: 2b 00    +.

0084: 2b 00    +.

00c4: 00 00    ..

0094: 00 00    ..

00d4: bd 90    ..

0084: bd 90    ..

00c4: 52 50    RP

0094: 52 50    RP

00d4: 8e 40    .@

Net:   Could not get PHY for mdio@f00: addr 0

am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed

No ethernet found.

Hit any key to stop autoboot:  0

=> ls mmc 1

   319850   tiboot3.bin

  1249495   tispl.bin

  1310899   u-boot.img

  1311667   u-boot_nand.img

  8358687   uImage.gz

    58030   k3-am625-sk.dtb.img

13397064   rootfs.bin.lzo.img

   131072   uEnv.img

48758784   hmi.ubi

  1966080   boot_bak.ubi

        8   crc.dat

    12285   ti_logo_414x97_32bpp.bmp.gz

   160770   ti_logo_414x97_32bpp.bmp

13 file(s), 0 dir(s)

=> fatload mmc 1 $loadaddr ti_logo_414x97_32bpp.bmp

ERROR: reserving fdt memory region failed (addr=9c800000 size=300000 flags=4)

ERROR: reserving fdt memory region failed (addr=9cb00000 size=100000 flags=4)

ERROR: reserving fdt memory region failed (addr=9cc00000 size=e00000 flags=4)

160770 (0x13B) bytes read in 46 ms (3.3 MiB/s)

=> bmp display $loadaddr m m

=>

This is another log after tunning on this config ==> CONFIG_VIDEO_TIDSS

And the "bmp display $loadaddr m m will cause the system reset.

開啟CONFIG_VIDEO_TIDSS後，bmp display $loadaddr m m會reset，

但是在uboot下dm tree，video和panel是沒有probe的。

video         0  [   ]   tidss_drv             |   |-- dss@30200000

pinctrl       2  [   ]   single-pinctrl        |   `-- pinctrl@a40000

pinconfig    18  [   ]   pinconfig             |       `-- cpsw-cpts

clk           1  [   ]   fixed_factor_clock    |-- clock-divider-oldi

nop           0  [ + ]   gpio_led_wrap         |-- leds

led           0  [ + ]   gpio_led              |   |-- led-0

led           1  [ + ]   gpio_led              |   `-- bl_en

clk           2  [   ]   fixed_clock           |-- clk-0

regulator     0  [   ]   regulator_fixed       |-- regulator-0

regulator     1  [   ]   regulator_fixed       |-- regulator-1

regulator     2  [   ]   regulator_fixed       |-- regulator-2

regulator     3  [   ]   regulator_fixed       |-- regulator-3

regulator     4  [   ]   gpio regulator        |-- regulator-4

regulator     5  [   ]   regulator_fixed       |-- regulator-5

panel         0  [   ]   simple_panel          |-- panel-lvds

LOG:

U-Boot 2024.04-dirty (Sep 30 2025 - 11:21:43 +0800)

SoC:   AM62X SR1.0 HS-FS

Model: Texas Instruments AM625 SK

EEPROM not available at 0x50, trying to read at 0x51

Reading on-board EEPROM at 0x51 failed -121

DRAM:  475 MiB (effective 512 MiB)

Core:  81 devices, 34 uclasses, devicetree: separate

NAND:  0 MiB

MMC:   mmc@fa00000: 1

Loading Environment from MMC... MMC Device 0 not found

*** Warning - No MMC card found, using default environment

In:    serial

Out:   serial

Err:   serial

EEPROM not available at 0x50, trying to read at 0x51

Reading on-board EEPROM at 0x51 failed -121

Setting bus to 1

0000: 2b 40    +@

0084: 2b 40    +@

00c4: 00 d0    ..

0094: 00 d0    ..

00d4: bd 70    .p

0084: bd 70    .p

00c4: 52 c0    R.

0094: 52 c0    R.

00d4: 91 10    ..

Net:   Could not get PHY for mdio@f00: addr 0

am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed

No ethernet found.

Hit any key to stop autoboot:  0

=> ls mmc 1

   319850   tiboot3.bin

  1249495   tispl.bin

  1316219   u-boot.img

  1316995   u-boot_nand.img

  8358687   uImage.gz

    58030   k3-am625-sk.dtb.img

13397057   rootfs.bin.lzo.img

   131072   uEnv.img

48758784   hmi.ubi

  1966080   boot_bak.ubi

        8   crc.dat

   160770   ti_logo_414x97_32bpp.bmp

12 file(s), 0 dir(s)

=> fatload mmc 1 $loadaddr ti_logo_414x97_32bpp.bmp

ERROR: reserving fdt memory region failed (addr=9c800000 size=300000 flags=4)

ERROR: reserving fdt memory region failed (addr=9cb00000 size=100000 flags=4)

ERROR: reserving fdt memory region failed (addr=9cc00000 size=e00000 flags=4)

160770 (0x13B) bytes read in 47 ms (3.3 MiB/s)

=> bmp display $loadaddr m m

"Synchronous Abort" handler, esr 0x96000044, far 0xffffffffff700000

elr: 000000008087d87c lr : 000000008087d818 (reloc)

elr: 000000009da3487c lr : 000000009da34818

x0 : 000000009b9b1c60 x1 : ffffffffff700000

x2 : fffffffffffca000 x3 : 0000000000000000

x4 : 0000000000000000 x5 : 000000009b9b1c60

x6 : 0000000000000000 x7 : 000000000000000a

x8 : 0000000000002a74 x9 : 000000009b98375c

x10: 0000000000000003 x11: 0000000000002a34

x12: 0000000000000000 x13: 000000009b984540

x14: 00000000ffffffff x15: 000000009b983a68

x16: 000000009da348ac x17: 0000000000000000

x18: 000000009b996d80 x19: 0000000000000000

x20: 000000009b99a2a0 x21: 000000009b99a340

x22: 000000009b983a50 x23: 0000000000000005

x24: 000000009dae8da4 x25: 0000000000000000

x26: 0000000000000000 x27: 0000000000000000

x28: 000000009b9ad340 x29: 000000009b9839f0

Code: f9401001 8b020022 eb02003f 54fffec2 (b8004433)

Resetting CPU ...

resetting ...

This E2E is related? plz confirm.

My cust is using 10.1 SDK.

Hi Rio,
The U-Boot you are using has a 'dirty' tag implying there are custom changes. can you share the U-Boot diff? 
Also, I expect the default loadaddr to be 0x82000000 and not 0x80200000.
You may be trying to overwrite over existing data. Please use 0x82000000 as the loadaddr.

Hi Divy:

Cust has tried, plz see the below log.

1 key info is:

      Cust wants to probe the TI_DSS, but nothing of DSS can be probed.

Any comments?

BR Rio

=> ls mmc 1

   319718   tiboot3.bin

  1249363   tispl.bin

  1316563   u-boot.img

  1317339   u-boot_nand.img

  8359052   uImage.gz

    58018   k3-am625-sk.dtb.img

13397103   rootfs.bin.lzo.img

   131072   uEnv.img

48758784   hmi.ubi

  1966080   boot_bak.ubi

        8   crc.dat

    76216   recive_uart

    76216   recive_uart_flow

    83983   mp.log

   160770   ti_logo_414x97_32bpp.bmp

15 file(s), 0 dir(s)

=> fatload mmc 1 0x82000000 ti_logo_414x97_32bpp

Failed to load 'ti_logo_414x97_32bpp'

=> NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty

NOTICE:  BL31: Built : 04:20:32, Nov  1 2024

In:    serial

Out:   serial

Err:   serial

EEPROM not available at 0x50, trying to read at 0x51

Reading on-board EEPROM at 0x51 failed -121

Setting bus to 1

0000: 2b 20    +

0084: 2b 20    +

00c4: 00 90    ..

0094: 00 90    ..

00d4: be d0    ..

0084: be d0    ..

00c4: 52 90    R.

0094: 52 90    R.

00d4: 8f a0    ..

Net:   Could not get PHY for mdio@f00: addr 0

am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed

No ethernet found.

Hit any key to stop autoboot:  0

=> ls mmc 1

   319718   tiboot3.bin

  1249363   tispl.bin

  1316563   u-boot.img

  1317339   u-boot_nand.img

  8359052   uImage.gz

    58018   k3-am625-sk.dtb.img

13397103   rootfs.bin.lzo.img

   131072   uEnv.img

48758784   hmi.ubi

  1966080   boot_bak.ubi

        8   crc.dat

    76216   recive_uart

    76216   recive_uart_flow

    83983   mp.log

   160770   ti_logo_414x97_32bpp.bmp

15 file(s), 0 dir(s)

=> fatload mmc 1 0x82000000 ti_logo_414x97_32bpp.bmp

ERROR: reserving fdt memory region failed (addr=9c800000 size=300000 flags=4)

ERROR: reserving fdt memory region failed (addr=9cb00000 size=100000 flags=4)

ERROR: reserving fdt memory region failed (addr=9cc00000 size=e00000 flags=4)

160770 (0x13B) bytes read in 41 ms (3.7 MiB/s)

=>  bmp display 0x82000000 m m

"Synchronous Abort" handler, esr 0x96000044, far 0xffffffffff700000

elr: 000000008087db88 lr : 000000008087db24 (reloc)

elr: 000000009da34b88 lr : 000000009da34b24

x0 : 000000009ba750c0 x1 : ffffffffff700000

x2 : fffffffffffca000 x3 : 0000000000000000

x4 : 0000000000000000 x5 : 000000009ba750c0

x6 : 0000000000000000 x7 : 000000000000000a

x8 : 0000000000002a68 x9 : 000000009b98392c

x10: 0000000000000003 x11: 0000000000002a28

x12: 0000000000000000 x13: 000000009b984840

x14: 00000000ffffffff x15: 000000009b983c38

x16: 000000009da34bb8 x17: 0000000000000000

x18: 000000009b996d80 x19: 0000000000000000

x20: 000000009b99a2a0 x21: 000000009b99a340

x22: 000000009b983c20 x23: 0000000000000005

x24: 000000009dae90e4 x25: 0000000000000000

x26: 0000000000000000 x27: 0000000000000000

x28: 000000009ba8de40 x29: 000000009b983bc0

Code: f9401001 8b020022 eb02003f 54fffec2 (b8004433)

Resetting CPU ...

resetting ...

Please share your uboot diff. This is not the behaviour in default U-Boot provided by TI and I am not able to reproduce your issue at my end.
Also, please use code block to post your console logs.

Hi Divy:

Yes, I know, I'm waiting my cust to reply the diff, plz wait.

BR Rio

Hi Diya:

   #1. Plz note: Customer only patch for the Serial Nand Flash boot.

   #2. Cust cannot share their diff.

   #3. How about I ask them to share the Map file of uboot, and you to look up the "LR" register to trace the code?

BR Rio

Hi,

Rio Chan said:

There is no error on this address: ==> (loadaddr=0x82000000):

Since these are custom changes unsharable for the customer, it becomes difficult for us to support this.
Also, I remember you mentioning that loadaddr=0x82000000 showed no errors, then why in your later posts are they seeing errors again? Clearly there has been some diff to their uboot modifications and you may ask them to revert those.

Hi Divy:

1 question:

 When you in the uboot, can you probe the TI DSS?

 If yes, can you share us your log + Uboot config? (Both.)

Thanks.

BR Rio

Hi,

U-Boot SPL 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')
SPL initial stack usage: 17056 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.11.0(release):v2.11.0-906-g58b25570c9-dirty
NOTICE:  BL31: Built : 04:20:32, Nov  1 2024

U-Boot SPL 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.1.8--v10.01.08 (Fiery Fox)')
SPL initial stack usage: 1904 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2024.04-ti-g29d0c23d67ee (Nov 29 2024 - 11:41:54 +0000)

SoC:   AM62PX SR1.0 HS-FS
Model: Texas Instruments AM62P5 SK
DRAM:  2 GiB (effective 8 GiB)
Core:  85 devices, 31 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Warning: ethernet@8000000port@2 (eth1) using random MAC address - 1a:bf:be:d8:c8:39
, eth1: ethernet@8000000port@2
Hit any key to stop autoboot:  0
=> printenv loadaddr
loadaddr=0x82000000
=> fatload mmc 1 $loadaddr ti_logo_414x97_32bpp.bmp
160770 bytes read in 16 ms (9.6 MiB/s)
=>

Hi Divyansh:

The cust is concerning why this lead to crash:

BR Rio

=>  bmp display 0x82000000 m m

"Synchronous Abort" handler, esr 0x96000044, far 0xffffffffff700000

elr: 000000008087db88 lr : 000000008087db24 (reloc)

elr: 000000009da34b88 lr : 000000009da34b24

x0 : 000000009ba750c0 x1 : ffffffffff700000

x2 : fffffffffffca000 x3 : 0000000000000000

x4 : 0000000000000000 x5 : 000000009ba750c0

x6 : 0000000000000000 x7 : 000000000000000a

x8 : 0000000000002a68 x9 : 000000009b98392c

x10: 0000000000000003 x11: 0000000000002a28

x12: 0000000000000000 x13: 000000009b984840

x14: 00000000ffffffff x15: 000000009b983c38

x16: 000000009da34bb8 x17: 0000000000000000

x18: 000000009b996d80 x19: 0000000000000000

x20: 000000009b99a2a0 x21: 000000009b99a340

x22: 000000009b983c20 x23: 0000000000000005

x24: 000000009dae90e4 x25: 0000000000000000

x26: 0000000000000000 x27: 0000000000000000

x28: 000000009ba8de40 x29: 000000009b983bc0

Code: f9401001 8b020022 eb02003f 54fffec2 (b8004433)

Resetting CPU ...

Hi Rio,
Since we do not have customer's diff, there is not much we can help here. You may ask them to use CCS or some debugger to debug U-Boot, this is all we can do to help without knowing the changes.