DLPC7540EVM: Can only connect to board in boot loader mode

Hello Alex,

This has been assigned.  You should receive a reply in the next day or so.

Fizix

Hello Alex,

Have you tried following the 'Troubleshooting' section (2.5) of the DLPC7540EVM User's Guide?

Best,

Aaron

Hi Aaron,

Yes, I've tried the steps mentioned in the troubleshooting section but no luck unfortunately.

Hello Alex,

Please advise what version of the software are you using as well as what DMD you are connecting with?

When you go to manually connect the board and you select USB, the EVM is not selectable, is that correct? Is the board powered up at the time?

Best,

Aaron

Hi Aaron,

I'm using GUI version 3.2.0.6 with DMD DLP650TE EVM.

That's correct that the EVM is not selectable, the dropdown menu is blank. However, when I go move the jumper and put the board in bootloader mode the software automatically detects the board and the software displays : "EVM Status: Connected, Bootloader Mode"

Hello Alex,

Thank you for confirming the version.

Last few things before I might need to get our software team involved. Can you send the 'Event Viewer'' log under the Debug tab of the GUI. Also, can you go to the advanced mode and try through the connection tab?

if you try and program anything to the board when not in debug mode, will anything be displayed in the Command Log?

Best,

Aaron

Hi Aaron, the Event Viewer log is empty and no luck connecting using the Advanced mode either, although it says the logging interface (UART com port) is working but the command interface is not - sure sure if that hints at anything.

If I try and program anything when not in debug mode, I get nothing in the Command Log and just a "Firmware Update Failed" in the event viewer.

Thanks,

Alex

Hey Alex,

Could you send a photo of how you have everything connected? I have a hunch but I'd like to see if there's anything else on the board.

Thanks,

Aaron

That's how it's currently all connected.

Hello Alex,

Let me discuss this with my software team about this.

Best,

Aaron

Hey Alex,

I noticed that the flex cable going to the front-end doesn't look like our front-end. Could you please advise if this is going to the provided daughter-card for the DLPC7540EVM?

If this is going to another front-end card, there might be something interfering with the communication.

Best,

Aaron

Hey Aaron,

I am using an FPGA to generate the video input. Unfortunately, the issue still persists when using the provided front-end HDMI to v by one board.

Alex

Hey Alex,

Thanks for the patience! It seems like you main application might be failing to load properly. Could you send the serial port debug log seen through the UART connection during a normal powerup, not debug/boothold mode? This will require an RS232 connection (J102) to USB cable.

I typically utilize TeraTerm as my serial port terminal to read back information. You'll have to set the port to a 115200 baud rate.

Best,

Aaron

Thanks,

I'll track down/purchase a serial to USB cable and get back to you with those logs.

Alex

Hey Alex,

I will keep this thread open and await your input.

As a quick note, some serial-to-USB connectors might also require drivers to be recognized by the PC.

Best,

Aaron

Here's a log from the device during boot:

----------------------------------------
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 - 5073 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  - 4400,
        TotalArea.LinesPerFrame  - 2250,
        ActiveArea.FirstPixel    - 384,
        ActiveArea.FirstLine     - 82,
        ActiveArea.PixelsPerLine - 3840,
        ActiveArea.LinesPerFrame - 2160,
        PixelClockFreqInkHz      - 594000,
        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: 3840 x 2160
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 = 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

Hey Alex,

There doesn't seem to be a reason why the system should lose communication.

I've reached out to the software team accordingly and they will follow up soon.

Best,

Aaron

Hello Alex,

Until I hear back from the software team, could you help me test that the the MicroUSB cable is functional by testing with a different cable? You previously mentioned you had tested this with a second system, but I'm not sure if that meant an additional cable was tested or not.

This should be a quick test, but I'm still checking with my team as well for ideas to investigate.

Best,

Aaron

Alex,

Additionally, could you help me understand what is being done to the board when you are going from recognized boothold mode to when you do not see the error?

Best,

Aaron

Hey Aaron,

Yes, I've tried a few different USB cables.

I see the error whenever powering up and the jumper is on J67. With the jumper on J9, the board is recognized in the GUI. I then power down the board (both switches off) and move the jumper back to J67 and power on (both switches on in the correct order) and the board is no longer recognized in the GUI - even if I close the GUI and restart the application.

Alex

Hey Alex,

Okay, so the hardware is not likely the issue. Please advise if the PC is the same you utilized. There are some on my team that have had issues with drivers. I wonder if those had not been manipulated with an update or not.

If this persists, we can hold a quick call to live debug this.

Best,

Aaron

Hello Alex,

I'm not sure if you were able to test this on another machine. Please advise as this might be as simple as a driver issue.

If this persists, again, I would be happy to hold a quick call.

Best,

Aaron

Hi Aaron,

After much investigation, I've been able to get it working but only on a Windows VM running under Linux. I had tried to completely remove the drivers and re-install but no luck there. My leading theory is that it's some sort of corporate IT policy on my windows machine that's stopping it from working correctly. IT are adamant that there's nothing that should be stopping it from working.

Either way I have a solution that's a little clunky but it mostly works for what I need it for.

Thanks,

Alex