-
Notifications
You must be signed in to change notification settings - Fork 128
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
no console output after bootconsole disabled. #44
Comments
I can't see the UART initialization in the console log. You should see something like this:
Perhaps the kernel config has changed an no longer has the 16550A UART. You need these config options in the kernel
|
Recently experienced something similar and updating the getty baudrate from 38400 to 115200 solved it for me |
Ahh. This is probably my fault. I removed 8250 UART as it's not on the Unleashed board and we had passed the 3-byte SPI 16MiB threshold. |
Now that we've fixed the 16MiB limit on HiFive Unleashed, there is no need to drop this drive any more. Fixes #44.
Now that we've fixed the 16MiB limit on HiFive Unleashed, there is no need to drop this drive any more. Fixes #44.
Now that we've fixed the 16MiB limit on HiFive Unleashed, there is no need to drop this drive any more. Fixes sifive#44.
Just found that there is no output after bootconsole disabled by kernel.
The text was updated successfully, but these errors were encountered: