Errors in Due board/schematic files

Adding another mystery here:

The Due .sch and .brd files show IC10 up in between the two header rows.

A Due I ordered and received this week has IC10 in the lower left near the power jack.

Now I'm beginning to wonder how many other small inconsistencies are present in the files, and whether the files represent a viable circuit at all. I built a board using them and I've been trying to get it to work for weeks with no luck.

I'm trying to debug my own board based on the due schematics. So I made the mistake placing a 12MHz cristal for 16U2.
Now I'm waiting 16Mhz one. At least, the SAM3X8E is moving from the JTAG port, AtmelStudio, pwm_led_example.c + SAMICE.
One thing I'm wondering is 4pin "DEBUG" connector. maybe SWD ports but doesn't work. even it's white dot mark doesn't mean The '1' pin.

@michaeluna
That was reported soon after the Due was released, no reasonable reason (IMO anyway) was offered for the downloadable files being different to the production boards.

@Aiekakiku
The schematics are wrong WRT that crystal and at least on other item (that doesn't affect anyone making a similar board).

All in all it's clear that the offered "design files" are not the exact files used to create the production board.

I built a board using them and I've been trying to get it to work for weeks with no luck.

Do you want to share your schematics? I've only designed a SAM board so far not actually built it, but I may spot something.

Re the debug connector, AFAIK you need to use JTAG to enter SWD mode anyway so I'm not sure what use it is. I may be wrong on that but that's how I interpret the data sheet.


Rob

My own board based on the due schematic can be recognized by arduino 1.5.2 afetr replacing 12MHz cristal with 16MHz.
then I can write down Blink sketch on it. It works, but I feel something wrong around the reset circuit.

but the Arduino IDE consistently says it's unable to find a device on that COM port.
Actually I got this message. then reset the board and it come to be able to write sketch. something wrong.

PS. 'DEBUG' connector worked, JLink Debuger requirs one more pin ' Vref ' .

I think I found something. R23 10K on MASTER_RESET signal. It's not good. In my memmory. NRSTB pulled up inside cpu with 15k orhm.

So 16U2 can't draw the signal down to the graund. Acturally it saw it dwon to half level. After short the R23, my own board is smoosely recognized and recieve the scketch and move correctly.

But it causes another problem. Maybe short is not good. Do I need 1k or some resistor instead? or 16U2(22) RESET_CMD pin is Open Drain?

You might have a point there. The internal pullup is a nominal 15k and the MASTER-RESET signal is driven through a series 10k (R23 as you say), that forms a voltage divider that will be about .94V on the reset pin when asserted by the 16U2.

I can't find the valid voltage levels for the NRSTB pins but the max Vil for a standard pin is 0.3 x VDDIO, or .99V.

That's pretty close and not a great choice given that the pullup resistor can range from 10 to 20k. Of course NRSTB may have a different threshold.

Can you verify that R23 is actually 10k?

The only reason I can think of for having R23 at all is to protect the 16U2 in the case of it asserting MASTER-RESET at the same time as the reset PB was pressed. Therefore I assume that pin 22 on the 16U2 is not open drain.

I would replace the 10k with a 1k as you say, just to be on the safe side.


Rob

I can't find out the acutual value of R23 on the real due board. because it doesn't have silk name on the board.
I looked into the Arduino-usbserial.c. It says

void setResetPin(bool v) {
/* Target /RESET line /
....
/
INACTIVE => set as INPUT (internal pullup on target /RESET keep it at 3.3v) */
...
}

Maybe, maybe it would never drive the reset Hi. I'm not sure.

OK, sounds like something put in as a "maybe we'll use it one day" feature that is not used.

If that's the case this is another discrepancy between the design files and the real thing.

I'd say you don't need R23 at all.


Rob

Graynomad, you're a helpful dude. Thank you so much for your expertise.

Here's my schematic. I literally just opened the Due release files and added some of my own circuitry to it to make this musical instrument I've been designing.

I have a question related to JTAG here, because that's the next avenue I'm exploring to figure out what's up with my boards.

The 10-pin connector the JTAG on the Due boards has 1mm spacing, which is super small. I'm looking high and low for the connector cable to attach to those pins and I'm not finding it anywhere. Maybe it's because I din't know what it's proper name is? In any case, do any of you have a link to the type of cable that connects to those pins?

In my next revision of the board I'm switching that header to the standard size. And making both USB jacks identical, that was a huge headache as well...

The spacing is actually 1.27mm or .05", they are reasonably common although nowhere near as much as the .1" version.

Or if you need to convert to the standard 20-pin JTAG this should work

And making both USB jacks identical

So they should both be micro AB sockets then I assume.


Rob

@michaeluna
I gather that schematic is not yet finished? There are a lot of unconnected nets.

Where do all the debounced switch inputs go?

EDIT: I also juts noticed that none of the wire joins have dots, that normally means they are not connected.


Rob

Michaeluna,

From going over the DUE schematic some time ago, I remember questioning the existence of T2. It is a P-channel fet that always seems to be turned on. It doesn't harm anything I suppose. However, it would never turn off unless the 5V power port suddenly became negative. I've seen uses like this for battery-polarity reversal protection. I'm not sure how it applies here though.

I had some other minor comments that can be found here:
http://forum.arduino.cc/index.php?topic=146574.msg1101238#msg1101238

Also, when it is obvious, I think that judicious use of power-ports and net-labels make a schematic easier to read, and preferable over crossing wires (i.e. the bank of switches, digital pots, and so forth). If you're trying to convey special pcb grouping, routing, or operation with the display of the wires on the schematic, then a few words on the schematic print would go a long way to explain your intentions.

Rob is right-on about the junction dots.

Best of luck with your project.

Chris

I would like to confirm the post from Aiekakiku (thanks!) Errors in Due board/schematic files - #12 by Aiekakiku - Arduino Due - Arduino Forum
R23 is the wrong value. It should be 1K

On my DUE it was preventing the 16U2 from resetting the SAM3X and causing the "No device found on COMxx" errors.
It also prevented the SAM3X from being reset after successfully loading a sketch.
I suspect that many others have this same problem on the DUE.

my related post with details: Due appears as COM6 port but gives error "No device found on COM6" on upload - #9 by system - Arduino Due - Arduino Forum

Update: See also Due appears as COM6 port but gives error "No device found on COM6" on upload - #11 by system - Arduino Due - Arduino Forum for the necessary 16U2 firmware fix


Andrew

i think this thread should ''official'' and all the differences between reference schematic and real board should be posted here

@michaeluna... I've been doing schematic drawings for nearly 50 years and "That" is the most unique and difficult to follow schematic drawing I've seen yet.
That having been said and it wasn't intended as a criticism by any means your work, as far as it goes is OK.
Remember always that a schematic is a road map first and in many cases additional material not usually included in the BOM is represented on the schematic.
Individual circuits like the Power Supplies, Controller and I/O circuitry are usually in separate area's... The Uno drawing is an example of one that is close to the ideal.
I used a high end cad package when I last worked (2008) and I do realize that struggling with a 'difficult' free package has it's special challenges, ones you have done well with.
My best piece of advice would be to study how others (professionals) compose their drawings and try to incorporate (copy the style) of the most legible and understandable ones into your style.
A Schematic drawing is an engineering document used for many different purposes and by many different people. All the way from the poor techie that has to use it for troubleshooting to the people who actually order parts and use the schematic as a means of verifying the BOM for accuracy... of parts and sometimes the count as well.
And let's not forget the other engineers that may need to use the drawing as well... Great work for a beginner.

Doc

I have found a group label inconsistencies in the schematic. The naming of the AD inputs is flipped in the schematic.

Sources: Atmel SAM3X datasheet 23-Mar-15
Arduino DUE Schematic (download fom site dated ?)

Peripheral from pg.18
Datasheet Labels from pg.40

Pin # Peripheral Label (Datasheet) Label (Schematic)

78 PA16 AD7 AD0
79 PA24 AD6 AD1
80 PA23 AD5 AD2
81 PA22 AD4 AD3
82 PA6 AD3 AD4
83 PA4 AD2 AD5
84 PA3 AD1 AD6
85 PA2 AD0 AD7

ADC Channel 7 is A0
…………………………….
ADC Channel 0 is A7

It's weird…but correct. :confused:

Members

I noticed that the DUE .sch has 2 pins marked as SS0/PWM10. Please see photo. Why is this? What are they used for?