Wi-Fi Combo Forum Discussions
Hello, I am trying to understand if it is possible to use 2 of the WiFI boards and leverage them as a bridge. Is it doable and what OS should I use.
Show Lesswiced_rtos_delay_milliseconds(WIFI_SLEEP_TIME);
wwd_result_t host_rtos_delay_milliseconds( uint32_t num_ms )
{
//WPRINT_APP_INFO(("Timer Start\n"));
if ( ( num_ms * SYSTICK_FREQUENCY / 1000 ) != 0 )
{
if ( ( tx_thread_sleep( (ULONG) ( num_ms * SYSTICK_FREQUENCY / 1000 ) ) ) != TX_SUCCESS )
{
return WWD_SLEEP_ERROR;
}
}
else
{
uint32_t time_reference = host_platform_get_cycle_count( );
int32_t wait_time = (int32_t)num_ms * CPU_CLOCK_HZ / 1000;
//WPRINT_APP_INFO(("Timer Start\n"));
while ( wait_time > 0 )
{
uint32_t current_time = host_platform_get_cycle_count( );
wait_time -= (int32_t)( current_time - time_reference );
time_reference = current_time;
}
}
return WWD_SUCCESS;
}
When using the above function enters the sleep mode, using an external interrupt
Is there a way to wake-up ??
enviroment :
WICED v3.1.1
RTOS ThreadX v5.6
NetX v5.7_sp1
Show LessHello,
I want to interface 512MB micro SD card with WICED WiFi module. Any thoughts? Are there any suggested parts? Any libraries?
Thanks,
Raghu
Show LessHello!
I just finished a project with Broadcom WICED as below.
It's <C language style development-platform> for embedded IoT.
WizFi250-CSI(C Script Interpreter) for rapid-prototyping, DIY, IoT-startup or students.
I believe that this is helpful for rapid-prototyping, DIY, IoT-startup or students.
I wanted to do this project with open-source, but I could not do that because of WICED license.
If you have an interest in it, please contact to me.
Steve Kim
Show LessI'm having a strange issue when trying to test wifi connection and disconnection handling.
In my code I've written handlers for link_up and link_down.
In another thread, I'm pinging google.com.
It all works fine when in the first run, but when I turn my wifi off ( it goes into link_down handler) and than up(it goes in link_up handler), ping always times out.
What my guess is, there are some variables which needs to be reinitialized. I call
wiced_network_down(WICED_STA_INTERFACE);
in my link_down handler to make sure when next time my device connects to wifi router, it obtains proper ip address.
But still no luck with pinging google after wifi reconnect. I'm attaching my source code herewith
Show LessLooking into wiced_spi_* and platform_spi_* APIs and they don't look like thread safe to me, is that the case ? Also, it looks like current SPI implementation would not support multiples devices with difference settings such as clock frequency or bus mode, is that the case as well ?
Show LessI'm evaluating various Bluetooth modules. My specific application would transfer a small (~20 byte) packet between 2 endpoints. What would the typical latency be between (2) WICED modules? Thanks!
Show LessI am working on an application where the wiced module is required to sample an audio stream with its internal ADC. Due to the RTOS, this requires the use of the DMA and continuous conversion, setup for which is not supported in the wiced SDK.
Does anyone know if it is possible to initialize the ADC without using the API in the wiced SDK? I have tried to initialize the ADC like one would normally on the microcontroller, but it does not seem to compile and throws several errors. What do I have to alter to be able to initialize the ADC (with the DMA and interrupts) outside of the SDK?
Currently I am using the USI WM-N-BM-14, which has a STM32F2**, but if there is a way to implement this, I would assume it would be relatively similar across all wiced modules.
Show LessIs there a way to create a 38kHz signal from WICED platform for infrared packet transmission? I would normally prefer to do this sort of programming on a separate MCU which is not running any OS/framework so that I can have control over timings. Is there any specific way time-accurate functions can be implemented in such environments?
The idea is that there are two states for the output:
ON = toggled at 38kHz (freq changeable by the program)
OFF = Not toggled.
The communication will take place based on the lengths of ON and OFF. The timings need to be accurate to nearest microsecond.
The problem is that WICED has a thread-based OS, which may not be able to deliver exact timings. I thought of two ways this can be approached.
1) Using native MCU timers to achieve the above mentioned requirements (devboard based on STM32F2xx MCU)
2) Using SPI to transmit required data as a stream.
The problem with SPI is that I cannot define clock rate below 234kHz due to some prescalar limitation. And even if I use >235kHz clock speed, there is no guarantee that clock will always be at this speed (thus affecting the timings)
As for using Timer functionality of the MCU, I am not sure how to approach it. There is a STM32F2xx peripheral library which provides functions for output compare using TIM1 and TIM8. My approach in this case will be to use these Timers with DMA to output required waveform with accurate timings. Now the question is, are these timers being used by some other functions? Will defining them cause any problem on the system, and how to use them under WICED environment?
Also, has anyone been able to successfully use the Timers or implemented IR control on WICED platform? It would be quite helpful you can share your experience.
Message was edited by: Omair Suria
Show LessI am trying to run the snip scan as per the Quick Start Guide in the debugger.
The debugger comes up as expected with the first line of code - exactly as shown in the QSG. The only exception is that in the Console messages I get
stepi ignored. GDB will now fetch the register state from the target.
When I try to get the program to run (F8 - takes 2 continues to run) (having already set a breakpoint in the scan.c code) it stops at the end of for the vPortYieldFromISR routing in port.c. When i try to get the program to repeatedly stops here never advancing to the breakpoint in scan.c
Without a breakpoint set the code executes without stopping. I have tried other code snips with the same results
I think the configuration of the debugger is correct but the directions listed in the QSG seem to be for an earlier version and their are some minor differences as I installed the software
Show Less