I have v3.3 new board (serialNr=...) with some problems:
Stuck in bootloader.
(no communication with MegaTune and no LCD characters, just 2 lines of squares).
In BrayTerm i have <0> and the board don't respond to any command.
- Common mistake is forgetting to capitalize Man, wrong com serial port selected or some other program open that is using that serial port (MegaTune, AVR studio4 etc.)
After that i try to update the firmware .i update with psituner and afterthat with perl (perl bin/prog.pl vems.hex :COMn Etwf) 3 diferent files of vems.hex and NOTHING. WHat is my Problem Now? The boot need to be updated?(it is posible to lose some information when i connect and disconnect rapidly the board Please help
- I am definatly lower on the I.Q. rating than most people here and I have had my share of problems that I cant figure out so in my experience, if you give a very detailed list of the steps you are taking, ie.
- opened terminal program, set baud rate to 9600
- typed Man
- typed Manmcbffmcb, changed to 19200baud etc etc
- also, if you havent found it yet, see [this page] for help with uploading firware. I am not computer smart and I easily figured it out with the help of that page.
- I update 1.0.18 firmware and nothing ;the board respond only in boot mode
- you might need to edit the .bat file and remove the "t" option (from Etw or Et) if already (stuck) in bootloader (an earlier unsuccessful upgrade attempt?)
- I recommend complete package with more recent firmware, see bat files for megaloader syntax, you need to remove "t" from the syntax, as you already have it in bootloader in advance. http://media.vems.se/code/VemsMT1.0.36.zip for example
After i upload 1.0.36 file vems.hex with perl command(perl bin/prog.pl vems.hex w) in command window i have:
total serious errors during write: 0
VERIFYING...
error at page 0
255,128,0,0
137,239,205,79error at page256
0,0,0,128
0.63.52.141verified<0 101632>
total serious errors at verify: 2
FAILURE we say E
- What is the length of the vems.hex file? Isn't it empty or something because of some unzip or filesystem-permissions error ?
- Maybe you can open in wordpad or other text editor and copypaste the first line to here ?
I edit the .bat file (that becomes: )
- Copypaste the effective line from the .bat here - the command and arguments actually used, wether perl prog.pl or megaloader
Problem at verifying :
Verify flash
Error at page: 0
Error at page: 0
too many errors, bailig out
- NOW it is possible that my atmega128 be burned?
- not likely (read below), unless you tried to apply something directly to the AVR like the standard ALS switch
- but if burnt, programming via ISP is not sure to help (and involves more risk than via bootloader)
- maybe prog.pl or required "serialport.pm" API is broken ? (unlikely, it should give different error message)
- is it possible that bootloader is trashed ? (this can be fixed with 5-wire ISP from parallel port)
- yes, this is theoretically possible. While the commands we (prog.pl and megaloader) use have strong checksum, the old atmel-bootloader compatible commands are still supported and those allow trashing the flash (possibly a page in the bootloader area) with very bad luck (still unlikely, but...).
'''A: I think its more reasonable that you have a bad serialport/cable, USB adapter? //Emil Larsson
Read all document befor you tke a conclusion; i write the flash with rs232;in terminal the board respond to any command but ONLY IN BOOT MODE (and in boot mode i can enter only by loopback the board serial plug)
A bad serial adapter/cable (or broken ground in the cable) often seem to work for a few characters, but than fails in the middle of a bigger block.
Enter BOOT mode in 19200,8n1 and get answer for the following commands (all verified OK):
- S => AVREFI1
- p => S
- v => 20
- V => 20
- Than you are very likely to be able to reflash.
- i can reflash but on verifying i get error.
- Try a separate verify operation, just make sure the firmware (vems.hex or whatever you named it) is the same when you verify (that you uploaded). Verify is similar as writing, but without "w" in the command-argument
- if you tried prog.pl, try megaloader (or try prog.pl if you tried megaloader; you can even upload with one and verify with the other)
- I'm thinking of a way to read/verify your bootloader and get verbose results.
- avrdude (or uisp is another program for this) and a simple (solder in 10 minutes, or less if starting from an old PC RS232 header to connector grey flat-cable) 5-wire ISP cable is just the only simple solution I can think of at the moment. See MembersPage/MattiasSandgren/NickesBMW/AvrBootCode