Get the latest version
TWELITE STAGE
TWELITE NET 1.3.0 (2020/04) and later will be distributed as part of TWELITE STAGE.
1
*** TWELITE STAGE Directory Structure ***
2
{STAGE TO FOLDER}/
3
TWELITE_Stage.exe -- STAGE executable (Windows)
4
dll/ -- for STAGE exe (Windows)
5
TWELITE_Stage/ -- STAGE related files
6
BIN/ -- stores .bin files
7
8
MWSDK/ -- TWELITE SDK(MWSDK) top dir.
Copied!
release version
Please download the release version from the following link. The MWSDK will be part of the TWELITE STAGE distribution.
TWELITE STAGE-トワイライトステージ - MONO-WIRELESS.COM
official release
The official release will have a name. The format of the name is
MWSTAGE followed by {year}_{month}, as in MWSTAGE2020_05. Versions of the TWELITE SDK (MWSDK) that do not include the TWELITE Stage tool are likewise named with the MWSDK followed by {year}_{month}, as in MWSDK2020_05.If the release name is accompanied by UNOFFICIAL, it is named for "updates between releases".
It is distributed as follows.
Update between releases
Any problems found after the release, or updates to samples, etc., will be reflected in the GitHub repository (a database that stores source code and files, including their history) below.
- MWSDK_COMMON - A repository of common parts of the MWSDK. It uses submodules, so you need to be familiar with Git.
- MWSDK_COMMON_SNAP - This is a repository of the common parts of the MWSDK that can be downloaded in zip format.
These modifications may include intermediate content, or omissions of predetermined behavior checks. There may be unconfirmed side effects or inconsistencies between configurations. Please judge whether to use them by yourself.
As a rule, we do not provide support for fixes after the release. Please ask for technical support based on the released version.
In addition, if you find any inconvenience with the fixes after the release, please contact our technical support.
Our support team cannot answer questions about how to use Git or GitHub. We recommend that you refer to general instructions. Also, we may not be able to help you with GitHub services.
MWSDK_COMMON_SNAP repository
To update the MWSDK, download the zip file from this repository, and replace the directory and files with the ones before the update.
The links include links to the complete set of files in each release (the preliminary version is UNOFFICIAL).
GitHub画面例
The repository contains the following directories:
- ChipLib
- LICENSE
- MkFiles
- TWENET
Replace these four directories in the TWELITE STAGE distribution directory。
1
.../MWSTAGE/ --- TWELITE STAGE distribution directory
2
.../MWSDK --- MWSDKdirectory
3
.../ChipLib <-- Replace the following four directories
4
.../LICENSE
5
.../MkFiles
6
.../TWENET
Copied!
MWSDK_COMMON repository
This repository manages the files of the common parts of MWSDK, but while the MWSDK_COMMON_SNAP described above focuses only on file differences per release, the repositories of each library, sample, etc. are sub-modules, and the update history can be referenced individually.
If you download a zip file, the files will not be stored in the folder that corresponds to the submodule. (This is a GitHub specification).
About Repository Use
- GIT submodule is used; if you download an archive from GitHub site in .zip format or other format, the files containing submodule will not be included. (See below for an example of git command to clone with submodule)
- The MWSDK_COMMON repository is the distributed MWSDK directory without the Tools directory and some files (the cmd file for registering environment variables in the Windows version).
How to clone from the repository (MWSDK 2020/04 or later)
In this section, we will describe how to clone the contents of MWSDK from GitHub using the command line. Please prepare an environment where you can use the git command beforehand, or use bash if you are using Windows.
The first step is to extract the MWSDK (TWELITE STAGE) from the distribution. It will have the following structure.
1
=== directory structure ===
2
.../MWSTAGE +- MWSDK +- TWENET
3
- ChipLib
4
- ...
5
- Tools
Copied!
Rename the MWSDK directory at the time of distribution to something else.
1
$ cd .../MWSTAGE ...is the customer's installation directory
2
$ mv MWSDK MWSDK.orig
3
4
=== directory structure ===
5
.../MWSTAGE +- MWSDK.ORIG
6
+- TWENET
7
- ...
8
- Tools
Copied!
In the MWSTAGE directory, clone MWSDK_COMMON from GitHub, and add the
--recurse-submodules option to retrieve the submodules files.1
$ pwd
2
.../MWSTAGE
3
$ git clone --recurse-submodules https://github.com/monowireless/MWSDK_COMMON MWSDK
4
...(It'll take a while.)
5
6
=== directory structure ===
7
.../MWSTAGE +- MWSDK
8
+- TWENET
9
- ... (Tools is not included)
10
- MWSDK.ORIG
11
+- TWENET
12
- ...
13
- Tools
Copied!
Finally, transplant the
MWSDK.ORIG/Tools directory to MWSDK.1
$ mv MWSDK.ORIG/Tools MWSDK/
2
3
=== ディレクトリ構成 ===
4
.../MWSTAGE +- MWSDK
5
+- TWENET
6
- ...
7
- Tools
8
- MWSDK.ORIG
9
+- TWENET
10
- ... (Tools is not included because it was mv'd.)
Copied!
TWELITE MWX library SDK (2019/12)
This is the first version of the SDK dedicated to the MWX library.
For development with MWX, please use the latest version of TWELITE STAGE.
Before TWELITE NET 1.2.0 (2018/05)
See the link below.
旧ソフトウエア開発環境 - MONO-WIRELESS.COM