Depending on the environment, this application may not work or may require various settings. If you encounter any problems, please refer to the description in this document to improve your environment.

extract TWELITE STAGE SDK

1. Download the TWELITE STAGE SDK for your system (Windows, macOS, Linux, etc.).

2. Extract the downloaded archive file (e.g. ZIP). The folder name of each level of the destination folder should not contain any characters other than one-byte numbers 0..9, one-byte alphabets a..zA..Z, and some symbols -_. . It must not contain spaces, Kanji characters, Hiragana characters, etc. Example(Windows): × C:\work\作業\ × C:\Users\user1\work dir\ 〇 C:\Work\Work1

3. Check the folder after expansion. If you extract on C:\Work, the folder name will be something like C:\Work\MWSTAGE, but your extractor may create a folder with the archive file name. Rename or move the folder as needed.

In the text, the expanded folder (e.g. C:\WorkMWSTAGE )} may be written as {MWSTAGE installation}.

Settings unique to each system, etc.

See below.

• Windows

• macOS

• linux

• RaspberryPi

Folder structure of TWELITE STAGE SDK

The folder {MWSTAGE installation} where the TWELTIE STAGE SDK is installed contains the following

• TWELITE STAGE application executable

• MWSDK folder - libraries, source code, etc.

• Tools - toolchain for building, etc.

For details, see Folder Structure" for details.

macOS

環境

We develop in the following environment

• macOS 10.14 (Mojave, Intel)

• macOS 12.4 (Monterey, Apple Silicon)

Additional installation and warning dialogs.

• The download archive is not signed. At runtime, you may receive a security warning as an application downloaded from the Internet.

• You may be asked for permission to run from the path where you installed TWELITE_Stage.

• You may get an installation dialog for the make utility when executing a build.

• The toolchain is code-signed, but if the code signature is not properly authenticated, you may be asked for permission to run each executable in the build toolchain (ba-elf-gcc etc.}).

The above is required to give permission or installation work for the TWELITE_Stage to work.

Reference: Manual installation of the make utility

※ Different OS versions and other factors may require a different procedure.

If an error occurs when executing make on the command line (bash), install XCode.

$ xcode-select --install

After installation is complete, type "make" and the following message should appear.

$ make
make: *** No targets specified and no makefile found.  Stop.

Handling of Serial Port

MONOSTICK and TWELITE-R use FT232 series semiconductors from FTDI (https://www.ftdichip.com). In order to use them, you may need to deal with device drivers.

If the serial port does not appear when you start TWELITE-R, you need to unload (disable) FTDI's driver. See "Reference" below.

Reference: utilities from FTDI, Inc.

Download and use D2xxHelper from https://www.ftdichip.com/Drivers/D2XX.htm. You can find the same in our archive in the TWELITE_Stage/INSTALL folder.

Reference: Manual unloading of FTDI device drivers

Unload FTDI-related drivers.

$ sudo kextunload -b com.apple.driver.AppleUSBFTDI

Linux

Environment

TWELITE STAGE is developed and tested in the following environment.

• Ubuntu 16.04, 18.04, 20.04

• NNLinux Beta8 64bit

• Centos7

device driver

In order to recognize MONOSTICK or TWELITE-R from TWELITE STAGE, you must unload the ftdi_sio module and also have read/write permission to the USB device.

We have a udev configuration script Ј(Ubuntu, CentOS Ј) to automate this configuration. It copies the definition to /etc/udev/rules.d and reloads the configuration. After configuration, unplug and plug the USB device before running TWELITE_Stage.run. If the USB device appears on the screen right after startup, the configuration is reflected.

Ubuntu 16.04, 18.04. 20.04

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ sudo ./set_udev_sudo.sh

Definition file (line breaks for easier reading)

ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
   MODE="0666",
   RUN+="/bin/sh -c 'rmmod ftdi_sio && rmmod usbserial'"
ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015",
   MODE="0666",
   RUN+="/bin/sh -c 'rmmod ftdi_sio && rmmod usbserial'"

Centos 7

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/centos/
$ sudo ./set_udev_sudo.sh

Definition file (line breaks for easier reading)

ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
   MODE="0666", 
   RUN+="/bin/sh -c '/usr/sbin/rmmod ftdi_sio'"
ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015",
   MODE="0666", 
   RUN+="/bin/sh -c '/usr/sbin/rmmod ftdi_sio'"

Application Registration

Register your program according to your desktop environment if necessary.

Ubuntu 16.04, 18.04, 20.04

Definition file generation scripts for Ubuntu are available.

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ ./make_launch_icon.sh

This script creates a .desktop file (app definition) in $HOME/.local/share/applications.

After the script is executed, the TWELITE STAGE icon will be added to the application list.

Windows

Environment

The following environment is used for development.

• Windows 10 version 1903

• VisualStudio 2019 (32bit build )

Requirements for operation

• FTDI's FT232 series may require device driver installation to work; if MONOSTICK or TWELITE-R is not recognized, please install the D2XX driver from ftdichip.com. Visual C++ Distributable Code for Visual Studio 2019 (runtime library) may be required. If you get an error when starting the application and it does not start, please redistribute it in this package TWELITE_Stage³_INSTALL³VC_redist.x86.exe or get it from Microsoft's website and install it. Distribution binaries are 32-bit.

RasPi

The TWELITE Stage app runs on a Raspberry Pi.

• Mouse and touch screen support.

• The build toolchain is included and can be used to compile the application.

• Four executable versions are available: framebuffer version, X11 version, framebuffer lightweight version, and X11 lightweight version. The lightweight version omits semi-transparency effects, etc.

Environment

TWELITE STAGE has been developed and tested in the following environment.

• Hardware

  • Raspberry Pi 3 Model B

  • LCD Screen: Raspberry Pi Touch Display (7")

• OS & distribution

  • Raspberry PI OS (32bit) Lite (Version:August 2020)

Known Issues/Limitations.

• Operation of /dev/serial0 may fail on the first boot.

• The operation of /dev/serial0 has not been tested on Raspberry Pi 4B.

• Touch screen operation has not been tested on Raspberry Pi 4B.

• The input string to TWELITE STAGE is passed as is to the input string to the shell or getty running on /dev/tty1. It is recommended to start from /dev/tty1.

• This may be affected by other installations or running programs (such as X11).

Extract archive

The downloaded archive file should be extracted to a folder whose path name does not contain spaces or Japanese characters.

In the following, it is extracted to the home folder of the Raspberry Pi.

$ cd /home/pi
$ unzip MWSTAGE2020_XX_YYYY.zip

folder structure

../MWSTAGE
     TWELITE_Stage.run    TWELITE_Stage App.
     BIN/                 BIN files of App. firmware
     MWSDK/               MWSDK library, etc.
     TWELITE_Stage/       TWELITE_Stage Application related files

Device Driver

In order to recognize MONOSTICK or TWELITE-R from TWELITE STAGE, you must unload the ftdi_sio module and also have read/write permission to the USB device.

A udev configuration script is provided to automate this setup. It copies the definition to /etc/udev/rules.d and reloads the configuration. After configuration, unplug and plug the USB device before running TWELITE_Stage.run. If the USB device appears on the screen right after startup, the configuration is reflected.

$ cd ./MWSTAGE/TWELITE_Stage/INSTALL/ubuntu/
$ sudo ./set_udev_sudo.sh

Definition file (line breaks for easier reading)

ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
   MODE="0666",
   RUN+="/bin/sh -c 'rmmod ftdi_sio && rmmod usbserial'"
ACTION=="add",
   ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015",
   MODE="0666",
   RUN+="/bin/sh -c 'rmmod ftdi_sio && rmmod usbserial'"

UARTについて

In the environment described above, /dev/serial0 is available by configuring the serial port from raspi-config.

  $ sudo raspi-config

  From the Menu:
  "3 Interface Options    Configure connections to peripherals"
  →"P6 Serial Port Enable/disable shell messages on the serial connection"

  Select the following: do not use as a login shell, or enable hardware.
  "Would you like a login shell to be accessible over serial?" -> <No>
  "Would you like the serial port hardware to be enabled?" → <Yes>

Wiring example

 [TWELITE]               [RaspberryPi]
  GND  ------------------ Gound (#6,#9,#14,#20,#25,#30,#34,#39のいずれか)
  TXD(DIO6,DIP#10) ------ GPIO15/UART0 RXD (#10)
  PRG(SPIMISO,DIP#7) ---- GPIO23 (#16)
  RXD(DIO7,DIP#3) ------- GPIO14/UART0 TXD (#8)
  RST(RESETN,DIP#21) ---- GPIO22 (#15)
  VCC  ------------------ 3V3 (#1,#17のいずれか)
  SET(DIO12,DIP#15) ----- GPIO12 (#32)

• Refer to the manufacturer's manual for both TWELITE and RaspberryPi.

• DIP# is the pin number of the TWELITE DIP.

• The above wiring does not guarantee stable operation of the TWELITE wireless microcontroller module.

Launch TWELITE Stage app.

• It will not run on the X11 desktop; close X11.

• Run TWELITE_Stage.run. The TWELITE Stage app will appear on the screen screen.

Notes.

• Mouse and touch screen are supported.

• During the TWELITE Stage app, the characters you enter may also be displayed on the console screen.

Others

/dev/dri

You may get the following error when starting TWELITE_Stage.run.

  "The path /dev/dri/ cannot be opened or is not available"

You may ignore it.

Insufficient memory

At build time, if the number of CPUs is 4 or more, the parallel compilation is executed minus one CPU number (3 parallel compilations for 4 cores). In some cases, insufficient memory may occur. In that case, please change the number of parallels.

RaspberryPi 4

The following settings are required: OpenGL related drivers must be enabled.

• Select Advanced Settings → A2 GL Driver → G2 GL (Fake KMS\ in raspi-config)

• Install the libgles-dev package.

• Touch screen operation has not been tested