SLUAB44 December   2025 UCD3138

 

  1.   1
  2.   Abstract
  3. 1Introduction to FUSION-PRODUCTION-GUI
  4. 2Limitations of FUSION-PRODUCTION-GUI for Mistake-Proof Programming
  5. 3Implementing Mistake-Proof Programming for UCD3138x
  6. 4Experimental Verification
  7. 5Conclusion
  8. 6References

Implementing Mistake-Proof Programming for UCD3138x

As shown in Figure 3-1, for a UCD3138x chip that has never been programmed, the chip always remains in ROM mode. The Boot ROM takes control of the processor and configures the chip as a PMBus slave, with the device address always set to 11 (0x0B). As listed in Table 3-1, the Boot ROM provides a set of functional commands in ROM mode that can be used to control the UCD3138.

Table 3-1 UCD3138x Boot ROM Supported Commands
Boot ROM Function Command Byte
Configure Read Address 0xFD
Read 4 Bytes 0xFA
Read 16 Bytes 0xF9
Read Next 16 Bytes 0xF8
Write 4 Bytes 0xF5
Write 16 Bytes 0xF4
Write Next 16 Bytes 0xF3
Mass Erase Flash 0xF2
Page Erase Flash 0xF1
Execute from Program Flash 0xF0
Calculate Checksum 0xEF
Read Checksum 0xEE
Read Version 0xEC

Among these, the Read Version (0xEC) command can be used to read the current ROM version through the Boot ROM. Figure 3-1 shows the command definition for the 0xEC instruction.

 0xEC Command DefinitionFigure 3-1 0xEC Command Definition

Therefore, we can implement a mistake-proof design by reading the chip's ROM version information using the 0xEC command. The specific workflow is illustrated below:

 PRODUCTION-GUI Mistake-Proof Programming FlowFigure 3-2 PRODUCTION-GUI Mistake-Proof Programming Flow

In actual factory programming scenarios, chips may undergo secondary programming, in which case the chip will be in Flash Mode. Therefore, the Send_Any_Device_To_ROM script task provided in FUSION-PRODUCTION-GUI can be used to force the chip to jump to ROM mode. Subsequently, the I2C_Read_General script task is used to execute the 0xEC command to read the chip's ROM version information. The ROM version is then checked for a match. If the ROM version matches, the subsequent programming process proceeds. Conversely, if the ROM version information does not match, the programming process is halted and an error is reported.