• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 3 answers
  • Subscribers 28 subscribers
  • Views 463 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DLP6500FYE: Uploading multiple batch files to device firmware

user6239567
Prodigy 90 points
Part Number: DLP6500FYE
Other Parts Discussed in Thread: DLPR900

Hello,

I am trying to upload a sequence of 9 images to my device firmware and also two batch files. The two batch files specify how to display the patterns, and they are identical except the exposure time is different. I can successfully use the GUI tool to create a new firmware image based on version 5.0.1 which contains the images and both batch files, and I can upload this to the device. But then I have the problem that only one of the batch files works. To get both batch files in the firmware image, I write a first image with one batch files, and then I must update this to a second image with both batch files. Afterwards, only whichever batch file I write first works. (since I can get either file to work depending on the order I write them, it seems like there is no problem with the batch files themselves)

What appears to be the problem is: the software does not write the batchfile I provide verbatim to the firmware. It seems to change some values. Most importantly, when issuing the "pattern display LUT definition command" (i.e. MBOX_DATA) it will change the byte specifying the image pattern index. I don't understand when or why this happens. When I upload the first batch file, the image pattern index is set to 0, as I expect (i.e. it is not changed). When I upload the second, it is modified and set to 1. So when I try and run that batchfile after uploading the firmware nothing happens, because there is no image pattern stored in index 1.

I would like to be able to upload both batch files and have them both work. 

I have attached my two batch files (120us and 250ms), as well as screen shots from the GUI showing how they appear after they are written to the firmware image (in this case, I wrote 120us first). I circled the byte which sets the image pattern index. .

  • 0
    TI__Guru 54430 points

    Hello User,

    How are you attempting to run the second batch file?

    I will have to attempt to recreate this in the lab.  Can you at a high level explain what you are attempting to do?

    Thanks,

    Fizix

  • 0 in reply to Fizix
    Prodigy 90 points

    Dear Fizix,

    I am trying to run the batch files from the GUI. Under the "batch files" tab in the lower right hand corner is a small box labelled "batch files stored in the EVM" and a drop down menu which allows me to select a batch file. I select the batch file I want I click the "execute" button.

    I want to have two batch files in the firmware which set parameters for displaying a set of nine images . The only difference in the batch files is they change the parameters for the display e.g. one batch file displays the patterns for 120us each and does not wait for a trigger signal, and the other cycles through the same patterns as the device receives triggers. Please let me know if I can clarify this more.

    Best,

    Peter

  • 0 in reply to user6239567
    TI__Guru 54430 points

    Peter,

    That is exactly what I was looking for.  Give me an opportunity to look at this in the lab.

    Fizix

  • 0 in reply to Fizix
    TI__Guru 54430 points

    Peter,

    Thank you for your patience.  Please insert as the second line of each batch file this command:

    PAT_START_STOP : 0x00

    You cannot update the Pattern Display LUT while patterns are running.  They must be stopped first.

    I built my firmware as follows (and it works):

    1. Start with an empty firmware file (no patterns or batch files).
    2. Set the operating mode is "Pattern on-the-Fly Mode" as shown by the radio buttons at the left.
    3. Starting with the empty firmware file in the Firmware tab, build a new firmware embedding the patterns (but no batch file yet).  
    4. Now select "Pre-stored Pattern Mode" radio button at the left.
    5. In the batch file tab add your first batch file from the disk.
    6. Starting with the firmware with the patterns in the Firmware tab add your 1st batch file with a name to the batch file window and build it.  If you want it to run at startup, mark it as "Default".
    7. In the batch file tab add your second batch file from the disk.
    8. Starting with the firmware with patterns and the 1st batch file in the Firmware tab add your 2nd batch file with another name and build it.
    9. In the Firmware tab get the final firmware from the disk and make sure that the Image Pattern Index has not change.
    10. Upload the final firmware to the EVM if it is correct.

    NOTE:  It is not necessary to load any of the intermediate firmware's to the EVM.  Whichever firmware file you have shown in the firmware tab will be the starting firmware for what you build. If this still results in the Image Pattern Index changing please let me know.  

    I hope this does the trick.

    Fizix

  • 0 in reply to Fizix
    TI__Guru 54430 points

    Peter,

    P.S.  I used Firmware 5.0.0 and GUI 4.0.0 for my testing to match your conditions.

  • 0 in reply to Fizix
    Prodigy 90 points

    Dear Fizix,

    Thank you for getting back to me.

    I am aware of the pattern start/stop command. Typically I issue this from the GUI before executing the firmware. I think that it shouldn't matter if I do this manually or in the batch file?

    The procedure you describe sounds identical to what I was doing to create the firmware, but I am happy to try it again following very carefully. Possibly I missed some step here. Unfortunately I will not have access to the DMD until at least next week.

    I guess I did not give the version of the GUI I am using, so I will need to check and confirm that it is the same as yours.

    Just to confirm, the batch files that you write to the firmware are identical to mine except for (1) an additional stop command that you issue at the start, which should have the same effect as hitting the stop button on the GUI and (2) for the batch file you upload second, the second to last byte on the "MBOX" commands is 0x00?

  • 0 in reply to user6239567
    TI__Guru 54430 points

    Hello Peter,

    I have tried this with GUI's 4.0.0 & 4.0.1 with FW 5.0.0 & 5.0.1 (all combinations).   Each resulted in correct batch files in the firmware.

    I have not tried embedding batch files without the stop command.  I will have to try that.  I am not at my lab either, but have been building them in the GUI on my laptop at home.

    What I don't know is if the GUI is trying to be too smart.  The strange thing is, the numbers for bits 10:0 of bytes 11:10 in the altered second batch file are not in the valid range of 0 - 255 (at least according to the Programmer's Guide).  If it is still doing the same, 

    If this doesn't work, try starting over with the default OOB firmare in the DLPR900 PROM directory for your EVM.

    Definitely understand the access thing as we are for the most part locked down also.

    Fizix