Cross-version control

Since MultiProg 2.2.57, the desktop app and TGSN firmware verify each other's version before allowing programming operations.

What gets checked

When you open the TGSN backend in MultiProg:

1. The desktop app reads the TGSN firmware version (already exposed via the protocol).
2. It compares against the minimum required firmware for this MultiProg release.
3. The TGSN side runs the symmetric check — it knows the minimum MultiProg version it expects.

If either side is too old, the operation is refused with a clear message instead of failing later with a cryptic protocol error.

Why we need this

The TGSN protocol evolves between releases — new commands, new status frames, new arguments. Without a version gate, you would hit one of:

• Bad packet / timeout on commands the firmware doesn't know;
• a 3-byte status frame interpreted as 2-byte (target status silently dropped);
• parameters parsed in the wrong order on a new family.

The cross-check moves all of these into a single, readable error at connect time.

What the messages look like

MultiProg side (firmware too old) — comes from mp_version.h on the desktop. For MultiProg 2.3.0 the required minimum is TGSN ≥ 3.3.0:

TGSN firmware is too old for this version of MultiProg.
Required: TGSN ≥ 3.3.0
Detected: TGSN 3.2.x
Run TGSN Install to pull the latest firmware.

TGSN device side (modules not installed) — separate check shown on the device's Update screen when the system modules have never been pulled:

Please install modules via TGSN Installer
Required from version:
MultiProg 2.2.54 / TGSN 3.2.6

That second pair (2.2.54 / 3.2.6) is the prerequisite for the module mechanism itself — anything below those versions predates the modules feature. The active gate for ongoing operation is the mp_version.h constant above.

(Exact wording may vary slightly across releases.)

How to fix it

If the desktop is older:

• Settings → Check Updates in MultiProg pulls the latest installer and re-launches with admin rights — see Updates.

If the TGSN firmware is older:

1. Open TGSN → TGSN Install in MultiProg.
2. Run TEST to confirm the device is reachable.
3. Run Setup WiFi + authorization if your network or account changed.
4. Run Online installation (OTA) to pull the latest firmware and modules.

In the current release modules are not installed from the on-device Settings → Update menu — they are pulled only through the TGSN Install flow above. See Module management for details.

Troubleshooting

Symptom	Likely cause	Action
Connect refused with "TGSN firmware too old" right after a MultiProg upgrade	TGSN still on previous firmware	OTA the TGSN
Connect refused with "MultiProg too old" right after a TGSN OTA	Stale MultiProg installer	Update MultiProg, then reconnect
Both versions look fine but connect still refused	License module out of date (per-license F_K module)	Re-run TGSN Install (it refreshes the license module too)