Closed branylagaffe closed 5 months ago
One reason for this problem could be that the MMU is initialized before QEMU start producing any trace, thus Flexus on initialization read the not-yet-configured QEMU(/arm) to configure the MMU. This behaviour will cause Flexus to read registers set to 0, and be unable to configure the MMU.
Fixed by d496cdb2d6151ce0bff59af5ed3078cf0f595a87 LGTM, done !
MMU Bad initialization
Description
The MMU initialization goes wrong, which fall onto a
g_assert_not_reached()
Steps to Reproduce
trace.cfg
./runq images/busybox
Expected Behavior
The initialization should go on and set the MMU before receiving any trace.
Actual Behavior
Assertion ERROR.
Additional Information
gcc-13
Screenshots (if applicable)