Part Number:AM5726
Tool/software: Linux
Hi,
We are using a custom board using a AM5726. We used the Yocto SDK that comes with the TI IDK Dev board. When bringing up the custom board, Linux had a kernel error during boot. On our custom board the PMIC was mapped to I2C2 instead of I2C1. IDK Dev board uses the PMIC chip on I2C1. We were able to get the board to boot by disabling the PMIC regulator (palmas) driver. The next revision of the board had the PMIC chip mapped to I2C1. Surprisingly, the kernel did not boot with the configuration. We discovered Uboot and the kernel support PMIC bus config through the device tree files, but the SPL portion of U-Boot was hardcoded to use the PMIC on I2C1. The reason the I2C2 config booted was because the SPL code using I2C1 didn't actually succeed in talking to the chip. When we disabled the SPL I2C1 code, the kernel was able to boot. It seems the drivers for the PMIC put the system into a state where the kernel encounters errors and exceptions during boot.
We have studied the PMIC chip but nothing is jumping out as us yet. The PMIC chips are very similar versions and share the same datasheet.
Dev Board PMIC: TPS6590375ZWSR
Alpha Board PMIC: TPS6590379ZWST
Datasheet: https://drive.google.com/file/d/11H_vpx8h7Uag8_VhHMIKdL9mVizqxDFY/view
One difference between our custom board and the IDK is the custom board is using AM5726, not AM5728, which doesn't not contain GPU, or video support. We tried disabled configuration of the supplies that map to GPU, EVE, and IVA supplies, but that didn't see to fix the issue.
We'd like to add the PMIC driver functionality back in. Any recommendations are welcome.
Thanks,
Christine