Closed adelton closed 5 months ago
It also report:s
Cannot open file config.txt
Cannot open file pieeprom.sig
That's the way the tool works, allowing custom firmware images to be used - see https://github.com/raspberrypi/usbboot/tree/master/msd for a firmware binary with MSD support. It could have included a fixup4.dat file, which would allow the image to adjust for devices with more RAM, but in practice it's not necessary.
I wonder if these should be read when a specific command line parameter is used, not when the files happen to be in the current (?) directory?
We'll consider any submitted PRs, but otherwise this is unlikely to change.
I briefly considered masking "file not found" or moving to a higher verbosity debug level but it's actually quite useful be because it indicates progress from the bootloader so I think NGTF.
Describe the bug
I've built
rpiboot
on my Fedora and was able to use it to boot and enable my Compute Module 4 as USB mass storage (/dev/sda
). However, during the execution, therpiboot
reportedThis file is nowhere to be found in this repository and is it concerning that the tool looks for some "random" file which could possibly change its behaviour.
Steps to reproduce the behaviour
rpiboot
.Device(s)
Raspberry Pi CM4
Compute Module IO board.
PiTray mini 200904857.
RPIBOOT logs
Kernel logs
Device UART logs
No response