DLPDLCR471TPEVM: How to update bootloader using JTAG?

Hello User,

Welcome to the E2E forum and thank you for your interest in DLP® technology.

Our expert will provide more information and point you to the right document for programming use JTAG. Please expecting the answer in two days. 

Regards,

Lori 

Thank you very much for providing the materials. I will wait as you said.

I will develop based on the document. And if I have any questions, I will ask again. Thank you again.

Hello.

Thank you very much for providing the materials. I downloaded the materials through the link.

I have a question Where can I get the .bin file in the picture below?

There is no .bin in the firmware and bootloader folder downloaded from the DLPDLCR471TPEVM link.Using the .img in the firmware folder??

Thank you again for your support, and please reply.

Hello, Lori Wang.

hank you for your reply.

I have a question about the bootloader-FW download link.

The link,  provided contains the following files : Bootloader_Update_6540-v1p1p0-Setup

Run the downloaded file, the following files will be created in the folder.  I can't find .bin.

I tried searching with the JTAG flash tool and it's the same.

Is there something I'm doing wrong in the process of finding .bin?

Thank you for always being so kind in your responses. Please reply.

Hello, Lori Wang.

Thank you very much for providing the bootloader bin file. I will upload the bootloader using the FlashProgrammer tool and UM232H.

I will ask questions if I have any questions while developing. Thank you again for helping me develop.

Hello, Lori Wang.

I installed the bootloader as described in the documentation, but the DLP EVM GUI does not recognize it. I have a few questions.

In the DLP LightCrafter 4500 documentation,

1. it's J30 where the jumper should be connected.

2. Start Address (HEX) : 0X00000000, SIZE (HEX) : 0x0020000

In the Display 471TP EVM,

1. Is it J9 (Header for BOOT_HOLD jumper)?

2. Should I set the Start Address and SIZE to the same? The initial value is SIZE 0x00008000.

I have repeated the Section 4 process several times as recommended in the document, but it is not recognized.

1. I'm getting an error that the FlashDeviceParameters.txt file is missing. Should I have that file?

2. Can I get the board files and .bin, .txt files back. Please.

And, is there anything that can help?

Thank you.

Hello TAE-YOUNG,

1. Did you connect the J20 for ASIC JTAG cable for programming the bootloader?

2. Please try to use Start Address (HEX): 0x00000000 and Size (HEX): 0x0020000. 

1. If you try to continue click "OK", does this error message disappear? 

2. What do you mean get the these .bin and .txt files back? 

Regards,

Lori 

Hello, Lori Wang.

Thank you for your reply.

1. Yes. I connected the UH232H to the J20 for ASIC JTAG cable.

2. Yes. I tried 0X0020000. When the program ends, SIZE changes to 0x0000C230.

 -> 

When click the Flash Info button, will see :

After completing all the steps I tried to update the firmware from the DLP EVM GUI(3.2.0.6) but it did not connect.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

1. 1. Yes, the error message is disappear.

2. Requested the FlashDeviceParameters.txt file for DLPC6540 (DLP471 ENM)

- Flash memory information

 Mfg : MICRON

 MfgID : 0x0089

 Device :  28EW256ABA1H

 DevID : 0x227E

- From the link www.ti.com/.../DLPC900REF-SW, I got FlashDeviceParameters.txt Version 4.

// Mfg MfgID LMfgID, Device DevID LDevID, 
"Micron", 0x0089, 0x0000000000000089, "MT28EW256", 0x227E

Even if I comment out other chipset parameter information and upload the bootloader, it still isn't recognized.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Is it possible that the cable length connecting JTAG (UM-232H) and J20 is the problem?

Please let me know if you have any other issues.

Since I asked the question using Google Translate, there may be some parts that are lacking in conveying the content. Please understand.