View previous topic :: View next topic |
Author |
Message |
Madf
Joined: 13 Nov 2011 Posts: 179 Location: Moscow
|
Posted: Wed Jul 12, 2017 9:30 pm Post subject: XMEGA-A1 Xplained verification hex |
|
|
Hello.
There are problems with the work of XMEGA-A1 Xplained.
I use the type "xm128a1def.dat".
When I try to fill the firmware with a PDI program, I get an error:
Code: | Verifying Flash...Failed! address=0x0400 expected=0x8d actual=0xff
Verifying Flash...Failed! address=0x0400 expected=0x11 actual=0xff
Verifying Flash...Failed! address=0x0400 expected=0x11 actual=0xff
Verifying Flash...Failed! address=0x0400 expected=0x11 actual=0xff
Verifying Flash...Failed! address=0x0400 expected=0x96 actual=0xff |
Does not pass verification code/firmware.
The program itself seems to be working.
If you take the demo "xmega-a1_xplained-demo.hex" and flash it, then the test passes - ok (including verification)!
I use AVR Studuo 6 + AVRISP MKii for firmware. This set always worked without problems with any types of AVR.
It seems that BASCOM incorrectly creates addressing in the HEX file.
Can not understand why the verification of the HEX file from BASCOM fails?
(BASCOM-AVR version : 2.0.7.9 , Latest : 2.0.7.8 ) |
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5921 Location: Holland
|
Posted: Wed Jul 12, 2017 9:48 pm Post subject: |
|
|
i can not understand why they list the same address 5 times but expects a different value ?
maybe you need to update studio?
if studio does not like the hex you should get some info. so i wonder how studio can determine there is a problem after the programming?
try to erase the chip, and then check if it is blank. then program the chip.
because they check the content with the chip, i conclude that this can not be a bascom problem. contact atmel. _________________ Mark |
|
Back to top |
|
|
Madf
Joined: 13 Nov 2011 Posts: 179 Location: Moscow
|
Posted: Wed Jul 12, 2017 10:00 pm Post subject: |
|
|
All modes work correctly (erase, fuse bits, signature).
When I flashing "xmega-a1_xplained-demo.hex" a large file size, then there is no problem. All is well.
When I flashing the HEX file creating BASCOM, I get an error on the verification.
Above I showed the types of errors, it's not many errors at once, but only one line and process stopid. |
|
Back to top |
|
|
Madf
Joined: 13 Nov 2011 Posts: 179 Location: Moscow
|
Posted: Wed Jul 12, 2017 10:10 pm Post subject: |
|
|
I'll try to update / install Atmel Studio, I'll write the result later. |
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5921 Location: Holland
|
Posted: Wed Jul 12, 2017 10:11 pm Post subject: |
|
|
if you think a bit logical, you can determine that it is not a bascom problem :
- first you program chip using the hex file right? so studio read and program these bytes
- then it checks the flash content with the hex. so it again reads the hex and compares with the flash memory
why would this be a problem of the hex file as you suggest?
it does not make sense. and that some other hex file works, what does that mean? totally nothing. _________________ Mark |
|
Back to top |
|
|
Madf
Joined: 13 Nov 2011 Posts: 179 Location: Moscow
|
Posted: Wed Jul 12, 2017 11:09 pm Post subject: |
|
|
Installed Atmel Studio 7, it updated the firmware of the programmer to version 1.18 - the problem disappeared, the code began to work correctly.
Thanks for the help.
ps: I think the topic will be useful to those who use XMEGA-A1 Xplained. The problem with the no flashing XMEGA solved simply, removed the chip from the scheme USB. |
|
Back to top |
|
|
albertsm
Joined: 09 Apr 2004 Posts: 5921 Location: Holland
|
Posted: Wed Jul 12, 2017 11:14 pm Post subject: |
|
|
of course i knew that. it is all logic.
I use bascom to program all chips without problem. _________________ Mark |
|
Back to top |
|
|
|