aboutsummaryrefslogtreecommitdiffstats
path: root/3rdparty/qtimgui/demo-window/demo-window.cpp
diff options
context:
space:
mode:
authorDavid Shah <dave@ds0.me>2019-10-24 10:43:18 +0100
committerDavid Shah <dave@ds0.me>2019-10-24 10:43:18 +0100
commit8343488bdf6ef21844913bd1043e27541b0573c1 (patch)
treee5e864f32d898a2619709b0b5d654139d65358bd /3rdparty/qtimgui/demo-window/demo-window.cpp
parent4775930e4943fef042b8a4c7e339fefeb1f251be (diff)
downloadnextpnr-8343488bdf6ef21844913bd1043e27541b0573c1.tar.gz
nextpnr-8343488bdf6ef21844913bd1043e27541b0573c1.tar.bz2
nextpnr-8343488bdf6ef21844913bd1043e27541b0573c1.zip
sdf: Improve SDF output
Signed-off-by: David Shah <dave@ds0.me>
Diffstat (limited to '3rdparty/qtimgui/demo-window/demo-window.cpp')
0 files changed, 0 insertions, 0 deletions
generated by cgit v1.2.3 (git 2.25.1) at 2025-09-06 19:02:22 +0000
ref='#n132'>132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 
# Ubertest
## Intro / Features

Ubertest is a blackbox regression test for flashrom. It requires two flashrom binaries, one of which is assumed to be an older or stable version and the other which is the new version being tested.

Tests can be run on the local host or on a remote machine (via SSH). Additionally, the ubertest script supports using a secondary programmer to check the result of the primary programmer.

Ubertest supports multiple modes of operation which allow regions to be flashed selectively based on presence of a layout file or integrated layout mapping:
- Clobber mode: The entire ROM can be used for testing.
- Layout mode: Target a region using a flashrom layout file.
- Descriptor mode: Target a region using an Intel flash descriptor (Intel systems)
- Flashmap mode: Target a region using a flashmap

The tests assume that we care about 4KiB and 64KiB sector/block sizes. Some large ROMs available today only support 64KiB block erase operations, however testing on large regions can be impractical for many devices. The `--small-region` option may be used to restrict tests to using a smaller amount of flash memory (currently 16KiB).

### Terminology

- DUT: Device under test
- Local host: The machine which is running the script. It might also be the DUT.
- Remote machine: DUT controlled via SSH with primary programmer.
Programmers
	- Primary programmer: The programmer which will be tested using the new version of flashrom.
	- Secondary programmer: An optional programmer which will be used along with the old version of flashrom to verify the result of the primary programmer. This is generally assumed to be an external programmer connected to the local host e.g. via USB or serial. It may also be a secondary internal interface, for example if the DUT has a SPI ROM and both linux_spi and linux_mtd support and the developer wishes to test one against the other.

## Basic Usage

For a full list of options use `-h/--help`.

### Mandatory Options

`-n/--new <path>`: New (unstable) flashrom binary to test. Also see Note 1 below.

`-t/--type <type>`: Type of test to run:
- Single test: A single test of the specified mode will be run. If this type is selected, then a mode must also be specified.
- Endurance test: The ROM will be erased/written with random content until the first failure.

`-p/--primary-programmer`: Primary programmer options, e.g. “internal”, “ch341a_spi”, etc.

**Note 1**: When a remote host is used these options refer to files that are on the remote host, not the local host. See Testing on a Remote Host/DUT below.