Review of Arduino Due

Table of contents

RoadTest: Arduino Due

Author: awneil

Creation date:

Evaluation Type: Independent Products

Did you receive all parts the manufacturer stated would be included in the package?: True

What other parts do you consider comparable to this product?: Broadly Comparable to SAM4S XPlained

What were the biggest problems encountered?: The translation from "Arduino-speak" to "normal" terminology. But that was rxpected!

Detailed Review:

As an “old hand” embedded systems developer with over 25 years experience, I have thought that Arduino sounds a useful hardware platform – but have no interest in learning its rather idiosyncratic software language & environment. Therefore the object of this Road Test was to investigate using the Arduino Due as plain, ordinary “bare-metal” development board – without any of the Arduino stuff.

 

Although not trivial, the task was not really any harder than expected. There were no showstoppers.

 

I was able to use the free Keil MDK "Lite" edition to create standard 'C' programs, download and debug using a uLink-2 in the normal manner

 

image

 

The full report is in the attached MS-Word document.

 

The attached MS-Excel workbook contains the information deduced about pinouts & connections.

 

The attached ZIP file contains the final source code & uVision-4 Project described in the report.

 

All files are supplied "AS IS" without warranties of any kind; use entirely at own risk.

Anonymous
Parents
  • As a long time Keil / Real View jockey,  I decided to play with the due and take a look see.  I too used the base µVision project  SAM3X-EK \Blinky in the Keil distribution and ran into a "issue" that led me to this site. To wit:

    1. Everything seems to run out of box, hooked a poti to the due's A6 Input and all was as expected ,  the Output to the term via  due's USB prog. port  was fine: e.g.   as I turn the poti:

    AD value: 0x0008

    AD value: 0x0008

    AD value: 0x01E7

    AD value: 0x0C3C

    AD value: 0x0FFF

    AD value: 0x0FFF

    So ....

    2. Started to "play" with the UART, and...hum...no input char is ever received rather, the RHR always returns 0 whenever  the keyboard is hit.  OK to make a long story short...I attached a USB/Serial to the TX0-RX0 + GND, opened another term...!!!.. and it works, this time with  each opened term repeating the I/O of the other term-:)))  --pull the lines to TX0-RX0 ( due PIN0 / 1 ) and only Tx on the program port USB reattach the TX0/RX0 works.  I then recompiled to use USART0 ( due 18/19 ) !BINGO! works with no echo to the USB prog. port.

     

    I should be appreciative if any one could assist me in understanding this behaviour.

     

    BTW - downloaded a sketch reading the port and that work as expected.

     

    Update- Situation resolved.  In order to rec chars on the Uart-USB  Prog. Port,  pull ups  must be enabled-:)

    PIOA->PIO_PUER   =0x00000300;

     

    I also have most of the other components DAC, SPI etc. running under Keil-J-link, and it is much more convenient than any other IDE. 

Comment
  • As a long time Keil / Real View jockey,  I decided to play with the due and take a look see.  I too used the base µVision project  SAM3X-EK \Blinky in the Keil distribution and ran into a "issue" that led me to this site. To wit:

    1. Everything seems to run out of box, hooked a poti to the due's A6 Input and all was as expected ,  the Output to the term via  due's USB prog. port  was fine: e.g.   as I turn the poti:

    AD value: 0x0008

    AD value: 0x0008

    AD value: 0x01E7

    AD value: 0x0C3C

    AD value: 0x0FFF

    AD value: 0x0FFF

    So ....

    2. Started to "play" with the UART, and...hum...no input char is ever received rather, the RHR always returns 0 whenever  the keyboard is hit.  OK to make a long story short...I attached a USB/Serial to the TX0-RX0 + GND, opened another term...!!!.. and it works, this time with  each opened term repeating the I/O of the other term-:)))  --pull the lines to TX0-RX0 ( due PIN0 / 1 ) and only Tx on the program port USB reattach the TX0/RX0 works.  I then recompiled to use USART0 ( due 18/19 ) !BINGO! works with no echo to the USB prog. port.

     

    I should be appreciative if any one could assist me in understanding this behaviour.

     

    BTW - downloaded a sketch reading the port and that work as expected.

     

    Update- Situation resolved.  In order to rec chars on the Uart-USB  Prog. Port,  pull ups  must be enabled-:)

    PIOA->PIO_PUER   =0x00000300;

     

    I also have most of the other components DAC, SPI etc. running under Keil-J-link, and it is much more convenient than any other IDE. 

Children
No Data