What techniques do you have to develop before hardware is available?

This page summarizes the projects mentioned and recommended in the original post on /r/embedded

Nutrient - The #1 PDF SDK Library
Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.
nutrient.io
featured
CodeRabbit: AI Code Reviews for Developers
Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
coderabbit.ai
featured
  1. tlib

    For simulation I have been using a simulation framework named Renode. It has decent support for quite a few embedded platforms and is easy to extend. Peripheral development is done in C#, but there is support for python and rust in development. The translation library for the cpus is called tlib. It uses an older fork of tcg which is what qemu is built upon. https://renode.io/about/ and https://github.com/antmicro/tlib for reference. You can even run peripherals developed in HDL in verilator and connect them with the target CPU on the same sysbus.

  2. Nutrient

    Nutrient - The #1 PDF SDK Library. Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.

    Nutrient logo
  3. Google Test

    GoogleTest - Google Testing and Mocking Framework

    Everything else was covered: Ceedling+Unity+CMock for Unit Testing in C, CppuTest or GoogleTest or other options for C/C++. FFF is also useful when mocking. If you test and develop your modules correctly, they should when they are in your application. If you are developing using an Event-Driven Framework like QP or QML, then I would not test anything to do with the framework, but the functions that are called in each event. Same thing if you are using an RTOS, test what's inside your threads/tasks.

  4. fff

    A testing micro framework for creating function test doubles (by meekrosoft)

    Everything else was covered: Ceedling+Unity+CMock for Unit Testing in C, CppuTest or GoogleTest or other options for C/C++. FFF is also useful when mocking. If you test and develop your modules correctly, they should when they are in your application. If you are developing using an Event-Driven Framework like QP or QML, then I would not test anything to do with the framework, but the functions that are called in each event. Same thing if you are using an RTOS, test what's inside your threads/tasks.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts

  • Unit testing C++ SDK using Cpputest lib in STM32

    1 project | /r/embedded | 3 Apr 2022
  • commonly used c-unit testing framework in 2022?

    3 projects | /r/cprogramming | 21 Mar 2022
  • industry standard for Test frameworks?

    3 projects | /r/C_Programming | 6 Feb 2022
  • Embedded Cross-Compiled Test Driven Development with CGull

    1 project | /r/embedded | 26 Jul 2021
  • Unit Testing in C

    6 projects | /r/C_Programming | 29 Jun 2021

Did you know that C++ is
the 7th most popular programming language
based on number of references?