PowerEdge T630 — CPLD update attempt (from 1.0.1 → 1.0.6) — signature verification failure (RED007)

Hello — I’m asking for help with a PowerEdge T630 that will not power on from the front panel or via iDRAC. Below is the timeline and actions I’ve taken so far:

1. System facts

   • Model: Dell PowerEdge T630

   • Current System CPLD version reported in iDRAC: 1.0.1

   • iDRAC version: 2.86.86.86 (example) / BIOS: 2.14.0 (both already updated)

2. Problem statement

   • The server does not respond to the front panel power button or iDRAC power-on commands.

   • I verified that the front panel switch pulls the 3.3V line to 0V, so the physical button signal reaches the board.

   • iDRAC produces no power-on logs — it is silent (no POST / no BMC boot). This behavior strongly suggests a CPLD-related power-sequencing issue.

3. Reason for CPLD update

   • T630 boards originally shipped with CPLD 1.0.1. Later CPLD updates (1.0.5 / 1.0.6) included fixes to power-sequence and iDRAC handshaking. Updating to CPLD 1.0.6 is expected to restore correct power-handshake behavior.

4. Files obtained and initial inspection

   • I obtained a Windows DUP package named CPLD_Firmware_PCON3_WN64_1.0.6_A00.exe.

   • Inside the package: payload/signed_HRZN_CPLD_106.jbc, cpldie.exe, hapi/ driver files, package.xml, etc. (This is a Windows HAPI-style package intended to be run on Windows.)

5. Attempts and adjustments performed locally

   • Because the target server cannot boot Windows, I could not run cpldie.exe on the target.

   • I attempted to locate an LC/iDRAC .hdr variant from archives (Wayback, FTP mirrors), but a T630 LC .hdr was not available publicly.

   • I edited the package manifest (package.xml) to add the T630 SystemID (0x0649 / sometimes 0602 in my investigation), so the DUP would be accepted as applicable to T630.

   • I created a self-extracting EXE (SFX) / rewrapped the expanded folder into an .exe and uploaded that to iDRAC / Lifecycle Controller.

6. iDRAC behavior and logs

   • iDRAC accepted the uploaded package: “Package successfully downloaded.”

   • The update job started and iDRAC logged the following sequence:

     • RED110 Downloading the ..._1.0.6_A00.exe update package

     • RED054 An update job JID_xxx was created

     • RED052 Processing of update packages is starting

     • RED007 Unable to verify Update Package signature

   • After the job, the server rebooted but the System CPLD version remained 1.0.1 — the CPLD write did not occur.

7. Interpretation so far

   • The iDRAC accepted the package and began processing, but signature verification failed and the actual JBC payload was not written.

   • This indicates the package was modified (manifest reworked / SFX rewrapped) and can reach the processing stage, but the device-side signature check still blocks the CPLD flash.

8. Attempts considered / fallback options

   • Request a signed LC/.hdr package from Dell support that is explicitly for PowerEdge T630 (the preferred, safe option).

   • Run cpldie.exe / write operation from a working Windows machine if possible (some Windows engines can continue with a signature warning).

   • Direct JTAG programming of the CPLD with Intel/Altera Quartus (USB-Blaster) and signed_HRZN_CPLD_106.jbc as a last-resort hardware recovery (I am prepared to do this if necessary).

9. What I can provide to Dell / support

   • iDRAC System Event Log entries (showing RED007) and the exact package file I used (if requested).

   • Board photos of the CPLD area and the test pad layout (for JTAG guidance).

10. Request

• Could Dell provide a signed CPLD update package for T630 (LC/iDRAC-compatible .hdr or a signed package that passes iDRAC signature verification), or advise on an official recovery path (repair or board-level service)?

Thank you for any help or pointers. I’m happy to provide logs, screenshots, or additional details on request.

— End of summary.