-
Notifications
You must be signed in to change notification settings - Fork 779
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sival,triag] Some SiVal ROM_EXT are broken #21706
Comments
Tag @johngt for visibility |
…ival ROM_EXT This test also seems to be part of issue lowRISC#21706, so this commit marks it as broken in sival ROM_EXT. This should fix the currently failing CI checks on `master`. Signed-off-by: Andreas Kurth <[email protected]>
The following tests also seem to be part of issue lowRISC#21706: - //sw/device/tests:pwrmgr_all_reset_reqs_test - //sw/device/tests:pwrmgr_random_sleep_all_reset_reqs_test Thus this commit marks them as broken in SiVal ROM_EXT. This should contribute to fixing the currently failing CI checks on `master`. Signed-off-by: Andreas Kurth <[email protected]>
The following tests also seem to be part of issue #21706: - //sw/device/tests:pwrmgr_all_reset_reqs_test - //sw/device/tests:pwrmgr_random_sleep_all_reset_reqs_test Thus this commit marks them as broken in SiVal ROM_EXT. This should contribute to fixing the currently failing CI checks on `master`. Signed-off-by: Andreas Kurth <[email protected]>
Also fix minor typos in other pwrmgr top-level test code. Addresses lowRISC#21706 Signed-off-by: Guillermo Maturana <[email protected]>
Also fix minor typos in other pwrmgr top-level test code. Addresses #21706 Signed-off-by: Guillermo Maturana <[email protected]>
Also, the test pwrmgr_all_reset_reqs_test_fpga_cw310_sival_rom_ext is passing for me. |
Can confirm that |
We found that @matute do you know of any OTP configuration that might cause the |
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses #21706. Signed-off-by: Tim Trippel <[email protected]>
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]> (cherry picked from commit 698b5a6)
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]> (cherry picked from commit 698b5a6)
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]> (cherry picked from commit 698b5a6)
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses lowRISC#21706. Signed-off-by: Tim Trippel <[email protected]> (cherry picked from commit 698b5a6)
The `otbn_boot_services_functest` must run in the ROM_EXT slot since it manipulates the keygmr state, which normally is done by the ROM_EXT. This partially addresses #21706. Signed-off-by: Tim Trippel <[email protected]> (cherry picked from commit 698b5a6)
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see #22819 (comment) This is related to #21706 and #22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see #22819 (comment) This is related to #21706 and #22140. Signed-off-by: Pirmin Vogel <[email protected]>
These tests are all working in ROM_EXT on master and earlgrey_es_sival now that we've fixed the underlying keymgr issue. For details, see lowRISC#22819 (comment) This is related to lowRISC#21706 and lowRISC#22140. Signed-off-by: Pirmin Vogel <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in lowRISC#21706. This commit fixes this and addresses lowRISC#21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in lowRISC#21706. This commit fixes this and addresses lowRISC#21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in lowRISC#21706. This commit fixes this and addresses lowRISC#21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in lowRISC#21706. This commit fixes this and addresses lowRISC#21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in lowRISC#21706. This commit fixes this and addresses lowRISC#21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in #21706. This commit fixes this and addresses #21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]>
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in #21706. This commit fixes this and addresses #21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]> (cherry picked from commit aa4031d)
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext test was marked as broken in #21706. This commit fixes this and addresses #21500. The source of the bug is due to the nature of the ROM_EXT that runs through a CDI attestation flow advancing the key manager state to "OwnerRootKey" in the process. This was not accounted for in the test, which assumed an active "CreatorRootKey" state (this works for sim_dv tests but not with ROM_EXT). The solution to this issue lies in rendering the test state-agnostic, meaning it will execute its verifications independently of the current key manager state. This approach thus mimics the keymgr_sideload_{aes,kmac,otbn} tests which follow a similar strategy. Signed-off-by: Andrea Caforio <[email protected]> (cherry picked from commit aa4031d)
Description
The following tests have been found to be broken in
//hw/top_earlgrey:fpga_cw310_sival_rom_ext
execution environment. See #21580 for details. This issue tracks the lists for further triaging.edn_kat_fpga_cw310_sival_rom_ext
-> fixedflash_ctrl_mem_protection_test_fpga_cw310_sival_rom_ext
flash_ctrl_test_fpga_cw310_sival_rom_ext
pmp_smoketest_tor_fpga_cw310_sival_rom_ext
rv_core_ibex_address_translation_test_fpga_cw310_sival_rom_ext
sram_ctrl_execution_test_fpga_cw310_sival_rom_ext
uart_tx_rx_test_fpga_cw310_sival_rom_ext
keymgr_test_fpga_cw310_sival_rom_ext
boot_data_functest_fpga_cw310_sival_rom_ext
irq_asm_functest_fpga_cw310_sival_rom_ext
alert_functest_fpga_cw310_sival_rom_ext
keymgr_functest_fpga_cw310_sival_rom_ext
rnd_functest_fpga_cw310_sival_rom_ext
rstmgr_functest_fpga_cw310_sival_rom_ext
watchdog_functest_fpga_cw310_sival_rom_ext
mod_exp_otbn_functest_hardcoded_fpga_cw310_sival_rom_ext
rsa_verify_functest_fpga_cw310_sival_rom_ext
sigverify_dynamic_functest_hardcoded_fpga_cw310_sival_rom_ext
chip_power_idle_load_fpga_cw310_sival_rom_ext
chip_power_sleep_load_fpga_cw310_sival_rom_ext
csrng_edn_concurrency_test_fpga_cw310_sival_rom_ext
-> fixedcsrng_kat_test_fpga_cw310_sival_rom_ext
-> fixedentropy_src_csrng_test_fpga_cw310_sival_rom_ext
-> fixedentropy_src_edn_reqs_test_fpga_cw310_sival_rom_ext
-> fixedflash_ctrl_clock_freqs_test_fpga_cw310_sival_rom_ext
flash_ctrl_ops_test_fpga_cw310_sival_rom_ext
keymgr_key_derivation_test_fpga_cw310_sival_rom_ext
keymgr_sideload_aes_test_fpga_cw310_sival_rom_ext
keymgr_sideload_kmac_test_fpga_cw310_sival_rom_ext
lc_ctrl_otp_hw_cfg0_test_fpga_cw310_sival_rom_ext
otp_ctrl_smoketest_fpga_cw310_sival_rom_ext
pmp_smoketest_napot_fpga_cw310_sival_rom_ext
sram_ctrl_sleep_sram_ret_contents_scramble_test_fpga_cw310_sival_rom_ext
aes_kwp_sideload_functest_fpga_cw310_sival_rom_ext
aes_sideload_functest_fpga_cw310_sival_rom_ext
ecdh_p256_sideload_functest_fpga_cw310_sival_rom_ext
ecdsa_p256_sideload_functest_fpga_cw310_sival_rom_ext
kdf_kmac_sideload_functest_hardcoded_fpga_cw310_sival_rom_ext
kmac_sideload_functest_hardcoded_fpga_cw310_sival_rom_ext
pwrmgr_random_sleep_all_reset_reqs_test_fpga_cw310_sival_rom_ext
pwrmgr_all_reset_reqs_test_fpga_cw310_sival_rom_ext
There are some common patterns but each test needs to be investigated:
//hw/top_earlgrey:fpga_cw310_sival_rom_ext
and enable the//hw/top_earlgrey:fpga_cw310_sival
exec env instead//hw/top_earlgrey:fpga_rom_with_fake_keys
but the values in the sival ROM_EXT are differentThe corresponding sival issues should be reopened.
The text was updated successfully, but these errors were encountered: