Scribd Logo
Upload

Welcome to Scribd!

  • Best Practices Firmware

    Uploaded by

    Jhoan Esteban León
    4 views1 page
    The document provides best practices for firmware architecture and code organization. It recommends having a header file for each source file with function definitions and macros, following UpperCamelCase naming for files, and using the unit testing library UNITY. The main.c file initializes peripherals and runs the app loop. Code should follow a folder structure with folders for tasks, middleware, and drivers. Testing should be done in separate test files using a unit testing approach.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document provides best practices for firmware architecture and code organization. It recommends having a header file for each source file with function definitions and macros, following UpperCamelCase naming for files, and using the unit testing library UNITY. The main.c file initializes peripherals and runs the app loop. Code should follow a folder structure with folders for tasks, middleware, and drivers. Testing should be done in separate test files using a unit testing approach.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    4 views1 page

    Best Practices Firmware

    Uploaded by

    Jhoan Esteban León
    The document provides best practices for firmware architecture and code organization. It recommends having a header file for each source file with function definitions and macros, following UpperCamelCase naming for files, and using the unit testing library UNITY. The main.c file initializes peripherals and runs the app loop. Code should follow a folder structure with folders for tasks, middleware, and drivers. Testing should be done in separate test files using a unit testing approach.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 1

    Basado en el documento original ARQUITECTURA DEL FIRMWARE desarrollado por los antiguos

    ingenieros de TECREA SAS

    Elaborado por Jhoan Esteban Leon – jhoan.leon@colcircuitos.com

    Best practices:

    - Always a source file (Xxxx.c) should have a header file (Xxxx.h) with all global macros,
    variables and function definitions and a test file (TestXxxx.c) to do the testing (unit
    testing) of all funcions in the source code.
    - Follow the UpperCamelCase standard for file naming.
    - Follow the unit testing approach with the library UNITY for Embedded C,
    http://www.throwtheswitch.org/unity see the introduction and fully documentation
    and source files in the github repository: https://github.com/ThrowTheSwitch/Unity

    El main.c es solo para inicializar los periféricos y el estado inicial del micro y para correr la app
    en el loop.

    Seguir la estructura de carpetas:

    Task/APP

    Middleware/API

    Drivers/BSP

    You might also like