Wi-Fi Combo Forum Discussions

Hi,

I am using WICED SDK 3.1.2 to develop the product that periodically sends the data to the server over the WIFI. We need the system date and time. Is there any API for the system date and time? we need your urgent help!

Thanks in advance

When we present scan results to the user, we need to provide a good/marginal link indication. The wl_bss_info structure contains a phy_noise value that is not returned in the scan results created by scan_result_handler(). Is the phy_noise populated? Can we use it as a noise floor indicator? What is the range?

Mike

Hi all,

     I want to use MFI and Bluetooth to contral a device together.I use apps_homekit examples.If only use mfi, it work.But when I add "wiced_bt_stack_init" after "wiced_init", it generate "WAC failure".  If I remove defined "USE_MFI=1", it will stop at function "wiced_homekit_start". So can I use ble with MFI? Or some docments and examples help?

Hi,

I've tried to get that information from the Web, but couldn't find any defenitive answer.

Let's say that I'm developing a device "A". That device has several attributes that can be modified and queried and some states that could be toggled by the user. ( i.e. turn on the light, etc. ).

Assuming that the device would have the apple auth chip, and that the software for the device would be included in the device's firmware - would the end user be able to use the device *without* installing any device-specific software ?

( and by "use" I mean to take advantage of the fact that the device is more expensive, etc. )

The reason I'm asking is that I'm trying to determine the "value" of the MFi feature for my application. I'm sure that with some accompanied software, a device could be accessed. but I was wondering if I could avoid having a iOS-specific application code of being written.

Thanks!

Tsachi

Hi.

I wish to know a work around for this and when will it be supported?

Currently, WICED SDK 3.3.1 claims to support BLE but misses out on the most important and basic requirement of being able to advertise Vendor Specific 128-bit UUID for custom services and characteristics.

This issue was identified while trying to customize the ble_proximity_reporter application. See question posted on the forum yesterday ...Wiced SDK 3.3.1: Customizing the ble proximity reporter for Vendor Specific Services and Attributes

I am still waiting on a workaround or an answer as to how to fix it or when will the fix be available?

Thanks!

Regards,

Manish

Description:

1.      Name of the Board: WICED Eval board ­ BCM943362WCD4_EVB

2.      Board Revision: 01

3.      Is this issue reproducible in WICED evaluation board: Yes

4.      WICED SDK Version in which the issue is seen: 3.3.1

5.     Step-by-step procedure to reproduce the issue:

        ./make snip.scan-BCM943362WCD4-debug download run
6.     How easy is it to reproduce the issue?: Every time

I get following error from OpenOCD when downloading:

Downloading Bootloader ...

**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****

Downloading DCT ...

**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****

Downloading Application ...

**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****

I am using Linux:

Linux linux-VirtualBox 3.2.0-79-generic-pae #115-Ubuntu SMP Thu Mar 12 14:33:25 UTC 2015 i686 i686 i386 GNU/Linux

This works with WICED SDK 2.4.1.

Hi.

I am trying to use the aes_* APIs from the wicked_security.h ...

Is there a init-encrypt-decrypt flow or routine that I can repurpose to get the AES going on the BCM943341WCD.

WICED SDK 3.3.1 does not have any examples, but if there is something available in other SDKs please let me know.

hi ,

  sometime, when I create a timer event by wiced_rtos_register_timed_event() function,an error appear in the openocd_log.txt file. but I delete the timer event ,the error disappear. Which reasons could cause this problem ?? in SDK 3.1.2,  platform BCM9WCDUSI09

Info : only one transport option; autoselect 'jtag'

trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst

adapter speed: 1000 kHz

adapter_nsrst_delay: 100

jtag_ntrst_delay: 100

Warn : target name is deprecated use: 'cortex_m'

jtag_init

Info : J-Link initialization started / target CPU reset initiated

Info : J-Link V9 compiled Oct 28 2014 19:25:34

Info : J-Link caps 0xb9ff7bbf

Info : J-Link hw version 90000

Info : J-Link hw type J-Link

Info : J-Link max mem block 71184

Info : J-Link configuration

Info : USB-Address: 0x0

Info : Kickstart power on JTAG-pin 19: 0xffffffff

Info : Vref = 3.304 TCK = 1 TDI = 0 TDO = 0 TMS = 0 SRST = 0 TRST = 0

Info : J-Link JTAG Interface ready

Info : clock speed 1000 kHz

Polling target stm32f2xxx.cpu failed, GDB will be halted. Polling again in 100ms

Info : JTAG tap: stm32f2xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)

Info : JTAG tap: stm32f2xxx.bs tap/device found: 0x06411041 (mfg: 0x020, part: 0x6411, ver: 0x0)

Info : Selecting JTAG transport command set.

Info : AP INIT COMPLETE

Info : stm32f2xxx.cpu: hardware has 6 breakpoints, 4 watchpoints

Info : JTAG tap: stm32f2xxx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)

Info : JTAG tap: stm32f2xxx.bs tap/device found: 0x06411041 (mfg: 0x020, part: 0x6411, ver: 0x0)

Info : Selecting JTAG transport command set.

Info : AP INIT COMPLETE

Polling target stm32f2xxx.cpu succeeded again

Info : Selecting JTAG transport command set.

Info : AP INIT COMPLETE

Info : accepting 'gdb' connection from 3333

Info : device id = 0x20036411

Info : flash size = 1024kbytes

Warn : acknowledgment received, but no packet pending

Info : Auto-detected RTOS: ThreadX

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Warn : stepi ignored. GDB will now fetch the register state from the target.

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: Not implemented: target_get_gdb_fileio_info_default

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: Not implemented: target_get_gdb_fileio_info_default

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)

Error: address + size wrapped(0xfffffffe, 0x00000004)