One Time Programmable memory map incorrect
@timg236 is already working on this.
Since Aug 25, 2026.
Assessment
This issue has not been assessed yet.
Description
Following the white paper for one-time programmable memory, the memory rows for RPi 5/ CM5 are listed as rows 74-84. The documentation page covering OTP in this repo lists rows 77-84 for BCM2712 devices. Recent testing confirms that for the CM5, the rows are 77-84. Additionally, the example in the white paper for programming (page 9) covers RPi4/ CM4 devices only with reference to rows 40-42. As the customer programmable memory rows start at 77 and not 74, the method for row determination is incorrect as described int he white paper.
Additionally, while trying to confirm the correct rows prior to writing to this region, I found a command in the vcio driver linux/drivers/char/broadcom/vcio.c on line 41
0x00030086, /* SET_CUSTOMER_OTP_LOCK */
which looks to be another possible lock command for OTP memory. I did not have the opportunity to test this command as I had already locked the region using the
0x00038021, /* SET_CUSTOMER_OTP */
command listed in the white paper and found it to work as expected. Still, might warrant investigation and clarity if this command has value.
Given that you only get one shot at writing to this region, it would be greatly appreciated if any documentation is highly specific and accurate.
- Dominant language
- Python
- Stars
- 5.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/documentation
-
Pico-SDK use of Red Text on Pure Black Background Strains EyesMay be free again @katshann-raspberry claimed this 100 days ago, and no pull request is open. Openbacklog doxygen
raspberrypi/documentation#4156 · 6 comments · 1 assignee ·
-
GPIO and the 40-pin header: legend embedded in associated image is outdatedMay be free again @stevedavies-rp claimed this 100 days ago, and no pull request is open. Openbacklog diagram
raspberrypi/documentation#4124 · 3 comments · 1 assignee ·
-
Solution: Sync Flash to GS Camera with use of the XVS PIN and an Pico or ArduinoMay be free again @lucyhattersley claimed this 47 days ago, and no pull request is open. Openbacklog camera 📷 tutorial 📘
raspberrypi/documentation#4034 · 9 comments · 1 assignee ·
-
Update needed to "Raspberry Pi Debug Probe" for PICO 2May be free again @katshann-raspberry claimed this 100 days ago, and no pull request is open. Openbacklog restructure rp2040
raspberrypi/documentation#4003 · 10 comments · 1 assignee ·
-
How to change the primary UART of a Raspberry PiMay be free again @katshann-raspberry claimed this 99 days ago, and no pull request is open. Openbacklog documentation troubleshooting
raspberrypi/documentation#3938 · 1 comment · 1 assignee ·
All issues in raspberrypi/documentation
Similar issues
-
integration: media_player
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
home-assistant/core#193344 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
daniel-ospina/tortoise#13607 ·
Maintainers usually reply within 1 day
-
documentation priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day