SAM4E Xplained error on verify flash 0x404c61

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

Good day all !

I assumed my error was due to a bad nand flash so I bought a second Xplained.

2nd does the same thing.

 

What is wrong with my universe?

 

Verifying Flash...Failed! address=0x404c61 expected=0x00 actual=0x02

 

Details:

Timestamp: 2017-09-19 17:40:18.251

Severity: ERROR

ComponentId: 20000

StatusCode: 0

 

Verifying Flash...Failed! address=0x404c61 expected=0x00 actual=0x02

 

 

... it's the GMAC demo ... code untouched.

Whaa ?,.

Last Edited: Wed. Sep 20, 2017 - 04:28 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The default is to use the .elf file but ... 

... when I look at the Intel hex file I see a hiccup:

:104C20000000000000000000000000000000000084
:104C30000000000000000000000000000000000074
:104C4000F8B500BFF8BC08BC9E467047912C4000E8
:104C50001D014000F8B500BFF8BC08BC9E46704777
:044C6000F900400017
:084C6400DCF8FF7F01000000F5
:104C6C000100000000093D001000002000000000C1
:104C7C0000000000FC02002064030020CC03002094

... the address error is after the 'F9" of a 4 record line at the end of a segment.

I suspect this partial line is choking some where in code?

How does the load process work on the EDBG chip?

Still trying to open a case with Microchip ... I may need an act of Congress to get thru to them.

I can't create a case because their web site chokes on the device type.

 

 

Whaa ?,.

Last Edited: Wed. Sep 20, 2017 - 07:38 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The hex files loads no problem.

Seems to only be the elf which I assume is the same data in elf format?

 

 

Whaa ?,.

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

Is there anyone in this forum?

Whaa ?,.

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

Well I guess this message is going to no one but me.

 

I did figure out that there are two align errors associated with casts.

Being new to arm I learned yesterday that you can have align issues with pointer casts.

 

When I remove the offending lines I compile, program, and verify ok.

 

Why would Atmel send a GMAC demo example for the SAM4E with such a major bug?

 

Is this why they were absorbed by Microchip?

 

Long story short weird casts can cause align errors such that when you program flash the verify comes back with errors.

 

 

 

 

Whaa ?,.

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

That doesn't make any sense.

 

Alignment errors happen at run time

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

Well it's back.

Different address:

 

Verifying Flash...Failed! address=0x404867 expected=0x7f actual=0x5f

 

Timestamp: 2017-10-01 11:03:04.397

Severity: ERROR

ComponentId: 20000

StatusCode: 0

 

Verifying Flash...Failed! address=0x404867 expected=0x7f actual=0x5f

 

I get absolutely no support from Atmel (now Microchip?).

 

Phoned there Corp HQ because their website wont accept Atmel part numbers but you have to provide a part number to get support.

no one called back after two weeks.

 

What other CPU's could I use?

 

Does Intel make ARM's ?

 

 

 

 

 

Whaa ?,.

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

As I add more code ... the problem is now gone again. 

 

 

It seems certain code combinations cause this issue.

With a specific source code being compiled ... it happens every time.

Change a couple things ... it goes away.

 

Whaa ?,.

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

I recall having this issue before and was able to find the offending code and rework the code to make it verify correctly.  I'm using the SAME70, by the way.  Recently, I've come across this issue again, and found this thread.  I've been able to narrow down the code and find the lines which cause the elf verification issue (some sprintf functions) but I know these worked before so I didn't want to change them.

 

As a test, I tried flashing the same firmware from my other computer (running a different version of Atmel Studio) and found that it programmed and verified without error.  Now that I think about it, I believe I saw the same thing the first time a came across this issue.  That was a year ago, and I can't say which versions of AS were running at that time.  This time around, the working version is 7.0.1188, while the version that produces verification errors is 7.0.1417.