MMPF0100 Programming Issue using KITPFGUI

mixtwitch — Sun, 19 Dec 2021 22:54:47 GMT

Hi there, I'm seeing some odd behaviour trying to program a blank MMPF0100 with the below config using KITPFGUI;

DEVICE:PF0100A
ADDR:E0:DATA:03 // OTP_SYS_PWRON_CFG|OTP_SYS_DVS_CLK|OTP_SYS_SEQ_CLK
ADDR:E1:DATA:03 // OTP_SYS_PWRON_CFG|OTP_SYS_DVS_CLK|OTP_SYS_SEQ_CLK
ADDR:E2:DATA:03 // OTP_SYS_PWRON_CFG|OTP_SYS_DVS_CLK|OTP_SYS_SEQ_CLK
ADDR:E7:DATA:02 // OTP_SYS_TBB_MODE|OTP_SYS_IS_PROGRAMMED
ADDR:E8:DATA:01 // OTP_SYS_PGOOD
ADDR:FF:DATA:08 // OTP_SYS_I2C_DEVICE_ADDRESS
ADDR:A0:DATA:1C // SW1AB VOUT
ADDR:A1:DATA:1B // SW1AB SEQ
ADDR:A2:DATA:00 // SW1AB CFG
ADDR:A8:DATA:1C // SW1C VOUT
ADDR:A9:DATA:1B // SW1C SEQ
ADDR:AA:DATA:00 // SW1C CFG
ADDR:AC:DATA:38 // SW2 VOUT
ADDR:AD:DATA:1C // SW2 SEQ
ADDR:AE:DATA:00 // SW2 CFG
ADDR:B0:DATA:26 // SW3A VOUT
ADDR:B1:DATA:1D // SW3A SEQ
ADDR:B2:DATA:0C // SW3A CFG
ADDR:B4:DATA:18 // SW3B VOUT
ADDR:B5:DATA:1B // SW3B SEQ
ADDR:B6:DATA:00 // SW3B CFG
ADDR:B8:DATA:00 // SW4 VOUT
ADDR:B9:DATA:1D // SW4 SEQ
ADDR:BA:DATA:10 // SW4 CFG
ADDR:BC:DATA:00 // SWBST VOUT
ADDR:BD:DATA:1E // SWBST SEQ
ADDR:C0:DATA:06 // VSNVS VOUT
ADDR:C4:DATA:1F // VREFDDR SEQ
ADDR:C8:DATA:00 // VGEN1 VOUT
ADDR:C9:DATA:00 // VGEN1 SEQ
ADDR:CC:DATA:00 // VGEN2 VOUT
ADDR:CD:DATA:00 // VGEN2 SEQ
ADDR:D0:DATA:0F // VGEN3 VOUT
ADDR:D1:DATA:1F // VGEN3 SEQ
ADDR:D4:DATA:0F // VGEN4 VOUT
ADDR:D5:DATA:1F // VGEN4 SEQ
ADDR:D8:DATA:0F // VGEN5 VOUT
ADDR:D9:DATA:1B // VGEN5 SEQ
ADDR:DC:DATA:0F // VGEN6 VOUT
ADDR:DD:DATA:1F // VGEN6 SEQ

For some reason the bolded addresses are not programming properly, and when I do a verify I get the below;

Extracting OTP Data from Target Device...
Verifying OTP Data from Target Device...
OTP REG:[AD], DATA:[0x1C] = [0x1E] (PROGRAMMING ERROR)
OTP REG:[B6], DATA:[0x00] = [0x01] (PROGRAMMING ERROR)
OTP REG:[D0], DATA:[0x0F] = [0x0D] (PROGRAMMING ERROR)
OTP REG:[DD], DATA:[0x1F] = [0x1E] (PROGRAMMING ERROR)
Verification Complete. 5 Programming Errors

This has happened multiple times. I'm using the KITPFPGMEVME programmer and my own board with the PMIC loaded. I've double checked the I2C bus lines, the high voltage programming line etc and all look ok. And weirdly it seems to be these specific bits. One thing of note is that I am using the rail sequence slots at the end of the sequence - i.e. slots 26-31, rather than the ones at the beginning, to add some delay to the rail power up sequence. I usually use those at the beginning and have not seen this issue before. Your help would be much appreciated.

Re: MMPF0100 Programming Issue using KITPFGUI

guoweisun — Mon, 20 Dec 2021 02:45:36 GMT

Have you ever try it in the PF0100 programming socket board? if yes,what's the result!

topic MMPF0100 Programming Issue using KITPFGUI in Power Management

MMPF0100 Programming Issue using KITPFGUI

Re: MMPF0100 Programming Issue using KITPFGUI