There is a shortage of displays right now, I was lucky to get in just before it got really bad. And also very lucky the quantity was so high, because it ended up being the minimum order quantity for the only place that could get them any faster than 6 months!
This is part of the reason the kickstarter units are behind schedule, we should get all of them delivered to us by the end of the year.
I’m looking into ways to sell the parts on the store here, but it only makes sense to me if I can sell them cheaper than they are available elsewhere. I’m looking at ways of selling the battery separate but that is a project for another day.
Don’t forget the original board files are out there too!
I just wanted to jump in here and say I love to see all this work here, it’s so cool to see everyone helping each other out. These kind of forum posts are exactly how I got started. Keep it up everyone!
I’ve recently ordered my Arduboy from the webstore and I think I’m gonna get it in my hands soon enough. But since I always love cool projects, for as simple as they may be, I bought everything necessary to build my own homemade Arduboy, or “Hackduboy” as some have said.
I know a bit about electronics and programming, but have never messed with any Arduino related thing.
Well, my dev box is running memory tests , so I decided to take a crack at putting one of these together. The parts box provided everything but sufficient switches, so tried one of these instead. It worked well enough to verify functionality, but the buttons were problematical at best, the LEDs had the wrong common pin, and the entire thing was a bit flakey. Since I Need more switches anyway, I’ve placed an order for those. Thanks to those who contribute the writeup.
I’d really rather use a Uno than a Leonardo, but the code doesn’t compile and I think it’ sufficiently unlikely that the leonardo version will work to bother trying it. Please let me know if that’s wrong. The Arduboy2 library doesn’t seem to be any better off. At one point Scott had a branch of the Arduboy library for the atmega328p, but the examples in that don’t build for me.
So, is the idea of moving from the Leonardo to a Uno dead? My next choice would be a pro mini (I buy those in six-packs), but that’s still got a 328 and not a 32u4, so probably no better.
Yeah and I think overall the library (and others also) is moving the opposite direction of that also. We’re moving to smaller code size and very optimized for real Arduboy hardware (timers, ports, etc). Someone who wants the best experience really needs to use the same components - which as mlxxxp said is the 32u4 when it comes to CPU.
For me, this isn’t about “best experience”, but about “easier development”. I’ve got one 32u4 based Arduino, and something like a dozen 328p based ones in my parts box.
What I’m thinking about now is turning a proto shield into an “Arduboy shield”. Just solder the LCD, buttons and speaker on the thing, and then plug it into whatever fits my project best. The Leonardo for current Arduboy code, but it could go on a Mega or a Zero for a SAMBoy, or a Nuecleo board or even the STM32F469 Discovery if there’s ever an STMBoy. Anyone else interested in such a project?
Do you mean a project to create a standard “Arduboy” shield? It might be difficult because it’s best to assign pins based on the capabilities of the particular processor. E.g. PWM pins for the RGB LED or a DAC output for the speaker.
Clearly, it wouldn’t be “standard”, since there’s not really a standard. The devkit used different pins, and a number of systems similar to the one proposed here used different pins as well. Making it use the same pins as the current production Arduboy is more a matter of “why not” than “why”.
This would be in the same space as all those other DIY systems. The only real difference is being on a shield would make it easier to experiment with other processors than being on a breadboard or a custom PCB.
Sure. If you just brought out all the peripheral signals to pads, that could then be jumpered to pads on all the pins (either by soldering or by some kind of plug/socket system), and made it both 5V and 3.3V compatible, it could be useful.
Do the pads really have an advantage over just plugging stuff into a proto shield or a bread board stuck to one (what I’m doing now)? I’ve found such things to be a bit fragile, which is why I’m looking at hardwiring things to a proto board. Sure, using header pins or some such would make it easy to use binaries from some hypothetical 2nd gen system, but what are the chances that it’s going to use the same peripheral set with a different CPU?
The only advantage I see to a shield with pads is that you could hardwire all the power and ground connections, but all the signals will still have to be manually connected, so not a big advantage over a solderless breadboard, like I use.
Not much. That’s why porting the libraries to another processor architecture can take some effort. But the goal is that the library’s API abstracts the hardware well enough that sketches will recompile with little or no change, as long as the sketches use just the API and don’t directly access the hardware or contain assembler code.