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.

Problem with SHA-1 authentication on bq20z75 with bqEVSW

Other Parts Discussed in Thread: BQEVSW

I am just getting started with the BQ20z75ev1-001 evaluation kit, and have four cells wired up as directed to the eval board.  bqEVSW recognizes the setup, and I can successfully communicate with the bq20z75 device.  However, I cannot get the SHA-1 function to work. I am attempting to use the procedure outlined in Chapter 13 of SLUA404 bz20zxx Application Book.  I can successfully read and verify the authentication key (it is set to the default), and can modify said key.  I apparently can send the challenge message using the Write SMB Block function, as directed.  However, when I try to read by the challenge response, I get all zeros.

From what I've read, the device comes in the full-access mode, and I haven't (intentionally) changed this; furthermore, as far as I can tell, the device indicates the same (if I'm reading that correctly).  To be real clear, I enter 54 in the "Read SMB Word" section of the Pro page in bqEVSW, and hit the Read button; the system returnes 0040, which I interpret the following:

  • FAS bit is low, meaning the Full access security mode is active
  • SS bit is low, meaning Sealed mode is NOT active

What am I missing?

TIA,

Bob

 

  • Bob,

    I was able to replicate the procedure exactly as described in Chapter 13 of slua404 and got the response shown in the screenshots. Try using those values shown for the key and challenge and see if it works.

    Regards,

    Jason

  • Hi Jason,

    Boy, I am glad I decided not to cheat!  When I read your post, my initial reaction was to reply that I did try that procedure exactly as described.  However, since it is first thing in the morning, I decided to try it one more time, and now it works just fine!

    However, this worries me a bit, until I thought about it some more, and I think I know what was happening.  Earlier I had found the bqEVSW software expects exactly an even number of digits in the Write SMB Block "Block Data" widget, as it gives an error if not.  Today, I discovered it will also give an error when writing more than 20 bytes to 2f, but it apparently fails silently if you give it too few bytes!  So, it appears that I had originally entered the data string shown in SLUA404, but missed exactly one (probably) byte.  Then, the part simply ignored the write operation, meaning (presumably) that it had no response to return; hence, all zeros is as good as any.

    Can anyone confirm my understanding of this behavior?  Not critical, as I have it working, but I would like to close the loop in my understanding.

    Thanks, Jason!

    -Bob