I wanted to know what is the reason for continuous BLE disconnect  (on the peripheral side).

I am running wiced-3.5.1 and I have an Inventek 43341 module configured as a BLE peripheral. I sometimes see the BLE periodically go between disconnect and connect with a reason code of 62. This results in a bad user experience wherein a user with his/her iOS phone has to wait for a long time to connect to your product that acts as a BLE peripheral.

I wish to know what reason code 62 implies and is there a patch on 3.5.1 to resolve this known issue.

Thanks!

Regards,

Manish

I have abandoned trying to use my J-link in favor of an Olimex JTAG_ARM-USB-OCD-H dongle.

I am trying to configure WICED to use it but I am still getting the OpenOCD failure at the boot-load stage.

I have loaded the requisite drivers and my device manager shows…

WICED USB JTAG Devices

                Olimex OpenOCD AMR-USB-TINY-H

                Olimex OpenOCD JTAG ARM USB-TINY-H (Interface 0)

I am reasonably sure that my Olimex dongle is properly wired because I can start OpenOCD as follows:

openocd -f ./interface/ftdi/olimex-arm-usb-tiny-h.cfg

                 -f interface/ftdi/olimex-arm-jtag-swd.cfg

                 -f ./target/stm32f4x.cfg <NL>

Open On-Chip Debugger 0.9.0-rc1 (2015-04-24-22:09)

Licensed under GNU GPL v2

For bug reports, read

http://openocd.org/doc/doxygen/bugs.html

Info : FTDI SWD mode enabled

adapter speed: 2000 kHz

adapter_nsrst_delay: 100

none separate

cortex_m reset_config sysresetreq

Info : clock speed 2000 kHz

Info : SWD IDCODE 0x2ba01477

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

You may have noticed, I am using the SWD interface and not JTAG.  I have the Olimex SWD adapter in between the dongle and the target.

In addition, I can start a PuTTY telnet session and manually interact with OpenOCD on the target board.

First questions:

1. Must I start OpenOCD prior to running WICED ? 
2. If so is so is there a way to make WICED do that for me?
3. Is there something I need to do in WICED since I am using the SWD interface?

In WICED my Make Target entry is:

MyProgram CEL_WB4343WF3SP2  JTAG=Olimex_ARM-USB-TINY-H download

Next questions:

What settings do I need in each of the debug configuration tabs?

In Main I have:

C/C++ Applictions:   build/eclipse_debug/last_built.elf

Project: WICED_SDK

In the Debugger Tab I have:

<path> \WICED\WICED-SDK-3.5.2\WICED-SDK\tools\ARM_GNU\bin\Win32\arm-none-eabi-gdb.exe

Under remote target, in the JTAG device pull-down I chose OpenOCD (via pipe)

In the Startup Tab

In the checked box under Halt I have:

add-symbol-file build/eclipse_debug/last_bootloader.elf 0x8000000

This worked before I switched to the Olimex dongle and was using a Broadcom BCM Eval module prior to my target hardware.

"Load Image" is checked using project binary.

The first entry of the openocd_log.txt file after a download attempt is...

Open On-Chip Debugger 0.9.0-00029-gafd5db2-dirty (2015-05-29-18:47)

Licensed under GNU GPL v2

For bug reports, read

  http://openocd.org/doc/doxygen/bugs.html

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

Warn : Using DEPRECATED interface driver 'ft2232'

Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...

Error: unable to open ftdi device: device not found

Sorry for all the exposition but I wanted to give as much information as possible to perhaps reduce some back and forth.

Any help convincing WICED to download my compiled program into my target via the Olimex dongle will get you included in my will.

Thanks

Hi...

I am using this UART Setup and UART Messages Over Webpage  code in wiced sdk 2.4.0 , i want to receive hex-values  through uart and display the hex-value or equivalent decimal value in a webpage , when i tried to display i am not getting actual data.

also i tried this  to display data on console-Teraterm

{

unsigned char test_data[16] = {0xD0,0xD1,0xD2,0xD3,0xD4,0xD5,0xD6,0xD7,0xD8,0xD9};

wiced_uart_transmit_bytes( WICED_UART_1, test_data, sizeof(test_data));

}

same issue...Please help me...Thank you...

I'd like to confirm  that does BCM4343W have EAP-TLS enterprise security?

In datasheet of BCM4343W, it is only said that:

Security:

– WPA and WPA2 (Personal) support for

powerful encryption and authentication.

– AES in WLAN hardware for faster data

encryption and IEEE 802.11i compatibility.

– Reference WLAN subsystem provides Cisco

Compatible Extensions (CCX, CCX 2.0, CCX

3.0, CCX 4.0, CCX 5.0).

– Reference WLAN subsystem provides Wi–Fi

Protected Setup (WPS).

it seems that there is no enterprise security in BCM4343W.

I have installed the SDK named ‘WICED-SDK-3.7.0-IDE-Installer.exe’ on windows xp computer. But the SDK can not be successfully compiled on windows xp. Does anyone know how to solve it ?The error message is as follows:

07:00:27 **** Build of configuration Default for project WICED-SDK ****

"D:\\CY-WIFI\\WICED-SDK-3.7.0\\WICED-SDK\\make.exe" snip.scan-BCM943362WCD4

MAKEFILE MAKECMDGOALS=snip.scan-BCM943362WCD4 OTA2_SUPPORT is disabled

Building Bootloader

In file included from WICED/platform/MCU/STM32F2xx/../wwd_resources.c:15:0:

./platforms/BCM943362WCD4/./wifi_nvram_image.h:45:9: error: expected ',' or ';' before 'NVRAM_GENERATED_MAC_ADDRESS'

         NVRAM_GENERATED_MAC_ADDRESS                                          "\x00"

         ^

make.exe[3]: *** [build/waf.bootloader-NoOS-BCM943362WCD4/Modules/./WICED/platform/MCU/STM32F2xx/../wwd_resources.o] Error 1

make.exe[3]: *** Waiting for unfinished jobs....

make.exe[2]: *** [main_app] Error 2

make.exe[1]: *** [bootloader] Error 2

tools/makefiles/standard_platform_targets.mk:54: recipe for target 'bootloader' failed

Makefile:286: recipe for target 'main_app' failed

make: *** [main_app] Error 2

07:01:11 Build Finished (took 43s.765ms)

Hello

I use segger jlink to download on wiced sdk 3.4.0.  in windows 10 64 bit

I saw this tread https://community.broadcom.com/message/8850#8850

Jlink support for wiced sdk not working.

and followed

1.download libusb driver - link (http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/libusb-win32-bin-1.2.6.0.zip/download)
2.extract

3.run the app "inf-wizard" in libusb-win32-bin-1.2.6.0\bin
4.select jlink
5.complete driver installation.

6.Changethe line in the file wiced_toolchain_common.mk from:

    JTAG ?= BCM9WCD1EVAL1

    to

    JTAG ?= jlink

7.add the parameter JTAG=jlink to the make target.

8.Try loading with wiced sdk, now it should work.

And I add {   reset_config trst_and_srst srst_push_pull srst_nogate connect_assert_srst } in jlink.cfg

but still failed on download.

Here is the openocd_log :

Open On-Chip Debugger 0.9.0-00029-g9f797a3-dirty (2015-09-16-09:22)

Licensed under GNU GPL v2

For bug reports, read

  http://openocd.org/doc/doxygen/bugs.html

trst_and_srst separate srst_nogate trst_push_pull srst_push_pull connect_assert_srst

adapter speed: 1000 kHz

adapter_nsrst_delay: 100

Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.

jtag_ntrst_delay: 100

Warn : target name is deprecated use: 'cortex_m'

jtag_init

Error: J-Link command 0x01 failed (0)

Error: J-Link command EMU_CMD_VERSION failed (0)

Info : J-Link JTAG Interface ready

Error: J-Link command 0xdd failed (0)

Error: J-Link command 0xdf failed (0)

Error: J-Link setting speed failed (0)

Error: usb_bulk_write failed (requested=6, result=0)

Error: jlink_tap_execute failed USB io (-107)

Error: J-Link setting speed failed (0)

After that I found the thread

https://community.broadcom.com/message/19009#19009

He had same openocd_log as mine, but no answer for him.

Could any one give me any suggestion to solve this issue ?

Thank you.