Threaded Mode | Linear Mode

Uli · 07-20-2022, 06:24 AM

Dear users,

I tried to update my HP41CL that I bought in 2020. I used clupdate 1.1.0 on my Windows PC. And I used rom_files_220629.zip.

After starting with "*" and FLCHK? everything seemed fine. The HP41CL makes a beep every ~4 seconds and the PC shows "KEEP ALIVE" and more and more ")".

This process takes a long time and I got tired and went to bed. After about 4 hours I found that the process was finished. The HP41CL had switched off. It works, but I suspect that the update was not completed. CAT 2, for example, shows YFNZ 4F.

Am I doing something wrong?

Greetings
Uli

MeindertKuipers · 07-20-2022, 07:03 AM

You did everything right, almost. The update process must be finished with the FLUPD command (see example 1 in the CL_UPDATE manual), this is the actual update where the updated ROM images are re-programmed in FLASH.

Uli · 07-20-2022, 07:23 AM

(07-20-2022 07:03 AM)MeindertKuipers Wrote: You did everything right, almost. The update process must be finished with the FLUPD command (see example 1 in the CL_UPDATE manual), this is the actual update where the updated ROM images are re-programmed in FLASH.

So I have to watch the HP41CL all the time and make sure it doesn't switch off so that I can type FLUPD at the right moment?

MeindertKuipers · 07-20-2022, 08:22 AM

(07-20-2022 07:23 AM)Uli Wrote:
(07-20-2022 07:03 AM)MeindertKuipers Wrote: You did everything right, almost. The update process must be finished with the FLUPD command (see example 1 in the CL_UPDATE manual), this is the actual update where the updated ROM images are re-programmed in FLASH.

So I have to watch the HP41CL all the time and make sure it doesn't switch off so that I can type FLUPD at the right moment?

Usually I switch off audio (CF 26) and XEQ "ON" so the HP41 does not switch off and is silent during the process. The update program on the host computer will give you an approximate time for the FLCHK? to complete, so you can time your nap. It also gives this timing estimate for the FLUPD process.

Uli · 07-20-2022, 11:12 AM

(07-20-2022 08:22 AM)MeindertKuipers Wrote:
(07-20-2022 07:23 AM)Uli Wrote: So I have to watch the HP41CL all the time and make sure it doesn't switch off so that I can type FLUPD at the right moment?

Usually I switch off audio (CF 26) and XEQ "ON" so the HP41 does not switch off and is silent during the process. The update program on the host computer will give you an approximate time for the FLCHK? to complete, so you can time your nap. It also gives this timing estimate for the FLUPD process.

Thanks a lot for the very helpful tipps. Now I do know , what I have to do.

Greetings
Uli

Sylvain Cote · (This post was last modified: 07-20-2022 11:43 AM by Sylvain Cote.)

Hello Uli,
I would suggest that you look at the examples (p.43 to p51) of the 41CL Update Functions Manual.
Example #2 (p.44) show how to shorten the outdated ROMs scan time from minutes/hours to seconds/minutes. (CPONLY before FLCHK?)
Example #3 (p.45) show how to update the OS sector. (OSUPDT & OSPROT)
However the actual Flash update will takes minutes/hours to do.
As suggested by Meindert, it is a good idea to deactivate the sleep mode on your computer and on your 41CL (ON).
Sylvain

Edit: FLCHK? only scan for outdated ROMs, it is FLUPD who do the actual update.

Code:

FLCHK? → Check Flash Memory Against Flash Database

FLUPD  → Update Flash Memory

The update process is clearly explained in the 41CL Update Functions Manual.

Uli · 07-20-2022, 01:44 PM

(07-20-2022 11:36 AM)Sylvain Cote Wrote: Hello Uli,
I would suggest that you look at the examples (p.43 to p51) of the 41CL Update Functions Manual.
Example #2 (p.44) show how to shorten the outdated ROMs scan time from minutes/hours to seconds/minutes. (CPONLY before FLCHK?)
Example #3 (p.45) show how to update the OS sector. (OSUPDT & OSPROT)
However the actual Flash update will takes minutes/hours to do.
As suggested by Meindert, it is a good idea to deactivate the sleep mode on your computer and on your 41CL (ON).
Sylvain

Edit: FLCHK? only scan for outdated ROMs, it is FLUPD who do the actual update.

Code:

FLCHK? → Check Flash Memory Against Flash Database FLUPD → Update Flash Memory
The update process is clearly explained in the 41CL Update Functions Manual.

Hi Sylvain,
I have read the mentioned examples in the update manual. From my point of view these are very good for people who are more specialists as me. But the steps I have to do on the pc are not mentioned in the examples.
I use your presentation from HHC2017 together with the document "clupdate-1.1.0-readme.txt" that comes with the clupdate software. With these documents I can see, what I have to do on the HP41CL and on the pc.

Yes, now I understand that FLCHK? makes only a scan. My HP41CL is still as before.

Greetings
Uli

Sylvain Cote · 07-20-2022, 06:08 PM

Hello Uli,
I am at work right now (UTC-4h), I will post a step-by-step procedure here tonight (my time).
Regards,
Sylvain

Sylvain Cote · (This post was last modified: 07-26-2022 02:33 PM by Sylvain Cote.)

Physical setup

plug serial cable in your 41CL
plug serial cable to your computer

Calculator should always be off when you plug/unplug the serial cable to/from the calculator.
You should also insert fresh batteries before doing a Flash update.

Note: it is important to physically connect your 41CL to your computer before doing the MMU configuration.
The reason is that sometime the MMU is deactivated when you plug or unplug the serial cable.
When that happen you just need to reactivate the MMU by executing the MMUEN command.

Configuring 41CL

Code:

Command       Description

------------  ---------------------------------------------------

Code:

MMUDIS        Disable memory management unit

MMUCLR        Clear MMU configuration

"YFNX"        41CL Extreme Functions ROM image identifier

PLUG1L        Map YFNS ROM image to page 8 (port 1 low page)

"YUPS"        41CL Update Functions ROM image identifier

PLUG1U        Map YUPS ROM image to page 9 (port 1 high page)

Code:

TURBO50       Activate 50x speed up    (optional)

SERINI        Initialise serial port   (optional)

BAUD48        Set port to 4800 bauds   (optional)

ON            Deactivate sleep mode    (optional)

CF 26         Deactivate sound         (optional)

MMUEN         Activate MMU configuration

CAT 2 should show the following

Code:

-TIME 3B

-CL TIME

-YFNX 4C

-SYS FNS

-SER FNS

-MISC FNS

UPDATE 4D

-EXT FCN 3B

-CL EXT FNC

Note: you may see different version for some ROMs but that is ok.

On the 41CL

Code:

Command       Description

------------  ---------------------------------------------------

FDBVER?       Get current FLDB version of your 41CL

The output is the FLDB date currently installed in your 41CL. Date format respect MDY/DMY mode.
Mine is 06/05/2022 for June 5th, 2022, yours will be somewhere in 2020.

Software & files needed before going further:

Java 1.8+ must be installed on your computer (I use Temurin OpenJDK 17)
clupdate 1.1.0 must be downloaded and unzippped (available here)
latest rom_files must be downloaded (available here)

From the command line:

Code:

cd folder-where-clupdate-and-rom_files-are-located

java -jar clupdate-1.1.0.jar --update rom_files_220629.zip COMx 4800

You should see something like this on your computer: (I use a Mac so my serial port name is different than the ones on Windows)

Code:

hh:mm:ss --update   [fileName: rom_files_220629.zip] [portName: /dev/tty.usbserial-AQ01D0DE] [baudRate: 4800]

hh:mm:ss File       rom_files_220629.zip loading ... done

hh:mm:ss Serial     /dev/tty.usbserial-AQ01D0DE opened at 4800 baud.

hh:mm:ss Waiting    for 41CL commands ...

On the 41CL

Code:

Command       Description

------------  ---------------------------------------------------

CMOPEN        Open serial port

You should see something like this on your computer:

Code:

HH:MM:SS Received   OPEN_CHANNEL_REQUEST(0x41)

HH:MM:SS Sent       OPEN_CHANNEL_RESPONSE(0x42)

On the 41CL

Code:

Command       Description

------------  ---------------------------------------------------

CPONLY        Enable compare mode.

"*"           All Flash memory will be scanned

FLCHK?        Scan Flash ranged specified in ALPHA

On your computer, you should see the new FLDB ROM image being downloaded to your 41CL

Code:

HH:MM:SS Received   FLDB_8MB_IMPORT_REQUEST(0x47) [Page: 0x0DE] [BoardGeneration: third] [EstimatedFullScan: 02h 51m 18s]

HH:MM:SS File       [FileName: FLDB.ROM] [YCRC:0x06292022] [Rev: 2022-06-30]

HH:MM:SS Sending    8192 = 8192 bytes sent

Then, several lines of:

Code:

HH:MM:SS Received   KEEP_ALIVE(0x59))))))))))))))))))))))))))))))))

...

HH:MM:SS Received   KEEP_ALIVE(0x59))))))))))))))))))))))))))))))))

Then, the updated FLDB (called CFLDB) is being uploaded to your computer:

Code:

HH:MM:SS Received   CORR_FLDB_8MB_EXPORT_REQUEST(0x4F)

HH:MM:SS Sent       CORR_FLDB_8MB_EXPORT_RESPONSE(0x50)

HH:MM:SS Receiving  2183 2186 2186 1637 = 8192 bytes received

HH:MM:SS File       CFLDB.ROM saved

Finally, the diff report between your 41CL FLDB and the new FLDB (CFLDB):

Code:

HH:MM:SS Report     Outdated ROM images [BoardGeneration: third]

HH:MM:SS Report     EVAL_3K.ROM     [Page:0x0B7 ID:FRML Rev:2022-06-29 YCRC:0xFEA85C11]

HH:MM:SS Report     EVAL_APP.ROM    [Page:0x0B8 ID:FRMX Rev:2022-06-29 YCRC:0x91C0F69E]

HH:MM:SS Report     FLDB.ROM        [Page:0x0DE ID:FLDB Rev:2022-06-29 YCRC:0x06292022]

HH:MM:SS Report     IMDB.ROM        [Page:0x0DF ID:IMDB Rev:2022-06-23 YCRC:0x16F7EB60]

HH:MM:SS Report     XMTWIN.ROM      [Page:0x173 ID:XMTW Rev:2022-06-29 YCRC:0x8F1118C5]

HH:MM:SS Report     SMAT43.ROM      [Page:0x1A2 ID:SM44 Rev:2022-06-29 YCRC:0xC7FE7120]

HH:MM:SS Report     WARPB1.ROM      [Page:0x1B8 ID:WARP Rev:2022-06-29 YCRC:0x23F9223A]

HH:MM:SS Report     WARPB2.ROM      [Page:0x1B9 ID:WARP Rev:2022-06-29 YCRC:0x3869A14A]

HH:MM:SS Report     WARPB3.ROM      [Page:0x1BA ID:WARP Rev:2022-06-29 YCRC:0x9E92DDB3]

HH:MM:SS Report     XMEMXF.ROM      [Page:0x202 ID:XMXF Rev:2022-06-29 YCRC:0x407CDBAC]

HH:MM:SS Report     XMMTRX.ROM      [Page:0x203 ID:XMMA Rev:2022-06-29 YCRC:0x40F50C7D]

HH:MM:SS Report     XMPPC.ROM       [Page:0x204 ID:XMPP Rev:2022-06-29 YCRC:0x74968745]

HH:MM:SS Report     2022JUL.ROM     [Page:0x288 ID:CEPH Rev:2022-06-29 YCRC:0x18C5232A]

HH:MM:SS Report     2022JUN.ROM     [Page:0x289 ID:LEPH Rev:2022-06-29 YCRC:0x503081B1]

HH:MM:SS Report     14 outdated pages, out of 1024 pages, spread over 8 Flash blocks, estimated update time: 00h 26m 28s

Note 1: your list will be longer because your FLDB is older.
Note 2: the estimated update time above is pretty much what it will take to complete the update.

Now we do the actual update, on the 41CL

Code:

Command       Description

------------  ---------------------------------------------------

FLUPD         Update Flash Memory

On your computer, for each ROM being updated you will see something like this:

Code:

HH:MM:SS Received   PAGE_IMPORT_REQUEST(0x53) [Page:0x0B7]

HH:MM:SS Image      EVAL_3K.ROM     [Page:0x0B7 ID:FRML Rev:2022-06-29 YCRC:0xFEA85C11]

HH:MM:SS Sending    8192 = 8192 bytes sent

The update will go on until you see "UPD DONE" on your 41CL.

On the 41CL type:

Code:

Command       Description

------------  ---------------------------------------------------

CDBEXP        Export CFLDB ROM image

On your computer, you should see the updated FLDB (called CFLDB) being uploaded to your computer and the updated report.

Code:

HH:MM:SS Received   CORR_FLDB_8MB_EXPORT_REQUEST(0x4F)

HH:MM:SS Sent       CORR_FLDB_8MB_EXPORT_RESPONSE(0x50)

HH:MM:SS Receiving  2183 2186 2186 1637 = 8192 bytes received

HH:MM:SS File       CFLDB.ROM saved

HH:MM:SS Report     Outdated ROM images [BoardGeneration: third]

HH:MM:SS Report     0 outdated pages, out of 1024 pages, spread over 0 Flash blocks, estimated update time: 00h 00m 00s

Note: if you have outdated system ROM your list will not be empty.
If that is the case I will address that scenario in another post.

On the 41CL type:

Code:

Command       Description

------------  ---------------------------------------------------

CMCLOSE       Close serial port

OFF           

ON            To reactivate the sleep mode on your 41CL

CDBDEL        To clear the CFLDB location in your 41CL.

FDBVER?       Get current FLDB version of your 41CL

The output is the FLDB date currently installed in your 41CL. Date format respect MDY/DMY mode.
You should see 06/29/2022 for June 29th, 2022.

I hope this is detailled enough so you can do it.

Regards,

Sylvain

edit 1: typos
edit 2: added optional & MDY/DMY comments

Chr Yoko · 07-21-2022, 09:02 AM

Merci Sylvain, super useful "pense-bête" ;-)

Uli · 07-21-2022, 10:02 PM

Dear Sylvain,

what for a great document. I am currently traveling, but I read carefully through it and I can say that is absolutely that what I am looking for. I would like to say thanks a lot. I will test it on Sunday and it’s difficult for me to wait.

I am sure that I can manage the update procedure now.

Thank you very much!

Greetings
Uli

Uli · 07-25-2022, 08:44 PM

After FLCHK? everything seemed to be ok.
The HP41CL made a beep every ~ 5 sec.. PC shew many, many „)“.

And after nearly 3 hours the procedure ended, as mentioned at the beginning.
But unfortunately without success.

Please see the screenshot of the pc. Do you have any idea? If not, I will try it again.

I have not used TURBO50. I used it first, but the FLCHK? needed only a few seconds, so I thought something went wrong.

Monte Dalrymple · 07-25-2022, 09:48 PM

(07-25-2022 08:44 PM)Uli Wrote: After FLCHK? everything seemed to be ok.
The HP41CL made a beep every ~ 5 sec.. PC shew many, many „)“.

And after nearly 3 hours the procedure ended, as mentioned at the beginning.
But unfortunately without success.

Please see the screenshot of the pc. Do you have any idea? If not, I will try it again.

I have not used TURBO50. I used it first, but the FLCHK? needed only a few seconds, so I thought something went wrong.

The update functions automatically go to 50x while running. Nothing you need to do.

Your first FLCHK? ran in CPONLY mode, which is MUCH faster. Nothing went wrong. The message on the screen should have shown the number of pages needing an update. and it would have been fine to do FLUPD at that point.

Your screenshot shows the FLCHK? running regularly, taking long enough that the connection to the serial port (by Java) seems to have been lost. The "keep-alive" message sent by the 41CL was intended to keep the PC awake, but unfortunately doesn't seem to do that. Best laid plans.

Sylvain Cote · (This post was last modified: 07-26-2022 03:53 PM by Sylvain Cote.)

Hello Uli,

As Monte said, when CPONLY is active, scanning is much faster, like 170 times faster, so instead of taking a little less than 3 hours, it takes a little more than a minute.

This is the first time I am seeing this error.
Serial communication works.
The program fails when it is trying to write the CFLDB.ROM image to disk, which is right after it has received it from the serial port.

Code:

...

HH:MM:SS Received   CORR_FLDB_8MB_EXPORT_REQUEST(0x4F)

HH:MM:SS Sent       CORR_FLDB_8MB_EXPORT_RESPONSE(0x50)

HH:MM:SS Receiving  2176 2186 2193 1637 = 8192 bytes received

HH:MM:SS File       CFLDB.ROM saved    ← ← ← program fails here

HH:MM:SS Report     Outdated ROM images [BoardGeneration: third]

...

Something is preventing the program to write the CFLDB.ROM file.

Do you have write access to that disk/folder ?
Do you have a file named CFLDB.ROM who is read only in that folder ?

UPDATE

I just tried it.
I have created a CFLDB.ROM file on my disk then changed the file attributes to read only.
Then, I have run the program and got the same error as you.
So, delete the CFLDB.ROM file that is on your disk, Windows will ask you to confirm it, then retry the procedure with the CPONLY option this time.

Best regards,

Sylvain

Edit: typos

Chr Yoko · 07-26-2022, 12:24 PM

I just used Sylvain procedure's with freshly recharged NiMh cells.

Doing so i found a typo hereby :

Code:

PLUG1H        Map YUPS ROM image to page 9 (port 1 high page)

H is wrong, U is right => XEQ PLUG1U

And on the DOS line :

Code:

java -jar clupdate-1.1.0.jar --update rom_files_220629.zip COMx 4800

=> Do not forget to replace the x into COMx by your COM number (mine was COM2 on the GPD Pocket 2 and of course got an error with a x instead ....).

Worked well besides a transmission error during the update phase that i had to restart over on the 41CL and it resumed from there.
Maybe one ROM has been missed in the process ?

I redid a

Code:

Code:

Command       Description

------------  ---------------------------------------------------

CPONLY        Enable compare mode.

"*"           All Flash memory will be scanned

FLCHK?        Scan Flash ranged specified in ALPHA

And got no update proposed, so i guess all went well :-)
(first time i tried without the XEQ CPONLY and it was running crazy slow as Monte is warning above)....

Sylvain Cote · 07-26-2022, 02:36 PM

(07-26-2022 12:24 PM)Chr Yoko Wrote: Doing so i found a typo hereby :

Code:

PLUG1H Map YUPS ROM image to page 9 (port 1 high page) H is wrong, U is right => XEQ PLUG1U

Oups, corrected, thanks!

(07-26-2022 12:24 PM)Chr Yoko Wrote: And on the DOS line :

Code:

java -jar clupdate-1.1.0.jar --update rom_files_220629.zip COMx 4800
=> Do not forget to replace the x into COMx by your COM number (mine was COM2 on the GPD Pocket 2 and of course got an error with a x instead ....).

Well, yeah, I was assuming that it was clear, but you are right of course to mention it.

Monte Dalrymple · 07-26-2022, 04:22 PM

(07-26-2022 12:24 PM)Chr Yoko Wrote: I just used Sylvain procedure's with freshly recharged NiMh cells.

Doing so i found a typo hereby :

Code:

PLUG1H Map YUPS ROM image to page 9 (port 1 high page) H is wrong, U is right => XEQ PLUG1U

And on the DOS line :

Code:

java -jar clupdate-1.1.0.jar --update rom_files_220629.zip COMx 4800
=> Do not forget to replace the x into COMx by your COM number (mine was COM2 on the GPD Pocket 2 and of course got an error with a x instead ....).

Worked well besides a transmission error during the update phase that i had to restart over on the 41CL and it resumed from there.
Maybe one ROM has been missed in the process ?

I redid a

Code:

Code: Command Description ------------ --------------------------------------------------- CPONLY Enable compare mode. "*" All Flash memory will be scanned FLCHK? Scan Flash ranged specified in ALPHA

And got no update proposed, so i guess all went well :-)
(first time i tried without the XEQ CPONLY and it was running crazy slow as Monte is warning above)....

CPONLY mode is fine if the Flash is known-good. That is, nothing messed with the Flash since the last update AND the last update finished cleanly. CPONLY only compares FLDB values between the 41CL and the PC, so it's only good if the YCRC values in the FLDB actually reflect the state of the Flash. An update that doesn't finish cleanly means that some pages may not have been updated, even though the FLDB _has_ been updated. So, I would probably run FLCHK again, but NOT in CPONLY mode. Or look at the PC screen to see where things went wrong.

Uli · 07-26-2022, 08:09 PM

Hi All!

Today I was successful, because of your wonderful support.
Thanks a lot !

PLUG1H: I have changed it in the beginning of my tests to PLUG1U without understanding why.

TURBO50: to activate it I need always to remove the serial connection before.

Access to folder: Sylvain solved my main problem. There was no access to the folder , where clupdate is installed. My fault!

UPDATE IS DONE. And I feel like a king.

Should I do anything in addition because I have have outdated system ROM ?
If not, it’s okay for me.

Sylvain Cote · (This post was last modified: 07-26-2022 08:56 PM by Sylvain Cote.)

Hello Uli,

... or should I say Majesty Big Grin

Great news!

Here is the procedure to update the OS Flash block.
I am skipping some intermediate output.

Assuming the same 41CL configuration

Code:

Command       Description

------------  ---------------------------------------------------

MMUDIS        Disable memory management unit

MMUCLR        Clear MMU configuration

"YFNX"        41CL Extreme Functions ROM image identifier

PLUG1L        Map YFNS ROM image to page 8 (port 1 low page)

"YUPS"        41CL Update Functions ROM image identifier

PLUG1U        Map YUPS ROM image to page 9 (port 1 high page)

MMUEN         Activate MMU configuration

From the command line:

Code:

cd folder-where-clupdate-and-rom_files-are-located

java -jar clupdate-1.1.0.jar --update rom_files_220629.zip COMx 4800

You should see something like this on your computer: (I use a Mac so my serial port name is different than the ones on Windows)

Code:

hh:mm:ss --update   [fileName: rom_files_220629.zip] [portName: /dev/tty.usbserial-AQ01D0DE] [baudRate: 4800]

hh:mm:ss File       rom_files_220629.zip loading ... done

hh:mm:ss Serial     /dev/tty.usbserial-AQ01D0DE opened at 4800 baud.

hh:mm:ss Waiting    for 41CL commands ...

On the 41CL

Code:

Command       Description

------------  ---------------------------------------------------

CMOPEN        Open serial port

OSUPDT        Disable OS Flash block protection

"000>007"     Pages range to be scanned/updated

FLCHK?        Scan Flash ranged specified in ALPHA

FLUPD         Update Flash Memory

CDBEXP        Export CFLDB ROM image

On your computer, you should see the updated FLDB (called CFLDB) being uploaded to your computer and the updated report.

Code:

HH:MM:SS Received   CORR_FLDB_8MB_EXPORT_REQUEST(0x4F)

HH:MM:SS Sent       CORR_FLDB_8MB_EXPORT_RESPONSE(0x50)

HH:MM:SS Receiving  2183 2186 2186 1637 = 8192 bytes received

HH:MM:SS File       CFLDB.ROM saved

HH:MM:SS Report     Outdated ROM images [BoardGeneration: third]

HH:MM:SS Report     0 outdated pages, out of 1024 pages, spread over 0 Flash blocks, estimated update time: 00h 00m 00s

On the 41CL

Code:

Command       Description

------------  ---------------------------------------------------

OSPROT        Enable OS Flash block protection

CMCLOSE       Close serial port

CDBDEL        To clear the CFLDB location in your 41CL.

FDBVER?       Get current FLDB version of your 41CL

The output is the FLDB date currently installed in your 41CL. Date format respect MDY/DMY mode.
You should see 06/29/2022 for June 29th, 2022.

Regards,

Sylvain

Edit: typos

Uli · 07-27-2022, 02:19 PM

It is sooooooooo easy to update the HP41CL ....
if I get help from YOU!

:-)