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.

[参考译文] TDA4VM:重新启动后引导失败

Guru**** 2330830 points
Other Parts Discussed in Thread: TDA4VM, TPS6594-Q1, TPS6593-Q1, LP8764-Q1
请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1495893/tda4vm-boot-fail-after-reboot

器件型号:TDA4VM
主题中讨论的其他器件: TPS6594-Q1TPS6593-Q1LP8764-Q1

工具/软件:

尊敬的 TI

当定制电路板在 eMMC 模式下引导时、它会在我关闭电源并在电路板上正确引导。

但当我尝试通过 Linux 控制台中的"reboot"命令重新引导时、它无法引导。

当通过上电复位(断电/上电)达到 uboot 提示时、会捕获以下日志


U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:15 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
Trying to boot from MMC1
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from nowhere... OK
init_env from device 17 not supported!
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
I/TC:
I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan 30 10:48:03 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Fixing SA2UL firewall owner for GP device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
Trying to boot from MMC1
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted


U-Boot 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)

SoC:   J7200 SR2.0 GP
Model: Texas Instruments K3 J7200 SoC
DRAM:  2 GiB (effective 4 GiB)
Core:  80 devices, 31 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   No ethernet found.
Hit any key to stop autoboot:  0

当 重新启动失败(热复位)时、捕获以下日志

U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:15 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed -121
Trying to boot from MMC1
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
fdt_find_or_add_subnode: fit-images: FDT_ERR_BADSTRUCTURE

当我尝试热重置时、您能检查为什么它停止启动吗?

BR

杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Jace:

    进入 u-boot 提示符后、您是否可以尝试"reset"命令并共享输出日志?
    这是否始终失败在你的最后?

    是否使用 boot0分区从 eMMC 引导?

    - Keerthy

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Keerthy。

    我在 uboot 中尝试了"reset"并成功完成了所有操作。

    请在下面查找日志

    U-Boot 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)
    
    SoC:   J7200 SR2.0 GP
    Model: Texas Instruments K3 J7200 SoC
    DRAM:  2 GiB (effective 4 GiB)
    Core:  80 devices, 31 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
    Loading Environment from MMC... OK
    In:    serial@2800000
    Out:   serial@2800000
    Err:   serial@2800000
    Net:   No ethernet found.
    Hit any key to stop autoboot:  0
    => reset
    resetting ...
    
    U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:15 +0900)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    Reading on-board EEPROM at 0x51 failed -121
    Trying to boot from MMC1
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Loading Environment from nowhere... OK
    init_env from device 17 not supported!
    Starting ATF on ARM64 core...
    
    NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
    NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
    I/TC:
    I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan 30 10:48:03 UTC 2024 aarch64
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
    I/TC: Primary CPU initializing
    I/TC: GIC redistributor base address not provided
    I/TC: Assuming default GIC group status and modifier
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    I/TC: HUK Initialized
    I/TC: Activated SA2UL device
    I/TC: Fixing SA2UL firewall owner for GP device
    I/TC: Enabled firewalls for SA2UL TRNG device
    I/TC: SA2UL TRNG initialized
    I/TC: SA2UL Drivers initialized
    I/TC: Primary CPU switching to normal world boot
    
    U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    Trying to boot from MMC1
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    
    
    U-Boot 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)
    
    SoC:   J7200 SR2.0 GP
    Model: Texas Instruments K3 J7200 SoC
    DRAM:  2 GiB (effective 4 GiB)
    Core:  80 devices, 31 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
    Loading Environment from MMC... OK
    In:    serial@2800000
    Out:   serial@2800000
    Err:   serial@2800000
    Net:   No ethernet found.
    Hit any key to stop autoboot:  0
    => reset
    resetting ...
    
    U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:15 +0900)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    Reading on-board EEPROM at 0x51 failed -121
    Trying to boot from MMC1
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Loading Environment from nowhere... OK
    init_env from device 17 not supported!
    Starting ATF on ARM64 core...
    
    NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
    NOTICE:  BL31: Built : 16:09:05, Feb  9 2024
    I/TC:
    I/TC: OP-TEE version: 4.1.0-51-g012cdca49 (gcc version 11.4.0 (GCC)) #1 Tue Jan 30 10:48:03 UTC 2024 aarch64
    I/TC: WARNING: This OP-TEE configuration might be insecure!
    I/TC: WARNING: Please check optee.readthedocs.io/.../porting_guidelines.html
    I/TC: Primary CPU initializing
    I/TC: GIC redistributor base address not provided
    I/TC: Assuming default GIC group status and modifier
    I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    I/TC: HUK Initialized
    I/TC: Activated SA2UL device
    I/TC: Fixing SA2UL firewall owner for GP device
    I/TC: Enabled firewalls for SA2UL TRNG device
    I/TC: SA2UL TRNG initialized
    I/TC: SA2UL Drivers initialized
    I/TC: Primary CPU switching to normal world boot
    
    U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    Trying to boot from MMC1
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    
    
    U-Boot 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:36 +0900)
    
    SoC:   J7200 SR2.0 GP
    Model: Texas Instruments K3 J7200 SoC
    DRAM:  2 GiB (effective 4 GiB)
    Core:  80 devices, 31 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
    Loading Environment from MMC... OK
    In:    serial@2800000
    Out:   serial@2800000
    Err:   serial@2800000
    Net:   No ethernet found.
    Hit any key to stop autoboot:  0

    当我尝试在 Linux 控制台"重新引导"时、它无法始终使用相同的日志进行引导。

    我正在使用 boot0分区从 eMMC 引导。

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Jace:

    "RESET"(复位)命令也是对电路板的热重启。 因此、内核 eMMC 驱动程序执行的某种操作会导致上述问题、因为 U-boot 在复位时似乎可以正常工作。

    - Keerthy

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Lee:  

    您能帮我解决以下问题吗?

    • 您使用的是哪个 SDK 版本?
    • 您的引导流程是什么?

    此致
    Diwakar

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Diwakar

    我将使用 ti-processor-sdk-linux-j7200-evm-09_02_00_04。

    对于启动流程、我没有对原始 SDK 进行任何更改。

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、 Jace:

    请留出一些时间来看看 EVM 上是否也存在问题。

    此致
    Diwakar

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、 Jace:

    你能帮助我在9.2SDK 上的完整日志重新启动和不重新启动,我也需要内核日志。

    在哪个分区中保留 rootfs?请分享将映像刷写到 eMMC 所遵循的步骤。

    此致
    Diwakar

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Diwakar

    就我的测试而言、 TDA4VM 可以正确地重新启动。

    我应该在 uboot 提示符下运行"mmc rst-function 0 1"、以 使重新启动在 EVM 中正常工作。

    有关此命令的历史记录、请参阅以下链接。

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1300817/processor-sdk-am62x-reboot-is-not-working-on-am62x-board

    正如我在第一个说明中提到的、这个问题发生在我们的定制电路板中。

    当我多次测试重新启动命令时、它会显示如下所示的另一个错误消息。

    U-Boot SPL 2023.04-gb62e4c6e (Mar 26 2025 - 17:09:15 +0900)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    Reading on-board EEPROM at 0x51 failed -121
    Trying to boot from MMC1
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    k3_arm64 a72@0: clk_get failed: -22
    rproc failed to be initialized (-22)
    
    resetting ...

    您能从该日志中得到一些提示吗? 重新启动后、某个时钟似乎不稳定。

    您能解释一下 uboot 和 kernel 中的详细重启顺序吗?

    因为重新引导在 uboot 中可以正常工作、但在内核中失败。

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、Jace:

    这是你第一次得到正确的日志?

    K3_ARM64 a72@0:CLK_Get 失败:-22

    问题似乎来自 a72节点0本身。

    您能帮助我们完成之前要求的完整日志吗  

    在哪个分区中保留 rootfs?请分享将映像刷写到 eMMC 所遵循的步骤。

    此致
    Diwakar

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Diwakar。

    请在下面找到完整的日志。

    仅供参考、我们为定制电路板定制了器件树。

    e2e.ti.com/.../kernel_5F00_log_5F00_20250404.txt

    我们在 eMMC 中创建了许多分区、以将应用和配置文件存储在单独的分区中。

    此外、我们还定制了 Yocto Process SDK 的方法、以生成我们的 rootfs (实际上是为了减小 rootfs 大小)

    Rootfs 存储在/dev/mmcblk0p15中

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Lee:

    很抱歉晚才回复。

    SDK:ti-processor-sdk-linux-j7200-evm-09_02_00_04。

    您能向我们提供与 Linux SDK 中默认器件树相比、您的定制电路板的器件树中所做的更改吗?

    此致

    Gokul

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    嗨、Gokul

    重新引导失败似乎与 tps6594驱动程序相关。

    当我通过 在内核配置中删除 CONFIG_MFD_TPS6594来禁用 tps6594初始化时、重新启动会正常工作。

    根据我的检查、tps6594-i2c.c 同时初始化了 tps6594和 lp8764。

    因此、我逐个禁用、然后再次测试重新启动。

    当我禁用  lp8764的初始化时、它成功地重新启动。

    最后、我在初始化 lp8764并禁用 初始化 lp8764的情况下比较 lp8764寄存器。

    1.在 tps6594-i2c.c 和 tps6594-core.c 中初始化后、重新引导失败

    root@j7200-evm:~# i2cdump -f -y 1 0x4c
    No size specified (using byte-data access)
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
    00: 00 86 b1 01 31 3b 31 3b 31 3b 31 3b 00 00 3d 00    .???1;1;1;1;..=.
    10: 41 00 41 00 b2 00 00 00 12 12 12 12 00 00 00 00    A.A.?...????....
    20: 00 00 00 00 00 00 00 00 00 00 00 21 3f 00 00 00    ...........!?...
    30: 00 01 18 18 18 18 18 01 20 20 01 00 00 41 02 49    .???????  ?..A?I
    40: 02 aa 00 04 3e 01 55 55 05 00 00 00 00 00 6c ff    ??.?>?UU?.....l.
    50: ff 1b 12 02 80 00 80 a0 09 38 00 00 00 00 00 00    .????.???8......
    60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    70: 00 00 00 00 00 00 00 00 00 00 00 00 00 c0 00 00    .............?..
    80: 00 08 08 00 0f 00 03 00 00 00 55 0b 00 00 04 00    .??.?.?...U?..?.
    90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    a0: 00 00 00 80 00 00 08 00 00 00 00 00 00 00 00 00    ...?..?.........
    b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    c0: 00 00 00 e0 00 00 00 00 00 00 00 00 00 54 9d 00    ...?.........T?.
    d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    f0: 9a 95 eb 34 24 8a f8 35 71 4f 00 00 00 00 5d 57    ???4$??5qO....]W

    2.跳过 tps6594-i2c.c 中的初始化、重新引导成功

    root@j7200-evm:~#  i2cdump -f -y 1 0x4c
    No size specified (using byte-data access)
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
    00: 00 86 b1 01 31 3b 31 3b 31 3b 31 3b 00 00 3d 00    .???1;1;1;1;..=.
    10: 41 00 37 00 b2 00 00 00 12 12 12 12 00 00 00 00    A.7.?...????....
    20: 00 00 00 00 00 00 00 00 00 00 00 21 3f 00 00 00    ...........!?...
    30: 00 01 18 18 18 18 18 01 20 20 01 00 00 41 02 49    .???????  ?..A?I
    40: 02 aa 00 04 3e 01 55 55 05 00 00 00 00 00 6c ff    ??.?>?UU?.....l.
    50: ff 1b 12 02 80 00 80 a0 09 38 10 00 00 00 00 00    .????.???8?.....
    60: 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00    ......?.........
    70: 00 00 00 00 00 00 00 00 00 00 00 00 00 c0 00 00    .............?..
    80: 00 08 08 00 0f 00 00 00 00 00 55 0b 00 00 04 00    .??.?.....U?..?.
    90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    a0: 00 00 00 80 00 00 08 00 00 00 00 00 00 00 00 00    ...?..?.........
    b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    c0: 00 00 00 e0 00 00 00 00 00 00 00 00 00 54 9d 00    ...?.........T?.
    d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
    f0: 9a 95 eb 34 24 8a f8 35 71 4f 00 00 00 00 5d 57    ???4$??5qO....]W

    我发现、当我将0x12设置为0x37时、它可以成功重新启动。

    我有两个问题。

    当我检查 tps6594_i2c_probe (struct i2c_client *client)时、它会   连续初始化 tps6594和 lp8764。

    device_id 的静态常量结构 tps6594_i2c_of_match_table[]={
    {.compatible ="ti、tps6594-Q1"、.data =(void *) TPS6594、}、
    {.compatible ="ti、tps6593-Q1"、.data =(void *) TPS6593、}、
    {.compatible ="ti、lp8764-Q1"、.data =(void *) LP8764-Q1、}、

    这是有意的吗?

    因为 tps6594_device_init ()是在 兼容为"ti,lp8764-Q1"时调用的。

    我尝试找到 lp8764的数据表来检查0x12的寄存器说明、我将该寄存器更改为0x37以重新启动。

    您能告诉我在哪里可以找到包含寄存器说明的 lp8764数据表吗?

    此外、最好解释为什么此寄存器会影响重新启动过程?

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Lee:

    我已指派相应的专家处理此问题。感谢您的耐心。

    此致

    Gokul

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、Jace:

    是0x37与0x41。 当0x41是0x12寄存器的值时、您能否确认发生失败?

    - Keerthy

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Keerthy。

    是的、我可以确认 当0x41是0x12寄存器的值时会发生问题。

    请参阅下面的日志

    root@j7200-evm:~# i2cget -f -y 1 0x4c 0x12
    0x41
    root@j7200-evm:~# reboot
             Stopping Session c1 of User root...
    [  OK  ] Removed slice Slice /system/modprobe.
    [  OK  ] Stopped target Multi-User System.
    [  OK  ] Stopped target Login Prompts.
    [  OK  ] Stopped target RPC Port Mapper.
    [  OK  ] Stopped target Timer Units.
    [  OK  ] Stopped Daily Cleanup of Temporary Directories.
    [  OK  ] Closed Process Core Dump Socket.
    [  OK  ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
             Stopping Avahi mDNS/DNS-SD Stack...
             Stopping containerd container runtime...
             Stopping Getty on tty1...
             Stopping Netperf Benchmark Server...
             Stopping Serial Getty on ttyS2...
             Stopping Load/Save Random Seed...
             Stopping TEE Supplicant...
             Stopping Telnet Server...
    [  OK  ] Stopped Avahi mDNS/DNS-SD Stack.
    [  OK  ] Stopped TEE Supplicant.
    [  OK  ] Stopped Netperf Benchmark Server.
    [  OK  ] Stopped containerd container runtime.
    [  OK  ] Stopped Getty on tty1.
    [  OK  ] Stopped Serial Getty on ttyS2.
    [  OK  ] Stopped Load/Save Random Seed.
    [  OK  ] Stopped Telnet Server.
    [  OK  ] Stopped Session c1 of User root.
    [  OK  ] Removed slice Slice /system/getty.
    [  OK  ] Removed slice Slice /system/serial-getty.
             Stopping User Login Management...
             Stopping User Manager for UID 0...
    [  OK  ] Stopped User Manager for UID 0.
             Stopping User Runtime Directory /run/user/0...
    [  OK  ] Unmounted /run/user/0.
    [  OK  ] Stopped User Runtime Directory /run/user/0.
    [  OK  ] Removed slice User Slice of UID 0.
             Stopping Permit User Sessions...
    [  OK  ] Stopped User Login Management.
    [  OK  ] Stopped Permit User Sessions.
    [  OK  ] Stopped target Network.
    [  OK  ] Stopped target Remote File Systems.
             Stopping Network Configuration...
    [  OK  ] Stopped Network Configuration.
    [  OK  ] Stopped target Preparation for Network.
    [  OK  ] Stopped IPv6 Packet Filtering Framework.
    [  OK  ] Stopped IPv4 Packet Filtering Framework.
    [  OK  ] Stopped Marvell 88E6390 switch enable.
    [  OK  ] Stopped PKAA system init.
    [  OK  ] Stopped target Basic System.
    [  OK  ] Stopped target Path Units.
    [  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
    [  OK  ] Stopped Forward Password R…uests to Wall Directory Watch.
    [  OK  ] Stopped target Slice Units.
    [  OK  ] Removed slice User and Session Slice.
    [  OK  ] Stopped target Socket Units.
    [  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
    [  OK  ] Closed Docker Socket for the API.
    [  OK  ] Closed dropbear.socket.
    [  OK  ] Closed Network Service Netlink Socket.
             Stopping D-Bus System Message Bus...
    [  OK  ] Stopped D-Bus System Message Bus.
    [  OK  ] Closed D-Bus System Message Bus Socket.
    [  OK  ] Stopped target System Initialization.
    [  OK  ] Stopped Apply Kernel Variables.
    [  OK  ] Stopped Load Kernel Modules.
    [  OK  ] Stopped Create Volatile Files and Directories.
    [  OK  ] Stopped target Local File Systems.
             Unmounting /media/ram...
             Unmounting /run/media/mmcblk0p1...
             Unmounting /run/media/mmcblk0p11...
    [   42.363334] EXT4-fs (mmcblk0p11): unmounting filesystem.
             Unmounting /run/media/mmcblk0p12...
    [   42.376251] EXT4-fs (mmcblk0p12): unmounting filesystem.
             Unmounting /run/media/mmcblk0p16...
    [   42.391114] EXT4-fs (mmcblk0p16): unmounting filesystem.
             Unmounting /run/media/mmcblk0p17...
    [   42.405113] EXT4-fs (mmcblk0p17): unmounting filesystem.
             Unmounting /run/media/mmcblk0p9...[   42.437011] EXT4-fs (mmcblk0p9): unmounting filesystem.
    
             Unmounting Temporary Directory /tmp...
             Unmounting /var/volatile...
    [  OK  ] Unmounted /media/ram.
    [  OK  ] Unmounted /run/media/mmcblk0p1.
    [  OK  ] Unmounted /run/media/mmcblk0p11.
    [  OK  ] Unmounted /run/media/mmcblk0p12.
    [  OK  ] Unmounted /run/media/mmcblk0p16.
    [  OK  ] Unmounted /run/media/mmcblk0p17.
    [  OK  ] Unmounted /run/media/mmcblk0p9.
    [  OK  ] Unmounted Temporary Directory /tmp.
    [  OK  ] Unmounted /var/volatile.
    [  OK  ] Stopped target Swaps.
    [  OK  ] Reached target Unmount All Filesystems.
    [  OK  ] Stopped File System Check on /dev/mmcblk0p1.
    [  OK  ] Stopped File System Check on /dev/mmcblk0p11.
    [  OK  ] Stopped File System Check on /dev/mmcblk0p12.
    [  OK  ] Stopped File System Check on /dev/mmcblk0p16.
    [  OK  ] Stopped File System Check on /dev/mmcblk0p17.
    [  OK  ] Stopped File System Check on /dev/mmcblk0p9.
    [  OK  ] Removed slice Slice /system/systemd-fsck.
    [  OK  ] Stopped target Preparation for Local File Systems.
    [  OK  ] Stopped Remount Root and Kernel File Systems.
    [  OK  ] Stopped Create Static Device Nodes in /dev.
    [  OK  ] Reached target System Shutdown.
    [  OK  ] Reached target Late Shutdown Services.
    [  OK  ] Finished System Reboot.
    [  OK  ] Reached target System Reboot.
    [   42.952697] kauditd_printk_skb: 3 callbacks suppressed
    [   42.952709] audit: type=1334 audit(1651167784.576:13): prog-id=8 op=UNLOAD
    [   42.965458] audit: type=1334 audit(1651167784.576:14): prog-id=7 op=UNLOAD
    [   42.972380] audit: type=1334 audit(1651167784.580:15): prog-id=6 op=UNLOAD
    [   42.979278] audit: type=1334 audit(1651167784.580:16): prog-id=5 op=UNLOAD
    [   42.986174] audit: type=1334 audit(1651167784.588:17): prog-id=4 op=UNLOAD
    [   42.993081] audit: type=1334 audit(1651167784.588:18): prog-id=3 op=UNLOAD
    [   42.994096] watchdog: watchdog0: nowayout prevents watchdog being stopped!
    [   42.999974] audit: type=1334 audit(1651167784.588:19): prog-id=10 op=UNLOAD
    [   43.007093] watchdog: watchdog0: watchdog did not stop!
    [   43.013784] audit: type=1334 audit(1651167784.588:20): prog-id=9 op=UNLOAD
    [   43.038708] systemd-shutdown[1]: Using hardware watchdog 'K3 RTI Watchdog', version 0, device /dev/watchdog0
    [   43.048586] systemd-shutdown[1]: Modifying watchdog timeout is not supported, reusing the programmed timeout.
    [   43.058535] systemd-shutdown[1]: Watchdog running with a timeout of 1min.
    [   43.072369] systemd-shutdown[1]: Syncing filesystems and block devices.
    [   43.082090] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
    [   43.099287] systemd-journald[156]: Received SIGTERM from PID 1 (systemd-shutdow).
    [   43.107791] audit: type=1335 audit(1651167784.732:21): pid=156 uid=0 auid=4294967295 tty=(none) ses=4294967295 comm="systemd-journal" exe="/lib/systemd/systemd-journald" nl-mcgrp=1 op=disconnect res=1
    [   43.136263] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
    [   43.152567] systemd-shutdown[1]: Unmounting file systems.
    [   43.160772] [996]: Remounting '/' read-only with options 'n/a'.
    [   43.179502] EXT4-fs (mmcblk0p15): re-mounted. Quota mode: none.
    [   43.190689] systemd-shutdown[1]: All filesystems unmounted.
    [   43.196310] systemd-shutdown[1]: Deactivating swaps.
    [   43.201413] systemd-shutdown[1]: All swaps deactivated.
    [   43.206673] systemd-shutdown[1]: Detaching loop devices.
    [   43.216033] systemd-shutdown[1]: All loop devices detached.
    [   43.221675] systemd-shutdown[1]: Stopping MD devices.
    [   43.227003] systemd-shutdown[1]: All MD devices stopped.
    [   43.232336] systemd-shutdown[1]: Detaching DM devices.
    [   43.237613] systemd-shutdown[1]: All DM devices detached.
    [   43.243057] systemd-shutdown[1]: All filesystems, swaps, loop devices, MD devices and DM devices detached.
    [   43.257600] systemd-shutdown[1]: Syncing filesystems and block devices.
    [   43.264469] systemd-shutdown[1]: Rebooting.
    [   43.325266] reboot: Restarting system
    
    U-Boot SPL 2023.04-gb62e4c6e (Apr 25 2025 - 08:46:22 +0900)
    SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.4--v09.02.04 (Kool Koala)')
    EEPROM not available at 0x50, trying to read at 0x51
    Reading on-board EEPROM at 0x51 failed -121
    Trying to boot from MMC1
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
    fdt_find_or_add_subnode: fit-images: FDT_ERR_BADSTRUCTURE

    从器件地址0x4C 用于  lp8764-Q1。

     在我们的电路板中、tps6594-Q1的从器件地址为0x48。

    据我所知、TDA4VM 中的这些地址是相同的。

    正如我之前所问的、"tps6594-Q1"和"lp8764-Q1"在同一函数 tps6594_device_init ()中进行初始化。

     "tps6594-Q1"和"lp8764-Q1"是否具有相同的寄存器集? 因为您的捕获屏幕适用于 tps6594。

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Keerthy。

    对此有任何更新?

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好、

    我已经邀请了我们的 PMIC 专家。 同时、如果您不是从 Linux 控制 lp8764节点、是否可以禁用该节点?

    - Keerthy

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Keerthy。

    除了  tps6594_device_init ()中的初始化之外,我们在 Linux 中不控制 lp8764。

    我暂时跳过它。

    BR

    杰斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    您好 Keerthy

    对此有任何更新?

    禁用 lp8764节点可能是一个临时解决方案。 我是对的吗?

    BR

    杰斯