• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 238 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLPC230-Q1: CMD Error (0xD7) - System must stay in Standby mode until reset has occured.

Wayne Pincence
Prodigy 30 points
Part Number: DLPC230-Q1
Other Parts Discussed in Thread: DLP5530Q1EVM,

Tool/software:

We have a design that uses the DLPC230-Q1, which is mostly based on the DLP5530Q1EVM.

Many of our boards fail to function after programming, and when I try to troubleshoot the problem, they seem to be stuck in a loop with this error:

Failed to complete system reset.
Short status Error details:
   Error Flags : CMD
   Error Code : Command Error (0xD7) - System must stay in Standby mode until reset has occurred.
Error History Info:
   Title: Error code : 0xD7
   Category: CMD
   Informational Bits: 0x6F00
   Raw Bytes in hex (big-endian): 20 D7 6F 00

What is interesting is that this is in response to attempting to reset from DLPC230 Control Program.

Here is the full command log from pressing the reset button in DLPC230 Control Program.

02/24/2025 10:37:27.1649 AM Host Cheetah SPI Read Short Status Read C0 7B 00 93 FF C0 7B 04 41 79 D7 20 02
02/24/2025 10:37:27.1659 AM Host Cheetah SPI Read Error History (Prefetch) Write 01 7C 01 C1 06 FF 01 7C 00 1E
02/24/2025 10:37:27.1669 AM Host Cheetah SPI Read Short Status Read C0 7D 00 ED FF C0 7D 04 49 7C D7 20 84
02/24/2025 10:37:27.1699 AM Host Cheetah SPI Read Activate Read 02 7E 00 89 FF 02 7E 02 F9 00 74 01 00 79 D7 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3D
02/24/2025 10:37:27.1709 AM Host Cheetah SPI Read Short Status Read C0 7F 00 C7 FF C0 7F 04 41 7C D7 20 66
02/24/2025 10:37:27.1729 AM Host Cheetah SPI Write Clear Error History Write C3 80 04 AA BB CC DD E7 FF C3 80 00 AD
02/24/2025 10:37:27.1739 AM Host Cheetah SPI Read Short Status Read C0 81 00 05 FF C0 81 04 41 80 00 00 47

We have several thousand boards with no problems, so it shouldn't be a design issue.  If I remember correctly, replacing the flash chip on boards has resolved the problem in the past, so my only guess is something is corrupt in the flash data.  I did compare a board with the problem, and a board without the problem, and all the flash block CRCs as read in DLPC230 Control Program match.

  • 0
    Prodigy 30 points

    If I don't have logging for Short Status turned on, it looks a lot different.

    02/24/2025 10:45:31.2396 AM Host Cheetah SPI Write System Reset Write 00 7F 04 AA BB CC DD E1

    FF 00 7F 00 4A

    It almost seems like the Control Program won't actually send the reset command because it sees the error flag in the short status.  Even though the fix for the error flag is to do a reset.

  • 0 in reply to Wayne Pincence
    Prodigy 30 points

    I just found some more errors on boards with this problem.

    On first powerup, if I read the Error History, I get this:

    1 636 DMD low speed interface communication failed. The ASIC did not receive an ACK from the DMD. This can occur if there is a DMD connection issue, or if the flash low speed port configuration does not match hardware connections. Operational 000 000 124 066

    I am not sure if the line "if the flash low speed port configuration does not match hardware connections" is really referring to the flash, or something different.

  • 0 in reply to Wayne Pincence
    TI__Expert 3625 points

    Hello Wayne,

    Thank you for reaching out to us.

    It looks like the configured DMD interface in the Composer project does not match the actual DMD lane mapping. If this configuration matches, then the DMD might not be seated correctly on the interposer.

    Thank you,

    Regards,
    Aishwarya

  • 0 in reply to Aishwarya K Aithal
    Prodigy 30 points

    The DMD is definitely seated properly.  I can't rule out soldering of the socket or the DLPC230 however.

    It shouldn't be a channel swapping issue, we program every board with the same BIN file.

    Unfortunately, because of the way the PCB is designed, we have no real way to verify most of the connections from the DLPC230 to the socket.

    It sounds like these boards will likely just be assembly failures, I was just hoping there might be a software issue instead.  But now that I have seen the 636 error code on power up on multiple boards with the same symptom, I believe it must be an open somewhere on the LS signals.

  • 0 in reply to Wayne Pincence
    TI__Expert 3625 points

    Wayne,

    That's unfortunate. Let us know if you would need any other help.

    Thank you,

    Regards,
    Aishwarya