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.

BQ27542 Programming SREC

Other Parts Discussed in Thread: EV2400, BQSTUDIO

I'm trying to use Battery Management Studio and an EV2400 to program an SREC file to the BQ27542, but it is not working.  I believe I should use the Programming plugin to do this.  Here is what I see when I attempt that.  The main window says "Programming - Command channel not found." and the "Progress Information" popup never progresses.

Is there something I need to do to the gauge before attempting to program?  Am I even using the Battery Management Studio correctly?

Thanks,

Adam J.

  • Hello Adam,

    I'm discussing with our tools team regarding this. Will get back to you as soon as possible.

    Thank you.
  • Hello Adam,

    This issue was reported on bqStudio v1.3.45. A test version with changes was released on ti.com. Please download v1.3.47 in a clean directory and try programming again. 

    You can do a clean installation of 1.3.47 by specifying an alternative path in the beginning of the installer. You may have to copy over the bq27542 bqz from the existing 1.3.45 installation over to the 1.3.47. 

    Let us know if the issue persists.

    Thank you.

  • That worked! Thanks!
  • Fernando,

    I'm continuing to have trouble programming even with the test version of bqStudio (1.3.47). I'm still using the GDK to program an SREC file to the BQ27542. The test version of bqStudio works more frequently than the older version, but still fails often, and the behavior is different. The response after I click "Program" in the programming plugin is "No acknowledge from device." However, the dashboard and registers plugins work fine.
  • Hello Adam,

    Is this behavior only when using the GDK or you are getting NACKs when using an EV2400 as well? Is the gauge sealed when trying to program it?

    Thank you.
  • Fernando,

    The behavior is the same regardless of whether I use a GDK or EV2400. The program hangs and often crashes when I attempt the UNSEAL command.

    How do I know if the gauge is unsealed?

    Thanks,

    Adam J.
  • Hello Adam,

    You can verify if the gauge is unsealed by verifying the FAS and SS bits are cleared.

  • Fernando,

    OK...If I click the "UNSEAL" button, 80% of the time the program crashes. If it does not crash, and I hit the "UNSEAL FULL ACCESS" button, the program crashes. But if I refresh the Registers plugin after clicking "UNSEAL" (assuming the program doesn't crash first) and before clicking "UNSEAL FULL ACCESS," the SS bit reads as low. Once the SS bit reads low, then clicking "UNSEAL FULL ACCESS" seems to work. Also, I never get a prompt asking me for an unseal code, which I wonder if I'm supposed to get?

    So, in summary, the successful order of operations seems to be:
    1.) Click "UNSEAL".
    2.) Click "Refresh" (on Registers plugin) & verify that SS bit has gone low (green).
    3.) Click "UNSEAL FULL ACCESS".
    4.) Click "Refresh" & verify that FAS bit is low.
    5.) Open Programming plugin; browse to .srec file.
    6.) Click "Program".

    Does that sound correct? Is there some reason the program crashes when I don't refresh the Registers plugin?

    Thanks,

    Adam J.
  • Hello Adam,

    I believe bqStudio uses the default unseal/full access keys to unseal the gauges and prompts for keys if they have been changed. Have you change these or are they still the default?

    You should not have to worry about unsealing the gauge, unless of course the seal command has been sent.

    Your procedure is correct. My only theory at the moment would be if the pop-up window that prompts for the unseal keys is not being handled correctly by the software and causing the crash. I'll talk to the tools team regarding this.

    Thank you.
  • Fernando,

    I haven't changed the keys, so bqStudio isn't presenting a pop-up for the unseal keys.

    Nor have I sent the seal command. So very strange that I'm required to unseal. But it's working for now, and that's good.

    Thanks; please keep me posted regarding what the tools team says.

    Adam J.