• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 235 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.

BQ27Z561EVM-011: Programming bq27z561 by writing flash?

craig
Intellectual 510 points
Part Number: BQ27Z561EVM-011
Other Parts Discussed in Thread: BQSTUDIO, BQ35100

Tool/software:

Hello,

I curently have a bq27z561evm, bqstudio will not work for upload on the targe board (no interface). Could I program the devkit (evm), then read the flash values back (saving them to a plain text file) and write those values with the host mcu onto the gauge on the target board? Would that accomplish the programming? Any gotchya's I need to be aware of?


  • 0
    TI__Mastermind 35661 points

    Hey Craig,

    Yes, you are able to export the EVM gauge configuration into a bq.fs file. Then you can use the bq.fs file to program onto other gauges. Read this document about gauge communication: https://www.ti.com/lit/an/slua801/slua801.pdf

    Regards,

    Nick Richards

  • 0 in reply to Adrian
    Intellectual 510 points

    Hey Nick,

    Do you have an interface api/file? I'm 90% there with my own currently. 

    Anyway I'm going through the process specified in the gauge communications document you indicated. 

    1)The bq227z561 is NOT a rom device, so I would have to use the df.fs and/or the bq.fs files, but NOT the ot.fs and gm.fs files- Correct? And would the same be applicable the bq35100-It is NOT a ROM device so it would function the same, That is to same file types would be used for it albeit they'll correspond to the bq35100 (generated from bqstudio).

    2)section 5 indicates 0xAA corresponds to the 'device address' when in actuality its the address with the appended 0 (write mode)?...which makes sense, but my generated file also uses 0x16. Does this mean another i2c address becomes available when programming?

    the value is 0x16, which would be 0x0B for 7MSB-device address


    3)Do the bytes need to be reversed (placed in little endian), for the given commands or is are the bytes in little endian order ALREADY (no reversing needed)?

  • 0 in reply to Adrian
    Intellectual 510 points

    Yeah the address 0x16 for an i2c device address is not making sense, can you clarifiy?

  • +1 in reply to craig
    Intellectual 510 points

    nvm got it. The 0x16>>1 address is applicable in this flash mode-Weird.

  • 0 in reply to craig
    TI__Mastermind 35661 points

    Hey Craig,

    We have BQStudio for an interface for programming firmware files but it is not meant for production. We do not have an interface api/file for this.

    1. You can use df.fs, bq.fs, and gm.fs. bq.fs is the complete file so usually you only need to program that file

    2. 0x16 is the ROM address for some of our gauges

    3. I believe the bytes should already be in little endian format in any fs file

    Regards,

    Nick Richards