mcuboot/sim
Thomas Altenbach 60806bce8e sim: Fix MCUBOOT_SWAP_USING_SCRATCH defined in direct-xip and ram-load
When 'direct-xip' or 'ram-load' features were enabled,
CONFIG_BOOT_SWAP_USING_SCRATCH and MCUBOOT_SWAP_USING_SCRATCH were
defined even though swap using scratch wasn't used. This commit fixes
the issue.

Signed-off-by: Thomas Altenbach <thomas.altenbach@legrand.com>
2024-07-15 20:03:21 -03:00
..
mcuboot-sys sim: Fix MCUBOOT_SWAP_USING_SCRATCH defined in direct-xip and ram-load 2024-07-15 20:03:21 -03:00
simflash sim: Trivial dependency updates 2022-04-12 08:11:57 +02:00
src sim: Put AreaDesc in an Rc 2024-06-26 16:43:56 -06:00
tests sim: Add new ram-load test cases 2023-06-29 13:21:30 +02:00
.gitignore sim: Add simulator code 2017-01-09 12:28:10 -07:00
Cargo.toml sim: PSA Crypto ECDSA enablement 2023-09-12 16:29:11 +02:00
README.rst doc: Fix case in titles 2021-11-03 17:05:40 +01:00

README.rst

MCUboot simulator
#################

This is a small simulator designed to exercise the mcuboot upgrade
code, specifically testing untimely reset scenarios to make sure the
code is robust.

Prerequisites
=============

The simulator is written in Rust_, and you will need to install it to
build it.  The installation_ page describes this process.  The
simulator can be built with the stable release of Rust.

.. _Rust: https://www.rust-lang.org/

.. _installation: https://www.rust-lang.org/en-US/install.html

Dependent code
--------------

The simulator depends on some external modules.  These are stored as
submodules within git.  To fetch these dependencies the first time::

  $ git submodule update --init --recursive

will clone and check out these trees in the appropriate place.

Testing
=======

The tests are written as unit tests in Rust, and can be built and run
automatically::

  $ cargo test

this should download and compile the necessary dependencies, compile
the relevant modules from mcuboot, build the simulator, and run the
tests.

There are several different features you can test. For example,
testing RSA signatures can be done with::

  $ cargo test --features sig-rsa

For a complete list of features, see Cargo.toml.

Debugging
=========

If the simulator indicates a failure, you can turn on additional
logging by setting ``RUST_LOG=warn`` or ``RUST_LOG=error`` in the
environment::

  $ RUST_LOG=warn ./target/release/bootsim run ...

It is also possible to run specific tests, for example::

  $ cargo test -- basic_revert

which will run only the `basic_revert` test.