cancel
Showing results for 
Search instead for 
Did you mean: 

STM32H743 Custom External Loader fails with v2.18 and up

YuraM
Associate

Hello,

I had generated an External QSPI loader for W25Q128JV and STM32H743 some 2 years ago.


I originally used it with STlink Utility Programmer and then switched to STM32CubeProgrammer.  All good and working as expected with CubeProgrammer v2.17.

I stopped updating the CubeProgrammer as every version after that including the latest v2.20 no longer functional with my custom .stldr file refusing to mass erase the device.

 

Does anyone know what changed in CubeProgrammer support for External Loaders starting with v2.18 ?

Thank you,

Yuri

1 REPLY 1

https://community.st.com/t5/stm32cubeprogrammer-mcus/cubeprogrammer-not-connecting-qspi/td-p/823984

I'm not sure anything specific changed, but will ask @STTwo-32 to check on changes and primary contact details.

I know the newer versions stopped working on Win7, which was unhelpful as older equipment is often retired into test and production donkey work.

Watch out for them using Memory Mapped mode for NOR_FLASH, and make sure your Init, Write and Erase functions clear/abort out of that seamlessly

Watch also for Winbond changing ID from EF40 to EF70 for some of the newer parts. I try to check for Winbond parts so I don't used magic sequences and Status Register settings that will break other manufacturers parts.

https://github.com/cturvey/stm32extldr/tree/main/h7_w25q128

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..