S7-300 314C-2DP All LEDs Blinking: MMC Reset & Recovery Guide

The SIMATIC S7-300 CPU 314C-2DP is a compact controller that integrates a CPU, digital I/O, and a PROFIBUS-DP master/slave interface into a single unit. When all front-panel status LEDs (SF, BF, DC5V, RUN, STOP) begin flashing simultaneously after a power cycle or program download, the controller is signalling a hardware/firmware defect, a missing or unrecognised Micro Memory Card (MMC), or a corrupted firmware image. This guide provides the diagnostic sequence and step-by-step recovery procedure that returns the CPU to STOP or RUN without re-flashing.

1. Affected Hardware and Firmware Versions

The phenomenon is documented across multiple order numbers of the 314C-2DP family:

The MMC is mandatory on every S7-300 CPU from the 31xC series onward. Without an MMC inserted, the CPU performs a firmware self-test that ends with all LEDs blinking to indicate that no loadable firmware image was located.

2. LED Pattern Reference

The 314C-2DP front panel groups its indicators into three functional clusters. A simultaneous blink of every LED in the cluster differs from a steady ON state and from a slow/steady blink of an individual LED.

When every LED blinks together at the same 1 Hz cadence and the MAINT LED also flickers whenever an MMC is inserted, the firmware has classified the system as defective and refused to leave the self-test phase. Per the SIMATIC S7-1200/300 manual collection, this is the documented signature of an MMC read error or a corrupted internal flash image.

3. Root Cause Analysis

Three primary root causes produce the simultaneous-blink symptom on a 314C-2DP:

1. Missing or unrecognised MMC. The S7-300 C-CPUs cannot boot without an MMC. A blank MMC formatted by Windows is not bootable.
2. Corrupted MMC content. A partial write during a download, an ejected card mid-transfer, or a power loss during the previous STOP → RUN transition can corrupt the FAT and the S7 image headers.
3. Firmware / hardware defect. Internal flash, RAM, or the MMC socket has failed. The firmware detects this on POST and freezes the CPU in the all-blink state.

Contributing factors reported in field service tickets:

• An analog module (e.g., SM 334 AI4/AO2 12-bit) inserted between the CPU and a digital module without 24 V on the analog module's load supply. The 314C-2DP performs a backplane ID check; an under-powered analog module returns a module diagnostic that, when combined with a missing MMC, escalates to the all-blink state.
• STEP 7 V5.4 / V5.5 download aborted by unplugging the MPI cable or by an ES timeout.
• MMC with file system written by a third-party card reader instead of the CPU itself.

4. Diagnostic Sequence

Before performing a destructive reset, capture as much information as the CPU will surrender.

4.1 Try to Read the Diagnostic Buffer

Even when SIMATIC Manager > Accessible Nodes reports no node, attempting an online connection sometimes succeeds during the brief boot window. Launch SIMATIC Manager and select PLC > Diagnostics/Setting > Diagnostic Buffer. The diagnostic buffer is non-volatile and survives the all-blink state on most firmware versions. Look for entries with Event ID 0x13A1 (MMC read error), 0x4542 (firmware update failed), or 0xE002 (hardware defect).

4.2 LED Cadence Decoding

Power-cycle and observe the very first 5 seconds:

• MAINT flashes twice at power-up, then everything blinks: MMC inserted but not readable. Try a known-good card.
• All LEDs blink immediately with no MAINT pulse: MMC slot not seeing a card, or card socket damaged.
• STOP stays steady, others flash: CPU halted in self-test, recovery possible via MRES.

4.3 Verify the Analog Module Load Voltage

If the analog module is the SM 334 (6ES7334-0CE01-0AA0), measure the 24 V supply at terminals L+ and M on the analog module's front connector. The load voltage is required even when no analog inputs are used in the program; the backplane diagnostic on the 314C-2DP will declare a module error otherwise.

5. Recovery Procedure

Proceed in this order. Stop at the first step that restores the CPU.

Step 1 — Power Cycle with a Known-Good MMC

1. Power OFF the rack.
2. Remove the existing MMC.
3. Insert an MMC that has been previously written by an S7-300 CPU (not formatted by Windows).
4. Power ON and wait 60 seconds. Observe LEDs.
5. If the CPU reaches STOP (STOP LED steady, others OFF), proceed to Step 5 (download project).

Step 2 — Memory Reset (MRES) on the CPU

1. Set the mode switch to STOP.
2. Hold the MRES button for at least 3 seconds until the STOP LED blinks twice, then release.
3. Within 3 seconds, press MRES again and hold until the STOP LED blinks rapidly.
4. Release. The CPU performs a full memory reset and copies a fresh boot image from the MMC.

Step 3 — Erase and Re-write the MMC

1. Insert the suspect MMC into a PC card reader.
2. Open SIMATIC Manager > PLC > Memory Card > Erase Memory Card. This formats the card with the S7 file system, not FAT32.
3. Reinsert the MMC into the powered-OFF CPU.
4. Power ON and observe the LEDs. If the CPU stops blinking, the MMC was the failure point.

Alternative manual procedure using the PG:

1. Connect the PG via MPI to the CPU.
2. Select PLC > Memory Card > Copy RAM to ROM to write a fresh working image to the MMC.
3. Power-cycle the CPU.

Step 4 — Re-flash the Firmware

When Steps 1-3 fail, the internal flash image is suspect. Re-flash using the Siemens FW Update Tool from the S7-300 Automation & Drives service pack:

1. Download the firmware update package matching the MLFB (e.g., 6ES7314-6CH04-0AB0 V3.4.6).
2. Place the CPU in STOP.
3. Connect via MPI/DP.
4. Launch the FW Update Tool, select the CPU, browse to the .upd file, and click Update.
5. Wait until the tool reports Update successfully completed. Do not power-cycle during the write phase.

The firmware update is the last software-based recovery. If the all-blink state persists, the CPU's MMC socket or internal flash is physically damaged and the unit must be replaced.

Step 5 — Re-download the Project

After the CPU returns to STOP:

1. Open the project in SIMATIC Manager.
2. Select PLC > Download.
3. When prompted, choose Download to Memory Card to mirror the project onto the MMC, or Download to Target Device to keep the working copy in RAM.
4. Switch the mode selector to RUN. The STOP LED must extinguish and the RUN LED must illuminate steady.

6. MMC Size and Type Compatibility

Not every MMC works in every S7-300 CPU. Use the table below to validate a spare card.

Third-party SD-to-MMC adapters are not supported on S7-300. Only genuine Siemens MMCs (order prefix 6ES7953-8L) or pre-formatted industrial-grade cards from approved vendors are guaranteed to be recognised by the firmware's POST.

7. Analog Module SM 334 Considerations

The 314C-2DP supports hot-swappable S7-300 SM modules. The analog module referenced in the field case (AI5/AO2 12-bit) is the SM 334 with order number 6ES7334-0CE01-0AA0 (4 AI / 2 AO, 12-bit resolution).

Wiring Requirements

• 24 VDC load supply at terminals 1L+ and 1M is mandatory, even when no analog channel is configured in the STEP 7 hardware configuration.
• Wire 2L+ and 2M are the sensor supply; not required for the boot sequence but required for any AI channel.
• Unused AI channels must be shorted at the channel terminals (signal to Mana) or declared as deactivated in the STEP 7 hardware configuration.

Diagnostic Buffer Entries

A missing 24 V load supply on the SM 334 generates Event ID 0x0E01 in the diagnostic buffer with the slot number. This entry alone does not put the CPU in the all-blink state, but combined with a missing or corrupted MMC, the CPU can latch the fault into the firmware defect handler.

8. Verification

Confirm successful recovery with the following checklist:

1. LED pattern. STOP LED steady ON, RUN LED OFF. SF and BF must be OFF. MAINT may briefly pulse during MMC read but must extinguish within 30 seconds.
2. SIMATIC Manager accessible nodes. The CPU must appear with its MPI address and diagnostics must be retrievable.
3. Diagnostic buffer clean. Read the buffer and confirm no Event ID between 0x13A0 and 0x13FF (MMC faults) and no 0x45xx (firmware faults).
4. Project download. Download the original hardware configuration and program. Verify the OB1 cycle time on the CPU's online diagnostic view.
5. Mode switch. Toggle to RUN. RUN LED must illuminate within 5 seconds with no SF, BF, or MAINT.
6. Persistent storage. Perform PLC > Copy RAM to ROM to ensure the working project is mirrored on the MMC.

9. Preventive Measures

• Always insert or remove the MMC with the rack powered OFF. Hot-swap is not supported on the 31xC series.
• Use Siemens MMCs only. Third-party cards pass the physical insertion test but fail the POST firmware signature check on random reads.
• Format MMCs only through SIMATIC Manager. Windows formatting writes FAT32 or exFAT, neither of which is recognised by the S7 firmware.
• Power-cycle after every program download. Some STEP 7 versions defer the firmware signature write until the next STOP → RUN transition.
• Keep a spare MMC with a known-good image on hand. A pre-written MMC containing the latest project shaves hours off recovery time during commissioning.

10. When to Replace the CPU

Replace the 314C-2DP module if any of the following applies:

• All-LEDs blink persists after Step 4 (firmware re-flash) with two different known-good MMCs.
• Diagnostic buffer reports Event ID 0xE002 (internal hardware error) repeatedly.
• The MMC slot shows physical damage, bent contacts, or the card does not click into place.
• The CPU is more than 10 years old and has logged repeated STOP/RUN transitions due to power quality.

Order the replacement as the identical MLFB plus a -Z variant (e.g., 6ES7314-6CH04-0AB0 Z) for the conformal-coated version when the cabinet environment is humid or corrosive.

11. Quick Reference: Recovery Decision Tree

12. Diagnostic Buffer Reference

13. Cross-Reference: S7-1200 vs S7-300 LED Behaviour

The blinking-LED pattern is consistent across the S7 platform. Per the SIMATIC S7-1200 manual collection, the S7-1200 CPU reacts to a defective firmware image by blinking every status LED at 1 Hz, identical to the S7-300 314C-2DP. The MAINT LED on S7-1200 also flickers when an SD card is inserted. The recovery procedure on S7-1200 differs in that the SD card can be erased directly from the TIA Portal without removing the card, while the S7-300 requires either MRES or SIMATIC Manager's Memory Card > Erase function.