• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 328 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.

SK-AM62B-P1: Building the U-Boot and Booting it on the GP device from SD card

Mallika Vignesh
Prodigy 110 points

Part Number: SK-AM62B-P1

Hi Team,

We have customized the board taking SK-AM62B-P1 as a reference and here are the schematics of the custom board.
optilink_1_build2_sch.pdf 

We used GP SOC on the board, so we have used the default SD Image from 08.05 version and we have encountered this on Console when board is trying to Boot.

 

U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 11:53:21 +0000)

SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')

SPL initial stack usage: 13424 bytes

Trying to boot from MMC2

Warning: Detected image signing certificate on GP device. Skipping certificate t                                             o prevent boot failure. This will fail if the image was also encrypted

Warning: Detected image signing certificate on GP device. Skipping certificate t                                             o prevent boot failure. This will fail if the image was also encrypted

Loading Environment from MMC... *** Warning - No MMC card found, using default e                                             nvironment

 

Starting ATF on ARM64 core...

 

NOTICE:  BL31: v2.7(release):v2.7.0-359-g1309c6c805-dirty

NOTICE:  BL31: Built : 11:48:12, Dec 14 2022

I/TC:

I/TC: OP-TEE version: 3.19.0-15-gd6c5d0037 (gcc version 9.2.1 20191025 (GNU Tool                                             chain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Wed Dec 14 11:5                                             2:03 UTC 2022 aarch64

I/TC: WARNING: This OP-TEE configuration might be insecure!

I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/                                             porting_guidelines.html

I/TC: Primary CPU initializing

I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')

I/TC: HUK Initialized

I/TC: Activated SA2UL device

I/TC: Fixing SA2UL firewall owner for GP device

I/TC: Enabled firewalls for SA2UL TRNG device

I/TC: SA2UL TRNG initialized

I/TC: SA2UL Drivers initialized

I/TC: Primary CPU switching to normal world boot

 

U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 11:52:19 +0000)

SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')

Trying to boot from MMC2

i2c_write: error waiting for data ACK (status=0x116)

pca953x gpio@22: Error reading output register

spl: mmc init failed with error: -70

SPL: failed to boot from all boot devices

### ERROR ### Please RESET the board ###


On discussion with below thread I made the chnages accrodingly and tried to make the SD Boot but there is no Console output when I have followed the Specified Steps.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1611523/sk-am62b-p1-am62x-custom-board-pmic-power-ok-sd-card-inserted-with-image-no-uart-or-peripheral-activity/6244811


On our Custom board we have unpopulated this one:

I have disabled the acknowledgemnt and tried to build bootloader files.
This has been seen on Console:

U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 11:53:21 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

## No elf image at address 0x89000000
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.7(release):v2.7.0-359-g1309c6c805-dirty
NOTICE:  BL31: Built : 11:48:12, Dec 14 2022
I/TC: 
I/TC: OP-TEE version: 3.19.0-15-gd6c5d0037 (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2014
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot




We are stuck at Board bring-Up and Need some infowith Custom Boot Loader generation.
Looking forward for assistance.

Regards,
Mallika


  • 0
    TI__Guru* 90301 points

    Hello,

    Mallika Vignesh said:
    I have disabled the acknowledgemnt and tried to build bootloader files.
    This has been seen on Console:

    Do you mean you build the U-Boot and saw those logs? If yes, the logs don't look like they are coming from your built U-Boot as evident by the timestamp (U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 11:53:21 +0000)) in the logs.

    For now, I would recommend building the default U-Boot without any modifications and confirm if you are able to boot it successfully. To confirm if you are booting your built U-Boot, check the timestamp in the logs.

    Thanks!

  • 0 in reply to Prashant Shivhare
    Prodigy 110 points

    hi Prashanth,

    On the suggestion, I have used the Default Image from 08.05 which is 

    tisdk-default-image-am62xx-evm.wic.xz

    and when I keep the Boot pins in SD Boot Mode, I have seen this on console:

    U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 11:53:21 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
    SPL initial stack usage: 13424 bytes
    Trying to boot from MMC2
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Loading Environment from MMC... *** Warning - No MMC card found, using default environment

    Starting ATF on ARM64 core...

    NOTICE: BL31: v2.7(release):v2.7.0-359-g1309c6c805-dirty
    NOTICE: BL31: Built : 11:48:12, Dec 14 2022
    I/TC:
    I/TC: OP-TEE version: 3.19.0-15-gd6c5d0037 (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Wed Dec 14 11:52:03 UTC 2022 aarch64
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
    I/TC: Primary CPU initializing
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
    I/TC: HUK Initialized
    I/TC: Activated SA2UL device
    I/TC: Fixing SA2UL firewall owner for GP device
    I/TC: Enabled firewalls for SA2UL TRNG device
    I/TC: SA2UL TRNG initialized
    I/TC: SA2UL Drivers initialized
    I/TC: Primary CPU switching to normal world boot

    U-Boot SPL 2021.01-g3983bffabc (Dec 14 2022 - 11:52:19 +0000)
    SYSFW ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
    Trying to boot from MMC2
    i2c_write: error waiting for data ACK (status=0x116)
    pca953x gpio@22: Error reading output register
    spl: mmc init failed with error: -70
    SPL: failed to boot from all boot devices
    ### ERROR ### Please RESET the board ###



    Regards,
    Mallika

  • 0 in reply to Mallika Vignesh
    TI__Guru* 90301 points

    Hi Mallika,

    Mallika Vignesh said:

    I have used the Default Image from 08.05 which is 

    tisdk-default-image-am62xx-evm.wic.xz

    I already shared the patch for this issue with the default images.

    I am suggesting to build the U-Boot from source and boot the generated images. Once you have a working bootable setup, you can apply the patch and repeat the same steps.