Fluke 123 working Firmware update need

[mario_nks]

Hello, I am looking for a working update for my Fluke 123.
Unfortunately, the version I found (FlashTool_F123_V108) doesn't seem to work properly.
The update process consistently aborts at the exact same point—specifically, when it attempts to write the calibration data.

Unfortunately, I'm at a loss as to how to proceed.

Perhaps someone here has a working version or even a helpful tip for me.

Best regards,

Mario

[squadchannel]

Is the calibration still present after the update? Are there any errors? Is the serial number still there?

If it is the same as the 190/190B-C/190II/THS3000, the firmware update will be performed in this order.

Set baud rate
Check serial number and model number
Dump calibration data
Switch to UHM mode
Write loader firmware
Erase flash memory
Write firmware
Reboot
Write calibration data
Set clock
Done.

question is whether the calibration data is still present. Check that first.

[mario_nks]

I attempted to get the device working again using the Software Update Tool, but the update only proceeds to a certain point before aborting.

I am only able to update the firmware by using the key combination of Up Arrow + Right Arrow + Power (accompanied by a faint beep)

otherwise the Thing is dead, just a tikel when powerd on abaout 0,5s

[squadchannel]

I knew it.
So you’re one of the people who had trouble with the firmware update, just like me.

try sending the ID command while the power is off.
9600 baud
Use the CR line feed character, not CRLF.

[mario_nks]

Thanks—how does that work?

[squadchannel]

IDentification

brand, model, firmware revision, firmware date, serial number, and available languages are returned.
If the serial number is intact, it should be currect serial number are returned. If the serial number field returns "SERIAL NUMBER" the calibration data is corrupted.


Huh, I thought I was supposed to get a reply. Talk about a huge misunderstanding.
try "QI 11"

QI 10 = model
QI 11 = serial
QI 12 = mainboard serial

[mario_nks]

The Problem is, that i could not do anything.

Only when i use key combination of Up Arrow + Right Arrow + Power (accompanied by a faint beep).

But i dont get any answer back

[mario_nks]

What settings do I actually need to configure just to connect?

Could you perhaps take a screenshot of that?

[squadchannel]

Don’t press any buttons. Unplug the power adapter, plug it back in, and then try again.

If you still don’t get a response,
after you hear that faint beep,
enter the capital letter X repeatedly until “0” response. You should get a response after about 10 attempts.
When you enter the ID command, you should “Universal Host Mask software; UHM V3.0” in response.


Once you've confirmed that you're in UHM, try sending the following command.

Code: [Select]

RB40008000,100Please reply the response. or, try pasting it into a binary editor.

[squadchannel]

What settings do I actually need to configure just to connect?

Could you perhaps take a screenshot of that?

In that case, hold on a second. I have some software I made.

modify the ports in the attached .cfg file to match your environment.
Drag and drop the .cfg file onto the .exe file after hearing a faint beep.
If the process completes without errors, an output file should be generated. I will perform a calibration dump. I believe it’s in the same location as the 190 series, but I’m not certain.
If an error occurs, reply with the message displayed. I will look into it.

[mario_nks]

This does not work. On which System should i try this

[squadchannel]

It will not work unless you use the 64-bit version. The 32-bit version of the MSYS2 environment has been deprecated.

attached. compiled for x86

[mario_nks]

I Think that is not normal

[squadchannel]

it's version 2.1, maybe the GB command doesn't exist.
I'll take a look.

[squadchannel]

If you're using PuTTY, see the image below.




After a faint beep, type a series of capital Xs, and you should return "0".
Then, type “help” and press Enter. Take a screenshot of the result and send it back to me.

[mario_nks]

i get this

[squadchannel]

I'm stuck. I don't know what to do.

Also, address of the calibration data is different....

[squadchannel]

@asis

Do you know the UHM command for 190 non BC model?
It looks like V2.1, but it seems that a RB/GB command present in v3.0 is missing.

[asis]

Hi,
@squadchannel

I have an FLK199C, but there's a SW for the FLK123/124:
Flash Tool_F123_V108 - 630 KB;
Flash Tool_F123_F124_V203 - 552 KB;
TestFluke123 - 630 KB;
-
What exactly are you looking for?
-
There's some experience with the Fluke 199 (not B/C) in the archives.
It takes time.

[squadchannel]

First of all, his 123 firmware is corrupted.
Assuming it’s the same as the 190B-C/190II, I initially planned to use the GB command via UHM to read the calibration data.

However, the first problem is
that the GB/RB commands cannot be executed for some reason,
and that the memory addresses for the calibration data differ from those of the 190B-C/190II.

Do you know the base address where the flash memory is located?
flash:0x800000
loader:0x400000

If you send “help” in UHM mode, do you get a response? If it’s UHM V3.0, it should return a list of available commands, but that doesn’t seem to be the case.

If there are significant differences between V2.1 and V3.0, this becomes more complicated.
I wish I had a dump of the 123.

[squadchannel]

Come to think of it, the GB command might have failed because the address was incorrect.

@mario_nks
Let's try it out using the attached cfg file.

Code: [Select]


GB000000,10000
GB800000,800000

This should result in two files being created.
The flash memory is likely located at 0x80000 - 0xFFFFF.
The UHM firmware is located at 0x0 - 0x10000.

compress and attach the created file.

[mario_nks]

here it is

[asis]

Hi,

@squadchannel

First of all, I'd like to know what platform the Fluke 123 is built on.
I looked at the FlashTool123 V1.08 and FlashTool123/124 V2.03 dump's and found that the basic control commands are only present in V2.03.
-
Let's find out.

[squadchannel]

No, commands exists in both versions.

I believe the difference between V1.xx and V2.xx lies in the hardware.
The LDF for V1.xx does not include an initialization command to enable the MMU.
V2.xx does include it.

This is likely because the increase in firmware size necessitated hardware changes, and with the installation of a larger-capacity flash memory, enabling the MMU became unavoidable.
The firmware that does not enable the MMU is found in the first-generation 19x equipped with UHM V2.1.
Also, the memory test section of the 123 service manual describes the response to the ID command in UHM mode. The manual shows V3.0, so his 123 must be an older model.

It might be difficult unless we know exactly what commands the V1.xx firmware updater sends. If we could use the RB/GB commands available in UHM V3.0, we could at least check the calibration status.

123 V108 and V203


190 V400


https://nl.linkedin.com/in/rob-van-de-schepop-750a5b15
ask the UHM developer, he might know something.....

[asis]

OK.
Exhaustively...
Thank you!