Freezing PIC !

[Acetronics2]

Hi, Picante

At First,You should try to read the device and compare its memory to the "original" HEX ...

with another programmer ...

CONFIG Word writing ( or loading ) problem ???

My easypic5 made it to me once or twice ... as the config word location depends on which IDE was used ...

Alain

[PICante]

Bonjour Alain,

So, what you suspect is that something changes in the HEX file while transferred to the device?

Thanks!

[Acetronics2]

Hi,

Something like that ... I know some IDEs which place the config word in another file than the HEX , whose programmer often losts the "header file" ( where config is located ) location...

most of time when there has been compilation errors before ... and an errorless compilation (since the IDE opening ) is always followed by a good chip programming.


Ahhh ... reliable IDE's ... where are you ???

Alain

[PICante]

Thanks Alain,

I am not sure how you mean: “most of time when there has been compilation errors before ... and an errorless compilation (since the IDE opening ) is always followed by a good chip programming”… and where exactly do you suggest I look for the misplaced file in my environment?

Remember I am kind’ a green in this area! :-)

[Bruce]

it’s a proto board and the programmer is permanently connected (ICSP kind).

This would be my 1st suspect. If the device programmer isn't releasing /MCLR it would
cause it to hang. It may also be causing problems by leaving it connected to the PIC pgm
and data pins.

Have you tried disconnecting your programmer & resetting power to your proto board?

[PICante]

Hi Bruce,

Yes I have tried this even though this programmer is supposed to be internally disconnected as it puts the PIC in run mode. I also tried to removed pull-ups and pull-downs while programming.
However as mentioned before the PIC accepts and run any program not compiled after this “disease” strikes? And this includes programs running in the exact same hardware.

Thanks Bruce.

[Bruce]

Strange problem for sure. I would create two copies of the same program. Something simple
like blink1.bas and blink2.bas. Compile blink1.bas and keep it in a separate directory outside
of my usual code files directory.

Compile blink2.bas and compare the two .hex files. The next time this happens, recompile
blink2.bas and compare the .hex files again.

If they're different you have it narrowed down to some part of the compile process. That
should make it easier to nail down.

I would also try reinstalling stuff one at a time. I.E. reinstall MCS, then test it before you
reinstall PBP or MPLAB. It may be only one of these getting screwed up.

I had some odd problems recently after installing XP service pack 3 where XP would not allow
me to save a ton of various file extensions. I had to do this;
http://www.winhelponline.com/blog/re...in-windows-xp/