Wi-Fi Combo Forum Discussions

Dear Sir,

Please provide me Complete Documents Regarding how to Create new Projects

in WICED IDE.And Also How to Compile and Debug

Dear Sir,

I am troubling in WICED IDE ,I build the just clicking on make target of respective project its working the code is also

downloading in CYBT343026EVAL kit but when i want to change name of BLE module or just i want to Compile the project by opening .C file

of Hello Sensor the many errors are coming also the device name getting updated

i did proper installation by referring documents

i also refers  many documents regarding this but not getting enough information to resolve this p[problem

please try to figure it out and let me know  why its coming

as soon as possible my development taking long time because of this problem

Please find attached Image for proper Clarification

I did many changes depend on video available on Site of Developer community

but still problem is not resolved

I want to develop this product as soon as possible but somewhere i stuck here solving problem

of IDE not Solving our logic.

Hello,

I have CYW943907AEVAL1F evaluation kit. I was wondering if we can use this as wifi module with the raspberry pi compute module IO board. I'm thinking these are pins to use. Please let me know if this is the right path to obtain wifi on the raspberry pi using this kit. Also can I use any other interface to get the wifi working other than SDIO?

Is there a linux driver support for the cyw43907 module, to work with raspbian?

Thanks,

Santosh

Hi:

  I find there are two sets of  timer API supported by the SDK,but I don't know which  one is more accurate for timing

one  set timer API is located at the wiced_timer.h:

wiced_result_t wiced_init_timer( wiced_timer_t* p_timer, wiced_timer_callback_t TimerCb,

                                 TIMER_PARAM_TYPE cBackparam, wiced_timer_type_t type);

wiced_result_t wiced_start_timer(wiced_timer_t* p_timer, uint32_t timeout);

/** Stops the timer
*
* @param[in]    wiced_timer_t           :Pointer to the timer structure
*
* @return       wiced_result_t
*/

wiced_result_t wiced_stop_timer(wiced_timer_t* p_timer);

/**  Checks if the timer is in use
*
* @param[in]    p_timer             :Pointer to the timer structure
*
* @return   TRUE if the timer is in use and FALSE if the timer is not in use
*/
wiced_bool_t wiced_is_timer_in_use(wiced_timer_t* p_timer);

/** Deinitialize the timer instance and stops the timer if it is running
*
* * @param[in]    p_timer           :Pointer to the timer
*
* @return   wiced_result_t
*/
wiced_result_t wiced_deinit_timer(wiced_timer_t* p_timer);

another is located at clock_timer.h:

extern void osapi_createPeriodicTimer(OSAPI_TIMER *timer,
                  void (*timerCallback)(INT32 arg, UINT32 overTimeInUs),
                  INT32  arg,
                  UINT32  interval);

//! Create a timer.
           void osapi_createTimer(OSAPI_TIMER *timer, void (*timerCallback)(INT32 arg, UINT32 overTimeInUs), INT32 arg);

//! Activates an OSAPI timer.
//! If this timer can be a wakeup source, we should call
//! osapi_setTimerWakeupSource after osapi_createTimer and before
//! osapi_activateTimer. Interval here is in micro seconds.
              extern void osapi_activateTimer(OSAPI_TIMER* timer, UINT32 interval);

//! Reports if timer is running/pending or not.
#define osapi_is_timer_running(timer) ((timer)->flags&OSAPI_TIMER_ACTIVE)

//! Marks the timer as being a wake up source.
//! This may be called before the call to osapi_activateTimer() to mark
//! the timer as a wake up source.
        extern void osapi_setTimerWakeupSource( OSAPI_TIMER* timer, UINT32 can_be_wakeup_source);

//! Remove the timer from timer list.
//! It will return 0 if successful
//! It will return 1 if timeout callback already called.
//! It will return 2 otherwise.
         extern UINT32 osapi_deactivateTimer(OSAPI_TIMER* timer);

//! Query timer for remain time until timeout.
//! This function will query current timer, return microseconds from now until it timeout
           extern UINT32 osapi_getTimerRemain(OSAPI_TIMER* timer);

//! See if certain timer is still linked to notifyTimerlist.
//! This will return TRUE, if timer is linked to the list.
       extern BOOL32 osapi_timerLinkedToNotifyTimeList(OSAPI_TIMER *timer);

who can tell me the function difference beteen the two sets of API ? whice one is more  accurate for timing application?

Looking forward to your reply!

thanks

Dear community,

I'm using a module based on your BCM4343W on a Linux OS  with Wiced SDK v.3.5.2

Ubuntu 18.04 LTS. I need a test image FW to put on it in order to manage the CE certification test?

Or, could you please provide me the WiFi_FCC_Tool_20170721\DUT_control_command\wl source code in order to build by myself it?

When I tryed to use the WL tool I receive a lot of error like this:

[..]

L:\EMC\test\WiFi_FCC_Tool_20170721\DUT_control_command>tx_carrier_stop.bat 14

L:\EMC\test\WiFi_FCC_Tool_20170721\DUT_control_command>wl --serial 14 fqacurcy 0
rwl_read_serial_port failed: reached max retry limit.
remote_CDC_rx_hdr: Header Read failed
set_info_fe: Reading CDC header failed
fqacurcy
Manufacturing test: set frequency accuracy mode.
freqacuracy syntax is: fqacurcy <channel>
Arg is channel number 1-14, or 0 to stop the test.


L:\EMC\test\WiFi_FCC_Tool_20170721\DUT_control_command>wl --serial 14 down
rwl_read_serial_port failed: reached max retry limit.
remote_CDC_rx_hdr: Header Read failed
set_info_fe: Reading CDC header failed
down    reset and mark adapter down (disabled)


L:\EMC\test\WiFi_FCC_Tool_20170721\DUT_control_command>wl --serial 14 up
rwl_read_serial_port failed: reached max retry limit.
remote_CDC_rx_hdr: Header Read failed
set_info_fe: Reading CDC header failed
up      reinitialize and mark adapter up (operational)


[..]

Thanks a lot,

BR,

Giordano

There are several features of the device we're not using that have their own VIO supply pins, such as USB, MII, SDIO, etc.  If we're not using a specific I/O block or interface do we need to power the I/O rail for that block?

Hi Sir

Our customer want to use USB 2.0 host for a custom class on a SPIL's SB-WM-N07 (CYW43907 wireless SoC) SiP. and they would like to connect the host to a custom class on a USB device running on an FX2 module.

As I described for this application, SB-WM-N07 need to receive image data from ‘Image sensor module’ via USB interface.

In more detail, SB-WM-N07 need to receive image data from FX2(GPIF to USB) via USB interface.

Our customer and we tried to find the way to use ‘Custom Class’ for FX2 USB device, couldn’t find it (SDK6.2.1 don't have example code).

Would you please provide example code or guideline that can use ‘Custom Class’?