[ERROR] Verification at address 0x80000000 failed. Expected: 0xFE. Actual: 0xFE.

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Gotta love that ATPROGRAM!  Just put the new one in... look what it does!

 

[ERROR] Verification at address 0x80000000 failed. Expected: 0xFE. Actual: 0xFE.

 

How do they get away with this?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK, full reboot... that problem went away.  Now I get the following:

 

[ERROR] Verification at address 0x80800000 failed. Expected: 0x00. Actual: 0xA5.

 

This is in the User Page... the file I'm verfing against is a HEX... there's no UP programming in it.  When I try to spec a size to prevent this, I get "can't set size on multiple spaces" or something.... this thing is broke!  And obviously it's been broke since 2015.

 

I've had other open issues with atprogram... been given crappy work-arounds, like reset the programmer etc.  Using an AVRDragon... is this thing the problem?  C'mon Microchip, get this fixed!

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Should probably add that this is the 'verify' cmd... the --verify switch works fine on the 'program' command, but I need a working 'verify' command to check that the secure bit is set.  Why does 'verify' assume that I'm verfing both the flash and User Page?  Even when verfing against a hex file?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK, so evidently you *can* have UP progged in the hex file... the section is right there, address 0x80800000... all zeros.  And I'm using the 'erase' with '-up'... claims 'Erase user page completed successfully'... so it should be FF's, not 0xA5.

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So when you declare a variable, it is automatically dimensioned as zeros... and this is what was biting me before.  I changed the declaration to a pointer to uFlash:

 

//__attribute__((__section__(".userpage")))
//static calStructType calFlash = {0xFF};// can't do this

 

 

pCalStructType pFlashCal = (void *) 0x80800000;// can do this

 

This fixes that part... still having a devil of a time with atbackend and Dragon.

 

Now it's:

 

[ERROR] Verification at address 0x80002008 failed. Expected: 0xD4. Actual: 0xD4.

 

I'm running two processes at once... have two UC3 chips to program on the target board... man, I'm hatin' life right now!  Seems to run fine when run alone.

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

How about this stuff?

 

Serial number 00A200066927 for avrdragon is not connected, but it matches 00A200066927

 

Why is it not connected?  Why does it match itself?  The wire is plugged in... both LED's are on... should I throw the Dragons in the trash?

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Now I get a *blue screen*... if I try to run two bat files, programming two UC3 processors simultaneously, it frickin' *blue screens*... 'to prevent damage to your computer'... who deals with this crap?  I filed a bug on atprogram a long time ago... looks like this is the results I get.