problem on atmega8 with USB_CFG_IOPORTNAME set to D
Posted: Fri Dec 23, 2011 4:55 pm
Hi,
i am having a problem setting USB_CFG_IOPORTNAME to D getting vusb to work. If i use B instead and connect INT0 additionally to D+ everything works fine, only if i use D as USB_CFG_IOPORTNAME and connect D+ directly to INT0 i cant get it to work. I seems to me, that there is a link between using PD2 as IOPORTNAME and as external interrupt at the same time.
this works:
#define USB_CFG_IOPORTNAME B
#define USB_CFG_DMINUS_BIT 0
#define USB_CFG_DPLUS_BIT 1
and connecting a additional wire between B1 and INT0.
this doesnt work:
#define USB_CFG_IOPORTNAME D
#define USB_CFG_DMINUS_BIT 4
#define USB_CFG_DPLUS_BIT 2
Does anyone expirienced simillar issues or has any idea why this could happen?
Greetz, mov01
By the way, i recognized that variables inside PROGMEM now needs to be declared as const(wich is in all available vusb-downloads not the case) getting a vusb firmware compiled with a modern avr-gcc.
i am having a problem setting USB_CFG_IOPORTNAME to D getting vusb to work. If i use B instead and connect INT0 additionally to D+ everything works fine, only if i use D as USB_CFG_IOPORTNAME and connect D+ directly to INT0 i cant get it to work. I seems to me, that there is a link between using PD2 as IOPORTNAME and as external interrupt at the same time.
this works:
#define USB_CFG_IOPORTNAME B
#define USB_CFG_DMINUS_BIT 0
#define USB_CFG_DPLUS_BIT 1
and connecting a additional wire between B1 and INT0.
this doesnt work:
#define USB_CFG_IOPORTNAME D
#define USB_CFG_DMINUS_BIT 4
#define USB_CFG_DPLUS_BIT 2
Does anyone expirienced simillar issues or has any idea why this could happen?
Greetz, mov01
By the way, i recognized that variables inside PROGMEM now needs to be declared as const(wich is in all available vusb-downloads not the case) getting a vusb firmware compiled with a modern avr-gcc.