USB Add On - Revision history

Admin at 12:09, 13 February 2013

2013-02-13T12:09:34Z

Admin at 12:07, 13 February 2013

2013-02-13T12:07:00Z

Admin at 12:05, 13 February 2013

2013-02-13T12:05:42Z

Show changes

Admin at 12:04, 13 February 2013

2013-02-13T12:04:52Z

Admin at 12:04, 13 February 2013

2013-02-13T12:04:07Z

Admin: Created page with " === This page contains ..."

2013-02-13T12:02:40Z

Created page with "<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black"> === This page contains ..."

New page

<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">
=== This page contains the following errors: ===
<div style="font-family:monospace;font-size:12px">error on line 1 at column 36376: error parsing attribute name </div>
=== Below is a rendering of the page up to the first error. ===
</parsererror>

The USB Add On is a commercial add on which is available from the MCS Electronics Web Shop.

The CONFIG USB statement needs this add on. The add on is written in BASCOM BASIC mixed with assembler. Since the examples from Atmel were not really consistent, it took some effort to create reusable code. At a later stage, a number of routines will be moved to an assembler library.

The advantage of the BASCOM code is that it is similar to the C-code examples.

 

[[File:Notice.jpg|notice]]Please read this entire topic first before you start with experiments.

 

The Add On only supports the device mode. There is no support for host mode yet. In fact the add on is just the first step into USB support.

 

To use the USB Add on, unzip all the files to the SAMPLES\USB directory.

You will find three samples :
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| hid_generic-162.bas
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| virtcom-162.bas
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| hid_keyboard-162.bas
|}
</div>
 

The same samples are also provided for the USB1287.

 

And you will find the include file : usbinc.bas. It is not allowed to distribute any of the files.

 

Further, you will find a subdirectory named VB which contains a simple VB generic HID sample that uses the HIDX.OCX from the OCX subdirectory.

 

The PDF directory contains a PDF with a translation between PS2 scan codes and USB key codes.

 

The TOOLS directory contains the USBDEVIEW.EXE which can be used to display all USB devices,

 

The CDC-Driver directory contains the INF file you need for the CDC/Virtual COM port example.

 

The USB162 has a boot loader which can be programmed by USB using FLIP. BASCOM will also support this USB boot loader in version 1.11.9.2.

It is great for development but of course the boot loader uses some space which you probably need. The chip is also programmable via the normal way with the ISP protocol. when you do not use FLIP, and you erase the chip, the boot loader from Atmel is erased too! You can always reprogram the Atmel boot loader. But not using FLIP which depends on the boot loader.

 

For USB to work properly the chip needs a good oscillator. The internal oscillator is not good enough. For that reason, the USB162 module from MCS has a 8 MHz crystal. Your hardware should use a crystal or crystal oscillator too.

 

It is not the intention of MCS or the documentation to learn you everything about USB. There is a lot of information available from various sources. It is the goal of MCS to make it easy to use USB with your AVR micro. When there is enough demand for it, a special Wizard will be created to be able to generate HID applications.

 

 

= HID Keyboard =

Let's begin with a simple program. Load the hid_keyboard-162.bas sample and compile it. Use either FLIP or a different programmer to program the chip. Each program has some important settings.

 

Const Mdbg = 1                        ' add print to see what is happening

Const Chiddevice = 1                 ' this is a HID device

 

MDBG is a constant that can be set to 0 since all the print statements will use flash code. When you are new to USB and want to look at the events, it is good to have it turned on. You can view all events from the program.

cHIDdevice need to be set to 1 when the application is a HID device. Most of your own devices will be HID devices. But the virtual COM example uses a different USB class and in that program, the constant is set to 0.

 

These constants are used in the add on to keep all code generic for all applications.

Since not all USB chips have the same options, the code also checks which microprocessor is used.

The USB1287 is a kind of M128 with USB support. It supports host and device mode. The USB162 is a cheap host chip. It does not support the HOST mode and it does not have all registers found in the USB1287. It also can not detect when a device is plugged/unplugged.

Atmel solved this in the STK526 in a simple way that we recommend too : A voltage divider is connected to PORTC.4 which serves as a simple way to detect plug/unplug.

In the USB_TASK() routine you will find this code :

 

If Usb_connected = 0 And Pinc.4 = 1 Then              ' portc.4 is used as vbus detection on stk526

 

This is used with the STK526. If you want to use a different pin, you have to change PINC.4.

When you use the USB1287 this is not needed since the 1287 has a Usbsta register which can determine if a device is plugged or removed.

 

The USB program structure is always the same :
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="15" | 1.
| constants are defined that describe the end points, interfaces, vendor ID, product ID
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="15" | 2.
| you call a subroutine that initializes your variables
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="15" | 3.
| In a loop you call :
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="15" | 4.
| the generic USB_TASK routine so that the USB communication with the PC is executed
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="15" | 5.
| the specific task is called
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="15" | 6.
| your other code is called
|}
</div>
 

This is clear in the keyboard sample :

 

Print "init usb task"

Usb_task_init

Do

Usb_task

Kbd_task

'call your other code here

Loop

 

While the word Task might give you the idea that multi task switching is used, this is not the case! The USB_Task must be called by your code in order to process pending USB events. It will also find out if a device is plugged or unplugged. Events are handled in the background by the Usb_gen_int interrupt.

In the example the KBD_TASK is a user routine which is called in regular intervals. There is always the normal USB_TASK and there is an additional task specific to the program. In the generic-hid example this is the hid_task routine.

 

HID classes are simple to use since they do not require additional drivers. FTDI chips need additional drivers. But the Atmel USB chips do not need additional drivers since they use standard implemented HID classes.

 

When you compile the program and program it into a chip you are ready to test it.

When you use FLIP you need to switch to application mode so your device can be recognized by windows. Windows will show some info that your device is found. And after installing the driver, it will report that your device is ready to be used.

On the terminal emulator, press a space, and set the focus to notepad or the bascom editor. The text data from thekeys: label is send as if it was typed on a keyboard! You in fact created a HID-keyboard, or USB keyboard. The document translatePS2-HID.pdf contains HID key codes which are different then PS2 key scan codes.

 

When you do not have a terminal emulator connected you can also modify the program and connect a push button. Which makes more sense for a keyboard :-)

So modify the code into :  If Inkey() = 32 Or Pinb.0 = 0 Then 'if you press SPACE BAR or make PINB.0 low

Now you can test the code without the terminal emulator.

 

 

All USB programs are similar. You specify the number of end points , the interfaces and the class. There is a lot of information available at

[http://www.usb.org/home http://www.usb.org/home]

Atmel has a number of samples and you will find tools and info at various places.

MCS will publish some convenient tools too.

 

= FLIP =

The USB chips are programmed with a boot loader. This is very convenient since you do not need any hardware to program the chip. FLIP can be downloaded from the Atmel site.

URL : [http://www.atmel.com/dyn/resources/prod_documents/Flip%20Installer%20-%203.3.1.exe http://www.atmel.com/dyn/resources/prod_documents/Flip%20Installer%20-%203.3.1.exe]

The FLIP website you can find at : [http://www.atmel.com/dyn/products/tools_card.asp?family_id=604&family_name=8051+Architecture&tool_id=3886 http://www.atmel.com/dyn/products/tools_card.asp?family_id=604&family_name=8051+Architecture&tool_id=3886]

 

FLIP is a Java application. The BASCOM-IDE can use the FLIP software to program the chip too. But in order to use the FLIP programmer, you need to install FLIP first.

When FLIP is working, you can select FLIP from Options, Programmer, in order to program quickly without the FLIP executable.

On Vista there is a problem with loading some of the FLIP DLL's. In case you get an error, copy the FLIP DLL's to the BASCOM application directory.

You need to copy the following files :
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| atjniisp.dll
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| AtLibUsbDfu.dll
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| msvcp60.dll
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| msvcrt.dll
|}
</div>
 

You can run the flipDLLcopy.cmd file from the BASCOM application directory to copy these files.

The content of the command file :

copy "c:\program files\atmel\flip 3.3.1\bin\atjniisp.dll" .

copy "c:\program files\atmel\flip 3.3.1\bin\AtLibUsbDfu.dll" .

copy "c:\program files\atmel\flip 3.3.1\bin\msvcp60.dll" .

copy "c:\program files\atmel\flip 3.3.1\bin\msvcrt.dll" .

pause

 

The last line pauses so you can view the result.  Notice the . (dot) that will copy the file to the current directory, which is the reason that you need to run this file from the BASCOM application directory.

 

As with other programmers, you press F4 to program the HEX file into the chip. A small window will become visible.

A number of dialogs are possible:

 

[[File:Flip error wrongdevice.png|center|flip_error_wrongdevice]]

In this case, you try to program a chip which is not supported by FLIP. The Mega88 is not an USB chip so the error makes sense.

 

The next dialog informs you about a missing DFU device.

[[File:Flip reset.png|center|flip_reset]]

In this case, the boot loader is not found. You can run the boot loader by following the sequence from the dialog box.

In order to make this work, the HWB and RST input both need a small switch to ground.

When HWB is pressed(low) during a reset, the boot loader will be executed.

 

In the device manager you will find the USB device :

 

[[File:Usb dev manager.png|center|usb_dev_manager]]

 

When you have a different chip, a different device will be shown !

 

When the programming succeeds, and there is no verify error, the application mode will be selected. This will disconnect the DFU and will connect your USB device !

 

[[File:Flip ok.png|center|flip_ok]]

The FLIP programmer window will be closed automatic when the programming succeeds.

 

The USB device will be shown :

[[File:Usb device kb.png|center|usb_device_KB]]

Since you created a keyboard device, the device will be shown under the KEYBOARDS node.

 

When you load a generic HID device it will be shown under HUMAN INTERFACE DEVICES

[[File:Usb generic.png|center|usb_generic]]

 

= HID Generic =

The generic HID class is the class that is well suited for transferring bytes between the PC and the micro processor.

As with any USB application, you specify the number of end points, The example just transfers 8 bytes in and 8 bytes out.

You need to change the Ep_in_length_1 , Ep_out_length, Length_of_report_in and Length_of_report_out constants when you want to transfer a different amount of bytes.

You also need to take into account the maximum data size which will depend on the used chip.

The Usb_user_endpoint_init sub routine also need to be adjusted. The size_8 constant specifies how many bytes are used by the endpoint.

 

'init the user endpoints

Sub Usb_user_endpoint_init(byval Nm As Byte)

 Call Usb_configure_endpoint(ep_hid_in , Type_interrupt , Direction_in , Size_8 , One_bank , Nyet_enabled)

 Call Usb_configure_endpoint(ep_hid_out , Type_interrupt , Direction_out , Size_8 , One_bank , Nyet_enabled)

End Sub

 

As with all USB program, we first initialize the USB task and the HID task. Then we call the tasks in a loop ;

 

Usb_task_init                                               ' init the usb task

Hid_task_init                                               ' init the USB task

Do

 Usb_task                                                  'call this subroutine once in a while

 Hid_task                                                  'call this subroutine once in a while

 'you can call your sub program here

Loop

 

The Hid_task itself is very simple :

 

Sub Hid_task()

   If Usb_connected = 1 Then                               ' Check USB HID is enumerated

      Usb_select_endpoint Ep_hid_out                   ' Get Data Repport From Host

      If Ueintx.rxouti = 1 Then                               ' Is_usb_receive_out())

         Dummy1 = Uedatx : Print "Got : " ; Dummy1         ' it is important that you read the same amount of bytes here as were sent by the host !

         Dummy2 = Uedatx : Print "Got : " ; Dummy2

         Dummy = Uedatx : Print "Got : " ; Dummy

         Dummy = Uedatx : Print "Got : " ; Dummy

         Dummy = Uedatx : Print "Got : " ; Dummy

         Dummy = Uedatx : Print "Got : " ; Dummy

         Dummy = Uedatx : Print "Got : " ; Dummy

         Dummy = Uedatx : Print "Got : " ; Dummy

         Usb_ack_receive_out

     End If

 

     If Dummy1 = &H55 And Dummy2 = &HAA Then               ' Check if we received DFU mode command from host

        Usb_detach                                         ' Detach Actual Generic Hid Application

        Waitms 500

        Goto &H1800                                        'goto bootloader

        'here you could call the bootloader then

     End If

 

     Usb_select_endpoint Ep_hid_in                         ' Ready to send these information to the host application

     If Ueintx.txini = 1 Then                              ' Is_usb_in_ready())

        Uedatx = 1

        Uedatx = 2

        Uedatx = 3

        Uedatx = 4

        Uedatx = 5

        Uedatx = 6

        Uedatx = 7

        Uedatx = 8

        Usb_ack_fifocon                                    ' Send data over the USB

     End If

   End If

End Sub

 

We first check if the device is connected to the USB bus. Then we use Usb_select_endpoint with the number of the end point, to select the end point.

When we want to communicate with an end point, we always have to select this end point using the Usb_select_endpoint procedure.

In the sample, we first select the EP_HID_OUT end point. We check the UEINTX.RXOUTI flag to determine if we received an interrupt with data. If that is the case, we read the UEDATX register to read the data byte.

The UEDATX register is the USB data register. When you read it, you read data from the USB bus. When you write it, you write data to the USB bus.

After reading the bytes you MUST acknowledge with the Usb_ack_receive_out macro.

 

The sample also shows how to run the boot loader from your code. In order to run the boot loader you must detach the current device from the USB bus. Then there is some delay to have windows process it. Finally the GOTO jumps to the boot loader address of the USB162.

 

If you want to write some data back, you need to select the end point, and check if you may send data. If that is the case, you assign the data to the UEDATX register and finally, you MUST acknowledge with the USB_ACK_FIFOCON macro.

 

Finally, you will find in the report data the length of the end points specified : Data &H75 , &H08  

You need to adjust these values when you want to send/receive more data.

 

= HIDX.OCX =

There are plenty of examples on the internet that show how to communicate with HID devices using the windows API.

The HIDX.OCX is an OCX control that can be used for simple communication.

Like all OCX controls, you must register it first with REGSVR32    :   regsvr32 hidx.ocx

After it has been registered you can run the VB test application named HIDdemo.exe.

 

The application will list all HID devices :

 

[[File:Hid ocx1.png|center|hid_ocx1]]

 

Our device is the device with VID 16D0 and PID 201D.

There can only be one application/process at the time that communicates with an USB device.

You must click the checkout-button the device to start communication. This will call the SelectDevice method of the OCX.

As soon as you do this, you will notice that the OnDataRead event will receive data.

 

[[File:Hid ocx2.png|center|hid_ocx2]]

 

The event has the following parameters :

(ByVal Device As Long, ByVal ReportID As Long, ByVal Data As String, ByVal Size As Long)

 

The device is a number with the index of all HID devices. The first device will have number 0. The report number is passed in ReportID. The data is passed as a string.

You can use MID to access this data : firstByte= Asc(Mid(data,1,1))

 

To write to the device, you can use the WriteDevice method. The same parameters are used as with the OnDataRead event.

Example : WriteDevice curdev, 0, s, 8

Curdev is the index of the device. 0 is the report ID and s contains the data. You must specify the length of the data to send.

 

To stop communication you can click the Checkin-button.This will call the ReleaseDevice method.

 

When the device changes, or will be removed or inserted, you will receive a notification.

In the sample program, all these events will result in a release of the device. This is done since the curdev variable can change when a new device is added. The index will not correspond to the existing index then anymore. The sample is very simple. In an application you could add a function or procedure that will examine the new list of devices and return the index of our device. When our device is found we could open it automatic again.

 

Notice that you can not add too much lines to a listbox in VB. Since data arrives at a very high rate, it will not take long before VB/Windows will give some error.

 
<div style="padding: 0px; margin: 0px;">
{| cellspacing="0" cellpadding="0" border="0" style="border: none; border-spacing: 0px; border-collapse: collapse;"
|- style="vertical-align: top;"
| valign="top" width="206" bgcolor="#ffff99" style="width: 206px; background-color: rgb(255, 255, 153); border-style: solid; border-color: rgb(0, 0, 0);" | Property
| valign="top" width="620" bgcolor="#ffff99" style="width: 620px; background-color: rgb(255, 255, 153); border-style: solid; border-color: rgb(0, 0, 0);" | Description
|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
NumCheckedInDevices

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Number of  available devices

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
NumCheckedOutDevices

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Number of devices that are checked out and communicating.

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
NumUnpluggedDevices

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" | 
|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
DevThreadSleepTime

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
The time in mS that the HID thread will sleep. You can see this as a timer interval. The lower the interval the more process time it will take. 100 mS is a good value for most applications.

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
Version

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
The version of the control

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
DeviceCount

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
The number of devices.

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" | 
| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" | 
|-
| width="206" bgcolor="#ffff99" style="width: 206px; background-color: rgb(255, 255, 153); border-style: solid; border-color: rgb(0, 0, 0);" | Methods
| width="620" bgcolor="#ffff99" style="width: 620px; background-color: rgb(255, 255, 153); border-style: solid; border-color: rgb(0, 0, 0);" | 
|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
SelectDevice

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Device : LONG that specifies the index of the device to select. The index starts at 0.
|}
</div>
|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
ReleaseDevice

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Device : LONG that specifies the index of the device to release. The index starts at 0.
|}
</div>
|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
WriteDevice

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Device : LONG that specifies the index of the device to write to. The index starts at 0.
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Report : LONG that specifies the report number. This would be 0 in most cases.
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Data : string that contains the data to send.
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Size : the length of the data to send.
|}
</div>
 

 

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" | 
| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" | 
|-
| width="206" bgcolor="#ffff99" style="width: 206px; background-color: rgb(255, 255, 153); border-style: solid; border-color: rgb(0, 0, 0);" | Events
| width="620" bgcolor="#ffff99" style="width: 620px; background-color: rgb(255, 255, 153); border-style: solid; border-color: rgb(0, 0, 0);" | 
|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
OnDeviceChange

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| none.
|}
</div>
 

This event fires when a device changes. This can be because a new device is added, or a device is removed.

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
OnDeviceArrival

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Device : LONG that specifies the index of the device that arrived. The index starts at 0.
|}
</div>
 

This event fires when a device is inserted. When a device is added or removed, the index that was used previously, does not need to match the new index anymore. For this reason you have to checkout the device again.

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
OnDeviceRemoval

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Device : LONG that specifies the index of the device that has been removed. The index starts at 0.
|}
</div>
 

This event fires when a device is removed. When a device is added or removed, the index that was used previously, does not need to match the new index anymore. For this reason you have to checkout the device again.

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
OnDataRead

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" |
Parameters
<div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Device : LONG that specifies the index of the device that sent data. The index starts at 0.
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| ReportID : LONG with the report ID of the device that sent the data.
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Data : string that contains the data. This string might contain 0-bytes.
|}
</div><div style="padding: 0px; margin: 0px;">
{| border="0" cellpadding="0" cellspacing="0"
|- valign="baseline" style="vertical-align: baseline;"
| width="13" | •
| Size : LONG that contains the length of the received data.
|}
</div>
 

When data is received you can read it in this event. For example :

dim ar(8) as Byte

For J=1 to Size

ar(j) = ASC(Mid(data,J,1)) ' fill the array

Next

 

|- style="vertical-align: top;"
| valign="top" width="206" style="width: 206px; border-style: solid; border-color: rgb(0, 0, 0);" |
 

| valign="top" width="620" style="width: 620px; border-style: solid; border-color: rgb(0, 0, 0);" | 
|}
</div>
 

 

The OCX can be used with all programming languages that can host OCX controls. The OCX was tested with Delphi and VB.

Your windows must support USB in order to use the OCX. So it will not work on Windows 95.

 

 

= Virtual COM sample =

The virtual COM demo shows how to implement an USB device with a virtual COM port. The Demo will echo data sent to the UART to the USB and vise versa.

When you compile and program the sample, you will notice that you find a new COM port in the device manager.

[[File:Notice.jpg|notice]]When you press CTRL+D, BASCOM will launch the device manager.

 

[[File:Dev mng.png|center|dev_mng]]

 

As you can see, the CDC class is used for the virtual COM port. As with most virtual COM devices, you can change the settings :

 

[[File:Virtual com.png|center|virtual COM]]

 

In the BASCOM application the procedure Cdc_get_line_coding is called when the PC need to know the settings.

The Cdc_set_line_coding is called when the settings are changed by the user. You need to change the settings according to the received parameters.

Notice that these settings are virtual too : for the USB it does not matter how the baud rate is set ! Only for a real UART this is important. For an USB-RS232 converter for example it is very convenient to be able to change the baud rate and other settings. But when you just use the USB port for communication, and choose to use the COM port in your program as a way for communication, then you do not really need the settings.

 

When you want to send date to the USB/COM you can use the Uart_usb_putchar procedure. Like any USB routine, it will select the proper end point. After the end point for sending data is selected it will wait if it may send data, and finally it will send this data.

The Uart_usb_getchar() function can be used to receive data from the USB/COM.

 

When you create your own device, the virtual COM port has the advantage that the PC application is simple. In most cases you already have the experience to read/write data to the PC COM port.

The disadvantage is that it requires mode code. It also need an INF file. This INF file you can change to suite your own needs.

When you create your own device, the HID device is the simplest way to go.

 

 

 

 

= CDC INF file =

The CDC INF file looks like this. The bold parts need to be changed if you want to customize with your own text and VID/PID.

 

; Windows 2000, XP & Vista setup File for AT90USBxx2 demo

 

[Version]

Signature="$Windows NT$"

class="Ports

@@ Line 845: / Line 845: @@
 <span style="font-family: Arial;">The CDC INF file looks like this. The bold parts need to be changed if you want to customize with your own text and VID/PID.</span>
-<span style="font-family: Arial;">&nbsp;</span> <source lang="null">
+<span style="font-family: Arial;">&nbsp;</span> <source lang="reg">
 ; Windows 2000, XP & Vista setup File for AT90USBxx2 demo

@@ Line 845: / Line 845: @@
 <span style="font-family: Arial;">The CDC INF file looks like this. The bold parts need to be changed if you want to customize with your own text and VID/PID.</span>
-<span style="font-family: Arial;">&nbsp;</span>
+<span style="font-family: Arial;">&nbsp;</span> <source lang="null">
-<span style="font-family: Arial;">; Windows 2000, XP & Vista setup File for AT90USBxx2 demo</span>
+[[Category:USB]]
-−
-<span style="font-family: Arial;">&nbsp;</span>
-−
-<span style="font-family: Arial;">[Version]</span>
-−
-<span style="font-family: Arial;">Signature="$Windows NT$"</span>
-−
-<span style="font-family: Arial;">class="Ports</span>

← Older revision		Revision as of 12:04, 13 February 2013
Line 75:		Line 75:

	It is not the intention of MCS or the documentation to learn you everything about USB. There is a lot of information available from various sources. It is the goal of MCS to make it easy to use USB with your AVR micro. When there is enough demand for it, a special Wizard will be created to be able to generate HID applications.		It is not the intention of MCS or the documentation to learn you everything about USB. There is a lot of information available from various sources. It is the goal of MCS to make it easy to use USB with your AVR micro. When there is enough demand for it, a special Wizard will be created to be able to generate HID applications.
−
−	~~ ~~
−
−	~~=== Below is a rendering of the page up to the first error. ===~~
−	~~</parsererror>~~
−
−	~~The USB Add On is a commercial add on which is available from the MCS Electronics Web Shop.~~
−
−	The CONFIG USB statement needs this add on. The add on is written in BASCOM BASIC mixed with assembler. Since the examples from Atmel were not really consistent, it took some effort to create reusable code. At a later stage, a number of routines will be moved to an assembler library.
−
−	~~The advantage of the BASCOM code is that it is similar to the C-code examples.~~
−
−	~~ ~~
−
−	~~[[File:Notice.jpg\|notice]]Please read this entire topic first before you start with experiments.~~
−
−	~~ ~~
−
−	~~The Add On only supports the device mode. There is no support for host mode yet. In fact the add on is just the first step into USB support.~~
−
−	~~ ~~
−
−	~~To use the USB Add on, unzip all the files to the SAMPLES\USB directory.~~
−
−	~~You will find three samples :~~
−	~~<div style="padding: 0px; margin: 0px;">~~
−	~~{\| border="0" cellpadding="0" cellspacing="0"~~
−	~~\|- valign="baseline" style="vertical-align: baseline;"~~
−	~~\| width="13" \| <span style="font-size: 10pt; font-family: 'Arial Unicode MS', 'Lucida Sans Unicode', Arial;">•</span>~~
−	~~\| hid_generic-162.bas~~
−	\|}
−	~~</div><div style="padding: 0px; margin: 0px;">~~
−	~~{\| border="0" cellpadding="0" cellspacing="0"~~
−	~~\|- valign="baseline" style="vertical-align: baseline;"~~
−	~~\| width="13" \| <span style="font-size: 10pt; font-family: 'Arial Unicode MS', 'Lucida Sans Unicode', Arial;">•</span>~~
−	~~\| virtcom-162.bas~~
−	\|}
−	~~</div><div style="padding: 0px; margin: 0px;">~~
−	~~{\| border="0" cellpadding="0" cellspacing="0"~~
−	~~\|- valign="baseline" style="vertical-align: baseline;"~~
−	~~\| width="13" \| <span style="font-size: 10pt; font-family: 'Arial Unicode MS', 'Lucida Sans Unicode', Arial;">•</span>~~
−	~~\| hid_keyboard-162.bas~~
−	\|}
−	~~</div>~~
−	~~ ~~
−
−	~~The same samples are also provided for the USB1287.~~
−
−	~~ ~~
−
−	~~And you will find the include file : <span style="font-weight: bold;">usbinc.bas</span>. It is not allowed to distribute any of the files.~~
−
−	~~<span class="f_ImageCaption"> </span>~~
−
−	~~Further, you will find a subdirectory named VB which contains a simple VB generic HID sample that uses the HIDX.OCX from the OCX subdirectory.~~
−
−	~~ ~~
−
−	~~The PDF directory contains a PDF with a translation between PS2 scan codes and USB key codes.~~
−
−	~~ ~~
−
−	~~The TOOLS directory contains the USBDEVIEW.EXE which can be used to display all USB devices,~~
−
−	~~ ~~
−
−	~~The CDC-Driver directory contains the INF file you need for the CDC/Virtual COM port example.~~
−
−	~~ ~~
−
−	~~The USB162 has a boot loader which can be programmed by USB using FLIP. BASCOM will also support this USB boot loader in version 1.11.9.2.~~
−
−	It is great for development but of course the boot loader uses some space which you probably need. The chip is also programmable via the normal way with the ISP protocol. when you do not use FLIP, and you erase the chip, the boot loader from Atmel is erased too! You can always reprogram the Atmel boot loader. But not using FLIP which depends on the boot loader.
−
−	~~ ~~
−
−	For USB to work properly the chip needs a good oscillator. The internal oscillator is not good enough. For that reason, the USB162 module from MCS has a 8 MHz crystal. Your hardware should use a crystal or crystal oscillator too.
−
−	~~ ~~
−
−	It is not the intention of MCS or the documentation to learn you everything about USB. There is a lot of information available from various sources. It is the goal of MCS to make it easy to use USB with your AVR micro. When there is enough demand for it, a special Wizard will be created to be able to generate HID applications.
−
−	~~ ~~

@@ Line 1: / Line 1: @@
 <parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">
-=== This page contains the following errors: ===
+The USB Add On is a commercial add on which is available from the MCS Electronics Web Shop.
-<div style="font-family:monospace;font-size:12px">error on line 1 at column 36376: error parsing attribute name </div>
 === Below is a rendering of the page up to the first error. ===
 </parsererror>