Core3Duino (April Fools?!) And XDuino

It’s inevitable. You knew it, we knew it, and while this is being posted on April 1st; its no joke. [johndavid400’s] Core3Duino. As we mentioned before, with the additional Arduinos you have now 3 separate processors, allowing 24digital IO, 18 PWM, 18 analog inputs, and more.

Now to keep flamers at bay (calm down), we’ve combined this post with the introduction of xDuino. Yet another attempt at porting Arduino to separate hardware platforms. For the price of a Duemilanove you can have 5 serial, 48 IO, 18 analog, 68Kbytes of Ram and more!

[Thanks Kamil]

16 thoughts on “Core3Duino (April Fools?!) And XDuino

  1. If you just need more i/o then a MUX shield is much cheaper. Maybe good for interfacing time critical Interrupt driven program with a control program on another “core”

    anyways still fun :D

  2. No joke, I’ve takled to this guy back when he was just doing one core (his instrucatble didn’t have any components listed during revision 1). I made a second core board and it’s kinda cool. I suppose you could make plenty more cores at long as you have enough amperes to go around. Each chip has to be separately programed however, so it’s not like it’s tripling the program space or anything.

  3. I have a sudden urge to line my walls with arduino “core” boards, and wire them all together in a core system…Think of the possibilities! And expense…and heat…dawwwww

  4. @K313k

    If you load up a stack that all the uC’s can use, you can just instantaniate the commands on a chip-by-chip basis. One chip would act as the task manager and manage the stack. It will search a registry-list of all the uC’s for any mC that is in a ready status. It would then set the chip to read a specific block of memory. In the block could be a set of commands and data to be proccessed. Once done, the uC would reset the list of uC status to a ready state.

    It can then have a master list of commands( read ROM) to help in instantaniating commands. As long as the memory is being seperated into independently executed blocks, you wouldn’t have to worry much about different uC’s trying to use the same resources. Just load your compiled program as a tasking list into the stack and the task manager uC handles the rest.

    As for power, the TM uC can control a multiplexer to monitor for changes in power consumsion and adjust accordingly.

Leave a Reply

Please be kind and respectful to help make the comments section excellent. (Comment Policy)

This site uses Akismet to reduce spam. Learn how your comment data is processed.