Adafruit Successfully Automates Arduino Development Using 'Claude Code' LLM (youtube.com) 7
Adafruit Industries used large language model (LLM) tool Claude Code to streamline hardware development, writes managing director ptorrone.
In a demo video Limor 'Ladyada' Fried compares the LLM's command-line interface to working with the build-automation tool CMake or "a weird cross between IRC and a BBS." The first step was converting a PDF of the hardware's datasheet into text, and Claude Code first displays the appropriate Bash command, while asking "Do you want to proceed?" ("What's nice is that it doesn't make changes, even though it has write access to files in the directory...") Eventually from the data sheet it creates things like an accurate register map, C++ headers, and even license text — and more.
"We are using it to automate parts of the coding and debugging process for an Arduino-compatible Metro Mini board with an OPT 4048 color sensor," writes ptorrone: Using Claude Code's shell access, we can compile, upload, and test code in a semi-automated workflow, allowing the LLM to suggest fixes for errors along the way... While the AI isn't perfect for high-level driver development, it's proving VERY useful for tedious debugging and super-fast iterative improvements, bringing hardware automation closer to ...reality.
In the video Fried describes it like this. "I have a full debugging cycle, where I'm there — I'm like driving the car — but I have this copilot that's telling me where to go..."
"I feel like I'm getting closer to having a semi-automated way of doing driver development."
In a demo video Limor 'Ladyada' Fried compares the LLM's command-line interface to working with the build-automation tool CMake or "a weird cross between IRC and a BBS." The first step was converting a PDF of the hardware's datasheet into text, and Claude Code first displays the appropriate Bash command, while asking "Do you want to proceed?" ("What's nice is that it doesn't make changes, even though it has write access to files in the directory...") Eventually from the data sheet it creates things like an accurate register map, C++ headers, and even license text — and more.
"We are using it to automate parts of the coding and debugging process for an Arduino-compatible Metro Mini board with an OPT 4048 color sensor," writes ptorrone: Using Claude Code's shell access, we can compile, upload, and test code in a semi-automated workflow, allowing the LLM to suggest fixes for errors along the way... While the AI isn't perfect for high-level driver development, it's proving VERY useful for tedious debugging and super-fast iterative improvements, bringing hardware automation closer to ...reality.
In the video Fried describes it like this. "I have a full debugging cycle, where I'm there — I'm like driving the car — but I have this copilot that's telling me where to go..."
"I feel like I'm getting closer to having a semi-automated way of doing driver development."
Until the AI learns that backdoors are usefull (Score:3)
for tethered access to millions of devices to be used for it's own proliferation.
https://hardware.slashdot.org/... [slashdot.org]
wow (Score:1)
It starts with a data sheet and produces header files with register definitions. Even license text! It's a real programmer!
It's nice to find ways to automate tedious tasks, but the constant barrage of bullshit never stops. Creating header files is not what programmers do, it's a thankless task that distracts programmers from doing what programmers do.
Re: (Score:3)
Having done a fair amount of driver development, I can tell you that coming up with a header file that represents a map of a device is something developers definitely do. It is the first step in making a device driver.
It is not much fun. Hours of trying to understand the documentation, probably you will make mistakes. Having an AI that does that for you is a super-excellent benefit. These days the AI might even be able to write some basic code for you that interfaces with the device. All a plus.
Re: (Score:2)
Like human created library code, my concern would be that it is inaccurate. Maybe if you had two AIs, one to write it and one to check the results.
Re: (Score:2)
One would assume the developer using the AI would check its work.
Re: (Score:2)
At which point I'd rather write it myself and have the AI check my work. Checking other people's work is more tedious than writing your own much of the time.
Re: (Score:3)
We disallow doing it professionally (which I support) but I've played extensively with it in personal projects.
It's capable of far more than "producing header files and register definitions".
Sounds like if that's all it does, they've got a ways to go in terms of catching up with what it's being used for by other similar products.
FTS,
Using Claude Code's shell access, we can compile, upload, and test code in a semi-automated workflow, allowing the LLM to suggest fixes for errors along the way... While the AI isn't perfect for high-level driver development, it's proving VERY useful for tedious debugging and super-fast iterative improvements, bringing hardware automation closer to ...reality.
Doesn't sound like what you describe.