41CL Self-Update

[Monte Dalrymple]

(10-25-2017 02:02 AM)BobVA Wrote:  Thanks Sylvain!

The CDBVER? function reported [edit] 10/01/2014 - thanks Bob! [/edit], which was a little confusing since I ran it yesterday. Just to be sure I'm rerunning FLCHK? now. Will update this to let you know what happens.

UPDATE:

Worked much better, successfully plowing though over a hundred updates and reporting "UPDATE DONE" on the 41.

However when I get to the last CDBEXP I get:

Code:

00:55:26 Received   CORR_FLDB_2MB_EXPORT_REQUEST(0x4B)
00:55:26 Sent       CORR_FLDB_2MB_EXPORT_RESPONSE(0x4C)
00:55:26 Receiving  2184 2184 2184 1640 = 8192 bytes received
00:55:45 File       CFLDB_V2.ROM saved
00:55:45 Report     Outdated ROM images [boardGeneration: FIRST]
00:55:45 Report     XFNS3-3B.ROM    [Page:0x003 ID:XFN3 Rev:2014-11-24 YCRC:0xA270BAF7]
00:55:45 Report     YFNZ-4F.ROM     [Page:0x007 ID:YFNZ Rev:2017-06-19 YCRC:0x3650EF10]
00:55:45 Report     Summary: 2 outdated of 256 ROM images

And I'm not sure if that's a problem or not? I tried re-running entire procedure after restarting the 41 to a "MEMORY LOST" state (but skipping the FLCHK?). FLUPD finished in just a second with no messages on the PC side and with the same result from CDBEXP.

Thanks again for the help!

Bob

By default FLUPD does NOT update the OS sector of Flash memory (pages 0x000 -
0x007). The report is saying that two pages in the OS sector are out-of-date.
Your CL will function just fine with the older software, but if you want to update
the OS sector you must explicitly enable that functionality. This is all explained
in the manual. I did it this way because updating the OS sector is dangerous,
and if something goes wrong only I can fix it. So READ THE MANUAL before
attempting it, and be aware that erasing the OS sector takes eight times as long
as regular sectors. So the CL will sit there, saying "ERS 000" for longer than you
might expect. Just leave it alone and let it do its thing!