Wi-Fi Combo Forum Discussions

How practical/possible is it to perform an OTA upgrade without using an external serial flash? Can the FR DCT, OTA app and Factory Reset App also be stored on the 1MB MCU flash? I am using STM32F205 as an MCU.

Hi All

Now I will share the experience for development environment building on Ubuntu OS based on EVK Board

The default SDK.tar.gz downloaded from Web can be used directly after unzipping. But the virtual Serial port can't be created By linux kernel of Ubuntu(Windows is ok). Also the wl tool was prebuilt for Window Only.  Located in path: WICED-SDK-3.1.1/apps/test/mfg_test/wl43362A2.exe, wl43341B0.exe, wl4390A1.exe and other three dll file. So the SDK can work perfectly on Windows in compare to work smoothly on Ubuntu. We wanna the sdk can work perfectly on Ubuntu also.

So we should fix tty issue first, Broadcom  EVK Board use FT2232HQ chip for programming. The chip can support USB->JTAG and USB->Serial. The usb device will be registered in kernel when we powered on the board. But the ttyUSB device can't be created.

First we will fix the ttyUSB issue, the FT2232 vid/pid was designed with brcm ID "0a5c 43fa". The kernel will not install driver successfully.

Let's fix it now:

Part A: ttyUSB issue

1 Create a new file:

# vi   /etc/udev/rules.d/73-broadcom-ftdi.rules

2 Paste the below info to edit window:

====================================================================================================

ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0a5c", ATTRS{idProduct}=="43fa", RUN+="/sbin/modprobe -b ftdi_sio"

ACTION=="add", SUBSYSTEM=="drivers", ENV{DEVPATH}=="/bus/usb-serial/drivers/ftdi_sio", ENV{MODALIAS}="usb:v0A5Cp43FAd0700dc00dsc00dp00icFFiscFFipFFin01" ATTR{new_id}="0a5c 43fa"

====================================================================================================

3 Press "Shift + :" and type "wq" to save and exit

4 run udev restart cmd:

# service udev restart

5 Unplug USB cable connected to Board in previous and re-plug again.

6 check the ttyUSB device. The ttyUSB device will created 2, ttyUSB[num] and ttyUSBX[num+1], e.g: ttyUSB0, ttyUSB1. The first one(ttyUSB0) is JTAG interface so we should by pass, and the second one(ttyUSB1) is the tty interface, we can use this.

7 We can run "openocd-all-brcm-libftdi -f ./tools/OpenOCD/BCM9WCD1EVAL1.cfg -f ./tools/OpenOCD/stm32f2x.cfg -f ./tools/OpenOCD/stm32f2x_gdb_jtag.cfg" to disconnect ttyUSB0. There is ttyUSB1 only now.

8 enter minicom

# minicom -D /dev/ttyUSB1

we can debugging via serial now, the function is same as window.

Part B: wl tool issue

In the apps/test/mft_test, we can find the wlxxx.exe and wlxxx.dll prebuilt tool for windows.

1 modify the Makefile : WICED-SDK-3.1.1/apps/test/mft_test/Makefile .  I have attached the modified Makefile.

2 Patched wl source:

Three files must be patched:

WICED-SDK-3.1.1/apps/test/mfg_test/43362A2/wl/exe/wlu_linux.c

WICED-SDK-3.1.1/apps/test/mfg_test/4390A1/wl/exe/wlu_linux.c

WICED-SDK-3.1.1/apps/test/mfg_test/43341B0/wl/exe/wlu_linux.c

Patch like below:

======================================================================

+#ifndef TARGETENV_x86

#ifndef TARGETENV_android

typedef u_int64_t u64;

typedef u_int32_t u32;

typedef u_int16_t u16;

typedef u_int8_t u8;

typedef u_int64_t __u64;

typedef u_int32_t __u32;

typedef u_int16_t __u16;

typedef u_int8_t __u8;

#endif /* TARGETENV_android */

+#endif

=======================================================================

3 enter into apps/test/mft_test/

# cd apps/test/mft_test/Makefile

# make

We will get Binary :

wiced_wlm_43362A2.so wl43362A2

wiced_wlm_43341B0.so wl 43341B0

wiced_wlm_4390A1.so wl4390A1

4 please build the test.mfg_test application and use wl tool test

5 wl test:

# ./apps/test/mfg_test/wl43362A2 --serial /dev/ttyUSB1 ver

5.90 RC230.255

wl0: Sep 10 2014 11:29:07 version 5.90.230.10 (WLTEST) FWID 01-2e323232

# ./apps/test/mfg_test/wl43362A2 --serial /dev/ttyUSB1 scan

# ./apps/test/mfg_test/wl43362A2 --serial /dev/ttyUSB1 scanresults

SSID: "jinyang"

Mode: Managed    RSSI: -61 dBm    SNR: 0 dB    noise: -92 dBm    Flags: RSSI on-channel     Channel: 6

BSSID: 8C:21:0A:A3:83:C6    Capability: ESS WEP ShortPre ShortSlot

Supported Rates: [ 1(b) 2(b) 5.5(b) 11(b) 6 9 12 18 24 36 48 54 ]

WPA:

    multicast cipher: AES-CCMP

    unicast ciphers(1): AES-CCMP

    AKM Suites(1): WPA-PSK

    No WPA Capabilities advertised

RSN:

    multicast cipher: AES-CCMP

    unicast ciphers(1): AES-CCMP

    AKM Suites(1): WPA-PSK

    Capabilities(0x0000): No Pre-Auth, Pairwise, 1 PTK Replay Ctr1 GTK Replay Ctr

802.11N Capable:

    Chanspec: 2.4GHz channel 6 20MHz (0x2b06)

    Control channel: 6

    802.11N Capabilities: SGI20 SGI40

    Supported MCS : [ 0 1 2 3 4 5 6 7 ]

wl tool can be used to test RF performance of BRCM WiFi chip. Such as Tx,Rx, Single Carrier Test.

OK, everything is ok now. WICED SDK can run perfectly on Ubuntu OS now.

Have a good experiencing with wiced sdk...

Regards

Harry

http://community.broadcom.com/servlet/JiveServlet/download/1843-4-5093/Wiced-SDK-3.1.2.pkg.zi

I used to flash my STM32F429 discovery board using Jlink base JTAG programmer, anyway after many code flashing and reflashing Now when I try to debug my program ,when I click the Start/Resume button I receive a SIGINT interrupt can't go further debugging.

Also if I use "snip.sntp_get_time-STDiscovery429_BCM43362-FreeRTOS-LwIP-SDIO JTAG=jlink-debug download"

IDE fails to program the device ,but If I use just "download run"I can flash the device.

What might be causing this issue to happen ?

Also Once I flash the code to board I have to power cycle it to get the new code running ,

Is this some kind of IDE bug or have I messed up the hardware?

Hi,

I wanted to test the webserver and followed the txt in the resources dir.

But I get the following error:

error: 'resources_apps_DIR_"appname"_DIR_"filename"_html' undeclared (first use in this function)

When I change the html file "top_web_page_top.html" into top.html in the appliance demo. Modify the makefile and http-page-database i get the same error.

Can someone give me a hint ?

We are using the ISM43341 product from Inventek as pin compatible upgrade from the ISM43362. How ever the platform files do not contain the same information regarding external GPIO, I2C and PWM outputs that we have been using in the past. I have updated the ISM43362 platform files to include additional definitions for the ADC pins and second I2C interfaces. I have attached these files. These definitions should be included in the new ISM43341 platform files.

Can you please provide an update to the files for the ISM43341 platform, When I requested this from Inventek they informed me that they are waiting for this information from Broadcom.....

Greg

I see that the appliance demo has 16 button and they activate the UART LED. How and which files would I program those 16 buttons to activate the GPIO ports. The intent control LED connected to GPIO output port.

Hi,

I can use "test.console-ISM43362_M3G_L44 download run" to compile the console application. I am trying  to use some wi-fi direct commands to mimic our real wifi-direct applications. Below are the issues

1. Starting a persistent group called DIRECT-test with WPA2 passphrase 12345678 on channel 1 using the command below

p2p_go_start p test 12345678 1

From Wi-Fi Direct settings on my Samusang Galaxy 3 tablet, I can see "WICED_P2P device". From Wi-Fi settings,I can also see "DIRECT-test1" wireless network. Does why the command "p2p_go_start" also create the "DIRECT-test1" wireless network, not only Wi-Fi direct "WICED_P2P device" network?

2.Once I tap the  "WICED_P2P device" on the tablet and the tablet can connect to  "WICED_P2P device" without any password. But I found that the Wiced device GO doesn't assign a IP address to the tablet.

3. How can I add the passord feature to allow only specific tablets to connect to "WICED_P2P device"?

Thanks,