Curious,
That means the CPU is running at 24mhz.
Why not run at 48mhz, since it's available.
_CPUDIV_OSC1_PLL2_1L
<br>
Curious,
That means the CPU is running at 24mhz.
Why not run at 48mhz, since it's available.
_CPUDIV_OSC1_PLL2_1L
<br>
DT
Sure it will!
Did you have...
DEFINE OSC 48
I use 48mhz CPU with USB without any problems.
<br>
DT
I can't make it NOT recognize the device when the OSC is 48 with 20mhz crystal.
Did you increase the size of the VUSB cap like mister_e suggested?
The way you have it now, the CPU is running at 24mhz. But, PBP thinks it 48mhz because of the DEFINE OSC 48. Any Time related statements will take twice as long.
If you are going to leave it at 24mhz? You should change to
DEFINE OSC 24
But I'd suggest trying 48 again.
<br>
DT
Yup I've changed the cap to 220nF
I've tried many configurations
20MHz Crystal
__CONFIG _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L ;with OSC 48 ; NON-WORKING
__CONFIG _CONFIG1L, _PLLDIV_5_1L & _CPUDIV_OSC3_PLL4_1L & _USBDIV_2_1L ;with OSC 24 ; WORKING
4MHz Crystal
__CONFIG _CONFIG1L, _PLLDIV_1_1L & _CPUDIV_OSC1_PLL2_1L & _USBDIV_2_1L ; with OSC 48 ; NON-WORKING ;Original post
__CONFIG _CONFIG1L, _PLLDIV_1_1L & _CPUDIV_OSC3_PLL4_1L & _USBDIV_2_1L ; with OSC 24 ; WORKING
I've seeking all the day to find the solution, I thus don't find it now I would continue to use it under 24MHz
But now I am occupied to migrate the code from VB6 towards VB.NET 2005 but I have a problem. I suppose that the post here is not welcome ?
Bookmarks