FS8530A0 OTP Programming Error - Boot Enable Flag is Missing

[Sam_91]

Hi NXP Team,

I am attempting to use KITFS85FRDMEVM to program the FS85 OTP configuration via I2C on my project boards.

I2C is connected through headers VDDI2C, SDA, SCL and GND.

For my setup I am providing 8V at the DBG pin in line with the evaluation methodology.

I am able to load my OTP script and verify the correct functionality on my PCB, though when I attempt to burn the OTP configuration files to memory I get Boot Enable flag error and programming does not succeed.

I tried a reboot to see if the configuration burned anyway, though the device operates in default state post this process.

I have viewed other threads which talk about issues with A1 variants where the memory was already burned, however I know this is not the case for these as the operation returns to default.

Any help would be much appreciated.

Kind regards,

Samuel

[Sebastian_etelligent]

Hi,

the solution seems not to work for me. On my Kit its J17 anyways, but the whole process works fine, except, the OTP burning fails everytime with the Boot Enable Flag missing prompt.

I´m using a fresh FS8530A0, Excel tool version 2.3 to generate the script files.

Best regards, Sebastian

[AndreasStolze]

Hi@ErikaC 

can you help my colleague Sebastian and myself out?

Looking at your manual, everything works out, we can change the FS85xx config (like seeing definite change as our desired voltages are generated).

However, when actually trying to burn the OTP, a error occurs:

Can you give us a hint what this flag is? We cannot find anything in the documentation about it.

Thank you
Andreas

[AndreasStolze]

Hi @guoweisun 

can you help us out?

Thank you!

[guoweisun]

Did you program the A0 version of FS85?

[AndreasStolze]

Yes, we specifically ordered them to use in the programming board.

[guoweisun]

Before do the OTP ,did you use this OTP script to verify  under OTP emulation mode?

[Sebastian_etelligent]

Yes, we created a script (.txt) via the excel document and our adjustments and emulated it succesfully in the GUI and board. Everything seems to be in order there, but the actual OTP programming failes everytime.

[Sebastian_etelligent]

We were now able to write the OTP. It seems, that our first SBC we tried had a defect, since it worked with a second sample and the same configurations.

[ErikaC]

Hello,

Thank you for contacting us

Make sure that the board is connected using the appropriate hardware configuration:

1. Configure the hardware. See Section 6 "Configuring the hardware for startup".
2. Launch the FlexGUI software.
3. Switch to Debug mode:
a. Place SW3 in the right direction (VBAT switched On).
b. Close SW2 (WAKE1).
While in Debug mode, all regulators are turned Off.
4. Load the mirror registers to work in OTP emulation mode. See Section 8.3 "Working
with the Script editor".
5. Unplug jumper J9 1-2 to start the device with the mirror configuration setting.
a. If the mirror registers are filled (with a configuration using the Script editor), that
configuration is used in the emulation session.
b. If the mirror registers are not filled (with a configuration using the Script editor), the
currently-programmed OTP fuse configuration is used, if it exists.
c. Otherwise, the mirror registers are not filled and the OTP fuse is not burned, and
the device will not start up.
As long as initialization phase is not closed by a first good WD_Answer, the WD does
not start and regulators do not stay alive. Also, as long as Debug mode is not exited
by writing FS_STATES:[DBG_EXIT] bit to 1, the FS0B pin cannot be released.

[Sam_91]

Hi,

Thanks for the quick reply.

I managed to burn the OTP configuration to the FS85 on my board, however - it does not function as it did in emulation mode.

The device draws current and powers up rails for ~1 second then shuts off.

Do you know if the FCCU1 must be high to keep the device alive? I have attached my configuration file and also the excel I used to create it.

Thanks,
Sam

[ErikaC]

I've sent you an email with more details.

[Sam_91]