You most likely had a weird chip and firmware combo too. Take it as a
learning experience.
- know your hardware
- make backups of firmware (ideally 2x & crc)
- check if updates are compatible with your device, only flash if you¡¯re
100%sure.
- learn jtag level reflashing for the device.
As for the GD, glad my tip helped point things in the right way.
-John
Op ma 30 jan. 2023 om 20:21 schreef Al Waschka <awaschka@...>
This gave me an idea.
Does the reverse apply? If the manufacturer used STMCube, could I have
successfully loaded an old NanoVNA dfu with DfuSE-Demo which ran with
anomalies but then when I tried to load a different version the computer
would not recognize the device being plugged in when booted with jogwheel
pressed?
On Jan 30, 2023, at 1:31 PM, Ray WW0AW via groups.io <hrpch=
[email protected]> wrote:
? This is great !!! Thank you my friend, for the files with full dump of
GS-400 which is just what I needed.
You're right, I destroyed the bootloader so I cannot use either
NanoVNA-App or QTbut I already verified that I can communicate to the MCU
via STLinkso I'll go ahead and flash it keeping my fingers crossed....I'll
return with good news of success.
On Sunday, January 29, 2023 at 09:54:19 PM CST, DiSlord <
dislordlive@...> wrote:
Read better....
You use STM-Cube, so you destroy bootloader (need use NanoVNA-App or QT
for update in bootload mode)
Upload this in 0x08000000 address as before
4-inch-GD32F303CCT6-20200619 FULL.bin
