-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cpu/sam0: flashpage write / read cycle produces different results depending on code layout in flash #14929
Labels
Area: cpu
Area: CPU/MCU ports
Platform: ARM
Platform: This PR/issue effects ARM-based platforms
Type: bug
The issue reports a bug / The PR fixes a bug (including spelling errors)
Comments
benpicco
added
Area: cpu
Area: CPU/MCU ports
Type: bug
The issue reports a bug / The PR fixes a bug (including spelling errors)
labels
Sep 2, 2020
I was able to reproduce this issue on SAME54. Good news is SAMLXX are not affected by this bug. Did not test on SAMD21 yet. |
What I tried so far:
So far to no avail. |
This was referenced Oct 16, 2020
aabadie
added
the
Platform: ARM
Platform: This PR/issue effects ARM-based platforms
label
May 20, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: cpu
Area: CPU/MCU ports
Platform: ARM
Platform: This PR/issue effects ARM-based platforms
Type: bug
The issue reports a bug / The PR fixes a bug (including spelling errors)
Description
When using
mtd_write()
/mtd_read()
,0xFF
is read instead of the written buffer.Adding a hexdump after the read / write operation makes the issue go away
Also compiling with
PICOLIBC=1
makes the issue go away. Compiling withTOOLCHAIN=llvm
did make the issue appear on CI for a while.Steps to reproduce the issue
Run
tests/periph_flashpage
onsame54-xpro
Expected results
The test success
Actual results
Versions
RIOT master (f68f19a)
The text was updated successfully, but these errors were encountered: