[参考译文] AM625：AM62x：HS-SE：SPL 无法写入 MCU_MMR0_RST_CTRL

您好 Daniel、

从 HS FS 器件在 HS SE 器件上运行的软件是否有任何区别？ 我尝试了在 HS SE 器件中写入 MCU_RST_CTRL MMR、我能够更新它。 您能分享用于更新此 MMR 的代码吗？  

此致、

Nihar Potturu。  

您好、

没有除了不同的 tiboot3 二进制文件之外没有区别。

我还能够通过 U-Boot 提示符在 HS-SE 器件上写入此寄存器。 但是、SPL 无法写入。

您可以在您的电路板上尝试这些更改吗？

--- a/arch/arm/mach-k3/am62x/am625_init.c
+++ b/arch/arm/mach-k3/am62x/am625_init.c
@@ -80,9 +80,14 @@ static __maybe_unused void enable_mcu_esm_reset(void)
 {
        /* Set CTRLMMR_MCU_RST_CTRL:MCU_ESM_ERROR_RST_EN_Z  to '0' (low active) */
        u32 stat = readl(CTRLMMR_MCU_RST_CTRL);

+       printf("CTRLMMR_MCU_RST_CTRL val: 0x%x\n", stat);
+       printf("CTRLMMR_MCU_RST_CTRL reg: 0x%x\n", CTRLMMR_MCU_RST_CTRL);
+       printf("RST_CTRL_ESM_ERROR_RST_EN_Z_MASK mask: 0x%x\n", RST_CTRL_ESM_ERROR_RST_EN_Z_MASK);
        stat &= RST_CTRL_ESM_ERROR_RST_EN_Z_MASK;
+       printf("write value: 0x%x\n", stat);
        writel(stat, CTRLMMR_MCU_RST_CTRL);
+       printf("read back: 0x%x\n", readl(CTRLMMR_MCU_RST_CTRL));
 }

您好 Daniel、

从共享的补丁中、我可以看到您在写入之前没有解锁 MCU CTRL MMR 寄存器。 这可能会导致此处出现问题。 我当时使用的是 SBL 流程、我们在 MCU+SDK 中有一个 API 来直接解锁这些 MMR 寄存器。 您是否可以采用以下代码作为参考、并在将 MMR 寄存器写入之前尝试解锁它们。

/* Reset Ctrl belongs to partition 6 of the CTRL MMR */
    uint32_t     rstPartition = 6U;
    uint32_t    volatile * ctrl_addr ;
    /* Unlock CONTROL MMR registers */
    SOC_controlModuleUnlockMMR(SOC_DOMAIN_ID_MCU, rstPartition);


    ctrl_addr = (volatile uint32_t *)(0x4518170);
    DebugP_log("Value of RST SRC register = %X\r\n",*ctrl_addr);
    *ctrl_addr &= (~(1<<17));


    /* Lock CONTROL MMR registers */
    /* Usual Wdg Application continues*/
    SOC_controlModuleLockMMR(SOC_DOMAIN_ID_MCU, rstPartition);
    DebugP_log("Value of RST SRC register after writing = %X\r\n",*ctrl_addr);

void SOC_controlModuleLockMMR(uint32_t domainId, uint32_t partition)
{
    uint32_t            baseAddr;
    volatile uint32_t  *kickAddr;

    if(SOC_DOMAIN_ID_MAIN == domainId)
    {
        #if 0 /* in AM62x, main dowmin MMRs are left unlocked since when working with linux kernel, linux kernel assumes MMRs are unlocked */
        baseAddr = (uint32_t) AddrTranslateP_getLocalAddr(CSL_CTRL_MMR0_CFG0_BASE);
        kickAddr = (volatile uint32_t *) (baseAddr + CSL_MAIN_CTRL_MMR_LOCKn_KICK0_OFFSET(partition));
        CSL_REG32_WR(kickAddr, KICK_LOCK_VAL);      /* KICK 0 */
        kickAddr++;
        CSL_REG32_WR(kickAddr, KICK_LOCK_VAL);      /* KICK 1 */
        #endif
    }

    if(SOC_DOMAIN_ID_MCU == domainId)
    {
        baseAddr = (uint32_t) AddrTranslateP_getLocalAddr(CSL_MCU_CTRL_MMR0_CFG0_BASE);
        kickAddr = (volatile uint32_t *) (baseAddr + CSL_MCU_CTRL_MMR_LOCKn_KICK0_OFFSET(partition));
        CSL_REG32_WR(kickAddr, KICK_LOCK_VAL);      /* KICK 0 */
        kickAddr++;
        CSL_REG32_WR(kickAddr, KICK_LOCK_VAL);      /* KICK 1 */
    }

    return;
}

void SOC_controlModuleUnlockMMR(uint32_t domainId, uint32_t partition)
{
    uint32_t            baseAddr;
    volatile uint32_t  *kickAddr;

    if(SOC_DOMAIN_ID_MAIN == domainId)
    {
        baseAddr = (uint32_t) AddrTranslateP_getLocalAddr(CSL_CTRL_MMR0_CFG0_BASE);
        kickAddr = (volatile uint32_t *) (baseAddr + CSL_MAIN_CTRL_MMR_LOCKn_KICK0_OFFSET(partition));
        CSL_REG32_WR(kickAddr, KICK0_UNLOCK_VAL);   /* KICK 0 */
        kickAddr++;
        CSL_REG32_WR(kickAddr, KICK1_UNLOCK_VAL);   /* KICK 1 */
    }

    if(SOC_DOMAIN_ID_MCU == domainId)
    {
        baseAddr = (uint32_t) AddrTranslateP_getLocalAddr(CSL_MCU_CTRL_MMR0_CFG0_BASE);
        kickAddr = (volatile uint32_t *) (baseAddr + CSL_MCU_CTRL_MMR_LOCKn_KICK0_OFFSET(partition));
        CSL_REG32_WR(kickAddr, KICK0_UNLOCK_VAL);   /* KICK 0 */
        kickAddr++;
        CSL_REG32_WR(kickAddr, KICK1_UNLOCK_VAL);   /* KICK 1 */
    }

    if(SOC_DOMAIN_ID_WKUP == domainId)
    {
        baseAddr = (uint32_t) AddrTranslateP_getLocalAddr(CSL_WKUP_CTRL_MMR0_CFG0_BASE);
        kickAddr = (volatile uint32_t *) (baseAddr + CSL_MCU_CTRL_MMR_LOCKn_KICK0_OFFSET(partition));
        CSL_REG32_WR(kickAddr, KICK0_UNLOCK_VAL);   /* KICK 0 */
        kickAddr++;
        CSL_REG32_WR(kickAddr, KICK1_UNLOCK_VAL);   /* KICK 1 */
    }

    return;
}
 

此致、

Nihar Potturu。  

尊敬的 Nihar：

U-Boot 会正确解锁所有分区。 请参阅 https://github.com/phytec/u-boot-phytec/blob/7228051878d7f093457a1a043c28a5231e448862/arch/arm/mach-k3/am62x/am625_init.c#L192 和 https://github.com/phytec/u-boot-phytec/blob/7228051878d7f093457a1a043c28a5231e448862/arch/arm/mach-k3/am62x/am625_init.c#L47

同样、看门狗在 FS 器件上能够处理相同的 U-Boot 映像。

很抱歉、我们将在明天之前分享有关此问题的最新信息。