From a732c60d2b9b51840cce15c34e18868db0ae305c Mon Sep 17 00:00:00 2001
From: EmanuelFeru <aerdronix@gmail.com>
Date: Sun, 26 May 2019 15:36:29 +0200
Subject: [PATCH] deleted

---
 Inc/ert_main.c | 116 -------------------------------------------------
 1 file changed, 116 deletions(-)
 delete mode 100644 Inc/ert_main.c

diff --git a/Inc/ert_main.c b/Inc/ert_main.c
deleted file mode 100644
index ba38846..0000000
--- a/Inc/ert_main.c
+++ /dev/null
@@ -1,116 +0,0 @@
-/*
- * Academic License - for use in teaching, academic research, and meeting
- * course requirements at degree granting institutions only.  Not for
- * government, commercial, or other organizational use.
- *
- * File: ert_main.c
- *
- * Code generated for Simulink model 'BLDC_controller'.
- *
- * Model version                  : 1.790
- * Simulink Coder version         : 8.13 (R2017b) 24-Jul-2017
- * C/C++ source code generated on : Wed May 22 23:49:19 2019
- *
- * Target selection: ert.tlc
- * Embedded hardware selection: ARM Compatible->ARM Cortex
- * Emulation hardware selection:
- *    Differs from embedded hardware (MATLAB Host)
- * Code generation objectives:
- *    1. Execution efficiency
- *    2. RAM efficiency
- * Validation result: Not run
- */
-
-#include <stddef.h>
-#include <stdio.h>                     /* This ert_main.c example uses printf/fflush */
-#include "BLDC_controller.h"           /* Model's header file */
-#include "rtwtypes.h"
-#include "zero_crossing_types.h"
-
-/*
- * Associating rt_OneStep with a real-time clock or interrupt service routine
- * is what makes the generated code "real-time".  The function rt_OneStep is
- * always associated with the base rate of the model.  Subrates are managed
- * by the base rate from inside the generated code.  Enabling/disabling
- * interrupts and floating point context switches are target specific.  This
- * example code indicates where these should take place relative to executing
- * the generated code step function.  Overrun behavior should be tailored to
- * your application needs.  This example simply sets an error status in the
- * real-time model and returns from rt_OneStep.
- */
-void rt_OneStep(void);
-void rt_OneStep(void)
-{
-  static boolean_T OverrunFlag = false;
-
-  /* Disable interrupts here */
-
-  /* Check for overrun */
-  if (OverrunFlag) {
-    return;
-  }
-
-  OverrunFlag = true;
-
-  /* Save FPU context here (if necessary) */
-  /* Re-enable timer or interrupt here */
-  /* Set model inputs here */
-
-  /* Step the model */
-  BLDC_controller_step();
-
-  /* Get model outputs here */
-
-  /* Indicate task complete */
-  OverrunFlag = false;
-
-  /* Disable interrupts here */
-  /* Restore FPU context here (if necessary) */
-  /* Enable interrupts here */
-}
-
-/*
- * The example "main" function illustrates what is required by your
- * application code to initialize, execute, and terminate the generated code.
- * Attaching rt_OneStep to a real-time clock is target specific.  This example
- * illustrates how you do this relative to initializing the model.
- */
-int_T main(int_T argc, const char *argv[])
-{
-  /* Unused arguments */
-  (void)(argc);
-  (void)(argv);
-
-  /* Initialize model */
-  BLDC_controller_initialize();
-
-  /* Attach rt_OneStep to a timer or interrupt service routine with
-   * period 1.0E-5 seconds (the model's base sample time) here.  The
-   * call syntax for rt_OneStep is
-   *
-   *  rt_OneStep();
-   */
-  printf("Warning: The simulation will run forever. "
-         "Generated ERT main won't simulate model step behavior. "
-         "To change this behavior select the 'MAT-file logging' option.\n");
-  fflush((NULL));
-  while (1) {
-    /*  Perform other application tasks here */
-  }
-
-  /* The option 'Remove error status field in real-time model data structure'
-   * is selected, therefore the following code does not need to execute.
-   */
-#if 0
-
-  /* Disable rt_OneStep() here */
-#endif
-
-  return 0;
-}
-
-/*
- * File trailer for generated code.
- *
- * [EOF]
- */