easyHID question

[keymuu]

ok, back again....

220nF is the value recommended in the datasheet.

changed the Vusb=100nF to 200nF (added another 100nF), but this did not change anything, no ding-dong sound. Ok one small change, before there was a pop-up window telling that the USB port is not usable. That pop-up window does not come anymore, but the port still dies after the second connection and the PC needs a reboot to come alive again.

The 22 ohms should be fine. I've just never seen them before. Your reference to the SN65220 helped with that problem.

Ok on the +5V.
I prefer to detect the plugged status in a USB interrupt, because it tells you when it's communicating with the computer. The way you have it, it only detects if it's plugged into a port or hub. But that's not going to help the problem at this point.

The USB connection is not a high priority matter, not now and not later either, don't now yet how to implement it...on portB change interrupt perhaps...

There are several things that can go wrong here, we'll just have to work through it.

You mentioned before ...
> The programmer configuration is: ...

Are you setting the config's manually in the programmer's software?
If so, is the VREGEN bit enabled? (Turns on the 3.3v regulator)

The configuration, the mePROG configuration is attached. Where else could one set any configurations, one would think that easyHID could do that job for you... I do not know where that would be...

I assume you've blinked an LED somewhere to verify the oscillator is running at the correct speed.

No LED blinking, however I have verified that PIC runs with the correct speed. Can tell, that if the speed is not correct and then when you connect it to your PC it will tell you something like "An illegal USB device is....". I have quite fresh experience of that. I have also verified the speed with a oscilloscope to be correct now. And as earlier told, PIC works just fine with the USB commands commented in Pic Basic Rro.

On these chips, if the main oscillator isn't working, it can switch over to the internal oscillator at a different freq.

I'm not quite sure about this, meaning what? If it works without USB (same configuration) shouldn't it the work also with the USB or at least every part should see the right frequency. As earlier said, it works fine without the USB compiled to the code. Ex. if you have a 12MHz crystal, it is first, inside PIC divided with 3 (12/3, 8/2, 4/1, 16/4, 20/5 etc) to get 4MHz that is then multiplied to 96MHZ that goes to USB use and on the other hand divided with 2 to get the 48MHz for the PIC other parts. Then when one instruction takes 4 clock cycles to accomplish, the real speed of a 48MHz PIC is actually 12MHz. That is when you can see the crystal frequency, the reference. So, one basic instruction is about 83 ns long.
Correct?