No im not, im using melabs pic programmer. Should I take out that define statement?
No im not, im using melabs pic programmer. Should I take out that define statement?
Okay, Finally I got the thing to show up on the pc! A 1k pull up resistor needs to be put on D+ and Vsub!! I was under the assumption that there was an internal pull up resistor there. Maybe I didn't configure that in the code.
Well Thanks for everyones help so far.
The windows doesnt recognize the device tho. So it wont enumerate as an HID device yet.
Last edited by jizyjuice; - 7th April 2007 at 23:40.
There are internal pull-ups. And EasyHID configures them for Full-Speed, so you shouldn't need external ones.
Did you use all the configs from post #11?
In particular _VREGEN_ON_2L.
Your original configs had that turned OFF, just want to make sure it's turned ON now.
It doesn't really matter, it's fine even if not using a bootloader. But if you were using a bootloader it may have caused problems with the config settings, so I thought I'd ask.Should I take out that define statement?
DT
I used the config code from post 11, but _BORV_2_2L and _FCMEN_OFF_1H dont seem to be define for the 2550, so I took them out.
Is there another file i need to include to get these fuses to work correctly?
You still have MPASM 5.02 so it's _FCMEM_OFF_1H
That'll change after you upgrade MPASM.
_BORV_2_2L is defined for the 2550. I can see it in the .LST file in your .ZIP in post #10
Can't image why there would be a problem with it. But since it's in the same line as _VREGEN_ON_2L, it makes me wonder if there's something else wrong with that line which caused the error.
DT
I looked at the list file and it should be _BORV_21_2L. So, now I've set the fuses correctly, nothing happens now. Windows doesnt pop up with anything, not even usb device unrecognized. I have no idea what could be wrong
I set the fuses finally. The brown out reset voltage fuse is _BORV_21_2L, found this looking through the lst file. Now nothing seems to work, not even simple LED flashes. I have no idea what is going on.
Now that you get "nothing". It seems like FCMEM_OFF is doing it's job, and now it's not running on the internal oscillator.
I think your problem might be the 33pf caps on the crystal. Or a bad/wrong crystal.
The datasheet shows that it should be around 22pf for 20mhz.
With FCMEM_ON, the chip will switch over to the internal oscillator if the primary isn't working. You'll see LED's blink, but it's not the right frequency for USB to work.
___________
DT
Q. Why do they put braille on the number pads of drive-through bank machines?
Bookmarks