Hi

We’re having issues programming the external QSPI flash chip of the STM32F769I-EVAL board.

We’ve followed the guide found in the wiki, wiki.segger.com/STM32F769I_EVAL, and tried to load the “STM32CubeDemo_STM32F769I-EVAL_V1.3.0.hex” file found in STM cube via J-Flash but the QSPI code section seems to fail verification 9 out of 10 times. The eval board seems ok and will program fine with st-link (using the external loader option) and the inbuilt programmer.

I’ve attached the xml and jflash file for checking and can confirm that the elf file is in the same directory.

Thanks

Phil

Hi

The J-Flash version is 6.34f

Log files attached, the hex file is too big to upload via the forum, but you can download it via the ST website at,

st.com/en/embedded-software/stm32cubef7.html

The hex file is in the following folder, STM32Cube_FW_F7_V1.12.0\Projects\STM32F769I_EVAL\Demonstration\STemWin\Binary

Hi,

Unfortunately it still seems to be failing the verification, I've attached the log.

When you say erase the whole chip I'm assuming you mean setting the erase -> chip option in the production tab of the project settings?

Many Thanks

Hi,

I've just re-downloaded your new file again, placed it in the folder with the exe. I haven't touched the xml file as the new elf file name hasn't changed from the wiki post one.

Run J-flash as per your last post, and were still seeing a verification error.

As I stated in my first post, It does work occasionally but most of the time it fails. The only way we've been able to get it to program consistently with J-Flash is to erase the whole chip via st-link first.

I've attached 3 logs all with the new elf file, one passing, one failing and one with ST Link erase first

Many Thanks

Phil

Hi Nino,

Thanks for the update, we’re evaluating whether using 3-Byte mode is going to cause us any issues.

Best Regards,
Phil

Hi Nino,

We’ve investigated our options and unfortunately, we cannot work in 3-byte address mode as that would make it very difficult to access the higher (greater than 128Mb) areas of the flash chip using the easier STM32 FMC memory mapped mode.

We have managed to implement a hardware work around for using your flash loader when programming the QSPI chip below 128Mb. It would appear that it does not send a reset instruction as part of the qspi init routine, and so the qspi chip is left in whatever mode was previously running on it.

To work round this we’ve now connected the unused reset pin of the qspi chip to eval board’s reset line which seems to fix the programming of the qspi chip below 128Mb but above that we still have a verify error.

Thanks for your help
Phil