One Time Programmable memory map incorrect

Open
#4,319 2 comments 0 reactions 2 assignees View on GitHub

@timg236 is already working on this.

Since Aug 25, 2026.

Assessment

This issue has not been assessed yet.

Description

white paper

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/documentation

All issues in raspberrypi/documentation

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.