[参考译文] TDA3XEVM：SD 卡引导

您好！  

您能给 我们详细介绍一下用例和 项目背景、以及您为何要 在 TDA3x EVM 上使用 SD Boot 吗？ 这里的最终产品是什么？

谢谢。

你(们)好

我要继续 TDA3中的摄像头启动。

为了方便开发 SDK、我想使用 SD 卡。

谢谢

是的、我知道

我想知道的是、当我继续使用指南中指定的 QSPI_SD 器件时、它不起作用。

该链接显示不支持快速引导。

我不想做快速启动。

您在 SDK 中遵循什么文档？ 您如何创建 SD 卡、以及复制了哪些文件？  

谢谢。

Vision SDK TDA3XX (v03.08.00)
这是用户指南。

SD 卡格式 FAT32和
将 Appimage 文件移动到 SD 卡后、它将更改为 QSPI 模式并启动。

我知道 TDA3不支持 SD 引导模式、

对吗？

我现在使用 QSIP_SD。

但不管用。

Unknown 说：

QSPI_SD 引导-文件打开失败

文件打开失败。 在复制 AppImage 文件之前、请检查您是否已按照上述文档中所述正确创建了 SDcard。

我知道 TDA3不支持 SD 引导模式、

对吗？

请分享您的信息来源。

谢谢。

我按照上述说明创建了 SD 卡。

VisionSDK_UserGuide_TDA3xx 指南中不存在 SD 引导模式。

谢谢

好的、感谢提供的信息。 SD 卡的 FAT32分区是否标记为可引导？ BTW 您如何创建 AppImage？

是的、就是这样。 以下是 SD 卡设置。

使用 make -s appimage 命令创建它后、将 APPIMAGE_BE 更改为 APPIMAGE 并将其移动到 SD 卡。

如果刷写到 QSPI 中、是否同样有效？

是的、对

您能否共享工作中 QSPI 情况的调试日志、以便我们进行比较并将您指向要查看的代码？

一个选项是使用 CCS 调试此代码。 我们建议在代码中放置一个 while (1)循环、并在调试模式下重新编译 appimage。 使用 QSPI_SD 进行引导、使用 CCS 连接它、然后进行单步调试直至它停止。

谢谢。

QSPI 日志：

 TDA3xx SBL Boot 

 Identified 15X15 Silicon 

 DPLL Configuration Completed 

 Clock Domain Configuration Completed 

 Module Enable Configuration Completed 

 TI EVM PAD Configuration Completed 

 DDR Configuration Completed 

 TDA3xx SOC Init Completed 

 App Image Download Begins 

 Manufacturer ID - 0x20
 Device ID - 0xba
 IPU1 CPU0 Processing 

 IPU1 CPU0 Image Load Completed 

 App Image Download Completed 

*****************************************************************

 32K Timer is used to measure cycles, divide by 32K to get time in seconds 

 Reset to SBL Init Cycles - 484  (14.77 ms) 

 SBL Initial Config Cycles - 225  (6.86 ms) 

 SOC Init Cycles - 471  (14.37 ms) 

 DDR Config Clock Cycles - 228  (6.95 ms) 

 App Image Load Cycles - 9984  (304.68 ms) 

 Slave Core Bootup Cycles - 6  (0.18 ms) 

 SBL Boot-up Cycles - 10916  (333.12 ms) 

 Time at which SBL started IPU1_0 - 11400  (347.90 ms) 

*****************************************************************

 No IPU1 CPU1 App Found, Switching to while Loop 

 Jumping to IPU1 CPU0 App 
[IPU1-0]      0.409870 s:  ***** IPU1_0 Firmware build time 16:27:11 Mar 25 2025
[IPU1-0]      0.410022 s:  *** SYSTEM: CPU Frequency <ORG = 212800000 Hz>, <NEW = 212800000 Hz>
[IPU1-0]      0.410541 s:  *** UTILS: CPU MHz = 20 Mhz ***
[IPU1-0]      0.410663 s:  SYSTEM: System Common Init in progress !!!
[IPU1-0]      0.417769 s:  UTILS: CIO: Init Done !!!
[IPU1-0]      0.417830 s:  SYSTEM: IPC init in progress !!!
[IPU1-0]      0.417891 s:  SYSTEM: Notify init done !!!
[IPU1-0]      0.418074 s:  SYSTEM: MsgQ init done !!!
[IPU1-0]      0.418135 s:  SYSTEM: IPC init DONE !!!
[IPU1-0]      0.420118 s:  SYSTEM: System Common Init Done !!!
[IPU1-0]      0.420209 s:  SYSTEM: System Init in progress !!!
[IPU1-0]      0.420270 s:  SYSTEM: BSP Common Init in progress !!!
[IPU1-0]      0.420331 s:  SYSTEM: BSP Common Init Done !!!
[IPU1-0]      0.420362 s:  SYSTEM: BSP Platform Init in progress !!!
[IPU1-0]      0.420484 s: PLATFORM: UNKNOWN CPU detected, defaulting to CPU REV 2.0
[IPU1-0]      0.420606 s:  SYSTEM: BSP Platform Init Done !!!
[IPU1-0]      0.420667 s:  SYSTEM: FVID2 Init in progress !!!
[IPU1-0]      0.420789 s:  SYSTEM: FVID2 Init Done !!!
[IPU1-0]      0.420850 s:  SYSTEM: VPS Init in progress !!!
[IPU1-0]      0.420880 s:  SYSTEM: VPDMA Descriptor Memory Address translation ENABLED [0xa0000000 -> 0x80000000]
[IPU1-0]      0.423046 s: *** VPDMA Firmware Loading... ***
[IPU1-0]      0.423137 s: VPDMA Firmware Address = 0x9ffc7800
[IPU1-0]      0.423229 s: VPDMA Load Address     = 0x4897d004
[IPU1-0]      0.423320 s: VPDMA Firmware Version = 0x4d0001b8
[IPU1-0]      0.423381 s: VPDMA List Busy Status = 0x00000000
[IPU1-0]      0.423473 s: *** VPDMA Firmware Load Success ***
[IPU1-0]      0.459189 s:  SYSTEM: VPS Init Done !!!
[IPU1-0]      0.459921 s:  UTILS: DMA: HWI Create for INT34 !!!
[IPU1-0]      0.460165 s:  SYSTEM: SW Message Box Msg Pool, Free Msg Count = 1024 
[IPU1-0]      0.460226 s:  SYSTEM: Heap = LOCAL_DDR            @ 0x00000000, Total size = 262144 B (256 KB), Free size = 260992 B (254 KB)
[IPU1-0]      0.460379 s:  SYSTEM: Heap = SR_OCMC              @ 0x00000000, Total size = 0 B (0 KB), Free size = 0 B (0 KB)
[IPU1-0]      0.460531 s:  SYSTEM: Heap = SR_DDR_CACHED        @ 0x86103000, Total size = 369086464 B (351 MB), Free size = 369086464 B (351 MB)
[IPU1-0]      0.460714 s:  SYSTEM: Heap = SR_DDR_NON_CACHED    @ 0xbfe00000, Total size = 916224 B (0 MB), Free size = 916224 B (0 MB)
[IPU1-0]      0.460867 s:  SYSTEM: Initializing Links !!! 
[IPU1-0]      0.535990 s:  SYSTEM: Initializing Links ... DONE !!! 
[IPU1-0]      0.536570 s:  BOARD: Board Init in progress !!!
[IPU1-0]      0.536875 s:  BOARD: Board Init Done !!!
[IPU1-0]      0.544714 s: 
[IPU1-0]      0.544744 s:  Vision SDK Version    : [REL_VISION_SDK_03_08_00_00]
[IPU1-0]      0.544836 s:  FVID2 Version         : [FVID_02_01_00_01]
[IPU1-0]      0.544897 s:  BSP Version           : [PDK_01_10_04__xx]
[IPU1-0]      0.544958 s:  Platform              : [EVM]
[IPU1-0]      0.545019 s:  SOC                   : [TDA3XX]
[IPU1-0]      0.545080 s:  SOC Revision          : [ES2.0]
[IPU1-0]      0.545141 s:  Board Detected        : [TDA3XX BASE]
[IPU1-0]      0.552796 s:  EEPROM Base Board Name: [ADAS-LOW-DDR3]
[IPU1-0]      0.552857 s:  Base Board Revision   : [REV D]
[IPU1-0]      0.552918 s:  Daughter Card Revision: [REV A]
[IPU1-0]      0.552979 s:  
[IPU1-0]      0.555541 s:  SYSTEM: UART: INTERRUPT Mode is Selected 
[IPU1-0]      1.558195 s:  QSPI Init Started 
[IPU1-0]      1.558348 s:  MID - 20 
[IPU1-0]      1.558409 s:  DID - ba 
[IPU1-0]      1.558439 s:  QSPI Init Completed Sucessfully 
[IPU1-0]      1.565637 s:  UTILS: DMM: API NOT supported in TDA3xx !!! 
[IPU1-0]      1.565729 s:  UTILS: DMM: API NOT supported in TDA3xx !!! 
[IPU1-0]      1.566552 s:  
[IPU1-0]      1.566644 s:  Current System Settings,
[IPU1-0]      1.566705 s:  ========================
[IPU1-0]      1.566735 s:  Display Type   : HDMI 1920x1080 @ 60fps 
[IPU1-0]      1.566796 s:  Capture Source : Sensor OV10635 1280x720  @ 30fps - VIP, YUV422 
[IPU1-0]      1.566888 s:  My IP address for interface 1 : none 
[IPU1-0]      1.566949 s:  My IP address for interface 2 : none 
[IPU1-0]      1.567010 s:  ISS Settings   : LDC=[OFF] VTNF=[OFF] WDR=[OFF] 
[IPU1-0]      1.567071 s:  
[IPU1-0]      1.567101 s:  ============
[IPU1-0]      1.567162 s:  Usecase Menu
[IPU1-0]      1.567193 s:  ============
[IPU1-0]      1.567254 s: 
[IPU1-0]  
[IPU1-0]  Vision SDK Usecases,
[IPU1-0]  -------------------- 
[IPU1-0]  1: Single Camera Usecases
[IPU1-0]  2: Multi-Camera LVDS Usecases
[IPU1-0]  3: AVB RX Usecases, (TDA2x & TDA2Ex ONLY)
[IPU1-0]  4: Dual Display Usecases, (TDA2x EVM ONLY)
[IPU1-0]  5: ISS Usecases, (TDA3x ONLY)
[IPU1-0]  6: TDA2x Stereo Usecases 
[IPU1-0]  9: RADAR Usecases
[IPU1-0]  a: Miscellaneous test's
[IPU1-0]  f: TIDL Usecase
[IPU1-0]  g: Camera Radar Combo Usecases
[IPU1-0]  
[IPU1-0]  s: System Settings 
[IPU1-0]  
[IPU1-0]  x: Exit 
[IPU1-0]  
[IPU1-0]  Enter Choice: 
[IPU1-0]  

6448856 说：

一个选项是使用 CCS 调试此代码。 我们建议在代码中放置一个 while (1)循环、并在调试模式下重新编译 appimage。 使用 QSPI_SD 引导、使用 CCS 连接它、然后进行单步调试直至停止。[/QUOT]

您能告诉我如何操作吗？

我不熟悉 CCS 的使用。

SD 卡扇区大小是否仅支持512？

谢谢。

在错误的情况下、SBL 无法检测到有效的应用程序映像文件：

App Image Download Begins

QSPI_SD Boot - File open fails

Valid App Image is not Available

在理想情况下、应用程序映像的加载已适当完成：

App Image Download Begins

Manufacturer ID - 0x20
Device ID - 0xba
IPU1 CPU0 Processing

IPU1 CPU0 Image Load Completed

App Image Download Completed

因此、您必须检查 SBL 无法检测到文件的原因。 可能是不受支持的 SD 卡！  

我建议通过添加有关文件加载功能和检查的更多打印内容来调试 SBL。

谢谢。

TDA3xx SBL 引导

识别出15x15器件

DPLL 配置完成

时钟域配置完成

模块启用配置已完成

TI EVM PAD 配置完成

DDR 配置完成

TDA3xx SOC 初始化完成

应用程序映像下载开始
媒体文件未准备就绪：
QSPI_SD 引导-文件打开失败-------------------------------------------------------

有效的应用程序映像不可用

(二

32K 计时器用于测量周期、除以32K 可获得时间(以秒为单位)

复位为 SBL Init 周期- 558 (17.02ms)

SBL 初始配置周期- 225 (6.86ms)

SoC 初始化周期- 470 (14.34ms)

DDR 配置时钟周期- 229 (6.98ms)

应用程序映像加载周期- 551 (16.81ms)

从内核启动周期- 65 (1.98ms)

SBL 启动周期- 1543 (47.08ms)

SBL 启动 IPU1_0的时间- 2101 (64.11ms)

(二

未找到 IPU1 CPU1应用程序、切换到 while 环路

在调试 SBL 端时、会出现与上述错误类似的错误。

SD 卡本身是否无法被识别？

代码：

int32_t SBLUtilsQspiSDBootRprc(sbllibAppImageParseParams_t *imageParams)
{
    int32_t    retVal   = STW_EFAIL;
    char      *filename = "AppImage";
    FRESULT    fresult;
    MMC_INST_t num = MMC4_INST;

#ifndef BOARD_TYPE_TDA3XX_RVP
    /*IOExpander mux config : Mux F : MMC4*/
    SBLUtilsConfigDevice(SBL_UTILS_DEVICE_ID_MMC4);
#endif
    
    if (0 != HSMMCSDInit(num))
    {
        SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "\n No valid SD card \n");
        retVal = STW_EFAIL;
    }
    else
    {

#ifdef DEVICE_TYPE_HS
        char      *dspFilename ="sbl_c66x";
        fresult = f_open(&gAppImageSDFilePtr, dspFilename, (BYTE) FA_READ);
        if (FR_OK != fresult)
        {
            SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR,
                         "\n QSPI_SD Boot - File open fails \n");
            retVal = STW_EFAIL;
        }
        else
        {
            SBLLibPrintf(SBLLIB_TRACE_LEVEL_INFO1,
                         "\n SD Boot - file open completed successfully \n");

            SBLLibRegisterImageCopyCallback(&SBLUtilsSDFileRead,
                                            &SBLUtilsDDRReadEdma,
                                            &SBLUtilsSDFileSeek);
            SBLLibRegisterAuthenticateRPRCCallback(&SecurityLib_authenticateDecryptBinary);
            imageParams->appImageOffset = 0U;
            retVal = SBLLibMultiCoreImageParseV2(imageParams);

            f_close(&gAppImageSDFilePtr);

            /*Start DSP 1 Decryption App*/
            SBLLibDSP1BringUp(imageParams->entryPoints->entryPoint[SBLLIB_CORE_ID_DSP1],SBLLIB_SBL_BUILD_MODE_PROD);

            /* Zero Out DSP Entry point used for Decyption*/
            imageParams->entryPoints->entryPoint[SBLLIB_CORE_ID_DSP1] = NULL;
            SBLLibRegisterAuthenticateRPRCCallback(&SecurityLib_DspAuthenticateDecryptBinary);

        }
#endif
        fresult = f_open(&gAppImageSDFilePtr, filename, (BYTE) FA_READ);
        if (FR_OK != fresult){
            switch (fresult) {
		case FR_DISK_ERR:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Disk I/O error occurred while opening file: ");
		    break;
		case FR_INT_ERR:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Internal error occurred while opening file: ");
		    break;
		case FR_NOT_READY:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Media not ready for file: ");
		    break;
		case FR_NO_FILE:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "No such file: ");
		    break;
		case FR_NO_PATH:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "No such path for file: ");
		    break;
		case FR_INVALID_NAME:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Invalid file name: ");
		    break;
		case FR_DENIED:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Access denied for file: ");
		    break;
		case FR_EXIST:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "File already exists: ");
		    break;
		case FR_INVALID_OBJECT:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Invalid file object for: ");
		    break;
		case FR_WRITE_PROTECTED:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Write protection is enabled for file: ");
		    break;
		case FR_INVALID_DRIVE:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Invalid drive for file: ");
		    break;
		case FR_NOT_ENABLED:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Drive is not enabled for file: ");
		    break;
		case FR_NO_FILESYSTEM:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "No file system detected for file: ");
		    break;
		case FR_MKFS_ABORTED:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Format aborted while opening file: ");
		    break;
		case FR_TIMEOUT:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Timeout error while opening file: ");
		    break;
		case FR_LOCKED:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "File is locked: ");
		    break;
		case FR_NOT_ENOUGH_CORE:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Not enough memory for file: ");
		    break;
		default:
		    SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR, "Unknown error occurred while opening file: ");
		    break;
	    }
            SBLLibPrintf(SBLLIB_TRACE_LEVEL_ERROR,
                         "\n QSPI_SD Boot - File open fails --------------- \n");
            //retVal = STW_EFAIL;
        }
        else
        {
            SBLLibPrintf(SBLLIB_TRACE_LEVEL_INFO1,
                         "\n SD Boot - file open completed successfully \n");

            SBLLibRegisterImageCopyCallback(&SBLUtilsSDFileRead,
                                            &SBLUtilsDDRReadEdma,
                                            &SBLUtilsSDFileSeek);

            imageParams->appImageOffset = 0U;

            retVal = SBLLibMultiCoreImageParseV2(imageParams);

            f_close(&gAppImageSDFilePtr);
        }


#ifdef DEVICE_TYPE_HS
        /* DSP was loaded with decryption app, reset to load main app */
        SBLLibCPUReset(SBLLIB_CORE_ID_DSP1);
#endif
    }
    return retVal;
}

好的、这是可能的。 尝试另一张卡并检查。

谢谢。

即使使用不同的 SD 卡、症状也是相同的

查看文件 processor_sdk_vision_ 0/ti_components/drivers/pdk_ /packages/ti/boot/sbl_auto/sbl_utils src SBLUtilsQspiSDBootRprc/tda3xx/sbl_utils_tda3xx.c 并查看函数 SBLUtilsQspiSDBootRprc ()行 no：1864,我看到 f_open 函数发生故障。

有关该函数的建议调试。

谢谢。