Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"ENABLE_UART=0" do not disables console totally #567

Closed
myfreescalewebpage opened this issue Jan 20, 2020 · 4 comments · Fixed by #941
Closed

"ENABLE_UART=0" do not disables console totally #567

myfreescalewebpage opened this issue Jan 20, 2020 · 4 comments · Fixed by #941

Comments

@myfreescalewebpage
Copy link

myfreescalewebpage commented Jan 20, 2020

Description

When setting ENABLE_UART=0 to disable the console on GPIO14/15, the kernel boot log is not shown, but the console is started and the login prompt is displayed. It is possible to login and use the terminal.

Steps to reproduce the issue:

  1. Build with ENABLE_UART=0
  2. Load the raspberry pi (I'm using CM3+)
  3. Open serial console and boot the pi
  4. At the end of the boot the prompt is displayed on the console

Describe the results you received:

The console is available on the UART

Describe the results you expected:

The console should not be available at all on the UART, instead the UART should remain available for other usage

Additional information you deem important (e.g. issue happens only occasionally):

I have solved the issue setting "enable_uart=0" in the "config.txt" file. When ENABLE_UART=0 is set, the config file is just not filled. Instead it should be completed with "enable_uart=0".

Additional details (revisions used, host distro, etc.):

I'm using warrior branch

I can propose à PR if you indicate me on which branch I should do it. master ? How to apply on all branches then ?

@texierp
Copy link
Contributor

texierp commented Jan 20, 2020

Hi @myfreescalewebpage

I can propose à PR if you indicate me on which branch I should do it. master ? How to apply on all branches then ?

This must first be fixed on master and then backported to the specific branch with a new PR (with git cherry-pick -x <commit>)

Example:

Thanks !

@myfreescalewebpage
Copy link
Author

Hi @texierp thanks for the quick answer, will do that!

@myfreescalewebpage
Copy link
Author

myfreescalewebpage commented Jan 20, 2020

PR proposed on master : #568

@lokeb
Copy link

lokeb commented Mar 21, 2021

Has this problem been fixed? I am observing the same problem on RPI-4 on Debian buster arm64.

agherzan added a commit that referenced this issue Nov 13, 2021
Also, validate if the value of it is not 0 or 1.

Fixes: #567

Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
agherzan added a commit that referenced this issue Nov 13, 2021
Also, validate if the value of it is not 0 or 1.

Fixes: #567

Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
agherzan added a commit that referenced this issue Nov 14, 2021
Also, validate if the value of it is not 0 or 1.

Fixes: #567

Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
daregit pushed a commit to daregit/yocto-combined that referenced this issue May 22, 2024
…value of 0

Also, validate if the value of it is not 0 or 1.

Fixes: agherzan/meta-raspberrypi#567

Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
daregit pushed a commit to daregit/yocto-combined that referenced this issue May 22, 2024
…value of 0

Also, validate if the value of it is not 0 or 1.

Fixes: agherzan/meta-raspberrypi#567

Signed-off-by: Andrei Gherzan <andrei@gherzan.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants