README.md

Firmware updates Over The Air

This project is to enable remote firmware updates using ESP32, STM32F103C8T6 and Geogle Firebase.The ESP32 connects to WiFi, downloads the bootloader and firmware code, and communicates with the STM32.

Table of Contents

1. Introduction
2. Hardware Connection
3. Problems And Solutions
4. Main Features
5. New Features

Introduction

The technological evolution of a car has been in sync with rapid advances in communication, information processing and electronic hardware systems. Starting with isolated Electronic Control Units (ECUs) for Engine Management and Anti Lock Braking, typical cars now use from 25 to 100 microcontrollers for providing many features to ensure comfort and safety to the driver and passengers. The ECUs used in the car, for handling its overall function, are controlled by complex software code called as the firmware. With a large number of ECUs present in a car, the size of code in a modern luxury car can exceed 100 million lines of code as compared to 5 to 6 million lines of code required for a supersonic fighter aircraft.

FOTA (Firmware Over The Air) is emerging as a new flexible solution for these problems. FOTA is already an established technology for mobile phones and its application to automotive domain helps to tackle rising complexity of automotive systems. FOTA is based on the wireless communication between firmware server located in Cloud and the Telematics Control Unit used in a car as a client to download the new firmware. FOTA can update firmware of a car at any location whether it is an assembly shop, a dealer location, a service workshop or the parking space of the owner. Besides, FOTA allows download of firmware in the background when the vehicle is running and informs the driver, owner or service person when the installation of the updated firmware can be started.

Hardware Connection

• Connections Between ESP and Master ECU
  TX2 RX2 in esp <--> RX1 TX1 in master ECU.
  
• Connections Between Master ECU and Slave1
  TX2 RX2 in master ECU <--> RX1 TX1 in Slave1.
  
• Battery system
  1- Common GND between ECU's
  2- Common +5V between ECU's
  3-
  

Problems And Solutions

• How we can send our commends ?
  Using NodeRed to set specific buttons and its payload.
  To creat this DashBoard.
  

• How this Dashboard could be worth to our system ?
  Create ESP project on arduino ide on MQTT example on mosquitto server and make our ESP subscribe speific topic like "FOTA/FromBrokerToEsp".
  Make our ESP publish on another topic like "FOTA/FromEspToBroker" and make debug button on node-red to synchronize the debug info to mqtt.
  

• How ESP could affect on master ECU ?
  ESP get each string from broker and based on it , ESP will form specific frames suitable for bootloader and send it thruogh uart.

• How Master ECU do communicate with other branchs ?
  using CAN protocal tree to communicate between master ECU and each node in this tree. Where the FOTA (Firmware Over-The-Air) project includes several functions for managing large data transmissions and communication between CAN nodes over the CAN (Controller Area Network) protocol. The CAN_TransmitData function handles the transmission of large data files by breaking them into smaller packets, ensuring each packet is transmitted before proceeding. The CAN_ReceiveData function manages the reception and reassembly of large data files, discarding remote frames to focus on data frames. Both CAN_Read_RP_Level and CAN_Read_WP_Level functions read the Read Protection (RP) and Write Protection (WP) levels, respectively, and transmit them over the CAN network. Additionally, the CAN_Receive_AllPendingMessages_FIFO0 and CAN_Receive_AllPendingMessages_FIFO1 functions read all pending messages from the CAN FIFO0 and FIFO1, storing them in a buffer. The CAN_Select_Func function determines the appropriate bootloader function to execute based on the received CAN frame's standard ID and filter match index, calling functions for reading version information, writing memory, erasing memory, or jumping to an application address. These functions ensure robust and reliable firmware updates over the CAN network, with proper error handling and checking mechanisms in place.

• How to handle application on ECU ?
  At first we send our program by commend from mqtt to ESP called "Write program".
  ESP will download file from Firebase and send it to stm in speific address that you specify it before through dashboard.
  Through dashboard, We will send order to jump to application. Bootloader will write on application1 flag in the last page that the application is valid then jump to application.
  Each reset in system bootloader asks at first about this flag. If it is valid, Bootloader will jump on it.
  If application receive order to jump to bootloader, We will clear this flag and reset our reset.
  

• How to prevent hacker to write or read on our ECU that already written on Flash memory ?
  We will make protection level of our flash memory level 1 in write and read.
  
  

• How can uou test this project ?
  You can follow this videos on our channel "yyyyyyyyy".
  
  

Main Features

This features are available for each node or the master.

• Get software version: Vendor Id, Major version, Minor version, Patch Id.
• Read protection level: Read the protection level of flash memory.
• Jump to address: Jump to specific address if it's application address or any one other to implement this function
• Erase flash: To erase specific sectors in flash memory
• Memory write: To write on specific pages in flash memory.
• Enable/Disable write protection level: protect flash memory from writing on it or disabled.
• Enable/Disable read protection level: protect flash memory from reading on it or disabled.