Go Down

Topic: Arduino Due Mini/Nano (Read 14 times) previous topic - next topic


The trouble with BGAs is that you need about 10 layers to get the pins broken out.

And then the board cost goes up a lot ...


... and the ability of folk to roll their own boards based on those chips go down. It's hard enough and expensive enough to get a 4-layer board made...


A small factor Due is in the list of boards that will come out.

Good to hear.

There are a number of issues to solve ... for example with such a big processors it becomes hard to make something that would fit into a breadboard without removing access to most of the pins.

Removing access to pins is generally a bad idea; if a smaller chip doesn't provide a feature, fair enough, but if the chip does provide it and it is not broke out then this is frustrating, because SMD pins are so tiny so wiring directly to the pins is hard.
On the other hand, it may be worth examining whether breadboardability is a primary requirement for a small form factor. Breadboards with their parallel rows of connections impose a constraint on the PCB that is not needed or helpful. If a 'Nano Due' could be connected via multiple rows of solder holes (or pins, or sockets) around the periphery the more pins could be broken out.

For example: Is it important to have the two separate USB connections or just the "native" connection would suffice?

Since that is one of the defining features of the original Due then I would say yes, its important to keep on a Mini/Nano Due. For example, people might prototype and develop on an original Due, then use a mini/nano Due to mount permanently in the completed project.
There is also the possibility (and this is not without risk, but should be considered) to break away from the 2.54mm/0.1" grid spacing for sockets, and to make a range of small boards with smaller pitch (1mm?) sockets and corresponding small-pitch shields.


I think that you lose some features with the SAM3X8E but I can't find a good comparison chart right now.
Atmel just released asf 3.5 and I got a sd card/Fatfs api working on a SAM3X-EK so that is exciting. 
My goal is to get a standalone json/cgi server running,  I think that can lead to some really cool "Internet of Things" applications.

What is the priority: Due Mini vs Due Net?  Due Net would seem to be a little easier hardware wise but integrating FatFs/lwIP/SD card drivers might be a pain.

"Who left the fridge open?"
-Tugg Speedman
(Scorcher VI - Global Meltdown)


Go Up