[sgtpepper67]

Hello dankomanu
did you try also with ver 11.11.5?
It seems something did not go right during your procedure or the bin files inside vcds folder got corrupted. I did some time ago your almost same procedure and everything worked fine at the end..But after some attempts. Be always carefull at the automatic updates on the Internet. Let us know your findings. Thx. Cheers

[dankomanu]

Hi sgtpepper67
Thanks for your reply
I also thought that maybe the bin files got corrupted. And yes, I also try with ver 11.11.5 and the same message appears,Failed self test!
I install in a formated computer with windows xp and I don't have internet on it.
Can you share your bin files to check if mines are corrupted?
Thanks a lot.

[sgtpepper67]

To Dankomanu.

Here are the bin files for v.11.11.5 and 12.12.0... hope they are not get corrupted in the meantime!
Try it and let us know but in my opinion you most probably you'll maybe need to repeat the procedure from scratch to fix your "failed" warning. I had something quite similar and after having re-do all the reflash from zero I fixed it. Hope it helps mate. Cheers.

---

To Dankomanu.
bin files v. 12.12.0...

[sgtpepper67]

Hi Dankomanu, did you try the bin files? Any news? Bye

[dankomanu]

Hi sgtpepper67
Yes, I tried your bin files but still remains the same error, failed to self test!
Maybe the FT232RL.ept file or flash_192.hex and vers 6 11.11.5-12.12.0_eeprom 512 rl.hex are not properly to my cable?
Which file do you use to reflash your FTDI232RL chip?
Anyway I'll keep trying to reflash my cable in the next days.
Thanks a lot for your support

[sgtpepper67]

Hi Dankomanu,
after Mattydr67' suggestions and the other mates of the forum as well, I had flashed the atmega162 with firmware v.1.92 + eeprom vers 6 11.11.5-12.12.0_eeprom 512 rl.hex and used fuse/bits as 320 (not 512) by Mr. Fantomel's collection. There is mentioned about 512b words firmware but actually it seems there is only 256b words firmware. So if you did a wrong step and you set the fuse bits for 512b words firmware then your Atmega probably should not have been flashed well and perhaps this may be the reason why it failed. Hope it helps. Cheers.

[dankomanu]

Hi sgtpepper67
That is the only thing that I don't tray, because I don't know.
In PonyProg I don't see anything about the fuse set of 320 or 512b words.
Do you know how to set fuse bits as 320?
Thanks in advance.

[mattydr67]

Its 256b words not 320
Good luck

[sgtpepper67]

Hi sgtpepper67
That is the only thing that I don't tray, because I don't know.
In PonyProg I don't see anything about the fuse set of 320 or 512b words.
Do you know how to set fuse bits as 320?
Thanks in advance.

Hello Dankomanu,
I did it sometime ago so I am not sure 100% but maybe the original configurationsecuritybits (bitsettings) was the attached one otherwise it was the same as yours (the one you have attached in your post).. I did this screenshot at that time. Try it and let's know.

PS: try also with flash_192.hex + eeprom.hex (1kb) instead of "vers 6 11.11.5-12.12.0_eeprom 512 rl.hex" inside 12.12.0 from BM-BL-RL folder.

[dankomanu]

Hi
Thanks mattydr67 and sgtpepper67 for your replies.
Searching on the internet I found this site.
http://www.engbedded.com/fusecalc/
As you can see the size of the boot flash depend on BOOTSZ0 and BOOTSZ1 bits, and you can make 4 choices, 128, 256, 512 or 1024 words, that is why I didn't understand 320 words and of course, because I didn't know anything about Atmega 162 configuration.
Now I know a little more about this.
Thanks a lot and I'll let you know my discoveries.