Hello @Jocelyn RICARD ,
Thank you very much for your response.
I have two st-link headers available on my board (I only plug the st-link into one of the headers):
Here is where the JTRST line connects to the processor:
Are you saying that nRST also needs to be connected to the ST-LINK SYS_JTRST?
I noticed now I can communicate with the processor consistently but I am having difficulty performing an erase during provisioning (note that this 'open' provisioning worked consistently before I 'closed' then reopened the device):
AppliCfg with python script
=====
===== Provisioning of OEMiROT boot path
===== Application selected through env.sh: Applications/ROT/OEMiROT_Appli
===== Product state must be Open. Execute /ROT_Provisioning/DA/regression.sh if not the case.
===== DTCM/ITCM_AXI_SHARE is going to be forced to 0 for the provisioning steps
===== (if needed uncomment DTCM/ITCM_AXI_SHARE lines with the wished value in the ob_flash_programming script).
=====
Step 0: Preliminary stage
* Define product state value (* default choice)
Default product state is going to be applied
TEST >>OPEN <<
Step 1: Configuration management
* OEMiROT_Config.obk generation:
From TrustedPackageCreator ^(OBkey tab in Security panel^).
Select OEMiROT_Config.xml^(Default path is /ROT_Provisioning/OEMiROT/Config/OEMiROT_Config.xml^)
Warning: Default keys must NOT be used in a product. Make sure to regenerate your own keys!
Run Keygen script to randomly regenerate your own keys (Keys/*.pem)
Update the configuration (if/as needed) then generate OEMiROT_Config.obk file
Press any key to continue...
* Configure OEMiROT_Config.xml for OPEN
* Force the update of OEMiROT_Config.obk
Step 2: Image generations
* Configure OEMIROT_Boot project as OEMIROT...
* Boot firmware image generation
Open the OEMiROT_Boot project with preferred toolchain and rebuild all files.
At this step the project is configured for OEMiROT boot path.
Press any key to continue...
* Configure the Firmware binary input file in OEMiROT_Code_Image.xml...
* Configure the Image output file in OEMiROT_Code_Image.xml...
* Code firmware image generation:
Open the OEMiROT_Appli project with your preferred toolchain
Rebuild all files. The appli_enc_sign.hex file is generated with the postbuild command
Press any key to continue...
Step 3: Provisioning
* Force DTCM/ITCM_AXI_SHARE to 0...
Successful
* Provision the .obk files...
Successful obk provisioning
(see obkey_provisioning.log for details)
* Programming the option bytes and flashing the image...
Error when trying to "Write OEMiROT_Appli Code"
Programming aborted
=====
===== Error while executing "Write OEMiROT_Appli Code".
===== See ob_flash_programming.log for details. Then try again.
=====
[❌] Provisioning command failed: Encountered a bad command exit code!
Here is the ob_flash_programming.log contents:
OPTION BYTE PROGRAMMING VERIFICATION:
Option Bytes successfully programmed
Time elapsed during option Bytes configuration: 00:00:02.602
Application image programming in download slots
Write OEMiROT_Appli Code
-------------------------------------------------------------------
STM32CubeProgrammer v2.19.0
-------------------------------------------------------------------
ST-LINK SN : 0030001F3137510239383538
ST-LINK FW : V3J17M10B6S1
Board : STLINK-V3SET
Voltage : 3.23V
SWD freq : 8000 KHz
Connect mode: Normal
Reset mode : Software reset
Device ID : 0x485
Revision ID : Rev Y
Device name : STM32H7RSxx
Flash size : 64 KBytes (default)
Device type : MCU
Device CPU : Cortex-M7
BL Version : 0xE3
Opening and parsing file: zephyr_enc_sign.hex
Memory Programming ...
File : zephyr_enc_sign.hex
Size : 382.15 KB
Address : 0x90200000
Erasing memory corresponding to sector 0:
Erasing external memory sectors [32 37]
Error: failed to erase memory
Error: failed to erase memory
Additionally, even with the device back in 'Open' I am not able to perform an erase in Cube Programmer. I always get the error: "Mass erase operation failed.Please verify flash protection." Do you know how I can perform a mass erase? In Cube I have the following external loader set:
None of the WRP option bytes that are visible in Cube Programmer are set:
Thanks again!
