2020-01-17 01:01 AM
2020-01-17 01:09 AM
Hi @Evan .1
Did you go through this one ?
https://wiki.st.com/stm32mpu/wiki/STM32MP15_secure_boot
Hope it help
Olivier
2020-01-17 02:16 AM
Thanks. Do I understand correctly that sercure boot is only a image authorisation method. The image itself is not encrypted. So reverse engineering the code can be done on an other device. Or replace the processor and copy the image to that device without the header.
I like some more detail.
Also can I disable jtag/debug port.
Thanks
2020-01-17 06:35 AM
Hi,
you understanding is correct.
As all the code is stored on external memories which are seen as non secure devices, the code can be hacked.
The authentication process at least ensures that modified code is not executed.
From this reason disabling the debug port doesn't help - the processor doesn't need to be involved.
BR,
Milan
2020-01-19 11:14 PM
Thanks for the reply.
I want to know if I i can I prevent cloning and reverse engineering.
I don 't see secure boot on his own very useful. So probably I'm missing the big picture.
Thanks for the information.
EVS
2020-01-20 08:11 AM
see also https://wiki.st.com/stm32mpu/wiki/Boot_chains_overview#STM32MP_boot_sequence
and https://wiki.st.com/stm32mpu/wiki/OP-TEE_overview