Recently I’ve been trying to capture the optimized Kyber from the PQM4 library using HUSKY, and so far I’ve been able to successfully compile to get the .hex file and burn it into the STM32F415 chip.
The problem is that I can’t acquire the traces through HUSKY. My HUSKY is set to default settings, and every time I capture, I get an error with the info: (ChipWhisperer Scope WARNING|File _OpenADCInterface.py:642) Timeout in OpenADC capture(), no trigger seen! Timeout in OpenADC capture(), no trigger seen!
(ChipWhisperer Scope WARNING|File _OpenADCInterface.py:642) Timeout in OpenADC capture(), no trigger seen! Status : 12
I’ve also tried to compile only a certain function, like NTT, but I found that as long as it involves code implemented in assembly, I get the error described above every time I capture.
The HUSKY works fine with pure C code implementation. So I would like to ask if there is any solution for this. does the environment settings of chipwhisperer affect the proper functioning of the M4 optimized code implementation in the PQM4 library?