fix: turn off SPI and the serial login console for the DPi bus - #9
Merged
Merged
Conversation
The DPi computer board uses GPIO7 (SPI0 CE1) as a digital input, so the enabled SPI overlay claimed the pin and GPIO.setup raised "GPIO busy". The board also talks over RS485 on /dev/serial0, which the default serial getty holds open, giving "device reports readiness to read but returned no data (multiple access on port?)". Drop dtparam=spi=on, strip the console= token from cmdline.txt, and mask serial-getty@ttyAMA0 (enable_uart stays, so the UART hardware is still up). Update the smoke test, CI assertions, and README to match.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The DPi computer board uses GPIO7 (SPI0 CE1) as a digital input, so the enabled SPI overlay claimed the pin and GPIO.setup raised "GPIO busy". The board also talks over RS485 on /dev/serial0, which the default serial getty holds open, giving "device reports readiness to read but returned no data (multiple access on port?)".
Drop dtparam=spi=on, strip the console= token from cmdline.txt, and mask serial-getty@ttyAMA0 (enable_uart stays, so the UART hardware is still up). Update the smoke test, CI assertions, and README to match.