MediaTek LinkIt(TM) Development Platform for RTOS provides a comprehensive software solution for devices based on the MediaTek MT7687F SOC, including the LinkIt 7687 hardware development kit (HDK). The platform supports hardware abstraction layers, peripheral drivers, FreeRTOS, Wi-Fi and lwIP modules. This API reference describes the features of and how to use the APIs for each of the supported modules. Each module has a readme.txt under the module root directory. It contains the information about the module dependency, feature options, notes and brief introduction. Please refer to the readme.txt to learn the basic usage of the module.
More information on Linkit SDK official site: https://labs.mediatek.com/site/global/developer_tools/mediatek_linkit_rtos/sdk_intro/index.gsp
The SDK package supports GCC, Keil, and IAR tool chains. Follow the instructions at <sdk_root>/doc/LinkIt_for_RTOS_Get_Started_Guide.pdf to build your first project and run it on the HDK. Release notes are also under the <sdk_root>/doc folder.
\doc -> SDK documents, including get started guide, developer's guide, software and environment guide,
-> API reference manual, and SDK release notes.
\doc\HDK -> HDK documents, including user guide, layout information, schematics, daughterboard information,
-> BOM list. The HDK relative application notes are also in this folder, such as power measurement guide.
\doc\MCU -> Chipset documents, such as chipset product brief and chipset datasheet.
\driver\board -> Drivers for the development board
\driver\chip -> Chipset modules, such as GPIO, I2C, Bluetooth Low Energy.
\driver\CMSIS -> CMSIS interface drivers.
\driver\inc -> HAL driver APIs
\kernel -> OS / system service
\middleware\MTK -> MediaTek middleware. Read readme.txt in each module for details.
\middleware\third_party -> Open source software, such as cjson, fatfs, httpd. Read readme.txt in each module for details.
\project\<board> -> Example projects of the current SDK. Read <sdk_root>/project/readme.txt for more details.
\tools -> Script, generation script, gcc compiler. If there isn't a gcc compiler under the /tools/gcc folder,
-> extract the tool package to the root folder of the SDK with the following command.
-> tar -C <sdk_root> -xvzf SDK_VX.Y.Z_tool_chain.tar.gz
** Please make sure you have /tools/gcc before you build the SDK under linux environment. **
The architecture layers are described below:
- BSP
- Hardware drivers provide peripheral drivers for the development platform, such as ADC, I2S, I2C, SPI, RTC, GPIO, UART, Flash, Security Engine, TRNG, GDMA, PWM, WTD and IRDA TX/RX.
- Hardware Abstraction Layer (HAL) provides driver Application Programming Interface (API) encapsulating the low-level functions of peripheral drivers for the operating system (OS), middleware features and applications.
- FreeRTOS provides real-time OS with open source software for middleware features and projects.
- Middleware
- Wi-Fi provides OS dependent function calls, including Wi-Fi APIs that control the bridge supplicant and network processor messages.
- Network provides OS dependent features, such as IPv4, Hyper-Text Transfer Protocol (HTTP) client and the Simple Network Time Protocol (SNTP).
- Advanced features include Non-Volatile Random Access Memory (NVRAM), JavaScript Object Notation (JSON) and other features that are dependent on HAL and the OS.
- Example project
- Pre-configured projects, such as Wi-Fi station and Wi-Fi access point.
https://labs.mediatek.com/fileMedia/download/20ee756c-903c-4ec4-8fb4-163697638589
$ brew install gcc-arm-none-eabi
$ cd <linkit_sdk_root>
$ ln -s /usr/local tools/gcc/mac/gcc-arm-none-eabi
https://robbie-cao.github.io/blog/2016/05/17/install-gcc-arm-on-mac
There will be issue to build mt2523 with gcc-arm-none-eabi version 49+ due to -flto option.
lto1: fatal error: bytecode stream generated with LTO version 2.2 instead of the expected 4.1
compilation terminated.
lto-wrapper: fatal error: ../../../../../tools/gcc/mac/gcc-arm-none-eabi/bin/arm-none-eabi-gcc returned 1 exit status
compilation terminated.
/Users/robbie/Tools/gcc-arm-none-eabi-5_4-2016q2/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
Solution as below:
$ cd ~
$ wget https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q3-update/+download/gcc-arm-none-eabi-4_8-2014q3-20140805-mac.tar.bz2
$ mkdir Tools
$ tar -c gcc-arm-none-eabi-4_8-2014q3-20140805-mac.tar.bz2 -C Tools
$ cd <linkit_sdk_root>
$ ln -s ~/Tools/gcc-arm-none-eabi-4_8-2014q3 gcc-arm-none-eabi
$ cd ~
$ wget https://launchpad.net/gcc-arm-embedded/5.0/5-2016-q2-update/+download/gcc-arm-none-eabi-5_4-2016q2-20160622-linux.tar.bz2
$ mkdir Tools
$ tar jxvf gcc-arm-none-eabi-5_4-2016q2-20160622-linux.tar.bz2 -C Tools
$ cd <linkit_sdk_root>
$ ln -s ~/Tools/gcc-arm-none-eabi-5_4-2016q2 tools/gcc/linux/gcc-arm-none-eabi
$ cd ~
$ wget https://launchpad.net/gcc-arm-embedded/5.0/5-2016-q2-update/+download/gcc-arm-none-eabi-5_4-2016q2-20160622-win32.zip
$ mkdir Tools
$ unzip gcc-arm-none-eabi-5_4-2016q2-20160622-win32.zip -d Tools
$ cd <linkit_sdk_root>
$ ln -s ~/Tools/gcc-arm-none-eabi-5_4-2016q2 tools/gcc/win/gcc-arm-none-eabi
Build in Cygwin NOT support yet.
TBD
===============================================================
Build Project
===============================================================
Usage: ./build.sh <board> <project> [bl|clean] <argument>
Example:
./build.sh mt7687_hdk iot_sdk_demo
./build.sh mt7687_hdk iot_sdk_demo bl (build with bootloader)
./build.sh clean (clean folder: out)
./build.sh mt7687_hdk clean (clean folder: out/mt7687_hdk)
./build.sh mt7687_hdk iot_sdk_demo clean (clean folder: out/mt7687_hdk/iot_sdk_demo)
Argument:
-f=<feature makefile> or --feature=<feature makefile>
Replace feature.mk with other makefile. For example,
the feature_example.mk is under project folder, -f=feature_example.mk
will replace feature.mk with feature_example.mk.
-o=<make option> or --option=<make option>
Assign additional make option. For example,
to compile module sequentially, use -o=-j1.
to turn on specific feature in feature makefile, use -o=<feature_name>=y
to assign more than one options, use -o=<option_1> -o=<option_2>.
===============================================================
List Available Example Projects
===============================================================
Usage: ./build.sh list
Run source envsetup first of all.
Usage:
mmm [path] [option]
- path - relative path to Makefile (for an App) to be built with
- option - target to make, eg clean, debug, release, etc
Example:
mmm project/mt7687_hdk/apps/iot_sdk_demo clean (* at top folder)
mmm project/mt7687_hdk/apps/iot_sdk_demo (* at top folder)
mmm . clean (* at project/mt7687_hdk/apps/iot_sdk_demo)
mmm (* at project/mt7687_hdk/apps/iot_sdk_demo)
Currently support flashing in Windows ONLY!
-
Make sure the jumper pins J23, J26, J27, J30 and J33 are connected, as shown below:
-
Set the board to Flash Recovery mode by connecting jumper J25 (Flash Mode), as shown in the following figure:
-
Flashing with
mt76x7-flash-tool.exe(located at<sdk_windows_tools>\MT7687_FlashTool_Public\win\mt76x7-flash-tool.exe)
Refer to LinkIt 7687 Development Board User's Guide.
This guide described the hardware features of the LinkIt 7687 development board, its pin layout and how to configure its various features.
https://labs.mediatek.com/fileMedia/download/51594214-62e7-46fe-a995-6412cc879c08