Find your Raspberry Pi Pico W has regular network outages? Here's how to fix that.
Link Actions
The linked article describes the problem I'm having: I have a Pi Pico W programmed in C++ using PlatformIO and after a few hours of inactivity, the WiFi disconnects.
The rest of the program on the Pi Pico W continues to run, I can see it outputting debug statements in the serial link via USB.
I can't use the solution proposed on the linked page because I'm running an http server on the Pi Pico W, intended to receive commands maybe two or three times a day. These are completely asynchronous, so I don't have a way to know when a command is coming so I can get the WiFi connected again.
Is this a known issue? If so is there a solution that will cause the Pi Pico W to keep the WiFi connection active? I need that server running and listening 24 hours a day, 7 days a week, 365 days a year, irrespective of how little traffic is on it.
Hi all. Tho I have this problem a long time, I try to ask here too.
When I use PicoProbe for debug my code with Visual Studio Code (or Codium), can't get serial monitor working on the target Pico.
I have hooked up everything correctly, the probe's Rx/Tx GPIOs are connected to the target's UART0 Tx/Rx correctly (checked it, Tx-Rx and Rx-Tx, swapped it, no data at all. Tried to touch the wires to random spots, garbage appeared on the serial monitor, so the probe is probably listening)
Using USB as UART, connected directly to the target device does give me serial output, but through the probe and with UART, absolutely nothing.
I used the 'hello_serial' example project, built it with Codium (or VSCode), using the same plugins the pico_installer would setup. (MS CMake Tools, MS C++ tools and Cortex debug).
Debugging with openocd, or just running the built firmware on it's own and listening to it with the probe has the same result: nothing.
This should cover every Nintendo game cartridge, but it was made specifically for the Game Boy (DMG/Color/Advance). It currently just counts up the address pins and reads the data, with no defined range to read from.
Next hardware step is designing an adapter to map the pins for each console, and then making a PCB for both.
Next software step is writing cases for each of the memory mappers used in the cartridges... For each console... so only ~50 cases...
I wanted to make this because these universal readers cost ~$150-200 including adapters. Instead, I decided to spend $30 + $1000+ of my time
EasyEDA is a free and easy to use circuit design, circuit simulator and pcb design that runs in your web browser.
Link Actions
Hey all!
Been trying to build a PCB for a strip of neopixels using the RP2040. this is my second attempt at this; I fucked up on my first design, the xtal was wired wrong. i'm a noob at this too. made some changes. before sending this revision to the press, i wanted to ask around for a quick peak. if you see anything i'm missing, or any hints, etc. i'd appreciate.
also first time posting on lemmy. lets see how this thing goes.