Freezing PIC !

[mackrackit]

Does your programmer have a "erase before program" option?
And is it set to erase?

[Archangel]

Hi PICante,
You know . . . I'm thinking. . . when you set all that stuff (programs) up in your PC it returns everything to default settings, and then you may or may not go in and rearrange things to your liking, Where am I going with this you say? Maybe your programmer is somehow getting changed from intel hex file output to something else. I think in MCS, under view, program options or whatever it says (I am using my wife's computer so I am telling you this from memory), anyway in there where you change assemblers, there are check boxes which set the assemblers output type, and maybe it is getting it's settings changed.<br>
Edit: on my own computer now. . . Open up MCS, click on the tab marked View, Scroll down the list to "Compile and Program Options" click on this and a window will open, Under the Blue bar labled Compile and Program Options are 3 tabs. Click on the tab marked Programmer. On the lower 1/2 of this tab, right side are 3 check circles, marked as follows INHX8M , INHX85, and finally INHX32. The first one marked INHX8M should be checked.<br> Check this as the source of your problem.

[PICante]

Hi Dave & Joe,

No matter which tab (Compiler, Assembler or Programmer) the setting is INHX8M. The alternatives in my version are INHX8M, INHX8S and INHX32. However this felt like closing in on it since I can program the PIC successfully with any file not compiled after this “disease” strikes.

The programmer performs a (target erase) before slamming the new stuff, the “DOS” window for the programmer looks like this:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corporation

C:\PIC>set XWISP2=port 3

C:\PIC>x 64
 xwisp2 version 1.9.5 for Windows (Jan 24 2008, Open Watcom C/C++ 1.70)
File 64.hex loaded and is Intel Hex format conforming
Detected programmer: Wisp648, firmware version 1.23
Target: 16F688 revision 06 (ID=1186)
Target erased
Transferring program to 16F688 via Wisp648
Transferring program memory...100%
Verifying program memory......100%
Transferring data memory......100%
Verifying data memory.........100%
Transferring ID memory........100%
Verifying ID memory...........100%
Transferring fuses memory.....100%
Verifying fuses memory........100%
Write-Verify operation terminated successfully in 3.58 seconds
Putting target in run mode
xwisp2 terminated successfully in 5.30 seconds

Thanks guys!

[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! :-)