在与 XDS200调试器的 CCXML 连接方面、TMS320F280049和 TMS320F280049C 之间有何差异？
我们有一个项目、在49C 上自定义硬件运行正常、但是当我们移到49时、我们遇到了代码未正确刷新的问题。 我们要写入 OTP、以便代码从闪存引导、再说一次、它在49C 上可以正常工作、但在49 C 上不能正常工作。 用 OTP 进行刷写后、 我们在连接调试器时遇到问题、在读取闪存存储器时、它将读取全0、代码不会运行、似乎会卡在引导 ROM 中。
您好、Mathew：
我将回答您的问题、但我们方面取得了一些新的进展。
当我们刷写时 、我们没有得到任何我可以回忆的错误(不幸的是、我们 在前一个板中习惯了这样做、因此我们实际上并没有太多关注)、但软件无法正常工作。 尝试之后连接到电路板比往常更困难、处理器通常拒绝连接、有时当连接一段时间后、它可能会进入 CCS 所说的"低功耗模式"。
我们的电路板作为多个处理器、一对 Hercules 和一些 F280049、它们全部以菊花链形式连接。 我们有一个定制的 ccxml、用于理解这一切。 我们 使用使用 uniflash (v8.3.0)命令行的批处理脚本、按顺序将所有处理器从上一个(F280049)刷写到第一个(Hercules)。
我们使用链接器选项将 ECC 包含在输出可执行文件中、并且在调用 uniflash 时、我们将 FlashAutoECCSetting 选项设置为 false。 我们尝试写入的 OTP 旨在让我们无论引脚如何、都能够从闪存引导。 我们的输出十六进制文件具有以下内容：
我们注意到、在我们的输出十六进制文件中、这些存储器范围没有 ECC。
我们修改了执行 OTP 转储的 GEL 文件、也转储与 OTP 相关的 ECC、并在旧的49C 和新的49板之间进行比较。 好像49块电路板的 ECC 范围与我们在0xFFFF 中更改的 OTP 相关。
我相信这可能意味着我们能够恢复电路板、我们仍然不知道如何解决的唯一问题 是、很难连接到像这样刷写的 F28处理器、 每10次尝试中有8次连接被拒绝、尝试刷写任何内容始终失败。
如果您需要其他信息、请告诉我们。
谢谢。
何塞·洛佩斯
您好、Mathew：
很抱歉这么晚才回复。 我们已尝试将器件保持在等待引导模式、但我不确定是否出现了问题。 如果我们 设法连接到处理器并在引导 ROM 中逐步开始调试、当我们到达代码的以下部分时、器件会拒绝连接：
为了避免这种情况、我们只需使 PC 跳转到下一行代码。
我们还注意到代码的另一部分存在不可纠正的 ECC 错误、我们使用寄存器窗口禁用 ECC 以避免这种错误。
继续代码,我们强制它输入此部分(靠近 cbrom_system_init()的末尾):
此时我们断开调试器、软件应该会卡在无限循环中、禁用内部看门狗。 我们会尝试用我们的闪存脚本再次刷写代码、但 连接被拒绝。 我们已经尝试删除 GEL 文件、以确保它没有尝试进行奇怪的初始化、但似乎没有效果。 我们得到的错误通常与处理器处于"低功耗模式"或与 PLL 有关、但我认为也不是这样。
您好 Vamsi、
尝试时、出现以下错误：
单击"是"或"否"会多次产生相同的错误、然后显示"Load Program Failed"错误。 单击"取消"可在不刷新的情况下完成该过程。
控制台视图已满 相关错误：
C28xx_PROC_2: Trouble Reading Register ST1: (Error -1156 @ 0x5F010) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 9.2.0.00002) C28xx_PROC_2: Error: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.2.0.00002) C28xx_PROC_2: Trouble Reading Register ST1: (Error -1156 @ 0x5F012) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 9.2.0.00002) C28xx_PROC_2: Error: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.2.0.00002) C28xx_PROC_2: Trouble Reading Register PC: (Error -1156 @ 0x5F014) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 9.2.0.00002) C28xx_PROC_2: Error: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.2.0.00002) C28xx_PROC_2: Trouble Reading Register PC: (Error -1041 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002) C28xx_PROC_2: Trouble Reading Register ST1: (Error -1041 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002) C28xx_PROC_2: Trouble Reading Register ST1: (Error -1156 @ 0x5F016) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 9.2.0.00002) C28xx_PROC_2: Error: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.2.0.00002) C28xx_PROC_2: Error: (Error -1135 @ 0x3FC7A5) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.2.0.00002) C28xx_PROC_2: Unable to determine target status after 20 attempts C28xx_PROC_2: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging C28xx_PROC_2: Error occurred during flash operation: Could not read 0x00078200@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x00078204@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x00078208@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x0005F040@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783F0@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783F2@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783F4@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783F6@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783F8@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783FA@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783FC@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x000783FE@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F050@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F052@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F054@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F056@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x0005F059@Data: target is not connected C28xx_PROC_2: Warning: Failed unlocking device (zone 2) after reset. C28xx_PROC_2: Error occurred during flash operation: Could not read register ST1: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write register ST1: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write register ST1: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00007029@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005D22E@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00007062@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005FB00@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F824@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F820@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0005F980@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x0010E@Program: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00112@Program: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00114@Program: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00116@Program: target is not connected C28xx_PROC_2: Error occurred during flash operation: Cannot enable while the target is disconnected C28xx_PROC_2: Error occurred during flash operation: Could not read 0x00000064@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected C28xx_PROC_2: Error occurred during flash operation: Failed to run target while trying to execute wr_pll.alg C28xx_PROC_2: Error writing the PLL values (Flash algorithm timed out). Operation cancelled. C28xx_PROC_2: Perform a debugger reset and execute the Boot-ROM code (click on the RESUME button in CCS debug window) before erasing/loading the Flash. If that does not help to perform a successful Flash erase/load, check the Reset cause (RESC) register, NMI shadow flag (NMISHDFLG) register and the Boot-ROM status register for further debug. C28xx_PROC_2: Error occurred during flash operation: Could not write 0x00000064@Data: target is not connected C28xx_PROC_2: File Loader: Memory write failed: Unknown error C28xx_PROC_2: GEL: File: C:\Code\file.hex: Load failed. C28xx_PROC_2: Error occurred during flash operation: Could not read register PC: target is not connected C28xx_PROC_2: Error occurred during flash operation: Could not write register PC: target is not connected
谢谢。
何塞·洛佩斯
