2010-05-21 01:45 AM
dfuse at evaboard Keil MCBSTM32C
#bootloader2011-05-17 04:51 AM
Hi,
Hint. have you tried with PD6 and PB5 in 0V ? Question: What do you mean by ''PA10 connected via cable to 3,3v'' ? is it USB cable ? because PA9 is the VBUS pin not PA10. More important: ''Processor date code=961'': date code = YXX where Y= year and XX=week (max is 52) (at least that's what they say in the product datasheet) so 961 is not a valid date code...I think you should check with your provider or may be you didn't correctly read the code. I hope it could help. Cheers.2011-05-17 04:51 AM
Hi,
now we tried PD6 PA10 and PB5 at 0V, nothing happens. Processor data is: STM32F107 VCT6 Z 990MF VC MYS 99 961 ST e4 ARM2011-05-17 04:51 AM
Hi bst-one,
Date-code ''961'' is an early silicon not yet fully qualified in our mass production and is not containing the right boot-loader. Thus, embedded DFU is not working on that early engineering device. I recommend you ask for free-sample in our e-sampling program and rework the LQFP100 device mounted on your board if you have the adequate equipment. Else you can also contact your local distributor . Cheers, STOne-32.2012-08-09 03:26 AM
Hello,
can you verify that the workaround in AN2606 will help to use the DFU-Bootloader? I can try to pull down PA10 PB5 PD6 as described, but I need verification for the series application,. I have several products here, ready to sell, but i have a random problem to enter the bootloader on startup.... Thanks, Tobias