This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
手里有2块LAUNCHXL-CC1310的开发板,芯片是CC1310F128RGZ,板载XDS110仿真器。
参考LAUNCHXL-CC1310的原理图,做了一块CC1310的小板,芯片是CC1310F128RSM。
现在想使用板载的XDS110仿真器给自己做的小板烧写程序。使用CCS(版本10.4.0.00006 )开发环境,打开rfWakeOnRadioTx_CC1310_LAUNCHXL_nortos_ccs工程,编译后,给小板供电,小板和XDS之间连接上RST、TMS、TCK引脚,当下载程序时,报错了。
具体报错是:
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: Unable to determine target status after 20 attempts
Cortex_M3_0: 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
Cortex_M3_0: File Loader: Memory write failed: Target failed to read 0x20000A6C
Cortex_M3_0: GEL: File: E:\DesignWork\TempMonitor Update\cc1310 plan\Project\rfWakeOnRadioTx_CC1310_LAUNCHXL_nortos_ccs\Debug\rfWakeOnRadioTx_CC1310_LAUNCHXL_nortos_ccs.out: Load failed.
请问该如何解决。
另外LAUNCHXL-CC1310开发板程序烧写正常;但是不能打开SDK中RTOS的例程,否则报错;打开NO-RTOS就正常。
将两块板子的连线图传上来看看,是否已经共地了?两块板子的GND也要连接起来
但是不能打开SDK中RTOS的例程,否则报错;打开NO-RTOS就正常。
这个是什么意思?RTOS例程编译报错?
使用flash programmer 2应该是识别了芯片,但是写程序同样报错
报错提示是:>Initiate access to target: XDS-L2000O27 using 2-pin cJTAG.
>Reading file: E:/DesignWork/TempMonitor Update/cc1310 plan/Project/rfWakeOnRadioTx_CC1310_LAUNCHXL_nortos_ccs/Debug/rfWakeOnRadioTx_CC1310_LAUNCHXL_nortos_ccs.out.
>Start flash erase ...
>Unable to halt target CPU
>Reset target ...
>Reset of target successful.
关于写程序:我自己做的采集温度小板供电也是从LaunchPad上取的3.3V和GND,所以地是连在一起的。
关于打开SDK中RTOS的例程,是打开的过程中就会有个警告:See details below...rfPacketTx_CC1310_LAUNCHXL_tirtos_ccs No XDCtools, equivalent to the specified version '3.51.999', are available - defaulting to '3.62.1.15_core'.。
当编译时就会出现错误。感觉是版本不同导致的错误。
我看你的芯片还是A版本,A版本在2017年4月份后已不再生产,现在的CC1310都是B版本的
另外A版本不支持433M频段,建议在生产中使用B版本的芯片
看了上面的连线,没有问题,替换A版本为B版本,然后下载最新版本的SDK例程试一下
当编译时就会出现错误。感觉是版本不同导致的错误。
是的,这是版本的问题,XDCtools版本不匹配,下载最新的SDK则不会出现这个问题
嗯,电源连接线就是3.3V,GND;烧写程序就是RST、TCK、TMS。如果接线没错,你觉得芯片版本可能会造成这种影响。我再试试B版本的芯片,LaunchPad上的XDS110仿真器不用变吧,还需要升级什么的吗。
买了2片21+批次的CC1310,焊接到板子上。下载了最新的SDK,版本是simplelink_cc13x0_sdk_4_20_02_07。尝试下载程序,报错。
报错信息:
Cortex_M3_0: GEL Output: Memory Map Initialization Complete.
Cortex_M3_0: GEL Output: Board Reset Complete.
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: 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). (Emulation package 9.4.0.00129)
Cortex_M3_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. 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.4.0.00129)
Cortex_M3_0: Unable to determine target status after 20 attempts
Cortex_M3_0: 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
Cortex_M3_0: File Loader: Memory write failed: Could not read 0x20000A6C: target is not connected
Cortex_M3_0: GEL: File: E:\DesignWork\TempMonitor Update\cc1310 plan\Project\gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs\Debug\gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs.out: Load failed.。
在尝试用Flash Programmer2写程序时,我重新建了一个工程路径,在E盘根目录下建了TIPRJ的一个文件夹,然后打开的工程放到这里。
在Flash Programmer2找到上述目录下的,编译好的.out文件,烧写时,擦写FLASH正常,但后面就报错了。
报错信息:
>Initiate access to target: XDS-L2000O27 using 2-pin cJTAG.
>Reading file: E:/TiPrj/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs/Debug/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs.out.
>Start flash erase ...
>Erase finished successfully.
>Start flash programming ...
>Unable to halt target CPU
>Failed to write 14568 bytes to address 0x00000000.
>Reset target ...
>Reset of target successful.
强制擦除成功。再次烧写还是不行。
>Initiate access to target: XDS-L2000O27 using 2-pin cJTAG.
>Reading file: E:/TiPrj/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs/Debug/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs.out.
>Start flash erase ...
>Unable to halt target CPU
>Reset target ...
>Reset of target successful.
强制擦除
>Initiate access to target: XDS-L2000O27 using 2-pin cJTAG.
>Start flash erase ...
>Erase finished successfully.
>Reset target ...
>Reset of target successful.
似乎想不到其他原因了,可能是硬件有问题
你可以再做以下尝试:
1.使用Uniflash下载试试
2.做一些4*4对应的移植,编译好后再下载看看情况
下面帖子介绍了一些移植相关的信息:
下载了uniflash,选择了flash image,点击load image。出现报警,让升级XDS110的版本。
需要升级吗。升级后会影响我给LaunchPad下载程序吗。
>Start flash erase ...
>Erase finished successfully.
>Start flash programming ...
>Unable to halt target CPU
>Failed to write 13032 bytes to address 0x00000000.
>Reset target ...
>Reset of target successful.
今天仔细查看了硬件,看了下晶振好像焊接不好,重新焊接了晶振,使用Flash Programmer2烧写7*7的E:/TiPrj/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs/Debug/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs.out写进去一次,没有任何报错信息。
然后按照移植到5*5的帖子里的方法,弄了一个工程,再次烧写就不行了;后来重新打开一个7*7的原始工程,也烧写不进去了,如图报错。
莫名其妙又能烧写成功了。
>Initiate access to target: XDS-L2000O27 using 2-pin cJTAG.
>Reading file: E:/TiPrj/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs/Debug/gpiointerrupt_CC1310_LAUNCHXL_nortos_ccs.out.
>Start flash erase ...
>Erase finished successfully.
>Start flash programming ...
>Programming finished successfully.
>Start flash verify ...
>Skip verification of unassigned page: 4.
>Skip verification of unassigned page: 5.
>Skip verification of unassigned page: 6.
>Skip verification of unassigned page: 7.
>Skip verification of unassigned page: 8.
>Skip verification of unassigned page: 9.
>Skip verification of unassigned page: 10.
>Skip verification of unassigned page: 11.
>Skip verification of unassigned page: 12.
>Skip verification of unassigned page: 13.
>Skip verification of unassigned page: 14.
>Skip verification of unassigned page: 15.
>Skip verification of unassigned page: 16.
>Skip verification of unassigned page: 17.
>Skip verification of unassigned page: 18.
>Skip verification of unassigned page: 19.
>Skip verification of unassigned page: 20.
>Skip verification of unassigned page: 21.
>Skip verification of unassigned page: 22.
>Skip verification of unassigned page: 23.
>Skip verification of unassigned page: 24.
>Skip verification of unassigned page: 25.
>Skip verification of unassigned page: 26.
>Skip verification of unassigned page: 27.
>Skip verification of unassigned page: 28.
>Skip verification of unassigned page: 29.
>Skip verification of unassigned page: 30.
>Page: 0 verified OK.
>Page: 1 verified OK.
>Page: 2 verified OK.
>Page: 3 verified OK.
>Page: 31 verified OK.
>Verification finished successfully.
>Reset target ...
>Reset of target successful.
这个Skip verification of unassigned page: 26. 这些是跳过验证FLASH页吗。这个正常吗。
使用FLASH Programmer2烧写成功后,我又尝试用CCS写,不成功;
返回来再用FLASH Programmer2烧写,又不成功。
我试着强制擦除FLASH,报错。
>Create XBAL object failed: Session initialization failed
>XBAL EB pointer is null.
>Failed to create device object.
>Initiate access to target: using 2-pin cJTAG.
>Create XBAL object failed: Session initialization failed
>XBAL EB pointer is null.
>Failed to create device object.
>Initiate access to target: using 2-pin cJTAG.
>Create XBAL object failed: Session initialization failed
>XBAL EB pointer is null.
>Failed to create device object.
这个Skip verification of unassigned page: 26. 这些是跳过验证FLASH页吗。这个正常吗。
这是正常的,这种偶尔可以的基本上就是硬件有问题,有地方虚焊了或者连接不稳定