Wi-Fi Combo Forum Discussions
Please could you point me to at where I can find what address space is occupied by WAF on external flash?
Just to clarify: "As of WICED-SDK 3.1.1, WICED Application Framework (WAF) supports loading and storing of multiple
* application binaries in the external serial flash. Up to 8 binaries are supported..."
Basically, where is a memory layout map of where WAF stuff will be located on external flash?
My aim is to port and put a Flash File System (thinking of YAFFS) somewhere under or above WAF. And I need to know how addresses are set so I can reserve space for YAFFS so that it does not overlap with WAF.
Thanks in advance.
In SDK 2.4.1 the WLAN Firmware image resides in the wifi_image.c file in a form of a C style array.
On SDK 3.1.0 this file does not exists. From looking at the code I see the whole mechanism was changed and it is supplied as a bin file placed somewhere in the Flash memory and loded to the chip from there.
I also could see that the Firmware has some kind of a header that specify the size of the FW and maybe some other things.
I could not however find this structue definition anywhere in the code.
Since we do not work with a supported platform I need this to be able to load the new firmware so I can check new functionality.
Please provide this structure definition and any other info that I need to use the new Firmware of SDK 3.1.2.
We have developed a board based on the ISM44362 and included a 16 Mbit external serial flash (SST25VF016B). I am working on the code for OTA updates to the application running on the board. I want to store my updated app on the external serial flash, then reboot the board to install the new application as is shown in the OTA example code.
I reviewed the wiced_ota_server.c code, in particular the section where wired_framework_app_open() is called, along with getting/setting sizes. This code has been implemented in my application, followed by calls to wiced_framework_app_write_chunk() to store chunks of the OTA received application data. I am seeing failures when I call wiced_framework_app_write_chunk().
I have previously erased the serial flash using sflash_chip_erase(). Tracing through the wiced code, I observe that in wiced_apps_get_size(), there is a call to sflash_read to read the app header. The app header contains "1's" in all data fields (probably due to the erase), and nonsensical values are calculated for addresses and sizes in various functions inside of wiced_apps_common.c because of this.
Is there a way to format/initialize the serial flash to make it look like a multi-application file system?
What is the right way to erase an existing app and write a new one in its place (i.e. when I update from v1.0 to v2.0 to v3.0 etc.)
I am running Wiced SDK 3.1.2.
I'm new to WICED IDE programming, i installed the WICDE IDE and 3.1.0 SDK.
Building the snip.scan BM943362WCD4 is ok.
but to start debugging and (extern) run the project.
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. ****"
FTDI drivers are installed. this is a windows 7 64 bit computer.
openocd-all-brcm-libftdi.exe is in de sdk.
in openocd_log.txt i get the following.
Open On-Chip Debugger 0.8.0-dev-00139-g4dfe8d5-dirty (2013-08-22-12:22)
Licensed under GNU GPL v2
For bug reports, read
Info : only one transport option; autoselect 'jtag'
trst_and_srst separate srst_nogate trst_push_pull srst_push_pull connect_assert_srst
adapter speed: 1000 kHz
Warn : target name is deprecated use: 'cortex_m'
Error: unable to open ftdi device: device not found
Runtime Error: ./tools/OpenOCD/stm32f2x-flash-app.cfg:10:
in procedure 'script'
at file "embedded:startup.tcl", line 58
in procedure 'init' called at file "./tools/OpenOCD/stm32f2x-flash-app.cfg", line 10Show Less
I have an application in which the 43362 will primarily be used in SoftAP mode. Does the WICED SDK support the following while in SoftAP mode?
1. WEP security (in addition to WPA/WPA2)
2. MAC Filtering
I've noticed other forum discussions about WEP as a client, but nothing conclusive regarding WEP for SoftAP applications.
we are trying to port the WWD driver from the SDK into an existing software platform (NWstack, RTOS and multiple other modules). We are planing to implement our own SPI communication driver for the BCM43362.
I have checked the broadcom website but I have not found any specification of the IOCTL and IOVAR send via the SPI interface yet. Is there any documentation apart from the source code that describes the I/O Variables (IOVar), the IOCTL commands and the register interface. The data sheet only contains some basic information regarding the SPI Protocol.Show Less
I am working with the Sn8200 discovery wifi board. My board came with a pre-loaded softwar Following instructions from the Discover Wi-Fi Users manual V1.5, I was able to successfully establish a client-server connection between my PC and the sn8200 board. On the PC side I used the testserver.exe application from Murata. Now I am trying to do the same using my own script on the PC side but I am not able to make the connection. Is it possible to see the source code of the binary(SN8200-SNIC-UART-03-37191.bin) that has been loaded into my sn8200 board? Also, I am not able to detect my sn8200 as a com port on my windows machine? Can anybody give me some pointers for these?
Thanks and Regards,
I am using BCM943362WCD4, which uses STM32xxx MCU and SDK 3.1.1
I am trying to enable DMA for SPI master and it just does not work. Transfer times out trying to send out first byte. Has DMA even been tested ? Line 394, I can read:
dma_init.DMA_PeripheralBaseAddr = ( uint32_t )spi->port->DR;
This is obviously wrong, passing port DR register content instead of DR register address, I replaced by
dma_init.DMA_PeripheralBaseAddr = ( uint32_t )&(spi->port->DR);
But that does not change anything, timeout again.
I'll keep reviewing the code, but it would be nice to have some help on that topic, has anybody enabled DMA for SPI master ?
I am working on to design schematic to build proto boards using WICED WIFI modules. I am bit stuck on to decide what is needed for programming the module. If anybody has suggestion, please provide. I would like to know how to debug the final boards (using emulator or something) and what facility should be provided on the board.