Dave
Always wear safety glasses while programming.
Dave,
Thanks for the link, but unfortunately it didn't work. I'm 95% sure this is not a driver issue. I've tried connecting the PIC+board to 6 different computers now - 2 with success and 4 without. The 2 I had success with have lots in common - they're both Acer Desktop computers of about the same vintage and both run XP; however I don't think one has SP3 installed and I tend to agree it's not a service pack issue.
When I *initially* (ie. for the very 1st time) connect the PIC+CDC code to one of these Acer Desktops, the USB controller communicates with it well and gathers straight away that it has a CDC device connected. A little bit later it'll ask for a driver and all be it fine and dandy.
The machines that it doesn't work with have not much in common - 1 old XP laptop, 1 vista laptop and 2 non Acer desktops running XP - don't get to the stage of recognizing any of the identification or capabilities of the device.
So, I'm tending to think the issue is either a USB controller or a hardware issue?
If I *omit* the line OSCTUNE 0.6 = 1 which activates the PLL, which I think multiplies my 12Mhz crystal speed x4 to enable all speed modes of USB, I get the same "Device Not Recognized" error with the Acer Desktops. This leads me to think the process or mechanism that enables the host to recognize there's a USB device attached doesn't require the system clock to function properly perhaps? Dunno... But to get any further than acknowledging it has an unrecognizable USB device attached does require a working clock that complies with the USB requirements and the various correct protocols and handshaking for the enumeration to at least get to the point of the operating system to request a specific driver (if required)?
Troy.
Comment out the OSCTUNE line and have the configs set like this.
Code:__CONFIG _CONFIG1L, _CPUDIV_NOCLKDIV_1L & _USBDIV_OFF_1L __CONFIG _CONFIG1H, _FOSC_HS_1H & _PLLEN_ON_1H & _PCLKEN_ON_1H & _FCMEN_OFF_1H & _IESO_OFF_1H __CONFIG _CONFIG2H, _WDTEN_ON_2H & _WDTPS_512_2H __CONFIG _CONFIG4L, _STVREN_ON_4L & _LVP_OFF_4L & _BBSIZ_OFF_4L & _XINST_OFF_4L
Dave
Always wear safety glasses while programming.
Tried it. No luck on the Vista notebook, but it still works fine on the Acer Desktop boxes ie. status quo.mackrackit
Comment out the OSCTUNE line and have the configs set like this.
One thing I have noticed when I program the chip via the Microchip PICkit 2 interface is that a yellow message always appears after loading a HEX file compiled from a PBP example stating that some of the configuration words are not in the HEX file and requests me to check the configuration settings to verify they're ok. I'm assuming this isn't the cause of my grief as I've also tried to load some of Microchip's PIC18F precompiled examples where the message didn't come up, but still no luck on the Vista notebook.
Troy.
It's working on the vista notebook!
The fix could be classified as something obvious that I should've known or read about, but it took a fair bit of analyzing and reading to finally pinpoint the issue. It was a jumper (J12) on the Microchip development board which I left open that connected the VUSB; so Dave you were on the right track to begin with. Obviously the thing that really threw me off the scent was the fact it would work fine on some computers and not others.
Thanks again for the assistance Dave,
Cheers,
Troy.
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks