sudo ./rpiboot early exit without -d flag #228
Comments
polarbeared
changed the title
martamomotko
added a commit
to martamomotko/usbboot
that referenced
this issue
Jul 5, 2024
rpiboot: Minor code style and spelling fix rpiboot: Update to check if directory exists rpiboot: Moved directory existence check rpiboot: Fixed early exit without -d flag. Fixes raspberrypi#228
martamomotko
added a commit
to martamomotko/usbboot
that referenced
this issue
Jul 5, 2024
rpiboot: Removed directory existence check. Fixes raspberrypi#228 bootfiles: Add error check for file open operation
martamomotko
added a commit
to martamomotko/usbboot
that referenced
this issue
Jul 5, 2024
rpiboot: Removed directory existence check. Fixes raspberrypi#228 bootfiles: Add error check for file open operation
martamomotko
added a commit
to martamomotko/usbboot
that referenced
this issue
Jul 5, 2024
rpiboot: Removed directory existence check. Fixes raspberrypi#228 bootfiles: Add error check for file open operation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
There's an early exit in the main.c when it checks for whether the
-ddirectory flag is present.If a user tries to run the usbboot program to get the raspberry pi into mass storage mode by running
sudo ./rpiboot, directory (flag-d) will be equal to NULL, and the program will exit.Steps to reproduce the behaviour
command:
sudo ./rpibootresult:
RPIBOOT: build-date Jul 4 2024 version 20240422~085300 17b5a351 Waiting for BCM2835/6/7/2711/2712... Directory '(null)' does not existDevice(s)
Raspberry Pi CM4
Compute Module IO board.
No response
RPIBOOT logs
No response
Kernel logs
No response
Device UART logs
No response
The text was updated successfully, but these errors were encountered: