Skip to content

Commit 4098ba2

Browse files
Document E9 non-workaround (#2444)
Fixes #2380
1 parent 76811d3 commit 4098ba2

File tree

2 files changed

+30
-0
lines changed

2 files changed

+30
-0
lines changed

docs/index.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,7 @@ For the latest version, always check https://github.com/earlephilhower/arduino-p
4444
USB (Arduino and Adafruit_TinyUSB) <usb>
4545
Multicore Processing <multicore>
4646

47+
RP2350 Specific Notes <rp2350>
4748
RP2350 PSRAM <psram>
4849

4950
Bluetooth <bluetooth>
@@ -72,4 +73,5 @@ For the latest version, always check https://github.com/earlephilhower/arduino-p
7273
Ported/Optimized Libraries <libraries>
7374
Using Pico-SDK <sdk>
7475

76+
7577
Licenses <license>

docs/rp2350.rst

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
RP2350 Specific Notes
2+
=====================
3+
4+
The RP2350 chip (present on the Raspberry Pi Pico 2 board and many others)
5+
is supported by the core with some minor caveats:
6+
7+
* PSRAM is supported via a new ``pmalloc`` call and ``PSRAM`` variable decorator.
8+
* Both RP2350A and RP2350B (48 GPIOs) are supported.
9+
* Only ARM mode is available. For RISC-V (Hazard3), please use the raw SDK.
10+
* FreeRTOS and OTA are not yet supported.
11+
12+
P2350-E9 Errata ("Increased leakage current on Bank 0 GPIO when pad input is enabled")
13+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
14+
15+
Like all chips, the RP2350-A2 stepping has post-silicon chip errata covering certain
16+
bugs found after the chip was manufactured. Probably the most (in)famous and concerning
17+
is RP2350-E9 which is noted as resulting in "Increased leakage current on Bank 0 GPIO
18+
when pad input is enabled." At a high level, this means that in some cases when an
19+
input pin is being driven by a weak (high impedance) input, it may not read properly.
20+
21+
After discussion with the community and exploration of the issue by many users, this
22+
core has decided not to implement any forced workarounds for this issue. Given the
23+
physical nature of the problem and how no one specific solution is appropriate for
24+
all conditions.
25+
26+
For more information please read the errata yourself and check the Raspberry Pi Forums
27+
for the latest updates.
28+

0 commit comments

Comments
 (0)