Home
JAQForum Ver 20.06
Log In or Join  
Active Topics
Local Time 23:04 06 May 2024 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : verifying contents using pickit3

Author Message
kkoppert
Newbie

Joined: 12/04/2017
Location: New Zealand
Posts: 17
Posted: 07:45pm 05 May 2017
Copy link to clipboard 
Print this post

I keep burning the hexfile for MMBASIC 5.03.02 into a pic32mx170256B using a pickit3 and mpipe. I turn verify on and power the device from the tool. The result is

The following memory areas(s) will be verified:
program memory: start address = 0x0, end address = 0x3ffff
boot config memory
configuration memory

program memory
Address: 1d000400 Expected Value: ffffffff Received Value: ffff0000
Verify failed
2017-05-06 17:32:24 +1200 - Verify failed

Is this expected?
 
TassyJim

Guru

Joined: 07/08/2011
Location: Australia
Posts: 5914
Posted: 07:48pm 05 May 2017
Copy link to clipboard 
Print this post

It happens with some configurations and is nothing to worry about.
VK7JH
MMedit   MMBasic Help
 
WhiteWizzard
Guru

Joined: 05/04/2013
Location: United Kingdom
Posts: 2794
Posted: 08:08pm 05 May 2017
Copy link to clipboard 
Print this post

This is correct - and the MicroMite will work correctly

My understanding is that things happen inside a MicroMite after the very first power-up after flashing. This effectively changes 'memory/flash contents' and therefore, the verification will fail as 'things are different'.

If you were to save the contents of the MicroMite as a hex file (i.e. after it has done its initial 'memory/flash' alteration) then load & verify this file then it will pass

WW

For everything Micromite visit micromite.org

Direct Email: whitewizzard@micromite.o
 
bigmik

Guru

Joined: 20/06/2011
Location: Australia
Posts: 2870
Posted: 08:10pm 05 May 2017
Copy link to clipboard 
Print this post

Hi Kk,

This is because when the PIC programming is finished RESEST is released and on first power up MMBasic changes a few memory locations (I am not sure what but it causes a verify fail)

To do a verify...

Click on settings
Select RELEASE from Reset
Select HOLD in RESET

Then program your chip, it should verify OK.

Even though the default is hold in reset it actually requires selecting release first then selecting hold again.

Kind Regards,

Mick
Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<<
 
Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1664
Posted: 01:46am 07 May 2017
Copy link to clipboard 
Print this post

  bigmik said  To do a verify...

Click on settings
Select RELEASE from Reset
Select HOLD in RESET

Then program your chip, it should verify OK.

Even though the default is hold in reset it actually requires selecting release first then selecting hold again.


That info is really worth adding to numerous places of reference.

Had me bluffed in the early days as to why the error.
New ATT, Never used a Pickit3, or PIC's at all, so was a bit miffed by the error, but worked on when they proved themselves to be correctly programed.
 
Print this page


To reply to this topic, you need to log in.

© JAQ Software 2024