CC2640R2F: 烧录程序成功但是无广播信号且仿真报错

出现这两个错误通常是硬件有问题，检查硬件设计，尤其是电源部分和高频晶振部分

结合上面的部分设备没有广播，你要重点检查外部高频是否起振，以及频率是否准确

以下是关于两个错误的详细说明：

This error is caused by the inability of the JTAG debugger to access the DAP or one of its ARM subcores. This is usually caused by either a hardware failure on the board or invalid code on the subcore that causes it to reset itself continuously.

If this error is originated in software, it can potentially be recovered by accessing the DAP directly and trying to either reset the offending core, lock it or erase its flash memory via a GEL script (some microcontrollers have pre-loaded routines to allow that).

Notes:

• Some users reported this error also happens in conjunction with the Invalid device ID error above.
• For certain devices such as CC13xx and CC26xx, the GEL script is directly available on the menu Scripts → <device name> → MassErase.
• A procedure to try and unlock a Hercules device is described in this e2e forum thread.
• For CC3200/CC3220 devices, a few issues can cause this:
  • If using a Launchpad, the SOP jumpers may be set to "Flash" and not JTAG or SWD. Check this e2e thread for a more thorough procedure.
  • The device may also be in production mode. Check this e2e thread for details.
  • The device may be locked due to firmware problems, either the Service Pack or the Application firmware. Check the Launchpad and SDK documentation for details.
• For C6000 and SoC devices (Sitara, Keystone 2, etc.), check item 8 of the section Troubleshooting the connect phase above.
• For all Launchpad boards that use the XDS110 Debug Probe, a recent change on the default TCLK speed may cause this issue. Please check the section JTAG clock speed considerations at the XDS110 page.

    Error: (Error -1170 @ 0x0)
    Unable to access the DAP. 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). 
    

This error is caused by the inability of the debug probe to communicate with the device.

This can be caused by a number of hardware problems such as improper reset or power applied to the device, issues with clock (external crystal or oscillator). In this particular case, it is mandatory to verify all hardware details of your system.

This can also be caused by faulty software running on the device, which causes the core to be on an unstable state. For flash-based devices, you may need to unlock or mass erase the device. Check step 9 of the section Troubleshooting the connect phase above.

This error usually happens together with the Cannot Access the DAP error above.

Trouble Halting Target CPU: (Error -2064 @ 0x0)
Unable to read device status. Reset the device and try the operation again.
If the error persists, check the configuration, power cycle the board,
and try to make JTAG settings more stable (for example, lower TCLK).