v3.23.9: the CAP compatibility test suggestion on a failed install

A RAM install that fails at a LOAD step is typically the library-version
gate: the card verifies the CAP's import list when the Import component
completes (JC VM 4.5.2).  The failure hint now says so and points at the
CAP compatibility test (Set all 0.0, then restore the lines one at a time
to find the missing package and version), replacing the old "retry with a
smaller LOAD block" advice, which is a red herring for that gate.

The failure popup gains a one-click "Run the CAP compatibility test"
button: it closes the popup, switches the RAM operation selector to compat
and runs it with the same .cap (the file input still holds it and the probe
list is prefilled with its imports), so the diagnostic is one click away.

An INSTALL [for load] refusal now gets its own advice instead of the LOAD
hint: the card refused to open the load file - usually a duplicate load
file from an earlier run (delete the package first, Explore -> Delete), or
rejected load parameters.

Tests: the hint's wording and branches (LOAD vs INSTALL [for load]), the
button handler's op switch.  862 frontend + 842 Python; sw cache
simple-v422.

This commit is contained in:

Антон Трошин

2026-10-09 21:59:51 +03:00

parent dc8d71c6a7

commit 1473396e5b

7 changed files with 68 additions and 12 deletions

									
										pysim_simple_server/server.py
									
		+1
		-1
	
												View File
												
				@@ -36,7 +36,7 @@ from osmocom.tlv import BER_TLV_IE

				from osmocom.utils import rpad

				VERSION = '3.23.8'

				VERSION = '3.23.9'

				MAX_ENVELOPE_SEGMENTS = 5  # max SMS segments for outgoing C-APDU in ENVELOPE