Cann’t detect HDMI on Cboot start stage, help to analysis
boot_logo_reset_restart_fail.txt (25.8 KB)
I only see hdmi cable not connected. If you want other people to help you analyze your case, maybe you should tell more about your board.
[0002.916] could not find regulator
[0002.939] hdmi cable not connected
[0002.943] is_hdmi_needed: HDMI not connected, returning false
Hi Wayne:
we had connected HDMI to monitor, but the target cann’t detect the HDMI monitor on Cboot start stage, as the log file show, we didn’t know why?
Such info is really not what I need. You are just repeating the same thing.
Please tell us
- Which software version is that?
- Is this custom carrier board or NV devkit?
- Is this pure jetpack or you’ve modified something?
- Why do you only care about “cboot logo”? Do you need display after kernel is up?
- Which software version is that?
R32 , REVISION: 4.2 Jetson Nano Emmc
- Is this custom carrier board or NV devkit?
Our customization board - Is this pure jetpack or you’ve modified something?
not pure jetpack - Why do you only care about “cboot logo”? Do you need display after kernel is up?
it didn’t show cboot logo, it can display after kernel up
not pure jetpack
So what did you change?
we didn’t change cboot about hdmi .so we want to know why?
how cboot to check HDMI?
every your customer will customization ,so it must not pure jetpack, this is not your direction to solve the problem.
Yes, we know that you do the customization and I didn’t say “you can’t do customization”…
I just want to know what did you change so that we can find out why cboot cannot output HDMI…
Cboot uses the same dtb file as kernel side but different partition…
Is all wiring to HDMI exactly the same as the dev kit? Is any part of device tree for HDMI or the i2c (including i2c power rails) used by HDMI different (i2c is used for the monitor to report its capabilities via the DDC wire)?
we will check wire , maybe it is the Monitor’s problem(used ViewSonic Monitor), there is no this problem on other Monitors.
there is no this problem on other Monitors.
Some advice…you can try to tell such info in the beginning when you filed the topic… Keep telling something like “Cann’t detect HDMI on Cboot start stage” really does not help yourself. We have lots of user telling us monitor is not ON, and everyone shares different reasons…
I asked you “what did you change” was to know what was changed in your dtb and how did you flash it to your board. This is to prevent software side issue.
However, if you told us " there is no this problem on other Monitors.", then we can prevent checking the software.
Thus, please share more detail next time. It saves your own time.
Hi WayneWWW:
first ,thank you for your reply. But if you just ask me “what did you change”, I cann’t tell you directly because this is for our team, not just one.
and for “there is no problem on other Monitors” is not o give up the problem, because the monitor had this problem is our customer’s ,so we still to analy this problem.
So we still need your help, even if maybe it is not software side issue.
No matter what, we first check this peculiarity of this monitor .
Thank you again!
and we find it didn’t detect the HDMI just when warm reboot ,if cold reset ,it is ok.
if you just ask me “what did you change”, I cann’t tell you directly because this is for our team, not just one.
To be more precisely, it means the dts and board schematic. Sorry that I used to asking those info to other customers too much so takes this for granted.
Could you dump below logs too?
- The full log of dmesg and bootloader log in warm reboot
- The full log of dmesg and bootloader log in cold reset
cold_reboot_log.txt (78.5 KB) warm_reboot_log.txt (71.2 KB)
Hi,
Could you share the cboot part too? Only dmesg is shown in your log.
warm_reboot_uart_log.txt (26.5 KB)
And could you also provide the cboot log from cold reboot?
cold_reboot_uart_log.txt (21.5 KB)