This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DLPC4422: unable to communicate with PC

Part Number: DLPC4422
Other Parts Discussed in Thread: DLP660TE, DLPLCRDC4422EVM

Hello.

The DLPC4422 is connected to PC with a mini USB cable.

Yesterday, I succeeded to download the file '“Flash_DUAL_DLPC4422_DLP660TE_LED.img',and made the DLP Texas Instrument logo be visible on the DMD. But when I download other file in .img format, things were not going well. The software shows that the download was successful, but the DMD still showed the logo.

More serious problems occurred today. When I remove the jump on J31 and turned the SW1 on, the DMD screen did not light up. When I connected the jumper and turned the SW1 on, there was an 'USB error'.

So my question is:

1.What kind of files can be download correctly to the DLPC4422,and how can I make this kind of files?

2.What happened to my DLPC4422 and DLP660TE, or how to make them work?

PS

I have turned off DLPLCRDC4422EVM and disconnected then reconnected USB cable and powered on board for some times  but it did not work.

  • Hello,

    Thank you for using the DLP E2E forums.
    Please clarify what you mean by "other file in .img format".
    Also when you downloaded the other file, did you check the "Skip Boot Loader Area" in the GUI?

    My concern is that when you downloaded the other file, you may have deleted the bootloader portion in the memory. 

    Regards,
    Oscar

  • Hello.

    Thank you for your reply.

    I am afraid that I have deleted the bootloader portion in the memory. How can I remedy this?

    I downloaded some software to convert the format from .png to .img.

    1.save a file as .img format. 

    2.Resulting file 

    3.Open the file by a software

    I am confused that what kind of files can be recognized by DLPC4422.Files in .jpg .png .iso or in any other fomat?

    Thank you.

  • There is no mechanism to update the splash image (DLP® logo) using the DLPC4422 GUI.  This can only be done using tools that are released customers with NDA and development agreements in place.  

    The .img file used by the flash loader is a binary flash image file.  This .img file contains contains DLPC4422 controller software, configuration data, boot loader, etc..  It is not a picture file.  

    By programming a picture file using flash loader, the entire flash contents has been replaced with a picture; this includes the boot loader since it was not skipped.  At this point, there is no software in the flash. 

    Unfortunately, if you cannot communicate with the board both with and without J31 HOLD_BL in place; the board is now unusable. 

    The only way to recover from this is to use ARM debug tools (such as DSTREAM / Realview ICE, possibly others) to boot the board and then program the flash.   

    I believe this resolves the question of why you cannot communicate with the board.  Since you have opened a separate thread  regarding "DLPC4422: How to repair the boot loader area", I will continue the discussion on how to repair the boot loader there.