Fluke 19X/B/C/II Firmware to Binary converter

[patpat]

Fluke 19X/B/C/II Firmware to Binary converter
FlukeFW2Bin.exe takes the firmware file (Tetra.ldf, or data.bin) from within Fluke's FlashTool
(F190_II_V11.44.exe, FlashTool_19xC_2xC_V804.exe, FlashTool_F190C_V615.exe, etc.)
and converts it into 2 binary files for analysis purposes.

The firmware on these Fluke Scopes uses the Nucleus PLUS - Version CL7111A  RTOS what means
the uP is some form of ARM little-endian CL7111A probably similar to CIRRUS LOGIC CL-PS7111

The produced files binary must be loaded at 0x40000000 and 0x44000000
Entry point 0x40000080

Best,
Pat

[Assafl]

Since all of these use the same hardware - can a B version be converted to a C version?

[patpat]

Well the displays are essentially different but I do not know about the bandwidth differences.
At the moment I just looked a bit at the code related to the undocumented console commands.

EO ?
EX ?  Check Memory
FM ?
GD   GET DOWN
GL   GO TO LOCAL
GR   GO TO REMOTE
HO   HOLD
ID   IDENTIFICATION
IM ?
IS   INSTRUMENT STATUS
KY ?
PC   PROGRAM COMMUNICATION
PS   PROGRAM SETUP
PW ?
QC ?
QI ?
QM   QUERY MEASUREMENT
QP   QUERY PRINT
QS   QUERY SETUP
QW   QUERY WAVEFORM
RB ?
RC ?
RD   READ DATE
RI   RESET INSTRUMENT
RN ?
RP   REPLAY
RS   RECALL SETUP
RT   READ TIME
RW ?
SO   SWITCH ON
SS   SAVE SETUP
ST   STATUS QUERY
TA   TRIGGER ACQUISITION
VE ?
WB ?
WC ?
WD   WRITE DATE
WT   WRITE TIME
WW ?

EXTENSION COMMAND TABLE (RAM 0x444000000)
CF ?
EO ?
FC ?
PF ?
QF ?
TI ?
FP ?

[Assafl]

In the service manual Fluke states that the specific model is set when the main board is replaced. It can only be done at a Fluke service center.

My guess is that the run a console setup or modify an identification string.

The screen is just color. But it may be that a BW screen will be unreadable if the output is color.

Thanks for figuring out the console commands.

[lostking2008]

Does anyone know how to run the FlukeFW2Bin.exe utility, things like OS environment, commands, etc.? It does not come with any guide or readme.txt in the zip package.

Thanks,
Ken