Bug 1643714 - Raspberry PI 3 B: No way to disable serial I/O during early U-BOOT
Summary: Raspberry PI 3 B: No way to disable serial I/O during early U-BOOT
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: uboot-tools
Version: rawhide
Hardware: armhfp
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-27 18:46 UTC by Gunnar Guðvarðarson
Modified: 2025-03-03 17:29 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:44:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gunnar Guðvarðarson 2018-10-27 18:46:29 UTC
Description of problem:
U-BOOT prompts for "Press any key to stop autoboot", but the serial input pins accept input and some GPS hats send NMEA lines to serial input, stopping autoboot.

Version-Release number of selected component (if applicable):
Fedora-Minimal-armhfp-28-1.1-sda.raw.xz

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora-Minimal-armhfp-28-1.1-sda.raw.xz using fedora-arm-installer
2. Attach a GPS hat like https://learn.adafruit.com/adafruit-ultimate-gps-hat-for-raspberry-pi/pinouts
3. Turn on
4. Observe U-BOOT prompt interuppted with different baud rate garbage
5. Turn off
5. Unplug GPS hat
6. Turn on
7. Observe successful boot

Actual results:
U-BOOT prompt with 9600 baud rate garbage

Expected results:
Boot into Fedora

Additional info:
With google I found that the only way to prevent this is to recompile and install the modified U-BOOT. I have not done so yet since I hope this bug can be fixed.

Comment 1 Peter Robinson 2018-10-28 11:17:13 UTC
Actually a problem with U-Boot upstream

Comment 2 Eric Smith 2019-03-05 11:08:24 UTC
I'm not sure who the appropriate upstream contact would be. It would be nice if some u-boot command or option could be put into a file in the boot partition that would prevent u-boot from listening to the serial port.

Comment 3 Ben Cotton 2019-05-02 19:48:40 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2019-05-28 23:44:51 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Gunnar Guðvarðarson 2019-06-01 17:22:33 UTC
It seems unreasonable to me to deprecate this BR if nothing has changed with how U-Boot is used.

Comment 6 Peter Robinson 2019-06-02 23:11:51 UTC
(In reply to Gunnar Guðvarðarson from comment #5)
> It seems unreasonable to me to deprecate this BR if nothing has changed with
> how U-Boot is used.

It's just an automated process that closes out all old tickets for an EOL release. You could have updated the release at which point it wouldn't have been closed.

Comment 7 Chris Adams 2022-10-11 00:24:53 UTC
This is still a problem with Fedora 36 and Raspberry Pi 4B using uboot 2022.04. I changed the uboot environment variables stdin, stdout, and stderr to remove serial, and also set bootdelay=-2 to autoboot with no delay, yet still serial input (from a GPS HAT) causes uboot to stop.

Comment 8 Tom Shield 2025-03-03 17:29:39 UTC
Still a problem with F41 with a RPi 3B+ with a serial device attached.  U-Boot prompts for keyboard input to boot (and I don't have a keyboard attached).

Package installed is uboot-images-armv8-2024.10-1.fc41.noarch

Trying to use 

bootdelay=-2

(ignore all interrupts) in the u-boot environment does not work.

I have rebuilt u-boot based on the comments here: https://stackoverflow.com/questions/34356844/how-to-disable-serial-consolenon-kernel-in-u-boot
using the latest source from https://github.com/u-boot/u-boot.
and have gotten my 3B+ to boot with serial connected to Makerfocus V3P ups board.  

I did not try building a stock u-boot and adding bootdelay=-2 to its environment, but the above instructions make this the default.


Note You need to log in before you can comment on or make changes to this bug.