Wi-Fi Combo Forum Discussions

(Using standard BCM943341 Evaluation Board, with WICED 3.1.1).

I want to be able to re-flash the application area and reboot with the new firmware.  I already would have the new application .elf file available in a large buffer (having received it eariler via a serial connection).

Now, I know that there is the 'ota_fr' example and I've studied this in some detail (including its connection to the 'waf' routines to work with the on-board flash memory).  However, it uses a full blown HTML script and the WICED web server.  I just want to update (erase/write) the current application that I already have waiting in a buffer.

Does anyone have a sample piece of code to do this?

-- Robert

I plan to use USART3 on the ISM43362 which uses the STM32F205 processor.  I modified the platform.c and platform.h files to include the correct pins, interrupts, DMA channels and streams.  I also had to update the interrupt priorities function:

void platform_init_peripheral_irq_priorities( void )

{

    /* Interrupt priority setup. Called by WICED/platform/MCU/STM32F2xx/platform_init.c */

    NVIC_SetPriority( RTC_WKUP_IRQn    ,  1 ); /* RTC Wake-up event   */

    NVIC_SetPriority( SDIO_IRQn        ,  2 ); /* WLAN SDIO           */

    NVIC_SetPriority( DMA2_Stream3_IRQn,  3 ); /* WLAN SDIO DMA       */

    NVIC_SetPriority( DMA1_Stream3_IRQn,  3 ); /* WLAN SPI DMA        */

    NVIC_SetPriority( USART1_IRQn      ,  6 ); /* WICED_UART_1        */

    NVIC_SetPriority( USART2_IRQn      ,  6 ); /* WICED_UART_2        */

    NVIC_SetPriority( USART3_IRQn      ,  6 ); /* WICED_UART_2        */

    NVIC_SetPriority( DMA2_Stream7_IRQn,  7 ); /* WICED_UART_1 TX DMA */

    NVIC_SetPriority( DMA2_Stream2_IRQn,  7 ); /* WICED_UART_1 RX DMA */

    NVIC_SetPriority( DMA1_Stream6_IRQn,  7 ); /* WICED_UART_2 TX DMA */

    NVIC_SetPriority( DMA1_Stream5_IRQn,  7 ); /* WICED_UART_2 RX DMA */

    NVIC_SetPriority( DMA1_Stream3_IRQn,  7 ); /* WICED_UART_3 TX DMA */

    NVIC_SetPriority( DMA1_Stream1_IRQn,  7 ); /* WICED_UART_3 RX DMA */

    NVIC_SetPriority( EXTI0_IRQn       , 14 ); /* GPIO                */

    NVIC_SetPriority( EXTI1_IRQn       , 14 ); /* GPIO                */

    NVIC_SetPriority( EXTI2_IRQn       , 14 ); /* GPIO                */

    NVIC_SetPriority( EXTI3_IRQn       , 14 ); /* GPIO                */

    NVIC_SetPriority( EXTI4_IRQn       , 14 ); /* GPIO                */

    NVIC_SetPriority( EXTI9_5_IRQn     , 14 ); /* GPIO                */

    NVIC_SetPriority( EXTI15_10_IRQn   , 14 ); /* GPIO                */

}

I noticed that the entry for SPI DMA is DMA1_Stream3 and this is not correct for SPI1.  SPI1_RX is on DMA2_Stream0.  I compared this function to that of BCD943362 which is a similar module and the interrupt priorities are the same.

I would ask anyone more familiar with the STM32F205 to review and let me know the correct entry.  If it is correct as is, then I need to decide if it is priority 3 or 7 since USART3 uses that same DMA and stream but different channel.

Thanks,

Tom

Greetings!

In normal 'sockets' programming, after creating a socket, you then use a 'bind' call with "any port" specified so that you can receive a request for a TCP connection from a remote host regardless of the TCP Port used.  This would seem to be the case with the equivalent WICED WiFi TCP calls, since we have a 'create' and a 'bind' with WICED_ANY_PORT.

However, the normal 'listen' call then specifies that socket and (typically) the depth of the incoming queue (say '5').  However, with WICED, the TCP Port is required in the 'listen' command as the 2nd parameter.  Now, this negates the 'any port' specification of the port!

So, the question is:  how do I create a listen (and a following 'accept') for an incoming TCP connection request from ANY port?

Hello,

The document WICED-Application-Framework-April-2013.pdf (slide 10) mentions a Pull method where the device automatically upgrade itself over a nw connection.

Can someone gives more details on the procedure ?

Is it possible to get sample code ?

Thanks

Lionel

Hi all,

I have my own board equipped with SSB-WM-N01. I don't use FT2232HL because the board should be small. Instead. I use J-link to download and debug with OLIMEX-ARM-USB-TINY-H and also use CP2102 for USB-toUART. I already have SSB-WM-N01 platform file and I confirmed that the download is sucessful with OLIMEX-ARM-USB-TINY-H JTAG in BCM943362WCD4 EVAL board.

However, when I try to use J-Link to download an app to SSB-WM-N01 board, the following error is shown

"**** 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.

My question is the FT2232HL should be used for downloading and if not, what the next step is to figure out this error.

Best regards,

Yongsun

Hi @ all,

I'm currently porting the SDK v3.0.1 (for SN8000) in my project and have no OS on board. Therefor, I need a non-blocking mode for the SDK-API. My software will use the WLAN modem in a station mode and try to connet to an AP.

Using wwd_wifi_join() (wwd_wifi.h) causes a delay of ~3s, during this time my software is blocked.

I also tried wwd_wifi_join_specific(), but no difference. Tested with several APs and distances, but no difference.

I've added some debugouts to get an overview about the internal behavior. As I can see, the parameters (key, security type, ...) are transmitted to the WLAN module. After the SSID was send, the WICED driver waits for an join-result.

Is there any option/configuration/API (e. g. compiler setting) to make this process asynchon?

Can I register an callback for the join result and let the wwd_wifi_join() return immediately?

Thanks for helping,

Jan Gottwald