![]() ![]() It is quite possible that 'clone' chips can be made to look like a f4xx, e.g. if this don't work, then maybe it isn't a stm32f4xx after all. it should flash with the STM32cube programmer and dfu-util etc. That is the correct way to get into the *real* USB DFU mode, the on-chip USB DFU mode that is. There is a traditional finger dance for stm32f4xx pill boards. WeAct messed up by having their 3-sec-KEY-press triggered flash-bootloader activate USB-DFU for way too short a time before resetting again,ĭoes that sum up the situation correctly ? ST messed up clock detecting in their ROM bootloader, and What a pity, because once I have an ST-Link I'd probably use it for uploading AND debugging. But for that initial "correction" of the WeAct bootload ST-Link appears to be necessary. That done I probably could Program using USB-DFU later one. So I think I have to get me a ST-Link device anyhow, and if only to program a better, custom bootloader. My problem is that the WeAct Bootloader (activated by holding down "key" for > 3 seconds) does indeed switch USB to correct VID/PID (the ones STM32CubeProgramme expects) but only for 5 seconds! I've found a message from ST where they admit the ROM bootloader to somehow try to detect the HSE frequency caused by the external crystal using the internal RC Oscillator which is likely to fail with increasing ext. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |