Hi Simon, I got what is the 'dm tree' which is a driver model. This command could be done only in uboot stage. but i got the situation in which the initialisation of u-boot has not finished yet as showing in the following picture.
[image: image.png] .i would like to know what is wrong in the initialisation ?
Best Regard, Aubin
On Mon, 29 Aug 2022 at 05:24, momo aubin aubinno@gmail.com wrote:
Hi Simon,
Thanks for your answer.
The script that you are telling it is Env.txt right ?
What is a 'dm tree' ? Please could you provide me more infos about this ?
Thanks for your answer in advance.
On Sat, 27 Aug 2022 at 02:21, Simon Glass sjg@chromium.org wrote:
Hi Aubin,
On Fri, 26 Aug 2022 at 06:41, momo aubin aubinno@gmail.com wrote:
Dear all,
Is there any way that allows us to know that uboot has initialised all
his
peripherals before starting loading kernel ?
The goal of this check is to reset the board in case of bad
initialisation
and choose a different uboot .
Thanks for your answer in advance. Aubin
If there is a failure then it likely results in an error-return code from board_init_f() or board_init_r(). These generally halt U-Boot / cause a reboot. But this only covers the peripherals that U-Boot sets up early, like serial, clocks, pinctrl, MMC, PCI, etc.
U-Boot typically does not init a peripheral unless it is needed for U-Boot.
While U-Boot is running (e.g. a script) it may start up other peripherals (e.g. to read a kernel from USB) and in those cases errors can be handled by the script.
You can use 'dm tree' to see what devices have been probed successfully.
Regards, Simon
