Hello Vrund,
First, there is a 1.3.1 release of the firmware already available.
Only change compared to 1.3.0 is that mcu boot related exe files used for signature operations are now digitally signed by ST avoiding issues with automatic removal.
Answers to your questions:
1) For single slot do i required SBSFU_Loader project?
A: Yes, you need a loader outside your application in this case.
2) I only want to upload non secure image(my user application) do i need to run SBSFU\SBSFU_Appli\Secure project?
A: Yes, the secure boot is checking authenticity of both secure and non secure images, and then jumps to secure.
The secure image is important to setup the security configuration of your platform.
3) Postbuild.bat process remains same as x cube sbsfu right?
A: No, in TFM we use a different implementation of SBSFU that is based on open source mcu boot.
So, scripts are different.
4) project example is with L552ZE , i have to use STM32L562 what configuration or settings i need to change in cubeIDE?
A: You need to adapt the target if you want to use HW accelerated crypto. Also, you will need to adapt the interfaces used by SBSFU: UART, LED and button.
But you can copy this from the TFM implementation on the STM32L562
5) Example project already using mbedTLS library right?
A: Yes, we don't use the ST S-CUBE-CRYPTOLIB here.
6) getting-started-with-stm32cubel5-tfm-application-stmicroelectronics.pdf
is not useful as i required SBSFU on stm32l562 and not TFM right?
A: You can have a look to the AN5447 that shows the differences between the 2.
Basically, TFM uses the same secure boot (based on mcuboot).
You can also have a look to the presentation made in the security MOOC part 6.
Best regards
Jocelyn
