DLPC150: Development of PCB for basic operation of DLP2010NIR

Hello Srinivas,

Welcome to the E2E forum!

Let me address your questions in order.

1. Is there an alternative way to communicate with the DLPC 150?

I2C is going to be the only way to communicate with the DLPC 150 as it is the communication protocol the software has been built around.

2. Can the system run without the use of DLPC150 configuration firmware and flash memory ? 

The flash memory is necessary to hold the firmware, which in turn is crucial for the functionality of the controller as well as to interpret I2C. These both are needed for the system to run.

3. If I were to build the entire reference design would it be possible to just move the micromirror in a desired angle via the GUI?

This specific of control is not typical of the DLPC150 Gui and would be more accessible with a Light Control model from the DLP product line.

Please let us know if you have any further questions.

Regards,

Austin

Hi SP,

Point 2. Yes with valid firmware in the SPI flash, yes you should be able to communicate via I2C. Refer to DLPC150 controller datasheet power-up and power-down timings, typically soon after releasing the HOST_IRQ signal the controller is ready to receive the command.

Point 3, Discovery explorer GUI is used for some other chipset, it cannot work for DLPC150NIR chipset.

rest my colleague get back to you.

Regards,

Sanjeev 

Hello Srinivas,

I have included some procedures and pseudo-code that should help you with the flash upload below this message. Please keep in mind that these steps are meant for another EVM, but should serve the DLPC150 well.

Please let us know if you have any further question.

SPI Communication – SPI Write Procedure
1. Install drivers and application for Cheetah. (Included with Cheetah purchase or downloaded from www.totalphase.com)
2. Download the Flash Part file “winbond-spi-flash.xml” from TI.
3. Copy “winbond-spi-flash.xml” to wherever parts .xml files are installed. This is typically in \parts sub-directory wherever the Flash GUI application resides.
4. Connect Cheetah box to PC with USB cable
5. Turn on power to EVM and turn Projector ON (i.e. SW_ONOFF). You should see default test image on screen.
6. Connect Cheetah box cable to EVM header J6. Image on screen disappears as this holds the DPP343x in Reset.
7. Run Cheetah “Flash GUI” application on PC.
8. On Adaptor menu, click “Add Adapters” and if drivers are installed properly you can select SPI Adapter.TP1363-923331
9. On the Adaptor section, click “Power Button” next to TP1363-923331 to turn power on the adaptor.
10. On the Operations menu, click “Choose Target” and choose the manufacturer and part number. Bit rate should be limited to 4000 KHz.
11. On the File menu, click “Load File” and browse to the location of the Flash Image. Choose the “Binary Files” in the “Files of Type” and you should see the image files with .img extension. Chose the .img file and click “Open”. This will load the data.
12. On the Operations menu, click “Program + Verify”. Wait for the system to complete the process.
13. Remove the Cheetah cable. You should see default image reappear on the screen. This means Flash has programmed properly and DPP343x has come out of Reset and is executing the new software.
14. Verify the new software version is correct by reading system status via I2C command.

I2C Communication
Instead of communicating with the EEPROM device direct over SPI, it is possible to write to it indirectly by sending I2C commands to the controller. These I2C commands allow the user to use the controller as a SPI host, and encode the flash image in I2C instead of SPI. In this case, the controller serves as the SPI host (instead of a Cheetah or equivalent device) and allows the user to execute a flash write without needing to implement an external SPI interface.
WARNING: This method will only work if a “working” flash image has been booted to the controller and the system is running. If the EEPROM flash device is empty, or contains incorrect firmware, then the controller cannot boot and thereby cannot execute these I2C-SPI commands.
The following I2C commands are available for flash read/write operations (seen in DLPC343x Programmer’s Guide):
Command I2C Opcode Read Short Status 0xD0 Read Update Pre-Check 0xDD Write Data Type 0xDE Write Data Length 0xDF Write Erase Flash 0xE0 Write Start Data 0xE1 Write Continue Data 0xE2 Read Start Data 0xE3 Read Continue Data 0xE4

Pseudo-code for “Flash Download”:
ReadUpdatePreCheck(imageSize) if( precheckReturnBytes != 0 ) { // Error, image is too big to write }

WriteDataType(0) WriteDataLength(stepSize);

while (sentBytes < image_size) { if (sentBytes == 0) WriteStartData(dataBytes[stepSize]) else WriteContinueData(dataBytes[stepSize])

sentBytes += stepSize;

// recommended to check flash download status periodically (every 4096 bytes) if ((sentBytes % 4096) == 0) { ReadShortStatus() // check status every so often, to make sure all's well if (statusCommunicationFailure = True) { // Error has occurred in Flash Download } }

Delay(m_writedelay); }
p-dollo@ti.com DPP343x EVM Flash Setup Guide July 23rd 2020
// Success! System may now be rebooted with new flash image

Pseudo-code for “Flash Read”:
WriteDataType(0) WriteDataLength(stepSize);

while (readBytes < image_size) { if (sentBytes == 0) dataBytes[stepSize] = ReadStartData() else dataBytes[stepSize] = ReadContinueData()

readBytes += stepSize;

// recommended to check flash download status periodically (every 4096 bytes) if ((readBytes % 4096) == 0) { ReadShortStatus() // check status every so often, to make sure all's well if (statusCommunicationFailure = True) { // Error has occurred in Flash Download } }

Delay(m_writedelay); } // Success! System may now be rebooted with new flash image

Kind Regards,

Austin

Hello Austin ,

Perfect , I will keep your suggestion in mind . Thank you !

Have a nice day ,

Best ,

SP.