PIC18F4850 will not oscillate

[mackrackit]

You do still do not have the OSC set for HS

[Darrel Taylor]

Dave, I don't think you imported the .hex file.

Here's what meProg shows ...

[mackrackit]

Dave, I don't think you imported the .hex file.

DOH!!! I imported something... Now that I do it again, MPLAB shows the same as you.

[Archangel]

Hi,
It looks like all your smt caps are shorted in the PCb traces, is that possible ?

[IRQ_Diode]

Joe,

I am not sure what you mean. Are you saying if maybe the caps got shorted when solder?mmm... you know what I have not checked on that.

After opening a ticket with Microchip, they could not help me much either. They thought that maybe I damaged the crystal when I solder it. Which I suppose it could be a possibility.

Since I had to order new boards anyways, I placed the XTAL closer to the PIC (Maybe 15-30mils closer) and the new boards work fine. So I am not sure what happen before but I guess it is one of those items I will not find out what happen without using up more time that I already have.

Thanks for the help.

[Archangel]

Not a solder bridge, but copper where it should not be? Looks like the traces bridge the caps and some other components. Looks like exacto knife time.

[IRQ_Diode]

Joe,

I see what you mean now. My bad, the layout I uploaded is black and white, and the component bodies are part of my capture. Those aren't really copper, they are just the bodies of the components.

[mark_s]

Another silly thought. Some times you can open a hex file in the melabs programmer and it's not the latest. The compiler may be storing it in a different directory. You may be opening an older version of your hex file from another directory. As much as you modify your basic code, you keep programing the chip with the same hex. Recompile and check the date and time stamp on the file. I have used that chip before and it is not difficult to get working. If you post your code, someone can compile it and see whats going on.