layer8.space is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to the 8th Layer of Madness Most topics are related to Linux, Anime, Music, Software and maaaany more PS: BSD is also welcome 😜

Administered by:

Server stats:

279
active users

#lwip

0 posts0 participants0 posts today

Progress of the night: Getting the essentials of the #lwip stack running on the #CH32V208.

Still need to clean it up _a lot_ and build the wrapping library, so it's actually useful.
But seeing lwip run at all is amazing.
(So I don't need to depend on the proprietary, closed source #WCHNET library)

Good night :D

Continued thread

It's still got some issues, but looks like UDP/IP works for the most part. I've done a couple #CoAP requests, so that's cool.

There's a bit of into in the repo but this will need more detail and a larger writeup of the whole project(s), covering
#ESP32 #NetIF <> #ESPNow,
#LwIP over ESPNow
#Linux #TUNTAP <> #ESPNow

And that's all just been groundwork for what I really want to do (recap: CoAP like serverless #MQTT)

git.oit.cloud/morgan/ifnow.git

Oit Cloud Consulting ServicesifnowUserland driver to bind a TUN interface to ESP-Now on a monitor mode WiFi interface.
Continued thread

holy heck! I got #CoAP over #LoRa working! I had expected more issues with packet management, waiting for TX to complete specifically but one again it's 'just worked'. Admittedly with only two devices in a tame environment but still super cool. In addition I found the 223.0.blah broad address wasn't going to work without additional work but turns out CoAP with #LwIP will respond to requests on, 255.255.255.255.

Very happy with progress of getting #CoAP over #ESPNow going. Basically works but is a pile of hack. Single file composed of various bits of #espidf example, driver and test code. So I'm going to spend today rewriting it, as at least 2 distinct components. One will be `esp-netif-now`, binding ESP-Now to #LwIP. The other part would be a more abstract, "what does serverless MQTT look like?". I'll continue posting my stream of conciseness here and if I can figure out audio issues, I'll also stream.

Continued thread

Progress?! The #CoAP client side *is* connecting to the server, and the server *is* responding and I *think* I see the response packet coming back to the client side, but #LwIP just seems to.... stop.

Continued thread

huh, I might actually be a sprinkling of Semephores away from this actually working.

I got #LwIP over #ESPNow working, with basic UDP packets, LwIP seemingly taking care of ARP.

But if I enable the #CoAP server/client everything just seems to go to broadcast, like the increased traffic is breaking something.

Still mostly immobile so I'm still hacking on this. I'm especially excited for this route (using ESP-NETIF) because once I figure it out, it would be trivial to implement over #LoRa

I've been tinkering with this idea of #CoAP over [insert broadcastable media] for a while now.

It started largely with #LoRa but I slid down a #LwIP rabbit hole that derailed that experiment.

I'm now rethinking it in context of my #ESP32 based workshop dust collection remote. I'm trying to achieve faster startup times and connecting to WiFi is by far the biggest bottleneck.

0 / rambling on...

Replied in thread

@cv Everything except and the FatFS library. But i'm going to replace the FAT library with a driver that is able to handle asynchronous I/Os. Network is working super well tho, lwIP is very Zig-compatible.

All apps, kernel and so on is written in pure Zig, and it's very convenient