Objective Development Forums

Have you tried to burn his exact hex file? Do you have the exact bill of parts ( any differences, out side the caps you mentioned )

Hi, I used many of his projects, I's say start with usbLyzer and print or save what it shows. See if its the descriptor, device, or config that gives the issues. You can use the hot plug feature to get the negotiations. You say it compiles and the usb does not work, then its in the configs. Your on ...

Why not contact Paul?
http://denki.world3.net/

Not sure you come by here or not anymore ( could not reach you via email ) hopping you could just spare a few moments. I was able to apply the patch but it seems the packets stop after 5 tries? I did a test with a blink LED, and I get 5 blinks and then it stops. If I take out the sender while(!usbIn...

Going to go out on a limb here an assume I'm missing the point. However if I'm not, my question to you... Why not switch the defines in the config.h ? Assuming you use the default for most projects. #define USB_CFG_DMINUS_BIT 0 /* This is the bit number in USB_CFG_IOPORT where the USB D- line is con...

Yikes, tampering of the registry is something you need to do at your own risk my friend. Only advise I have there is search for you PID/VID. usbDview is by far the better choice
http://gobbledgeek.wordpress.com/2011/01/10/usbdview/

Yes that is how you do it but if you already have the device install you will need to remove it first. When the device is install windows marks down the name in the registry and changing that in the firmware does not change the registry. Use usbDview or manually edit the registry on your own.

Use the code below, this may help a little. When ( ! usbInterruptIsReady() ) , You are limited to a very small amount of code space before the next pull must be done. I have tried using that section of code to preform a check on the d- line. My need was for a line Low for x amount of time. I realize...

As it says on in the rules please contact us directly through our support form. m Try to keep it short and to the point. " Hi, I want to use separate ports for each of my usb pins. " Wound be a great title. Its a lot more clear then whats on this thread... Indicate you posted a forum threa...

Contact Christian, he will tell you if its do-able. He does not get on the forums much.

If Micha is right and you want D- on Port C and D+ on Port D, I dont think that will work. Why do you need to use another port, is it because of your board wiring?

Huh? Ok the below means PORTD use pin 0 for D- and 2 for D+ #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 0 /* This is the bit number in USB_CFG...

Look in usbconfig.h
'

I dont think much goes on during boot. possible some driver talk as the usb device initialize but then the talk with silence I would guess.

Well I have found its ok to use a loop count of 5 but be sure to kill the interrupts. Since the pin (-) of the usb has a pullup it should normally be hi. I found xp can take a max loop of 20, but vista needs 5 or less. checkAlive() { cli(); DDRD &= ~0x02; for( ; i < 5 ; i++) { //make your test.....