Table of Contents
Advertisement
This is the UART log for MT7681 AP mode after boot up:
==> Recovery Mode
<== Recovery Mode
(-)
load_ap_cfg
store_ap_cfg
===> APStartUp
PMK Updating ...
AP SETTING: SSID[MT7681_AP1], AuthMode[9], WepStatus[8], Channel[8]
APStartUp ...
[WTask]53637
MT7681 is now ready to accept Wi-Fi client connections.
Refer to section 5.3.1, "Creating a TCP client that connects to a remote TCP server" for detail log of
client connection.
In AP mode only 3 clients may connect to a MT7681 at the same time.
5.3. Using uIP for TCP/IP operations
This section provides an introductory guide to using
MT7681. For more information on this stack refer to the uIP Reference Manual (uip-refman.pdf)
available from the
source
The design principle of uIP is that applications must provide an APP_CALL callback function that
uIP calls whenever an event occurs. Several APIs are provided to check these events:
•
if uip_newdata() returns a non-zero value, a remote host has sent new data that are
stored in the uip_appdata global variable.
•
if uip_poll() returns a non-zero value, the connection is idle, and you can send new data
to the remote host. For more information, see chapter 1.6 of the uIP Reference Manual.
In MT7681 SDK this callback is iop_tcp_appcall(), which is in cust\tcpip\iot_tcp_app.c.
This document contains information that is proprietary to MediaTek Inc.
Unauthorized reproduction or disclosure of this information in whole or in part is strictly prohibited.
MediaTek LinkIt™ Connect 7681 Developer's Guide
/*start to running recovery/Calibration image*/
/*end to running recovery/Calibration image*/
/*start to running AP image*/
OK
repository.
© 2015, 2016 MediaTek Inc.
uIP (micro
IP), the TCP/IP stack included in the
Page 44 of 65
Advertisement
Table of Contents
