jpm, (edited )
@jpm@aus.social avatar

Hey makers, hackers, and electronics folks of the fediverse, what’s your go-to small cheap dev board that ISN’T an ATmega (too small) or ESP32 (too cursed)? I’m asking because I’m writing a gadget-device framework in Rust, and would like to port it to the most popular dev boards.

odo2063,
@odo2063@chaos.social avatar

@jpm Raspi disqualifise because the company is 💩 🤷

Unixbigot,
@Unixbigot@aus.social avatar

@jpm voted NRF because I use that cpu in my own design dev boards. The RISC-V CH32xxx chips are distracted-boyfriend-meme atm too.

jpm,
@jpm@aus.social avatar

@Unixbigot is there a popular dev board based on these yet? The CH32V003 looks a bit too small for this project I’m working on but the rest look good?

Unixbigot, (edited )
@Unixbigot@aus.social avatar

@jpm not afaik, too early as you say.

ETA: I mean, there /are/ dev boards based on these chips (besides the mfr EVBs) but it’s too early to say which ones if any are “popular”

DamonWakes,
@DamonWakes@mastodon.sdf.org avatar

@jpm It WAS the Pico, but since Raspberry Pi torched their reputation I'll be looking for something else next time.

mitka,

@jpm @DamonWakes what happened?

mitka,

@jpm @DamonWakes oh, hired an ex cop that used it to make spy equipment. FFS, do they not know their customer base and opinions about government surveillance?

DamonWakes,
@DamonWakes@mastodon.sdf.org avatar

@mitka @jpm That's the one. The finicky power requirements and Wi-Fi problems of the Pi 4 haven't done them any favours either, but it's mostly the spy cop thing and their embarrassing response to the resulting criticism.

dmakovec,
@dmakovec@theblower.au avatar

@jpm I am curious as to the nature of this ESP32 curse of which you speak? <eyes a couple of M5 Atoms still in their packaging, begging to be hooked up>

chockg,
@chockg@ioc.exchange avatar

@dmakovec @jpm I also am curious about this said curse

jpm,
@jpm@aus.social avatar

@chockg @dmakovec so the “cursed” aspect of the ESP32 is you’re pretty much locked in to their toolchain and their choice of tools. If you’re ok with the tools they supply, they work fine. The problems come when you need to customise the tools they provide (eg upgrading to GCC 10 to support emojis in identifiers), or roll your own tools (eg using Rust from the ground up), because the documentation is very light on details.

jpm,
@jpm@aus.social avatar

I already know about embedded-hal and friends, the idea is that this will build on top of it, providing more of the application-level features and patterns that normally need to be developed by you every time

https://aus.social/@jpm/111655029820406430

TT_392,
@TT_392@fosstodon.org avatar

@jpm what is a gadget-device framework?

jpm,
@jpm@aus.social avatar

@TT_392 the idea is that this builds on top of embedded-hal, providing a bunch of common functions that all embedded devices expose. Eg a SPI peripheral is connected to a SPI bus, each peripheral has its own GPIO pin that controls NSS, and only a single device on the bus can have their NSS pin asserted at a time. A I2C peripheral is connected to an I2C bus, each peripheral has its own unique I2C device ID, and only a single device can be talking on the bus at a time. A UART has an asynchronous stream of bytes coming in, that you plug into some kind of parsing function that then sends a complete message for further processing.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • rust
  • slotface
  • kavyap
  • thenastyranch
  • everett
  • tacticalgear
  • rosin
  • Durango
  • DreamBathrooms
  • mdbf
  • magazineikmin
  • InstantRegret
  • Youngstown
  • khanakhh
  • ethstaker
  • JUstTest
  • ngwrru68w68
  • cisconetworking
  • modclub
  • normalnudes
  • osvaldo12
  • cubers
  • GTA5RPClips
  • Leos
  • tester
  • megavids
  • provamag3
  • anitta
  • lostlight
  • All magazines