CC3235S CCS开发环境搭建

您好

关于CC3235S CCS开发环境搭建，有什么指导文档吗？（因为之前工程师离职了，到时搭建文件文档丢失，请谅解下）

另外一个问题，就是关于连接WiFI的问题

我们产品在仓库里，采用低功耗版本的例子，发现只有一般机器的概率连不上AP，仓库的AP都是一个SSID，类似Mesh自组网，在一个地方空中有10左右的相同的SSID，但是信号强度不同，从-33~-90dBm都有，所有的样机，测试手机AP,笔记本AP或是单独的路由器都没有问题，但是在仓库这种多一个相同的AP，就搞不定，请帮忙指导下，谢谢。

Kevin Qiu1：

快速入门：dev.ti.com/…/node
是否测试过最多超过几个station出现连不上的情况

,

user6234078：

公司内部没有环境，在客户现场看到这样的，客户那边都在运行，也不好让他们把AP关掉，但是手机和电脑都链接没有问题的。模块是在官网上购买的。

,

Kevin Qiu1：

你所说的仓库库AP是指路由器？这些路由器配置是否有差别？之前是否可以正常连接，还是说一直有问题。
如果有多个相同SSID的AP广播，在配置文件中未指定BSSID，则CC3235S将连接信号强度最强的AP。

,

user6234078：

之前没有测试过，他们AP是信锐NAC-3600，AP的SSID都是一样，然后一一个AP控制器NAC-6380，他们服务器统一分配IP地址，关键的问题，有一半的可以连接，有一半的不可以，程序和硬件都一样，只是不同wifi模块而已，配置文件中，都没有制定BSSID，但是他的确没有连接成功。 然后我用透传程序《at_commands_CC3235S_LAUNCHXL_freertos_ccs》不能连接的设备也能连接，但是用《power_measurement_CC3235S_LAUNCHXL_freertos_ccs》也不行，应该是软件上设置有些问题，我也不清楚这2个例子有什么区别。

顺便请教下AUTO CONNET 跟FAST CONNET 有什么区别，有相关的文档吗？

,

Kevin Qiu1：

Auto – This policy is similar to Auto connection in STA mode. The device starts the Wi-Fi Direct find
process, and searches for all Wi-Fi Direct profiles stored on the device, then tries to find the best
candidate to start negotiating. If at least one candidate is found, the connection attempt is triggered. If
more than one device is found, the best candidate according to profile parameters is chosen.
• Fast – In Wi-Fi Direct mode, this policy is the equivalent to the Wi-Fi Direct persistent group, but it has
a different meaning between GO and CLIENT. This option is very useful for making a fast connection
after reset, but it is dependent on the last connection state. This option is active only if there was a
successful connection before the device was reset, because the last connection parameters are saved
and used by the fast connection option. If the device was a CLIENT in its last connection (before reset
or remote disconnect) then following the reset, users must send the p2p_invite to the previously
connected GO, to perform a fast reconnection. If the device was the GO in its last connection (before
reset or remote disconnect) then following reset, users must reinvoke the p2p_group_owner, and wait
for the previously connected peer to reconnect to the device.
这个一半可以一半不可以是无差别的吗，将其他位置可以正常连接的移到不能连接处是否可以正常连接
若是无差别的怀疑是AP设置的问题

,

user6234078：

目前是随机的，我正在整理MAC地址，目前只能看到MAC地址有区别，其他都没有，位置都是一样的， 最强信号-30dBm。 关键官方的程序《power_measurement_CC3235S_LAUNCHXL_freertos_ccs》也不行， 但是在《at_commands_CC3235S_LAUNCHXL_freertos_ccs》就没有问题。所有都可以连接。

,

user6234078：

通过虚拟无线接入点（Virtual AP）技术，最多可提供32个ESSID，不同的SSID使用不同的认证接入方式和上网访问权限，不同SSID之间互相隔离的，可以对使用相同SSID的子网或同一个VLAN下进行终端二层隔离，保证用户数据安全。 应该是采取了这种技术的AP，连接就存在问题了。

,

Kevin Qiu1：

如果是固定数量Station可以连接，那就可能是AP对连接的Station有数量限制

,

user6234078：

能连接的都行，不能连接就是不行，不是Station的数量限制，同一批产品，有些是没问题，有些就连接不上。如果数量限制的话，应该是一批都不行呀。

,

Kevin Qiu1：

不好判断具体问题所在，最好先确定是硬件问题还是软件问题，所有模块程序都一样的话硬件出问题的概率大一些 CC3235S模块是从哪里购买的？是这个模块吗www.ti.com.cn/…/CC3235MODAS

,

user6234078：

是的，官方网站上买了1K。

另外咨询下关于在开发板上用CCS仿真的问题，目前遇到问题：CS_DAP: Error connecting to the target: (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 8.3.0.00003)
硬件是能烧录固件忙，但是无法仿真，请您给与指导，谢谢，

,

user6234078：

补充说明下，是在官网上购买的CC3235MODS, 数量为1K。

,

user6234078：

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

—–[Print the board config pathname(s)]————————————

C:\Users\ADMINI~1\AppData\Local\TEXASI~1\CCS\ccs920\0\0\BrdDat\testBoard.dat

—–[Print the reset-command software log-file]—————————–

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Aug 26 2019'.
The library build time was '13:34:49'.
The library package version is '8.3.0.00003'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

—–[Print the reset-command hardware log-file]—————————–

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

—–[Perform the Integrity scan-test on the JTAG IR]————————

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

—–[Perform the Integrity scan-test on the JTAG DR]————————

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

从此打印信息来看，仿真没有问题呀，为啥就是报错呢？

CS_DAP: Error connecting to the target: (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 8.3.0.00003)

,

Kevin Qiu1：

实际使用的CC3235MODS只是模组还是CC3235MODSF LaunchPad
SDK版本是多少？使用的是CCS9.2？看起来是固件不匹配

,

user6234078：

是模组（芯片为CC3235S） 

CCS是9.2，SDK用的是3.30.

,

Kevin Qiu1：

模组的话建议你先检查下硬件
仿真错误看下Cannot access the DAP部分：dev.ti.com/…/node

,

user6234078：

从文档的描述来看，说TCLK的高了，我把频率都设置成5.5MHZ,2.5MHz，1.25MHz,甚至200KHz都测试过，问题还是一样的。

,

Kevin Qiu1：

还有可能是硬件问题
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.
检查连线是否正确，下载器是否正常

,

user6234078：

跟硬件工程师也反复确认了，JTAG 就是用贵公司的开发板（CC3220 LaunchPad）,上面打印信息也没有问题，唯一错误提示是：
—–[Print the reset-command hardware log-file]—————————–

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

但是我能正常烧录，所以复位这块应该没有问题。

,

Kevin Qiu1：

这个是正常的，EMU0和EMU1没有接
www.ti.com.cn/…/sprui94.pdf