Hi, I'm currently working on a STM32H747-DISCO board with the graphic library TouchGFX wich is using the Quad-SPI extern NOR flash.
I'm using a Jlink Base Prob V10.1.
I have no problem flashing and debuging the M7 embedded on the board with an empty project.
But with the TouchGFX library, i need the flash Quad-SPI used to store texts, images etc.
When i tried to flash it the first time, it seems that the Jlink was unable to read the the memory for the Quad-SPI, the adress it tried to reach was out of bound.
A sample of the Console's lines :
.
.
.
Read 2 bytes @ address 0x0802506C (Data = 0xB508)
Read 4 bytes @ address 0x08001730 (Data = 0x68FA1AD3)
Reading 64 bytes @ address 0x24080040
WARNING: Failed to read memory @ address 0x24080040 // The max adress readable should be 0x2407D000
WARNING: Failed to read memory @ address 0x2408007C
Reading 64 bytes @ address 0x24080040
WARNING: Failed to read memory @ address 0x24080040
WARNING: Failed to read memory @ address 0x2408007
.
.
.
After some research i founded the documentation to add new support for the H747-DISCO : wiki.segger.com/Open_Flashload…ending_an_Existing_Device
In the file JLinkDevice.xml i added a configuration for the board because no one existed :
.
.
. //I used the same parameters for ST product and M7 core, the adress seems to be the same for me. //
<Device>
<ChipInfo Vendor="ST" Name="STM32H747XI" Core="JLINK_CORE_CORTEX_M7"/>
<FlashBankInfo Name="QSPI Flash" BaseAddr="0x90000000" MaxSize="0x08000000" Loader="Devices/ST/STM32H7/ST_STM32H745I_Disco_QSPI.elf" LoaderType="FLASH_ALGO_TYPE_OPEN" />
</Device>
.
.
.
Second flash, now it seems to work fine, the adress are read by JLINK but to complete the debug i need to "reset and relaunch" a second debug session.
When i debug the MCU, it's blocked in the "HardFault_Handler" loop untill i launch this second session.
The only error i found is this one : "ERROR: Failed to erase sectors."
But it doesn't seems to block anything.
My question is simple : Do you have any thoughts of why ?
Here the log of the second debug/relaunch debug session working : Log_Second_debug.txt
Thanks for you time and help !!!
I'm using a Jlink Base Prob V10.1.
I have no problem flashing and debuging the M7 embedded on the board with an empty project.
But with the TouchGFX library, i need the flash Quad-SPI used to store texts, images etc.
When i tried to flash it the first time, it seems that the Jlink was unable to read the the memory for the Quad-SPI, the adress it tried to reach was out of bound.
A sample of the Console's lines :
.
.
.
Read 2 bytes @ address 0x0802506C (Data = 0xB508)
Read 4 bytes @ address 0x08001730 (Data = 0x68FA1AD3)
Reading 64 bytes @ address 0x24080040
WARNING: Failed to read memory @ address 0x24080040 // The max adress readable should be 0x2407D000
WARNING: Failed to read memory @ address 0x2408007C
Reading 64 bytes @ address 0x24080040
WARNING: Failed to read memory @ address 0x24080040
WARNING: Failed to read memory @ address 0x2408007
.
.
.
After some research i founded the documentation to add new support for the H747-DISCO : wiki.segger.com/Open_Flashload…ending_an_Existing_Device
In the file JLinkDevice.xml i added a configuration for the board because no one existed :
.
.
. //I used the same parameters for ST product and M7 core, the adress seems to be the same for me. //
<Device>
<ChipInfo Vendor="ST" Name="STM32H747XI" Core="JLINK_CORE_CORTEX_M7"/>
<FlashBankInfo Name="QSPI Flash" BaseAddr="0x90000000" MaxSize="0x08000000" Loader="Devices/ST/STM32H7/ST_STM32H745I_Disco_QSPI.elf" LoaderType="FLASH_ALGO_TYPE_OPEN" />
</Device>
.
.
.
Second flash, now it seems to work fine, the adress are read by JLINK but to complete the debug i need to "reset and relaunch" a second debug session.
When i debug the MCU, it's blocked in the "HardFault_Handler" loop untill i launch this second session.
The only error i found is this one : "ERROR: Failed to erase sectors."
But it doesn't seems to block anything.
My question is simple : Do you have any thoughts of why ?
Here the log of the second debug/relaunch debug session working : Log_Second_debug.txt
Thanks for you time and help !!!