Squirrels have fuzzy tails.
0 Members and 1 Guest are viewing this topic.
# 58 I/O Total# 16 ADC# 25+ Servos# I2C, SPI# 3 UART + USB# Up to 8 external interrupts# 12 PWM Channels# 64KB Flash, 4KB EEPROM, 8KB SRAM# 16 MIPS throughput at 16 MHz# 6 Timers (four 16-bit, two 8-bit)# pre-programmed with a bootloader - no programmer required# numerical LED display# built in 3.3V, 5V, and unregulated power buses# external memory support (port A)# all software is free# 100% open source, large support community# Windows, Mac, and Linux compatible# and more!
Is there a particular reason why the 1280 or 2560 is not going to be used? Is the 640 already overkill for most projects?
will the original still be available
four fewer servos (no one needed more than 20 so far)
Is there any chance of the Axon II coming out earlier?
what is the point of the number LCD? Will it show how much space is used up?
You are targeting a $130 product towards beginners? I thought your target market is competent builders who simply need a powerful prototyping platform. I feel somebody who needs all those IOs and peripherals is going to find the slow speed a real bottleneck someday.How about sticking a microSD card holder on it? Using Tiny-FatFs is really easy.
Looks like the 7 segment LED replaces the status LED from the original Axon. Kind of a waste to use 7 pins on it but I doubt anyone will miss those.
With a massive chip like that, somebody might want to do some on-chip debugging, have you thought about making JTAG easily accessible? It will be a pain in the butt to wire up the interface manually.
I've had cases when memory locations were accessed where they are not allocated, sometimes even into the stack, or the stack went too deep, and caused resets and other weird behaviour. Your hyperterminal will not let you analyze things like that in detail.
I'd suggest trying to move the reset button back to the edge of the board though, to make it easier to access.