working_on

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
working_on [2021/01/25 15:49] adminworking_on [2021/05/21 15:12] (current) admin
Line 11: Line 11:
   * Renesas ZMOD4410   * Renesas ZMOD4410
   * http://www.ica.miteco.es/   * http://www.ica.miteco.es/
 +  * see [[sensors]]
 +  * see [[air monitoring system components]]
  
 **PR19_03_Yocto**    //Yocto environment for STM32P1 board.// **PR19_03_Yocto**    //Yocto environment for STM32P1 board.//
   * TODO: real-time   * TODO: real-time
 +  * TODO: https://onlinelibrary.wiley.com/doi/full/10.1002/eng2.12114
  
-<color /#00ff00>**PR20_01_STM32**</color>    //STM32 development environment with libopencm3.//+**PR20_01_STM32**    //STM32 development environment with libopencm3.//
   * TODO: Consolidate makefiles (use XMC4800 makefile, http://reecestevens.me/blog/2016/07/08/embedded-programming-without-ide/). Add also improvements from https://tty.uchuujin.de/2016/02/stm32-from-scratch-makefile/.   * TODO: Consolidate makefiles (use XMC4800 makefile, http://reecestevens.me/blog/2016/07/08/embedded-programming-without-ide/). Add also improvements from https://tty.uchuujin.de/2016/02/stm32-from-scratch-makefile/.
   * TODO: Measure improvements by using SRAM for code, as well as using ITCM memory (https://rhye.org/post/stm32-with-opencm3-4-memory-sections/).   * TODO: Measure improvements by using SRAM for code, as well as using ITCM memory (https://rhye.org/post/stm32-with-opencm3-4-memory-sections/).
 +  * TODO: STM32MP1 environment, follow https://bootlin.com/blog/building-a-linux-system-for-the-stm32mp1-basic-system/
  
 <color /#00ff00>**PR20_02_RTEMS**</color>    //Develop a simple application on an ARM platform (SPI sensor throughput, CPU load, GPIO interrupt latency, interrupt latency with user thread processing, PPS jitter).// <color /#00ff00>**PR20_02_RTEMS**</color>    //Develop a simple application on an ARM platform (SPI sensor throughput, CPU load, GPIO interrupt latency, interrupt latency with user thread processing, PPS jitter).//
-  * TODO: Run RTEMS examples in Nucleo hardware +  * [[MCU execution time]] 
-  * TODO: Run RTEMS tests in Nucleo hardware +  * [[pulse measurement]] 
-  * TODO: GPIO toggling, sigrok-cli OS softwareDSLogic Saleae logic  +  * <del>TODO: Run RTEMS examples in Nucleo hardware</del> 
-    GPIO toglingNo RTOS functionality involvedHow does it compare to e.gbare-metal with libopencm3? +  * <del>TODO: Run RTEMS tests in Nucleo hardware</del> 
-    * Ping-pong between 2 tasks (e.g. using mutex). These are the only 2 tasks running in the system+  * [[RTEMS BSP for TMS570LC4357]] 
-    * Ping-pong between 2 tasks through a GPIO loopback+  * Run Nucleo examples from SRAM 
-    * Periodic timer, with system at 50% load, check jitter.+  - GPIO toggling on bare-metal. Compare performance of different boardsflash/RAM/ITCM, etc. 
 +  Interrupt latency (GPIO input/output) on bare-metal. Compare performance of different boardsflash/RAM/ITCM, etc. 
 +  GPIO toggling on RTEMS using a single uninterrupted taskCompare performance of different boardsUseful to make sure the systems and toolchains are working as expectedRunning from flash/RAM/ITCM
 +  RTEMS interrupt latency and jitter at different CPU loads (GPIO input/output)Compare performance of different boards. 
 +  - RTEMS scheduling latency and jitter using mutex at different CPU loads (measured using two GPIO outputs). Compare performance of different boards
 +  RTEMS periodic timer jitter at different CPU loads (measured using one GPIO output). Compare performance of different boards
 +  - RTEMS contribution: CPU load 
 +  - RTEMS contribution: task priority assignment with ML 
 + 
  
 **PRXX_XX_Micropython** **PRXX_XX_Micropython**
  • working_on.1611589795.txt.gz
  • Last modified: 5 years ago
  • by admin