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

bq27520-G4 / wait command in DFFS file

K.Yaita
Guru 29720 points
Other Parts Discussed in Thread: BQ27520-G4, BQSTUDIO

Hi TI members,

My customer considers to use bq27520-G4 in his system.
He used DFFS file that is output by bqstudio and write the data to each bq27520-G4s however sometimes write failure was occured.
I heard the failure is about 1/20 probability.
Is it possible case for bq27520-G4?

As a trial, he increased the wait time (X: value) in wait command in DFFS, probability of write failure decreased dramatically.
-------------------------------------------------------
http://www.tij.co.jp/jp/lit/an/slua541a/slua541a.pdf


-------------------------------------------------------
How much wait time should he increase to prevent the write failure?
Is there any other workaround?
Could you set appropriate wait time if I send my customer's DFF file? 
 
Best Regards,
Yaita / Japan disty

  • 0
    TI__Guru* 76230 points

    hi Yaita,

    When you say failed, how are you determining this failure? waht parameters are you observing to say the programming failed.  What value did the customer increase the wait time to? Was the flashstream which the customer is using extracted from the gauge using bqstudio.  Indeed we have seen cases were insufficient wait time between writes has caused failures and 200ms has been  a good number that worked in most cases. If 200 ms doesn't work in your case, then there will be a need to increase that time to say 300ms.

    thanks

    Onyx

  • 0 in reply to Onyx Ahiakwo
    Guru 29720 points

    Hi Onyx-san,

    I appreciate for your support.

    I heard write failure means the device is still in ROM mode after programming DFFS file.
    He uses DFFS file that is extracted from the bqstudio and as a trial he added 10ms wait time every line in DFFS file write failure doesn't occur after that.

    I believe the cause comes from the capacitance of I2C lines as you said in the following, so I will talk to my customer in terms of it .
    https://e2e.ti.com/support/power_management/battery_management/f/180/p/556752/2041097#2041097

    Please let me contact you again if I need your additional help..

    Best Regards,
    Yaita

  • 0 in reply to K.Yaita
    Guru 29720 points

    Hi Onyx-san,

    I would like to confirm one more..

    >Indeed we have seen cases were insufficient wait time between writes has caused failures and 200ms has been  a good number that worked in most cases.
    My customer added 10ms wait time every line in DFFS file and confirmed write failure doesn't occur after that.
    When you have seen cases were insufficient wait time between writes, did you add wait time every line just like above?
    I would like to know how to set the wait time for workaround toward write failure in general.

    Best Regards,
    Yaita