Errors and warnings while booting inside cboot

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hello!

We created our own carrier HW for Xavier NX module.
SW Release: 32.6.1

While booting, before kernel, there are a lot of errors and warnings:

[0000.211] E> FAILED: Thermal config
[0000.218] E> FAILED: MEMIO rail config

T-boot:
[0000.378] E> DEVICE_PROD: Invalid value data = 70020000, size = 0.
[0000.384] W> device prod register failed

Cboot:
��WARNING: no registered clock for FMON_NAFLL_CLUSTER1 (id 281)
��clk_set_parent failed for clk i2c2, parent pll_aon (-22)
clk_set_parent failed for clk i2c8, parent pll_aon (-22)
Failed to register PTO counter for id 281
Failed to register PTO counter for id 281
Failed to register PTO counter for id 281
Failed to register PTO counter for id 281

[0001.819] E> DEVICE_PROD: Invalid value data = 0, size = 0.
[0001.824] W> device prod register failed

[0001.857] E> failed to read label property for node 158712: 13
[0001.859] E> failed to read reg property for node 158776: 13
[0001.862] E> failed to read reg property for node 158828: 13
[0001.867] E> failed to read reg property for node 158912: 13

[0001.905] E> I2C: slave not found in slaves.
[0001.906] E> I2C: Could not write 0 bytes to slave: 0x00ae with repeat start true.
[0001.907] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.907] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xae at 0x00000000 via insta
nce 0.
[0001.915] E> eeprom: Failed to read I2C slave device
[0001.920] I> Eeprom read failed 0x3526070d
[0001.925] I> Find /i2c@c240000’s alias i2c1
[0001.928] I> Reading eeprom i2c=1 address=0x50
[0001.933] E> I2C: slave not found in slaves.
[0001.936] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start true.
[0001.944] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.949] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 at 0x00000000 via insta
nce 1.
[0001.959] E> eeprom: Retry to read I2C slave device.
[0001.964] E> I2C: slave not found in slaves.
[0001.968] E> I2C: Could not write 0 bytes to slave: 0x00a0 with repeat start true.
[0001.976] E> I2C_DEV: Failed to send register address 0x00000000.
[0001.981] E> I2C_DEV: Could not read 256 registers of size 1 from slave 0xa0 at 0x00000000 via insta
nce 1.
[0001.991] E> eeprom: Failed to read I2C slave device
[0001.995] I> Eeprom read failed 0x3526070d

[0002.268] E> Error -9 when finding node with path /boot-configuration
[0002.268] E> tegrabl_cbo_parse_info: “boot-configuration” not found in CBO file.

[0011.841] W> WARN: Fail to override “console=none” in commandline

[0011.844] E> tegrabl_linuxboot_add_disp_param, du 0 failed to get display params
[0011.851] E> tegrabl_linuxboot_add_disp_param, du 0 failed to get display params
[0011.858] E> tegrabl_linuxboot_add_disp_param, du 0 failed to get display params

[0011.911] W> MAC addr invalid!
[0011.913] E> Failed to get WIFI MAC address
[0011.918] W> MAC addr invalid!
[0011.920] E> Failed to get Bluetooth MAC address

[0012.152] E> tegrabl_display_clear: display is not initialized
[0012.157] W> Boot logo display failed…

Is it possible to completely get rid of these errors or at least hide them from the system log?
As I understand, this is detection of components that not existed in our system.

3

Hi,

  1. For some early stage of bootloader, you can check the bootloader/t186ref/BCT file and see if any “debug” option in those cfg files and set it to 0. It shall not give you any print. Please be aware that it includes other “normal” print too. We are not able to only hide the error log.

  2. (3) is bpmp log not cboot.

  3. For cboot, you can try to change the debug level to hide the log.

4

Thank you for hint.
What about
[0002.255] E> Error -9 when finding node with path /boot-configuration
[0002.256] E> tegrabl_cbo_parse_info: “boot-configuration” not found in CBO file.
[0002.263] I> Using default boot order
[0002.266] I> boot-dev-order :-
[0002.269] I> 1.sd
[0002.271] I> 2.usb
[0002.273] I> 3.nvme
[0002.275] I> 4.emmc
[0002.277] I> 5.net
And how to change boot order?

5

https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-3251/#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/getting_started.html

→ search cbo.dtb

6

How to change it?
There is no sources for cboot…

7

There is. Check the l4t archive website

8

Sorry, in Release 32.6.1 cboot sources are presented.
I will suppress warn and error messages.
Thank you.

How to edit bpmp log options?

9

Use dtc tool to compile the bpmp dtb back to dts, check the content, there should be some “serial” option, set the port to 0xff and it will not print any bpmp log anymore.

I mean every bpmp log. Not only warning or error.

10

Hi WayneWWW
One more question.

Which device tree is related to the cboot?
I didn’t find sources of device tree inside cboot sources.
Is it external file inside bootloader folder?
What is it name for Xavier NX board?

11

device tree for cboot is same as that one used by kernel. Same file to put to different partition.

1 Like
12

Hi WayneWWW
In bootloader folder I have file bpmp_t194.bin
This is output file of TBoot-BPMP.
But I can’t find sources for it.
Are they exist in public?

13

As I already said, not all bootloader components are open source.

14

Is Microboot1 (MB1) also not open source?

15

The earliest bootloader binary that is open source is cboot. Any bootloader prior to this is not open source.

1 Like
17

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.