Giter Site home page Giter Site logo

imtatlantique-2022's Introduction

IMT Atlantique - 2022

Summary of session 1

  • Hardware progress

    • In 35 years, processing power has been multiplied by 70 while cost has been divided by 38000. It's difficult to imagine what we will get over the next ten years
  • Memory, processing power and application

    • In 1969, the mission to the Moon succeeded thanks to a computer with 72 KB of ROM and 4 KB of RAM
    • It's possible to make a lot with only few resources
    • Nowadays, a microcontroller costing less than 2โ‚ฌ is more powerful than the Apollo computer
  • Connected device architecture

    • Computer vs microcontroller
      • Computer architecture: CPU, memory, interfaces with peripherals (an important one: disk drive), buses
      • In a computer, at boot time, a bootstrap program loads the OS into memory. Then the OS loads the applications
      • Thanks to the virtual memory mechanism provided by a computer OS, processes are isolated
      • A microcontroller: a whole computer on a chip
    • Memory
      • Evolution of ROM, which now can be erased and written
      • Memory map of a microcontroller
      • Many microcontroller provides a bootloader
    • Architecture
      • Overall architecture of a connected device
    • Important characteristics
      • Depend on the application
      • Some characteristics specific to the IoT
      • Hardware tools
      • Software tools
      • Support
    • Common microcontroller families for connected devices
      • Arm: a company that provides IP blocks, not microcontroller chips - The most widely used architecture
      • Many microcontroller manufacturers rely on Arm IP: Microchip, Nordic, NXP, STMicroelectronics, Texas Instruments, etc.
      • STMicroelectronics STM32 family
      • Cypress PSoc family. Microcontrollers with analog blocks
      • Espressif ESP family. Wi-Fi (+ Bluetooth) microcontrollers
      • MangOH boards: an open source design based on a Sierra Wireless cellular communication module running Linux
      • Microcontrollers for a few US dollars, demonstration/development boards for a few tens of US dollars
  • Session 1 exercises

Summary of session 2

  • Solutions to session 1 exercises

  • Software development

    • Cross development
      • The application is developped for a target machine (microcontroller board) different from the development machine (desktop computer)
      • On the development machine: edit, compile, link and possibly emulate
      • With the development machine and the target board: flash, run, debug
      • Debugging may require some specific hardware tool
    • Execution environments
      • OS - mostly Linux based
        • Facilities similar to a desktop Linux, including package manager, GUI, etc.
        • Usual memory requirements: 512 MB to 1 GB of RAM, 1 GB to 8 GB of Flash (SD card <=> disk drive)
        • An MMU (Memory Management Unit) is required. Supports virtual memory and so process isolation
        • Linux can be built for no MMU
        • Many different distributions, often generated by Yocto
      • RTOS (Real Time OS)
        • Deterministic response time
        • Monolithic: RTOS + application can't be dissociated
        • A task may crash another task, or the whole application + RTOS
        • Usual memory requirements: a few KB of RAM, a few KB of Flash
        • Many different RTOSes
      • Bare metal
        • No OS, no RTOS, directly on the microcontroller
        • Abstraction layer may be provided (CMSIS, etc.)
    • Interruptions and background task
      • An interruption makes the microcontroller stop the current execution, save the context, run some dedicated short code, restore the context, resume the execution
      • Interrupt handler, Interrupt Service Routine (ISR)
      • Events that can generate interruptions: input signal change for a GPIO, timer events, UART events, A/D conversion events, etc. + some software events
      • Interrupt during an ISR execution: priorities
    • Usual architecture of a bare metal application
      • Saving energy: sleep modes
    • Code example: UART RX
    • Useful design patterns
      • Finite State Automaton (FSA) or Finite State Machine (FSM)
      • Ring buffer or circular buffer
  • Session 2 exercises

Summary of session 3

Summary of session 4

Summary of session 5

  • Debriefing about espidf-udp
  • Introduction to RTOS
  • Session 5 exercise: using espidf-udp as a code base,
    • Develop a python server which accepts at least one TCP connection request, and which creates a socket to receive data
    • Define a message format. Explain every decision you take
    • Add code to the python server to decode and display messages complying with the format you defined, received on the TCP socket
    • Develop an ESP32 application which connects to the server using a TCP socket, and which sends messages to the server over the socket, on a periodic basis

imtatlantique-2022's People

Contributors

pascalbod avatar

Stargazers

Charles Perno avatar GUOXIONG SUN avatar

Watchers

James Cloos avatar  avatar  avatar

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.