7in QLED screen is a useless info without a link to the product. It's not an official display, so how should anybody know what CCC you have in front of you?Thank you for the detailed explanation earlier. I wanted to share a photo of the current power supply setup I am using (attached). Could you please confirm if there might be any compatibility or stability issues with this setup?made a test as below:Based on that other linked topic, the 900mA thing looks to be a red herring that the Raspberry Pi engineers will need to address.
OP, have you tried a different SD Card or re-imaging? The problem is clear here that the Pi is not detecting the SD card. So unless the SD Card reader is faulty, the problem lies directly with the SD Card itself.
official 27W PSU -> boot diagnostics screen shows 5000mA
official 15W PSU -> boot diagnostics screen shows 3000mA
USB-C PD powerbank with USB-C PD capable cable -> boot diagnostics screen shows 3000mA = that's what the power bank is able to deliver @5V
USB-C PD powerbank with USB-A to USB-C cable -> Pi shows 900mA
But even with this the Pi5 is able to boot from NVMe. It will show warning that non 5A capable PSU is connected and current to peripherals is limited.
So even if that situation is not the 'real root cause' there is something wrong with OP's setup.
@OP: what else is connected to the PI?
have to tried another uSD?
Note: from here https://www.raspberrypi.com/documentati ... hosenpower below command is referred, give belowoutput (powered via USB-A to USBc (Pi5 shows 900mA) and when powered from the USB-C PD power bank (Pi shows 3A)when using official 27W PSU it isCode:
hexdump -C /proc/device-tree/chosen/power/usbpd_power_data_objects00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|00000010 00 00 00 00 00 00 00 00 00 00 00 00 |............|0000001cleave it with you to decode this ...Code:
pi@Pi5-new:~ $ hexdump -C /proc/device-tree/chosen/power/usbpd_power_data_objects00000000 0a 01 91 f4 00 02 d1 2c 00 03 c0 e1 00 04 b0 b4 |.......,........|00000010 00 00 00 00 00 00 00 00 00 00 00 00 |............|0000001c
Additionally, I have a 7-inch QLED screen and a USB connection for serial communication connected to the Raspberry Pi. Do you think these peripherals could contribute to the issue?
Regarding the diagnostic command you mentioned (hexdump -C /proc/device-tree/chosen/power/usbpd_power_data_objects), I currently cannot access the terminal on the Raspberry Pi due to the booting issue. Are there any alternative ways to execute this command or obtain similar diagnostics without terminal access?
Your guidance would be highly appreciated.
I have i.e. This one on hands https://www.waveshare.com/70h-1024600.htm?sku=22684 - which requires min 500mA input current. During power on it will need even more because of the TFT's inrush current.
Don't connect that until you have your boot issue sorted! Use a monitor or a TV for setting up that Pi.
My only comment on that DC/DC board: trashbin! Oh, sorry! Where all grenn -> e-waste
Statistics: Posted by aBUGSworstnightmare — Thu Jan 16, 2025 5:38 pm