Difference between revisions of "Project:YAAC"

From London Hackspace Wiki
Jump to navigation Jump to search
m (Reverted edits by Ytogohiga (Talk) to last revision by Danielsikar)
Line 1: Line 1:
----
 
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 
----
 
=[http://uwujojedeh.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]=
 
----
 
=[http://uwujojedeh.co.cc CLICK HERE]=
 
----
 
</div>
 
 
Project maintained by Daniel Sikar ~/ dsikaratgmaildotcom.
 
Project maintained by Daniel Sikar ~/ dsikaratgmaildotcom.
  
Line 18: Line 10:
 
==== Overview ====
 
==== Overview ====
  
This is something I developed above the 20/20 Archery Club, at the previous London Hackspace address. It is based on three projects, the [http://dorkbotpdx.org/wiki/benito Benito 7], [http://www.makestuff.eu/wordpress/?page_id=569 Nanduino] and [http://www.pjrc.com/teensy/ Teensy]. You can run sketches on this device, though getting to burn actual code onto the YAAC is not as straightforward as with *real* Arduinos.&lt;br&gt;
+
This is something I developed above the 20/20 Archery Club, at the previous London Hackspace address. It is based on three projects, the [http://dorkbotpdx.org/wiki/benito Benito 7], [http://www.makestuff.eu/wordpress/?page_id=569 Nanduino] and [http://www.pjrc.com/teensy/ Teensy]. You can run sketches on this device, though getting to burn actual code onto the YAAC is not as straightforward as with *real* Arduinos.<br>
&lt;br&gt;
+
<br>
 
On the host side, for this specific project, I am running Ubuntu 10.04. It will probably run on other Debian based distributions without hickups. I don't know about Macs. I have burnt code on the YAAC running Windows Vista SP3 on the host, using the AVR toolchain - as per Benito 7 and Nanduino recipes. I don't know about running the Arduino IDE on Windows (TODO - find out).
 
On the host side, for this specific project, I am running Ubuntu 10.04. It will probably run on other Debian based distributions without hickups. I don't know about Macs. I have burnt code on the YAAC running Windows Vista SP3 on the host, using the AVR toolchain - as per Benito 7 and Nanduino recipes. I don't know about running the Arduino IDE on Windows (TODO - find out).
  
Line 85: Line 77:
 
== Software required ==
 
== Software required ==
  
* Arduino IDE - to compile sketches.&lt;br&gt;
+
* Arduino IDE - to compile sketches.<br>
* Teensyduino Arduino IDE addon - to list the Teensy on the Arduino IDE.&lt;br&gt;
+
* Teensyduino Arduino IDE addon - to list the Teensy on the Arduino IDE.<br>
* Teensy loader - the Teensy GUI, this actually needs to be running otherwise the Arduino IDE will not compile sketches.&lt;br&gt;
+
* Teensy loader - the Teensy GUI, this actually needs to be running otherwise the Arduino IDE will not compile sketches.<br>
* dfu programmer - to burn the actual code (hex file) onto the AT90USB162.&lt;br&gt;
+
* dfu programmer - to burn the actual code (hex file) onto the AT90USB162.<br>
  
 
=== Installation ===
 
=== Installation ===
Line 125: Line 117:
 
which should generate a list such as:
 
which should generate a list such as:
  
Bus 005 Device 002: ID 044e:300d Alps Electric Co., Ltd Bluetooth Controller (ALPS/UGPZ6)&lt;br&gt;
+
Bus 005 Device 002: ID 044e:300d Alps Electric Co., Ltd Bluetooth Controller (ALPS/UGPZ6)<br>
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;br&gt;
+
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader&lt;br&gt;
+
Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader<br>
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;br&gt;
+
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
(...)&lt;br&gt;
+
(...)<br>
  
The YACC at this point should not be listed because the device needs to be reset first.&lt;br&gt;
+
The YACC at this point should not be listed because the device needs to be reset first.<br>
Push the reset button for 5 seconds (I count five elephants) then run lsusb again.&lt;br&gt;
+
Push the reset button for 5 seconds (I count five elephants) then run lsusb again.<br>
  
 
$ lsusb
 
$ lsusb
  
This time, all being well, an Atmel device should enumerate:&lt;br&gt;
+
This time, all being well, an Atmel device should enumerate:<br>
  
Bus 005 Device 002: ID 044e:300d Alps Electric Co., Ltd Bluetooth Controller (ALPS/UGPZ6)&lt;br&gt;
+
Bus 005 Device 002: ID 044e:300d Alps Electric Co., Ltd Bluetooth Controller (ALPS/UGPZ6)<br>
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;br&gt;
+
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader&lt;br&gt;
+
Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader<br>
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;br&gt;
+
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub&lt;br&gt;
+
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
'''Bus 002 Device 003: ID 03eb:2ffa Atmel Corp.'''&lt;br&gt;
+
'''Bus 002 Device 003: ID 03eb:2ffa Atmel Corp.'''<br>
 
(...)
 
(...)
  
Line 150: Line 142:
 
=== Running sketches and generating hex code ===
 
=== Running sketches and generating hex code ===
  
At this point in time, Serial.print() does not work on this setup so there is not a lot of feedback from the device.&lt;br&gt;
+
At this point in time, Serial.print() does not work on this setup so there is not a lot of feedback from the device.<br>
At any rate, the sketches are run on the Arduino IDE, as per normal usage, piggybacking on the Teensy to make the Arduino IDE believe there is indeed a compatible device attached. This will generate a hex file in your /tmp directory. That is the code that needs to be burnt into the YAAC.&lt;br&gt;
+
At any rate, the sketches are run on the Arduino IDE, as per normal usage, piggybacking on the Teensy to make the Arduino IDE believe there is indeed a compatible device attached. This will generate a hex file in your /tmp directory. That is the code that needs to be burnt into the YAAC.<br>
  
 
=== Burning hex code ===
 
=== Burning hex code ===
  
From the prompt run:&lt;br&gt;
+
From the prompt run:<br>
  
 
  $ sudo dfu-programmer at90usb162 erase
 
  $ sudo dfu-programmer at90usb162 erase
  $ sudo dfu-programmer at90usb162 flash --debug 20 /tmp/build&lt;...&gt;.tmp/&lt;filename&gt;.cpp.hex  
+
  $ sudo dfu-programmer at90usb162 flash --debug 20 /tmp/build<...>.tmp/<filename>.cpp.hex  
 
  $ sudo dfu-programmer at90usb162 start
 
  $ sudo dfu-programmer at90usb162 start
  

Revision as of 00:16, 24 November 2010

Project maintained by Daniel Sikar ~/ dsikaratgmaildotcom.

YAAC



QR code


Project Brief

Summary

YAAC - Yet Another Arduino Clone. Based on Atmel's AT90USB162. Low part count. Cheap to build.

Overview

This is something I developed above the 20/20 Archery Club, at the previous London Hackspace address. It is based on three projects, the Benito 7, Nanduino and Teensy. You can run sketches on this device, though getting to burn actual code onto the YAAC is not as straightforward as with *real* Arduinos.

On the host side, for this specific project, I am running Ubuntu 10.04. It will probably run on other Debian based distributions without hickups. I don't know about Macs. I have burnt code on the YAAC running Windows Vista SP3 on the host, using the AVR toolchain - as per Benito 7 and Nanduino recipes. I don't know about running the Arduino IDE on Windows (TODO - find out).

Yak.jpg

Logo placeholder.

Motivation

1. Gaining experience with SMD components (AT90USB162).

2. Building a cheap device that can be programmed via USB.

3. Working with Atmel microcontrollers.

4. Being able to tap into the growing Wiring code examples.

Prototype

With the reset button on the right edge of the bread board.

Yaac.jpg

Schematic

Basically, the AT90USB162, a couple of connectors, a 16MHz Oscillator, a few capacitors and a reset button. TODO upload the Eagle Cadsoft files to Github.

Yacc schematic.jpg

PCB

Both layers

Yacc pcb.jpg

The YAAC, one USB Type B socket, one reset button, one crystal oscillator, five capacitors, one AT90USB162 and a couple of pin strips.

Bottom layer

Yaacbottom.jpg

Top layer

Mirrored to match bottom layer, when turned over face to face.

Yaactop.jpg

BOM

Part Value           Device          Package      Description                         
C3   22p             C-US050-024X044 C050-024X044 CAPACITOR, American symbol          
C4   22p             C-US050-024X044 C050-024X044 CAPACITOR, American symbol          
C5   1uF             CPOL-USE1.8-4   E1,8-4       POLARIZED CAPACITOR, American symbol
C6   10uF            CPOL-USE1.8-4   E1,8-4       POLARIZED CAPACITOR, American symbol
C7   220nF           C-US050-025X075 C050-025X075 CAPACITOR, American symbol          
Q1   16MHz           CRYSTALHC49S    HC49/S       CRYSTAL                             
S1                   10-XX           B3F-10XX     OMRON SWITCH                        
SL1                  M16             16P          AMP QUICK CONNECTOR                 
SL2                  M16             16P          AMP QUICK CONNECTOR                 
U1   AT90USB162-16AU AT90USB162-16AU VQFP32                                           
X1                   USB-B-H         USB-B-H      USB Connectors

Software required

  • Arduino IDE - to compile sketches.
  • Teensyduino Arduino IDE addon - to list the Teensy on the Arduino IDE.
  • Teensy loader - the Teensy GUI, this actually needs to be running otherwise the Arduino IDE will not compile sketches.
  • dfu programmer - to burn the actual code (hex file) onto the AT90USB162.

Installation

  • Arduino
$ sudo apt-get update
$ sudo apt-get install arduino
$ arduino
  • Teensyduino
$ wget http://www.pjrc.com/teensy/teensyduino-0018
$ chmod +x teensyduino-0018 
$ ./teensyduino-0018
  • Teensy loader
$ wget http://www.pjrc.com/teensy/teensy.gz
$ gunzip teensy.gz
$ chmod +x teensy
$ ./teensy
  • dfu programmer
$ sudo apt-get install dfu-programmer

Programming the YAAC

Enumerating

Once connected, from the prompt run lsusb (list USB devices):

$ lsusb

which should generate a list such as:

Bus 005 Device 002: ID 044e:300d Alps Electric Co., Ltd Bluetooth Controller (ALPS/UGPZ6)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
(...)

The YACC at this point should not be listed because the device needs to be reset first.
Push the reset button for 5 seconds (I count five elephants) then run lsusb again.

$ lsusb

This time, all being well, an Atmel device should enumerate:

Bus 005 Device 002: ID 044e:300d Alps Electric Co., Ltd Bluetooth Controller (ALPS/UGPZ6)
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 03eb:2ffa Atmel Corp.
(...)

That is the YAAC.

Running sketches and generating hex code

At this point in time, Serial.print() does not work on this setup so there is not a lot of feedback from the device.
At any rate, the sketches are run on the Arduino IDE, as per normal usage, piggybacking on the Teensy to make the Arduino IDE believe there is indeed a compatible device attached. This will generate a hex file in your /tmp directory. That is the code that needs to be burnt into the YAAC.

Burning hex code

From the prompt run:

$ sudo dfu-programmer at90usb162 erase
$ sudo dfu-programmer at90usb162 flash --debug 20 /tmp/build<...>.tmp/<filename>.cpp.hex 
$ sudo dfu-programmer at90usb162 start

Note, the device must be reset before proceeding with the 3 steps above. Also, AFAIK, you must be root to access the USB device. If you forget sudo, strange things might happen e.g. code not burning, device not erasing and starting, etc, though no error message will be given - it will fail silently.

Potential improvements

Lots of room for improvement:

  • Getting Serial.print() to work
  • Getting the actual YAAC listed on the Arduino IDE, instead of the Teensy.
  • Burning code straight from the Arduino IDE onto the YAAC, though this would required major roadworks, as the current FTDI chip, which deals with the Arduino's USB protocol, would have to come out of the loop. Why not use the FTDI, and do a straight clone? Because it increases the cost.
  • Use all SMD components, doubled sided board, shield compatible format.