[参考译文] J784S4XEVM：TI 请为 J784S4XEVM 中的 MCU 提供 Hello World

这种许多预处理器使得无法读取

尊敬的 Mehmet：

您是否尝试在 MCU1_0 上为 J784S4_EVM 构建 UART 裸机驱动程序示例？

此致、

Anil

你好

我的目标是使 J784S4_EVM MCU1_0 内核正常工作。 为了进行物理验证,我从方框图 中选择了 Simple UART 。 我想构建、部署、调试和查看 UART 输出、只是证明了内核的工作原理。

我设法编译 UART 裸机测试应用。 不知道是否相关。

mehmet@thinkstation:/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/build$ make -s UART_Baremetal_TestApp BOARD=j784s4_evm CORE=mcu1_0
# Linking into /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.xer5f...
#
#
# /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.xer5f created.
#
# Generating stripped image into /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release_strip.xer5f...
#
/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/drv/uart/test /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/drv/uart/test
R5 Certificate being generated :
	X509_CFG = ./x509-temp.cfg
	KEY = /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/build/makerules/k3_dev_mpk.pem
	BIN = /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.appimage
	CERT TYPE = R5, 1
	CORE ID = 16
	LOADADDR = 0x41c00100
	IMAGE_SIZE = 151732
	BOOT_OPTIONS = 0
Certificate being generated :
SUCCESS: Image /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.appimage.signed generated. Good to boot
/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/drv/uart/test /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/drv/uart/test
R5 Certificate being generated :
	X509_CFG = ./x509-temp.cfg
	KEY = /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/build/makerules/rom_degenerateKey.pem
	BIN = /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.appimage
	CERT TYPE = R5, 1
	CORE ID = 16
	LOADADDR = 0x41c00100
	IMAGE_SIZE = 151732
	BOOT_OPTIONS = 0
Certificate being generated :
SUCCESS: Image /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.appimage.hs_fs generated. Good to boot
# SBL App image /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release.appimage and /opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm/UART_Baremetal_TestApp_mcu1_0_release_BE.appimage created.
#

mehmet@thinkstation:/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm$ ls
temp_stdout.txt                                       UART_Baremetal_TestApp_mcu1_0_release.appimage.signed  UART_Baremetal_TestApp_mcu1_0_release_strip.xer5f
UART_Baremetal_TestApp_mcu1_0_release.appimage        UART_Baremetal_TestApp_mcu1_0_release_BE.appimage      UART_Baremetal_TestApp_mcu1_0_release.xer5f
UART_Baremetal_TestApp_mcu1_0_release.appimage.hs_fs  UART_Baremetal_TestApp_mcu1_0_release.rprc             UART_Baremetal_TestApp_mcu1_0_release.xer5f.map
mehmet@thinkstation:/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_TestApp/bin/j784s4_evm$

谢谢！
Mehmet

P.S.如果您认为设置 RTOS 环境更容易、我们可以这样做。 我选择裸金属,只是因为我认为它会更简单。

尊敬的 Anil：

我使用以下命令成功构建。

mehmet@thinkstation:/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/build$ make -s UART_Baremetal_TestApp BOARD=j784s4_evm CORE=mcu1_0 BUILD_PROFILE=debug

然后加载并运行 “/opt/J784S4XEVM_RTOS/ti-processor-sdk-rtos-j784s4-evm-11_02_00_06/pdk_j784s4_11_02_00_15/packages/ti/binary/UART_Baremetal_Test App/bin/j784s4_EVM/UART_mcubcu1_0_debug.xer5f“ Baremetal_Test。 我遵循以下指南进行加载。

 https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j784s4/11_02_00_06/exports/docs/psdk_rtos/docs/user_guide/ccs_setup_j784s4.html



当前问题：

Problem1：UART 上不显示任何内容。 我们期望在 UART 输出中看到什么？
Problem2：为什么没有调试符号？

谢谢你
Mehmet

加载二进制文件后它究竟在哪里挂起？

我如何知道没有调试符号。 我附上了 gif

尊敬的 Mehmet：

请尝试以下操作：

1.运行 launch.js 文件后复位 CPU 内核

2.如果仍然遇到问题、请尝试运行以下 UART 诊断示例、该示例在 J784S4_EVM 上工作。

3.如果仍面临问题:

   请勿通过启动 lauch.js 来初始化内核、而是尝试连接 M4 内核（我们需要添加 J7AHP.gel 文件）和 MCU 内核、并尝试在 MCU 内核上运行二进制文件。

e2e.ti.com/.../board_5F00_diag_5F00_uart_5F00_mcu1_5F00_0_5F00_release.xer5f

此致、

Anil

你好 Anil

备选案文 1 解决了这一问题。 我现在可以加载二进制文件:) 谢谢

我从无引导模式切换到 SD 引导。 我期望二进制文件存储在 MCU 闪存中。 如何使加载的二进制文件在电源复位后继续运行？

BR、
Mehmet