Benito: My first at90USB162 project.

Introduction.

The Benito Board is an at90USB162 board intended for use in programming and communicating with microcontrollers which have serial based bootloaders.

Among those are the Phillips lpc21xx series ARM chips, the Dallas Semiconductor, DS500x family and Atmels using any number of STK500 compatible bootloaders.

In the case of the Atmel and Phillips chips, a reset pulse is required to put the device into programming mode. A logical trigger for this pulse is the DTR signal which is pulled low when the computer begins to talk to a given device.

Background

Recently on avrfreaks.net….

Smileymicros wrote:

Now that they have the AT90USB82 for $2,17 each per hundred at DigiKey, I’m forced to reconsider. Why the f*ck would I continue using the FTDI part which costs $3.89 each per hundred?Smiley

It was not the first time I had had this question posed. Paul Stoffregen was talking about the new at90usb82/162 chips a few months back, its cheaper than the ftdi232 and has at least 2 driverless public usb-serial implementations: Dean Camera’s and Atmel’s. The best part is that it has a built in usb based bootloader and its a fully programmable AVR microcontroller. I thought it would be perfect to replace the ftdi ft232 series chips and to build an stk500 programmer with built in usb to boot. It seemed like the thing to do for many reasons.

Hardware

The sample code from both Atmel and MyUSB are based mostly on the AT90USBKey so I started with the schematic from that and cut out everything that I didn’t need. (a careful rereading of the datasheet says I am missing a 1uf cap here can you find it?).

A little hard to read

Click for larger image.

Compared to the the ftdi boards I have been working on the parts count is pretty high but I am banking on flexibility to make it worth while.

board positive

Click for link to positive at 600%

For the prototype I used my usual 1.5 sided board technique where the ground plain is brought to the top of the board and the alignment can be off by a couple of mm. The leds are some super bright ones in a plcc4 package that I have several hundred of. The pads in the eagle library for the are HUGE. I turned over the eagle files to Monty Goodson of bittybot.com who has lots of experience at getting things to be small so hopefully the final board will be a lot smaller.

In the mean time feel free to use the Positive image above to create your own board

The Programming Header

At the moment I have a very Avr centric view of the universe. For that reason the programming header that made the most sense was a combination of a serial connection with the 6 pin isp connection. For target boards based on other processors such as the DS5000 and the LP21xxx the SPI pins can be repurposed and the software adjusted accordingly.

Using the built-in boot-loader

When you get power, usb, crystal, reset and hwb wired you can enter the chips usb boot-loader by holding HWB low during reset. If you have a mac like me and look look at the usb section of your system profiler you should see the following:

device AT90USB162DFU:Version:    0.00

Bus Power (mA):    500

Speed:    Up to 12 Mb/sec

Manufacturer:    ATMEL

Product ID:    0x2ffa

Serial Number:    1.0.5

Vendor ID:    0x03eb

You can now program the chip using FLIP if you are running winblows (sic) or dfu-programmer from sourceforge http://dfu-programmer.sourceforge.net/DFU stands for Device Firmware Update.

Running dfu-programmer looks like this.

$ dfu-programmer at90usb162 erase$ dfu-programmer at90usb162 flash --debug 20 USBtoSerial.a90

target: at90usb162

chip_id: 0x2ffa

vendor_id: 0x03eb

command: flash

quiet: false

debug: 20

device_type: AVR

------ command specific below ------

validate: true

hex file: USBtoSerial.a90

Validating...3182 bytes used (25.90%)

$ dfu-programmer at90usb162 start

I made the .a90 file from my modifications to Dean Camera’s sample code (to be described later) with the following voodoo.

avr-objcopy -R .eeprom -O ihex USBtoSerial.elf USBtoSerial.a90

Now on top of the blinking lights on the board an entirely different device is attatched to my usb port.


The “Driverless” Serial Device.

The USB standard is a lot about throwing several thousand dollars down so you can play as a member. Fortunately for the rest of us there are a couple of generalized devices that have generic definitions. one is the HID (human interface device) and the other is a CDC communications device under the CDC a class of devices is defined which looks like a modem (ACM). If a device says its one of these and acts accordingly most well developed operating systems will load a generic driver for them and just work. (and then there is windows which still requires a .inf file to load the generic driver). 

Atmel’s Code Samples.

As much as I love Atmels processors it is a constant source of irritation that their best tools are only made avaliable on the windows operating system. It was nice to see that the sample code for Atmel was avaliable for avr-gcc and I ran it up only to find myself picking through 5 layers of slashes “\”. This is not just a preference it is bad coding practice. (to quote an old co-worker of mine “Its Rubbish — Bin it!)

So I ran it up made it work and started looking at alternatives.

This lead me to Dean Camera’s MyUSB library. Though it is still in development it is still easier to understand and work with than Atmel’s Code.

crtusb162.o

When compiling Atmel’s CDC code I wound up with a linker error complaining that crtusb162.o did not exist After recommending AVRMackPack for nearly 6 months I thought I had found my first bug. After rebuilding my own version of tool chain and digging around I found that it is a known bug and should be fixed in future releases. In the mean time the fix is easy. Either copy it from the avr3 library into your source or link the directory to avr35 where the linker should find it.

#cd  /usr/local/AVRMacPack/avr-4/lib/#ln -s avr3 avr35

Building the Firmware with MyUSB

The firmware linked below under resources implements a USB serial port which produces a 2ms *reset pulse instead of DTR. It is based on the USBtoSerial Demo from version 1.3.2 of the MyUSB library. To build it unpack the MyUSB library into your work area. Then under the MyUSB library directory create a directory called Projects and unpack the Benito firmware into the Projects directory. If you have xcode (v>2.4) and AvrMacPack you can open the project and build it. Other platforms will have to adjust the Makefile to match their environment. the “make program” target defined in the make file uses the dfu-programmer utility so you can program the device using its built in bootloader.

Results:

By using Dean Camera’s MyUSB library I was able to create a serial programmer which plugs into Linux and OSX and it “just works”. I was able to produce the reset pulse in firmware and it continued to “Just Work”. You can see it above plugged into a modern device RBBA board running Limor Frieds AdaBoot. I was able to do this in a very short amount of time and while the hardware is slightly more complicated than the ft232 boards the cost at 100 boards is actually cheaper.

Moving Forward

In the photo below you can see my prototype boards (both sides) next to an ft232rl based programmer with a capacitor based “auto reset hack”. The board on the bottom shows the connection between an at90USB82 and a phillips Arm chip.

On the Atmel side the next step is to implement an STK500 based programmer using the SPI port on the at90USB162. I expect that this will be a farely easy adaptation however I may revisit the DS500x chips that I have first and work out the best way to switch between the software modes. first. From there it would also be a no brainer to adapt the firmware for the lpc21xx chip pictured above.

Resources



				
				

			
  1. Hi Feurig!

    Glad to see you’re finding my USB stack library useful. Just a minor correction in the post; you’ve written my name as “Dean Cameron” twice rather than “Dean Camera”.

    Cheers!
    – Dean

  • Donald Delmar Davis Says:

    Sorry Dean,

    This has been corrected. I have been kind of sketching things out here and then posting them to DorkbotPDX when I am ready to share them with the world. I noticed that it gets more correct as I move along.

    I don’t suppose suppose this is a good time to ask you about how you would impliment a software DTR pulse.

    feurig (ddd7 on avrfreaks)

  • Leave a Reply

    You must be logged in to post a comment.