TMS320F28377D: 28377 JTAG 烧录不了

你好，

   用CCS10JTAG烧录的时候，时常会芯片烧录不进去，可以连接上，但每次烧录就会断开连接，尝试进行擦除也不行，故障代码如下描述，请帮忙分析下原因，谢谢！

C28xx_CPU1: GEL Output:Memory Map Initialization Complete
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006)C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.4.0.00006)C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: 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_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x00130@Program: target is not connected
C28xx_CPU1: Error executing PLL configuration algorithm. Operation cancelled. (0x0)
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: C:\Users\Administrator\Desktop\OUTFIRST\PWM_F2837xS.out: Load failed.
C28xx_CPU1: Error occurred during flash operation: Could not read register PC: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F800@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_en.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: 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_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x5D200@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D22E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D208@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D214@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D20E@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D222@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005D200@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x00000@Program: target is not connected
C28xx_CPU1: Error occurred during flash operation: Cannot enable while the target is disconnected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Failed to run target while trying to execute pwrite_dis.alg
C28xx_CPU1: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.
C28xx_CPU1: 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_CPU1: Error occurred during flash operation: Could not read 0x0007026D@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not read 0x0005F444@Data: target is not connected
C28xx_CPU1: Error occurred during flash operation: Could not write register PC: target is not connected

Green Deng：

你好，是你自己设计制作的板子吗？这类报错通常都是仿真器的接口问题，可能你更多的要检查一下硬件情况，可以对照一下官方的开发板原理图：

C:\ti\c2000\C2000Ware_4_01_00_00\boards\LaunchPads\LAUNCHXL-F28379D

C:\ti\c2000\C2000Ware_4_01_00_00\boards\controlCARDs\TMDSCNCD28379D

,

user5059962：

我这个是批量出货的产品，芯片经历了四个阶段，从28075换到28377s，再换到28377d，后续又把28377d程序加密了，在前3个阶段没有出现过上述情况，在28377d加密以后才出现。这里我就有几个疑问：1、当前测出供电电压3V左右；2、从28377s换到28377d，是否导致功耗增加；这是硬件层面我担心供电不够；3、加密后的程序，直接烧进去空的芯片内，是否会出现这种锁死的情况？也就是说，是否程序原因会导致上述问题，谢谢！

,

Green Deng：

功耗上，两款芯片也没差多少，也就几十mA左右，你可以看一下两款芯片datasheet的5.5 Power Consumption Summary。

烧写加密后的芯片再连接的话是会出现无法连接的情况，但报错跟你也不太一样。而且你说有时候是可以正常连接的？

,

user5059962：

我看了下datasheet上说，供电电压范围是3.14-3.47V，我们是3V，可能这是个问题；另外烧写加密程序后，正如你说，确实会连不上，会报低电压，需要拉低GPIO84进入Wait Boot Mode，才可以再次连接。我的疑虑是，是否存在烧录程序有问题，也会导致烧录锁死的情况发生？

,

Green Deng：

抱歉之前没看仔细，3V的话确实电压太低，电压典型值是3.3V，波动范围如你上面所述。

至于程序，你提到你的程序本身就带加密，这样的话确实需要更改boot引脚才能再次连接。但是结合你刚才说的供电电压才3V，一般认为烧写过程中电压不稳定确实会造成烧写出问题，其中也确实包含会在代码区写入随机密码导致芯片被锁。

,

user5059962：

我现在把电压调整到3.3V了，还是会出现这个被锁死的现象，且这个概率也很大。我看了我的代码是不加密的，是否还存在其他问题会导致这个现象，比如我的程序直接从28377s到28377d，未作更改(但是运行完全正常)，是否可能引起此现象呢。我们现在芯片紧张，这个实验的消耗太大了，是否有什么办法可以修复这些芯片呢，谢谢！

DCSM如下：

.sect "dcsm_otp_z1_linkpointer" .long 0x1FFFFFFC ;Z1-LINKPOINTER1 .long 0xFFFFFFFF ;Reserved .long 0x1FFFFFFC ;Z1-LINKPOINTER2 .long 0xFFFFFFFF ;Reserved .long 0x1FFFFFFC ;Z1-LINKPOINTER3 .long 0xFFFFFFFF ;Reserved

.sect "dcsm_otp_z1_pswdlock" .long 0xFFFFFFFE ;Z1-PSWDLOCK .long 0xFFFFFFFF ;Reserved

.sect "dcsm_zsel_z1_p2" ;P2 is the 3rd block .long 0xFFFFFFFF ;Z1-EXEONLYRAM .long 0xFFFFFFFF ;Z1-EXEONLYSECT .long 0xDFFF5557 ;Z1-GRABRAM .long 0x55555555 ;Z1-GRABSECT

.long 0xFFFFFFFF ;Z1-CSMPSWD0 .long 0xFFFFFFFF ;Z1-CSMPSWD1 .long 0xFFFFFFFF; ;Z1-CSMPSWD2 .long 0xFFFFFFFF; ;Z1-CSMPSWD3 (MSW of 128-bit password)

,

user5059962：

我后来也用历程里面的程序烧录新的芯片，发现还是存在锁死的情况，可以排除软件问题；后来发现技术手册上说，dsp与烧录器之间不能超过15cm，我们有大概30多cm，我不确定这样是否会引起锁死，还是只是影响烧录；再一个，加入我换成SCI模式烧录的话，是否意味着可以避免这个问题，谢谢！

,

Green Deng：

你好，我觉得你的问题确实跟仿真器到芯片的距离有关。要求是15cm以内，但一般都是做得尽量短且等长，你的30cm确实太长了，一开始的报错也比较像是仿真器读取的问题。

你可以先考虑缩短连接线的长度再测试烧写，即使不是因为这个问题导致的，后续也是需要修改这个问题的

,

user5059962：

你好，我现在想通过SCI模式来升级，按Device Boot Mode表中，SCI模式的配置了那3个信号，GPIO28/29作为sci升级口，但C2PROGRAM1.7怎么都连不上，请问是还需要做其他处理吗,谢谢！

,

Green Deng：

你可以看一下这个帖子中关于串口升级的介绍：https://www.ti2k.com/wp-content/uploads/ti2k/DeyiSupport_C2000_c2000

需要注意的是，SCI串口和PC端连接还需要一个转换芯片，一般是转换为RS232或者RS485的方式进行通信