My instrumentation toolsuite (now named Fiddle) still lacks an up-to-date README, but now has example targets (uboot/arm + test.c for multiple archs (writes only traced in arm)). Requires radare2 + gdb w/ python2. Run https://t.co/g2fXynKIkQ to install. https://t.co/Ywx8sSQ7Kf
— @bxsays@infosec.exchange (@bxsays) June 22, 2018
A friendly reminder that this is research code (i.e., a brittle pile of crap), so it will probably be a headache both to get it to work and to work with. I plan on quietly and slowly updating the tools and documentation when I can find spare the time to do so.
— @bxsays@infosec.exchange (@bxsays) June 22, 2018
https://github.com/bx/bootloader_instrumentation_suite
This test suite helps you keep track of different versions of
u-boot/build tools, static analysis of that build’s binaries, and
runtime trace results of running that binary on a given hardware
configuration. For each u-boot/build configuration it keeps a database
of information it statically gathered for each boot stage, boot stage
images/ELF files, a prepared SD card image, and test results of
runtime trace analyses. If it detects changes in the u-boot source or
build tools it will create a new set of test result directories with a
new sdcard image and static analysis results.
u-boot/build tools, static analysis of that build’s binaries, and
runtime trace results of running that binary on a given hardware
configuration. For each u-boot/build configuration it keeps a database
of information it statically gathered for each boot stage, boot stage
images/ELF files, a prepared SD card image, and test results of
runtime trace analyses. If it detects changes in the u-boot source or
build tools it will create a new set of test result directories with a
new sdcard image and static analysis results.
Firmware Security 