<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
	<link rel="self" type="application/atom+xml" href="https://forums.obdev.at/app.php/feed/topic/6516" />

	<title>Objective Development Forums</title>
	
	<link href="https://forums.obdev.at/index.php" />
	<updated>2012-05-12T05:35:20+02:00</updated>

	<author><name><![CDATA[Objective Development Forums]]></name></author>
	<id>https://forums.obdev.at/app.php/feed/topic/6516</id>

		<entry>
		<author><name><![CDATA[honupata]]></name></author>
		<updated>2012-05-12T05:35:20+02:00</updated>

		<published>2012-05-12T05:35:20+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6516&amp;p=21582#p21582</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6516&amp;p=21582#p21582"/>
		<title type="html"><![CDATA[Re: usb device unrecognized with ATtiny45]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6516&amp;p=21582#p21582"><![CDATA[
Hi,<br /><br />Can you post your makefile and details of the hardware ?<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=5786">honupata</a> — Sat May 12, 2012 5:35 am</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[ptut]]></name></author>
		<updated>2012-03-19T17:42:54+02:00</updated>

		<published>2012-03-19T17:42:54+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6516&amp;p=21181#p21181</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6516&amp;p=21181#p21181"/>
		<title type="html"><![CDATA[usb device unrecognized with ATtiny45]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6516&amp;p=21181#p21181"><![CDATA[
Hi,<br /><br />Actually, I try to use USB interface with an Attiny45 with the vusb-20100715 library. The software compiles correctly and I send it to Attiny45. <br />However, when I connect device to the computer, I obtain an usb device unrecognized message in the task bar. So, I can't communicate with Attiny. <br />In the program, I chose a F_CPU value of 16500000UL. Is it good value?<br />Listings below are test_usb.c (main software) and usbconfig.h used for the compilation. I removed the F_CPU value.<br />test_usb.c:<br /><div class="codebox"><p>Code: </p><pre><code>/*<br /> * test_usb.c<br /> *<br /> * Created: 12/01/2012 10:11:26<br /> *  Author: maxime<br /> */ <br /><br /><br />#include &lt;avr/io.h&gt;<br />#include &lt;avr/wdt.h&gt;<br />#include &lt;avr/interrupt.h&gt;<br />//#include &lt;avr/delay.h&gt;<br />#include &lt;util/delay.h&gt;<br />#include &lt;avr/eeprom.h&gt;<br />#include &lt;avr/pgmspace.h&gt;<br />#include &quot;usbdrv/usbdrv.h&quot;<br />#include &quot;oddebug.h&quot;<br /><br /><br />char bytesRemaining;<br /><br /><br />PROGMEM char usbHidReportDescriptor&#91;22&#93; = {    /* USB report descriptor */<br />    0x06, 0x00, 0xff,              // USAGE_PAGE (Generic Desktop)<br />    0x09, 0x01,                    // USAGE (Vendor Usage 1)<br />    0xa1, 0x01,                    // COLLECTION (Application)<br />    0x15, 0x00,                    //   LOGICAL_MINIMUM (0)<br />    0x26, 0xff, 0x00,              //   LOGICAL_MAXIMUM (255)<br />    0x75, 0x08,                    //   REPORT_SIZE (8)<br />    0x95, 0x02,                    //   REPORT_COUNT (2)<br />    0x09, 0x00,                    //   USAGE (Undefined)<br />    0xb2, 0x02, 0x01,              //   FEATURE (Data,Var,Abs,Buf)<br />    0xc0                           // END_COLLECTION<br />};<br /><br />usbMsgLen_t usbFunctionSetup(uchar setupData&#91;8&#93;)<br />{<br />    usbRequest_t *rq = (void *)setupData;  <br />   //Utiliser les requètes pour les demande d'id.<br />   //Pour mettre en marche, vérifier qu'une télécommande est enregistrée.<br />   //Interruption pour l'envoie de donnée du bouton<br />    if(rq-&gt;bmRequestType == 64) //USB_TYPE_VENDOR | USB_RECIP_DEVICE | USB_ENDPOINT_OUT   //USBRQ_HID_GET_REPORT<br />   {   <br />      bytesRemaining = 2;              <br />        return USB_NO_MSG;                         <br />    }<br />   else if(rq-&gt;bmRequestType == 192 )// USB_TYPE_VENDOR | USB_RECIP_DEVICE | USB_ENDPOINT_IN <br />   {<br />      usbMsgLen_t len = 2;                     <br />        if(len &gt; rq-&gt;wLength.word)          <br />            len = rq-&gt;wLength.word;     <br />      return len;                <br />    }<br />    return 0;                               <br />}<br /><br />/* ------------------------------------------------------------------------- */<br />/* ------------------------ Oscillator Calibration ------------------------- */<br />/* ------------------------------------------------------------------------- */<br /><br />/* Calibrate the RC oscillator to 8.25 MHz. The core clock of 16.5 MHz is<br /> * derived from the 66 MHz peripheral clock by dividing. Our timing reference<br /> * is the Start Of Frame signal (a single SE0 bit) available immediately after<br /> * a USB RESET. We first do a binary search for the OSCCAL value and then<br /> * optimize this value with a neighboorhod search.<br /> * This algorithm may also be used to calibrate the RC oscillator directly to<br /> * 12 MHz (no PLL involved, can therefore be used on almost ALL AVRs), but this<br /> * is wide outside the spec for the OSCCAL value and the required precision for<br /> * the 12 MHz clock! Use the RC oscillator calibrated to 12 MHz for<br /> * experimental purposes only!<br /> */<br />static void calibrateOscillator(void)<br />{<br />uchar       step = 128;<br />uchar       trialValue = 0, optimumValue;<br />int         x, optimumDev, targetValue = (unsigned)(1499 * (double)F_CPU / 10.5e6 + 0.5);<br /><br />    /* do a binary search: */<br />    do{<br />        OSCCAL = trialValue + step;<br />        x = usbMeasureFrameLength();    /* proportional to current real frequency */<br />        if(x &lt; targetValue)             /* frequency still too low */<br />            trialValue += step;<br />        step &gt;&gt;= 1;<br />    }while(step &gt; 0);<br />    /* We have a precision of +/- 1 for optimum OSCCAL here */<br />    /* now do a neighborhood search for optimum value */<br />    optimumValue = trialValue;<br />    optimumDev = x; /* this is certainly far away from optimum */<br />    for(OSCCAL = trialValue - 1; OSCCAL &lt;= trialValue + 1; OSCCAL++){<br />        x = usbMeasureFrameLength() - targetValue;<br />        if(x &lt; 0)<br />            x = -x;<br />        if(x &lt; optimumDev){<br />            optimumDev = x;<br />            optimumValue = OSCCAL;<br />        }<br />    }<br />    OSCCAL = optimumValue;<br />}<br />/*<br />Note: This calibration algorithm may try OSCCAL values of up to 192 even if<br />the optimum value is far below 192. It may therefore exceed the allowed clock<br />frequency of the CPU in low voltage designs!<br />You may replace this search algorithm with any other algorithm you like if<br />you have additional constraints such as a maximum CPU clock.<br />For version 5.x RC oscillators (those with a split range of 2x128 steps, e.g.<br />ATTiny25, ATTiny45, ATTiny85), it may be useful to search for the optimum in<br />both regions.<br />*/<br />void    usbEventResetReady(void)<br />{<br />    calibrateOscillator();<br />    eeprom_write_byte(0, OSCCAL);   /* store the calibrated value in EEPROM */<br />}<br /><br />int main(void)<br />{<br />uchar   i;<br />uchar   calibrationValue;<br /><br />    calibrationValue = eeprom_read_byte(0); /* calibration value from last time */<br />    if(calibrationValue != 0xff){<br />        OSCCAL = calibrationValue;<br />    }<br />    odDebugInit();<br />    usbDeviceDisconnect();<br />    for(i=0;i&lt;20;i++){  /* 300 ms disconnect */<br />        _delay_ms(15);<br />    }<br />    usbDeviceConnect();<br />    sei();<br />    for(;;){                /* main event loop */<br />        wdt_reset();<br />        usbPoll();<br />    }<br />    return 0;<br />}</code></pre></div><br />and usbconfig.h<br /><div class="codebox"><p>Code: </p><pre><code>/* Name: usbconfig.h<br /> * Project: V-USB, virtual USB port for Atmel's(r) AVR(r) microcontrollers<br /> * Author: Christian Starkjohann<br /> * Creation Date: 2005-04-01<br /> * Tabsize: 4<br /> * Copyright: (c) 2005 by OBJECTIVE DEVELOPMENT Software GmbH<br /> * License: GNU GPL v2 (see License.txt), GNU GPL v3 or proprietary (CommercialLicense.txt)<br /> * This Revision: $Id: usbconfig-prototype.h 785 2010-05-30 17:57:07Z cs $<br /> */<br /><br />#ifndef __usbconfig_h_included__<br />#define __usbconfig_h_included__<br /><br /><br />/*<br />General Description:<br />This file is an example configuration (with inline documentation) for the USB<br />driver. It configures V-USB for USB D+ connected to Port D bit 2 (which is<br />also hardware interrupt 0 on many devices) and USB D- to Port D bit 4. You may<br />wire the lines to any other port, as long as D+ is also wired to INT0 (or any<br />other hardware interrupt, as long as it is the highest level interrupt, see<br />section at the end of this file).<br />+ To create your own usbconfig.h file, copy this file to your project's<br />+ firmware source directory) and rename it to &quot;usbconfig.h&quot;.<br />+ Then edit it accordingly.<br />*/<br /><br />/* ---------------------------- Hardware Config ---------------------------- */<br /><br />#define USB_CFG_IOPORTNAME      B<br />/* This is the port where the USB bus is connected. When you configure it to<br /> * &quot;B&quot;, the registers PORTB, PINB and DDRB will be used.<br /> */<br />#define USB_CFG_DMINUS_BIT      0<br />/* This is the bit number in USB_CFG_IOPORT where the USB D- line is connected.<br /> * This may be any bit in the port.<br /> */<br />#define USB_CFG_DPLUS_BIT       2<br />/* This is the bit number in USB_CFG_IOPORT where the USB D+ line is connected.<br /> * This may be any bit in the port. Please note that D+ must also be connected<br /> * to interrupt pin INT0! &#91;You can also use other interrupts, see section<br /> * &quot;Optional MCU Description&quot; below, or you can connect D- to the interrupt, as<br /> * it is required if you use the USB_COUNT_SOF feature. If you use D- for the<br /> * interrupt, the USB interrupt will also be triggered at Start-Of-Frame<br /> * markers every millisecond.&#93;<br /> */<br />#define USB_CFG_CLOCK_KHZ       (F_CPU/1000)<br />/* Clock rate of the AVR in kHz. Legal values are 12000, 12800, 15000, 16000,<br /> * 16500, 18000 and 20000. The 12.8 MHz and 16.5 MHz versions of the code<br /> * require no crystal, they tolerate +/- 1% deviation from the nominal<br /> * frequency. All other rates require a precision of 2000 ppm and thus a<br /> * crystal!<br /> * Since F_CPU should be defined to your actual clock rate anyway, you should<br /> * not need to modify this setting.<br /> */<br />#define USB_CFG_CHECK_CRC       0<br />/* Define this to 1 if you want that the driver checks integrity of incoming<br /> * data packets (CRC checks). CRC checks cost quite a bit of code size and are<br /> * currently only available for 18 MHz crystal clock. You must choose<br /> * USB_CFG_CLOCK_KHZ = 18000 if you enable this option.<br /> */<br /><br />/* ----------------------- Optional Hardware Config ------------------------ */<br /><br />/* #define USB_CFG_PULLUP_IOPORTNAME   D */<br />/* If you connect the 1.5k pullup resistor from D- to a port pin instead of<br /> * V+, you can connect and disconnect the device from firmware by calling<br /> * the macros usbDeviceConnect() and usbDeviceDisconnect() (see usbdrv.h).<br /> * This constant defines the port on which the pullup resistor is connected.<br /> */<br />/* #define USB_CFG_PULLUP_BIT          4 */<br />/* This constant defines the bit number in USB_CFG_PULLUP_IOPORT (defined<br /> * above) where the 1.5k pullup resistor is connected. See description<br /> * above for details.<br /> */<br /><br />/* --------------------------- Functional Range ---------------------------- */<br /><br />#define USB_CFG_HAVE_INTRIN_ENDPOINT    0<br />/* Define this to 1 if you want to compile a version with two endpoints: The<br /> * default control endpoint 0 and an interrupt-in endpoint (any other endpoint<br /> * number).<br /> */<br />#define USB_CFG_HAVE_INTRIN_ENDPOINT3   0<br />/* Define this to 1 if you want to compile a version with three endpoints: The<br /> * default control endpoint 0, an interrupt-in endpoint 3 (or the number<br /> * configured below) and a catch-all default interrupt-in endpoint as above.<br /> * You must also define USB_CFG_HAVE_INTRIN_ENDPOINT to 1 for this feature.<br /> */<br />#define USB_CFG_EP3_NUMBER              3<br />/* If the so-called endpoint 3 is used, it can now be configured to any other<br /> * endpoint number (except 0) with this macro. Default if undefined is 3.<br /> */<br />/* #define USB_INITIAL_DATATOKEN           USBPID_DATA1 */<br />/* The above macro defines the startup condition for data toggling on the<br /> * interrupt/bulk endpoints 1 and 3. Defaults to USBPID_DATA1.<br /> * Since the token is toggled BEFORE sending any data, the first packet is<br /> * sent with the oposite value of this configuration!<br /> */<br />#define USB_CFG_IMPLEMENT_HALT          0<br />/* Define this to 1 if you also want to implement the ENDPOINT_HALT feature<br /> * for endpoint 1 (interrupt endpoint). Although you may not need this feature,<br /> * it is required by the standard. We have made it a config option because it<br /> * bloats the code considerably.<br /> */<br />#define USB_CFG_SUPPRESS_INTR_CODE      0<br />/* Define this to 1 if you want to declare interrupt-in endpoints, but don't<br /> * want to send any data over them. If this macro is defined to 1, functions<br /> * usbSetInterrupt() and usbSetInterrupt3() are omitted. This is useful if<br /> * you need the interrupt-in endpoints in order to comply to an interface<br /> * (e.g. HID), but never want to send any data. This option saves a couple<br /> * of bytes in flash memory and the transmit buffers in RAM.<br /> */<br />#define USB_CFG_INTR_POLL_INTERVAL      50<br />/* If you compile a version with endpoint 1 (interrupt-in), this is the poll<br /> * interval. The value is in milliseconds and must not be less than 10 ms for<br /> * low speed devices.<br /> */<br />#define USB_CFG_IS_SELF_POWERED         0<br />/* Define this to 1 if the device has its own power supply. Set it to 0 if the<br /> * device is powered from the USB bus.<br /> */<br />#define USB_CFG_MAX_BUS_POWER           100<br />/* Set this variable to the maximum USB bus power consumption of your device.<br /> * The value is in milliamperes. &#91;It will be divided by two since USB<br /> * communicates power requirements in units of 2 mA.&#93;<br /> */<br />#define USB_CFG_IMPLEMENT_FN_WRITE      0<br />/* Set this to 1 if you want usbFunctionWrite() to be called for control-out<br /> * transfers. Set it to 0 if you don't need it and want to save a couple of<br /> * bytes.<br /> */<br />#define USB_CFG_IMPLEMENT_FN_READ       0<br />/* Set this to 1 if you need to send control replies which are generated<br /> * &quot;on the fly&quot; when usbFunctionRead() is called. If you only want to send<br /> * data from a static buffer, set it to 0 and return the data from<br /> * usbFunctionSetup(). This saves a couple of bytes.<br /> */<br />#define USB_CFG_IMPLEMENT_FN_WRITEOUT   0<br />/* Define this to 1 if you want to use interrupt-out (or bulk out) endpoints.<br /> * You must implement the function usbFunctionWriteOut() which receives all<br /> * interrupt/bulk data sent to any endpoint other than 0. The endpoint number<br /> * can be found in 'usbRxToken'.<br /> */<br />#define USB_CFG_HAVE_FLOWCONTROL        0<br />/* Define this to 1 if you want flowcontrol over USB data. See the definition<br /> * of the macros usbDisableAllRequests() and usbEnableAllRequests() in<br /> * usbdrv.h.<br /> */<br />#define USB_CFG_DRIVER_FLASH_PAGE       0<br />/* If the device has more than 64 kBytes of flash, define this to the 64 k page<br /> * where the driver's constants (descriptors) are located. Or in other words:<br /> * Define this to 1 for boot loaders on the ATMega128.<br /> */<br />#define USB_CFG_LONG_TRANSFERS          0<br />/* Define this to 1 if you want to send/receive blocks of more than 254 bytes<br /> * in a single control-in or control-out transfer. Note that the capability<br /> * for long transfers increases the driver size.<br /> */<br />/* #define USB_RX_USER_HOOK(data, len)     if(usbRxToken == (uchar)USBPID_SETUP) blinkLED(); */<br />/* This macro is a hook if you want to do unconventional things. If it is<br /> * defined, it's inserted at the beginning of received message processing.<br /> * If you eat the received message and don't want default processing to<br /> * proceed, do a return after doing your things. One possible application<br /> * (besides debugging) is to flash a status LED on each packet.<br /> */<br />/* #define USB_RESET_HOOK(resetStarts)     if(!resetStarts){hadUsbReset();} */<br />/* This macro is a hook if you need to know when an USB RESET occurs. It has<br /> * one parameter which distinguishes between the start of RESET state and its<br /> * end.<br /> */<br />/* #define USB_SET_ADDRESS_HOOK()              hadAddressAssigned(); */<br />/* This macro (if defined) is executed when a USB SET_ADDRESS request was<br /> * received.<br /> */<br />#define USB_COUNT_SOF                   0<br />/* define this macro to 1 if you need the global variable &quot;usbSofCount&quot; which<br /> * counts SOF packets. This feature requires that the hardware interrupt is<br /> * connected to D- instead of D+.<br /> */<br />/* #ifdef __ASSEMBLER__<br /> * macro myAssemblerMacro<br /> *     in      YL, TCNT0<br /> *     sts     timer0Snapshot, YL<br /> *     endm<br /> * #endif<br /> * #define USB_SOF_HOOK                    myAssemblerMacro<br /> * This macro (if defined) is executed in the assembler module when a<br /> * Start Of Frame condition is detected. It is recommended to define it to<br /> * the name of an assembler macro which is defined here as well so that more<br /> * than one assembler instruction can be used. The macro may use the register<br /> * YL and modify SREG. If it lasts longer than a couple of cycles, USB messages<br /> * immediately after an SOF pulse may be lost and must be retried by the host.<br /> * What can you do with this hook? Since the SOF signal occurs exactly every<br /> * 1 ms (unless the host is in sleep mode), you can use it to tune OSCCAL in<br /> * designs running on the internal RC oscillator.<br /> * Please note that Start Of Frame detection works only if D- is wired to the<br /> * interrupt, not D+. THIS IS DIFFERENT THAN MOST EXAMPLES!<br /> */<br />#define USB_CFG_CHECK_DATA_TOGGLING     0<br />/* define this macro to 1 if you want to filter out duplicate data packets<br /> * sent by the host. Duplicates occur only as a consequence of communication<br /> * errors, when the host does not receive an ACK. Please note that you need to<br /> * implement the filtering yourself in usbFunctionWriteOut() and<br /> * usbFunctionWrite(). Use the global usbCurrentDataToken and a static variable<br /> * for each control- and out-endpoint to check for duplicate packets.<br /> */<br /><br />#ifndef __ASSEMBLER__<br />extern void usbEventResetReady(void);<br />#endif<br />#define USB_RESET_HOOK(isReset)             if(!isReset){usbEventResetReady();}<br />/* This macro is a hook if you need to know when an USB RESET occurs. It has<br /> * one parameter which distinguishes between the start of RESET state and its<br /> * end.<br /> */<br /><br />#define USB_CFG_HAVE_MEASURE_FRAME_LENGTH   1<br />/* define this macro to 1 if you want the function usbMeasureFrameLength()<br /> * compiled in. This function can be used to calibrate the AVR's RC oscillator.<br /> */<br />#define USB_USE_FAST_CRC                0<br />/* The assembler module has two implementations for the CRC algorithm. One is<br /> * faster, the other is smaller. This CRC routine is only used for transmitted<br /> * messages where timing is not critical. The faster routine needs 31 cycles<br /> * per byte while the smaller one needs 61 to 69 cycles. The faster routine<br /> * may be worth the 32 bytes bigger code size if you transmit lots of data and<br /> * run the AVR close to its limit.<br /> */<br /><br />/* -------------------------- Device Description --------------------------- */<br /><br />#define  USB_CFG_VENDOR_ID       0xc0, 0x16 /* = 0x16c0 = 5824 = voti.nl */<br />/* USB vendor ID for the device, low byte first. If you have registered your<br /> * own Vendor ID, define it here. Otherwise you may use one of obdev's free<br /> * shared VID/PID pairs. Be sure to read USB-IDs-for-free.txt for rules!<br /> * *** IMPORTANT NOTE ***<br /> * This template uses obdev's shared VID/PID pair for Vendor Class devices<br /> * with libusb: 0x16c0/0x5dc.  Use this VID/PID pair ONLY if you understand<br /> * the implications!<br /> */<br />#define  USB_CFG_DEVICE_ID       0xdc, 0x05 /* = 0x05dc = 1500 */   <br />/* This is the ID of the product, low byte first. It is interpreted in the<br /> * scope of the vendor ID. If you have registered your own VID with usb.org<br /> * or if you have licensed a PID from somebody else, define it here. Otherwise<br /> * you may use one of obdev's free shared VID/PID pairs. See the file<br /> * USB-IDs-for-free.txt for details!<br /> * *** IMPORTANT NOTE ***<br /> * This template uses obdev's shared VID/PID pair for Vendor Class devices<br /> * with libusb: 0x16c0/0x5dc.  Use this VID/PID pair ONLY if you understand<br /> * the implications!<br /> */<br />#define USB_CFG_DEVICE_VERSION  0x00, 0x01<br />/* Version number of the device: Minor number first, then major number.<br /> */<br />#define USB_CFG_VENDOR_NAME     't','m'<br />#define USB_CFG_VENDOR_NAME_LEN 2<br />/* These two values define the vendor name returned by the USB device. The name<br /> * must be given as a list of characters under single quotes. The characters<br /> * are interpreted as Unicode (UTF-16) entities.<br /> * If you don't want a vendor name string, undefine these macros.<br /> * ALWAYS define a vendor name containing your Internet domain name if you use<br /> * obdev's free shared VID/PID pair. See the file USB-IDs-for-free.txt for<br /> * details.<br /> */<br />#define USB_CFG_DEVICE_NAME     'R','T'<br />#define USB_CFG_DEVICE_NAME_LEN 2<br />/* Same as above for the device name. If you don't want a device name, undefine<br /> * the macros. See the file USB-IDs-for-free.txt before you assign a name if<br /> * you use a shared VID/PID.<br /> */<br />/*#define USB_CFG_SERIAL_NUMBER   'N', 'o', 'n', 'e' */<br />/*#define USB_CFG_SERIAL_NUMBER_LEN   0 */<br />/* Same as above for the serial number. If you don't want a serial number,<br /> * undefine the macros.<br /> * It may be useful to provide the serial number through other means than at<br /> * compile time. See the section about descriptor properties below for how<br /> * to fine tune control over USB descriptors such as the string descriptor<br /> * for the serial number.<br /> */<br />#define USB_CFG_DEVICE_CLASS        0xff    /* set to 0 if deferred to interface */<br />#define USB_CFG_DEVICE_SUBCLASS     0<br />/* See USB specification if you want to conform to an existing device class.<br /> * Class 0xff is &quot;vendor specific&quot;.<br /> */<br />#define USB_CFG_INTERFACE_CLASS     0   /* define class here if not at device level */<br />#define USB_CFG_INTERFACE_SUBCLASS  0<br />#define USB_CFG_INTERFACE_PROTOCOL  0<br />/* See USB specification if you want to conform to an existing device class or<br /> * protocol. The following classes must be set at interface level:<br /> * HID class is 3, no subclass and protocol required (but may be useful!)<br /> * CDC class is 2, use subclass 2 and protocol 1 for ACM<br /> */<br />#define USB_CFG_HID_REPORT_DESCRIPTOR_LENGTH    22<br />/* Define this to the length of the HID report descriptor, if you implement<br /> * an HID device. Otherwise don't define it or define it to 0.<br /> * If you use this define, you must add a PROGMEM character array named<br /> * &quot;usbHidReportDescriptor&quot; to your code which contains the report descriptor.<br /> * Don't forget to keep the array and this define in sync!<br /> */<br /><br />/* #define USB_PUBLIC static */<br />/* Use the define above if you #include usbdrv.c instead of linking against it.<br /> * This technique saves a couple of bytes in flash memory.<br /> */<br /><br />/* ------------------- Fine Control over USB Descriptors ------------------- */<br />/* If you don't want to use the driver's default USB descriptors, you can<br /> * provide our own. These can be provided as (1) fixed length static data in<br /> * flash memory, (2) fixed length static data in RAM or (3) dynamically at<br /> * runtime in the function usbFunctionDescriptor(). See usbdrv.h for more<br /> * information about this function.<br /> * Descriptor handling is configured through the descriptor's properties. If<br /> * no properties are defined or if they are 0, the default descriptor is used.<br /> * Possible properties are:<br /> *   + USB_PROP_IS_DYNAMIC: The data for the descriptor should be fetched<br /> *     at runtime via usbFunctionDescriptor(). If the usbMsgPtr mechanism is<br /> *     used, the data is in FLASH by default. Add property USB_PROP_IS_RAM if<br /> *     you want RAM pointers.<br /> *   + USB_PROP_IS_RAM: The data returned by usbFunctionDescriptor() or found<br /> *     in static memory is in RAM, not in flash memory.<br /> *   + USB_PROP_LENGTH(len): If the data is in static memory (RAM or flash),<br /> *     the driver must know the descriptor's length. The descriptor itself is<br /> *     found at the address of a well known identifier (see below).<br /> * List of static descriptor names (must be declared PROGMEM if in flash):<br /> *   char usbDescriptorDevice&#91;&#93;;<br /> *   char usbDescriptorConfiguration&#91;&#93;;<br /> *   char usbDescriptorHidReport&#91;&#93;;<br /> *   char usbDescriptorString0&#91;&#93;;<br /> *   int usbDescriptorStringVendor&#91;&#93;;<br /> *   int usbDescriptorStringDevice&#91;&#93;;<br /> *   int usbDescriptorStringSerialNumber&#91;&#93;;<br /> * Other descriptors can't be provided statically, they must be provided<br /> * dynamically at runtime.<br /> *<br /> * Descriptor properties are or-ed or added together, e.g.:<br /> * #define USB_CFG_DESCR_PROPS_DEVICE   (USB_PROP_IS_RAM | USB_PROP_LENGTH(18))<br /> *<br /> * The following descriptors are defined:<br /> *   USB_CFG_DESCR_PROPS_DEVICE<br /> *   USB_CFG_DESCR_PROPS_CONFIGURATION<br /> *   USB_CFG_DESCR_PROPS_STRINGS<br /> *   USB_CFG_DESCR_PROPS_STRING_0<br /> *   USB_CFG_DESCR_PROPS_STRING_VENDOR<br /> *   USB_CFG_DESCR_PROPS_STRING_PRODUCT<br /> *   USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER<br /> *   USB_CFG_DESCR_PROPS_HID<br /> *   USB_CFG_DESCR_PROPS_HID_REPORT<br /> *   USB_CFG_DESCR_PROPS_UNKNOWN (for all descriptors not handled by the driver)<br /> *<br /> * Note about string descriptors: String descriptors are not just strings, they<br /> * are Unicode strings prefixed with a 2 byte header. Example:<br /> * int  serialNumberDescriptor&#91;&#93; = {<br /> *     USB_STRING_DESCRIPTOR_HEADER(6),<br /> *     'S', 'e', 'r', 'i', 'a', 'l'<br /> * };<br /> */<br /><br />#define USB_CFG_DESCR_PROPS_DEVICE                  0<br />#define USB_CFG_DESCR_PROPS_CONFIGURATION           0<br />#define USB_CFG_DESCR_PROPS_STRINGS                 0<br />#define USB_CFG_DESCR_PROPS_STRING_0                0<br />#define USB_CFG_DESCR_PROPS_STRING_VENDOR           0<br />#define USB_CFG_DESCR_PROPS_STRING_PRODUCT          0<br />#define USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER    0<br />#define USB_CFG_DESCR_PROPS_HID                     0<br />#define USB_CFG_DESCR_PROPS_HID_REPORT              0<br />#define USB_CFG_DESCR_PROPS_UNKNOWN                 0<br /><br />/* ----------------------- Optional MCU Description ------------------------ */<br /><br />/* The following configurations have working defaults in usbdrv.h. You<br /> * usually don't need to set them explicitly. Only if you want to run<br /> * the driver on a device which is not yet supported or with a compiler<br /> * which is not fully supported (such as IAR C) or if you use a differnt<br /> * interrupt than INT0, you may have to define some of these.<br /> */<br />/* #define USB_INTR_CFG            MCUCR */<br />/* #define USB_INTR_CFG_SET        ((1 &lt;&lt; ISC00) | (1 &lt;&lt; ISC01)) */<br />/* #define USB_INTR_CFG_CLR        0 */<br />/* #define USB_INTR_ENABLE         GIMSK */<br />/* #define USB_INTR_ENABLE_BIT     INT0 */<br />/* #define USB_INTR_PENDING        GIFR */<br />/* #define USB_INTR_PENDING_BIT    INTF0 */<br />/* #define USB_INTR_VECTOR         INT0_vect */<br /><br />#endif /* __usbconfig_h_included__ */<br /></code></pre></div><br />I have already checked that the pin configuration is same than the physical one.<br /><br />Is there anybody to help me solving this communication problem.<br /><br />Thank you for your answers.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=6511">ptut</a> — Mon Mar 19, 2012 5:42 pm</p><hr />
]]></content>
	</entry>
	</feed>
