• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 323 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.

RM48L952: Verification failed in FEE area with Uniflash

Sh.Sasaki
Guru 13625 points
Part Number: RM48L952
Other Parts Discussed in Thread: UNIFLASH,

Hi experts,

When my customer writes to the FEE area with Uniflash, the following "Verification failed" will occur.

I want to know why this error is printed.

This error occurs about 9 times when they write 10 times. That is, they rarely write successfully.

The writing environment is as follows.

Please let me know why this error is output and what is the cause.

Best regards,
Sasaki

  • 0
    TI__Guru**** 198746 points

    Hello Sasaki,

    I noticed that three hex files are loaded through the Uniflash. Does the 3rd hex file include the ECC value? If yes, please load this file separately, and disable the option of "Auto ECC generation".

  • 0 in reply to QJ Wang
    Guru 13625 points

    Hi Wang-san,

    Thank you for your reply.

    I will check it with my customer.

    Best regards,
    Sasaki

  • 0 in reply to QJ Wang
    Guru 13625 points

    Hi Wang-san,

    I confirmed this to my customer.

    QJ Wang said:
    I noticed that three hex files are loaded through the Uniflash. Does the 3rd hex file include the ECC value?

    Third hex file does not include the ECC value.

    When they enable "Auto ECC generation" and  load this file separately, ,the hex(fee.hex) file loads successfully in FEE.

    Please let me know if there are any other things to check with my customer.

    Best Regards,
    Sasaki

  • 0 in reply to Sh.Sasaki
    TI__Guru**** 198746 points

    Hello Sasaki,

    Is the bank7 programmed using FEE driver? and Is the fee.hex memory dump of FEE data?

    From the log file, why is not the 0xf020_0000~0xf020_0038 programmed? and only 0xe bytes programmed at 0xf020_0038, but 0x10 bytes are verified?

  • 0 in reply to QJ Wang
    Guru 13625 points

    Hi Wang-san,

    Thank you for your support.

    QJ Wang said:
    Is the bank7 programmed using FEE driver?

    My customers are programming Bank7 with Uniflash. 

    I think the FEE driver is not used when they use Uniflash. Is this correct?

    QJ Wang said:

    Is the fee.hex memory dump of FEE data?

    From the log file, why is not the 0xf020_0000~0xf020_0038 programmed? and only 0xe bytes programmed at 0xf020_0038, but 0x10 bytes are verified?

    I will check it with my customer.

    Best regards,
    Sasaki