Other Parts Discussed in Thread: DLPC3478, DLPA3005, DLP4710EVM-LC
Tool/software:
Dear TI Members
The components are arriving sequentially, so we are currently unable to assemble CASE3-HW.
[Question-A] I am testing without DMD Beam Engine that is CASE1-HW. DLPC3479 isn't failed that HOST_IRQ is high continually.
Can I test DLP3479 Auto initializaiton, Boot Diagnostic tool [link] /DLP Hardware Diagnostic tool/ without DMD Beam Engine connection?
We are using the same I2C code that was used for the DLPC3478 to communicate with the Host.
CASE 1-HW ) DLPC3479 & DLPA3005
CASE 2-HW) DLPC3479 & DLPA3005 & DMD4710 without R/G/B LED Connection
CASE3-HW) DLPC3479 & DLPA3005 & DMD4710 & R/G/B LED Connection
Is it possible to use the DLP3479 Boot up and diagnostic tools in the CAS1-HW architecture?
[Question -B]
-TI
The Firmware sets the address for a single device - Master/Primary.
If you look at the communication in the DLP4710EVM-LC schematic, the I2C line from external (Cypress IC) is sent to the Primary chip. A separate I2C line is then sent to the Secondary/Slave chip.
The main idea is that the Primary DLPC3479 controller will be the only one that is communicated to and controls the Secondary DLPC3479. Primary/Secondary selection is determined through GPIO4.
- LP
Question -B-1)"Using TI's Firmware Selector, both the Master Beam and Slave Beam use the same firmware, which has the same Firmware Address applied."
Did I understand this correctly?
Question -B-2) When the Host sends D4 to the 0x36 address to read the Slave DLPC3479, both the Master and Slave devices are D4.
How can DLPC3479 know that the Slave Device ID has been read?
Thanks