Skip to content

Create a New Project

Here are the steps required to create a new project:

Open NECTO Studio

  • Launch NECTO Studio from the start menu or desktop shortcut.

Start a New Project

  • Click on "Project" in the top menu.
  • Select "New" from the dropdown menu.

Configure Essential Project Settings

  • Enter a name for your project.
  • Choose a location to save your project files.

Select Project Type

NECTO Studio offers a range of project templates tailored to different development needs. Whether you’re creating a standard application, designing a complex UI, or building a reusable library, selecting the right project type gives you a head start with pre-configured files and outputs. Let’s break down each option!


πŸš€ Standard Project

  • Purpose: Create a standard C project, suitable for general embedded development.

  • Included Files:

    • CMakeLists.txt: Project build configuration.
    • main.c: Starter file with an empty main function.
  • Output Files:

    • .hex: Hexadecimal binary for MCU flashing.
    • .bin: Raw binary for deployment options.
  • Requirements:

    • No specific requirements β€” works with most setups.

πŸ–ΌοΈ Complex Designer Project

  • Purpose: Build complex graphical user interfaces with the LVGL library, targeting 32-bit MCUs.

  • Included Files:

    • CMakeLists.txt: Build configuration file.
    • main.c: Main source file with initialization logic.
    • main_screen.mscr: Blank screen template.
    • main_screen.c: Code for screen initialization.
  • Output Files:

    • .hex: Flashable binary for the MCU.
    • .bin: Raw binary format.
  • Requirements:

    • mikroSDK
    • Clock: > 64 MHz
    • Flash/ROM: > 180 kB
    • RAM: > 48 kB

🟩 Simple Designer Project

  • Purpose: Create lightweight UIs with small memory footprints for 8-bit, 16-bit, and 32-bit MCUs.

  • Included Files:

    • CMakeLists.txt: Build configuration.
    • main.c: Main source file with ready-to-use initialization logic.
    • main_screen.mscr: Blank screen template.
    • main_screen.c: Code for screen initialization.
  • Output Files:

    • .hex: Flashable binary for the MCU.
    • .bin: Raw binary format.
  • Requirements:

    • mikroSDK (no additional requirements).

πŸ“š Project with Library

  • Purpose: Create a C project with an integrated library and usage example.

  • Included Files:

    • CMakeLists.txt: Project build configuration.
    • main.c: Source file with an empty main function.
    • CMakeLists.txt: Separate configuration for library compilation.
    • lib.c: Ready-to-edit library source file.
  • Output Files:

    • .hex: Flashable binary for the MCU.
    • .a: Static library file with precompiled code.
  • Requirements:

    • No specific requirements β€” works out of the box.

πŸ› οΈ Library Project

  • Purpose: Build a reusable library in C for sharing across multiple projects.

  • Included Files:

    • CMakeLists.txt: Build configuration file.
    • lib.c: Empty, ready-to-edit source file for your library logic.
  • Output Files:

    • .a: Static library file with precompiled code.
  • Requirements:

    • No specific requirements β€” works with most setups.

Which Project Type Should You Choose?

  • If you’re building a regular firmware application β†’ Standard Project
  • If you want to create a rich, complex UI β†’ Complex Designer Project
  • For simpler UI designs β†’ Simple Designer Project
  • Need to test or package a library with an example? β†’ Project with Library
  • Want to build and share a standalone library? β†’ Library Project

Once you've picked your project type, click Next to configure the MCU and board settings! πŸš€

Configuration of Hardware Setup with Setups Wizard

The Setups Wizard in NECTO Studio is a powerful tool designed to streamline the configuration process for embedded hardware setups. This wizard guides users through selecting and configuring the appropriate compiler, development board, target microcontroller, display, and programmer/debugger device. Below is a detailed guide on how to use the Setups Wizard.

Compiler Selection

The first step in the Setups Wizard involves selecting the compiler that will be used for your project. NECTO Studio supports a variety of compilers:

  • GNU Project

    • GCC for ARM
    • GCC for RISC-V
  • LLVM Foundation

    • CLANG for ARM
    • CLANG for RISC-V
  • Microchip

    • MPLAB XC32
    • MPLAB XC16
    • MPLAB XC8
  • MIKROE

    • mikroC AI for ARM
    • mikroC AI for AVR
    • mikroC AI for dsPIC
    • mikroC AI for PIC
    • mikroC AI for PIC32

Advanced Compiler Settings

For each compiler, there is an advanced option that allows you to fine-tune various settings:

  • Compiler Settings:

    • ANSI Pack Bitfields: Enable or disable ANSI packing for bitfields.
    • Case Sensitivity: Toggle case sensitivity in the code.
    • Dynamic Linking for String Literals: Enable dynamic linking for string literals to save memory.
    • Generating Additional Files: Choose to generate additional files such as .LST (listing) and .ASM (assembly) files.
    • Long Hex Format: Enable the generation of long hexadecimal format.
  • Libraries Settings:

    • Choose SDK Version: Select the SDK version to use (latest mikroSDK version or bare metal version).
    • Redirecting Standard Output: Redirect standard output to the Application Output window within NECTO Studio or via UART protocol, with output readable through NECTO Studio's built-in UART Terminal tool.
    • Flatten GPIO Levels: Set GPIO levels (high, medium, or low) to optimize MCU memory efficiency.

GETTING STARTED TIP: For the successful completion of the Compiler Selection section, follow the instructions below:

  • Select GCC for ARM type of a compiler and click Next* in the upper right part of the NECTO Studio, to proceed to the Development Board Selection.*

Development Board Selection

Once the compiler is selected, the Setups Wizard filters the available development boards compatible with the chosen compiler.

Users can then select the appropriate development board for their project.

GETTING STARTED TIP: For the successful completion of the Development Board Selection section, follow the instructions below:

Select Fusion for ARM v8 type of a development board and click Next* in the upper right part of the NECTO Studio, to proceed to the Target Microcontroller Selection.*

Target Microcontroller Selection

After selecting the development board, the wizard filters the list of supported microcontrollers based on the chosen compiler and development board.

Users can select their target microcontroller unit (MCU) from this filtered list.

Advanced Microcontroller Settings

Each microcontroller has an advanced option for configuring specific settings:

  • Clock Settings: The clock settings are pre-configured at nominal values for most supported microcontrollers. However, users can adjust these settings as needed to match their project requirements.

GETTING STARTED TIP: For the successful completion of the Target Microcontroller Selection section, follow the instructions below:

Make sure MCU CARD for STM32 STM32F407ZG type of a microcontroller card remains selected and click Next* in the upper right part of the NECTO Studio, to proceed to the Display Selection.*

Display Selection

If applicable, users can select a TFT-based display for their project. The available displays vary in size (ranging from 3 to 7 inches) and type (capacitive and resistive). GETTING STARTED TIP: For the successful completion of the Display Selection section, follow the instructions below:

Make sure No display option remains selected and click Next* in the upper right part of the NECTO Studio, to proceed to the Programmer/Debugger Option.*

Programmer/Debugger Option

Finally, the Setups Wizard guides users in selecting a programmer/debugger device.

The options include:

  • CODEGRIP: Compatible with the Planet Debug feature for remote debugging.
  • GDB Server: Allows for debugging using GDB.
  • mikroProg: A versatile programmer/debugger device.

Advanced Programmer/Debugger Settings

Each programmer/debugger device has advanced settings for further configuration:

  • CODEGRIP Settings: Configure settings specific to CODEGRIP, ensuring compatibility with Planet Debug.
  • GDB Server Settings: Adjust settings for using the GDB server.
  • mikroProg Settings: Customize settings for the mikroProg device.

GETTING STARTED TIP: For the successful completion of the Programmer/Debugger Option section, follow the instructions below.

Make sure CODEGRIP option remains selected and click Finish* in the upper right part of the NECTO Studio, to proceed to the Review page.*

Review selected hardware settings

  • Review and rename the hardware setup.

Finish Project Setup

  • Click "Finish" to create the project.
  • NECTO Studio will generate the project structure and initial files.

By following these steps in the Setups Wizard, users can efficiently configure their hardware setup, ensuring all components are properly selected and configured for successful project development in NECTO Studio.

GETTING STARTED TIP:

Congratulations!

  • You have successfully created your new project inside NECTO Studio!
  • For the successful completion of the Getting Started section of this manual, please proceed to the Navigating the User Interface section.***