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.
你(们)好
专家。
我尝试在QNX中运行IPC_TEST应用程序。
我使用SDK7_1,QNX700。
当我刚运行tibin/ipc_test时,我收到了下面的控制台消息。
问题1. 我是使用build命令构建的,但在SDK7_1上收到错误消息。在SDK7_3上,构建正常。
CD <PSDK_RELEASE >/psdkqa/QNX
使所有vision应用程序_build_flags_MAK=0
问题2. 您能否查看我的开发版本(SDK 7.1 / QNX700)?
PSDK QNX 7.2 和PSDK 7.3 中的QNX720和QNX710是否为平均值?
不支持QNX700吗?
谢谢你
您好,
关于第1季度:
从 release_71/ti-processor-SDK-RTOS-j721e-EVM-VM-07_01_00_11/psdkqa/QNX运行以下命令时,请提供完整的构建日志。 预计不会出现构建错误。
清洁;
全部完成
关于问题2:
TI SDK编号惯例和QNX SDP编号惯例不相关,但需要理解。
最新的公开发布的QNX软件开发平台(SDP)是QNX SDP 7.1。
当TI发布SDK时,它将指定该发行版测试和支持的QNX SDP。 这可以在TI SDK发行说明中看到。 例如 ,PSDK QNX 7.2 发行说明(. 3.1。发行说明- 07_02_00—处理器SDKQNX (TI.com)) 如果使用QNX SDP 7.0 或使用QNX SDP 7.1 ,则指定相关性。
此致,
KB
您好,
当402.2973万当运行 来自release_71/ti-processor_stk_jkqa/rp07-ev_qnx_7k_7kip_07_qa的命令时,请提供完整的构建日志。 预计不会出现构建错误。 [/引述]发生错误。
引导日志。
Fullscreen123456789101112131415161718192021NOTICE: BL31: v2.2(release):Temp_0.0.0.3-2-gdba7d0950-dirtyNOTICE: BL31: Built : 14:32:08, Mar 23 2022I/TC:I/TC: OP-TEE version: Temp_0.0.0.3-2-gdba7d0950-dev (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 2022. 03. 23. (수) 05:32:11 UTC aarch64I/TC: InitializedMMFLAGS=19Welcome to QNX Neutrino 7.0 on the ADAS_PRK 2 BoardMailbox_plugInterrupt: interrupt Number 489, arg 0x1011EEB0Mailbox_plugInterrupt: interrupt Number 490, arg 0x1011F050Mailbox_plugInterrupt: interrupt Number 491, arg 0x1011F1F0Mailbox_plugInterrupt: interrupt Number 492, arg 0x1011F390Mailbox_plugInterrupt: interrupt Number 493, arg 0x1011F530Starting TI IPC Resmgrsuggested mask to set for EL0 timer access: 0x303cntkctl_el1: setting bits 0x303, new value 0x303suggested mask to set for EL0 timer access: 0x303cntkctl_el1: setting bits 0x303, new value 0x303Path=0 - am65xtarget=0 lun=0 Direct-Access(0) - SDMMC: S0J56X Rev: 1.0eMMC Filesystem partitionA mount!!startup.sh start!!XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXNOTICE: BL31: v2.2(release):Temp_0.0.0.3-2-gdba7d0950-dirty NOTICE: BL31: Built : 14:32:08, Mar 23 2022 I/TC: I/TC: OP-TEE version: Temp_0.0.0.3-2-gdba7d0950-dev (gcc version 9.2.1 20191025 (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10))) #1 2022. 03. 23. (수) 05:32:11 UTC aarch64 I/TC: Initialized MMFLAGS=19 Welcome to QNX Neutrino 7.0 on the ADAS_PRK 2 Board Mailbox_plugInterrupt: interrupt Number 489, arg 0x1011EEB0 Mailbox_plugInterrupt: interrupt Number 490, arg 0x1011F050 Mailbox_plugInterrupt: interrupt Number 491, arg 0x1011F1F0 Mailbox_plugInterrupt: interrupt Number 492, arg 0x1011F390 Mailbox_plugInterrupt: interrupt Number 493, arg 0x1011F530 Starting TI IPC Resmgr suggested mask to set for EL0 timer access: 0x303 cntkctl_el1: setting bits 0x303, new value 0x303 suggested mask to set for EL0 timer access: 0x303 cntkctl_el1: setting bits 0x303, new value 0x303 Path=0 - am65x target=0 lun=0 Direct-Access(0) - SDMMC: S0J56X Rev: 1.0 eMMC Filesystem partitionA mount!! startup.sh start!! kern.mbuf.nmbclusters: 8192 -> 262114 Starting PMIC Resmgr Setting env variables. # TTS-EXEC: secpol_path=/fs/ph00_qnx/secpol.bin DMIU Service Started DMIU initialization successful [VPUSwUp]Start EthDiag for VPU!! [VPUSwUp]ADAS_PRK 1.5 (1220) [VPUSwUp]UDS version : 3.1.1 [VPUSwUp]TP Layer version : 3.2.0 info: starting LogFlushDaemon, foreground=0 ESM Init Done. [VPUSwUp]Session is changed to 01我尝试按以下方式构建。(SDK 7.1 ,QNX700)结果相同(IPC_TEST)
1.由于构建错误,跳过“Make all vision应用程序_build_flags_MAK=0”。 <-问题1. SDK 7.1 是否需要执行此流程?
2.构建远程内核
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no disable_recurse_DEPS=no core=mcu1_1 ex02_bios_multicore_echo_test
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no disable_recurse_DEPS=no core=mcu2_0 ex02_bios_multicore_echo_test
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no disable_recurse_DEPS=no core=mcu2_1 ex02_bios_multicore_echo_test
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no disable_recurse_DEPS=no core=mcu3_0 ex02_BIOS_multicore_echo_test
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no disable_recurse_DEPS=no core=mcu3_1 ex02_BIOS_multicore_echo_test
make build_profile=release Board=j721e_EVM teste_warnions_a_error=no core=c66xdsp_1 ex02_bios_multicore_echo_test
make build_profile=release Board=j721e_EVM teste_warnions_a_error=no core=c66xdsp_2 ex02_bios_multicore_echo_test
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no core=c7x_1 ex02_BIOS_multicore_echo_test
make build_profile=release Board=j721e_EVM Treate_warnions_a_error=no disable_recurse_DEPS=no core=mcu1_0 ex02_bios_multicore_echo_testb3.复制远程核心映像
cp ${PDK _安装路径}/ti/binary/ex02_bios_multicore_echo test/bin/j721e_evm/ex02_bios_multicore_echo test_c7x_1_release.xe71 ${ROOTFS}/lib/firmware/J7-C71_0-FW
cp ${pdk_install_path}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_EVM-ex02_bios_multicore_echo_test_c66xdsp_2_release.xe66 ${ROOTFS}/lib/firmware/J7-C66_1-FW
cp ${pdk_install_path}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_EVM-ex02_bios_multicore_echo_test_c66xdsp_1_release.xe66 ${ROOTFS}/lib/firmware/J7-C66_0-FW
cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_EVM/ex02_bios_multicore_echo_test_mcu3_1_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f1_1-fw
cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_EVM/ex02_bios_multicore_echo_test_mcu3_0_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f1_0-fw
cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_EVM/ex02_bios_multicore_echo_test_MCU2_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f0_1-fw
cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_bios_multicore_echo_test/bin/j721e_EVM/ex02_bios_multicore_echo_test_MCU2_0_release.xer5f ${ROOTFS}/lib/firmware/j7-main-r5f0_0-fw
cp ${PDK_INSTALL_PATH}/ti/./binary/ex02_BIOS_multicore_echo_test/bin/j721e_EVM/ex02_BIOS_multicore_echo_test_mcu1_release.xer5f ${ROOTFS}/lib/firmware/J7-MCU-r5f0_1-FW
cp ${pdk_install_path}/ti/./binary/ex02_bios_multicore_echo_testb/bin/j721e_EVM-ex02_bios_multicore_echo_testb_mcu1_0_release.xer5f ${ROOTFS}/lib/firmware/J7-MCU-r5f0_0-FW但这项工作取得了成功
CD vision应用程序
制作SDK
创建QNX_FS_CREATE_SD
[TARGET]$./VX_APP_QNX_ARM_IPC.OUT
谢谢你。
您好,
感谢您提供日志和说明。 (a)至(c)是对当前状况的准确总结:
A) TI SDK 7.1 正在接受测试
B) Vision Apps VX_app_QNX_arm_IPC.out工作正常。
C)运行IPC_echo测试不起作用。
关于(c),在A72上运行的IPC_ECHO_TEST二进制文件取决于C7/C6/R5核心上的正确图像。 必须构建所有内核以识别IPC使用的内存空间。 在步骤(3)中,所需的图像似乎已构建并复制到SD卡,因此缺失的部分可能是正在运行的A72二进制文件。
在本地安装SDK时,7.1 能够生成和IPC_TEST,并生成以下日志。
在 (+)[FAQ] TDA4VM的步骤(3)中:针对PSDK QNX 7.2 / PSDK QNX 7.3 -处理器论坛-处理器- TI E2E支持论坛的IPC_Test中,它表示必须从psdkqa/QNX 目录重建A72二进制文件。
在您的构建环境中,请尝试以下操作:
光盘psdkqa/qnx
清洁
制造
cd ./vision应用程序
制作QNX_FS_INSTALL_SD
目的是确保正确构建A72二进制文件并将其复制到SD卡。
此致,
KB