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

Fix failing device ID and flash tests #342

Merged
merged 2 commits into from
Jan 20, 2025
Merged

Fix failing device ID and flash tests #342

merged 2 commits into from
Jan 20, 2025

Conversation

PatrickKa
Copy link
Contributor

Fixes #339
Fixes #340

Apparently, semaphores don't yet work correclty in a thread's `init()`
function. Since `HardwareSpi::DoInitialize()` uses one, we must not
initialize SPIs there. Of course, this extends to all peripherals that
use an SPI.
@PatrickKa PatrickKa closed this Jan 20, 2025
@PatrickKa PatrickKa deleted the fram-flash-bugs branch January 20, 2025 15:02
@PatrickKa PatrickKa restored the fram-flash-bugs branch January 20, 2025 15:03
@PatrickKa PatrickKa reopened this Jan 20, 2025
@codecov-commenter
Copy link

codecov-commenter commented Jan 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.98%. Comparing base (c1ffc6b) to head (609214b).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #342   +/-   ##
=======================================
  Coverage   81.98%   81.98%           
=======================================
  Files          49       49           
  Lines        1782     1782           
  Branches       77       77           
=======================================
  Hits         1461     1461           
  Misses        321      321           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

We use the explicit 4-byte address commands anyway so it makes no
difference which mode we are in. Interestingly, status register 3 now
reads 0x41 instead 0x40. According to the datasheet this would mean that
we are now in 4-byte mode and previously were in 3-byte mode. This is
weird and unexpected but errors in datasheets are not unheard of.
@PatrickKa PatrickKa merged commit 2c470fc into master Jan 20, 2025
6 checks passed
@PatrickKa PatrickKa deleted the fram-flash-bugs branch January 20, 2025 16:34
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 this pull request may close these issues.

Flash test reads wrong value for status register 3 Device ID test reads wrong FRAM device ID
2 participants