TP1200 Comfort Panel Stuck on SIMATIC HMI Boot: Recovery Guide

1. Problem Description

The SIMATIC HMI TP1200 Comfort Panel fails to complete its boot sequence. The display shows the static "SIMATIC HMI" splash screen for an extended period, then drops to a blinking cursor in the upper-left corner of an otherwise blank screen. The runtime project never loads, the touch becomes unresponsive, and no further diagnostic output appears on the panel.

This symptom pattern is reported across two distinct failure modes that must be separated before applying a remedy:

1. Configuration migration failure – the active project was built for a different runtime environment (for example, a WinCC Basic V13 SP1 Basic Panel project) and has been ported into a WinCC Advanced V13 SP1 project targeting a TP1200 Comfort without a clean device swap.
2. Operating system / image corruption – the panel's internal flash image (the WinCE-based Comfort Panel runtime) has been damaged, typically by an interrupted firmware update, a power loss during a ProSave transfer, or an unsupported configuration push.

Both modes surface the same visual symptom (stuck splash + blinking cursor) but require different recovery paths. The diagnostic tree in section 4 separates them.

2. Affected Hardware and Software Versions

3. Root Cause Analysis

3.1 Runtime / Project Mismatch

The TP1200 Comfort is a Comfort-class panel. It does not run WinCC Basic / Basic Panel images. If a project originally targeted a Basic Panel (KTP400 Basic, KTP700 Basic, KTP900 Basic, KTP1200 Basic, etc.) and was simply re-pointed at the TP1200 Comfort, the panel will attempt to boot, recognise that the project image is incompatible, and stop at the splash screen. A blinking cursor with no further progress is the panel's standard fallback when the runtime loader cannot find or cannot execute a valid configuration.

3.2 Corrupted Flash Image

If the panel's internal image is intact, the same symptom is produced when:

• A firmware / image update was interrupted (power loss, Ethernet cable removed, ProSave or TIA closed mid-transfer).
• An incorrect or downgraded image was flashed that the bootloader cannot chain-load.
• Flash wear has progressed past the controller's bad-block reserve (typical endurance: ≥ 100,000 write cycles per sector, but write-intensive logging or constant recipe churn accelerates wear).
• The backup battery for the RTC / retentive area was allowed to discharge fully, leaving the registry in an inconsistent state.

3.3 Why the Splash Hangs

The Comfort Panel boot sequence is:

1. Bootloader (resides in protected NOR) → POST + memory test.
2. WinCE kernel load from NAND.
3. HMI loader service starts, mounts the project partition.
4. Runtime executable (HmiRtm.exe) launches the active project.

If step 3 or 4 fails, the loader leaves the splash on screen and yields to the WinCE explorer shell, which is what produces the blinking cursor at the upper-left corner of the desktop. This state is recoverable in software as long as the bootloader (step 1) is intact, which is the overwhelmingly common case.

4. Diagnostic Tree

Run the following checks in order before attempting any recovery:

1. Verify the project target. Open the project in TIA Portal, select the HMI device, and confirm the device type and version match the physical panel. If the device tree still shows a Basic Panel (KTP series), section 5 applies. If it shows the TP1200 Comfort with a valid image version, continue to step 2.
2. Attempt a direct Ethernet connection to ProSave. Configure a service PC with a fixed IP in the 192.168.0.0/24 range (the panel's default service IP is 192.168.0.2, the PC side typically 192.168.0.3). Ping the panel. If ping fails, the panel is in bootloader-level failure and only a serial / USB-PPI rescue or factory return is possible.
3. Check the loader output. Connect via ProSave → "Panel IP address / Name" → "Connect". A successful connection with no active project confirms a valid image and a project-level fault. A connection failure indicates image-level corruption.
4. Read the diagnostic buffer. ProSave → "Read diagnostic buffer" (when available) returns the last WinCE and loader events, which pinpoint whether the failure is project, registry, or image related.

5. Recovery Path A — Fix the Project: TIA Portal "Change Device / Version"

Use this path when the project was built for a Basic Panel runtime and has been incorrectly pushed to a Comfort Panel. This is the non-destructive fix and is the most common resolution when the original engineering was done in WinCC Basic and the commissioning PC only has WinCC Advanced.

5.1 Prerequisites

• TIA Portal V13 SP1 (or the version matching the panel's image) installed with both WinCC Basic and WinCC Advanced options.
• Full project archive (TIA Portal project file *.ap13 / *.ap14 / *.ap15) accessible from the engineering station.
• License key for WinCC Advanced V13 SP1 (a Comfort Panel runtime license is bundled with the engineering license; the panel itself ships with a 21-day trial if no license is present).

5.2 Step-by-Step

1. Open the project in TIA Portal. If TIA prompts for missing packages, install or point to the requested versions. Do not let TIA silently upgrade the project to a newer major version.
2. In the project tree, expand the HMI station and select the original Basic Panel device.
3. Right-click the device → "Change device / version".
4. In the dialog, navigate to SIMATIC HMI → Comfort Panels → 1200" → TP1200 Comfort. Confirm the order number (typically 6AV2124-1MC01-0AX0).
5. In the version column select 13.0.1.0 (V13 SP1) or whichever image version matches the panel's installed firmware. The dropdown only lists versions for which a license is available.
6. Click OK. TIA will re-bind all tags, screens, alarms, and recipes to the new device, and will warn about any features that are not supported on the Comfort platform (most KTP Basic features migrate cleanly; OP73 / OP77 texts do not).
7. Open Devices & Networks. Verify that the HMI connection to the PLC is still valid and the interface parameters (PROFINET name, IP, subnet) are correct for the new device.
8. Compile the HMI station: right-click the device → Compile → Software (rebuild all). Resolve all warnings. Errors must be zero before a download is attempted.
9. Download to the panel: right-click the device → Download to device → Software and configuration. Tick "Overwrite all" if the target is non-empty.

5.3 Verification

• The panel should complete the boot cycle in 60–90 s and reach the configured start screen.
• Tag values should reflect the live PLC state within one configured update cycle.
• ProSave → "Read diagnostic buffer" should show a clean boot with no loader errors.

6. Recovery Path B — Recover the Panel Image: ProSave OS Update

Use this path when the panel image is corrupted but the bootloader is still responsive to ProSave. The panel's own service tools can reflash the image without returning the unit to the factory.

6.1 Prerequisites

• SIMATIC ProSave version that matches the panel image (do not mix V13 and V14 service tools against a V14 image — use the matching TIA or ProSave installer).
• Ethernet crossover or direct connection (panel and PC on the same /24 subnet, no managed switch in between).
• The panel's .img firmware file. For V13 SP1, this is typically located in the TIA Portal install tree under Siemens\Automation\Portal V13 SP1\Data\Hmi\Transfer\13.0.1.0\Image or supplied with the panel's support package.
• Stable, conditioned power to the panel — connect the panel to a UPS or otherwise guarantee no interruption for the full duration of the transfer (typically 8–15 minutes for a TP1200).

6.2 Step-by-Step

1. Launch ProSave as Administrator (Windows) or with equivalent rights (Linux/Wine is not supported).
2. Select Device type: "TP1200 Comfort".
3. Set the Connection to "Ethernet" and enter the panel's IP (default 192.168.0.2 if untouched).
4. Click "Connect". If connection fails, the bootloader is unreachable; proceed to section 7.
5. Switch to the "OS Update" tab.
6. Browse to the panel-specific .img file. Confirm the file is the exact match for the panel variant — flashing a TP1500 image onto a TP1200 will render the panel unbootable.
7. Set the option to "Reset to factory settings" unless the goal is to preserve the existing project (in which case the active project is preserved and only the runtime binaries are refreshed).
8. Click "Execute update". The panel will display "Update in progress — do not power off".
9. Wait for the panel to reboot automatically. Do not close ProSave until the operation reports "Update successfully completed".

6.3 Verification

• Panel restarts and shows the standard "SIMATIC HMI" splash, then the loader screen, then either a trial-mode banner or the last loaded project.
• ProSave → "Device information" reports the new image version.
• Touch calibration: tap through the loader's calibration routine to confirm the touch controller is functional.

7. Recovery Path C — Bootloader-Level Recovery

If ProSave cannot connect, the bootloader is intact but the runtime is severely corrupted (or vice versa). Attempt the following in order:

1. Power cycle with extended off-time. Disconnect power for 30 s, restore, observe. The panel performs a cold-boot diagnostic that sometimes clears transient bad-block mappings.
2. Force transfer mode. On the TP1200 Comfort, hold the "Service" button (behind the front bezel) while powering on, or trigger transfer mode via the loader menu if reachable. This switches the panel into a state where it accepts a fresh image via ProSave on a fixed IP without a project present.
3. Try the Siemens recovery FAQ. Follow the step-by-step procedure in the official Siemens support FAQ SIMATIC HMI Panels: How do you update or restore the operating system? — this entry documents the exact button combinations, service-cable pin-outs, and image-file locations for Comfort Panels.
4. Escalate to Siemens Technical Support. If all of the above fail, the panel has likely suffered a hardware-level NAND failure or bootloader corruption that requires factory reflash or mainboard replacement. Open a support request via the Siemens Industry Online Support portal with the panel's serial number, MLFB, and a full description of the diagnostic steps already attempted.

8. Field-Proven Caveats

• Do not downgrade across major TIA versions. A V14 image cannot be installed with a V13 ProSave, and vice versa. A downgrade in the field typically bricks the loader.
• Watch the SD card slot. TP1200 Comfort panels accept an SD card that the loader will scan at boot. A corrupt SD card with an invalid project can produce the splash + cursor symptom. Remove the SD card and re-test before opening a return case.
• Touch calibration can survive a bad image. A panel stuck at the splash may still be touch-responsive in the loader layer. Use this to access the loader menu even if the runtime never starts.
• License keys are stored on the panel, not the image. An OS update does not wipe the license; only an explicit "Reset to factory settings" combined with a license wipe operation does. Verify the license is present after any recovery.
• Static IP for the service PC is mandatory. ProSave does not negotiate with DHCP; if the service PC is on DHCP, the connection will time out even when the panel and PC are physically wired correctly.
• Time the recovery. A full TP1200 image transfer is 8–15 minutes. A 3-minute "Update in progress" screen followed by the splash returning usually means the image file was wrong, not that the transfer was interrupted.

9. Preventive Measures

1. Back up the panel after every project change using ProSave → "Backup" before any new download. Store the backup off-line (network share, versioned repository).
2. Pin the engineering version. Use TIA Portal's project version stamp and refuse to open a project on a workstation that would auto-upgrade it. Configure a TIA portal-wide project version policy in the engineering team.
3. UPS the HMI cabinet. A short power loss during a download is the most common cause of image corruption in the field.
4. Document the panel's image version on a label or in the asset record, and verify it against the engineering project before any field service visit.
5. Keep an SD card with a known-good image on site for the critical panels. Some Comfort Panel variants can be brought back by booting from a properly authored SD card if the on-board image is corrupted.

10. Frequently Asked Questions