Hi,
My customer has been evaluating AM6442 SR1.0 GP devices with Linux SDK 08.00.00.12.
Now they have SR2.0 HS-FS devices, so SDK is updated to Linux SDK 08.04.01.04.
Customer found u-boot log is longer with SR2.0.
U-Boot SPL 2021.01-00001-g3b50742757-dirty (Dec 02 2022 - 15:06:05 +0900) EEPROM not available at 80, trying to read at 81 Reading on-board EEPROM at 0x51 failed 1 Resetting on cold boot to workaround ErrataID:i2331 resetting ... U-Boot SPL 2021.01-00001-g3b50742757-dirty (Dec 02 2022 - 15:06:05 +0900) EEPROM not available at 80, trying to read at 81 Reading on-board EEPROM at 0x51 failed 1 SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi') SPL initial stack usage: 13424 bytes Trying to boot from MMC2 Authentication passed Authentication passed Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices Starting ATF on ARM64 core... NOTICE: BL31: v2.7(release):v2.7.0-dirty NOTICE: BL31: Built : 04:31:41, Sep 28 2022 I/TC: I/TC: OP-TEE version: 3.18.0-62-g8e155bae3 (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 Wed Sep 28 04:35:24 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.4.7--v08.04.07 (Jolly Jellyfi') I/TC: HUK Initialized I/TC: Activated SA2UL 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-00001-g3b50742757-dirty (Dec 02 2022 - 15:06:33 +0900) EEPROM not available at 80, trying to read at 81 Reading on-board EEPROM at 0x51 failed 1 SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi') Trying to boot from MMC2 Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices U-Boot 2021.01-00001-g3b50742757-dirty (Dec 02 2022 - 15:06:33 +0900)
U-boot log with SR1.0 was below:
U-Boot SPL 2020.01-g84b608fd34 (Jan 28 2021 - 21:30:52 +0000) SYSFW ABI: 3.1 (firmware rev 0x0014 '20.12.1--v2020.12a (Terrific Ll') Trying to boot from MMC2 Starting ATF on ARM64 core... NOTICE: BL31: v2.4(release):07.02.00.004-dirty NOTICE: BL31: Built : 21:01:30, Jan 28 2021 U-Boot SPL 2020.01-g84b608fd34 (Jan 28 2021 - 21:11:26 +0000) SYSFW ABI: 3.1 (firmware rev 0x0014 '20.12.1--v2020.12a (Terrific Ll') Trying to boot from MMC2 U-Boot 2020.01-g84b608fd34 (Jan 28 2021 - 21:11:26 +0000)
As longer log output directly increases start-up time, the customer wants to minimize log output as less as possible.
Are there any methods to decrease log output with SR2.0?
Thanks and regards,
Koichiro Tashiro
