DLPC7540EVM: Problem where LED D6 lights up red when the power is turned on.

Hi there, the engineer in charge of this EVM and knows the answer is out of the office today.  I will ask him to check this issue in the morning US time tomorrow.

Sorry for the delay.

Hello Sasaoka,

The D6 LED is connected to DLPC7540 through GPIO #23. Per the Software Programmer's Guide, GPIO #23 is mentioned in section 4.8.

"4.8 Low-Level Fault: When the controller startup sequence encounters an error condition, the controller transitions to bootloader mode and sets GPIO_23 (connected to an LED) HIGH to indicate a low-level fault condition. See the debug message printed in the UART debug terminal or with the Get Boot Hold Reason command to get more details about the cause of error. When the Arm processor detects one of the data abort, pre-fetch abort or undefined instruction exceptions, it starts blinking GPIO_23 in specific hex code format. During this error condition, communication with the controller is not possible. The only way to communicate with the controller is to analyze the hex error code from the pattern and then debug the hardware to fix the issue."

Assuming only D6 is lit after SW5 and SW1 are turned on, the debug message printed in the UART debug terminal will give more details about the cause of error. 

Best,

Aaron

Hello Aaron,

I will tell you again that after SW5 and SW1 are turned on, only D6 will turn red and the others(D52 ,D5 ,D7 ,D15) will turn green.

Resends debug messages printed to the UART debug terminal.

Is there anything you can learn from this log?

*********************************************** log ***************************************************

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
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.
Sysmon: Transition to normal operating mode
Initializing WPC Failed: -6
Initializing WPC calibration data Passed...
Initializing WPC Brightness Table Failed: 0
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
source: SPLASH address: 0x10522d7c
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
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
SUCCESS: Product Configuration Valid, System Unlocked
Controller Info: Id = 0x01030059, Name = DLPC7540
DMD Info: DeviceId = 0x600D0096, FuseId = 0x00070008, FuseBitString = 00010000111111111, Name = DLP650TE_ECD_p65_UHD
illumination: Enabling SSI Driver...
sysmon: Transition to normal mode complete
sysmon: Completed _sysReset
sysmon: Init Complete
Startup Logo display time completed - 5098 milliseconds. Starting connector scan

------------------- SCANNING CONNECTOR : Vx1(ITE0) ----------------
Warning: No AFE1000/HW communcation found while attempting to place stand-by (However connector table seem to have a VGA entry)
IT6807 - iteState is ITE_POWERUP
digcontrol: Decoder 5 powerStandby complete

datapath: Transition to SCANNING on Vx1(ITE0)
digcontrol: ConfigureForSearch complete
Event: Source Change Detected on channel
Event: DSM Locked on channel
digcontrol: FillSourceConfig - srcConfig:
TotalArea.PixelsPerLine - 2200,
TotalArea.LinesPerFrame - 1125,
ActiveArea.FirstPixel - 192,
ActiveArea.FirstLine - 41,
ActiveArea.PixelsPerLine - 1920,
ActiveArea.LinesPerFrame - 1080,
PixelClockFreqInkHz - 148500,
inputFrameRate - 59,
srcColorType - RGB.
srcConfig->IsInterlaced - FALSE,
digcontrol: FillSourceConfig complete
Is3D = FALSE
dispfmt: DEI Disabled, Field Scaling Disabled
dispfmt: Input frame rate is 59Hz
dispfmt: input resolution: 1920 x 1080
dispfmt_CalculateDisplayArea: X, Y, Width, Height = 0, 0, 3840, 2160
dispfmt: minPan, pan, maxPan:0, 0, 0
data = { 1920, 0, 1920 }
dispfmt: minScan, scan, maxScan:0, 0, 0
data = { 1080, 0, 1080 }
dispfmt_CalculateCroppedArea: X, Y, Width, Height = 0, 0, 1920, 1080
dispfmt:apply_disp: activeSource = 0, dispSrc = 0
******* Try to set Color Profile 0 *******
pictcont: Active Display is 0
pictcont: Set White Peaking: 0
pictcont: Set gamma 0
pictcont: Sharpness 16
pictcont: cscIndex 0
pictcont: tableIndex 0

datapath: Transition to MONITORING on Vx1(ITE0)
gui: ccode 5 receiving GUI message

*********************************************************************************************

Best regards,

Sasaoka

Hello Aaron ,

You can't determine the cause of D6 turning red from the log I sent you last time can't you?

Our current situation is that we have connected the PC, EVM, Front-End, and DMD boards together and have confirmed using the GUI that the PC screen is displayed on the DMD and the LED enable and PWM signals are output to the connectors. However, it is 60Hz 4k.

What we are planning to do in the future is to prepare the original lighting and projection optics and LED drivers, dock them with the three DLP boards, and project the 240Hz 2k video input from the PC.

We cannot determine how this will affect our plans if we do not resolve this D6 LED issue. And we are concerned.

Please give me your opinion.

Best regards,

Sasaoka