![background image](http://html1.mh-extra.com/html/rabbit/rabbitcore-rcm4400w/rabbitcore-rcm4400w_product-manual_3115424087.webp)
User’s Manual
79
6.3.3 Other Key Function Calls
Remember to call
sock_init()
after all the Wi-Fi parameters have been defined. The
Wi-Fi interface will be up automatically as long as you configured Dynamic C at compile
time with one of the
TCPCONFIG
macros. Otherwise the Wi-Fi interface is neither up nor
down, and must be brought up explicitly by calling either
ifup(IF_WIFI0)
or
ifconfig(IF_WIFI0,…)
. You must bring the interface down when you configure
Dynamic C at run time before modifying any parameters that require the interface to be
down (see Section 6.3.2) by calling
ifdown(IF_WIFI0)
or
ifconfig(IF_WIFI0,…)
.
Then bring the interface back up.
Finally, no radio transmission occurs until you call
tcp_tick(NULL)
.
Instead of executing the above sequence based on
sock_init()
, you could use
sock_
init_or_exit(1)
as a debugging tool to transmit packets (ARP, DHCP, association,
and authentication) while bringing up the interface and to get the IP address.
Summary of Contents for RabbitCore RCM4400W
Page 1: ...RabbitCore RCM4400W C Programmable Wi Fi Core Module OEM User s Manual 019 0160 080131 F...
Page 6: ...RabbitCore RCM4400W...
Page 24: ...18 RabbitCore RCM4400W...
Page 32: ...24 RabbitCore RCM4400W...
Page 58: ...50 RabbitCore RCM4400W...
Page 102: ...94 RabbitCore RCM4400W...
Page 120: ...112 RabbitCore RCM4400W...
Page 124: ...116 RabbitCore RCM4400W...
Page 126: ......