This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM623: AM623 + TPS6521907 Booting error

Part Number: AM623
Other Parts Discussed in Thread: TPS65219

Tool/software:

Hi,

There are no kernel errors when booting up the custom board designed with the TPS621904(PMIC).

When the PMIC is changed to TPS6521907, a kernel error occurs as shown below.

["   11.168953] VDD_1V8: Bringing 3300000uV into 1800000-1800000uV"

Please let me know what I need to modify in Kernel.

I modified the circuit by looking at the TPS6521907 Technical Reference Manual.

Best Regards,

Frank Park

  • Hi Frank,

    That printed message seems to come from regulator/core.c: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/drivers/regulator/core.c?h=ti-linux-6.12.y#n1208

    This doesn't seem like an error, rather just a message that its shifting the VDD_1v8 voltage. Can you please clarify what the issue is?

    Thanks,

    Anshu

  • Hi Anshu,

    When I2C is disconneted between TPS6521907 and AM623 physically, I get the following message and boot properly.


    -------------------------------------------------------------------------------------
    [ 11.164811] tps65219 0-0030: Failed to read device ID: -121
    [ 11.170704] tps65219: probe of 0-0030 failed with error -121

    -------------------------------------------------------------------------------------

    When I2C is connected between TPS6521907 and AM623 physically, the message below appears and re-boots repeatedly.

    -------------------------------------------------------------------------------------

    [11.168953] VDD_1V8: Bringing 3300000uV into 1800000-1800000uV

    -------------------------------------------------------------------------------------

    I think if i2c setup is set to tps6521907 in the kernel, the problem will be solved.

    Can you guide me in what areas I need to change in ther kernel?

    Thanks,

    Frank