c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.8K
active users

#pico

4 posts4 participants0 posts today

GRAV CMS is off the list for testing, to complicated for me and steady further development seems no where to be seen. 😐

Automad and Kirby are what I'm left off with for now, besides smaller CMS Projects like Pico or Craft and similar, that I will test out as well in time. 😉

I will later update my old license for Kirby v3 to v4 when I'm done building a new Design for my blog with this new CMS as a base. 😃

Replied in thread

@rpimag I did a bit more work on my UART booting Flashless Picos. On the end of each "pico" there's an I2C port for the I/O expander (used to reset/setup the RP2350A to boot from UART) and a UART port to send the bin file/communicate after boot. The Pico2 in the PicoUART6 is running CircuitPython using Adafruit_CircuitPython_PIO_UART for the non-hardware UARTs.

Many people wanted a RESET button on their Pico but I decided to make one without buttons 🤣 .

It currently has no FLASH/PSRAM and boots over UART (3-pin at the bottom) or you can upload a UF2 over USB. The I2C expander towards the bottom (4-pin STEMMA QT) can twiddle the BOOTSEL, SD1 and RUN pins.

Hey fedi #gamedev folks - I'm looking for a framework that will make it fun to write some retro inspired games.

Something like #pico-8 without the restrictions.

I've been looking for something like that for a while (here's some old research: fdisk.quest/dreamengine/), but nothing quite fits the bill. Recently I got the urge to try to finish a silly roguelike I started like 3 times already.

I don't want to learn a full engine, and I'm not smart enough to tackle much outside modern, high-level languages, but I would like to be able to do some fun raster effects down the line.

Any recommendations?

Somewhere in the MIddle East, the cast gathers…

#Ukraine : I want my life back
#Trump : Let’s end this war. Deal me in…
#Ukraine : Yes
#Russia: But first, cut off your arms, legs and ears, and put your eyes out
#Ukraine: What?
#Russia : Oh, and move out of your house, I’m staying here. Then, there will be lasting peace between us.
#US : You’ve got a deal …
#EU : This doesn’t look good… We ought to say something…
#Orban & #Pico (chorus) : #Russia is owed another chance.

When you look at this bad script and see the actors for whom they are you’d quite rightly think that the author needs to go back and do some more scripting practice. Yet this is playing out before our eyes and the consequences are world changing for every one of us no matter where we live.

Remember #GavriloPrincip.
Remember #Kristallnacht
Remember the #YaltaConference

I'm debugging the ROM emulation on the Firestarter. It looks as if the code to monitor ROM enable and ROM selection is working but the host crashes once it starts accessing the ROM.

The first access of the ROM is when BASIC calls KL_INIT_BACK to initialise background ROMs.

The first read is the LD A,(&C000). A few cycles later the ROM's init routine at &C006 will be called.

Continued thread

RIGHT. Fucksake! Arghhh...

I have a solution to this, I do not like my solution to this, but it is a solution...

I reverted my project to use embassy from GitHub again.

I have then grabbed picoserve from GitHub and I have edited the relevant Cargo.toml to use the embassy packages from GitHub.

An in my project Cargo.toml I have referenced my downloaded and modified picoserve instead of using Crates.io... because no matter what I try I cannot make this work using Crates.io packages.

I have now successfully compiled the project modified to use picoserve, loaded it onto the #PicoW, and it runs and serves a "Hello World" via HTTP.

Today I successfully got #Rust code working for a #RaspberryPi #PicoW board! Not bad. All credit goes to the toolchains and projects... my efforts here are purely exploratory / discovery. My current status is I got some Pico / Pico W sample code working and then merged some samples together to form a foundation I'll build more code on top of. The merged code achieves:

  1. DHCP to local network
  2. Listen and respond to TCP
  3. Poke a GPIO (blink)
  4. Logging to USB-TTY

The real TL;DR is: The embassy project seems to be the best starting point for Rust on a Pico W. (Not a Pico 2, this is an older RP2040 board.)

The long version is: yvan.seth.id.au/rusty-pico-w.h

Yvan's Posts · Rusty Pico WGetting Rust working for Pi Pico W