Threaded Mode | Linear Mode

Neve · 01-15-2018, 04:07 PM

Hi,
I downloaded the new Clupdate program along with the rom_files_171202.zip.
I assume this is the newest update for everything, right? Because I also have the METX.ZIP, PWRX.ZIP and the WARP.ZIP flies.
Now can someone give me a step-by-step howto?
I know how to open a link to the calc. But then what...?
I tried to do a java -jar clupdate-1.1.0.jar —update rom_files_171202.zip /dev/tty.usbserial 4800
And I get:
8192 = 8192 bytes sent
And nothing. The calc returns to 0.0000
And what about the other files I mentioned? What do I do with them??

This may sound obvious to most of you, but I’m really a newbie...

Thanks for your help,

Sylvain Cote · 01-15-2018, 04:52 PM

I am at work at the moment, it's 11h50 here (GMT-5).
I will not be able to help you before 21h00.
Sylvain

Neve · 01-15-2018, 05:09 PM

(01-15-2018 04:52 PM)Sylvain Cote Wrote: I am at work at the moment, it's 11h50 here (GMT-5).
I will not be able to help you before 21h00.
Sylvain

No problem Sylvain, whenever you can.
You’re help is always valuable and appreciated.

Thank you.

**rprosperi** · 01-15-2018, 06:45 PM

Until Sylvain is available (he may have updated his tutorial), there is a quite detailed step-by-step explanation available here:

http://www.hpmuseum.org/forum/thread-926...l#pid82047

Keep in mind this was a few months ago, so some small details have changed (e.g. the clupdate program is no longer 1.0.0, so would need to use the updated version number, the UPDAT ROM is now version 3B, etc.) but the sequence and flow are still the same.

A key thing to understand is the clupdate software is a server that, once run with --update option, will sit and wait for data requests; the actual update process (initially scanning and then updating) is controlled by commands on the 41CL.

Also, the updates you will need will be unique to your machine's age and configuration, so interpret the results stated in that walk-through accordingly.

If you will be doing a full update (a good idea), plan on spending a few hours for the complete process, and I suggest you start with a fresh set of N batteries in your 41CL. For 95+% of that time you don't need to do anything, just wait for the update process to proceed.

Good Luck

Neve · 01-15-2018, 06:57 PM

Thank you.
I’d actually like to do a full update of my new V5 board.

**rprosperi** · 01-15-2018, 07:24 PM

(01-15-2018 06:57 PM)Neve Wrote: Thank you.
I’d actually like to do a full update of my new V5 board.

No problem with that, the procedure is exactly the same. With a V5 board, there are only a few updates needed, so total update time should be less than 30 mins.

Neve · 01-16-2018, 03:27 AM

(01-15-2018 07:24 PM)rprosperi Wrote:
(01-15-2018 06:57 PM)Neve Wrote: Thank you.
I’d actually like to do a full update of my new V5 board.

No problem with that, the procedure is exactly the same. With a V5 board, there are only a few updates needed, so total update time should be less than 30 mins.

Not working....

Neve · 01-16-2018, 03:40 AM

This is what I get:

java -jar clupdate-1.1.0.jar --update rom_files_171202.zip /dev/tty.usbserial 4800

04:36:46 --update [fileName: rom_files_171202.zip] [portName: /dev/tty.usbserial] [baudRate: 4800]
04:36:46 File rom_files_171202.zip loading ... done
04:36:48 Serial /dev/tty.usbserial opened at 4800 baud.
04:36:48 Waiting for 41CL commands ...
04:36:50 Received OPEN_CHANNEL_REQUEST(0x41)
04:36:50 Sent OPEN_CHANNEL_RESPONSE(0x42)

After CMOPEN, nothing on the calculator. Zilch.
It just returns to 0.0000

What am I missing...?

Sylvain Cote · (This post was last modified: 01-17-2018 12:45 AM by Sylvain Cote.)

(01-16-2018 03:40 AM)Neve Wrote: This is what I get:

java -jar clupdate-1.1.0.jar --update rom_files_171202.zip /dev/tty.usbserial 4800

04:36:46 --update [fileName: rom_files_171202.zip] [portName: /dev/tty.usbserial] [baudRate: 4800]
04:36:46 File rom_files_171202.zip loading ... done
04:36:48 Serial /dev/tty.usbserial opened at 4800 baud.
04:36:48 Waiting for 41CL commands ...
04:36:50 Received OPEN_CHANNEL_REQUEST(0x41)
04:36:50 Sent OPEN_CHANNEL_RESPONSE(0x42)

After CMOPEN, nothing on the calculator. Zilch.
It just returns to 0.0000

What am I missing...?

Hello Neve,

I was not able to finish updating the update procedure last night, sorry about that.

Good news, is that it is working.
CMOPEN only open the communication channel, its normal response is nothing on the calculator and OPEN_CHANNEL_REQUEST/OPEN_CHANNEL_RESPONSE on the computer.

I suggest that you really read the following documents:

clupdate-1.1.0-readme.txt (part of the clupdate-1.1.0.zip file)
41CL Update Functions Manual
HHC 2017 CLUpdate Presentation Document & Video

Open up the clupdate-1.1.0-readme.txt file and go to line 611, you will see an example of the update process.

The basic things that you have to type on the calculator once everything has been setup are:

Code:

CMOPEN         // open up the communication channel

"*"            // scan all Flash space for outdated ROMs

FLCHK?         // do the scanning process (take around 3 hours on the v5 board)

"*"            // update all outdated ROMs marked by FLCHK?

FLUPD          // do the update process (should not take much time since your v5 is almost up to date)

CMCLOSE        // close communication channel

Best regards,

Sylvain

edit: FLUPD was misspelled

**rprosperi** · 01-16-2018, 03:11 PM

(01-16-2018 03:40 AM)Neve Wrote: After CMOPEN, nothing on the calculator. Zilch.
It just returns to 0.0000

What am I missing...?

As Sylvain noted, this is correct and as I noted yesterday, this means the clupdate server software is waiting for commands on the 41CL

Initially this can be confusing as most often an update such as this is controlled from the PC side, but the 41CL is smart enough to check which updates it needs and then request them from the server (which is waiting for these requests).

Note the line:
04:36:48 Waiting for 41CL commands ...

You should be OK to update your V5.

Neve · 01-16-2018, 07:37 PM

(01-16-2018 01:14 PM)Sylvain Cote Wrote: Hello Neve,

I was not able to finish updating the update procedure last night, sorry about that.

Good news, is that it is working.
CMOPEN only open the communication channel, its normal response is nothing on the calculator and OPEN_CHANNEL_REQUEST/OPEN_CHANNEL_RESPONSE on the computer.

I suggest that you really read the following documents:

clupdate-1.1.0-readme.txt (part of the clupdate-1.1.0.zip file)

41CL Update Functions Manual

HHC 2017 CLUpdate Presentation Document & Video

Open up the clupdate-1.1.0-readme.txt file and go to line 611, you will see an example of the update process.

The basic things that you have to type on the calculator once everything has been setup are:

Code:

CMOPEN // open up the communication channel "*" // scan all Flash space for outdated ROMs FLCHK? // do the scanning process (take around 3 hours on the v5 board) "*" // update all outdated ROMs marked by FLCHK? FLUDP // do the update process (should not take much time since your v5 is almost up to date) CMCLOSE // close communication channel

Best regards,

Sylvain

OK, process started.
This is what I have on the screen after XEQ FLCHK?:
java -jar clupdate-1.1.0.jar --update rom_files_171202.zip /dev/tty.usbserial 4800

20:27:16 --update [fileName: rom_files_171202.zip] [portName: /dev/tty.usbserial] [baudRate: 4800]
20:27:16 File rom_files_171202.zip loading ... done
20:27:18 Serial /dev/tty.usbserial opened at 4800 baud.
20:27:18 Waiting for 41CL commands ...
20:27:20 Received OPEN_CHANNEL_REQUEST(0x41)
20:27:20 Sent OPEN_CHANNEL_RESPONSE(0x42)
20:28:39 Received FLDB_8MB_IMPORT_REQUEST(0x47) [Page: 0x0DE] [BoardGeneration: third] [EstimatedFullScan: 02h 51m 18s]
20:28:39 File [FileName: FLDB.ROM] [YCRC:0x12022017] [Rev: 2017-12-02]
20:28:39 Sending 8192 = 8192 bytes sent
20:29:06 Received KEEP_ALIVE(0x59))))))))))))))))))))

Now waiting... I'll be reading what you recommended, a little at a time....

Is this all I have to do?
What about the other files I have: METX.ZIP, PWRX.ZIP and WARP.ZIP? Do I need to update the separately, or are they included in the rom_files_171202.zip file?

Thank you all!!

Neve · 01-16-2018, 07:55 PM

(01-16-2018 03:11 PM)rprosperi Wrote:
(01-16-2018 03:40 AM)Neve Wrote: After CMOPEN, nothing on the calculator. Zilch.
It just returns to 0.0000

What am I missing...?

As Sylvain noted, this is correct and as I noted yesterday, this means the clupdate server software is waiting for commands on the 41CL

Initially this can be confusing as most often an update such as this is controlled from the PC side, but the 41CL is smart enough to check which updates it needs and then request them from the server (which is waiting for these requests).

Note the line:
04:36:48 Waiting for 41CL commands ...

You should be OK to update your V5.

Thank you!!!

Sylvain Cote · (This post was last modified: 01-17-2018 12:46 AM by Sylvain Cote.)

(01-16-2018 07:37 PM)Neve Wrote:
(01-16-2018 01:14 PM)Sylvain Cote Wrote: ...
The basic things that you have to type on the calculator once everything has been setup are:

Code:

CMOPEN // open up the communication channel "*" // scan all Flash space for outdated ROMs FLCHK? // do the scanning process (take around 3 hours on the v5 board) "*" // update all outdated ROMs marked by FLCHK? FLUPD // do the update process (should not take much time since your v5 is almost up to date) CMCLOSE // close communication channel
...

You typed: java -jar clupdate-1.1.0.jar --update rom_files_171202.zip /dev/tty.usbserial 4800
Result:

(01-16-2018 07:37 PM)Neve Wrote: 20:27:16 --update [fileName: rom_files_171202.zip] [portName: /dev/tty.usbserial] [baudRate: 4800]
20:27:16 File rom_files_171202.zip loading ... done
20:27:18 Serial /dev/tty.usbserial opened at 4800 baud.
20:27:18 Waiting for 41CL commands ...

You typed: XEQ "CMOPEN"
Result:

(01-16-2018 07:37 PM)Neve Wrote: 20:27:20 Received OPEN_CHANNEL_REQUEST(0x41)
20:27:20 Sent OPEN_CHANNEL_RESPONSE(0x42)

You typed: "*" then XEQ "FLCHK?"
Result:

(01-16-2018 07:37 PM)Neve Wrote: 20:28:39 Received FLDB_8MB_IMPORT_REQUEST(0x47) [Page: 0x0DE] [BoardGeneration: third] [EstimatedFullScan: 02h 51m 18s]
20:28:39 File [FileName: FLDB.ROM] [YCRC:0x12022017] [Rev: 2017-12-02]
20:28:39 Sending 8192 = 8192 bytes sent
20:29:06 Received KEEP_ALIVE(0x59))))))))))))))))))))

FYI: each time you see a closing parenthesis ")" a ROM image has been checked.
You have 1024 images to check on a v5 board, a new line is created after 32 ROMs has been checked, so expect 32 KEEP_ALIVE lines before the scanning ends.

(01-16-2018 07:37 PM)Neve Wrote: Now waiting... I'll be reading what you recommended, a little at a time....
Is this all I have to do?

Yes for the moment.

After the scanning is finished, you must do the actual update by typing: "*" then XEQ "FLUPD"

After the update is finished, you must close the communication by typing: XEQ "CMCLOSE"

(01-16-2018 07:37 PM)Neve Wrote: What about the other files I have: METX.ZIP, PWRX.ZIP and WARP.ZIP? Do I need to update the separately, or are they included in the rom_files_171202.zip file?

I do not know, I have to check, I will come back later with the answer.

Sylvain

Edit 1 & 2: typos / 3: FLUPD was misspelled

Neve · 01-16-2018, 09:03 PM

Yes, will do. Still ongoing....
Calc reads CRC 235
Thanks for checking Sylvain.

**rprosperi** · 01-16-2018, 09:19 PM

(01-16-2018 07:37 PM)Neve Wrote: What about the other files I have: METX.ZIP, PWRX.ZIP and WARP.ZIP? Do I need to update the separately, or are they included in the rom_files_171202.zip file?

The latest released version of these files (unless you got them directly from Angel) are included in the rom_files_171202.zip file, so no need to use them, your auto-update will include all that.

However there will be new versions of PWRX and WARP coming soon, so keep an eye on Monte's "File Area" page for a new version of the rom_files_YYMMDD.zip file. Although it is possible to update individual files manually, the auto-update process is designed to use the .zip ROM sets and I suggest you go this way in general.

Neve · 01-16-2018, 09:27 PM

(01-16-2018 09:19 PM)rprosperi Wrote:
(01-16-2018 07:37 PM)Neve Wrote: What about the other files I have: METX.ZIP, PWRX.ZIP and WARP.ZIP? Do I need to update the separately, or are they included in the rom_files_171202.zip file?

The latest released version of these files (unless you got them directly from Angel) are included in the rom_files_171202.zip file, so no need to use them, your auto-update will include all that.

However there will be new versions of PWRX and WARP coming soon, so keep an eye on Monte's "File Area" page for a new version of the rom_files_YYMMDD.zip file. Although it is possible to update individual files manually, the auto-update process is designed to use the .zip ROM sets and I suggest you go this way in general.

Oh, ok...

Theses individual files I have are the ones from http://systemyde.com/hp41/index.html ... So I don't know if they are included in the 171202 rom update...

But thanks anyways rprosperi

Neve · (This post was last modified: 01-16-2018 10:36 PM by Neve.)

Update

So far:

23:23:10 Received CORR_FLDB_8MB_EXPORT_REQUEST(0x4F)
23:23:10 Sent CORR_FLDB_8MB_EXPORT_RESPONSE(0x50)
23:23:10 Receiving 2184 2186 2186 1636 = 8192 bytes received
23:23:29 File CFLDB.ROM saved
23:23:29 Report Outdated ROM images [BoardGeneration: third]
23:23:29 Report YLIB-3C.ROM [Page:0x00B ID:YLIB Rev:2017-12-01 YCRC:0x6DAA8777]
23:23:29 Report CLILUPD.ROM [Page:0x064 ID:YUIL Rev:2017-12-01 YCRC:0xC5E62000]
23:23:29 Report MPATHS.ROM [Page:0x0C6 ID:METX Rev:2017-12-01 YCRC:0x2ECCA7B0]
23:23:29 Report FLDB.ROM [Page:0x0DE ID:FLDB Rev:2017-12-02 YCRC:0x12022017]
23:23:29 Report IMDB.ROM [Page:0x0DF ID:IMDB Rev:2017-12-01 YCRC:0x6CD0415C]
23:23:29 Report PWREXT2.ROM [Page:0x181 ID:PWRX Rev:2017-12-01 YCRC:0x130E6ABF]
23:23:29 Report WARPB1.ROM [Page:0x1B8 ID:WARP Rev:2017-12-02 YCRC:0x514CB769]
23:23:29 Report WARPB2.ROM [Page:0x1B9 ID:WARP Rev:2017-12-02 YCRC:0xF862D31E]
23:23:29 Report EPH2018A.ROM [Page:0x21C ID:P18E Rev: YCRC:0xAA054808]
23:23:29 Report EPH2018B.ROM [Page:0x21D ID:P18E Rev: YCRC:0xAA4816ED]
23:23:29 Report MORTAR.ROM [Page:0x221 ID:MRTR Rev: YCRC:0xCBFBFA57]
23:23:29 Report 11 outdated pages, out of 1024 pages, spread over 8 Flash blocks, estimated update time: 00h 25m 34s
23:26:15 Received OPEN_CHANNEL_REQUEST(0x41)
23:26:15 Sent OPEN_CHANNEL_RESPONSE(0x42)
23:27:58 Received PAGE_IMPORT_REQUEST(0x53) [Page:0x00B]
23:27:58 Image YLIB-3C.ROM [Page:0x00B ID:YLIB Rev:2017-12-01 YCRC:0x6DAA8777]
23:27:58 Sending 8192 = 8192 bytes sent
23:31:00 Received PAGE_IMPORT_REQUEST(0x53) [Page:0x064]
23:31:00 Image CLILUPD.ROM [Page:0x064 ID:YUIL Rev:2017-12-01 YCRC:0xC5E62000]
23:31:00 Sending 8192 = 8192 bytes sent
23:34:03 Received PAGE_IMPORT_REQUEST(0x53) [Page:0x0C6]
23:34:03 Image MPATHS.ROM [Page:0x0C6 ID:METX Rev:2017-12-01 YCRC:0x2ECCA7B0]
23:34:03 Sending 8192 = 8192 bytes sent

At first the FLUDP returned "NONEXISTENT", so I tried FLUPD, same result "NONEXISTENT"... Then the calc turned itself off ...!!!
Powered it back on, CMOPEN. And it "seems" to be working... Weird...

Sylvain Cote · 01-17-2018, 12:54 AM

(01-16-2018 10:35 PM)Neve Wrote: At first the FLUDP returned "NONEXISTENT", so I tried FLUPD, same result "NONEXISTENT"...

I had given the instructions by memory and misspelled the FLUPD function, sorry about that.

(01-16-2018 10:35 PM)Neve Wrote: Then the calc turned itself off ...!!!
Powered it back on, CMOPEN. And it "seems" to be working... Weird...

This is typical of a low battery scenario.
Anyway, if your calculator goes off, you just need to execute a CMOPEN to reopen the communication, then execute the FLUPD function to continue the update were it was.

Sylvain

Neve · 01-17-2018, 06:41 AM

(01-17-2018 12:54 AM)Sylvain Cote Wrote:
(01-16-2018 10:35 PM)Neve Wrote: At first the FLUDP returned "NONEXISTENT", so I tried FLUPD, same result "NONEXISTENT"...
I had given the instructions by memory and misspelled the FLUPD function, sorry about that.

No sweat, I figured as much...

(01-16-2018 10:35 PM)Neve Wrote: Then the calc turned itself off ...!!!
Powered it back on, CMOPEN. And it "seems" to be working... Weird...

(01-17-2018 12:54 AM)Sylvain Cote Wrote: This is typical of a low battery scenario.
Anyway, if your calculator goes off, you just need to execute a CMOPEN to reopen the communication, then execute the FLUPD function to continue the update were it was.

Sylvain

Yes, although I had a fresh set of rechargeable batteries in it that I had just recharged for that purpose. So I suppose the other files I mention are not needed...? Did you have time to check?

Or maybe someone can tell me how to install and check individual files? Now that I know how to do a comple update...

Thanks for bearing with me.

I know I should make more time and read all the manuals and everything! But so much to do and so little time.... I will eventually (It’s not my field of expertise, so I might not understand everything, but I will)