firmware
IEM Firmware Documentation
Loading...
Searching...
No Matches
rtos.c File Reference

Application initialization and entry point. More...

#include "rtos.h"
#include "main.h"
#include "can.h"
#include "state.h"
#include "tractive.h"
#include "vnav.h"
Include dependency graph for rtos.c:

Functions

void application_init ()
 Application initialization.
void application_start ()
 Application entry point.
void HAL_GPIO_EXTI_Callback (uint16_t gpio_pin)
 STM32 HAL external interrupt callback override.

Variables

Global_Handles_t hdls_g

Detailed Description

Application initialization and entry point.

Author
Jamie Pruett :)
Version
0.1
Date
2024-11-01

Function Documentation

◆ application_init()

void application_init ( )

Application initialization.

Keeps code that we write and edit isolated from CubeMX in main.c

Here is the call graph for this function:
Here is the caller graph for this function:

◆ application_start()

void application_start ( )

Application entry point.

Keeps code that we write and edit isolated from CubeMX in main.c

Here is the call graph for this function:
Here is the caller graph for this function:

◆ HAL_GPIO_EXTI_Callback()

void HAL_GPIO_EXTI_Callback ( uint16_t gpio_pin)

STM32 HAL external interrupt callback override.

HAL register callbacks is weird for EXTI - there is a function to do it, but CubeMX doesn't generate an EXTI_HandleTypeDef struct for the external interrupt line and doesn't use one in the interrupt handler. Overriding the weak HAL callback here and adding new pins as needed is the most straightforward implementation I can think of. May go with a more elegant solution later

Parameters
gpio_pinGPIO pin the external interrupt was generated on
Here is the call graph for this function:

Variable Documentation

◆ hdls_g