I'm sorry, I've initially performed this test on arduino-pico, and I thought I had checked that nothing in there would interfere.
Running my basic testcase now on plain pico SDK 2.1.0 yields the expected results: GPIOn_CTRL not reset and still showing 0x00003305
I still don't get what's resetting my GPIO, but I guess it is not the chip nor the pico SDK at this point.
Running my basic testcase now on plain pico SDK 2.1.0 yields the expected results: GPIOn_CTRL not reset and still showing 0x00003305
I still don't get what's resetting my GPIO, but I guess it is not the chip nor the pico SDK at this point.
Statistics: Posted by kbraden — Sat Dec 14, 2024 7:23 pm