-
Notifications
You must be signed in to change notification settings - Fork 582
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
Update Raspberry Pi samples suggesting modifying config.txt settings #2297
Comments
When was that change made and where is it documented? I set up a version of bookworm about a month ago and there everything was thr same as before. |
I looked at it and can confirm the change. The only change appears to be the place of the file, though. Also, there's a file in the original place that contains the information to look in the new place - people should be able to understand that. |
[Triage] If you are willing to adjust the documentation in the repository, feel free. In that case, please make sure you are clear about the fact that depending on the OS version, it's one or the other. The params should be already good on what we've been checking. We ❤️ PR so looking forward to reviewing it 😉 |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. |
[Triage] on top of docs we need to update Board class config reading logic as part of this |
The latest available version of Raspberry Pi OS (Bookworm) has changed the location of the config.txt file where you can enable the SPI hardware interface. It used to be in
/boot/config.txt
, and now it is located in/boot/firmware/config.txt
. Also, the setting went through different names, but the latest name isdtparam=spi=on
.Some of the sample docs still have the old instructions and need updating. For example, the nRF24L01 sample: https://github.com/dotnet/iot/blob/main/src/devices/README.md#important
The text was updated successfully, but these errors were encountered: