Can AI program the Picocomputer?

[rumbledethumps]

Yes it can. It even read the documentation and figured out how to use graphics.

pong.mp4

The slop: main.c

I've been testing the documentation that I recently updated by having AI write various things that are only possible by reading the datasheets. It's full of bugs and I wouldn't want to maintain code like this, but the docs are clearly good enough. A real human editor would be better for this, but asking folks to contribute to the documentation of an open source project is like asking them to gouge out their own eyeballs with a rusty spork.

[netzerohero]

The pong-code isn't very readable - but wow! I'm awestruck... Amazing how far these areas (6502 to multicore-ARMS w/SW replacing glue-HW, modern IDEs & SW-tooling, now merging w/ today's AI) have progressed; and all available in this project you've kicked-off! The steps of how you went about this would IMHO make for an interesting video or wiki-page.

With regard to folks contributing to documentation...I dunno...that may actually be interesting... a way to test and improve one's own understanding by improving documentation while providing the community example through different approaches and perspectives.

[netzerohero]

Thanks for your response. I just watched your YouTube video on this. Fascinating! - Thank you for posting and in taking your time to share in such a matter. I'm sure I'll be watching it a few times as a reference into this new realm. I'm intrigued to see how this merging of a code-assistant AI can blend in pushing a constrained-resource system like the 6502 of the past into producing effective results only limited to the imagination (now expanding w/ AI). IMHO that was the fun years ago. Your SBC HW/SW project is expanding to a demonstrative eco-system - like the hobbyist driven SBC-trainers back then. (And I cannot help to notice a repeating theme, now as a prompt to the AI: Read-the-Documentation!).

[rumbledethumps]

The biggest text on the PCB is a link to the documentation. And it's there twice!

[vruumllc]

Wow, I hadn't noticed you posted a couple new videos!
I'm very glad to see them -- your videos are always so enjoyable, and are the ultimate advertisement for a truly excellent platform.
You might want to add the new ones to your RP6502 playlist.
Thanks, as always, for sharing your efforts!

[rumbledethumps]

I think you were asking for file management APIs. There in there too.

[vruumllc]

Yes! I saw it in the latest docs. I’ve been so busy that I haven’t had a chance to try the new file management API, but I am excited about it. Many thanks!

[diyelectromusic]

A real human editor would be better for this, but asking folks to contribute to the documentation of an open source project is like asking them to gouge out their own eyeballs with a rusty spork.

I've just built my first Picocomputer and whilst the hardware documentation is excellent, it did take me a while to figure out how to get started running something once built. I've you'd like me to try to pen a "Getting Started" guide to getting something running on the 6502 for the first time, then I'd be very happy to give it a go. I'm not familiar with sphinx though, so might need a few pointers...

The Picocomputer is excellent and I've really enjoyed seeing the development process in the videos. I look forward to seeing what other people have been doing with it.

Best wishes,
Kevin

[rumbledethumps]

I don't think it's necessary to keep "Builder", "Programmer", and "User" docs all in the same place. The way I use sphinx is basically one notch more complicated than a wiki, so dig in if you want but it's not hard or necessary.

The built-in help system is an example of user docs not in sphinx/rst. The help system was internationalized in the latest release so it's easier than ever to edit and there's plenty of flash. It was my intent that folks move to help after building then back to the datasheets if they want to write software.

I think what's missing is an onboarding or "what to try in the first few hours" guide. Perhaps a video of someone doing all the things, including browsing the help. Or a selection of roms and something that can be printed so the experience can be done offline.

My advice would be to either enhance what we have, or consider experimenting with another medium for onboarding docs. I read your blog post and you'll be pleased to hear that you've barely scratched the surface. @jasonfrowe enabled standalone music production on the newly added FM synth, so you'll want that USB hub and some speakers. And the Pico 2 W adds even more toys to play with.

Thank you for the Ko-Fi.