Re: Firmware upgrade failure on WorkCentre 6515DN

GuyAdams · ‎11-10-2022

Thanks to a little help from DrStrange I have finally managed to update two of our WorkCentres.

The file we were downloading at our offices on a leased 1GB/1GB line, always prematurely finished downloading at around 259MB. As per DrStranges advice, I downloaded over 4G on my phone and copied to a computer, that download is 399MB

The correct downloaded zip file has an MD5 of 27E5557DD4EAA61D6AB23DB8D591AC86

The correct bin file has an MD5 of 00F90B398A742A2BF4C3407D10B52737

The firmware update utility states the file is from 2022/09/07 (yyyy/mm/dd).

I have also downloaded the firmware from DrStranges Dropbox link and the MD5s match the above.

I would suggest that there is an issue with the server(s) serving the firmware file.

Many thanks,

Guy

DrStrange · ‎11-07-2022

Hi @techted. I tried to post a reply to you but a moderator rejected it as s_p_a_*?mb possibly automatically due to a trigger word. I have been told that my post has now been approved and put back in this topic but I don't see it and it seems that other posts in the topic including my own OP in September have also been removed so I don't want to risk reposting in case it gets removed again. I have replied to you via PM.

Edit:

Techted tells me via PM that when he downloads the 65.69.51 FW his compressed file download is 259MB whereas when I download it just now, it is 399MB. So I have put it up on my dropbox account if anybody wants to try it. Obviously I am an untrustworthy source so scan for virii and use at your own risk. This not the file I downloaded on 3rd November which I seem to recall having a date of 3rd November in the FW upgrade utility. Unfortunately, I deleted that file.The file date in the dropbox link as reported in the FW upgrade utility is 7th September. My printer is 6515DN, my OS is windows 10 x64. I will be deleting the link tomorrow.

Link:

https://www.dropbox.com/s/62859p9rzxkvzbn/656951_WC6515_E.zip?dl=0

DrStrange · ‎11-07-2022

@techted:

Yes, I did update successfully over WiFi. And if I had reread the Versalink Firmware Installation v7.pdf instructions again I would have updated instead over ethernet/USB as instructed and that I tried to do in my original post.

Can I correct your post in the Hardware sub-forum: it was not I who downgraded to the bridging firmware, it appears to have been SadAdmin who did this.

Apologies for posting in the wrong sub-forum. If I had posted in the Hardware sub-forum, you surely would have seen the topic and not started another topic.

I downloaded the 65.69.51 firmware again to check the date given in the Versalink Firmware Utility, both from the link given in Xerox's website support page and from CathyO-Xerox's link. Both seem to point to the same link, although hers is for Windows 11 and I downloaded from the Xerox's support page for Windows 10, which is what I use. It would give more confidence that one is getting the revised firmware if Xerox were to change the release date of the firmware on the support page from 22/09/15 to the release date of the revised firmware. File sizes for each file I downloaded are the same: 407,716 KB. The firmware upgrade utility says the date for each firmware .bin file is 2022/9/7 06:00:24. In windows the date modified is 2022/09/07 7:00, size on disk 417,501,184 bytes. I seem to remember when I was upgrading to 65.69.51 on 2022/11/3 that the date in the firmware upgrade utility was different and that it was 2022/11/3 although I cannot confirm that unfortunately as I did not keep the .bin fiirmware file.

I assume that you are running the Firmware Upgrade Utility in the Administrator account?

Perhaps someone here who successfully upgraded to 65.69.51 and kept the .bin file could send it to you?

I am based in the UK so all dates are written as YYYY/M(M)/D(D).

I didn't keep the Software Upgrade Report but in the EWS these are what I have for the 65.69.51 file versions:

System v65.69.51

Controller ROM v1.84.2

IOT ROM v1.30

IOT2 ROM v4.11.0

ADF ROM v42.0.0

FaxROM v104.8.0

Panel ROM v91.6.11

Boot ROM v11.1.222

SJFI v4.7.0

SSMI v2.5.2

RSEP v1.8.25

If you suspect a problem there, might it more helpful to you if you asked somebody still on the 65.59.11 bridge version to confirm your version numbers are correct?

techted · ‎11-07-2022

@DrStrange wrote:
I successfully upgraded my 6515DN to 65.69.51 (from 65.66.91) using the Versalink Firmware Upgrade Utility over wifi. When the transfer progress indicator in the utility reached 100%, it stated that the firmware had been stored successfully. The printer then turned off. I turned it back on and the printer displayed a progress indicator. When it reached 100% it turned itself off then back on several times. When the control panel eventually came back up, it printed a software upgrade report stating the software had been successfully upgraded to 65.69.51.

Can I confirm that you used a WiFi connection to update the firmware? Sounds dangerous not using a hard connection (ethernet or USB).

I posted a similar thread not realising your thread existed. Unfortunately, am still unable to sucessfully update my firmware even with the 'fixed' firmware. I tried doing it via WiFi like you did in case that made a difference. It unfortunately did not.

https://forum.support.xerox.com/t5/Hardware/Firmware-upgrade-failed-for-Xerox-WorkCentre-6515/td-p/2...

When your printer completed its firmware update, it printed out a Software Upgrade Report. Can I compare the version numbers you got? Am wondering if the problem lies there. These are mine:

Software version

System v65.59.11

Controller ROM v1.69.1

IOT ROM v1.3.0

IOT2 ROM v4.11.0

ADF ROM v42.0.0

Fax ROM v104.8.0

Panel ROM v91.6.11

Boot ROM v11.0.219

SJFI v4.7.0

SSMI v2.5.2

RSEP v1.8.25

techted · ‎11-07-2022

@GuyAdams wrote:
Many thanks for the link. I have downloaded it, the firmware update utility states the firmware file was written on the 3rd of November, so its definiately the revised firmware.

Hi, where in the firmware update utility can you see it stated that the firmware was written on 03 Nov 2022? What I see in the utility says the bin file date is 2022/08/31.

I downloaded the bin file from the new link:

https://www.support.xerox.com/en-us/product/workcentre-6515/content/156307?language=en&platform=win1...

SadAdmin · ‎11-03-2022

Hi GuyAdams,

Not sure of your upgrade path, but have you tried downgrading to the unencrypted bridge version of the Firmware Ver.65.59.11, then upgrade to the newly released version of Firmware Ver.65.69.51?

That was my upgrade path.

SadAdmin · ‎11-03-2022

Thank you DrStrange for starting this thread for me to hop on. I too have exactly the same success as DrStrange describes and also the lack of option to update software via the printers built in webserver.

Also thank you CathyO-Xerox and TammyL-Xerox from Team Xerox!

DrStrange · ‎11-03-2022

I successfully upgraded my 6515DN to 65.69.51 (from 65.66.91) using the Versalink Firmware Upgrade Utility over wifi. When the transfer progress indicator in the utility reached 100%, it stated that the firmware had been stored successfully. The printer then turned off. I turned it back on and the printer displayed a progress indicator. When it reached 100% it turned itself off then back on several times. When the control panel eventually came back up, it printed a software upgrade report stating the software had been successfully upgraded to 65.69.51.

Although, as mentioned in my OP, I still don't have the setting that should be in the EWS>Admin>System>Software Update page to upgrade by selecting a firmware .bin file.

Thanks for fixing this firmware.

GuyAdams · ‎11-03-2022

@CathyO-Xerox wrote:
Hello,
We have been informed that they have fixed the firmware. If some of you can try it and and let us know if it works, that would be great:
https://www.support.xerox.com/en-us/product/workcentre-6515/content/156307?language=en&platform=win1...

Many thanks for the link. I have downloaded it, the firmware update utility states the firmware file was written on the 3rd of November, so its definiately the revised firmware.

Unfortunately, we are still getting the same problem.

We have tested on two machines (currently 65.68.31), Windows 11 x64 laptop, no antivirus or firewall present.

Regards,

Guy