RP2350 Datasheet: Error regarding input enable text in Section 9.10

[norandomtechie]

We're using the RP2350 in our embedded systems course, and we're having students dive into the constituent functions in order to understand the effect of registers on peripherals. A student pointed out a conflict between system behavior and some text in the datasheet.

In Section 9.10: Software examples, there is the following paragraph regarding setting IE and OD bits for GPIO pins under pads_bank0:

By default, all pads come out of reset ready to use, with input enabled and output disable set to 0. Regardless, gpio_set_function in the SDK sets the input enable and clears the output disable to engage the pad’s IO buffers and connect internal signals to the outside world.

However, this is not the case when we reach main. The following is a screenshot of the register values before we execute any line of code in main on an RP2350B, showing that IE is 0 for all pins:

My guess is that either there's a very minor typo and it's supposed to be "enable" instead of "enabled". Is this the case, or are we missing something else entirely?

(Full disclosure - we're using PlatformIO with custom support we added to build code with the Pico SDK, instead of the official Pico-VScode extension. We don't see any behavioral differences between the two, but thought it would be worth mentioning.)

[Wren6991]

Thanks, looks like the text surrounding the software examples was copied from the RP2040 datasheet without updating. The correct description is given in 9.3 Reset state:

9.3. Reset state
At first power up, Bank 0 IOs (GPIOs 0 through 29 in the QFN-60 package, and GPIOs 0 through 47 in the QFN-80
package) assume the following state:
• Output buffer is high-impedance
• Input buffer is disabled
• Pulled low
• Isolation latches are set to latched (Section 9.7)
The pad output disable bit (GPIO0.OD) for each pad is clear at reset, but the IO muxing is reset to the null function,
which ensures that the output buffer is high-impedance.

Should be an easy fix, thank you for reporting.

[norandomtechie]

Thanks for the fast response! I credit @rmgelston for the report.