Search found 43 matches

So with the added confidence of getting it to work with the internal oscillator, I played around with the code a bit more to get it to work with my external (I think???) oscillator.

I think this wa ...

I don't know why setting up the clock on the PIC gives me such a headache, but I just can't get a simple "Hello World" going on my RS232 port.

so far:

#INCLUDE <18F46K80.h>
#NOD ...

So if the device is USB powered, I have no issue sustaining a connection forever.

It is only when I use an external power supply that the issue crops up. My EE is going to look into some condition ...

I had the same line of thinking, Ttelmah...

Brought the sucker home over the weekend. I ran the same example 12 program for 16 hours straight with no issues. I used a different (brand new) USB ca ...

Oddly enough, this same thing occurs when I use the CCS USB demo board as well.

I used the same fuses and clock setup as laid out in the USB exercise book.

Same issue, even with a 1 µF capacitor in place for VUSB.

0.47 µF ceramic cap.

I'll see if I can track down a 1 µF cap see if the issue comes up again.

The "putc" functions use the byte value of the input.

The following all output the character A
putc('A')
putc(65)
putc(0x41)

I would recommend looking into the printf() function in ...

Another thought (moving away from PIC programming and into PC HW architecture and settings), but could there be something with the port powering down when the PC locks or idles or something?

I ran example 12 from the USB exercise book. On two different machines.
First - Windows 7 - 64 bit, Intel ICH10 USB controller
Second - Windows XP - 32 bit, Intel IC7 USB Controller

Sadly, I got ...

Unfortunately, I am using Windows 7, but 64-bit.
My chipset is the Intel ICH10.

Maybe some other info that would help...

My client program is written in C#. I am using the System.IO.Ports namespace to handle the data transfer on the PC side. All that happens when I get this ...

20 minutes later (actually 18), communication ceased.

I am going to try a couple more things to see if there is something in the usb_cdc driver that will help diagnose the issue at hand.

OK, so I poked around in the examples a little more and found this comment:

usb_task() must be called periodically in your main loop. If it is not called faster than once per millisecond, USB may ...

I am on a PIC18F2550.

I adapted my USB handling from the CDC example provided with the USB demo board. Everything works fine for about an hour, then just goes kaput.