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.

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.

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\instanceIn 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?

@CrossroadsYes 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.

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

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

Quote

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

Quote

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

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

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.

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.

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.

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