instagram story viewer > #beagleboard

#beagleboard

Posts
OpenClaw vs. a 475-page datasheet: let the robot do the transcribing 🦞🤖 The u-blox SAM-M8Q has been sitting on my bench for months. This little GPS module has a built-in antenna, coin cell backup, speaks both NMEA and UBX binary protocol over UART or I2C. So why isn't it in the shop already? Well, it's mostly cause of the 475-page interfacing datasheet documenting every command, struct, and config register. Hundreds of message types. I got partway through by hand with some Claude Code Sonnet assistance, but ran out of time - plus it was still tedious when babysitting Sonnet. However, now we're living in an Opus + Codex era! So I pointed my Raspberry Pi OpenClaw at it. https://github.com/adafruit/openclaw Here's the setup: Raspberry Pi 5 running OpenClaw, wired to a QT Py RP2040, which talks to the SAM-M8Q. Opus 4.6 reads the datasheet (converted to markdown first by Sonnet 4.6 with 1M context to minimize re-parsing that PDF every session) and builds the implementation plan. I review the plan to make sure it prioritizes the most common commands and reports, and flagged some unessential sections like automotive-assist or RTK-specific. Then Codex is assigned each message implementation task as a sub-agent and writes the actual C code for the Arduino library. Opus suggested using struct-based parsing rather than digging through each uint8_t array; we just memcpy the checksummed message raw bytes onto the matching struct and extract the typed bit fields. We've got four message types done so far. After each message is implemented, Codex also writes a test sketch that will exercise / pretty-print the results of each message, great for self-testing as well as regression testing later. Tonight I'm telling it to keep going while I sleep: code, parse, test against live satellite data, fix failures, commit and push on success, then move on to the next. To me this is a great usage of "agentic" firmware development: there's no creativity in transcribing 84 different structs from a 475-page datasheet. Once the LLMs are done, I can review the PRs as if it were an everyday contributor and even make revision suggestions.
OpenClaw vs. a 475-page datasheet: let the robot do the transcribing 🦞🤖 The u-blox SAM-M8Q has been sitting on my bench for months. This little GPS module has a built-in antenna, coin cell backup, speaks both NMEA and UBX binary protocol over UART or I2C. So why isn't it in the shop already? Well, it's mostly cause of the 475-page interfacing datasheet documenting every command, struct, and config register. Hundreds of message types. I got partway through by hand with some Claude Code Sonnet assistance, but ran out of time - plus it was still tedious when babysitting Sonnet. However, now we're living in an Opus + Codex era! So I pointed my Raspberry Pi OpenClaw at it. https://github.com/adafruit/openclaw Here's the setup: Raspberry Pi 5 running OpenClaw, wired to a QT Py RP2040, which talks to the SAM-M8Q. Opus 4.6 reads the datasheet (converted to markdown first by Sonnet 4.6 with 1M context to minimize re-parsing that PDF every session) and builds the implementation plan. I review the plan to make sure it prioritizes the most common commands and reports, and flagged some unessential sections like automotive-assist or RTK-specific. Then Codex is assigned each message implementation task as a sub-agent and writes the actual C code for the Arduino library. Opus suggested using struct-based parsing rather than digging through each uint8_t array; we just memcpy the checksummed message raw bytes onto the matching struct and extract the typed bit fields. We've got four message types done so far. After each message is implemented, Codex also writes a test sketch that will exercise / pretty-print the results of each message, great for self-testing as well as regression testing later. Tonight I'm telling it to keep going while I sleep: code, parse, test against live satellite data, fix failures, commit and push on success, then move on to the next. To me this is a great usage of "agentic" firmware development: there's no creativity in transcribing 84 different structs from a 475-page datasheet. Once the LLMs are done, I can review the PRs as if it were an everyday contributor and even make revision suggestions.
AI just wrote a working device driver from scratch 🤯 A dev had an old MacBook on FreeBSD with no Wi-Fi driver — so he let AI try. First attempt? Compiled but useless. The fix? Instead of "write me a driver," he had AI study an existing one, create a detailed spec, then generate code from that. Spec-first + multi-agent = actual working driver. The workflow is everything. Full episode: https://youtu.be/ycTg7GnNuCg
AI just wrote a working device driver from scratch 🤯 A dev had an old MacBook on FreeBSD with no Wi-Fi driver — so he let AI try. First attempt? Compiled but useless. The fix? Instead of "write me a driver," he had AI study an existing one, create a detailed spec, then generate code from that. Spec-first + multi-agent = actual working driver. The workflow is everything. Full episode: https://youtu.be/ycTg7GnNuCg
Last-minute notice for the world’s largest embedded conference? No big deal when GitLab’s platform-integrated AI is the ultimate teammate. But don’t take our word for it. Just ask Colleen Lake. 😅 Watch her build a portable device cloud from scratch, including 3 Raspberry Pi 5s, 3 Pico Ws, and a whole lot of zip ties, just in time to prep for her session at Embedded World. Wish her luck in the comments! 👇
Last-minute notice for the world’s largest embedded conference? No big deal when GitLab’s platform-integrated AI is the ultimate teammate. But don’t take our word for it. Just ask Colleen Lake. 😅 Watch her build a portable device cloud from scratch, including 3 Raspberry Pi 5s, 3 Pico Ws, and a whole lot of zip ties, just in time to prep for her session at Embedded World. Wish her luck in the comments! 👇
Got myself a big a$$ add-on for the CYD with Bruce firmware (yeah I need to update this version, I know). This addon contains nRF24, C1101, PN532 NFC/RFID, IR, a dedicated header for GPS, battery control and so on. So now it can do basically everything a Flipper 0 can do, for a quarter of its price. Well that was it for today, until next time! 👋😁 . . . . #cybersecurity #linux #infosec #ubuntu #brucefirmware #marauder #cyd #cheapyellowdisplay #bruce #firmware #termux
Got myself a big a$$ add-on for the CYD with Bruce firmware (yeah I need to update this version, I know). This addon contains nRF24, C1101, PN532 NFC/RFID, IR, a dedicated header for GPS, battery control and so on. So now it can do basically everything a Flipper 0 can do, for a quarter of its price. Well that was it for today, until next time! 👋😁 . . . . #cybersecurity #linux #infosec #ubuntu #brucefirmware #marauder #cyd #cheapyellowdisplay #bruce #firmware #termux
https://github.com/fathyb/carbonyl #terminal #linux #larp #computers #browser
https://github.com/fathyb/carbonyl #terminal #linux #larp #computers #browser
🚀 Meet the uConsole by ClockworkPi — a pocket-sized Linux beast for makers & hackers! 🧠💻 🛠️ Modular. DIY. Customizable. Build it yourself, tweak it your way, and carry a full Linux setup in your hands 🤏 🔐 Cybersecurity on the go Perfect for pen-testing, blue-teaming & Kali Linux labs 🕶️⚡ 🎮 Retro gaming ready Turn downtime into playtime with classic emulation fun 👾 👨‍💻 Code anywhere SSH, Tailscale, Python, dev tools & even small AI models — all in your pocket 🤖⌨️ ⚠️ Good to know: • Assembly required 🧩 • Bring your own 18650 batteries 🔋 • Not a desktop replacement, but insanely flexible 💡 ✨ Built for makers | hackers | Linux lovers This isn’t just a device — it’s a mobile terminal lifestyle 🔥🐧 #uConsole #ClockworkPi #LinuxOnTheGo #CyberSecurity #HackersLife MakersGonnaMake RetroGaming DIYTech PortableLinux
🚀 Meet the uConsole by ClockworkPi — a pocket-sized Linux beast for makers & hackers! 🧠💻 🛠️ Modular. DIY. Customizable. Build it yourself, tweak it your way, and carry a full Linux setup in your hands 🤏 🔐 Cybersecurity on the go Perfect for pen-testing, blue-teaming & Kali Linux labs 🕶️⚡ 🎮 Retro gaming ready Turn downtime into playtime with classic emulation fun 👾 👨‍💻 Code anywhere SSH, Tailscale, Python, dev tools & even small AI models — all in your pocket 🤖⌨️ ⚠️ Good to know: • Assembly required 🧩 • Bring your own 18650 batteries 🔋 • Not a desktop replacement, but insanely flexible 💡 ✨ Built for makers | hackers | Linux lovers This isn’t just a device — it’s a mobile terminal lifestyle 🔥🐧 #uConsole #ClockworkPi #LinuxOnTheGo #CyberSecurity #HackersLife MakersGonnaMake RetroGaming DIYTech PortableLinux
If you write software, you already know how to build systems that survive change. Swap a dependency, update a config, move on. Your app doesn't care. #Robotics hasn't traditionally worked that way — but it should. Change one line of config. New camera. Same code. That's the idea, and it's simpler than it sounds. Full breakdown at the link in bio.
If you write software, you already know how to build systems that survive change. Swap a dependency, update a config, move on. Your app doesn't care. #Robotics hasn't traditionally worked that way — but it should. Change one line of config. New camera. Same code. That's the idea, and it's simpler than it sounds. Full breakdown at the link in bio.
Prototype de Game Bot PHP+ ADB
Prototype de Game Bot PHP+ ADB
What should I do guys? 🤔
What should I do guys? 🤔
Day 13 - Members Module complete crud on both ends #ai #frontent #programminh
Day 13 - Members Module complete crud on both ends #ai #frontent #programminh
“Running 10+ apps on Arch Linux… btw I use Arch 😉⚡ No lag. No mercy. #ArchLinux #LinuxGang #TechReels #NoLag #poweruser
“Running 10+ apps on Arch Linux… btw I use Arch 😉⚡ No lag. No mercy. #ArchLinux #LinuxGang #TechReels #NoLag #poweruser
JWT - full video in my YouTube channel link in my bio. . . . . . #software #youtube
JWT - full video in my YouTube channel link in my bio. . . . . . #software #youtube
back to up