[参考译文] AWR2944：未知编译器错误

您好：

您正在尝试构建什么？

这是在 windows 上吗？

您是否在任何地方进行了任何编辑？

我还建议先清理、然后再构建。 库似乎尚未更新。

此致、

Gabriel

您好、

我只是尝试 根据 DDM 类型构建 SDK mmwave_mcuplus_sdk_04_07_01_04。

我的 syscfg 如下所示替换 mss.syscfg。

运行环境是 Linux。

每次构建之前、我都会进行清理。

它似乎与以下 CPU 设置有关。

因为编译器在相同环境中的结果是不同的。 C66 似乎优于 R5F。

BRS、

Bolong

/**
 * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
 * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
 * @cliArgs --device "AWR294X" --package "ETS" --part "Default" --context "r5fss0-0" --product "MCU_PLUS_SDK_AWR2944@09.00.00"
 * @versions {"tool":"1.19.0+3426"}
 */

/**
 * Import the modules used in this configuration.
 */
const flash      = scripting.addModule("/board/flash/flash", {}, false);
const flash1     = flash.addInstance();
const adcbuf     = scripting.addModule("/drivers/adcbuf/adcbuf", {}, false);
const adcbuf1    = adcbuf.addInstance();
const cbuff      = scripting.addModule("/drivers/cbuff/cbuff", {}, false);
const cbuff1     = cbuff.addInstance();
const crc        = scripting.addModule("/drivers/crc/crc", {}, false);
const crc1       = crc.addInstance();
const edma       = scripting.addModule("/drivers/edma/edma", {}, false);
const edma1      = edma.addInstance();
const edma2      = edma.addInstance();
const gpio       = scripting.addModule("/drivers/gpio/gpio", {}, false);
const gpio1      = gpio.addInstance();
const gpio2      = gpio.addInstance();
const ipc        = scripting.addModule("/drivers/ipc/ipc");
const mcan       = scripting.addModule("/drivers/mcan/mcan");
const mcan1      = mcan.addInstance();
const mcan2      = mcan.addInstance();
const uart       = scripting.addModule("/drivers/uart/uart", {}, false);
const uart1      = uart.addInstance();
const uart2      = uart.addInstance();
const watchdog   = scripting.addModule("/drivers/watchdog/watchdog", {}, false);
const watchdog1  = watchdog.addInstance();
const clock      = scripting.addModule("/kernel/dpl/clock");
const debug_log  = scripting.addModule("/kernel/dpl/debug_log");
const mpu_armv7  = scripting.addModule("/kernel/dpl/mpu_armv7", {}, false);
const mpu_armv71 = mpu_armv7.addInstance();
const mpu_armv72 = mpu_armv7.addInstance();
const mpu_armv73 = mpu_armv7.addInstance();
const mpu_armv74 = mpu_armv7.addInstance();
const mpu_armv75 = mpu_armv7.addInstance();
const mpu_armv76 = mpu_armv7.addInstance();
const mpu_armv77 = mpu_armv7.addInstance();
const mpu_armv78 = mpu_armv7.addInstance();

/**
 * Write custom configuration values to the imported modules.
 */
flash1.$name                  = "CONFIG_FLASH0";
/* bootloader1.flashDriver       = flash1; */
flash1.flashManfId            = "0xC2";
flash1.device                 = "CUSTOM_FLASH";
flash1.fname                  = "MX25V1635F";
flash1.flashDeviceId          = "0x2315";
flash1.flashQeType            = "2";
flash1.flashSize              = 2097152;
flash1.peripheralDriver.$name = "CONFIG_QSPI0";

adcbuf1.$name = "CONFIG_ADCBUF0";

cbuff1.$name = "CONFIG_CBUFF0";

crc1.$name = "CONFIG_CRC0";

edma1.$name                             = "CONFIG_EDMA0";
edma1.instance                          = "EDMA_DSS_B";
edma1.regionId                          = 0;
cbuff1.edmaConfig                       = edma1;
edma1.edmaRmDmaCh[0].resourceType       = scripting.forceWrite("ownDmaCh");
edma1.edmaRmDmaCh[0].$name              = "CONFIG_EDMA_RM0";
edma1.edmaRmDmaCh[0].startIndex         = 0;
edma1.edmaRmDmaCh[0].endIndex           = 63;
edma1.edmaRmQdmaCh[0].$name             = "CONFIG_EDMA_RM1";
edma1.edmaRmTcc[0].$name                = "CONFIG_EDMA_RM2";
edma1.edmaRmTcc[0].startIndex           = 0;
edma1.edmaRmTcc[0].endIndex             = 63;
edma1.edmaRmParam[0].$name              = "CONFIG_EDMA_RM3";
edma1.edmaRmParam[0].startIndex         = 0;
edma1.edmaRmReservedDmaCh[0].$name      = "CONFIG_EDMA_RM4";
edma1.edmaRmReservedDmaCh[0].startIndex = 0;
edma1.edmaRmReservedDmaCh[0].endIndex   = 0;

gpio1.$name                = "CONFIG_GPIO0";
gpio1.pinDir               = "OUTPUT";
gpio1.GPIO.$assign         = "GPIO";
gpio1.GPIO.gpioPin.pu_pd   = "pu";
gpio1.GPIO.gpioPin.$assign = "PAD_AB";

gpio2.$name                = "CONFIG_GPIO1";
gpio2.pinDir               = "OUTPUT";
gpio2.GPIO.gpioPin.pu_pd   = "pu";
gpio2.GPIO.gpioPin.$assign = "PAD_AZ";

ipc.r5fss0_1     = "NONE";
ipc.vringNumBuf  = 1;
ipc.vringMsgSize = 1152;

mcan.dataSynchJumpWidth = 1;
mcan.nomRatePrescalar   = 4;
mcan.nomTimeSeg1        = 4;
mcan.nomTimeSeg2        = 1;
mcan.dataTimeSeg1       = 6;
mcan.dataTimeSeg2       = 1;
mcan.dataRatePrescalar  = 0;

mcan1.$name        = "CONFIG_MCAN0";
mcan1.MCAN.$assign = "MCANB";

mcan2.$name           = "CONFIG_MCAN1";
mcan2.MCAN.RX.$assign = "PAD_BO";
mcan2.MCAN.TX.$assign = "PAD_BN";

uart1.$name           = "CONFIG_UART0";
uart1.UART.$assign    = "UARTA";
uart1.UART.RX.$assign = "PAD_DA";
uart1.UART.TX.$assign = "PAD_DB";

uart2.$name           = "CONFIG_UART1";
uart2.intrEnable      = "DISABLE";
uart2.UART.RX.$used   = false;
uart2.UART.TX.$assign = "PAD_DE";

edma2.$name                        = "CONFIG_EDMA1";
flash1.peripheralDriver.edmaConfig = edma2;
uart1.edmaConfig                   = edma2;
uart2.edmaConfig                   = edma2;
edma2.edmaRmDmaCh[0].$name         = "CONFIG_EDMA_RM5";
edma2.edmaRmQdmaCh[0].$name        = "CONFIG_EDMA_RM6";
edma2.edmaRmTcc[0].$name           = "CONFIG_EDMA_RM7";
edma2.edmaRmParam[0].$name         = "CONFIG_EDMA_RM8";
edma2.edmaRmReservedDmaCh[0].$name = "CONFIG_EDMA_RM9";

watchdog1.$name          = "CONFIG_WDT0";
watchdog1.wdt_func_clk   = 150000000;
watchdog1.expirationTime = 200;
watchdog1.resetMode      = "Watchdog_RESET_OFF";

mpu_armv71.$name        = "CONFIG_MPU_REGION0";
mpu_armv71.attributes   = "Device";
mpu_armv71.allowExecute = false;

mpu_armv72.$name = "CONFIG_MPU_REGION1";
mpu_armv72.size  = 14;

mpu_armv73.$name    = "CONFIG_MPU_REGION2";
mpu_armv73.baseAddr = 0x80000;
mpu_armv73.size     = 14;

mpu_armv74.$name    = "CONFIG_MPU_REGION3";
mpu_armv74.baseAddr = 0x10200000;
mpu_armv74.size     = 20;

mpu_armv75.$name      = "CONFIG_MPU_REGION4";
mpu_armv75.attributes = "NonCached";
mpu_armv75.size       = 14;
mpu_armv75.baseAddr   = 0x102EC000;

mpu_armv76.$name        = "CONFIG_MPU_REGION5";
mpu_armv76.baseAddr     = 0xC5000000;
mpu_armv76.size         = 13;
mpu_armv76.attributes   = "NonCached";
mpu_armv76.allowExecute = false;

mpu_armv77.$name        = "CONFIG_MPU_REGION6";
mpu_armv77.baseAddr     = 0xA4030000;
mpu_armv77.size         = 12;
mpu_armv77.attributes   = "NonCached";
mpu_armv77.allowExecute = false;

mpu_armv78.$name        = "CONFIG_MPU_REGION7";
mpu_armv78.baseAddr     = 0x88000000;
mpu_armv78.size         = 21;
mpu_armv78.attributes   = "Cached+Sharable";
mpu_armv78.allowExecute = false;

/**
 * Pinmux solution for unlocked pins/peripherals. This ensures that minor changes to the automatic solver in a future
 * version of the tool will not impact the pinmux you originally saw.  These lines can be completely deleted in order to
 * re-solve from scratch.
 */
flash1.peripheralDriver.QSPI["0"].$suggestSolution = "PAD_AL";
flash1.peripheralDriver.QSPI["1"].$suggestSolution = "PAD_AM";
flash1.peripheralDriver.QSPI["2"].$suggestSolution = "PAD_AN";
flash1.peripheralDriver.QSPI["3"].$suggestSolution = "PAD_AO";
flash1.peripheralDriver.QSPI.$suggestSolution      = "QSPI0";
flash1.peripheralDriver.QSPI.CLK.$suggestSolution  = "PAD_AP";
flash1.peripheralDriver.QSPI.CS.$suggestSolution   = "PAD_AQ";
gpio2.GPIO.$suggestSolution                        = "GPIO";
mcan1.MCAN.RX.$suggestSolution                     = "PAD_AH";
mcan1.MCAN.TX.$suggestSolution                     = "PAD_AI";
mcan2.MCAN.$suggestSolution                        = "MCANA";
uart2.UART.$suggestSolution                        = "UARTB";

您好：

为什么要将 MSS_CPU 设置为 C66？

MSS 代码旨在在 R5F 内核上运行。 如果您将该代码更改回、它会生成什么代码？

此致、

Gabriel

您好、

我原始代码使用 R5F 对 MSS_CPU 使用、并找到了错误。

由于错误消息显示“Related CPU“、因此我尝试测试并更改为 C66 以查看昨天的结果不同。

我发现一个旧问题与下面的  AM2634 相同：链接到静态库时遇到错误 

您能帮我一步一步地解决问题吗？

BRS、

Bolong

您好：

我已经尝试在 SDK 4.7.1.4 上构建 2944 DDM 演示、没有问题。 我甚至使用您提供的自定义.syscfg 文件构建它。 我将分享用于构建环境的 setenv.bat 文件、该文件在 CCS 和编译器用法上存在一些差异。 请尝试使用这些相同的设置构建 DDM 演示。 您是否在代码中的任何位置进行了任何其他更改？ 我不知道是什么原因导致您出现问题。

您好：

我目前没有访问 Linux 系统的权限。 您无法使用 Windows 吗？

如果不是、请给我几天时间来获得一台 Linux 计算机并在我这边进行测试

此致、

Gabriel

您好：

我们仅使用 Linux 服务器来编译器。

您可能需要几天的时间来测试它。

我是否需要使用 TI CCS 工具并输入 arc.syscfg 来获取 ti_xxx.c、然后复制它们以替换 mss/mssgenerated 或 dss/dssgenerated 文件夹中的逻辑块？

Thnaks、

Bolong