μT-Kernel 3.0

Where can I get μT-Kernel 3.0?

• μT-Kernel 3.0 is available from UCT GitHub.
  → https://github.com/UCTechnology/mtk3_bsp
• The original of μT-Kernel 3.0 is available from the TRON Forum GitHub and web page.
  → https://github.com/tron-forum
  → https://www.tron.org/

Is μT-Kernel 3.0 available for a fee?

• μT-Kernel 3.0 is available for free, including for commercial use.
• μT-Kernel 3.0 is distributed according to T-License 2.2.

Is there any document for μT-Kernel 3.0?

• The specification and other documents are available free of charge on the TRON Forum website.
• The original document related to μT-Kernel 3.0 is in Japanese.
  → Comparison between μT-Kernel 3.0 and FreeRTOS

How can I port μT-Kernel 3.0 to my company’s developed boards?

• In μT-Kernel 3.0, CPU- and board-dependent source codes are collected in a specific folder. μT-Kernel 3.0 can be ported by rewriting the board-dependent part.
  → Example of porting μT-Kernel 3.0 (to be released later)

Is there any support for μT-Kernel 3.0?

• We provide support service for μT-Kernel 3.0 for a fee.
  • Porting of μT-Kernel 3.0 to target boards and support for them
  • Device driver development service

Computer Network

Can I use network functions (TCP/IP) on μT-Kernel 3.0?

• lwIP can be used.
  • lwIP (lightweight IP): Open source TCP/IP protocol stack for embedded devices
    → Example of porting lwIP (to be released later)
• For hardware, Ether Shield2 for Arduino is available.
  • A sample LAN driver for Ether Shield2 will be released for free.

Can I use the onboard Ether port and Wi-Fi function?

• Network function can be used with on-board devices by developing device drivers.
  → Example of LAN driver development for Ether Shield2 (to be released later)

Device drivers

How can I implement device drivers for μT-Kernel?

• For μT-Kernel, device driver is developed in accordance with the “T-Engine Standard Device Driver Specification.”
  • μT-Kernel 3.0 comes with sample drivers for UART, I²C, and ADC.
    → Example of serial driver (UART) development (to be released later)
  • T-Engine Standard Device Driver Specification unifies the access methods (API specifications) for various devices. This allows access to a variety of devices using the same API.
    → How to use the device driver API (to be released later)

Can we add our own device drivers for our own devices?

• Device drivers can be added freely.
  → Example of LAN driver development for Ether Shield2 (to be released later)
• If implemented in accordance with T-Engine standard device driver specification, application development and porting will be easy.

Please contact us for further information.