• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Answers 5 answers
  • Subscribers 29 subscribers
  • Views 383 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DLP4500: checksum miss match issue during firmware uploading - Checksum mismatch: Expected 172a2b66; Received 10264a6a

weng yeong pang
Prodigy 170 points
Part Number: DLP4500
Other Parts Discussed in Thread: DLPR350

Dear TI,

I encounter checksum mismatch issue when uploading firmware. The error message pop up is "Checksum mismatch: Expected 172a2471; Received 10264375".

I am using Lightcrafter GUI version 4.0.0 and DLPR350 firmeare version is 4.1.0.

Link below is the .bin file I upload and .ini file I used in this .bin file.

https://we.tl/t-axpjPlpWgk

Best regards,

Weng Yeong

  • 0
    TI__Mastermind 30875 points

    Hi Weng,

    weng yeong pang said:
    I am using Lightcrafter GUI version 4.0.0 and DLPR350 firmeare version is 4.1.0.

    Is it happening only during the v4.1.0 f/w update or any another image file? Can you try the older v3.1.0 GUI and let me know if you are seeing the same error code.

    Are you also experimenting on the EVM HW or your own design using some other NOR flash ? 

  • 0 in reply to Sanjeev
    Prodigy 170 points

    Dear Sanjeev,

    I can load the firmware by using v3.1.0GUI without checksum missmatch issue. Then I try to load the firmware by using v4.0.0GUI again, the checksum missmatch issue does not encounter anymore.

    I try with another same model unit EVM HW. At first I use the v4.0.0GUI to load the firmware, it encounter checksum missmatch issue. Then I use the v3.1.0GUI load the firmware, it works normally. After that I use the v4.0.0GUI to load the firmware again, it can works normally.

    But I try another same model unit EVM HW again. The firmware can be load normally by using v4.0.0GUI. This is weird. I do not what is the root cause of it.

    Best regards,

    Weng Yeong 

  • 0 in reply to weng yeong pang
    TI__Mastermind 30875 points

    Hi Weng Yeong,

    The GUI while updating the f/w maintains a local cached copy of the last programmed firmware binary may be this causing issue when switching between the f/w and GUI version.

    You can try this option  -

    You can uncheck and try updating let me know how it behaves, by unchecking it will take longer time to download because it will download the full image otherwise it will compare the sector by sector and skip the matching areas.

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Prodigy 170 points

    Dear Sanjeev,

    I have unchecked this fast flash update box everytime I load the firmware.

    I found that the issue behave like this. After I load the f/w A with v3.1.0GUI, the same f/w A can be load in the v4.0.0GUI without any issue. But when I use v4.0.0GUI load f/w B, it encounter checksum missmatch issue. Then I load back the f/w A by using v4.0.0GUI, the checksum missmatch issue persist. I need to use v3.1.0GUI to load the f/w to recover.

    Besides, only the f/w with slant pattern image stored inside will encounter this issue. f/w with horizontal & vertical pattern image stored inside does not encounter this issue.

    Best regards,

    Weng Yeong 

  • +1 in reply to weng yeong pang
    TI__Mastermind 30875 points

    Dear Weng,

    when you tell it is f/w A and f/w B which GUI you are using to create the f/w image file.

    As far as f/w update is concerned, looks like there is a problem in latest GUI we will try to reproduce it here first.

    For now since version 3.1.0 GUI is working okay, you should consider this version whenever you are trying to update it.

    When it comes to f/w download it doesn't matter even if you use the old GUI to download. BUT if you are creating f/w file using GUI then definitely it matters.

    So for now -

    Prepare or create the f/w file using latest GUI 4.0.0

    Use GUI v3.1.0 ONLY for download.

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Prodigy 170 points

    Dear Sanjeev,

    I am using v4.0.0GUI to create the f/w A & B.

    Ok. Noted. Thanks alot.

    Best regards,

    Weng Yeong

  • 0 in reply to weng yeong pang
    TI__Mastermind 30875 points

    okay no problem.

  • 0 in reply to Sanjeev
    TI__Mastermind 28005 points

    Weng Yeong,

    I tested the firmware that you provided above (test.bin) and I was able to load it without any problems on my LCR4500EVM + GUI. To note, I am using v4.0.0 of the GUI and v4.1.0 of the Firmware. I uploaded the FW using the "Firmware Upload" tab under "Image/Firmware" using Windows 10.

    I used default settings for everything else. Hopefully this helps.

    Regards,

    Philippe Dollo

  • 0 in reply to Philippe Dollo
    Prodigy 170 points

    Dear Philippe Dollo,

    I am using v4.0.0GUI and v4.1.0 firmware too. But I am using Windows 8. We design the PCB controller board ourselves but we are following TI design guideline.

    This link below contain the f/w A and f/w B I tested and encounter checksum missmatch issue. Can you help to verify? 

    https://we.tl/t-QMEJ1IcSW6

  • 0 in reply to weng yeong pang
    TI__Mastermind 30875 points

    Yeong,

    Please try on Windows 7 or Windows 10 pc or a laptop and let us know if you still see the problem.

    Our experimental results on EVM and Windows 10 machine, you HW and OS environment are totally different from ours, first try with different PC running Windows 10 and see if you still see the issue.

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Prodigy 170 points

    Dear Sanjeev,

    I have tested in Windows 7 PC and Windows 10 PC.

    In Windows 7, it has the same behavior as the issue I encounter in Windows 8.

    In Windows 10, when open the v3.1.0GUI the EVM HW cannot be detected. But the EVM HW can be detected by using v4.0.0GUI. And the same issue encountered in the Windows 10 with v4.0.0GUI.

    Any idea from your side on this issue?

    Thank you.

    Best regards,

    Weng Yeong 

  • 0 in reply to weng yeong pang
    TI__Mastermind 30875 points

    Hi Weng,

    v3.1.0 GUI not detecting could be due to the software changes in the GUI.

    So we go back to the original problem, even on Windows 10, with v4.0.0 GUI, you have checksum error, this we are not able to reproduce.

    Again are you checking with your own hardware or TI EVM? If you have not tried, can you try with TI hardware once?

    Regards,

    Sanjeev

  • 0 in reply to Sanjeev
    Prodigy 170 points

    Dear Sanjeev,

    I found that this issue is caused by the flash NOR chip model.

    Flash NOR chip model: M29W128GL70N6FTR will not encounter this issue. But flash NOR chip model: S29GL128S90TF1010 will encounter this issue. Both chips are act as the same functionality role. Just S29GL128S90TF1010 model is with slower random access time that is 90ns compare to M29W128GL70N6FTR model random access time is 70ns.

    S29GL128S90TF1010 model able to work in v3.1.0GUI but cannot work in v4.0.0GUI.

    M29W128GL70N6FTR model able to work in both version of GUI.

    Best regards,

    Weng Yeong

  • 0 in reply to Sanjeev
    Prodigy 170 points

    After I copy the FlashDeviceParameters content in v3.1.0GUI to v4.0.0GUI, this issue solved.

    Thanks a lot for your support. =)

  • +1 in reply to weng yeong pang
    TI__Mastermind 30875 points

    I was about to send same details. Glad you found :) Note if you are using a different flash part you must update the FlashDeviceParameters.txt file, this contains the flash id, # sectors and sector start address.

    Good luck !!!