Author Topic: MPLAB Software Question (Verify Command)  (Read 732 times)

0 Members and 1 Guest are viewing this topic.

Offline ko4nrbsTopic starter

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
MPLAB Software Question (Verify Command)
« on: April 18, 2025, 03:09:23 pm »
I am using MPLAB ver. 6.20 to Read and save the firmware from my PIC16F688 chips.  The boards they are installed on are no longer supported so am saving the firmware in the event one of the PIC chips gets corrupted.  Before I Export the firmware from the PIC I select the Verify command to ensure it was Read properly.   I need to compare the firmware between several different PIC chips to make sure they all have the same firmware.  Does the Verify command do that if I Open the firmware file on the computer and install a different PIC into the Pickit 3 chip programming adapter?   Confused as to what the software is actually Verifying. 
Thanks,
Bill
 

Online JPortici

  • Super Contributor
  • ***
  • Posts: 3634
  • Country: it
Re: MPLAB Software Question (Verify Command)
« Reply #1 on: April 18, 2025, 03:13:25 pm »
I am using MPLAB ver. 6.20 to Read and save the firmware from my PIC16F688 chips.  The boards they are installed on are no longer supported so am saving the firmware in the event one of the PIC chips gets corrupted.  Before I Export the firmware from the PIC I select the Verify command to ensure it was Read properly.   I need to compare the firmware between several different PIC chips to make sure they all have the same firmware.  Does the Verify command do that if I Open the firmware file on the computer and install a different PIC into the Pickit 3 chip programming adapter?   Confused as to what the software is actually Verifying. 
Thanks,
Bill

When you program, unless you specify it, the programmer already verifies.
the process is:
- Program hex file
- Verify (read back and compare with the provided hex file)
- Overwrite the configuration bits to lock readout, if specified in the hex file
 

Offline mikeselectricstuff

  • Super Contributor
  • ***
  • Posts: 14204
  • Country: gb
    • Mike's Electric Stuff
Re: MPLAB Software Question (Verify Command)
« Reply #2 on: April 18, 2025, 03:27:32 pm »
I am using MPLAB ver. 6.20 to Read and save the firmware from my PIC16F688 chips.  The boards they are installed on are no longer supported so am saving the firmware in the event one of the PIC chips gets corrupted.  Before I Export the firmware from the PIC I select the Verify command to ensure it was Read properly.   I need to compare the firmware between several different PIC chips to make sure they all have the same firmware.  Does the Verify command do that if I Open the firmware file on the computer and install a different PIC into the Pickit 3 chip programming adapter?   Confused as to what the software is actually Verifying. 
Thanks,
Bill
yes, verify compares the loaded file with the device
Youtube channel:Taking wierd stuff apart. Very apart.
Mike's Electric Stuff: High voltage, vintage electronics etc.
Day Job: Mostly LEDs
 
The following users thanked this post: ko4nrbs

Online Ian.M

  • Super Contributor
  • ***
  • Posts: 13412
Re: MPLAB Software Question (Verify Command)
« Reply #3 on: April 18, 2025, 03:33:13 pm »
Note that MPLAB does *NOT* give any sort of warning or error message when you read a code protected PIC MCU.  The read-back program memory from a protected PIC is blank (0x0000 NOP filled).   Most commercial products that aren't open source use code protection.  Unless you have *either* checked that you have valid program memory contents and that the CONFIG word(s) don't have any code protection bits enabled, *or* confirmed that you can program a factory fresh PIC and that it runs in your application, this whole exercise is a futile waste of your time and effort.
 
The following users thanked this post: ko4nrbs

Offline ko4nrbsTopic starter

  • Regular Contributor
  • *
  • Posts: 69
  • Country: us
Re: MPLAB Software Question (Verify Command)
« Reply #4 on: April 18, 2025, 03:45:39 pm »
Note that MPLAB does *NOT* give any sort of warning or error message when you read a code protected PIC MCU.  The read-back program memory from a protected PIC is blank (0x0000 NOP filled).   Most commercial products that aren't open source use code protection.  Unless you have *either* checked that you have valid program memory contents and that the CONFIG word(s) don't have any code protection bits enabled, *or* confirmed that you can program a factory fresh PIC and that it runs in your application, this whole exercise is a futile waste of your time and effort.
Thankfully it's not protected.
Bill
 
The following users thanked this post: Ian.M


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf