Other Parts Discussed in Thread: DLP4710, , DLPA3005, TIDA-01226, DLPDLCR4710EVM-G2
I have a custom projector which uses the DLP4710, DLPA3005 and a pair of DLPC3439 controllers, similar to the TIDA-01226 ref design. There's no MSP430, HDMI receiver, or USB interface, a different micro is there to signal projector_on, monitor status pins, and talk I2C. Main power is 12VDC, and the interface voltage and flash voltage are both 3.3v. The mirror signals are wired according to option1. It will eventually have RGB24 parallel input, but for now those parallel input lines are all pulled down to ground with 7.8K resistors.
When the projector_on signal is given, the DLPA3005 produces the proper 1.1V, 1.8V, 2.5V and 3.3V rails, and the RESETZ, INTZ, and master and slave controller IRQ signals all go high, followed by a burst of activity (about 33msecs) on both of the controllers' flash SPI bus ports. Then nothing. The power rails that were up are still up and stable, but no other rails come up and the IRQ lines never fall. Nothing gets hot. If I remove the flash chips, they verify correctly in a programmer. Both controllers have a good stable clock from a shared oscillator, all 3 LEDs are present, the JTAG reset is pulled down on both controllers as in the reference design, and the SPI signals between master controller and power manager are pulled with same resistor arrangements as in the ref design.
As a further sanity check, I removed the DLP controllers and mirror device from one circuit board and wired a micro to the SPI bus connected to the DLPA3005. After signalling projector_on, I was able to easily access all its documented registers, which all started at the proper default values. That device seems to be behaving properly, and its SPI bus is clearly properly wired.
Could you please provide more information about what other things I should check, and whose failure would cause the controller boot process to stall?Are you able to provide a much finer-resolution explanation of the boot process and what exactly gets checked, in what sequence, and with what consequences if conditions are wrong?
Does the DMD itself need to be installed for the boot to complete, or can some testing be done without it? (I've been testing with it, but they're rare and expensive right now). If there was a problem with the interposer or DMD would the controllers complete their boot, or would they abort the boot?
I'm a bit concerned that there's no easy way to verify that all the signals are getting to the DMD through the interposer, is this ever generally an issue?
Do your devices log failed boot diagnostics into the serial flash devices, and if so, can that be extracted and analyzed? Is there any debugging ability available via the controller JTAG ports?
I'd sure appreciate any further tips you can provide.