Difference between revisions of "Coduino"
From Hackstrich
(Parts ordered.) |
(status updates.) |
||
Line 2: | Line 2: | ||
== Project Status == | == Project Status == | ||
+ | * 2012-02-24: First board assembled, runs 'blink' on all 4 CPUs successfully. | ||
+ | * 2012-02-22: Parts arrived. | ||
* 2012-02-21: Ordered parts from Digikey. | * 2012-02-21: Ordered parts from Digikey. | ||
* 2011-10-18: PCBs received. | * 2011-10-18: PCBs received. |
Revision as of 04:44, 26 February 2012
The Coduino (Coprocessor for Arduino systems) will be an Arduino-compatible CPU/support on a shield, to enable multiprocessor stacks. It may also be made in multi-CPU version (2 or 4 CPUs on a shield) for really cool projects.
Project Status
- 2012-02-24: First board assembled, runs 'blink' on all 4 CPUs successfully.
- 2012-02-22: Parts arrived.
- 2012-02-21: Ordered parts from Digikey.
- 2011-10-18: PCBs received.
- 2011-09-30: Completed routing board, added all required silkscreen, submitted to Laen for prototype manufacturing. Need to order parts now.
- 2011-09-29: Almost done routing board.
- 2011-09-26: Started routing board.
- 2011-09-25: Added master reset button and power LED. Schematic passes checklist.
- 2011-09-23: Started working on schematic, now 90% complete. Need to add a master reset button and a power LED.
- Pre-Sept 2011: Put specs and BOM together.
Specs/Brainstorming
- Will use ATMega328p for compatibility with the Duemilanove board.
- As of March 2011 these are available again in TQFP and QFN packages.
- Standard boot loader will be used.
- Serial only in the first revision, no USB-Serial on the board itself (FTDI cables are easy to get now).
- Will communicate with the master Arduino (bottom of the stack) via I2C (with jumpers to disconnect this), leaving all other pins available.
- Main headers will just 'stack-through' the master Arduino, the I/O from the Coduino will be broken out on separate headers (maybe with a 'base board' that can connect to stack shields on the Coduino via a cable?).
- Board could have capability for 1, 2, or 4 (or 3 really, but I like more even numbers) processors, and just get stuffed with the desired number for cost control.
- I2C would be connected through to each MCU as the communication interface