When I upload the program to the revision 3 board I get this message
Arduino: 1.8.19 (Windows 7), Board: "Arduino Mega or Mega 2560, ATmega2560 (Mega 2560)"
Sketch uses 3970 bytes (1%) of program storage space. Maximum is 253952 bytes.
Global variables use 242 bytes (2%) of dynamic memory, leaving 7950 bytes for local variables. Maximum is 8192 bytes.
avrdude: verification error, first mismatch at byte 0x076c
0x30 != 0xb0
avrdude: verification error; content mismatch
avrdude: verification error; content mismatch
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
The same program uploads fine to my older Version 2 board.....is there a problem with my new board?
It's a really strange situation, some programs download and verify ok and others don't.
The error occurs at various locations e.g. 0x046c 0x30 != 0xb0 for one failed download another 0x0c6c 0x00 != 0x80
I'm not sure if it's a duff board or version 3 of the board doesn't work properly
No I have an older board and that still works fine so I'm guessing it's not the IDE. It must be a duff board as you can download a program that won't verify but if you add one extra line of code the modified version will verify, add some more and it fails etc etc.
If you upload the identical code several times does it error out always a t the same address? Does is always error with identical code if it threw an error once?
May be a bad bit in one cell that accepts only the 0 value.
Same error same place for same code, different error different place for different codes.
Have returned the board as convinced it's a faulty processor chip.
Ordering new board so will see if that works!
I had constant issues uploading anything to my 2560 clone board. Even reflashed the bootloader (over SPI with another arduino board) and destroyed the board info. Well, nothing worked for me as I was constantly seeing timeouts in the console and no success. So what I did at the end (one step before calling it "DEAD"), was to replace the USB cable with much shorter one with good isolation. And behold - a miracle, the board was flashed without any issues and started reporting prints on the serial. So I hope that could help someone else. I guess the serial chip onboard is total crap as I've used the other cable with so many other boards mostly cloned UNOs and one original - actually that cable came with it (the "problematic" one).