• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 81 subscribers
  • Views 405 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.

TMS320F280048-Q1: UNIFLASH verify error when programming a hex file with DCSM enabled

Steve Lim
Intellectual 2745 points
Part Number: TMS320F280048-Q1
Other Parts Discussed in Thread: UNIFLASH

Hi Champs,

My customer is using the latest UniFlash version 6.1.x for F280048-Q1 flash programming. 
Program Load and Verify Image were OK when DCSM was not used. But, after enabling DCSM with a password, there was some error message during Verify Image. How can we clear this issue?

-----------------------------------------------------------------------------------------------------------------------------------------------------
Verifying Program: user_files/images/test_dcsm.hex

        Preparing ...

        0 of 24 at 0x78000

error: C28xx_CPU1: File Loader: Verification failed: Memory map prevented reading 0x78000@Program
 -----------------------------------------------------------------------------------------------------------------------------------------------------

Thanks,
Steve

  • 0
    TI__Guru* 84255 points

    Steve,

    If the device is locked, you need to first unlock the device using the password, and then do the verify.

    Please check if this is the case.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Intellectual 2745 points

    Vamsi,,

    Thanks for your quick answer.
    When the customer didn't consider DCSM, the customer has been used "Verify Image" to make sure programmed data during mass production. But, after adding password lock, they want omit the verify process with due to complexity of programming. 
    As far as I know, UniFlash does verify action with Fapi_doVerify() by default during the program load. But I'm not sure if it's enough for them. If they skip the additional verify process, do you think there will be no problem with mass production?

    Does Uniflash send hex file to target with CRC checking?

    Thanks,
    Steve

  • +1 in reply to Steve Lim
    TI__Guru* 84255 points

    Steve,

    Ok, what is the complexity?  They can provide the password and unlock to verify - correct?  

    During UniFlash program load:  Verify happens twice - Flash wrapper logic in the device does one round of verify after the program.  Then, UniFlash does another round of verify using API verify function.  

    UniFlash does not send the hex file to target with CRC checking - Even if it does, it may not solve your purpose completely as you may doubt that the UniFlash can miss sending some data.

    As you know, UniFlash has checksum feature - customer can unlock and simply check the checksum.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Intellectual 2745 points

    Hi Vamsi,

    They want to use CLI interface for programming and validation. Is it possible to run "program & unlock & verify" with a single command interface ?

    Thanks,
    Steve

  • 0 in reply to Steve Lim
    TI__Guru* 84255 points

    Steve,

    Glad they can unlock and verify.

    We will get back to you on the CLI question.

    Thanks and regards,

    Vamsi

  • 0 in reply to Steve Lim
    TI__Guru**** 420650 points

    Hi Steve,

    Steve Lim said:
    They want to use CLI interface for programming and validation. Is it possible to run "program & unlock & verify" with a single command interface ?

    You can program and verify with a single command via CLI. But I believe you'll need to do the unlock with a separate command. Please use the -p option for the list of supported flash operations (including various unlock operations) 

    Thanks

    ki