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

Writing in the Manufacturer Info Block of bq27510-G2

Kathleen Gayo
Intellectual 620 points

Hi,

I had done multiple dfis before and was able to parse the bqfs to be included in the C# code for the programming at production phase.

As a last minute request of the client, they would want to redo the characterization and write the company name, dfi version and dfi generated date in the Manufacturing Block (A and B). Basically,  i am hoping to write Company Incorporated V1 YYYY-MM-DD in the Manufacturer Block.

Question:

1. Can I modify the Manufacturer Block of an old DFI file and update it without having to go thru the learning process again? If yes, can anyone guide me on how i could do this?

2. If i have to perform the characterization again, (as there are some revisions in the hardware design), how can i write the data in the manufacturer block using EV2300 and bq EVSW? Would i have to write the hex value of the manufacturer block one by one in the Data Flash System Data tab? Should i do this before i update the Golden pack? 

Thanks,

Kat

  • 0
    TI__Genius 14985 points

    Hi Kat,

    It is easy to update any parameters in a golden file.  You don't need to redo the learning cycle.

    Just load the current golden file into the EVM, update the info in the Data Flash tab one by one (click, type, Enter), then export the SENC file from the I2C Pro screen.  Then convert it to bqfs/dffs using Flashstream.exe.

    If you need more details or help on any of those steps, let us know.

  • 0 in reply to dMax
    Intellectual 620 points

    Hi dmax,

    I will be needing the manufacturer info on all 30K units. given the process you had stated, then this means i would need to Read to *.senc file in I2C Pro. would i need to read/write byte first before exporting the senc file?

    In addition, does the Manufacturer Info Block A 0 represent the first byte i want to put in?

    How about if i will redo the characterization? Our client had insisted on doing so. should i key in the manufacturer info after the learning cycle before updating the golden pack?

    Thanks,

    Kat

  • 0 in reply to Kathleen Gayo
    TI__Genius 14985 points

    Yes, change the values in Data Flash, then read out the SENC file again in I2C Pro.

    It doesn't matter if you change the Manufacturer Info Block data before or after redoing the characterization since it doesn't affect the gauging function.  It's just a scratch pad.

    A 0 is the first byte is the first byte of the Manufacturer Info Block.

  • 0 in reply to dMax
    Intellectual 620 points

    dmax,

    i tried updating the manufacturer info block (type enter values in Data Flash).

    I also entered ROM mode and Read to senc file. After reading, an error appeared stating: Read Failed! Error Code = 221 

    How can I work around this?

    Thanks,

    Kat

  • 0 in reply to Kathleen Gayo
    TI__Genius 14985 points

    I've had problems with reading SENC files in I2C Pro of EVSW if the path that I'm saving too is too long. 

    So try to save the SENC file to a very short path (like C:\) and let me know if that works.

  • 0 in reply to dMax
    Intellectual 620 points

    dmax,

    I had transferred the senc file in C:\ but is till get the same error

    Thanks,

    Kat

  • 0 in reply to Kathleen Gayo
    TI__Genius 14985 points

    Hi Kat,

    From your other posts it seems like you might have figured this out.  Did you get it working and what was the root cause or solution?

  • 0 in reply to dMax
    Intellectual 620 points

    dMax,

    The solution actually came up randomly. I followed your instruction to have the senc file in a shorter directory. Moving the file to C: didn't result to a successful read/update. So i had moved the senc file around in different directories and I got it to work successfully when the senc was in the Desktop.

    -Kat