<?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/6336" />

	<title>Objective Development Forums</title>
	
	<link href="https://forums.obdev.at/index.php" />
	<updated>2012-01-10T13:10:44+02:00</updated>

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

		<entry>
		<author><name><![CDATA[Daid]]></name></author>
		<updated>2012-01-10T13:10:44+02:00</updated>

		<published>2012-01-10T13:10:44+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20634#p20634</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20634#p20634"/>
		<title type="html"><![CDATA[Re: Need help! Trying to establish connection, but failed..]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20634#p20634"><![CDATA[
You cannot &quot;break&quot; an AVR with wrong fuses. The only 2 things you can do that cause problems:<br />-Disable ISP (however, this is only available when using high voltage programming)<br />-Set an external crystal without having one connected<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=5154">Daid</a> — Tue Jan 10, 2012 1:10 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[IloveIphonyWikyBolex]]></name></author>
		<updated>2012-01-09T17:28:53+02:00</updated>

		<published>2012-01-09T17:28:53+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20628#p20628</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20628#p20628"/>
		<title type="html"><![CDATA[Re: Need help! Trying to establish connection, but failed..]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20628#p20628"><![CDATA[
<blockquote><div><cite>Daid wrote:</cite>Maybe I'm mistaken but I'm not seeing the pull up resistor to D-? It's R3 in this schematic: <!-- m --><a class="postlink" href="http://www.obdev.at/Images/vusb/circuit-zoomed.gif">http://www.obdev.at/Images/vusb/circuit-zoomed.gif</a><!-- m --><br />It's very important for it identifies the device as a low speed device.</div></blockquote><br /><br />I made a mistake by putting the 1.5k resistor on a different breadboard line, than putting the same line with the cable underneath the resistor. I'm going to fix this when I get home.<br /><br />Can anyone check if the fuses are right for this device? because I don't want to break another IC.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=6235">IloveIphonyWikyBolex</a> — Mon Jan 09, 2012 5:28 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[Peter Chaffe]]></name></author>
		<updated>2012-01-09T12:44:20+02:00</updated>

		<published>2012-01-09T12:44:20+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20625#p20625</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20625#p20625"/>
		<title type="html"><![CDATA[Re: Need help! Trying to establish connection, but failed..]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20625#p20625"><![CDATA[
post in error<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=6086">Peter Chaffe</a> — Mon Jan 09, 2012 12:44 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[Daid]]></name></author>
		<updated>2012-01-09T12:16:47+02:00</updated>

		<published>2012-01-09T12:16:47+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20623#p20623</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20623#p20623"/>
		<title type="html"><![CDATA[Re: Need help! Trying to establish connection, but failed..]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20623#p20623"><![CDATA[
Maybe I'm mistaken but I'm not seeing the pull up resistor to D-? It's R3 in this schematic: <!-- m --><a class="postlink" href="http://www.obdev.at/Images/vusb/circuit-zoomed.gif">http://www.obdev.at/Images/vusb/circuit-zoomed.gif</a><!-- m --><br />It's very important for it identifies the device as a low speed device.<p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=5154">Daid</a> — Mon Jan 09, 2012 12:16 pm</p><hr />
]]></content>
	</entry>
		<entry>
		<author><name><![CDATA[IloveIphonyWikyBolex]]></name></author>
		<updated>2012-01-08T00:11:58+02:00</updated>

		<published>2012-01-08T00:11:58+02:00</published>
		<id>https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20617#p20617</id>
		<link href="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20617#p20617"/>
		<title type="html"><![CDATA[Need help! Trying to establish connection, but failed..]]></title>

		
		<content type="html" xml:base="https://forums.obdev.at/viewtopic.php?t=6336&amp;p=20617#p20617"><![CDATA[
Hello community,<br /><br />I've been trying to get the HID MOUSE example working from the v-usb package, but it's not working for me.<br /><br />I have a ATmega162-16PU and I just can't establish an usb connection. My laptop says it's found &quot;a unknown device&quot;. I've been working for days now to find the problem, but i just cant find it. it'll be great if someone could help me.(Maybe it's my fuses that are not set right, but i'm not so sure, since i already broken a ATMEGA32-16PU with the wrong fuses...)<br /><br />Could someone check if my fuses are right and check the code? As I don't have much time left till my deadline...<br /><br />Anyways Thanks!<br /><br />This is a picture of my current breadboard, i'm trying to follow this guide(With the HID Bootloader), but no luck(The blue lines are the connectors for ISP programming):<br /><br /><a href="http://imageshack.us/photo/my-images/210/imag0153xs.jpg/" class="postlink"><img src="http://img210.imageshack.us/img210/4532/imag0153xs.jpg" class="postimage" alt="Image" /></a><br /><br /><br />I normally upload the .hex file with &quot;Mysmallusb Light&quot; and with the program: &quot;myAVR_ProgTool&quot;(ISP Programmer), as i don't know how to upload with Avrdude though STK500 with COM1 port(referring to the ISP programmer mentioned earlier).<br /><br />This is my makefile<br /><div class="codebox"><p>Code: </p><pre><code># Name: Makefile<br /># Project: hid-mouse example<br /># Author: Christian Starkjohann<br /># Creation Date: 2008-04-07<br /># Tabsize: 4<br /># Copyright: (c) 2008 by OBJECTIVE DEVELOPMENT Software GmbH<br /># License: GNU GPL v2 (see License.txt), GNU GPL v3 or proprietary (CommercialLicense.txt)<br /># This Revision: $Id: Makefile 692 2008-11-07 15:07:40Z cs $<br /><br />DEVICE  = atmega162<br />F_CPU   = 12000000   # in Hz<br />FUSE_L  = 0xDF # see below for fuse values for particular devices<br />FUSE_H  = 0x89<br />FUSE_E  = 0xFB<br />AVRDUDE = avrdude -c usbasp -p $(DEVICE) # edit this line for your programmer<br /><br />CFLAGS  = -Iusbdrv -I. -DDEBUG_LEVEL=0<br />OBJECTS = usbdrv/usbdrv.o usbdrv/usbdrvasm.o usbdrv/oddebug.o main.o<br /><br />COMPILE = avr-gcc -Wall -Os -DF_CPU=$(F_CPU) $(CFLAGS) -mmcu=$(DEVICE)<br /><br />##############################################################################<br /># Fuse values for particular devices<br />##############################################################################<br /># If your device is not listed here, go to<br /># http://palmavr.sourceforge.net/cgi-bin/fc.cgi<br /># and choose options for external crystal clock and no clock divider<br />#<br />################################## ATMega8 ##################################<br /># ATMega8 FUSE_L (Fuse low byte):<br /># 0x9f = 1 0 0 1   1 1 1 1<br />#        ^ ^ \ /   \--+--/<br />#        | |  |       +------- CKSEL 3..0 (external &gt;8M crystal)<br />#        | |  +--------------- SUT 1..0 (crystal osc, BOD enabled)<br />#        | +------------------ BODEN (BrownOut Detector enabled)<br />#        +-------------------- BODLEVEL (2.7V)<br /># ATMega8 FUSE_H (Fuse high byte):<br /># 0xc9 = 1 1 0 0   1 0 0 1 &lt;-- BOOTRST (boot reset vector at 0x0000)<br />#        ^ ^ ^ ^   ^ ^ ^------ BOOTSZ0<br />#        | | | |   | +-------- BOOTSZ1<br />#        | | | |   + --------- EESAVE (don't preserve EEPROM over chip erase)<br />#        | | | +-------------- CKOPT (full output swing)<br />#        | | +---------------- SPIEN (allow serial programming)<br />#        | +------------------ WDTON (WDT not always on)<br />#        +-------------------- RSTDISBL (reset pin is enabled)<br />#<br />############################## ATMega48/88/168 ##############################<br /># ATMega*8 FUSE_L (Fuse low byte):<br /># 0xdf = 1 1 0 1   1 1 1 1<br />#        ^ ^ \ /   \--+--/<br />#        | |  |       +------- CKSEL 3..0 (external &gt;8M crystal)<br />#        | |  +--------------- SUT 1..0 (crystal osc, BOD enabled)<br />#        | +------------------ CKOUT (if 0: Clock output enabled)<br />#        +-------------------- CKDIV8 (if 0: divide by 8)<br /># ATMega*8 FUSE_H (Fuse high byte):<br /># 0xde = 1 1 0 1   1 1 1 0<br />#        ^ ^ ^ ^   ^ \-+-/<br />#        | | | |   |   +------ BODLEVEL 0..2 (110 = 1.8 V)<br />#        | | | |   + --------- EESAVE (preserve EEPROM over chip erase)<br />#        | | | +-------------- WDTON (if 0: watchdog always on)<br />#        | | +---------------- SPIEN (allow serial programming)<br />#        | +------------------ DWEN (debug wire enable)<br />#        +-------------------- RSTDISBL (reset pin is enabled)<br />#<br />############################## ATTiny25/45/85 ###############################<br /># ATMega*5 FUSE_L (Fuse low byte):<br /># 0xef = 1 1 1 0   1 1 1 1<br />#        ^ ^ \+/   \--+--/<br />#        | |  |       +------- CKSEL 3..0 (clock selection -&gt; crystal @ 12 MHz)<br />#        | |  +--------------- SUT 1..0 (BOD enabled, fast rising power)<br />#        | +------------------ CKOUT (clock output on CKOUT pin -&gt; disabled)<br />#        +-------------------- CKDIV8 (divide clock by 8 -&gt; don't divide)<br /># ATMega*5 FUSE_H (Fuse high byte):<br /># 0xdd = 1 1 0 1   1 1 0 1<br />#        ^ ^ ^ ^   ^ \-+-/ <br />#        | | | |   |   +------ BODLEVEL 2..0 (brownout trigger level -&gt; 2.7V)<br />#        | | | |   +---------- EESAVE (preserve EEPROM on Chip Erase -&gt; not preserved)<br />#        | | | +-------------- WDTON (watchdog timer always on -&gt; disable)<br />#        | | +---------------- SPIEN (enable serial programming -&gt; enabled)<br />#        | +------------------ DWEN (debug wire enable)<br />#        +-------------------- RSTDISBL (disable external reset -&gt; enabled)<br />#<br />################################ ATTiny2313 #################################<br /># ATTiny2313 FUSE_L (Fuse low byte):<br /># 0xef = 1 1 1 0   1 1 1 1<br />#        ^ ^ \+/   \--+--/<br />#        | |  |       +------- CKSEL 3..0 (clock selection -&gt; crystal @ 12 MHz)<br />#        | |  +--------------- SUT 1..0 (BOD enabled, fast rising power)<br />#        | +------------------ CKOUT (clock output on CKOUT pin -&gt; disabled)<br />#        +-------------------- CKDIV8 (divide clock by 8 -&gt; don't divide)<br /># ATTiny2313 FUSE_H (Fuse high byte):<br /># 0xdb = 1 1 0 1   1 0 1 1<br />#        ^ ^ ^ ^   \-+-/ ^<br />#        | | | |     |   +---- RSTDISBL (disable external reset -&gt; enabled)<br />#        | | | |     +-------- BODLEVEL 2..0 (brownout trigger level -&gt; 2.7V)<br />#        | | | +-------------- WDTON (watchdog timer always on -&gt; disable)<br />#        | | +---------------- SPIEN (enable serial programming -&gt; enabled)<br />#        | +------------------ EESAVE (preserve EEPROM on Chip Erase -&gt; not preserved)<br />#        +-------------------- DWEN (debug wire enable)<br /><br /><br /># symbolic targets:<br />help:<br />   @echo &quot;This Makefile has no default rule. Use one of the following:&quot;<br />   @echo &quot;make hex ....... to build main.hex&quot;<br />   @echo &quot;make program ... to flash fuses and firmware&quot;<br />   @echo &quot;make fuse ...... to flash the fuses&quot;<br />   @echo &quot;make flash ..... to flash the firmware (use this on metaboard)&quot;<br />   @echo &quot;make clean ..... to delete objects and hex file&quot;<br /><br />all: hex<br />   <br />hex: main.hex<br /><br />program: flash fuse<br /><br /># rule for programming fuse bits:<br />fuse:<br />   @&#91; &quot;$(FUSE_H)&quot; != &quot;&quot; -a &quot;$(FUSE_L)&quot; != &quot;&quot; &#93; || \<br />      { echo &quot;*** Edit Makefile and choose values for FUSE_L and FUSE_H!&quot;; exit 1; }<br />   $(AVRDUDE) -U hfuse:w:$(FUSE_H):m -U lfuse:w:$(FUSE_L):m<br /><br /># rule for uploading firmware:<br />flash: main.hex<br />   $(AVRDUDE) -U flash:w:main.hex:i<br /><br /># rule for deleting dependent files (those which can be built by Make):<br />clean:<br />   rm -f main.hex main.lst main.obj main.cof main.list main.map main.eep.hex main.elf *.o usbdrv/*.o main.s usbdrv/oddebug.s usbdrv/usbdrv.s<br /><br /># Generic rule for compiling C files:<br />.c.o:<br />   $(COMPILE) -c $&lt; -o $@<br /><br /># Generic rule for assembling Assembler source files:<br />.S.o:<br />   $(COMPILE) -x assembler-with-cpp -c $&lt; -o $@<br /># &quot;-x assembler-with-cpp&quot; should not be necessary since this is the default<br /># file type for the .S (with capital S) extension. However, upper case<br /># characters are not always preserved on Windows. To ensure WinAVR<br /># compatibility define the file type manually.<br /><br /># Generic rule for compiling C to assembler, used for debugging only.<br />.c.s:<br />   $(COMPILE) -S $&lt; -o $@<br /><br /># file targets:<br /><br /># Since we don't want to ship the driver multipe times, we copy it into this project:<br />usbdrv:<br />   cp -r ../../../usbdrv .<br /><br />main.elf: usbdrv $(OBJECTS)   # usbdrv dependency only needed because we copy it<br />   $(COMPILE) -o main.elf $(OBJECTS)<br /><br />main.hex: main.elf<br />   rm -f main.hex main.eep.hex<br />   avr-objcopy -j .text -j .data -O ihex main.elf main.hex<br />   avr-size main.hex<br /><br /># debugging targets:<br /><br />disasm:   main.elf<br />   avr-objdump -d main.elf<br /><br />cpp:<br />   $(COMPILE) -E main.c<br /><br /></code></pre></div><br /><br />This is my 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 />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 />*/<br /><br />/* ---------------------------- Hardware Config ---------------------------- */<br /><br />#define USB_CFG_IOPORTNAME      D<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      3<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    1<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      100<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           20<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 />#define USB_CFG_HAVE_MEASURE_FRAME_LENGTH   0<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       0xe8, 0x03 /* VOTI's lab use PID */<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     'o', 'b', 'd', 'e', 'v', '.', 'a', 't'<br />#define USB_CFG_VENDOR_NAME_LEN 8<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     'M', 'o', 'u', 's', 'e'<br />#define USB_CFG_DEVICE_NAME_LEN 5<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        0<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     3<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    52<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><p>Statistics: Posted by <a href="https://forums.obdev.at/memberlist.php?mode=viewprofile&amp;u=6235">IloveIphonyWikyBolex</a> — Sun Jan 08, 2012 12:11 am</p><hr />
]]></content>
	</entry>
	</feed>
