Verification fails during FW upload on Vertex K8400

Vertex 3D Printer Vertex - Printer software (repetier, slicer, ...)
1

Hi.
I’ve suddenly got a verification failure when trying to upload a new firmware to my Vertex K8400.
Everything have worked flawlessly in the past and I am almost sure that I was using the exact same computer, drivers and software.

I’ve verified that the firmware does get flashed by changing the version string and verified the changed version string on the LCD but the code verification always fails on me!
I tried to upload a very small, almost empty sketch and then the verification passes, but verification always fails again when uploading a larger sketch such as the Vertex Marlin FW.

I’ve been using two different machines during this testing, one Windows 10 64 bit, and one windows 7 64 bit computer.
Programming jumper on the Vertex main board is in place and no mains is connected when flashing. I’ve used different USB cables, hey I even used my 15 cm long super shielded USB cable that always used to be bullet proof.
I’ve also tried to disconnect everything from the Vertex mainboard to secure having enough current for doing a proper flash.

I am curently using Arduino IDE version 1.0.6 and the latest VCP drivers from FTDI version 2.12.06.

Programmer type Tools–>Programmer–>“AVRISP mkII”.
Board type Tools–>Board–>“Arduino Mega 2560 or Mega ADK”

I’ve tried to redefine the default VCP port settings in the device manager as described in various forum posts (setting baud rates, stop bits and increasing timeout etc.), but since nothing helps I rolled back to the default settings again.
I’ve also removed all the drivers completely from the system (even removed all the driver files from disk) uninstalled the Arduino IDE and installed the Arduino IDE and FTDI drivers again.
I’ve done this whole procedure using a number of FTDI driver versions, going back as far as 2011 and on two different computers running Windows 7 and Windows 10 OS:es.

I am slowly starting to suspect that the bootloader on my Vertex main board might be defective…
I am running out of ideas myself, so do you think that re flashing the boot loader is a good idea at this stage, or is there anything more I can try first?

I’ve found a header on the main board that looks just like an ICSP header connection.
Here is a photo on how I am planning to connect the ICSP header.

Can anyone please confirm that this is correct?
I know that I can always measure the connections to check if they are correct myself, but I am a bit lazy by nature and it is always a good idea to have a confirmation from the vendor (Velleman) directly if possible…

Do you recommend any specific 2560 bootloader or is stk500boot_v2_mega2560.hex OK to use?

//Tanks!

2

Are you using the Arduino software version 1.0.6 or lower?
You can find it in this link.
http://arduino.cc/download.php?f=/arduino-1.0.6-windows.exe
For all other operating systems.
https://www.arduino.cc/en/Main/OldSoftwareReleases#previous

3

[quote=“Wrong Way”]Are you using the Arduino software version 1.0.6 or lower?
[/quote]
LOL

Lol, weird question IMHO… The guy seems to know what he’s talking about so pointing him to the DL location of the arduino software seems a bit obsolete don’t you think?

4

Sorry I missed the part about the version he was using.
I was just trying to help.
So Jeafke what do you suggest?

5

Well I’m gonna be deadhonest and have absolutely no clue whatsoever but to make sure its NOT his current setup.
I’d try 1 thing first and that is just get the girlfriend/friend/mom/dad/daughter/son’s computer and try to send the default velleman FW from some complete different computer for once…
So you can completely rule out your current setup.

Obviously you where trying to help, no doubt about that.
But I can imagine it could be frustrating for jacka.
If you ask a really well constructed question and get a response like this:

Q helpdesk: “Check this: Are sure you turned on your computer Mr.?”
A: “Fuck Hell Yeah!!!”
Q helpdesk: “Next thing to check: Is your computer plugged into the mains Mr.?”
A: “Oh shit thanks that’s it”

Hopefully someone @Velleman can help this fella.

Kind regards
JeAfKe

6

Jacka,

I reread your post and see that you tried 2 different computers.

Anyways I have read that sometimes if you download the firmware with Internet Explorer it does not download correct.
Have you tried FireFox or a different web browser?

This is just a guess after that I’m out of ideas.

7

If that would be the case the zip file would get corrupt and wouldn’t be possible to extract without errors in the first place.

Kind Regards
JeAfKe

8

Not true
Read some of the post.

9

Oh okay,

Very odd IMHO but I guess it could be possible if IE decompresses it by itself or something but still very strange…
What if U tried to upload an older FW version? It still messes up?
And what log message does it return? It should give some clue in the bottom Text Console.

And what if U disabled verification in preferences?

(I haven’t tested this myself but sounds like a possible solution??? I googled a screen-shot of what setting I mean.)

Preferences_3.png649×602

Kind regards.
JeAfKe

10

First of all, tanks a lot for your effort trying to help me out guys, I really appreciate it!
It is fully understandable to miss out on some of the details when digging through such a tangled mass of text, trust me I take no offence at all. I am just happy that someone takes their time trying to help me out.

Unfortunately, there is nothing wrong with the code base. I’ve successfully uploaded it to one of my regular arduino mega 2560 boards, wich is using a different driver than the Vertex Board.
I’ve also already tried to upload an older already proved FW to my Vertex main board as you suggested JeAfKe, but that still fails.

The printer actually seems to work OK after flashing a new firmware to it even when the verification fails, but with a potentially shitty bug inside that you never know the side effects of before it hits the fan.
Unfortunately, we would gain nothing by disabling the verification. It would be just like burying one’s head in the sand and pretending that the problem does not exist. We can do that just as well by ignoring the failed verification in the first place.

I just wish that identifying the ICSP header on the mainboard would be more obvious with an explicit ICSP text printed next to it.
I would really appreciate if someone @Velleman could confirm the ICSP header connection and what bootloader I shall use.
It will take some additional time and effort to confirm the ICSP connection myself for sure. But hey, I will go ahead anyways.

The darkest hour is just before dawn.
Thanks again guys!

Best regards.
Jacka

11

The ICSP header is a standard ICSP header that`s on a AVRISP mkII
U could see a 1 next to header to indicate pin 1

12

OK thanks VEL337. My picture in the first post was correct then, thanks again!
I’ll guess that any standard bootloader for 2560 such as the stk500boot_v2_mega2560.hex bootloader will do.
I’ll give it a go and hope for the best…

Thanks again for all your help guys, I’ll keep you updated.

Best regards.
Jacka

13

I think I found something in this thread.
http://forum.velleman.eu/viewtopic.php?f=60&t=13916&hilit=arduino+verification

14

Well, thanks again Wrong Way. Sorry to say but I’ve already tried that and it does not help me I am afraid.

Flashing a new bootloader did not improve anything, still same issues as before…
I am affraid my frustration is really starting to show its ugly face.
I have no trouble at all with my other Arduino Mega boards who are using an Atmega8U2 programmed as a USB-to-serial converter instead of the FTDI chip.
So I really smell a rat regarding the FTDI drivers.
Sure this bugs the hell out of me and the printer and I still have some unfinished business.
But I have decided to let things rest and put this aside for a while.
I’ve flashed a new firmware to my K8400 directly with my avrisp mk2 via the ICSP header so the printer is working just fine.
I can not get this damn bootloader thing to work together with the FTDI chip and drivers thats all.

Thanks again for all your help guys, I really appreciate it!

Cheers,
Jacka

15

Perhaps the Velleman crew can jump in and offer assistance in the form of warrantee for a broken board? I’m going to update mine this week, i’ll use the same drivers/version that you are using and report back.

16

Thanks to3dornottobe, that would be wonderful!

Cheers,
Jacka

17

I had the same problem, could not upload the firmware.
i had always a verification error on different locations.
i tested with w7 32b, w8.1 64b
Problem seems to be the FTDI drivers, but i am not sure.
if i want to remove these drivers, windows will not do that [w7 32b and w8.1 64b]
so i used avrisp mk2 to set new FW in the K8400.
now i copy the files to print on sdcard.
if i use repetier software to print, my computer will not shut down afterwards.
that is only if i used the FTDI software.
but printing is ok if i use repetier.

and for sure i used all software versions as discribed.

regards m