This hypothesis makes sense.An untested hypothesis...
Perhaps the firmware only has the ability to check the power supply connected to the usb-c power connector? Perhaps in the absence of information from that port confirming that the power supply is adequate it acts defensively and asks for user confirmation to proceed? Information from the default console on the dedicated serial 'debug' port might be helpful to confirm this.
The behaviour you describe matches what I see if I attempt to boot from a usb mass storage device with a competent, but 'dumb' (ie. non-PD), 5 volt usb-c power supply.
Have you tried the "I know what I am doing and my dumb PSU is working fine, just boot anyway" entry in /boot/firmware/config.txt?
See Powering Raspberry Pi 5 https://www.raspberrypi.com/documentati ... berry-pi-5 for details.
I followed this post and tried 2 options
1. setting PSU_MAX_CURRENT=5000 in the EEPROM bootloader config
2. setting usb_max_current_enable=1 in /boot/config.txt
without any luck.
Statistics: Posted by huesla — Wed Jan 31, 2024 11:45 am