Other Parts Discussed in Thread: MSPM0L1305,
Tool/software:
Hi,
I am currently writing firmware for a battery management system which features MSPM0L1305 and BQ76952 using Code Composer Studio.
I am currently implementing the OTP process and was able to successfully proceed up to step 8 described in the following documentation. However, when I send the OTP_WR_CHECK()(Subcommand 0x00A0) to AFE the reading from 0x40 to 0x5F are all 0xFF (i.e., 32 bytes of 0xFF's).
However, if I replace the OTP_WR_CHECK() subcommand with some random 2-byte number, for example 0x0000 or 0x1234, which are not defined as commands, surprisingly the reading from 0x40 is 0x80 which successfully moves the code on to the next step (i.e., step 10 in the documentation above).
Can anyone share some insights into this behavior?
Is there a certain case where the AFE fills the memory from 0x40 to 0x5F with the value 0xFF?
Thank you,
Kyungjae Lee