-
Notifications
You must be signed in to change notification settings - Fork 448
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Showing
2 changed files
with
30 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. | ||
|