Andrew Scheller
Andrew Scheller
See also https://github.com/balena-io/etcher/issues?q=is%3Aissue+libgconf
ping @pelwell and @XECDesign - should we be including a newer wifi firmware in the APT repos?
I'm not going to comment on why your code may not be working, but... > Since the pico has its own rtc and time.h does not return the actual time,...
> * Remove `+ 1` on claim bit for second core in `multicore_doorbell_claim()` -- besides being OOB this also seems to just be looking at the wrong bit as it...
This is well beyond my personal level of knowledge, but in case it helps, the sourcecode for the RP2350 bootrom is at https://github.com/raspberrypi/pico-bootrom-rp2350
It was written for RP2350 rather than RP2040, but according to the comments in #2280 , https://github.com/raspberrypi/pico-examples/pull/571 might have some good pointers on how to do GPIO over the QSPI...
Both approaches sound equally plausible to me, but this'll be a decision for @kilograham to make. Note that there are many places in pico-sdk where "mass code duplication" has been...
``` +-+---------------- 1 ---------------- | Exception: src/boards/include/boards/waveshare_rp2350_pizero.h:30 PICO_DEFAULT_UART_TX_PIN is set to 4 which isn't a valid pin for TX on UART 0 +---------------- 2 ---------------- | Exception: src/boards/include/boards/waveshare_rp2350_pizero.h:33 PICO_DEFAULT_UART_RX_PIN is...
> It takes the source and target frequencies in MHz as 16-bit numbers I guess that means you can't overclock the Pico to 66 GHz? :rofl:
See also #2255