summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/108/other/1772
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/zero-shot/108/other/1772')
-rw-r--r--results/classifier/zero-shot/108/other/177227
1 files changed, 27 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/108/other/1772 b/results/classifier/zero-shot/108/other/1772
new file mode 100644
index 000000000..e6136f705
--- /dev/null
+++ b/results/classifier/zero-shot/108/other/1772
@@ -0,0 +1,27 @@
+device: 0.891
+performance: 0.837
+graphic: 0.765
+files: 0.736
+permissions: 0.725
+vnc: 0.704
+socket: 0.652
+semantic: 0.640
+network: 0.638
+PID: 0.633
+debug: 0.585
+other: 0.522
+boot: 0.393
+KVM: 0.139
+
+MPS2 AN521 has the wrong number of MPU region defined
+Description of problem:
+The AN521 is integrating SSE-200 on the MPS2+ FPGA prototyping board.
+The current implementation in qemu behaves as though there are 16MPU regions when it really only has 8, as describes as `MPU_NS` and `MPU_S` core configuration parameters in the SSE-200's [Techincal Reference Manual](https://developer.arm.com/documentation/101104/0200/functional-description/cpu-elements/cortex-m33-configurations?lang=en).
+Steps to reproduce:
+1. Prepare your Zephyr dev environment
+2. fix `boards/arm/mps2_an521/mps2_an521.dts` to set `arm,num-mpu-regions`  to the appropriate value of 8.
+3. build a Zephyr test such as `west build -p -b mps2_an521 -T tests/kernel/interrupt/arch.interrupt` 
+4. run `qemu-system-arm -machine mps2-an521 -chardev stdio,id=con,mux=on -serial chardev:con -kernel ./build/zephyr/zephyr.elf`
+Additional information:
+With matching MPU region number in QEMU and Zephyr's DTS, the application shows the test suite's progress & outcome.
+If there's a mismatch, the application will enter a fault and not display the expected traces.