adafruit-mirror/arduino-pico
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Document E9 non-workaround (#2444)

Browse source 
Fixes #2380
This commit is contained in:
Earle F. Philhower, III 2024-09-12 09:51:24 -07:00 committed by GitHub
parent 76811d3c66
commit 4098ba29af
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 30 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/index.rst
View file

@ -44,6 +44,7 @@ For the latest version, always check https://github.com/earlephilhower/arduino-p
USB (Arduino and Adafruit_TinyUSB) <usb>
Multicore Processing <multicore>
RP2350 Specific Notes <rp2350>
RP2350 PSRAM <psram>
Bluetooth <bluetooth>
@ -72,4 +73,5 @@ For the latest version, always check https://github.com/earlephilhower/arduino-p
Ported/Optimized Libraries <libraries>
Using Pico-SDK <sdk>
Licenses <license>

28
docs/rp2350.rst Normal file
View file

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