RP2350 5.10.7. OTP bootloader contains wrong OTP row range/data capacity for OTP bootloader

Open Beginner friendly
#478 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Domain
documentation

Research direction

Start by comparing sections 5.10.7 and 13.10, especially the OTP row ranges and capacity statements quoted in the issue. Update the three specified phrases so they match the reserved pages and ECC-protected capacity described in section 13.10, then verify the surrounding documentation remains consistent.

Written by the indexing model from the issue text.

Description

documentation rp2350

5.10.7, says

The entire bootloader will need to fit in the OTP rows from 0x0C0 to 0xF48 to avoid interfering with other reserved OTP
functionality, giving a maximum size of 7440 bytes (2 bytes per ECC row). If some boot keys and OTP keys are unused,
this region can extend slightly on either end.

However, 13.10. Predefined OTP data locations says

Pages 3 through 60 (rows 0x0c0 through 0xf3f) are free for arbitrary user content such as OTP-resident bootloaders, and
Raspberry Pi will avoid allocating any of these locations for bootrom configuration if possible. This is a total of 7424
bytes of ECC-protected content.

...

Pages 0, 1, and 61 through 63 are reserved for future use by Raspberry Pi. Software should avoid allocating content in
these regions, even if they currently have no defined use in this data listing.

Suggest replacing:

  • 0x0C0 to 0xF48 with 0x0C0 through 0xF3F
  • 7440 bytes with 7424 bytes
  • can extend slightly on either end with can extend slightly on the beginning (as row 61 is entirely reserved for future use).
Dominant language
No language data
Stars
35
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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/pico-feedback

All issues in raspberrypi/pico-feedback

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.