CATStudio GKI signal injection fails for all signals — "Failed to open ...gki" — missing NvmData template files

Technical Subjects Software General Function
1

Environment

  • Tool: CATStudio V3.1.0.85
  • Module: Quectel EC200A, Revision: EC200AEUHAR01A21M16 , ASR Microelectronics baseband
  • Install path: ...\CATStudio_V3_1_0_85\Exec\

Issue

Attempting to send any signal from CommandConsole’s GKI tab fails with the same error, regardless of which signal is selected:

Failed to open "...\CATStudio_V3_1_0_85\Exec\NvmData\<signalName>.gki" file.

Steps to reproduce

  1. Open CommandConsole → GKI tab.
  2. Select any entry from “Available Signals” (tested with sacErrcEcidMeasReq, sacDevGetErrcMeasInfoReq, sacErrcGetLteCaInfoReq, and several others).
  3. Click Send.
  4. Error dialog appears immediately, referencing a missing .gki file for that specific signal.

Diagnostic notes

  • The Exec\NvmData\ folder does not exist on this installation at all prior to attempting a send.
  • The failure is identical across every signal tested — not isolated to one function or subsystem — which suggests a missing/incomplete local template library (NvmData) rather than a per-signal issue.
  • All other CommandConsole functionality (Command Server tab, diag command sending, UEFilter logging mask) works normally; only GKI signal sending is affected.

Questions

  1. Is a pre-populated NvmData folder (containing .gki template files per signal) meant to ship with the CATStudio install package, or is it expected to be auto-generated on first use? Ours currently has neither.
  2. Could you provide the complete Exec\NvmData folder (or a corrected/complete CATStudio_V3.1.0.85 install package) so GKI signal templates are available locally?
  3. Separately — is GKI-level signal injection restricted or disabled by firmware/licensing on this specific module SKU or firmware build? We want to rule this out explicitly, since the symptom could theoretically originate on either the tool side or the firmware side.

Happy to provide the exact firmware version, IMEI, or additional logs if useful for troubleshooting.