CC3351: CC3351 BLE scanning and Wi-Fi questions

Hi Shuyang, 

Issues #2 and #3 have been reported, so we have addressed these internally. We have engineering release of these available on mysecure, while the public version will be available at the end of this month.

Regarding the first issue, can you provide the steps you are using to bring up the BLE connection? 

Hi Sabeeh,

BLE has two cmd files in the log directory, which are all the actions and results I performed after loading the driver.

Added before "scan on" command -->Menu scan -->Transport le -->Back

Then it can be swept to the opposite cc3351 device.

However, the problem now is that my mobile phone can scan to the cc3351 via the BLE assistant(APP). However, many other colleagues cannot scan the cc3351 using the same APP. I used a Bluetooth device that supports dual mode B to call  btmgmt -i hci0 off to emulate a ble device. And the rest of the operation is the same as calling cc3351. My colleague can scan this device B with a ble assistant.

I saw the cc3351 and the broadcast packet of device B through my mobile phone's ble assistant, I wonder if there is a problem with my settings, which has caused the cc3351 cannot be scanned by some devices?

The screenshot of the previous attachment shows the cc3351 broadcast packet captured by the ble assistant, which is attached to Device B broadcast packet that can be scanned by colleagues normally.

Below are the information of the environment:

Operating System Environment:

1.openwrt+bluez5.66

2.cc3351 Official yocto file system

The same kernel for both systems, am6231 cpu + 6.1.83kernel

Only insmod and echo 1 > ble_enable are executed after power-on

In the next step. This is followed by the operations in the cmd file in the previous log.

Hi Shuyang,

Your steps are a little unclear to me for getting the BLE advertising is a little confusing to me. Could you perhaps follow these commands for the getting the device to advertise? I'm not sure how this is from OpenWRT:

echo 160 >> /sys/kernel/debug/bluetooth/hci0/adv_min_interval
echo 160 >> /sys/kernel/debug/bluetooth/hci0/adv_max_interval

btmgmt -i hci0 info

btmgmt -i hci0 power off

btmgmt -i hci0 le on

btmgmt -i hci0 connectable on

btmgmt -i hci0 debug-keys off

btmgmt -i hci0 sc on

btmgmt -i hci0 bondable on

btmgmt -i hci0 pairable on

btmgmt -i hci0 privacy off

btmgmt -i hci0 name cc33xxble

btmgmt -i hci0 advertising on

btmgmt -i hci0 power on

hcitool -i hci0 lerlon