Arduino Forum

After much discussion about pinout diagrams and Arduino documentaion I decided it's time to put my money time where my mouth is and create a pinout diagram for the Due

NOTE: Regardless of new posts this first post will always point to the current versions of the drawing.

ANOTHER NOTE: This might look pretty flash but it is NOT VERIFIED and NOT OFFICIAL it's very easy to make a mistake with this sort of thing. This means that you should not bet the farm by doing a design based on this drawing without checking what you are doing.

---

UPLOAD HISTORY:

28 Aug 2019
Manolofen's Spanish version added.

7 Apr 2014
Gogol's editable version added.

8 Jun 2013
Errata  fixed.

26 Feb  2013
Some new annotations added.
SPI Arduino pins numbers added.
The SDA1 and SCL1 pins were swapped, as were all related labels except D71 and D70. Fixed.
PDF version added.

11 Nov 2012
First version.

---

ERRATA/CHANGES/ADDITIONS: (not available in the latest version but will appear next time I upload)
None known at this time.

---

LATEST VERSION: (8 Jun 13)



Web-friendly version (176kB) (900x1004)
Due-pinout-WEB.png (http://www.robgray.com/temp/Due-pinout-WEB.png)

A4 version (628kB) (2676x2400px)
Due-pinout-A4.png (http://www.robgray.com/temp/Due-pinout-A4.png)

A3 version (884kB) (3679x3300px)
Due-pinout-A3.png (http://www.robgray.com/temp/Due-pinout-A3.png)

CorelDRAW vector file (672kB)
Due-pinout.cdr (http://www.robgray.com/temp/Due-pinout.cdr)

SVG vector file (2.0MB)
Due-pinout.svg (http://www.robgray.com/temp/Due-pinout.svg)

PDF file (569kB)
Due-pinout.pdf (http://www.robgray.com/temp/Due-pinout.pdf)

Note the CC BY-ND license, you can use this diagram for any purpose commercial or non-commercial but you cannot make changes. If you want a custom size or version email me.

Editable PDF version (676k)
This allows you to enter your project's functions for each pin. With thanks to member Gogol.
Due-pinout-fillable-form.pdf (http://www.robgray.com/temp/Due-pinout-fillable-form.pdf)

SPANISH version, thanks to member Manolofen
Due-pinout-A4-spanish-grande.jpg (https://www.fantasystudios.es/arduino/images/arduinos/due/Due-pinout-A4-spanish-grande.jpg)



______
Rob

If there's any interest I'll continue with it.

there is !

greets

Quote

If there's any interest I'll continue with it.

there is !

greets

From me too,

put the current from the Pins on it too and it will be damn near perfect

Exactly what I have been looking for!

I really like that you also bring in which ss is getting occupied with the ether shield

I like it - gonna get big when you get down to the double laeyer of signals on the bottom.

And Idea could be to take tat part of, and rotate it 90 degrees. No point in writing over the board, for that matter, an outline of the board, with the important parts marked would do also.

Like fan it out left & right along the bottom?
     __||||___
     ___||____ 
   
That would work, keep everything  upright & readable along the sides.

Ok I'll carry on, I actually did quite a lot today and yes it's getting pretty big. Except for the photo it's a vector drawing so can be printed at any size as a cheat sheet for the wall or wherever.

For that I either need a better quality photo or yes I can draw a vector overlay, after all you don't really need a photo with every component although it does look nice.

Does anyone have a hi-res pic of a Due? This one is from the product page, it has a lot of flare and is lo-res anyway. Good quality and NO barrel distortion please. If I get a Due I'll shoot my own from a great distance so there's little perspective distortion. (I did work as a product photographer in a past life)

As for the bottom pins, currently I favour breaking that section off, but I'll play with CR's idea and see how readable it is. Often this creates too many parallel lines that are hard to follow though.

I am also noticing that some Arduino names are NOT the same as the SAM names. For example

*  16       TXD1  |  PA13  | "TX2"
*  17       RXD1  |  PA12  | "RX2"
*  18       TXD0  |  PA11  | "TX1"
*  19       RXD0  |  PA10  | "RX1"

from variant.cpp.

Note that the SAM UART # and the Arduino Serial # do not match. Why I can not say but that's a trap for young players.

I'll post a more complete version in a few hours.

______
Rob

I`ll be happy to make a picture tonight if still needed

Thanks panzar, for the moment just a jpeg maybe 2000px on the long side will do. If possible square, shot from as far away as possible with a long lens, no pincushion/barrel distortion, even light, no hot spots etc. :)

You can email me rob@robgray.com.

EDIT: Oh, and a plane background, doesn't matter what colour.

______
Rob

Nice work so far! This will be helpful Rob!

Does anyone have a hi-res pic of a Due? This one is from the product page, it has a lot of flare and is lo-res anyway. Good quality and NO barrel distortion please. If I get a Due I'll shoot my own from a great distance so there's little perspective distortion. (I did work as a product photographer in a past life)

Remember that the picture you have now, seems to be the one with markings on the ICSP next to the 16u2 chip, my Due does not have those markings, so one should prefer to get an picture of that one, so we have the correct orientation, since it's upside down compared to the SPI (old icsp placement) on the board.

OK, at this point it doesn't matter because I'm only doing the header pinout, but if there are such differences I'll need the current board when I do other stuff.

______
Rob

Here's the current version, it's growed a bit.




My brain hurts from checking and cross checking and it's very likely that there are errors at this point. Feel free to point them out :)

Note the extra serial port (Serial4?), not supported as far as I can see but there none the less.

______
Rob

supernice, for completeness, will you do the spi, icsp, cortex, and swid to?

Thanks panzar, for the moment just a jpeg maybe 2000px on the long side will do. If possible square, shot from as far away as possible with a long lens, no pincushion/barrel distortion, even light, no hot spots etc. :)

You can email me rob@robgray.com.

EDIT: Oh, and a plane background, doesn't matter what colour.

______
Rob

Lightroom lens correction FTW ;)

I`ll have a try tonight

ohhh and keep it man it looks like you are eating the datasheet :D

@neslekkim
Yes I'm happy to do the ICSP, SPI and SWD pinouts and anything else that's useful, as you said though we need to know which PCB layout is correct for the future.

What do you mean by "cortex"?

looks like you are eating the datasheet

My brain literally does hurt from nutting this lot out. Yes I can correct pincushion and barrel distortion in Photoshop :)

______
Rob

Awesome work so far Rob.
What a confusing data sheet.
Looks like there are multiple sets of SPI controllers  - I don't see how they make it to IO pins tho.
For example PA25-26-27-28 make up SPI 0 with 3 additional chip selects on PA29-30-31 - where are are PA30-31 on the Due schematic? PA25-26-27 only seem to be on a 2x3 header?
Similarly for PE28-29-30-31 for 2nd SPI - what pins do they get multiplexed onto? I can't tell from the data sheet, same for the additional chip selects on PF0,1,2.

Here's the current version, it's growed a bit.



Link to larger version

www.robgray.com/temp/Due-pinout-1.jpg (http://www.robgray.com/temp/Due-pinout-1.jpg)

My brain hurts from checking and cross checking and it's very likely that there are errors at this point. Feel free to point them out :)

Note the extra serial port (Serial4?), not supported as far as I can see but there none the less.

______
Rob

Giant work, cool. Can you send the cdr file too?

What do you mean by "cortex"?

the tiny connector, jtag, 2x5 pin, is an socalled Cortex debug port, atleast people have told me that.
http://infocenter.arm.com/help/topic/com.arm.doc.faqs/attached/13634/cortex_debug_connectors.pdf
(maybe there is an better name out there)

Awesome work so far Rob.
What a confusing data sheet.
Looks like there are multiple sets of SPI controllers  - I don't see how they make it to IO pins tho.
For example PA25-26-27-28 make up SPI 0 with 3 additional chip selects on PA29-30-31 - where are are PA30-31 on the Due schematic? PA25-26-27 only seem to be on a 2x3 header?
Similarly for PE28-29-30-31 for 2nd SPI - what pins do they get multiplexed onto? I can't tell from the data sheet, same for the additional chip selects on PF0,1,2.

Is it strange that I didn't get SPI to work ? :)

pins 50-53 is supposed to be spi also?.

C:\arduino-1.5.1r2\hardware\arduino\sam\system\CMSIS\Device\ATMEL\sam3xa\include\instance
In that folder, it seems that there are two spi controllers yes, but the spi library seems to ignore that fact, and I couldnt find out which of them its using.

After much discussion about pinout diagrams and Arduino documentaion I decided it's time to put my money time where my mouth is and make a start on a pinout diagram for the Due

If there's any interest I'll continue with it.

That adds a bunch more detail than the one I did (which was based on the one I did for the Mega2560, which in turn was based on Nick's original for the Uno R3). Overall I prefer it (though it is going to get crowded for the double row of headers at the back of the board.

How about you continue to work on it and then I add it to the (now stickied, I see) Due pinout thread?

@Crossroads
Yes these ARM chips are way more complicated, I usually have to do a spread sheet to keep track of the pin options used or it gets out of hand.
I'll be looking into the SPI stuff today probably.

I think I'll add another type of label, maybe "other useful functions" for things like external memory, the unsupported serial port, extra SPIs, SPIs on USARTs etc. I'll check out the pins you mentioned.

@Markus_L811
I'll add a link to the CDR file on the first post sometime today.

@neslekkim
Good a name as any I think. On the Due it appears to be the standard Cortex 2x5 pinout. I'll be checking that.

but the spi library seems to ignore that fact,

I think a lot of the hardware is not yet supported. Massimo said that they decided to get the hardware out even though they hadn't written every driver or library. I assume that they will come along before long or that others will step up and write some code.

@Nantonos

How about you continue to work on it and then I add it to the (now stickied, I see) Due pinout thread?

Happy to do so, I plan to pirate some of your pinout info :)

@all
Note that the latest version of the drawing will now always be linked to from the first post on this thread.

______
Rob

I've been trying to get a clear version of the SPI pinouts while using a photo of the board however I just don't think it's possible without pulling the header images out from the board, something I don't want to do.

So I've done a version with a vector graphic in place of the photo, I will add some more details but I think it's clearer. The photo looks nice but at the end of the day it adds little to the object of the document.

Here's a sample with the new graphic, you'll notice that I am now able to place the SPI labels in an appropriate place. This should work OK for all of the internal headers although the Cortex debugging one might be a problem.

www.robgray.com/temp/Due-pinout-temp.jpg (http://www.robgray.com/temp/Due-pinout-temp.jpg)

Comments?

______
Rob

Yes, the vector represetation of the board reduces clutter, while still being clear enough with the board in your hand.

Incidentally PNG is a better raster format for sharp-edged artwork than JPEG, which is at its worst on this sort of image. SVG would also be a useful option.

I've been trying to get a clear version of the SPI pinouts while using a photo of the board however I just don't think it's possible without pulling the header images out from the board, something I don't want to do.

So I've done a version with a vector graphic in place of the photo, I will add some more details but I think it's clearer. The photo looks nice but at the end of the day it adds little to the object of the document.

Here's a sample with the new graphic, you'll notice that I am now able to place the SPI labels in an appropriate place. This should work OK for all of the internal headers although the Cortex debugging one might be a problem.

www.robgray.com/temp/Due-pinout-temp.jpg (http://www.robgray.com/temp/Due-pinout-temp.jpg)

Comments?

______
Rob

Think its easier to read. Btw. has the TWI on the top near the reset no pull-ups?

Here's a sample with the new graphic, you'll notice that I am now able to place the SPI labels in an appropriate place. This should work OK for all of the internal headers although the Cortex debugging one might be a problem.

www.robgray.com/temp/Due-pinout-temp.jpg (http://www.robgray.com/temp/Due-pinout-temp.jpg)

That is awesomely a lot better!

(If you have to increase size etc, I would prefer that it would scale/fit on an A4/Letter papersize, I'm going to print it out fullsize for reference)

I guess you are going to mark the usb ports also? which is native, which is programming, strange that they are not labeled on the board..

Just noticed one thing, the headers, VIN, do that pin give the same level as the input?, so If I use an 12volt adapter, I will get 12volt there?
If so, that is really something to be aware of.. I newer knew that..

has the TWI on the top near the reset no pull-ups

No pullups on the main I2C.

I would prefer that it would scale/fit on an A4/Letter papersize

At present it needs an A1 sheet, how large is your printer :) But it's all vector based so should scale to anything.

VIN, do that pin give the same level as the input?

VIN is the same everywhere, if you have 12v on the barrel jack you'll have 12v on the header pin. That said, if you're drawing a lot of current it would be better not to run it through the PCB.

VIN, do that pin give the same level as the input?

Yeah, that was just a quicky at hi-compression to show the new design, and the PNG was too large.

_____
Rob

Quote

VIN, do that pin give the same level as the input?

VIN is the same everywhere, if you have 12v on the barrel jack you'll have 12v on the header pin. That said, if you're drawing a lot of current it would be better not to run it through the PCB.

Wops, I haven't read it as VIN, I have read it as vcc :), thank god I have used only usb power, and breadboard psu so far :)

@Crossroads

OK I've done some searching.

where are are PA30-31 on the Due schematic?

PA30:31 are only available on the 217-pin chip.

Likewise for PE28-29-30-31, sorry there's no second SPI.

The good news is that two of the USARTs have the SCK pins broken out on PA16 (A0/D54) and PA17 (SCL1/D71).

I'm about to add them to the diagram.

______
Rob

Quote

has the TWI on the top near the reset no pull-ups

No pullups on the main I2C.

Strange why, difference between them?

Btw. On PB14 &PB15 is an another CAN Controller CAN1

Strange why, difference between them?

No idea, probably becaise SCL1 and SDA1 are the standard I2C signals and old shields don't expect pullups, whereas SCL and SDA are new so thay can ba added.

On PB14 &PB15 is an another CAN Controller CAN1

Yep, got them.

_____
Rob

PA30:31 are only available on the 217-pin chip.

Turns out the datasheet I was looking at is only the Summary data sheet - only shows the 100 & 144 pin packages.  Didn't realize there was a 217 pin package as well.

@Nantonos
Sorry, I just realised the earlier versions were actually JPEGs. Fixed now.

@all
Latest version just uploaded.

_____
Rob

@all
Latest version just uploaded.

The CANTX1 and some others are white, is that because its' not supported yet?, or should those be blue?

If anyone could confirm the SPI situation now..

They are on the schematic so at some point someone decided to at least label the nets. There's no mention of a second CAN on the product page so it looks like it's not yet supported and I've left them white. Likewise for the fourth USART and I doubt the SPI ability of two of the USARTs will ever be supported, but I think some people may want to use that one day.

BTW, does anyone know if the power jack is a 2.1 or a 2.5mm type?

______
Rob

Hi,

I new to this forum, although I use already since long AVR processors. Recently I bought an Arduino DUE.

The DUE pinout diagram is really awesome !! Great piece of work.

I think there are some minor errors:
1) port B.26 is not "TIOA0", but "TCLK0" (per B)
2) port B.16 is on physical pin 77 (not 78)
3) "TIOB7" (PWM10) is on pin 102 port C.29 (not 111 / A28)
Anyway please double check.

Perhaps you could also add the following:
- on A.19 "PWMH1" (per B)
- on C.19 "PWMH5" (per B)
- on B.14 "PWMH2" (per B)
- on C.18 "PWMH6" (per B)
- on A.20 "PWML2" (per B)
- on C.9 "PWMH3" (per B)
- on C.7 "PWMH2" (per B)
- on C.5 "PWMH1" (per B)
- on C.3 "PWMH0" (per B)
- on D.6 "PWMFI2" (per B)

best,
-D

This is just a first attempt and it's not finished.

Nice!

I would say but it looks good!

BTW, does anyone know if the power jack is a 2.1 or a 2.5mm type?

Power jack is 2.1

Hi,

I think you need to swap 5V and GND on the ICSP connector.

Maybe you could also add a comment that TX0 & RX0 are connected to the Mega16U2 (for programming).

-D

I guess you are going to mark the usb ports also? which is native, which is programming, strange that they are not labeled on the board..

Yes, I wondered, too. Then I turned the board over ....

Quote from: neslekkim on Nov 14, 2012, 10:52 am

I guess you are going to mark the usb ports also? which is native, which is programming, strange that they are not labeled on the board..

Yes, I wondered, too. Then I turned the board over ....

Ah, maybe, but I have mounted it on an tamiya plate :)

If you look closely you can tell the difference. The native port has a micro AB socket which is more rectangular. The programming port has a micro B socket which has diagonal bottom corners.

Quote from: neslekkim on Nov 14, 2012, 10:52 am

I guess you are going to mark the usb ports also? which is native, which is programming, strange that they are not labeled on the board..

Yes, I wondered, too. Then I turned the board over ....

Actually, I checked under the board now, There is no marking for the usb plugs.
Begins to wonder if Arduino.cc shipped discarded units to Adafruit?, to much changes between this one, and the one everyone else got.

@dancombine
Fixed and added, thanks for checking.

New version uploaded.

______
Rob

Hello Gray,
CANRX and CANTX in the board should be reversed. Great, great job man!

Fixed and uploaded. Thanks.

______
Rob

Sorry Rob, but you just had only to swap CANTX and CANRX inside the board, as follows:



Sorry again for the misunderstanding.

Bugger, I swapped everything else :)

Will fix.

EDIT: Fixed (I hope)

______
Rob

Good work.

Good work.

I would more than agree with that.

Btw. change the places from PWMH2 and CANTX1 and it looks more corporate

Thanks guys.

change the places from PWMH2 and CANTX1

Will do.

______
Rob

Hi Rob

thanks for the updates!

As you did correctly the change for PWM10 to point to C.18, the comment should now be updated as follows:
"Also connected to A.28".

thank you

Dan

All recent changes (I think) uploaded.

______
Rob

Rob,

thanks for the corrections.

One more thing: port C.29 (PWM10) is high current.
Could you also move the comment on the left "Allows serial2 to be used for SPI" above the "SCK1" box. This to make the total picture a bit less wide (as such fits better in a document).

Anyway I would like to thank you for a super job done. This is a great diagram to be used for all (hey Arduino guys, please take note ;)

best,
-Dan

Great work so far. I have a suggestion:  I printed the diagram out, and there's a problem that in print there's a lack of contrast with the yellow-on-grey port pin labels - they are almost unreadable. Given that (for me anyway) that's the most important column on the diagram could you change the colours for something more high contrast?

On pin 10: As you note this is also connected to port C29. Port C29 is referred to as digital pin 77 in Arduino - that is, if you load the Blink example and change the pin to 77, it will blink an LED connected to pin 10. It might be worth noting that as well.

Also could you add digital 'pins' 72 and 73? These aren't physical pins, but they are connected to the RX and TX LEDs near the native port - changing Blink to use pin 72 or 73 will flash them. Ports are C30 and A21 respectively.

Thanks Stimmer.

I've changed the colour of the port pins. As it's important this is legible in hard copy can you print it out again and see if that's now the case?

Note that at present I'm limiting the size to 2000px wide, this should print well up to about 8" or even A4 without pixelization. When it's more stable I'll upload larger versions.

I've added the LEDs.

But I'm having trouble with your second point. I can see that D10 and D77 are the same pin, IE C.29 or SS0/PWM10. But I can't see that any LED is connected to this. I don't have a Due so can't check this, which LED blinks?

New version uploaded with the above as I see it so far.

_____
Rob

Thanks Stimmer.

I've changed the colour of the port pins. As it's important this is legible in hard copy can you print it out again and see if that's now the case?

Note that at present I'm limiting the size to 2000px wide, this should print well up to about 8" or even A4 without pixelization. When it's more stable I'll upload larger versions.

I've added the LEDs.

But I'm having trouble with your second point. I can see that D10 and D77 are the same pin, IE C.29 or SS0/PWM10. But I can't see that any LED is connected to this. I don't have a Due so can't check this, which LED blinks?

New version uploaded with the above as I see it so far.

_____
Rob

Looks every post better, I would let Pin 4 even look like Pin 10 with the bonded Pin A29, and on TX0 RX0 may for USB programming isn'd obvious enough somethink that make it more clear that they are connectet on the programming port would be better my opinion.

Thanks very much, it is a lot more readable now.

The ports and pins for the TX/RX leds should be swapped. The LEDs themselves are in the correct order (ON,L,TX,RX) but the ports and pins should be in the order D13,D73,D72 ; B.27,A.21,C.30 ; 68,107,103

About D77, what I meant was if you plugged your own LED (and resistor) into D10 on the board, Blink will flash it when led=10 or led=77. It isn't connected to any LED already on the board.

There are some other pin number oddities in arduino_due_x/variant.cpp, for example digitalWrite(79,HIGH) will set both pins 70 and 71 - I don't think it's helpful to add these to the diagram though.

@Markus

Done and uploaded.

TX0 RX0 may for USB programming isn'd obvious

Is that what you meant?

Stimmer, just saw what you wrote. Will respond shortly.

______
Rob

The ports and pins for the TX/RX leds should be swapped.

Done.

what I meant was if you plugged your own LED (and resistor) into D10 on the board, Blink will flash it when led=10 or led=77.

Ok, what I've done should be enough then I think.

for example digitalWrite(79,HIGH) will set both pins 70 and 71 - I don't think it's helpful to add these to the diagram though.

Probably not, if there are useful anomalies I'll add them, at this point I think the diagram is bordering on information overload but there may still be a few things worth adding.

Note that the PNG size is way smaller, I exported to PNG8 rather than PNG24, with the limited colour gamut being used I think that's OK but let me know if it stuffs anything up.

______
Rob

Do we already know what the four solder pads/holes on the left next to the ICSP (right below the 16u2) are connected to?

They are connected to the 16u2, Port B  4,5,6,7 (relative to the diagram, 4 is SE, 5 NE, 6 SW, 7 NW) Remember that they and the ICSP pins work at 5v logic level.

Note that the PNG size is way smaller, I exported to PNG8 rather than PNG24, with the limited colour gamut being used I think that's OK but let me know if it stuffs anything up.

That is the correct thing to do; even with antialiasing there will still be enough colors.

(I'm one of the authors of the PNG format).

Continuing on graphic formats, both Adobe Illustrator (CS5) and Inkscape (0.48) choke on the Corel Draw file. Would it be possible to export to SVG? Or an earlier Corel Draw version, perhaps.

(I'm also one of the authors of SVG).

Would it be possible to export to SVG?

Another vote from my side.  :)

Hi Rob,

I've just gone through it again, and may I kindly ask for some other updates:

- port A.9 is also high current
- mark the little grey square close to ICSP with "mega16U2"
- would it make sense to add as well the erase button?
- the contour of the DUE board is good visible on the screen, but not really when you print.
  Can you make the contour darker or with more contract?
- add "TX0" on the board for port A.9
    and "RX0" for A.8
- on the actual DUE itself, there are marks with long lines across the pins, like
         COMMUNICATIONS                           
         same for PWM and ANALOG IN
  Do you think it makes sense to add those as well?


I think your pinout approaches perfection :)


thanks
-Dan

Do we already know what the four solder pads/holes on the left next to the ICSP (right below the 16u2) are connected to?

Stimmer is right about what that are connected to. Why they are connected is a mystery as those pins don't really have any special functions. When I design a board I often have a couple of spare pins broken out like that to allow pulse debugging with a logic analyser, maybe that's why they have done it.

Would it be possible to export to SVG?

Should be, I'll try that next update. @Nantonos, I won't try to tell you about graphics formats then :)

EDIT: Just created an SVG, it had two issues but I uploaded anyway. It looks like crap in a browser, can you guys try in a graphics program.

- port A.9 is also high current

Done

- mark the little grey square close to ICSP with "mega16U2"

Done

- would it make sense to add as well the erase button?

Done

- the contour of the DUE board is good visible on the screen, but not really when you print.Can you make the contour darker or with more contract?

Done
 

- add "TX0" on the board for port A.9 and "RX0" for A.8

Done

- on the actual DUE itself, there are marks with long lines across the pins, like
         COMMUNICATIONS                           
         same for PWM and ANALOG IN
  Do you think it makes sense to add those as well?

I did think of that but felt that things are getting a bit crowded to add them. I'll try it out though and see how it looks.
Looks OK I think, we'll leave it there for the time being. See what people think.

______
Rob

EDIT: Just created an SVG, it had two issues but I uploaded anyway. It looks like crap in a browser, can you guys try in a graphics program.

Looks great in Inkscape! Thanks for the good work.

Like D10 & D77, D87 works on D4 too comes from the bonded pins, and D86 works on Pin D52 it is SS2 the 3rd SPI select. Btw. did some one know where are the ADCs 8 and 9 are they missing?

did some one know where are the ADCs 8 and 9 are they missing?

Well spotted Markus

ADC8 -> B.12 -> SDA
ADC9 -> B.13 -> SCL

So it looks like you can get two more more ADCs if you aren't using that I2C port. However those two pins are pulled up by 1k5 resistors, so you'd have to drive the ADC with a low-impedance source.

D87 works on D4
D86 works on Pin D52 it is SS2 the 3rd SPI select

Added.

Unfortunately the 4th SPI CS pin is not connected.

Will upload new version soon.

______
Rob

Quote

did some one know where are the ADCs 8 and 9 are they missing?

Well spotted Markus

ADC8 -> B.12 -> SDA
ADC9 -> B.13 -> SCL

So it looks like you can get two more more ADCs if you aren't using that I2C port. However those two pins are pulled up by 1k5 resistors, so you'd have to drive the ADC with a low-impedance source.

Quote

D87 works on D4
D86 works on Pin D52 it is SS2 the 3rd SPI select

Added.

Unfortunately the 4th SPI CS pin is not connected.

Will upload new version soon.

______
Rob

You make an great job, really amazing, in my way you can wipe the Unofficial from the sheet, talk to Massimo this can or should an official Pinout!

:)

Thanks Markus you're too kind, but really I must insist, no applause, just throw money.

______
Rob

Just uploaded the latest version.

All above added plus some good news for those into audio codecs etc, all the SSC pins are available, this means you can play with I2S.

Notes to people using the vector versions.

The CC BY-SA logo is no longer a bit image, so that should scale properly without pixelating.

At some point I must have cut and pasted the entire drawing on top of itself. This means that there was two copies of everything, but they were in perfect register so you couldn't see any difference :) I've slowly been removing duplicates but there are still many left I would think.

Note about the pin mapping duplicates

It it worth having the D10/77, D4/87 and D52/86 duplications? They do exist but is there any point in knowing this?

______
Rob

It is worth knowing about the D10/D77 and D4/D87 duplicates, because each of these duplicates actually refers to a different port and pin. Also people probably ought to know not to set D10 and D77 as output and then have one high and one low, because then there would be an effective short circuit (and similar with D4/D87). Given that the intended audience will probably be more advanced users I'd say it was worth having on the diagram. In any case it might help when we get the inevitable "Where's pin 77?" questions here on the forum.

The D52/D86 duplicate is the same port and pin, I don't know what the reasoning behind it is, maybe it could be removed.

Good reasoning Stimmer, I'll get rid of the D52/D86 duplicate.

______
Rob

EDIT: Just created an SVG, it had two issues but I uploaded anyway. It looks like crap in a browser, can you guys try in a graphics program.

I fixed the issues (it uses SVG fonts, which browsers other than Opera don't support). Inkscape loads it and I re-saved from that, then used scour to get rid of needless bloat. Graynomand, if you pm me your mail address I will send you the fixed versions (work in Firefox, IE, Chrome, Opera).

Top left of the excellent diagram, explaining the color coding: "per A" / "Per B or X" - I am confused what the little black corner signifies. My guess is that the data sheet (AT91SAM) shows two variations a -A suffix and -X suffix. Is that it? And if it is, does it matter as the DUE probably comes with the same chip variation. The offical product page says SAM3X8E.

Top left of the excellent diagram, explaining the color coding: "per A" / "Per B or X" - I am confused what the little black corner signifies.

The IO Controller provides multiplexing of different Peripheral functions on a single pin, either A, B or extra (X).
This is a way to select one of them.
For more info, check the datasheet sections 11.3 and 32.5.3.

-Dan

What Dancombine said.

Actually I've been wondering if it's worth differentiating the peripheral mux option used. After all it has no real bearing on the average user and more experienced SAM users will either know this or will soon find out.

@Nantonos
I'll PM.

______
Rob

New version just uploaded, just a few layout changes, I think we're almost ready to call this done.

I didn't upload a new SVG, it blew out to 2Mb for no obvious reason. I'll work with Nantonos to get a good SVG file.

_____
Rob

I was under the impression that pin 50-52-53 also had something to do with spi?

Actually I've been wondering if it's worth differentiating the peripheral mux option used. After all it has no real bearing on the average user and more experienced SAM users will either know this or will soon find out.

Rob,

Actually yes, you're right. This might confuse the readers of the pinout. And when one is really in the weeds of selecting alternate peripheral pin functions, he would have to open the datasheet anyway to select the right register bits.

-Dan

neslekkim

That's on the Mega, with the Due SPI is only available on the 2x3 SPI header.

_____
Rob

Dan

Yes I think I'll remove them.

______
Rob

New version uploaded.

I'm still happy to implement any good ideas and of course fix bugs, but I think we're just about done here,

______
Rob

That's on the Mega, with the Due SPI is only available on the 2x3 SPI header.

Then I really don't understand why I cannot make work, those where the first ones I tested.

Then you'd better start a thread in the Due section of the forum. Post your code and people will check it out. It could still be the diagram but that's unlikely now I think.

_____
Rob

This glorious diagram is a great example of why I chose Arduino for my microcontroller dev/proto platform.  The community here is top-notch.  Thank you for the work, sir and well done!

Hi,

Very nice job this diagram !

I just would like to give my opinion on one thing :
I think you have already discussed this, but I'd prefer to have both peripheral A and B indicated.
To be honest I will print this layout and add some manual (and dirty) writing about periph A/B, so in my opinion it would be better to have it directly on the diagram...

Anyway, thanks a lot for your work!

thanks a lot for your work!

Thanks djjoshuad and dammien.

@djjoshuad dammien
We decided (well I think it was me and one other person but nobody disagreed :)) not to add that level of detail, so I'm afraid you'll have to get out the magic marker as I've moved on, I'll fix errors but have other stuff to do these days.

______
Rob

I read through this thread and want to thank everyone for making up the pin out for the DUE.  As a newbie on this board, it is very helpful.  I found the pinout at www.robgray.com/temp/Due-pinout-temp.jpg, but this does not include the 36 pin hearder at the end of the board.  Is there another pinout posted somewhere that I am missing?  Or does the pin out need to be updated for this large header?

read post # 1 in this thread.

I was inspired by your fantastic work and I have created a version for Arduino Uno. This is the link:

http://arduino.cc/forum/index.php/topic,145531.0.html

Bye, Pighixxx

Really well done Pighixxx.

______
Rob

i got the original picture but the link for the new one is broken.

i printed the original and found it to be quite useful but do have some suggestions re color use. there are some tags (especially the ones for the SPI connector) that have bad combinations of background and text colors that make it virtually impossible to read when printed. i could make no sense out of the SPI connections and had to sharpie them in on my printed copy. using a color laser at original size scaled to fit an 8.5 x 11 inch page

Since you have the LEDs between the Prog and Native ports, how about adding the other two LEDs Tx and Rx between the Power jack and Prog port (for the 16U2 communications)?

I'm not answering because I assume that these posts are about the new non-Due diagrams and therefore are addressed to Pighixxx.

Pighixxx can you start an English thread for your diagrams so we know which ones people are referring to?

______
Rob

I am referring to the Due board.  The Due has two other TX/RX LED between the power jack and the USB Programming port.  These LEDs reflect the 16U2 used for the programming port.

---

Pighixxx can you start an English thread for your diagrams so we know which ones people are referring to?

Hi Rob,
If you find it useful, i have no problem to open a new English thread.

Quote from: Graynomad on Feb 01, 2013, 03:31 am

Pighixxx can you start an English thread for your diagrams so we know which ones people are referring to?

Hi Rob,
If you find it useful, i have no problem to open a new English thread.

I for one will find it useful, now I'm just hoping that an Mega version also will pop up.. and the rest of the board for that matter, doesnt seem that the folks behind Arduino seem to see this as useful for their customers, but I like these.

Hi all,
This is the English thread of Arduino Uno Pinout Diagram (http://arduino.cc/forum/index.php/topic,146315.0.html)

Quote from: pighixxx on Feb 01, 2013, 12:55 pm

Quote from: Graynomad on Feb 01, 2013, 03:31 am

Pighixxx can you start an English thread for your diagrams so we know which ones people are referring to?

Hi Rob,
If you find it useful, i have no problem to open a new English thread.

I for one will find it useful, now I'm just hoping that an Mega version also will pop up.. and the rest of the board for that matter, doesnt seem that the folks behind Arduino seem to see this as useful for their customers, but I like these.

http://arduino.cc/forum/index.php/topic,125908.0.html

http://arduino.cc/forum/index.php/topic,125908.0.html

Yes I know that one, it was that one that started this thread, I was thinking about something along the lines of this thread and the new uno thread, if you don't see the differences..

Back on topic: With reference to the Native USB TX/RX LEDs ('pins' 73 and 72) - I just discovered that these LEDs use negative logic. That is, they light with digitalWrite(x,LOW) and extinguish with digitalWrite(x,HIGH) (the opposite to the L LED on pin 13 which uses positive logic).

So if it's not too much trouble it might be worth noting on the diagram that the LEDs on 72 and 73 are using negative logic. I was using them for debugging just now, and lost about half an hour wondering why my working code was registering a fault and my non-working code wasn't!  :smiley-mr-green:

...I was thinking about something along the lines of this thread and the new uno thread, if you don't see the differences..

Here the MEGA version  ;)
http://arduino.cc/forum/index.php/topic,146511.0.html

Bye

Thanks for doing these pighixxx, I did not have the time. They look fantastic (but then I suppose I would say that eh? :))

BTW the official Arduino font appears to be Consolas.

Re the above two comments about the LEDs, I'll add an annotation about the neg logic, what about the 16U2 LEDs though, how many people would use them directly?

______
Rob

Thanks to you!

I hope people appreciate the effort we made ??to put a bit of clarity ...
I'm working on the latest diagrams and then work!  :smiley-roll:

I want to use this post to thank again Rob who was the first author of this fantastic diagram; I was inspired by his work.

the drawing is definitely pretty and hopefully accurate but i have one suggestion. the readability is quite good on the computer but when printed with a (pretty decent) color laser printer, it is extremely difficult to read the dark colored tags. i could photoshop it myself but why not just reduce the density on the background colors? BTW. i was a professional cartographer (a million years ago) and dealt with printing and readability issues all the time.

One suggestion for the SPI header.  If you print out compiler defined variables MISO, MOSI, and SCK they print out pin numbers as follows: MISO 74, MOSI 75, SCK 76.  I believe these are the Digital Pin numbers for these three pins on the SPI header.  Variable SS is defined as 10 and that is D10/D77 as you note correctly for SPI-CS0.  Could these three Digital Pin values be added?  Thanks for your consideration.

Could SCL1, SDA1 be reviewed? Methinks the 9/70 and A.17/A.18 are reversed.

Sorry for my delayed response, I've moved on from this and have other stuff on my mind. I have also completely lost interest in the Due for a couple of reasons.

I have made all the above changes though and will post a new version soon.

@stimmer
Negative logic annotated.

@hiduino
I don't think I'll add those two LEDs as they are not really part of programming the Due for the normal application. I'm happy to be convinced otherwise though.

@spencoid
Hardware pins are now black on light blue, GND still the same. As that's the only use for that combo even if the text blocks out and it just prints black it's obvious what it is I think.

@TheKitty
I've added the Arduino pin #s for those three SPI pins, it's a bit of a kludge because there was no room but doesn't look too bad.

@Workalot
I think you are right about that, D70 and D71 were correct but the other labels were reversed.

@anyone with a colour printer
Let me know if the current colour scheme works, I don't have a printer so can't test. Bear in mind though that all printers are different, if it doesn't look good on a $20 Inkjet I'm not likely to change anything unless a few people have trouble.

______
Rob

quite readable now on my color laser printer. thanks for lightening up the blue. in fact, it looks just like the version i modified in photoshop.

Good, note the errata on the first post as well. I haven't got the energy/time to regenerate the files right now :)

______
Rob

1) This recent activity has made a good document gooder.

2) Your endeavour in time and effort to produce the 'Unofficial Guide'  seems out of whack with comments.

3) Noah did, and nr Bundaberg may have somewhat, shared similar water issues.

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.

_____
Rob

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.

______
Rob

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.

_____
Rob

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

______
Rob

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.

_____
Rob

Thanks for this - It is really helpful!

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

Glad to help.

_____
Rob

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. :(

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

thanks!! :D

GreyNomad,

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 :)

______
Rob

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.

Joe.

promacjoe, there's a spreadsheet available here  (http://forum.arduino.cc/index.php?topic=209034.msg1547134#msg1547134)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.

Joe.

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)

http://www.embarcados.com.br/arduino-due/

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

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.

Please post a link when it published.

______
Rob

The addition of quadrature inputs would be a great help.

primary pin designations and has a empty box so that the user can designate what pens are used for what purpose in their project

Both good ideas and I'll put them on my todo list, but I gotta say I have many other things on that list all with a higher priority (at present).

______
Rob

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.

Seems that you had a similar need, that I had. I created a diagram for the DigiX, where I combined both needs in one document.
There is an empty transparent form field over the additional information, which can be filled. Once filled, the field chances to solid background and covers the initial information.
Have a look at:
http://digistump.com/board/index.php/topic,1211.0.html

When Graynomad allows, I could overlay his PDF in the same way!

That's OK by me as long as the credit blurb stays intact, but I can't see what you mean, all I can find on that link is a JPEG.

______
Rob

In the very first post of that thread is an PDF linked.
DigiX-Pinout-beta-095a.pdf

The only link I can see in that post is this

http://digistump.com/wiki/digix/tutorials/pinout (http://digistump.com/wiki/digix/tutorials/pinout)

Maybe I can't see attachments because I'm not a member of that forum.

and

DigiX-Pinout-beta-095a.pdf  (http://DigiX-Pinout-beta-095a.pdf)

Gets a server not found error, although that might be a temp thing, I'll try again later.

______
Rob

You need to login, to see the attachment unfortunately.
However I attach it here as well

Enclosed now the current PDF with overlayed form fields, like I did for the DigiX.
In PDF-reader you need to "highlight existing fields" to see, where those fields are.
Once such a field is filled with own comment, it gets visible and covers the underlying basic information.

Thank you very much, this should help tremendously.
And I'm sure others will appreciate it just as much as I do.

Sam.

@gogol
Do you want me to add a link on the first post? With appropriate credit of course.

______
Rob

@gogol
Do you want me to add a link on the first post? With appropriate credit of course.

______
Rob

Of course, feel free to do so!   

regards

   Gogol

MACB  ETH 14 pin connector is shown in schematic
but not seen on BOARD

Correct, the schematic is wrong.

Why is is wrong and why not make it right? Who knows.

______
Rob

Those pins are on the DigiX available. However I miss some more pins:

• The NRST pin, see:  http://forum.arduino.cc/index.php?topic=160361.0


• The Erase-Pin, to allow easy programming with an openwrt-based WIFI-to-UART device


• The Backup-Voltage-Pin

I don't get it, why they tie C29,A28  and C26,A29 together??  :smiley-eek-blue:

Why indeed?

I haven't looked at the functions of those pins for ages, maybe there was a good reason but IIRC I couldn't think of one when I first saw the schematic.


______
Rob

Very good!!! Thanks a lot.

This is great :)

will you please point where is the clock(84 MHz)? :smiley-eek:

There is no external 84MHz clock AFAIK, I think you can put a clock signal out a pin but I doubt it would be the full 84MHz, maybe but that would be such an uncommon requirement I don't think it's needed on the diagram.

Also running 84MHz out to those headers would be an exercise in futility I suspect,

If it exists I'm willing to listen to arguments though.

______
Rob

THX, just received my first DUE, sadly it is not working but will get another to replace.

It may have been noted - but...

Is is possible that I2C ports SAM designations port numbers only are reversed?
SCL1 reads  TWCK0
SDA1 reads  TWD0 

and the "no number" I2C SAM designators are TWCK1 and TWD1

Rob Gray, you saved me a great deal of time.
Excellent job, thx.

Very minute / minor observation
The "TX" LED ( below USB native port ) is green, not yellow as shown on schematic.

I love these pinout diagrams!..

(what software do you use to create them?)

Great job!

Thanx a lot for the diagram :)

Can I use the internal resistors of pin14~19 by pinMode(pin,INPUT_PULLUP)? Does DUE has internal resistor on these pins?

Awesome!
Thanks you!

Hi,


One of the best diagrams i have seen so far for just about any micro controller.  Very clear and well laid out, easy to see where everything goes and where everything comes from.


Thanks.

Great work, thank you for creating. :)

Thank you for very helpful diagram.
Almost all pins are marked as digital. Does it mean that I can use all of them with digitalRead/Write and interrupts?

hi all
I have a project to read PT-100 using arduino due. but the problem is the bit value from analog is not constant
I hope someone from this forum can give me some explanation

The editable pdf is fantastic. Thanx mate. Much appreciated your work. Top notch

Hi Graynomad :)
What application did you use for drawing the diagram?
It looks nice, thanks.

bonjour

comment on rajoute l'atmegaS128 sur mini.menu.cpu ? merci

Thanks for the creation! Your work is truly great! I presuppose that you are a genius:)

Can anyone please help me out with the method of connecting arduino due board with LMP91000evm.

Information about DUE SPI is confusing. One problem I found today is in the schematic. MOSI text is on the + 5V pin. In this link https://www.arduino.cc/en/Reference/SPI (https://www.arduino.cc/en/Reference/SPI)it is correct I hope. All this creates a lot of posts.

---

Hello, I am new to here, appreciate if any gent knows the right ling to the 'DUE Pin Diagram'. I see the links on the first page of this thread is gone...
Thanks in ahead.
Chy

Links to pinouts not working. Please fix.

Since the links provided by Graynomad come from his own site (www.robgray.com), you should email him directly on his web site.

I have just been alerted to the fact that all the links are broken. I recently had to clean up my server and it seems that there was some collateral damage :(

Unfortunately the files in question are NOT in my backed up data, why I have no idea, but I'll try to find versions in other locations and re-instate them.

hello guys!

i am connecting arduino due i2c1 with my dac mcp4725 but dnt know how to use i2c1 .its working fine on i2c but i need multiple.

This is not the right place to post this thread (no link with the Graynomad pinout diagram). Ask the mod to transfer your post to the DUE threads.

I think that all files except Gogol's editable version have been restored. I can't find Gogol's file anywhere, if he's still a member maybe he has a copy.

Thanks  :)

I think that all files except Gogol's editable version have been restored.

web.archive.org has it:
https://web.archive.org/web/20180328233937/http://www.robgray.com/temp/Due-pinout-fillable-form.pdf (https://web.archive.org/web/20180328233937/http://www.robgray.com/temp/Due-pinout-fillable-form.pdf)

web.archive.org has it:
https://web.archive.org/web/20180328233937/http://www.robgray.com/temp/Due-pinout-fillable-form.pdf (https://web.archive.org/web/20180328233937/http://www.robgray.com/temp/Due-pinout-fillable-form.pdf)

Thanks, restored, all files should be good now.

After much discussion about pinout diagrams and Arduino documentaion I decided it's time to put my money time where my mouth is and create a pinout diagram for the Due

NOTE: Regardless of new posts this first post will always point to the current versions of the drawing.

ANOTHER NOTE: This might look pretty flash but it is NOT VERIFIED and NOT OFFICIAL it's very easy to make a mistake with this sort of thing. This means that you should not bet the farm by doing a design based on this drawing without checking what you are doing.

---

UPLOAD HISTORY:

7 Apr 2014
Gogol's editable version added.

8 Jun 2013
Errata  fixed.

26 Feb  2013
Some new annotations added.
SPI Arduino pins numbers added.
The SDA1 and SCL1 pins were swapped, as were all related labels except D71 and D70. Fixed.
PDF version added.

11 Nov 2012
First version.

---

ERRATA/CHANGES/ADDITIONS: (not available in the latest version but will appear next time I upload)
None known at this time.

---

LATEST VERSION: (8 Jun 13)



Web version (176kB) (900x1004, same as above)
Due-pinout-WEB.png (http://www.robgray.com/temp/Due-pinout-WEB.png)

A4 version (628kB) (2676x2400px)
Due-pinout-A4.png (http://www.robgray.com/temp/Due-pinout-A4.png)

A3 version (884kB) (3679x3300px)
Due-pinout-A3.png (http://www.robgray.com/temp/Due-pinout-A3.png)

CorelDRAW vector file (672kB)
Due-pinout.cdr (http://www.robgray.com/temp/Due-pinout.cdr)

SVG vector file (2.0MB)
Due-pinout.svg (http://www.robgray.com/temp/Due-pinout.svg)

PDF file (569kB)
Due-pinout.pdf (http://www.robgray.com/temp/Due-pinout.pdf)

Note the CC BY-ND license, you can use this diagram for any purpose commercial or non-commercial but you cannot make changes. If you want a custom size or version email me.

Editable PDF version (676k)
This allows you to enter your project's functions for each pin. With thanks to member Gogol.
Due-pinout-fillable-form.pdf (http://www.robgray.com/temp/Due-pinout-fillable-form.pdf)


______
Rob

Actually, We used this Due pinout diagram in My Engineering Main Project. We were Little Confused then. Somehow we managed it. Succeed  Back then me and my team is very new to this concept Eventually OR Accendentaly choose my career in VAR, 3D (https://scanse.io/) Technology, Lidar Because future is Full of Automation

Nice to see this diagram is still of some use.

Hola.
Con permiso de Rob, he traducido a Español el Pinout. Disfrutazlo.
Un saludo y gracias.


Hi.
With Rob's permission, I have translated the Pinout into Spanish. Enjoy it
Greetings and thank you.


Pinout DUE en Español: Download image (http://www.fantasystudios.es/arduino/images/arduinos/due/Due-pinout-A4-spanish-grande.jpg)

My Web AFPT - DUE: Arduino Facil Para Todos (http://www.fantasystudios.es/arduino/pages/Arduinos/due.html)

Thanks Manolofen, I've added it to post #1 so it's more accessible.

Rob

@graynomad, Indeed this old diagram is still in use. I am using it to compare to the Atmel (now Microchip) E70 Explained's "Ardunio" pinout set which was "claimed" to be compatible with Arduino Due R3, and it is NOT! With Microchip's takeover of Atmel this product is probably a dead horse (E70 MCU).
Note that many people/companies use a similar format for showing pinouts(see some of the Chinese flight controllers). Do you know of a modifiable template of your diagram? I'd like to make one for the SAM E70 Explained.
Thanks!

The original post has the drawing in editable formats, SVG and CDR. You should be able to use them as the base for your version.

Tks for share

based on the Atmel documentation A28 is pin 111

Sorry, I don't hang out here much these days and just got your PM. I'll look into it.

Rob

Thanks

Hi.

I made a library to easily enable debounce filter: DUE_Schmitt (https://github.com/NitrofMtl/DUE_Schmitt)

Here all pin schmitt capable:

A0 to A11
canRX
digital: 0, 2, 5, 7, 8, 9, 11,12,13, SDA1, SCL1
digital: 4 ( on port C.26 )
digital: 10 ( on port A.28 )
digital: 22 to 31
digital 33 to 40
digital 42, 43, 45, 46, 47, 49, 50, 51, 52

maybe it could be added to the diagram.

Regards.

Nitrof