-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release v0.8 #73
Release v0.8 #73
Conversation
``` devtool modify u-boot devtool finish --force-patch-refresh u-boot /build/../repo ```
In the presence of these "weirdnesses you may want to check on different hardware unit as well. |
@PLangowski I was able to trigger the Sometimes the SD card gets enumerated as mmcblk0, sometimes as mmcblk1. There is a race condition, the SDIO WiFi chip sometimes gets enumerated first as mmc0, and the SD card gets mmc1 then. We do not use WiFi, so we could even remove it (disable in devicetree) as a quick workaround to this issue. https://paste.dasharo.com/?a383dc8cd91aca31#2Mt88gsFh2o1xQcnMw2HMVoPGLBv4122eX5JFxD5hEvQ Let's focus on SPI first here. |
@macpijan The GPIO expander pins have been shifted by 112. I don't know the reason why this happened. Some service tries to export |
752886a
to
26663e1
Compare
Fixed the SPI problem by modifying the RteCtrl config. Now after boot the GPIOs are correctly exported and can be used to control SPI. |
I also disabled the WiFi chip. It seems that we fixed all the problems. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit e3937c9 could use some explanation as well.
Also, it's name is rather long, we do not always need to include the full path.
recipes-kernel/linux/linux-mainline/0010-sun8i-h2-plus-orangepi-zero.dts-disable-mmc1.patch
Show resolved
Hide resolved
recipes-kernel/linux/linux-mainline/0010-sun8i-h2-plus-orangepi-zero.dts-disable-mmc1.patch
Show resolved
Hide resolved
@@ -21,112 +21,112 @@ | |||
"description" : "oc3", | |||
"direction" : "out", | |||
"init_value" : 0, | |||
"sys_gpio" : 404 | |||
"sys_gpio" : 516 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know why this has changed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately I don't know
Signed-off-by: Pawel Langowski <[email protected]>
…assword Signed-off-by: Pawel Langowski <[email protected]>
The GPIO expander pin numbers have recently been shifted by 112. Therefore, the numbers in RteCtrl needed to be adjusted. Signed-off-by: Pawel Langowski <[email protected]>
Signed-off-by: Pawel Langowski <[email protected]>
f26ddf9
to
b089531
Compare
Signed-off-by: Pawel Langowski <[email protected]>
Looks good enough for me to get merged into develop. This thread bother me though: #73 (comment) In the end, we must understand this. |
See: 3mdeb/meta-rte#73 (comment) Needs a proper fix that this script is compatible for all RTE OS versions. This script could go directly to meta-rte - that would ease to keep it in sync. Finally, it should be removed entirely, and replaced with osfv_cli instead. Signed-off-by: Maciej Pijanowski <[email protected]>
@PLangowski @macpijan, which service does it? I have a problem with the homelab setup of RTE, where SPI is not enabled at boot on v0.7.5. I have no idea why it happens, and you seem to have a related discussion in this MR. |
It's |
@macpijan as I'm trying to describe in this Dasharo OSFV thread. For now I just changed |
Merged PRs:
#69
#70
#71 counterpart with adjustments - see 200cf5b
#76