wiki.emacinc.com - User contributions [en]

Getting Started with MitiPy

2020-09-23T21:02:01Z

CBost:

Getting Started with MitiPy

2020-09-23T20:59:57Z

CBost:

{{#seo:
|title=Getting Started with MitiPy
|titlemode=append
|keywords=MitiPy Getting Started
|description=The following page can be used to get familiarized with the MitiPy Industrial IoT Gateway.
}}



The MitiPy is an Industrial IoT device that is designed to provide a secure, flexible and ruggedized Industrial IOT Gateway solution. The MitiPy is
built around the STMicroelectronics STM32 microcontroller with 32bit m4 ARM core.The MitiPy provides a comprehensive wireless multi-protocol (Wi-Fi + BT5) connectivity solution.
Additionally, the MitiPy supports both the Skywire Cellular Module(s) and the MultiConnect mDot LoRa
module. This module also provides RS232, RS485, CAN, USB and Ethernet to support protocols such as
Modbus, PROFINET and EtherCAT. A wide range of configurable controller I/O pins are also available, enabling max system utilization.

The MitiPy Currently supports Micropython. A freeRTOS build is currently in development and will be available soon!







{{:Templateimpl:geninfo | initials=BS | title=IMX6U Getting Started | desc=The following page can be used to get familiarized with the DEV-IOT6U. | project=OE 5.0 }}
=== What Comes with the Development Kit ===
* SoM-IMX6U-120R2 (528MHz iMX6UL 4GB eMMC, 128MB SoM, connected to Carrier Board)
* SoM-112ES-131R1 (Dlx Carrier with Wifi/BT & Audio)
* 5V 3A Wall Power Supply
* 10 Pin Com to DB9 Cable 12"
* RJ45 to RJ45 Ethernet Cable 7'
* USB2.0A Male to Micro-USB Male 6'
* 2.4 & 5GHz 100mm Wifi Antenna
* MikroBus ROTARY B click
{{note | Do to a design flaw in the MikroBus Rotary B Click, the card does not allow another SPI device to be present on the SPI Bus. The SoM-IMX6U uses the SPI Bus and the presence of MikroBus Rotary B Card prohibits the SOM from booting.
'''To alleviate this issue, the pin labeled “SDO” must be cut and jumpers JB5 and JB6 on the Dev Kit Carrier Board (SoM-112) must be set to 3P3''' (see figures below)}}

=== Tools Required ===
* Desktop PC (Linux or Virtual Linux Machine)
** Instructions for Downloading a [[Getting_Started_With_EMAC_Virtual_LDC#Getting_Started_With_EMAC_Virtual_LDC|Virtual Machine with EMAC OE SDK pre-installed]]

== Setup ==
1. Install EMAC OE SDK on your computer.
* Installation options are linked [[Getting_Started_with_the_EMAC_OE_SDK#Installing_EMAC_SDK|HERE]].
2. Make the following cable connections using the cables provided:
* Board Micro-USB to USB Desktop
* Board Ethernet to Ethernet Network
* 5V Wall Power Supply to Board Power (may be left unplugged from wall until Step 3)
3. Open [[Getting_Started_With_Minicom|Minicom]] and create a terminal session with the DEV-IOT6U
* After supplying power, boot messages will be displayed followed by a '''log in''' prompt.
** '''somimx6ul login: root'''
** '''password: emac_inc'''
* Use command "ifconfig" in the terminal session to find the device's IP address that can be used during the development process.

== Development ==
There are two options in development with this device: 
1. Using the EMAC OE SDK on terminal. [ [[Getting_Started_with_the_EMAC_OE_SDK | Getting Started with the EMAC OE SDK]] ] 
- or 
2. Using the EMAC OE SDK on Qt Creator. [ [[Getting_Started_With_Qt_Creator|Getting Started With Qt Creator]] ]




=== MikroBus Rotary B Click ===
EMAC has provided a MikroBus Rotary B Card which provide a number of LEDs and a Rotary Switch to allow for easy demonstration and interaction of the Eval Kit.
Demo/Example Software is provided that interacts with this Card. This Software can be modified by the user as an exercise in using the development tools.

'''NOTE:''' Do to a design flaw in the MikroBus Rotary B Card which does not allow another SPI device to be present on the SPI Bus. The SoM-IMX6U uses the SPI Bus and the presence of MikroBus Rotary B Card prohibits the SOM from booting.
'''To alleviate this issue, the pin labeled “SDO” must be cut and jumpers JB5 and JB6 on the Dev Kit Carrier Board (SoM-112) must be set to 3P3''' (see figures below).
[[File:RotaryBClickModification.png]] 
[[File:JumpersMikroBus.png]]

== Demo ==
Proceed to this page for an example demo of the MikroBus Rotary B Click on the DEV-IOT6U: 
*[[Example_MikroBus_Rotary_on_the_DEV-IOT6U]]

== Further Information ==

{{:Templateimpl:whatnext | initials=BS | title=Getting Started with the EMAC OE SDK | desc=Basic tutorial for using the EMAC OE SDK. | project=OE 5.0 }}

* [[DEV-IOT6U | DEV-IOT6U Hardware Main Page]]
* [[Getting_Started_with_the_EMAC_OE_SDK | Getting Started with the EMAC OE SDK]]
* [[Getting_Started_With_Qt_Creator|Getting Started With Qt Creator]]
* [[Getting_Started_With_Minicom|Getting Started with Minicom]]

Getting Started with MitiPy

2020-09-23T20:42:51Z

CBost: Created page with "{{#seo: |title=Getting Started with MitiPy |titlemode=append |keywords=MitiPy Getting Started |description=The following page can be used to get familiarized with the MitiPy I..."

{{#seo:
|title=Getting Started with MitiPy
|titlemode=append
|keywords=MitiPy Getting Started
|description=The following page can be used to get familiarized with the MitiPy Industrial IoT Gateway.
}}



This page outlines a basic guide to getting starting using the DEV-IOT6U.
* [[DEV-IOT6U | DEV-IOT6U Hardware Main Page]]







{{:Templateimpl:geninfo | initials=BS | title=IMX6U Getting Started | desc=The following page can be used to get familiarized with the DEV-IOT6U. | project=OE 5.0 }}
=== What Comes with the Development Kit ===
* SoM-IMX6U-120R2 (528MHz iMX6UL 4GB eMMC, 128MB SoM, connected to Carrier Board)
* SoM-112ES-131R1 (Dlx Carrier with Wifi/BT & Audio)
* 5V 3A Wall Power Supply
* 10 Pin Com to DB9 Cable 12"
* RJ45 to RJ45 Ethernet Cable 7'
* USB2.0A Male to Micro-USB Male 6'
* 2.4 & 5GHz 100mm Wifi Antenna
* MikroBus ROTARY B click
{{note | Do to a design flaw in the MikroBus Rotary B Click, the card does not allow another SPI device to be present on the SPI Bus. The SoM-IMX6U uses the SPI Bus and the presence of MikroBus Rotary B Card prohibits the SOM from booting.
'''To alleviate this issue, the pin labeled “SDO” must be cut and jumpers JB5 and JB6 on the Dev Kit Carrier Board (SoM-112) must be set to 3P3''' (see figures below)}}

=== Tools Required ===
* Desktop PC (Linux or Virtual Linux Machine)
** Instructions for Downloading a [[Getting_Started_With_EMAC_Virtual_LDC#Getting_Started_With_EMAC_Virtual_LDC|Virtual Machine with EMAC OE SDK pre-installed]]

== Setup ==
1. Install EMAC OE SDK on your computer.
* Installation options are linked [[Getting_Started_with_the_EMAC_OE_SDK#Installing_EMAC_SDK|HERE]].
2. Make the following cable connections using the cables provided:
* Board Micro-USB to USB Desktop
* Board Ethernet to Ethernet Network
* 5V Wall Power Supply to Board Power (may be left unplugged from wall until Step 3)
3. Open [[Getting_Started_With_Minicom|Minicom]] and create a terminal session with the DEV-IOT6U
* After supplying power, boot messages will be displayed followed by a '''log in''' prompt.
** '''somimx6ul login: root'''
** '''password: emac_inc'''
* Use command "ifconfig" in the terminal session to find the device's IP address that can be used during the development process.

== Development ==
There are two options in development with this device: 
1. Using the EMAC OE SDK on terminal. [ [[Getting_Started_with_the_EMAC_OE_SDK | Getting Started with the EMAC OE SDK]] ] 
- or 
2. Using the EMAC OE SDK on Qt Creator. [ [[Getting_Started_With_Qt_Creator|Getting Started With Qt Creator]] ]




=== MikroBus Rotary B Click ===
EMAC has provided a MikroBus Rotary B Card which provide a number of LEDs and a Rotary Switch to allow for easy demonstration and interaction of the Eval Kit.
Demo/Example Software is provided that interacts with this Card. This Software can be modified by the user as an exercise in using the development tools.

'''NOTE:''' Do to a design flaw in the MikroBus Rotary B Card which does not allow another SPI device to be present on the SPI Bus. The SoM-IMX6U uses the SPI Bus and the presence of MikroBus Rotary B Card prohibits the SOM from booting.
'''To alleviate this issue, the pin labeled “SDO” must be cut and jumpers JB5 and JB6 on the Dev Kit Carrier Board (SoM-112) must be set to 3P3''' (see figures below).
[[File:RotaryBClickModification.png]] 
[[File:JumpersMikroBus.png]]

== Demo ==
Proceed to this page for an example demo of the MikroBus Rotary B Click on the DEV-IOT6U: 
*[[Example_MikroBus_Rotary_on_the_DEV-IOT6U]]

== Further Information ==

{{:Templateimpl:whatnext | initials=BS | title=Getting Started with the EMAC OE SDK | desc=Basic tutorial for using the EMAC OE SDK. | project=OE 5.0 }}

* [[DEV-IOT6U | DEV-IOT6U Hardware Main Page]]
* [[Getting_Started_with_the_EMAC_OE_SDK | Getting Started with the EMAC OE SDK]]
* [[Getting_Started_With_Qt_Creator|Getting Started With Qt Creator]]
* [[Getting_Started_With_Minicom|Getting Started with Minicom]]

FreeRTOS

2020-09-02T19:35:37Z

CBost:

{{#seo:
|title=FreeRTOS
|titlemode=append
|keywords=Micropython
|description=The following page can be used to get familiarized with Micropython on EMAC products.
}}



===Intro===
FreeRTOS is a lightweight RTOS design for embedded systems. Distributed freely under the MIT open source license, FreeRTOS includes a kernel and a growing set of libraries suitable for use across all industry sectors. FreeRTOS is built with an emphasis on reliability and ease of use. It allows the creation of multiple 'tasks' (multi-threading)
and provides essential kernel elements for the snychronization between these tasks(Things like Mutexes, Semaphores, queues, etc.) It also enables the implementation of more advanced features like Software timers, and tickless idle for power-saving purposes.

With a focus on compactness and speed of execution, FreeRTOS gives the user precision control over RTOS elements and forgoes the 'fluff' present in a full-blown OS. This allows users to scale their RTOS implementation to the needs of their project.

==From FreeRTOS's webpage: [https://www.freertos.org/about-RTOS.html What is an RTOS?]==

===''What is a General Purpose Operating System?''===
''An operating system is a computer program that supports a computer’s basic functions, and provides services to other programs (or applications) that run on the computer. The applications provide the functionality that the user of the computer wants or needs. The services provided by the operating system make writing the applications faster, simpler, and more maintainable. If you are reading this web page, then you are using a web browser (the application program that provides the functionality you are interested in), which will itself be running in an environment provided by an operating system.''

===''What is an RTOS?''===
''Most operating systems appear to allow multiple programs to execute at the same time. This is called multi-tasking. In reality, each processor core can only be running a single thread of execution at any given point in time. A part of the operating system called the scheduler is responsible for deciding which program to run when, and provides the illusion of simultaneous execution by rapidly switching between each program.
The type of an operating system is defined by how the scheduler decides which program to run when. For example, the scheduler used in a multi user operating system (such as Unix) will ensure each user gets a fair amount of the processing time. As another example, the scheduler in a desk top operating system (such as Windows) will try and ensure the computer remains responsive to its user. [Note: FreeRTOS is not a big operating system, nor is it designed to run on a desktop computer class processor, I use these examples purely because they are systems readers will be familiar with]''

''The scheduler in a Real Time Operating System (RTOS) is designed to provide a predictable (normally described as deterministic) execution pattern. This is particularly of interest to embedded systems as embedded systems often have real time requirements. A real time requirements is one that specifies that the embedded system must respond to a certain event within a strictly defined time (the deadline). A guarantee to meet real time requirements can only be made if the behaviour of the operating system’s scheduler can be predicted (and is therefore deterministic).''

''Traditional real time schedulers, such as the scheduler used in FreeRTOS, achieve determinism by allowing the user to assign a priority to each thread of execution. The scheduler then uses the priority to know which thread of execution to run next. In FreeRTOS, a thread of execution is called a task.''

===''What is FreeRTOS?''===
''FreeRTOS is a class of RTOS that is designed to be small enough to run on a microcontroller – although its use is not limited to microcontroller applications.''

''A microcontroller is a small and resource constrained processor that incorporates, on a single chip, the processor itself, read only memory (ROM or Flash) to hold the program to be executed, and the random access memory (RAM) needed by the programs it executes. Typically the program is executed directly from the read only memory.''

''Microcontrollers are used in deeply embedded applications (those applications where you never actually see the processors themselves, or the software they are running) that normally have a very specific and dedicated job to do. The size constraints, and dedicated end application nature, rarely warrant the use of a full RTOS implementation – or indeed make the use of a full RTOS implementation possible. FreeRTOS therefore provides the core real time scheduling functionality, inter-task communication, timing and synchronisation primitives only. This means it is more accurately described as a real time kernel, or real time executive. Additional functionality, such as a command console interface, or networking stacks, can then be included with add-on components.''

===What Next?===
For those unfamiliar with RTOS concepts we recommend checking out the FreeRTOS webpage [https://www.freertos.org/about-RTOS.html HERE]. FreeRTOS is extremely well documented and hence relatively easy to use. PDF documentation is provided [[CutiPy FreeRTOS Documentation | HERE]]. Of the most benefit is the [https://www.freertos.org/wp-content/uploads/2018/07/161204_Mastering_the_FreeRTOS_Real_Time_Kernel-A_Hands-On_Tutorial_Guide.pdf Mastering the FreeRTOS Real Time Kernel] reference document. FreeRTOS FAQs are addressed [https://www.freertos.org/FAQWhat.html#Kernel HERE]

===EMAC and FreeRTOS===
EMAC's software builds come with FreeRTOS already imported, letting the user jump-in and start using FreeRTOS functionality immediately.

{{:Templateimpl:whatnext | initials=BS | title=Getting Started with the EMAC OE SDK | desc=Basic tutorial for using the EMAC OE SDK. | project=OE 5.0 }}

[[ Getting Started with CutiPy and FreeRTOS | Getting Started with CutiPy and FreeRTOS ]]

[[CutiPy FreeRTOS Documentation | CutiPy FreeRTOS Documentation]]

[[ Getting Started with MitiPy and FreeRTOS | Getting Started with MitiPy and FreeRTOS ]]

[[MitiPy FreeRTOS Documentation | MitiPy FreeRTOS Documentation]]

[[STM32CubeIDE | STM32CubeIDE]]

2020-03-24T23:13:56Z

CBost:

{{#seo:
|title=Getting Started with CutiPy and FreeRTOS
|titlemode=append
|keywords=Cutipy Getting Started
|description=The following page can be used to get familiarized with the Cutipy.
}}



This page outlines a basic guide to getting starting using the Cutipy.







{{:Templateimpl:geninfo | initials=BS | title=Cutipy Getting Started | desc=The following page can be used to get familiarized with the Cutipy. | project=OE 5.0 }}
=== Tools Required ===
*Desktop PC (Windows/Linux/Mac will work)
*Micro-USB to USB Cable
*ST-LINK/V2 in-circuit debugger/programmer for STM8 and STM32 with JTAG 20 pin to SWD 10pin adaptor

=== Setup ===
1. Download and install [https://www.st.com/en/development-tools/stm32cubeide.html STM32CubeIDE] (The IDE used for CutiPy FreeRTOS development, For more information on the STM32CubeIDE click [[STM32CubeIDE | HERE]]) 
2. Download EMAC's CutiPy FreeRTOS project master branch [http://git.emacinc.com/FreeRTOS/CutiPy_FreeRTOS HERE]
3. Connect the ST-Link programmer to the CutiPy board for programming 
*''Connect the 10 pin SWD connector (small ribbon cable) to the CutiPy Board HDR6. Ensure the the painted red wire of the cable is on the same side as the arrow.Connect the other end to the adaptor, again ensuring the arrow is aligned with painted red wire. Connect the ST-Link to the adaptor with the large ribbon cable, and connect the ST-LINK to your desktop with it's provided USB cable'' 

4. Connect your CutiPy to Desktop using the micro-USB to USB cable. Your board is now powered. 
5. Open STM32CubeIDE and import the CutiPy FreeRTOS project 
*If needed, upgrade your ST-LINK firmware by navigating to '''Help''' and selecting '''ST-LINK Upgrade'''. The ST Link upgrade window will open. Select '''refresh device list''', and then select '''Open in update mode''', and finally '''Upgrade''' 
[[File:STLinkUpgrade.png]]
6. Build and upload the firmware 
*''To build and upload select the debug symbol (To just build select the hammer symbol)''. 
[[File:DebugToolbar1.png]]




{{:Templateimpl:using | initials=BS | title=Developing with the Cutipy | desc=The following page can be used to get familiarized with Micropython the Cutipy. | project=OE 5.0 }}

1.The baseline CutiPy FreeRTOS build has now been uploaded. Connect to the USB virtual com port on a serial terminal using Putty or TerraTerm. The USB virtual com port driver should install automatically after plugging the CutiPy to your PC. After successful installation of the driver '''STMMicroelectronics Virtual COM Port''' should be displayed as an available port. Connect to it as you would any normal serial port. 
[[File:USBcomPORT.png]]
* Using a serial terminal program like '''Putty''' or '''Tera Term''' connect to the port at a baud rate of 115200.

[[File:serial.png]]

{{note|The USB virtual com port will adjust it's baud rate to that selected by the terminal. It has been tested to work with standard baud rate selections from 110 to 921600.}}

2.After connecting the CutiPy FreeRTOS menu will be displayed. Navigate to tests for a demonstration of CutiPy functionality.

[[File:TestMenu.png]]

{{:Templateimpl:using | initials=BS | title='''EMAC CutiPy FreeRTOS Software Description''' | desc=The following page can be used to get familiarized with Micropython the Cutipy. | project=OE 5.0 }}

=== Project Layout ===

The CutiPy_FreeRTOS project was developed using the STM32CubeIDE. It contains auto-generated program files and code along with custom files/folders provided by EMAC.
{{note|editing of auto-generated code blocks and files should be avoided as these portions of the project will be overwritten if the auto-code generation feature of STM32CubeIDE is used (STM32CubeMX). Instead we recommend the user create their own custom folders in the project or just use the EMAC provided folder, '''CutiPy_User''' for project development.}}

Custom EMAC folder include: 
*'''CutiPy_Drivers''' provides custom written EMAC driver functions geared towards use with the CutiPy device. All functions are documented in their respective source files, hence the user should look here for function usage-rules and functionality. The functions written at a CutiPy module (COM A, COM B, SD_CARD, RS9116 radio, etc.) or individual driver level and were written with ease of use in mind.'''CP_FRTOS.c/h''' contains all FreeRTOS element declarations (Task handles, mutex handle, etc.) Here system level tasks and priorities can be adjusted if needed. '''CutiPy_Config.h''', contains options to turn off the menu to save memory space.

*'''CutiPy_Tasks''' contains the header and source files for the CutiPy freeRTOS for all EMAC provided system tasks. Task descriptions are provided in their respective source files 
*'''CutiPy_User''' is an empty project folder dedicated for use by the user.
*'''RS9116_1_2_1''' and ''''''RS9116_1_2_1/examples/utilities''' contain driver files for the Redpine Signals RS9116 radio module.

The only folders of real importance to the user is the CutiPy_Drivers folder. In addition to containing key driver functions it also contains CP_FRTOS.c that lists system task
priority, handle and size, and

Other project folders include:

*'''Middlewares'''- contains source files for the USB Virtual Com Port, fatfs (used mainly in conjuction with the sd card), and FreeRTOS. 
*'''Drivers''' -contains STMicroelectronic's driver files. The user should look here for driver functionality not covered by the provide emac driver files
*'''Src''' -contains initialization functions, and '''main.c'''
*'''Inc''' -contains various include files, but the only one of primary importance '''FreeRTOSConfig.h''' file 

=== Software Overview ===
[[File:diagrammm.png]]

CutiPy RTOS system-level tasks and synchronization have been provided by EMAC to ease user development.

=== Feature Description ===
EMAC has provided custom driver functions for the CutiPy's main peripherals. These are located under '''CutiPy_Drivers'''. See the source files for function descriptions. All of EMAC's custom functions will be prefixed by '''CP_''' followed by the the '''DRIVER_NAME'''. Functions with the prefix '''CP_FRTOS''' utilize an RTOS element and should only
be called with the scheduler running. We recommend user files be added to the '''CutiPy_User''' or that the user add their own custom folders, and not modify the project code directly. EMAC has provide custom system tasks to ease CutiPy use and jump-start user development.

'''ADCs'''- The CutiPy utilizes the STM32F407's 3 internal ADCs. Thirteen ADC pins are available to the user on HDR2. '''CP_ADC.c''' CP_FRTOS functions provide thread safe functionality through mutex control of the 3 ADC's. Aside from 'external' pin sampling this driver file also provide functions for sampling the internal temp sensor, the ram back up battery voltage, and the internal reference voltage (used for calculating the voltage from a raw read)

'''BATTERIES''' -The CuitPy has the option of being powered by an external 3.7 V 1200mah lithium ion rechargeable battery (EMAC Part#: PER-PWR0101PR0). It also has an onboard, jumper-enable 3.3V RTC-Ram Retention battery (See the CutiPy User Manual for more information. '''CP_BATTERIES.c''' contains functions for reading these battery voltages.

''''BUTTONS''' - Depending on the model of your CutiPy there can be up to 5 buttons, 1 Reset button + 4 user buttons (PB1 through PB4). All user buttons except PB3 are interrupt driven (rising and falling edge), hence there respective tasks block (don't run) until the interrupt is generated. PB3 is polled intermittently enough to avoid missed presses, but not so much as to block out other tasks. Callback functions are provided in '''CP_BUTTONS.C'''. The user may simply edit these functions directly, to implement unique callback functionality. Button Tasks are located in '''C

'''CAN'''-CAN communication is provided through HDR4 CAN1. The CAN1 subsystem consists of the STM32407's onboard CAN1 module an external CAN tranceiver (TCAN334GDCNT). '''CP_CAN.c''' contains easy-to-use functions for message reception/transmission, and module/tranceiver mode manipulation. An example use function is also included, as well as an internal loopback test. Note CAN1 is currently configured for baud rate of 500kHz.

'''COM_A''' COM_A consists of UART2 routed to an external RS-232 transceiver connected to the CN2 (The DB9 port). It is configured for baud rate of 115200. '''CP_COM_A.c''' provide driver functions for transceiver configuration and message transmission and reception. Two seperate mutexes are provided (CP_COM_A_RX_RecursiveMutexHandle and CP_COM_A_TX_RecursiveMutexHandle).

'''COM_B''' COM_B consists of UART3 an RS232 transceiver and an RS422/485 transceiver. The active transceiver is user selectable, and only one can be active at a time. '''CP_COM_B.c''' provides driver functions for message transmission/receipt and transceiver selection. For thread safe usage a mutex is provided (CP_COM_B_RecursiveMutexHandle).

'''DACs''' The STM32F407 two digital analog converter channels are available on HDR2, pins 20 and 21. Driver functions are provided '''CP_DAC.c'''.

'''DARLINGTON OPEN COLLECTOR DRIVERS''' Eight gpios are connected and control 8 darlington pair open collector transistors. The Darlington pair transistors have superior current sinking capabilities when compared to the on-board GPIOs. (See the ULN2803A datasheet for more information). A pull-up resistor connects the Collector end of the Darlington transistor to V_HIDRV-This is left floating, but can be used by the user to enable digital toggling between GND and V_HIDRV. With V_HIDRV left unconnected the darlington transistor is used as a switch, that sinks current in the ON position. '''CP_DARLINGTON_OC.c''' provides functions for setting/resetting. Thread safe control is achieved through the use of mutexes(CP_DARLINGTON_OC_PGX_RecursiveMutexHandle).

'''LCD''' On some models of the CutiPy an NHD-C12832A1Z-FSW-3V3 Liquid Crystal Display (LCD) Module is available for the display of text and simple images. The LCD communicates with the MCU via SPI2. '''CP_LCD.c''' contains functions for displaying text, writing individual pixels, issuing commands, etc. Note that mutex control of SPI2 is required as it is shared between the radio module and the LCD module. This feature has already been implemented by EMAC, thus all LCD and radio functions can be used together, from multiple threads/tasks without worrying about conflict.

'''LEDs''' Four LEDs are present on the CutiPy board (LD1 - LD4). They are controlled through the toggling of GPIO outputs on the MCU. '''CP_LEDs.c''' contains easy to use function for the controlling the LEDs (ON, OFF, Toggle)

'''RNG''' The STM32F407 true random number generator (RNG) is pre-initialized. The RNG generates 32 bit random numbers. '''CP_RNG.c''' contains simple 'get value' functions. The radio utilizes the RNG for certain encrpytion purposes, for this reason CP_FRTOS_GetRandomValue() should be use for thread-safe access.

'''RS9116 Wireless Module''' The external RS9116 Wireless Module enables the development of Bluetooth Low Energy (BLE), Bluetooth (BT) and WLAN applications. In WLAN mode the RS9116 is able function as an access point or a client. The module also has the ability to operate in dual mode (WLAN +BLE). '''RS9116.c''' contains initialization functions for the radio, as well as basic use functions like connect/disconnect and sleep. Other functions and advanced usage is covered in the RS9116 documentation.

'''MicroSD Card''' The CutiPy comes with a MicroSD slot.The CutiPy_FreeRTOS build comes with FatFs for the manipulation of files (See the FatFs documentation for more information). Demos are provided in '''CP_SD_CARD.c'''

===Documentation===

[[CutiPy_FreeRTOS_Documentation | CutiPy FreeRTOS Documentation]]

 

{{:Templateimpl:whatnext | initials=BS | title=Getting Started with the EMAC OE SDK | desc=Basic tutorial for using the EMAC OE SDK. | project=OE 5.0 }}

[[CutiPy FreeRTOS Documentation | CutiPy FreeRTOS Documentation]]

[[ STM32CubeIDE | STM32CubeIDE ]]

[[FreeRTOS | FreeRTOS]]

2020-03-23T21:37:57Z

CBost:

CutiPy FreeRTOS Documentation

2020-03-23T21:35:31Z

CBost: /* Redpine Signal RS9116 Radio Module */

Getting Started with CutiPy and FreeRTOS

2020-03-23T16:12:34Z

CBost:

{{#seo:
|title=Getting Started with CutiPy and FreeRTOS
|titlemode=append
|keywords=Cutipy Getting Started
|description=The following page can be used to get familiarized with the Cutipy.
}}



This page outlines a basic guide to getting starting using the Cutipy.







{{:Templateimpl:geninfo | initials=BS | title=Cutipy Getting Started | desc=The following page can be used to get familiarized with the Cutipy. | project=OE 5.0 }}
=== Tools Required ===
*Desktop PC (Windows/Linux/Mac will work)
*Micro-USB to USB Cable
*ST-LINK/V2 in-circuit debugger/programmer for STM8 and STM32 with JTAG 20 pin to SWD 10pin adaptor

=== Setup ===
1. Download and install [https://www.st.com/en/development-tools/stm32cubeide.html STM32CubeIDE] (The IDE used for CutiPy FreeRTOS development, For more information on the STM32CubeIDE click [[STM32CubeIDE | HERE]]) 
2. Download EMAC's CutiPy FreeRTOS project master branch [http://git.emacinc.com/FreeRTOS/CutiPy_FreeRTOS HERE]
3. Connect the ST-Link programmer to the CutiPy board for programming 
*''Connect the 10 pin SWD connector (small ribbon cable) to the CutiPy Board HDR6. Ensure the the painted red wire of the cable is on the same side as the arrow.Connect the other end to the adaptor, again ensuring the arrow is aligned with painted red wire. Connect the ST-Link to the adaptor with the large ribbon cable, and connect the ST-LINK to your desktop with it's provided USB cable'' 

4. Connect your CutiPy to Desktop using the micro-USB to USB cable. Your board is now powered. 
5. Open STM32CubeIDE and import the CutiPy FreeRTOS project 
*If needed, upgrade your ST-LINK firmware by navigating to '''Help''' and selecting '''ST-LINK Upgrade'''. The ST Link upgrade window will open. Select '''refresh device list''', and then select '''Open in update mode''', and finally '''Upgrade''' 
[[File:STLinkUpgrade.png]]
6. Build and upload the firmware 
*''To build and upload select the debug symbol (To just build select the hammer symbol)''. 
[[File:DebugToolbar1.png]]




{{:Templateimpl:using | initials=BS | title=Developing with the Cutipy | desc=The following page can be used to get familiarized with Micropython the Cutipy. | project=OE 5.0 }}

1.The baseline CutiPy FreeRTOS build has now been uploaded. Connect to the USB virtual com port on a serial terminal using Putty or TerraTerm. The USB virtual com port driver should install automatically after plugging the CutiPy to your PC. After successful installation of the driver '''STMMicroelectronics Virtual COM Port''' should be displayed as an available port. Connect to it as you would any normal serial port. 
[[File:USBcomPORT.png]]
* Using a serial terminal program like '''Putty''' or '''Tera Term''' connect to the port at a baud rate of 115200.

[[File:serial.png]]

{{note|The USB virtual com port will adjust it's baud rate to that selected by the terminal. It has been tested to work with standard baud rate selections from 110 to 921600.}}
{{note|COM A, the DB9 port may also be used for establishing an RS232 serial connection. It is configured for a baud rate of 115200.}}

2.After connecting the CutiPy FreeRTOS menu will be displayed. Navigate to tests for a demonstration of CutiPy functionality.

{{:Templateimpl:using | initials=BS | title='''EMAC CutiPy FreeRTOS Software Description''' | desc=The following page can be used to get familiarized with Micropython the Cutipy. | project=OE 5.0 }}

=== Project Layout ===

The CutiPy_FreeRTOS project was developed using the STM32CubeIDE. It contains auto-generated program files and code along with custom files/folders provided by EMAC.
{{note|editing of auto-generated code blocks and files should be avoided as these portions of the project will be overwritten if the auto-code generation feature of STM32CubeIDE is used (STM32CubeMX). Instead we recommend the user create their own custom folders in the project or just use the EMAC provided folder, '''CutiPy_User''' for project development.}}

Custom EMAC folder include: 
*'''CutiPy_Drivers''' provides custom written EMAC driver functions geared towards use with the CutiPy device. All functions are documented in their respective source files, hence the user should look here for function usage-rules and functionality. The functions written at a CutiPy module (COM A, COM B, SD_CARD, RS9116 radio, etc.) or individual driver level and were written with ease of use in mind. 

*'''CutiPy_Tasks''' contains the header and source files for the CutiPy freeRTOS for all EMAC provided system tasks. Task descriptions are provided in their respective source files 
*'''CutiPy_User''' is an empty project folder dedicated for use by the user.
*'''RS9116_1_2_1''' and ''''''RS9116_1_2_1/examples/utilities''' contain driver files for the Redpine Signals RS9116 radio module.

The only folders of real importance to the user is the CutiPy_Drivers folder. In addition to containing key driver functions it also contains CP_FRTOS.c that lists system task
priority, handle and size, and

Other project folders include:

*'''Middlewares'''- contains source files for the USB Virtual Com Port, fatfs (used mainly in conjuction with the sd card), and FreeRTOS. 
*'''Drivers''' -contains STMicroelectronic's driver files. The user should look here for driver functionality not covered by the provide emac driver files
*'''Src''' -contains initialization functions, and '''main.c'''
*'''Inc''' -contains various include files, but the only one of primary importance '''FreeRTOSConfig.h''' file 

=== Software Overview ===
[[File:diagrammm.png]]

CutiPy RTOS system-level tasks and synchronization have been provided by EMAC to ease user development.

=== Feature Description ===
EMAC has provided custom driver functions for the CutiPy's main peripherals. These are located under '''CutiPy_Drivers'''. See the source files for function descriptions. All of EMAC's custom functions will be prefixed by '''CP_''' followed by the the '''DRIVER_NAME'''. Functions with the prefix '''CP_FRTOS''' utilize an RTOS element and should only
be called with the scheduler running. We recommend user files be added to the '''CutiPy_User''' or that the user add their own custom folders, and not modify the project code directly. EMAC has provide custom system tasks to ease CutiPy use and jump-start user development.

'''ADCs'''- The CutiPy utilizes the STM32F407's 3 internal ADCs. Thirteen ADC pins are available to the user on HDR2. '''CP_ADC.c''' CP_FRTOS functions provide thread safe functionality through mutex control of the 3 ADC's. Aside from 'external' pin sampling this driver file also provide functions for sampling the internal temp sensor, the ram back up battery voltage, and the internal reference voltage (used for calculating the voltage from a raw read)

'''BATTERIES''' -The CuitPy has the option of being powered by an external 3.7 V 1200mah lithium ion rechargeable battery (EMAC Part#: PER-PWR0101PR0). It also has an onboard, jumper-enable 3.3V RTC-Ram Retention battery (See the CutiPy User Manual for more information. '''CP_BATTERIES.c''' contains functions for reading these battery voltages.

''''BUTTONS''' - Depending on the model of your CutiPy there can be up to 5 buttons, 1 Reset button + 4 user buttons (PB1 through PB4). All user buttons except PB3 are interrupt driven (rising and falling edge), hence there respective tasks block (don't run) until the interrupt is generated. PB3 is polled intermittently enough to avoid missed presses, but not so much as to block out other tasks. Callback functions are provided in '''CP_BUTTONS.C'''. The user may simply edit these functions directly, to implement unique callback functionality. Button Tasks are located in '''C

'''CAN'''-CAN communication is provided through HDR4 CAN1. The CAN1 subsystem consists of the STM32407's onboard CAN1 module an external CAN tranceiver (TCAN334GDCNT). '''CP_CAN.c''' contains easy-to-use functions for message reception/transmission, and module/tranceiver mode manipulation. An example use function is also included, as well as an internal loopback test. Note CAN1 is currently configured for baud rate of 500kHz.

'''COM_A''' COM_A consists of UART2 routed to an external RS-232 transceiver connected to the CN2 (The DB9 port). It is configured for baud rate of 115200. '''CP_COM_A.c''' provide driver functions for transceiver configuration and message transmission and reception. Two seperate mutexes are provided (CP_COM_A_RX_RecursiveMutexHandle and CP_COM_A_TX_RecursiveMutexHandle).

'''COM_B''' COM_B consists of UART3 an RS232 transceiver and an RS422/485 transceiver. The active transceiver is user selectable, and only one can be active at a time. '''CP_COM_B.c''' provides driver functions for message transmission/receipt and transceiver selection. For thread safe usage a mutex is provided (CP_COM_B_RecursiveMutexHandle).

'''DACs''' The STM32F407 two digital analog converter channels are available on HDR2, pins 20 and 21. Driver functions are provided '''CP_DAC.c'''.

'''DARLINGTON OPEN COLLECTOR DRIVERS''' Eight gpios are connected and control 8 darlington pair open collector transistors. The Darlington pair transistors have superior current sinking capabilities when compared to the on-board GPIOs. (See the ULN2803A datasheet for more information). A pull-up resistor connects the Collector end of the Darlington transistor to V_HIDRV-This is left floating, but can be used by the user to enable digital toggling between GND and V_HIDRV. With V_HIDRV left unconnected the darlington transistor is used as a switch, that sinks current in the ON position. '''CP_DARLINGTON_OC.c''' provides functions for setting/resetting. Thread safe control is achieved through the use of mutexes(CP_DARLINGTON_OC_PGX_RecursiveMutexHandle).

'''LCD''' On some models of the CutiPy an NHD-C12832A1Z-FSW-3V3 Liquid Crystal Display (LCD) Module is available for the display of text and simple images. The LCD communicates with the MCU via SPI2. '''CP_LCD.c''' contains functions for displaying text, writing individual pixels, issuing commands, etc. Note that mutex control of SPI2 is required as it is shared between the radio module and the LCD module. This feature has already been implemented by EMAC, thus all LCD and radio functions can be used together, from multiple threads/tasks without worrying about conflict.

'''LEDs''' Four LEDs are present on the CutiPy board (LD1 - LD4). They are controlled through the toggling of GPIO outputs on the MCU. '''CP_LEDs.c''' contains easy to use function for the controlling the LEDs (ON, OFF, Toggle)

'''RNG''' The STM32F407 true random number generator (RNG) is pre-initialized. The RNG generates 32 bit random numbers. '''CP_RNG.c''' contains simple 'get value' functions. The radio utilizes the RNG for certain encrpytion purposes, for this reason CP_FRTOS_GetRandomValue() should be use for thread-safe access.

'''RS9116 Wireless Module''' The external RS9116 Wireless Module enables the development of Bluetooth Low Energy (BLE), Bluetooth (BT) and WLAN applications. In WLAN mode the RS9116 is able function as an access point or a client. The module also has the ability to operate in dual mode (WLAN +BLE). '''RS9116.c''' contains initialization functions for the radio, as well as basic use functions like connect/disconnect and sleep. Other functions and advanced usage is covered in the RS9116 documentation.

'''MicroSD Card''' The CutiPy comes with a MicroSD slot.The CutiPy_FreeRTOS build comes with FatFs for the manipulation of files (See the FatFs documentation for more information). A Demo functions are provided in '''CP_SD_CARD.c'''

===Documentation===

[[CutiPy_FreeRTOS_Documentation | CutiPy FreeRTOS Documentation]]

 

{{:Templateimpl:whatnext | initials=BS | title=Getting Started with the EMAC OE SDK | desc=Basic tutorial for using the EMAC OE SDK. | project=OE 5.0 }}

[http://git.emacinc.com/micropython-public/micropython-doc CutiPy Micropython Documentation]

[[ Cutipy_Test | Cutipy Test Software ]]

[[ Cutipy-MicroPython Bluetooth LE demo | Cutipy-MicroPython Bluetooth LE demo ]]

[[ Micropython | Micropython ]]

[[CutiPy-Installing_MicroPython_Firmware | CutiPy-Installing Micropython Firmware]]

2020-03-23T15:59:20Z

CBost:

{{#seo:
|title=Getting Started with CutiPy and FreeRTOS
|titlemode=append
|keywords=Cutipy Getting Started
|description=The following page can be used to get familiarized with the Cutipy.
}}



This page outlines a basic guide to getting starting using the Cutipy.







{{:Templateimpl:geninfo | initials=BS | title=Cutipy Getting Started | desc=The following page can be used to get familiarized with the Cutipy. | project=OE 5.0 }}
=== Tools Required ===
*Desktop PC (Windows/Linux/Mac will work)
*Micro-USB to USB Cable
*ST-LINK/V2 in-circuit debugger/programmer for STM8 and STM32 with JTAG 20 pin to SWD 10pin adaptor

=== Setup ===
1. Download and install [https://www.st.com/en/development-tools/stm32cubeide.html STM32CubeIDE] (The IDE used for CutiPy FreeRTOS development, For more information on the STM32CubeIDE click [[STM32CubeIDE | HERE]]) 
2. Download EMAC's CutiPy FreeRTOS project master branch [http://git.emacinc.com/FreeRTOS/CutiPy_FreeRTOS HERE]
3. Connect the ST-Link programmer to the CutiPy board for programming 
*''Connect the 10 pin SWD connector (small ribbon cable) to the CutiPy Board HDR6. Ensure the the painted red wire of the cable is on the same side as the arrow.Connect the other end to the adaptor, again ensuring the arrow is aligned with painted red wire. Connect the ST-Link to the adaptor with the large ribbon cable, and connect the ST-LINK to your desktop with it's provided USB cable'' 

4. Connect your CutiPy to Desktop using the micro-USB to USB cable. Your board is now powered. 
5. Open STM32CubeIDE and import the CutiPy FreeRTOS project 
*If needed, upgrade your ST-LINK firmware by navigating to '''Help''' and selecting '''ST-LINK Upgrade'''. The ST Link upgrade window will open. Select '''refresh device list''', and then select '''Open in update mode''', and finally '''Upgrade''' 
[[File:STLinkUpgrade.png]]
6. Build and upload the firmware 
*''To build and upload select the debug symbol (To just build select the hammer symbol)''. 
[[File:DebugToolbar1.png]]




{{:Templateimpl:using | initials=BS | title=Developing with the Cutipy | desc=The following page can be used to get familiarized with Micropython the Cutipy. | project=OE 5.0 }}

1.The baseline CutiPy FreeRTOS build has now been uploaded. Connect to the USB virtual com port on a serial terminal using Putty or TerraTerm. The USB virtual com port driver should install automatically after plugging the CutiPy to your PC. After successful installation of the driver '''STMMicroelectronics Virtual COM Port''' should be displayed as an available port. Connect to it as you would any normal serial port. 
[[File:USBcomPORT.png]]

{{note|The USB virtual com port will adjust it's baud rate to that selected by the terminal. It has been tested to work with standard baud rate selections from 110 to 921600.}}

2.After connecting the CutiPy FreeRTOS menu will be displayed. Navigate to tests for a demonstration of CutiPy functionality.

{{:Templateimpl:using | initials=BS | title='''EMAC CutiPy FreeRTOS Software Description''' | desc=The following page can be used to get familiarized with Micropython the Cutipy. | project=OE 5.0 }}

=== Project Layout ===

The CutiPy_FreeRTOS project was developed using the STM32CubeIDE. It contains auto-generated program files and code along with custom files/folders provided by EMAC.
{{note|editing of auto-generated code blocks and files should be avoided as these portions of the project will be overwritten if the auto-code generation feature of STM32CubeIDE is used (STM32CubeMX). Instead we recommend the user create their own custom folders in the project or just use the EMAC provided folder, '''CutiPy_User''' for project development.}}

Custom EMAC folder include: 
*'''CutiPy_Drivers''' provides custom written EMAC driver functions geared towards use with the CutiPy device. All functions are documented in their respective source files, hence the user should look here for function usage-rules and functionality. The functions written at a CutiPy module (COM A, COM B, SD_CARD, RS9116 radio, etc.) or individual driver level and were written with ease of use in mind. 

*'''CutiPy_Tasks''' contains the header and source files for the CutiPy freeRTOS for all EMAC provided system tasks. Task descriptions are provided in their respective source files 
*'''CutiPy_User''' is an empty project folder dedicated for use by the user.
*'''RS9116_1_2_1''' and ''''''RS9116_1_2_1/examples/utilities''' contain driver files for the Redpine Signals RS9116 radio module.

The only folders of real importance to the user is the CutiPy_Drivers folder. In addition to containing key driver functions it also contains CP_FRTOS.c that lists system task
priority, handle and size, and

Other project folders include:

*'''Middlewares'''- contains source files for the USB Virtual Com Port, fatfs (used mainly in conjuction with the sd card), and FreeRTOS. 
*'''Drivers''' -contains STMicroelectronic's driver files. The user should look here for driver functionality not covered by the provide emac driver files
*'''Src''' -contains initialization functions, and '''main.c'''
*'''Inc''' -contains various include files, but the only one of primary importance '''FreeRTOSConfig.h''' file 

=== Software Overview ===
[[File:diagrammm.png]]

CutiPy RTOS system-level tasks and synchronization have been provided by EMAC to ease user development.

=== Feature Description ===
EMAC has provided custom driver functions for the CutiPy's main peripherals. These are located under '''CutiPy_Drivers'''. See the source files for function descriptions. All of EMAC's custom functions will be prefixed by '''CP_''' followed by the the '''DRIVER_NAME'''. Functions with the prefix '''CP_FRTOS''' utilize an RTOS element and should only
be called with the scheduler running. We recommend user files be added to the '''CutiPy_User''' or that the user add their own custom folders, and not modify the project code directly. EMAC has provide custom system tasks to ease CutiPy use and jump-start user development.

'''ADCs'''- The CutiPy utilizes the STM32F407's 3 internal ADCs. Thirteen ADC pins are available to the user on HDR2. '''CP_ADC.c''' CP_FRTOS functions provide thread safe functionality through mutex control of the 3 ADC's. Aside from 'external' pin sampling this driver file also provide functions for sampling the internal temp sensor, the ram back up battery voltage, and the internal reference voltage (used for calculating the voltage from a raw read)

'''BATTERIES''' -The CuitPy has the option of being powered by an external 3.7 V 1200mah lithium ion rechargeable battery (EMAC Part#: PER-PWR0101PR0). It also has an onboard, jumper-enable 3.3V RTC-Ram Retention battery (See the CutiPy User Manual for more information. '''CP_BATTERIES.c''' contains functions for reading these battery voltages.

''''BUTTONS''' - Depending on the model of your CutiPy there can be up to 5 buttons, 1 Reset button + 4 user buttons (PB1 through PB4). All user buttons except PB3 are interrupt driven (rising and falling edge), hence there respective tasks block (don't run) until the interrupt is generated. PB3 is polled intermittently enough to avoid missed presses, but not so much as to block out other tasks. Callback functions are provided in '''CP_BUTTONS.C'''. The user may simply edit these functions directly, to implement unique callback functionality. Button Tasks are located in '''C

'''CAN'''-CAN communication is provided through HDR4 CAN1. The CAN1 subsystem consists of the STM32407's onboard CAN1 module an external CAN tranceiver (TCAN334GDCNT). '''CP_CAN.c''' contains easy-to-use functions for message reception/transmission, and module/tranceiver mode manipulation. An example use function is also included, as well as an internal loopback test. Note CAN1 is currently configured for baud rate of 500kHz.

'''COM_A''' COM_A consists of UART2 routed to an external RS-232 transceiver connected to the CN2 (The DB9 port). It is configured for baud rate of 115200. '''CP_COM_A.c''' provide driver functions for transceiver configuration and message transmission and reception. Two seperate mutexes are provided (CP_COM_A_RX_RecursiveMutexHandle and CP_COM_A_TX_RecursiveMutexHandle).

'''COM_B''' COM_B consists of UART3 an RS232 transceiver and an RS422/485 transceiver. The active transceiver is user selectable, and only one can be active at a time. '''CP_COM_B.c''' provides driver functions for message transmission/receipt and transceiver selection. For thread safe usage a mutex is provided (CP_COM_B_RecursiveMutexHandle).

'''DACs''' The STM32F407 two digital analog converter channels are available on HDR2, pins 20 and 21. Driver functions are provided '''CP_DAC.c'''.

'''DARLINGTON OPEN COLLECTOR DRIVERS''' Eight gpios are connected and control 8 darlington pair open collector transistors. The Darlington pair transistors have superior current sinking capabilities when compared to the on-board GPIOs. (See the ULN2803A datasheet for more information). A pull-up resistor connects the Collector end of the Darlington transistor to V_HIDRV-This is left floating, but can be used by the user to enable digital toggling between GND and V_HIDRV. With V_HIDRV left unconnected the darlington transistor is used as a switch, that sinks current in the ON position. '''CP_DARLINGTON_OC.c''' provides functions for setting/resetting. Thread safe control is achieved through the use of mutexes(CP_DARLINGTON_OC_PGX_RecursiveMutexHandle).

'''LCD''' On some models of the CutiPy an NHD-C12832A1Z-FSW-3V3 Liquid Crystal Display (LCD) Module is available for the display of text and simple images. The LCD communicates with the MCU via SPI2. '''CP_LCD.c''' contains functions for displaying text, writing individual pixels, issuing commands, etc. Note that mutex control of SPI2 is required as it is shared between the radio module and the LCD module. This feature has already been implemented by EMAC, thus all LCD and radio functions can be used together, from multiple threads/tasks without worrying about conflict.

'''LEDs''' Four LEDs are present on the CutiPy board (LD1 - LD4). They are controlled through the toggling of GPIO outputs on the MCU. '''CP_LEDs.c''' contains easy to use function for the controlling the LEDs (ON, OFF, Toggle)

'''RNG''' The STM32F407 true random number generator (RNG) is pre-initialized. The RNG generates 32 bit random numbers. '''CP_RNG.c''' contains simple 'get value' functions. The radio utilizes the RNG for certain encrpytion purposes, for this reason CP_FRTOS_GetRandomValue() should be use for thread-safe access.

'''RS9116 Wireless Module''' The external RS9116 Wireless Module enables the development of Bluetooth Low Energy (BLE), Bluetooth (BT) and WLAN applications. In WLAN mode the RS9116 is able function as an access point or a client. The module also has the ability to operate in dual mode (WLAN +BLE). '''RS9116.c''' contains initialization functions for the radio, as well as basic use functions like connect/disconnect and sleep. Other functions and advanced usage is covered in the RS9116 documentation.

'''MicroSD Card''' The CutiPy comes with a MicroSD slot.The CutiPy_FreeRTOS build comes with FatFs for the manipulation of files (See the FatFs documentation for more information). A Demo functions are provided in '''CP_SD_CARD.c'''

===Documentation===

[[CutiPy_FreeRTOS_Documentation | CutiPy FreeRTOS Documentation]]

 

{{:Templateimpl:whatnext | initials=BS | title=Getting Started with the EMAC OE SDK | desc=Basic tutorial for using the EMAC OE SDK. | project=OE 5.0 }}

[http://git.emacinc.com/micropython-public/micropython-doc CutiPy Micropython Documentation]

[[ Cutipy_Test | Cutipy Test Software ]]

[[ Cutipy-MicroPython Bluetooth LE demo | Cutipy-MicroPython Bluetooth LE demo ]]

[[ Micropython | Micropython ]]

[[CutiPy-Installing_MicroPython_Firmware | CutiPy-Installing Micropython Firmware]]