新人求助:关于OADTarget例程调试问题
错误如下图所示,求大手指帮个忙啊!

Debug log的信息能否贴一下?
请看一下Debug log是不是这个报错:https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/p/404982/1435100#1435100
Viki Shi
Debug log的信息能否贴一下?

先编译BIM,再编译cc2640stack,最后编译CC2640APP.
另,需要安装python和一些脚本。看OAD文档8.1
8.1 Installing Python
Python scripts are used to create hex and bin files from project output. Make sure Python 2.7.x is installed and added to your system path environment variables. Also required is the Python IntelHex script hex_merge.py, freely available on the web at https://launchpad.net/intelhex/+download. The expected location of the script is “C:\Python27\Scripts\” as the post build procedure assumes the script is there.
For IAR, the python command can be found in Project Options -> Build Actions -> Post-build command line. For CCS, the python command can be found in Project Options -> CCS Build -> Steps -> Post-build steps. Change the above commands to include the full path of the python executable if a post-build issue occurs due to file path issues. See 8.3 for an example.
NOTE: To build the hex file
TY
另,需要安装python和一些脚本。看OAD文档8.1
8.1 Installing Python
Python scripts are used to create hex and bin files from project output. Make sure Python 2.7.x is installed and added to your system path environment variables. Also required is the Python IntelHex script hex_merge.py, freely available on the web at https://launchpad.net/intelhex/+download. The expected location of the script is “C:\Python27\Scripts\” as the post build procedure assumes the script is there.
For IAR, the python command can be found in Project Options -> Build Actions -> Post-build command line. For CCS, the python command can be found in Project Options -> CCS Build -> Steps -> Post-build steps. Change the above commands to include the full path of the python executable if a post-build issue occurs due to file path issues. See 8.3 for an example.
NOTE: To build the hex file
那些脚本我已近安装过了
你默认的代码编译都报错吗?
TY
你默认的代码编译都报错吗?
这个错误不是出现在编译的时候,而是调试的时候。 其他例程都没有问题
TY
你默认的代码编译都报错吗?
这个问题是出现在调试的时候,编译的时候是没有问题的。其他例程都能够调试
哎呦喂,你是用的xds110吗?你用的什么板子?你的仿真器是xds100V3还是xds110,还是别的什么?
TY
哎呦喂,你是用的xds110吗?你用的什么板子?你的仿真器是xds100V3还是xds110,还是别的什么?
恩 xds100
我用的xds110 板子是cc2650 sensortagTY
哎呦喂,你是用的xds110吗?你用的什么板子?你的仿真器是xds100V3还是xds110,还是别的什么?
IAR里把仿真器设置城xds110,默认是xds100V3

TY
IAR里把仿真器设置城xds110,默认是xds100V3
这个我是这样设置的
用flashprogrammer2能检测到芯片吗?
TY
用flashprogrammer2能检测到芯片吗?
可以检测到 也能够烧写程序
我试过了,确实是有这个错误。我认为主要是工程会把BIM,APP,STACK 合成一个hex文件。即包含了三部分的代码。我们通常不会修改OADTarget代码,
直接烧写那个hex就可以了,他是用于升级的常驻代码。
TY
我试过了,确实是有这个错误。我认为主要是工程会把BIM,APP,STACK 合成一个hex文件。即包含了三部分的代码。我们通常不会修改OADTarget代码,
直接烧写那个hex就可以了,他是用于升级的常驻代码。
我这里有一大堆的不懂,比如cc2650只有128k的可编程区,但是我的OAD_merge.hex有239k却也能烧写成功,也能够进行空中下载
1. 那是hex文件,hex文件是带地址的。当然大啦,百度一下hex文件的格式。
2. 实际的文件大小是看bin文件的大小
3. 你要先看oad的文档,那个讲得很清楚啊。
