[C] [Atmega168][VUSB] Nierozpoznano urządzenia USB

[bordeux]

Witam

Próbuje stworzyć moduł USB. W tym celu używam biblioteki V-USB.

Tutaj schemat urządzenia:

Tutaj komunikat po podłączeniu do USB:

FUSY są ustawione odpowiednio:

Mój program:

/* Name: main.c
* Project: DDS based on ObDev's PowerSwitch based on AVR USB driver
* Author: Christian Starkjohann (PowerSwitch) and Thomas Baier DG8SAQ (DDS extensions)
* Creation Date: 2005-01-16
* Tabsize: 4
* Copyright: (c) 2005 by OBJECTIVE DEVELOPMENT Software GmbH
* License: GNU GPL v2 (see License.txt) or proprietary (CommercialLicense.txt)
* This Revision: 
*/
#include <avr/io.h>
#include <avr/interrupt.h>
#include <avr/pgmspace.h>
#include <avr/wdt.h>

#include "usbdrv/usbdrv.h"
#include "usbdrv/oddebug.h"


#define DDS1_SDA (1<<1)		//PORTB1
#define DDS_SCL  (1<<3)		//PORTB3
#define DDS_UPDATE (1<<4)	//PORTB4

static uchar usb_val;

USB_PUBLIC uchar usbFunctionWrite(uchar *data, uchar len) //sends len bytes to DDS_SDA
{
uchar i;
uchar b;
uchar adr=0;
while (len!=0){
	b=1;
	for (i=0;i<8;i++){
		if (b & data[adr]){
			PORTB = (PORTB | DDS1_SDA) & ~DDS_SCL;
			PORTB = PORTB | DDS_SCL;
		}
		else{
			PORTB = PORTB & (~DDS1_SDA & ~DDS_SCL);
			PORTB = PORTB | DDS_SCL;
		}
		b=b<<1;
	}
len--;
adr++;
}
if (usb_val){
   PORTB = PORTB | DDS_UPDATE;		// update DDS
PORTB = PORTB & ~DDS_UPDATE;
   }
return 1;
}


USB_PUBLIC uchar usbFunctionSetup(uchar data[8])
{
usbRequest_t *rq = (void *)data;
static uchar    replyBuf[3];
   usbMsgPtr = replyBuf;
if(rq->bRequest == 0){       		// ECHO value
       replyBuf[0] = data[2];			// rq->bRequest identical data[1]!
       replyBuf[1] = data[3];
       return 2;
   }
if(rq->bRequest == 1){       		// set port directions
       //DDRA = data[2];
       DDRB = data[3];
	DDRD = data[4] & (~USBMASK & ~(1 << 2)); // protect USB interface
       return 0;
   }
if(rq->bRequest == 2){       		// read ports 
       //replyBuf[0] = PINA;
       replyBuf[1] = PINB;
	replyBuf[2] = PIND;
       return 3;
}
if(rq->bRequest == 3){       		// read port states 
       //replyBuf[0] = PORTA;
       replyBuf[1] = PORTB;
	replyBuf[2] = PORTD;
       return 3;
   }
if(rq->bRequest == 4){       		// set ports 
       //PORTA = data[2];
       PORTB = data[3];
	PORTD = data[4];
       return 0;
   }
if(rq->bRequest == 5){       		// use usbFunctionWrite to transfer len bytes to DDS
	usb_val = data[2];				// usb_val!=0 => DDS update pulse after data transfer
       return 0xff;
}
if(rq->bRequest == 6){       
       PORTB = PORTB | DDS_UPDATE;		// issue update pulse to DDS
	PORTB = PORTB & ~DDS_UPDATE;
       return 0;
   }
replyBuf[0] = 0xff;					// return value 0xff => command not supported 
   return 1;
}


int main(void)
{
wdt_enable(WDTO_1S);	//set Watchdog Timer
odDebugInit();
PORTB=0xe0;				//Set PortB 0-4 zero
DDRB=0x1f; 				//Set PORTB 0-4 output
   PORTD = 0;          	/* no pullups on USB pins */
   DDRD = ~USBMASK & ~(1 << 2);    /* all outputs except USB data and PD2 = INT0 */
   usbInit();
   sei();
   for(;;){    /* main event loop */
    wdt_reset();//restart watchdog timer
       usbPoll();
   }
   return 0;
}

Tutaj config dla v-usb:

/* Name: usbconfig.h
* Project: AVR USB driver
* Author: Christian Starkjohann
* Creation Date: 2005-04-01
* Tabsize: 4
* Copyright: (c) 2005 by OBJECTIVE DEVELOPMENT Software GmbH
* License: GNU GPL v2 (see License.txt) or proprietary (CommercialLicense.txt)
* This Revision: $Id: usbconfig.h 43 2005-04-10 21:04:36Z cs $
*/

#ifndef __usbconfig_h_included__
#define __usbconfig_h_included__

#define  F_CPU   12000000

/*
General Description:
This file contains parts of the USB driver which can be configured and can or
must be adapted to your hardware.

Please note that the usbdrv contains a usbconfig-prototype.h file now. We
recommend that you use that file as a template because it will always list
the newest features and options.
*/

/* ---------------------------- Hardware Config ---------------------------- */

#define USB_CFG_IOPORTNAME      D
/* This is the port where the USB bus is connected. When you configure it to
* "B", the registers PORTB, PINB and DDRB will be used.
*/
#define USB_CFG_DMINUS_BIT      1
/* This is the bit number in USB_CFG_IOPORT where the USB D- line (pin 2) is connected.
* This may be any bit in the port.
*/
#define USB_CFG_DPLUS_BIT       0
/* This is the bit number in USB_CFG_IOPORT where the USB D+ line (pin 3) is connected.
* This may be any bit in the port. Please note that D+ must also be connected
* to interrupt pin INT0!
*/
/* #define USB_CFG_CLOCK_KHZ       (F_CPU/1000) */
/* Clock rate of the AVR in MHz. Legal values are 12000, 16000 or 16500.
* The 16.5 MHz version of the code requires no crystal, it tolerates +/- 1%
* deviation from the nominal frequency. All other rates require a precision
* of 2000 ppm and thus a crystal!
* Default if not specified: 12 MHz
*/

/* ----------------------- Optional Hardware Config ------------------------ */

/* #define USB_CFG_PULLUP_IOPORTNAME   D */
/* If you connect the 1.5k pullup resistor from D- to a port pin instead of
* V+, you can connect and disconnect the device from firmware by calling
* the macros usbDeviceConnect() and usbDeviceDisconnect() (see usbdrv.h).
* This constant defines the port on which the pullup resistor is connected.
*/
/* #define USB_CFG_PULLUP_BIT          4 */
/* This constant defines the bit number in USB_CFG_PULLUP_IOPORT (defined
* above) where the 1.5k pullup resistor is connected. See description
* above for details.
*/

/* --------------------------- Functional Range ---------------------------- */

#define USB_CFG_HAVE_INTRIN_ENDPOINT    0
/* Define this to 1 if you want to compile a version with two endpoints: The
* default control endpoint 0 and an interrupt-in endpoint 1.
*/
#define USB_CFG_HAVE_INTRIN_ENDPOINT3   0
/* Define this to 1 if you want to compile a version with three endpoints: The
* default control endpoint 0, an interrupt-in endpoint 1 and an interrupt-in
* endpoint 3. You must also enable endpoint 1 above.
*/
#define USB_CFG_IMPLEMENT_HALT          0
/* Define this to 1 if you also want to implement the ENDPOINT_HALT feature
* for endpoint 1 (interrupt endpoint). Although you may not need this feature,
* it is required by the standard. We have made it a config option because it
* bloats the code considerably.
*/
#define USB_CFG_INTR_POLL_INTERVAL      10
/* If you compile a version with endpoint 1 (interrupt-in), this is the poll
* interval. The value is in milliseconds and must not be less than 10 ms for
* low speed devices.
*/
#define USB_CFG_IS_SELF_POWERED         0
/* Define this to 1 if the device has its own power supply. Set it to 0 if the
* device is powered from the USB bus.
*/
#define USB_CFG_MAX_BUS_POWER           500
/* Set this variable to the maximum USB bus power consumption of your device.
* The value is in milliamperes. [It will be divided by two since USB
* communicates power requirements in units of 2 mA.]
*/
#define USB_CFG_IMPLEMENT_FN_WRITE      1
/* Set this to 1 if you want usbFunctionWrite() to be called for control-out
* transfers. Set it to 0 if you don't need it and want to save a couple of
* bytes.
*/
#define USB_CFG_IMPLEMENT_FN_READ       0
/* Set this to 1 if you need to send control replies which are generated
* "on the fly" when usbFunctionRead() is called. If you only want to send
* data from a static buffer, set it to 0 and return the data from
* usbFunctionSetup(). This saves a couple of bytes.
*/
#define USB_CFG_IMPLEMENT_FN_WRITEOUT   0
/* Define this to 1 if you want to use interrupt-out (or bulk out) endpoint 1.
* You must implement the function usbFunctionWriteOut() which receives all
* interrupt/bulk data sent to endpoint 1.
*/
#define USB_CFG_HAVE_FLOWCONTROL        0
/* Define this to 1 if you want flowcontrol over USB data. See the definition
* of the macros usbDisableAllRequests() and usbEnableAllRequests() in
* usbdrv.h.
*/

/* -------------------------- Device Description --------------------------- */

#define  USB_CFG_VENDOR_ID  0xc0, 0x16  /* 5824 in dec, stands for VOTI */
/* USB vendor ID for the device, low byte first. If you have registered your
* own Vendor ID, define it here. Otherwise you use obdev's free shared
* VID/PID pair. Be sure to read USBID-License.txt for rules!
*/
#define USB_CFG_DEVICE_ID   0xdc, 0x05  /* 1500 in dec, obdev's free PID */
/* This is the ID of the product, low byte first. It is interpreted in the
* scope of the vendor ID. If you have registered your own VID with usb.org
* or if you have licensed a PID from somebody else, define it here. Otherwise
* you use obdev's free shared VID/PID pair. Be sure to read the rules in
* USBID-License.txt!
*/
#define USB_CFG_DEVICE_VERSION  0x00, 0x01
/* Version number of the device: Minor number first, then major number.
*/
#define USB_CFG_VENDOR_NAME     'B', 'o', 'r', 'd', 'e', 'u', 'x', '.', 'N', 'E', 'T'
#define USB_CFG_VENDOR_NAME_LEN 11
/* These two values define the vendor name returned by the USB device. The name
* must be given as a list of characters under single quotes. The characters
* are interpreted as Unicode (UTF-16) entities.
* If you don't want a vendor name string, undefine these macros.
* ALWAYS define a vendor name containing your Internet domain name if you use
* obdev's free shared VID/PID pair. See the file USBID-License.txt for
* details.
*/
#define USB_CFG_DEVICE_NAME     'B', 'O', 'R', 'D', 'E', 'U', 'X', '-', 'D', 'X'
#define USB_CFG_DEVICE_NAME_LEN 10
/* Same as above for the device name. If you don't want a device name, undefine
* the macros. See the file USBID-License.txt before you assign a name.
*/
/*#define USB_CFG_SERIAL_NUMBER   'N', 'o', 'n', 'e' */
/*#define USB_CFG_SERIAL_NUMBER_LEN   0 */
/* Same as above for the serial number. If you don't want a serial number,
* undefine the macros.
* It may be useful to provide the serial number through other means than at
* compile time. See the section about descriptor properties below for how
* to fine tune control over USB descriptors such as the string descriptor
* for the serial number.
*/
#define USB_CFG_DEVICE_CLASS    0xff
#define USB_CFG_DEVICE_SUBCLASS 0
/* See USB specification if you want to conform to an existing device class.
*/
#define USB_CFG_INTERFACE_CLASS     0
#define USB_CFG_INTERFACE_SUBCLASS  0
#define USB_CFG_INTERFACE_PROTOCOL  0
/* See USB specification if you want to conform to an existing device class or
* protocol.
*/
#define USB_CFG_HID_REPORT_DESCRIPTOR_LENGTH    0   /* total length of report descriptor */
/* Define this to the length of the HID report descriptor, if you implement
* an HID device. Otherwise don't define it or define it to 0.
*/

/* ------------------- Fine Control over USB Descriptors ------------------- */
/* If you don't want to use the driver's default USB descriptors, you can
* provide our own. These can be provided as (1) fixed length static data in
* flash memory, (2) fixed length static data in RAM or (3) dynamically at
* runtime in the function usbFunctionDescriptor(). See usbdrv.h for more
* information about this function.
* Descriptor handling is configured through the descriptor's properties. If
* no properties are defined or if they are 0, the default descriptor is used.
* Possible properties are:
*   + USB_PROP_IS_DYNAMIC: The data for the descriptor should be fetched
*     at runtime via usbFunctionDescriptor().
*   + USB_PROP_IS_RAM: The data returned by usbFunctionDescriptor() or found
*     in static memory is in RAM, not in flash memory.
*   + USB_PROP_LENGTH(len): If the data is in static memory (RAM or flash),
*     the driver must know the descriptor's length. The descriptor itself is
*     found at the address of a well known identifier (see below).
* List of static descriptor names (must be declared PROGMEM if in flash):
*   char usbDescriptorDevice[];
*   char usbDescriptorConfiguration[];
*   char usbDescriptorHidReport[];
*   char usbDescriptorString0[];
*   int usbDescriptorStringVendor[];
*   int usbDescriptorStringDevice[];
*   int usbDescriptorStringSerialNumber[];
* Other descriptors can't be provided statically, they must be provided
* dynamically at runtime.
*
* Descriptor properties are or-ed or added together, e.g.:
* #define USB_CFG_DESCR_PROPS_DEVICE   (USB_PROP_IS_RAM | USB_PROP_LENGTH(18))
*
* The following descriptors are defined:
*   USB_CFG_DESCR_PROPS_DEVICE
*   USB_CFG_DESCR_PROPS_CONFIGURATION
*   USB_CFG_DESCR_PROPS_STRINGS
*   USB_CFG_DESCR_PROPS_STRING_0
*   USB_CFG_DESCR_PROPS_STRING_VENDOR
*   USB_CFG_DESCR_PROPS_STRING_PRODUCT
*   USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER
*   USB_CFG_DESCR_PROPS_HID
*   USB_CFG_DESCR_PROPS_HID_REPORT
*   USB_CFG_DESCR_PROPS_UNKNOWN (for all descriptors not handled by the driver)
*
*/

#define USB_CFG_DESCR_PROPS_DEVICE                  0
#define USB_CFG_DESCR_PROPS_CONFIGURATION           0
#define USB_CFG_DESCR_PROPS_STRINGS                 0
#define USB_CFG_DESCR_PROPS_STRING_0                0
#define USB_CFG_DESCR_PROPS_STRING_VENDOR           0
#define USB_CFG_DESCR_PROPS_STRING_PRODUCT          0
#define USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER    0
#define USB_CFG_DESCR_PROPS_HID                     0
#define USB_CFG_DESCR_PROPS_HID_REPORT              0
#define USB_CFG_DESCR_PROPS_UNKNOWN                 0

/* ----------------------- Optional MCU Description ------------------------ */

/* The following configurations have working defaults in usbdrv.h. You
* usually don't need to set them explicitly. Only if you want to run
* the driver on a device which is not yet supported or with a compiler
* which is not fully supported (such as IAR C) or if you use a differnt
* interrupt than INT0, you may have to define some of these.
*/
/* #define USB_INTR_CFG            MCUCR */
/* #define USB_INTR_CFG_SET        ((1 << ISC00) | (1 << ISC01)) */
/* #define USB_INTR_CFG_CLR        0 */
/* #define USB_INTR_ENABLE         GIMSK */
/* #define USB_INTR_ENABLE_BIT     INT0 */
/* #define USB_INTR_PENDING        GIFR */
/* #define USB_INTR_PENDING_BIT    INTF0 */

#endif /* __usbconfig_h_included__ */

Tutaj projekt do pobrania - w Eclipse AVR:

http://bordeux.net/USB_module.zip

Gdzie leży błąd? Od rana nad tym pracuję i nie potrafię rozgryźć problemu.

[bordeux]

a jak zbadać to? Jak zbadać to czy soft jest do kitu czy płytka?

[rafal-bielsko]

Jeśli nie masz możliwości debugowania to zdefiniuj sobie jeden pin i podlącz tam diodę.

Potem w programie wklej sobie w miejsce gdzie masz wątpliwości "ledon;" i będziesz wiedzieć gdzie program wchodzi a gdzie nie.

Może w ten sposób trafisz na kawałek kodu który nie jest realizowany.

Płytkę zawsze warto sprawdzić kilka razy ale bez przesady 🙂.

Tu masz gotowe definicje dla PB0:

#define ledon DDRB  |= _BV(0);PORTB |= _BV(0);
#define ledoff DDRB  |= _BV(0);PORTB &= ~_BV(0);