AT90USBxxx Dual role demonstration with file system

License

Use of this program is subject to Atmel's End User License Agreement.

Please read file lic_page for copyright notice.

Description

This embedded application code illustrates how to implement a dual role application with the AT90USBxxx controller.

As the AT90USBxxx implements a device/host usb controller, the embedded application can operates in one of the following usb operating modes:

• USB device
• USB reduced host controller

About the source code

This source code is usable with the following compilers:

• IAR Embedded Workbench (5.11A and higher)
• AVRGCC (WinAVR 20080411 and higher).

Support for other compilers may required modifications or attention for:

• compiler.h file
• special registers declaration file
• interrupt subroutines declarations

About the sample application

By default the demonstration is preconfigured for dual role USB application. It means that the code generated allows to operate as a device or a host depending on the USB ID pin:

• Attached to a mini B plug (ID pin unconnected) the application will be used in the device operating mode. Thus the application can be connected to a system host (PC) to operate with the three modes:
  • Usb mouse (using joystick)
  • Usb mass storage (on board dataflash))
  • Usb generic HID (A pc side applications allow to communicate with the embedded firmware, see USB HID Generic PC demos).
• Attached to a mini A plug (ID pin tied to ground) the application will operate in reduced host mode. This mode allows to connect one of the following devices:
  • a standard USB mouse
  • a USB mass storage device
  • an AT90USB controller in USB DFU Bootloader
  • or another application in B device mode.
    
• In both modes, the STK525 can be connected to a serial terminal, where the user can acess a simple command line interperter (ushell) to perform file system access. To use the simple shell application, connect the STK525 to a serial terminal emulator (like Hyperterminal under windows systems). The serial port settings are:
  • 57600 bauds
  • 8bits data, no parity
  • no flow control To use the application, the SK525 should be configured to be self powered (see STK525 hardware manual).

Using the USB device mode

Connect the STK525 to a PC host system with a miniB (STK525 side) to plugA (PC host) cable

• The joystick allows to move the mouse cursor
• A removable drive allows to read/write files on the on-board data flash memory (for example to read write the "IN", "OUT" directories and "FIRMWARE.HEX" mentionned in the section Using the USB host mode )
• The ATMEL hid AT90USBxxx pc side application allows to read temperature, turn ON/OFF leds get joystick events and potentiometer position

Using the USB host mode

Connected in host mode (miniA plug inserted), the behavior of the application depends on the device type connected:

• Connected to a standard USB mouse, the mouse movements are visible with the LEDs.
• Connected to a USB Mass Storage Device (MSD), files can be exchange with the on-board data flash disk and the MSD.
  • The right direction of the joystick allows to read the content of a MSD "OUT" directory and to write it to an on-board data flash "IN" directory.
  • The left direction of the joystick allows to write the content of an on-board data flash "OUT" directory to a MSD "IN" directory.
• Connected to an AT90USB DFU bootloader, the left direction of the joystick allows to download a new firmware in the AT90USB device connected. The firmware is an Intel Hex file named "FIRMWARE.HEX" located to the root directory of the on-board data flash drive.

Using the shell terminal

Connected to a serial terminal emulator the Usheel command line interpreter allows to:

• Navigate in the file system (both on-board dataflash and a USB mass storage device connected to the USB host interface). The following commands are supported:
  • a: , b: ... goto selected drive
  • cd dirname
  • ls
  • touch filename
  • append filename
  • mark: bookmark current directory
  • cp filename: copy filename to bookmark
  • rm filename: erase file or empty directory
  • format drivename, with drivename: a, b...
  • deltree dirname
  • cat filename
  • cd..
  • mount disk(a,b,..)
  • mkdir dirname
  • disk: get number of drives
  • goto: goto bookmark
  • df: get free space information
  • cat filename
  • rm*: rm *
• Perform DFU commands with an AT90USB DFU device bootloader connected to the USB host interface
  • dfu_erase
  • dfu_prog filename: donwload the filename hex file into
  • dfu_start: Start the new application loaded the connected AT90USB
• Get information about the connected device and misc commands
  • lsusb
  • suspend: suspend USB bus activity
  • resume: resume USB bus activity
  • reboot: reset the application

For more information about File System module see File System

Architecture

As illustrated in the figure bellow, the application entry point is located is the main.c file. The main function first performs the initialization of a scheduler module and then runs it in an infinite loop. The scheduler is a simple infinite loop calling all its tasks defined in the conf_scheduler.h file. No real time schedule is performed, when a task ends, the scheduler calls the next task defined in the configuration file (conf_scheduler.h).

The sample dual role application is based on several different tasks:

• The usb_task (usb_task.c associated source file), is the task performing the USB low level enumeration process in device or host mode. Once this task has detected that the usb connection is fully operationnal, it updates different status flags that can be check within the high level application tasks.
• The storage task performs SCSI bulk only protocol decoding and performs flash memory access.
• The hid task performs the high level device application operation. Once the device is fully enumerated (DEVICE SETUP_SET_CONFIGURATION request received), the task checks for received data on its OUT endpoint and transmit data on its IN endpoint.
• The mouse task performs mouse events decoding and report construction to the USB host.
• The host mouse task manage events received from the USB mouse connected to display mouse activity on LEDs
• The host_ms_task manages the Device Mass Storage interface connected to shell commands
• The host_dfu_task manages the AT90USB DFU bootloader connection. When joy is up and left, the task load the FIRMWARE.HEX file from DataFlash to DFU Device.
• The ushell_task manages the terminal commands process

---