Due pinout diagram

1) Thanks, but shouldn't that be "more better"?

2) I've currently got the shits with Arduino Inc but I'll get over it. :) Meanwhile I created this document so it behooves me to make it as good as possible.

3) We're up in the hills, apart from the fact that the grass is 5-foot high and it rains every day so we can't cut it the recent events have not affected us thankfully. We just got home in time, Gympie is isolated again today with the highway cut on both sides, we drove through there a couple of days ago. This is Gympie's 4th flood in a year. Poor buggers.


Regarding the two LEDs, I’ve seen several posts of people getting confused about which LEDs they are looking at. So if at all just for identification and clarification so they don’t get confused of what they are, as opposed to the ones used for programming.

OK you talked me into it :), see the first post and advise if the text is not clear/correct.


It looks like the physical pin color was shifted from dark gray to light blue. The LED and SPI physical pin bubbles remain dark gray (no pun intended).

Bugger, I'll fix shortly.


All errata (as far as I know) fixed, new versions uploaded.


Nobody seemed to have asked these questions before, so I'll ask it now: 1. Why do all pins have a "Digital Pin" and "Physical Pin" and "Port Pin" alias? Where are these aliases used to refer to these pins - for instance, when would I need to refer to pin A3 by A.22, or AD4, or D57, or 81? 2. There seem to be many Reset pins. What does the Reset pin in the SPI cluster reset?

Digital pin is the Arduino name and that’s what most people would use.

Port pin is for those who are working directly with ports and not the Arduino abstraction layer.

Physical pin is for those who need to actual probe the chip and therefore have to know the real pin.

I don’t think there’s any programming syntax that uses say “A.22” as such, that’s just a common way to indicate bit 22 of port A.
Likewise for ADn, but if you are working directly with the ADC hardware you need to know what actual input is being addressed and “AD4” is as good a way as any to do that and the terminology used by Atmel.

Use A3 (for example) for analogRead().

Just the number for digitalRead/Write, ie 57 not D57.

AFAIK all the reset pins go to the same place, it’s just that the various connectors use the signal at different times.


Thanks for this - It is really helpful!

Excellent post :). Thanks for this. Very helpfull!

Glad to help.


where did you get the info on the high current vs low current pins? I’d like to map out some other pins from a design i’m working on but i can’t figure out whether they are the high current or low current pins. :frowning:

See page 1391: http://www.atmel.com/Images/doc11057.pdf

thanks!! :D


You said: "I have also completely lost interest in the Due for a couple of reasons."

Why? Isn´t it a very good board?

Hmmm, did I say that did I :)

There's nothing wrong with the Due, it's just that IMO it could have been a lot better. They ignored most of the neat hardware the chip has, mostly I assume in favour of Mega shield compatibility, so we have a powerful ARM board that can flash 54 LEDs but cannot interface correctly to an SD card, external memory or Ethernet.

I think it could have kept Duemilanove/Uno shield compatibility and used the spare pins for more useful functions. But then I would think that because it's exactly what I've done with my latest Mega2560 design and plan to do with a SAM design soon :)


Just wanted to thank you for putting out this diagram. It has helped a lot.

But I would like to have one addition to this diagram. The addition of quadrature inputs would be a great help.

Also, if you can make a second diagram that listed the primary pin designations and has a empty box so that the user can designate what pens are used for what purpose in their project, it would be very helpful.

Again, thank you, it has been a great help.


promacjoe, there's a spreadsheet available here that might help.

The spreadsheet is nice, But if the spreadsheet was all that was needed, this thread would never have been started. the graphical representation of the board that is presented here is much easier to read and understand. Being able to see and to locate each pen and its corresponding use is much better than a spreadsheet. Although a spreadsheet can display more data, is just not the same.

Thank you for your reply and I will look over the spreadsheet.


Thanks for the answer, GreyNomad.

I just published one article about the ARDUINO DUE board and included your pinout diagram (and gave all the credits to you and your webSite). (Portuguese - Brazil)

About the peripherals to interface with SD card, external memory or Ethernet not be available in Arduino DUE, I have the same criticism.

I´m writing one article for the next week analyzing specifically the DUE´s sch, that I´m going to include this type of concern.

Regards, Thiago