Back to the beginning

[AndyFreestone]

Just to try something, I was playing with a working example.

By changing the values written to Port B I would have expected the LED pattern to change. It didn't is stayed exactly the same.

Even when I removed all the calls to write to all the ports they kept on flashing as per the original program.

Do I have to delete the old .hex file and then recompile? I would have expected a recompile to overwrite a previous version ?

[Demon]

You really should bring this up on a forum that supports your programmer.

[Acetronics2]

Hi, Andy

playing it simple ...

I 'm working for years with an Easypic 5 ... Ok ???


1) you need to have the " Mikroprog suite for pic " and its drivers ( on your EasyPic CD or Here http://www.mikroe.com/easypic/programming/ ) installed.

2) connect your Easypic with the USB cable to your computer. power ON

3) open the mikroprog suite and @ first choose processor family and processor reference
Then hit : File/Load Hex in the upper left menu ... and browse for the PbP Hex generated file you want to program.

it's Here for me : C:\Documents and Settings\Alain\MCS_Prog ... Yes, Alain is my name !

4) Hit the " code" Button to show your Hex in the appearing window ...

5) Hit the " WRITE" button just under the processor reference ...

it runs ...

Alain

Edit ...

AND ...YES ... Easypic can be directly driven from MCS ...
just browse this forum to find the " How to " ...

[HenrikOlsson]

Andy,
Are you sure that you're actually ARE reprogramming the chip? It doesn't sound like you are to me.
Of course you MUST recompile the program and of course you MUST reprogram the chip - how else would it work? When you recompile the .hex file on disc will be replaces with the newly compiled (no need to delete it) but the one in the chip will of course only be replaced when you reprogram the chip. The above is how PBP and MicroCodeStudio does it. If you're actually working with the MikroE examples and their compiler then I don't know and you'll be better off asking the question on the MikroE forum.

Normally the programmer automatically erases the chip before programming but I'm sure there are settings for that in the programmer software.
If you load a .hex file into your programmer software you can use the VERIFY function in the software to compare that .hex file to the one currently in the chip. If they are not the same then you haven't reprogrammed the chip properly.

Robert,
Come on, give the guy a break will you, he's new at this and apparently struggling quite a bit (more than anyone in a long time for some reason).

/Henrik.

[Acetronics2]

Addendum due to the Timeout for editing...

Programmer file : Microprog suite for Pic.exe

Location : " C:\program Files\Mikroelektronika\Microprog suite for Pic

Parameter line : -pPIC$target-device$ -f$hex-filename$ -e -w

" tested and verified " ... no need to enter family and device ref then ...

[AndyFreestone]

Addendum due to the Timeout for editing...

Programmer file : Microprog suite for Pic.exe

Location : " C:\program Files\Mikroelektronika\Microprog suite for Pic

Parameter line : -pPIC$target-device$ -f$hex-filename$ -e -w

" tested and verified " ... no need to enter family and device ref then ...


Sorry but that might as well be in Japanese to me.

[Demon]

... You really should bring this up on a forum that supports your programmer.

vs

... If you're actually working with the MikroE examples and their compiler then I don't know and you'll be better off asking the question on the MikroE forum.
...
Robert,
Come on, give the guy a break will you, he's new at this and apparently struggling quite a bit (more than anyone in a long time for some reason).

/Henrik.

Didn't I say the same thing? lol

All he needs is to get one example working right on whatever chip he decides to use. He's got at least 2 to work with now, so it's down to hardware connection/setup, or programmer software.

Robert