• 状态 Resolved
  • 已锁定 已锁定
  • 个回复 14 个回复
  • 名订阅用户 0 名订阅用户
  • 次查看 143 次查看
  • 用户 0 名在线用户
选项
选项
相关

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.

[参考译文] DLP471TEEVM：DMD 错误(DMD 不工作)

admin
Guru**** 657930 points
Other Parts Discussed in Thread: DLP471TE, DLPC7540
请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/dlp-products-group/dlp/f/dlp-products-forum/1217119/dlp471teevm-dmd-error-dmd-not-working

器件型号：DLP471TEEVM
主题中讨论的其他器件：DLP471TE、 DLPC7540

尊敬的 TI 支持团队：

我希望你们都做得很好，因为我需要你们的帮助。
我们已经有一段时间装有 DLPC7540电路板的 TI DLP471TE EVM 了、直到最近、他们仍然能够正常工作。
两天前、DMD 未显示任何内容、甚至未显示开始屏幕。 我已尝试解决此问题、并已执行以下步骤：
1、以不同的配置交换所有的电缆,以测试电缆是否工作(不同的 USB 电缆,不同的 HDMI 电缆,也 因为我有3个跳线我互换他们)
2.检查电源(工作正常,提供所需的电流和电压)
3.不仅尝试在外部显示模式下运行,还尝试运行图形或图像
4.已重新安装固件(按照手册中的步骤进行操作-在重新启动后移动引导跳线并再次将其移回)
5.测量了 DMD 电路板上的测试点(3.3V 和 DMD VDD)-两者都起作用
6.已检查 DMD 本身的引脚-它们都正常
控制器电路板上亮起的指示灯：D5、D7、D25 -恒定绿色；D15 -闪烁绿色；D6 -恒定红色。 此外、所有电路板(DMD、控制器、HDMI)看起来都正常、没有电子元件烧毁的迹象。

我已随附图片、其中显示了在 GUI 和高级 GUI 中标记为已选中的错误(未显示其他复选标记)：


DMD (到目前为止)已在广泛波长的照明条件下并符合规范。

您能帮我解决这个问题吗？
我期待您的回复！

提前感谢！

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    您可以尝试检查控制器板与 DMD 板之间线路的连接性。 另外、还要尝试确保两者连接牢固

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    感谢您的回复和建议! 我已检查连接电缆的导通性、它们都工作正常。 它们之间的连接非常牢固-引脚未磨损、并且保持稳定。 此外、我想我无法读取 DMD 板测试点的电压、倘若这些电缆是问题所在。 我还想到其他什么吗？ 再次感谢！

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    您是否绑定了换 DMD？

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    这是一个伟大的想法,但不幸的是,我们只有这一个:/...

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    尊敬的 Dimitar：

    我们将在结束时研究此问题、并会在接下来的几天内与您联系。 感谢您的耐心。

    此致！

    Maxine

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    请尝试使用 USB 到串行转换器查看 J102的串行输出

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    您好！

    很抱歉回复延迟、但我们不得不等待 USB 转串行转换器电缆。
    我使用了 Wireshark 来检测器件之间通过串行 J102端口交换的一些信息：

    对我来说、好像发送了一些配置数据。 我已在此处附上捕获的软件包文件：

    https://drive.google.com/file/d/1DFmBmDQZjeqVvtYuhilHAhMqyax2Gj50/view?usp=sharing

    期待您的回复！

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    已申请对这些文件的访问权限

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    您需要在串行终端中打开一个 COM 端口、此端口应在您插入 USB-Serial 时填充。

    我将 Teraterm： https://ttssh2.osdn.jp/index.html.en 用作串行终端

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    您好！ 好的、我会这样做、并尽快报告。 谢谢！

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    因此、使用 TeraTerm 的 Serial J102只显示了我发送的命令。 以下是一个会话的快照：


    我认为另一个会话显示了错误(可能是 DMD 电源问题？)： 


    Command 0x0 execution took 52 us (greater than allowed 50 ms)
Command 0x11 execution took 77 us (greater than allowed 50 ms)
Command 0x0 execution took 56 us (greater than allowed 50 ms)
Command 0x11 execution took 77 us (greater than allowed 50 ms)
Command 0x22 execution took 205 us (greater than allowed 50 ms)
Command 0x21 execution took 117 us (greater than allowed 50 ms)
Command 0x26 execution took 65 us (greater than allowed 50 ms)
Command 0x11 execution took 86 us (greater than allowed 50 ms)
Command 0x22 execution took 189 us (greater than allowed 50 ms)
Command 0x21 execution took 87 us (greater than allowed 50 ms)
Command 0x26 execution took 56 us (greater than allowed 50 ms)
gui: GUI event 2 (parm = 4)
gui: GUI event 2 (parm = 0)
Command 0x21 execution took 122 us (greater than allowed 50 ms)
Command 0x11 execution took 82 us (greater than allowed 50 ms)
Command 0x11 execution took 69 us (greater than allowed 50 ms)
Command 0x900 execution took 182 us (greater than allowed 50 ms)
Command 0x913 execution took 161 us (greater than allowed 50 ms)
Command 0x11 execution took 77 us (greater than allowed 50 ms)
Command 0x11 execution took 53 us (greater than allowed 50 ms)
Command 0x11 execution took 82 us (greater than allowed 50 ms)
Command 0x22 execution took 205 us (greater than allowed 50 ms)
Command 0x21 execution took 105 us (greater than allowed 50 ms)
Command 0x26 execution took 65 us (greater than allowed 50 ms)
gui: GUI event 2 (parm = 4)
dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 3, dispSrc = 0
dispfmt: DISP_SetDisplay failed (ret=-101)
         CroppedArea = { 0, 0, 3840, 2160 }
         DisplayArea = { 0, 0, 3840, 2160 }
DISP_SetDisplay return value = 0
Command 0x21 execution took 97701 us (greater than allowed 50 ms)
Command 0x913 execution took 810 us (greater than allowed 50 ms)
Command 0x11 execution took 103 us (greater than allowed 50 ms)
Command 0x11 execution took 341 us (greater than allowed 50 ms)
Command 0x11 execution took 187 us (greater than allowed 50 ms)
Command 0x22 execution took 213 us (greater than allowed 50 ms)
Command 0x21 execution took 113 us (greater than allowed 50 ms)
Command 0x26 execution took 60 us (greater than allowed 50 ms)
gui: GUI event 2 (parm = 4)
dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 3, dispSrc = 0
dispfmt: DISP_SetDisplay failed (ret=-101)
         CroppedArea = { 0, 0, 3840, 2160 }
         DisplayArea = { 0, 0, 3840, 2160 }
DISP_SetDisplay return value = 0
Command 0x21 execution took 93902 us (greater than allowed 50 ms)
Command 0x90E execution took 771 us (greater than allowed 50 ms)
Command 0x11 execution took 94 us (greater than allowed 50 ms)
Command 0x11 execution took 90 us (greater than allowed 50 ms)
Command 0x11 execution took 69 us (greater than allowed 50 ms)
Command 0x22 execution took 193 us (greater than allowed 50 ms)
Command 0x21 execution took 83 us (greater than allowed 50 ms)
Command 0x26 execution took 73 us (greater than allowed 50 ms)
gui: GUI event 2 (parm = 4)
dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 3, dispSrc = 0
dispfmt: DISP_SetDisplay failed (ret=-101)
         CroppedArea = { 0, 0, 3840, 2160 }
         DisplayArea = { 0, 0, 3840, 2160 }
DISP_SetDisplay return value = 0
Command 0x21 execution took 96484 us (greater than allowed 50 ms)
Command 0x906 execution took 728 us (greater than allowed 50 ms)
Command 0x11 execution took 94 us (greater than allowed 50 ms)
Command 0x11 execution took 64 us (greater than allowed 50 ms)
Command 0x11 execution took 86 us (greater than allowed 50 ms)
Command 0x22 execution took 202 us (greater than allowed 50 ms)
Command 0x21 execution took 105 us (greater than allowed 50 ms)
Command 0x26 execution took 60 us (greater than allowed 50 ms)
gui: GUI event 2 (parm = 4)
dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 3, dispSrc = 0
dispfmt: DISP_SetDisplay failed (ret=-101)
         CroppedArea = { 0, 0, 3840, 2160 }
         DisplayArea = { 0, 0, 3840, 2160 }
DISP_SetDisplay return value = 0
Command 0x21 execution took 90877 us (greater than allowed 50 ms)
Command 0x90C execution took 848 us (greater than allowed 50 ms)
Command 0x11 execution took 103 us (greater than allowed 50 ms)
Command 0x11 execution took 61 us (greater than allowed 50 ms)
Command 0x11 execution took 82 us (greater than allowed 50 ms)
Command 0x22 execution took 184 us (greater than allowed 50 ms)
Command 0x21 execution took 96 us (greater than allowed 50 ms)
Command 0x26 execution took 56 us (greater than allowed 50 ms)
gui: GUI event 2 (parm = 4)
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 3, dispSrc = 0
dispfmt: DISP_SetDisplay failed (ret=-101)
         CroppedArea = { 0, 0, 3840, 2160 }
         DisplayArea = { 0, 0, 3840, 2160 }
Command 0x11 execution took 54517 us (greater than allowed 50 ms)
dispfmt: Image Size Limits minWidth:640 Width:3840 maxWidth:3840; minHeight:480 Height:2160 maxHeight:2160
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 3, dispSrc = 0
dispfmt: DISP_SetDisplay failed (ret=-101)
         CroppedArea = { 0, 0, 3840, 2160 }
         DisplayArea = { 0, 0, 3840, 2160 }
DISP_SetDisplay return value = 0
Command 0x21 execution took 95055 us (greater than allowed 50 ms)
Command 0x907 execution took 713 us (greater than allowed 50 ms)
Command 0x11 execution took 103 us (greater than allowed 50 ms)
Command 0x11 execution took 52 us (greater than allowed 50 ms)
Command 0x11 execution took 86 us (greater than allowed 50 ms)
Command 0x22 execution took 193 us (greater than allowed 50 ms)
Command 0x21 execution took 117 us (greater than allowed 50 ms)
Command 0x26 execution took 56 us (greater than allowed 50 ms)
Command 0x21 execution took 81 us (greater than allowed 50 ms)
Command 0x1C execution took 56 us (greater than allowed 50 ms)
Command 0x11 execution took 82 us (greater than allowed 50 ms)
Command 0x11 execution took 53 us (greater than allowed 50 ms)
Command 0x100B execution took 56 us (greater than allowed 50 ms)
Command 0x1E execution took 74 us (greater than allowed 50 ms)
Command 0x1F execution took 69 us (greater than allowed 50 ms)
Command 0x11 execution took 69 us (greater than allowed 50 ms)
Command 0x11 execution took 57 us (greater than allowed 50 ms)
Command 0x6 execution took 140 us (greater than allowed 50 ms)
Command 0x1 execution took 87 us (greater than allowed 50 ms)
Command 0x0 execution took 73 us (greater than allowed 50 ms)
Command 0x1 execution took 132 us (greater than allowed 50 ms)
Command 0x11 execution took 69 us (greater than allowed 50 ms)

----------------------------------------
Debug opened on URT0
I2C Port 1 initialized as Master port
I2C Port 2 initialized as Master port
I2C Port 0 initialized as Slave port
eeprom: Content validated
Cal data block CWLamp not in EEPROM : Using data from flash
Cal data block SSI present in EEPROM. Data version = 0
Cal data block ADC not in EEPROM : Using data from flash
Cal data block WpcSensor present in EEPROM. Data version = 4
Cal data block WpcBrightness present in EEPROM. Data version = 4
Cal data block XPR present in EEPROM. Data version = 4
Cal data block XPRWaveform not in EEPROM : Using data from flash
Cal data block EdgeBlend not in EEPROM : Using data from flash
Cal data block SurfaceCorrection won't fit in EEPROM : Using data from flash
Cal data block SurfaceCorrection not in EEPROM : Using data from flash
Cal data block BlendMap won't fit in EEPROM : Using data from flash
Cal data block BlendMap not in EEPROM : Using data from flash
API version: 4.5.0.0.0.0
App version: 4.5.0.0.0.0
usbIO: Debug Messges added at interface 1
usbIO: Keyboard Mouse added at interface 2
usbIO: USBD_Start DONE
usbIO: USBD_Listen started
sysmon: URT Cmd Handlerfailed to start
pca9539: Error - iox failure. APIcc = -7
IT6807 - Configuring IT680x...
digcontrol: Cfg complete
digcontrol: Decoder 2 powerStandby complete
digcontrol: Decoder 5 powerStandby complete
datapath: PowerStandby Complete..
sysmon: DLPA100 not present

illumination: Starting SSI Initialization...
  Configured SSI Driver Type = 0.
  Configuring sensor failed : -6.
  Initializing WPC configuration...
  SSI initialization failed.
illumination: Completed illum_Init
Sysmon: Transition to normal operating mode
  Initializing WPC Failed: -6
  Initializing WPC calibration data Passed...
  Initializing WPC Brightness Table Failed: 0
Environment:Temp Sensor Write Incomplete, returned fffffff9
*** gui: OSD_Init failure ***
datapath: autolock initialization passed
digcontrol.c : line - 194 : digcontrol_powerNormal()
iox_edid_init() failed
digcontrol: powerNormal failed
digcontrol.c : line - 194 : digcontrol_powerNormal()
iox_edid_init() failed
digcontrol: powerNormal failed
digcontrol: powerNormal complete
datapath: dig, adc, dec powerNormal
source: SetUserSFGColor = 1
9
 dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 1, dispSrc = 1
gui: GUI event 2 (parm = 4)
source: SPLASH address:  0x10526880
source: DisplaySplash size = 3840 x 2160
Blank screen is set to splash
dispfmt_CalculateDisplayArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt: minPan, pan, maxPan:0, 0, 0
         data = { 3840, 0, 3840 }
dispfmt: minScan, scan, maxScan:0, 0, 0
         data = { 2160, 0, 2160 }
dispfmt_CalculateCroppedArea:  X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt:apply_disp: activeSource = 2, dispSrc = 2

datapath: Transition to IDLING on Vx1(ITE0)
dispfmt_ConfigManualWarp(): LensCorrection enabled = 0
dispfmt_ConfigManualWarp: Config warping failed with error code -16
WarpValidateResult->InLinesPixOK = 1
WarpValidateResult->HCtrlOK = 0
WarpValidateResult->VCtrlOK = 1
WarpValidateResult->WrpPointsOK = 1
WarpValidateResult->FailRow = 0
WarpValidateResult->FailCol = 1
 Actuator EEPROM size - 6 (where 0 = 0.125k,1 = 0.25k,2 = 0.5k,3 = 1k,4 = 2k,5 = 4k,6 = 8k)

 [Actuator Type]: 128   [AWC WG Auto-Offset]: 0

 Actuator Type: 128   Unipolar: 0
 XPR Param in EEPROM: MAtch Signature
XPR 4 Way Orientation number: 22
XPR: Act subframe order: 0 3 1 2
 XPR_4WAY_TIActGetActuatorData(): Read from EEPROM failed
 XPR_4WAY_TIActGetActuatorData(): Read from actuator failed!!!
datapathf: XPR_4WAY_Init Failed
Illumination: Transition to operating mode
illumination: DMD LSIF comm error in DMD_Power()
illumination: Can't set up DMD
sysmon: Fault in illumination transition to operating mode
sysmon: Sysmon can't transition to operating mode
gui: GUI event 4 (parm = 0)
gui: executing OnOSDClose
illumination: Transition to standby
illumination: Disabling SSI Illuminators.
illumination: API WARNING - SEQ_POWER_DOWN_REFRESH_NOT_USED on Fusion DMD
sysmon: _sysStandby - Transition
omplete
by
sysmon.c : line - 741 : _sysReset()
_sysNormalRun() failed
sysmon: Init Complete
Command 0x0 execution took 60 us (greater than allowed 50 ms)
Command 0x11 execution took 90 us (greater than allowed 50 ms)
Command 0x0 execution took 73 us (greater than allowed 50 ms)
Command 0x11 execution took 86 us (greater than allowed 50 ms)
Command 0x22 execution took 223 us (greater than allowed 50 ms)
Command 0x21 execution took 108 us (greater than allowed 50 ms)
Command 0x26 execution took 60 us (greater than allowed 50 ms)
pctlCommands: switching to external source
Command 0x11 execution took 7634 us (greater than allowed 50 ms)
Command 0x21 execution took 100 us (greater than allowed 50 ms)
Command 0x11 execution took 69 us (greater than allowed 50 ms)
Command 0x11 execution took 52 us (greater than allowed 50 ms)
Command 0x11 execution took 77 us (greater than allowed 50 ms)
Command 0x22 execution took 172 us (greater than allowed 50 ms)
Command 0x21 execution took 106 us (greater than allowed 50 ms)
Command 0x26 execution took 60 us (greater than allowed 50 ms)

    期待您的回复！

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    我有点怀疑："照明：DMD_Power ()中的 DMD LSIF 通信错误"、

    这使我确信低速接口上有一条线或一个引脚损坏。 您能否特别检查这些线路以确保信号通过？

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    再次你好。 我使用 Tektronix TBS2000系列数字示波器(70 MHz、1 GS/s)进行测量(这是我们唯一使用的示波器)。 我不确定它是否可以测量这些信号、或者我是否测量错误。 除了 LS_RDATA_A_BIST_A -引脚 T13之外、我肯定会从您提到的几乎所有引脚/线路(LS_CLK_P -引脚 R9、LS_CLK_N -引脚 R10、LS_WDATA_P -引脚 T10、LS_WDATA_N -引脚 T11)中看到有一些 mV 的突变(~150至200)。 T13的物理位置不在我测量其他信号的背面。 下面是一些测量值和 DMD 引脚以及背面缺失的 T13图片。 蓝色线缆连接到主板的 GND。

    很遗憾、我不确定它是否能轻松解决。
    我们正在进行研究、我们的项目现已搁置14天以上。
    我们的供应商(Digikey)已完成此故障排除会话、并告诉我们、要将保修付诸行动、我们必须得出某种结论。 您是否认为此案例符合更换条件、以及我们是否可以采取其他措施来尝试修复此问题、修复时间不会超过1-2天、因为我们无法承受损失更多的时间？
    期待您的答复,并感谢到目前为止的善良的帮助!

  • 0
    TI__Guru**** 657930 points
    请注意，本文内容源自机器翻译，可能存在语法或其它翻译错误，仅供参考。如需获取准确内容，请参阅链接中的英语原文或自行翻译。

    您可以在此处查看是否有资格获得替换： https://www.ti.com/support-quality/additional-information/customer-returns.html?keyMatch=CUSTOMER%20SUPPORT%20CENTER