• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 835 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.

TMS320F28075: UNIFLASH Verify Error

SHULU ZHENG
Prodigy 20 points
Part Number: TMS320F28075
Other Parts Discussed in Thread: UNIFLASHHi， I’m using UNIFLASH to program and verify 28075, but there are a few questions, hope to get some help, thank you! 1, When using UNIFLASH window Tool to program and verfify 28075(already loaded with the same file) with password，it returns” program load compeleted successfully”, I didn’t see a verify process, and then I created a Standalone command line package automatically, but the user setting file didn’t include the AutoECC generated setting and verify setting, just include the passwords; 2, when using command line .bat file to program 28075, after successfully programming, an error occurred, it says”memory map prevented reading 0x78000 program”, this address belongs to OTP zone, and verify status is Failed. I am not sure if the window tool does verifying after programming, if it does and succeed, why the command line way failed?
  • 0
    TI__Guru* 87145 points

    Hi Shulu,

    Please check whether the "Verify Flash after Program" is enabled or not.  It should be enabled by default unless it is disabled by the user.  Also, enable verbose mode to see more detailed messages (which would show verify as well).  

    If you have the AutoEccGeneration and verify enabled, then it should reflect in the package.  Could you check whether they are enabled in the settings or not?

    I will check with the UniFlash command line developer to see if there is a reset included after the program operation - which can secure the device and does not allow verification since password is included.  

    Thanks and regards,

    Vamsi

  • 0
    TI__Genius 13095 points
    Shulu,

    1a. In the GUI, if you turn on verbose in the console, you should see more outputs related to the verify process.

    1b. The settings file in the generated command line package only stores any settings that have changed. Because AutoECC and Verify setting is 'on' by default, it will not be stored in the settings file.

    2. From what I can see, the memory map should allow memory reads at 0x78000 on the data page (not on the program page). Can you check your program to make sure it is writing to the correct page?

    As for why you do not see this error during 'program and verify', this is because the implementation of the verification process during 'program and verify' is different from the standalone verification. The verification during 'program and verify' goes through the 'Flash programmer' and therefore bypasses the memory map in some cases.

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    Prodigy 20 points
    Ricky, I modified the cmd file and placed OTP zone on the data page, It seems that you are right that the memory should be read only from data page. Now the verify status is success. Thank you!
    Ricky Lau said:
    Shulu,

    1a. In the GUI, if you turn on verbose in the console, you should see more outputs related to the verify process.

    1b. The settings file in the generated command line package only stores any settings that have changed. Because AutoECC and Verify setting is 'on' by default, it will not be stored in the settings file.

    2. From what I can see, the memory map should allow memory reads at 0x78000 on the data page (not on the program page). Can you check your program to make sure it is writing to the correct page?

    As for why you do not see this error during 'program and verify', this is because the implementation of the verification process during 'program and verify' is different from the standalone verification. The verification during 'program and verify' goes through the 'Flash programmer' and therefore bypasses the memory map in some cases.

    Thanks,
    Ricky