2025-03-02 9:17 PM - edited 2025-03-02 9:17 PM
hi,
yesterday before i have updated cube ide to version 1.18.0 , after the update qspi external loader stopped working .
Before the update qspi related stldr creation & external loader everything works fine , after the update everything related qspi debugging completely broken down .
Even the https://github.com/cturvey/stm32extldr also stopped working.
I have suspected v2 stlink driver , v2 st link firm ware & cube mx So, i have removed the the stlink driver and version v1.18.0 software and installed the ide version v1.17.0 but still the problem is same how to bring back( downgrade) old st link driver and compatible v2 st link firmware to v1.17.0.
Now my completely stopped due to this ! . please suggest me .
I don't know how many v2 st link user having similar debugging with qspi memory problem now ?
2025-03-05 2:56 AM - edited 2025-03-05 2:56 AM
hi,
I have downgraded the Stlink firmware by Stlink utility but no improvement .
I have cleaned completely C drive folder and reinstalled the cube ide 1.17.0 and lowest version cube programmer but no improvement , I am sure ST-Link v2 driver has been disturbed .
I
can you confirm me V3 stlink is working with cube ide v1.18.0 + external loader QSPI ?
2025-03-05 3:12 AM
Hi,
what is your st-link V2 ? the "stick" ? or maybe not genuine STM ?
can you try another one ?
+
other cpu , without QSPI: debug : working ok ?
2025-03-05 3:27 AM
hi,
with & without qspi debugging is happening but inside the qspi function it's not going and it's flashing the external data's .
i was try access the external location 0x90000000 read or write via cube programmer but it's giving error .
I am using Original Nucleo On Board V2 Stlink .
I don't have secondary computer .
Additionally i have tested with chinse stm32 v2 dongle ,that also giving same problem .