Stm32g0 USB DFU upgrade verification error -2

One 、 The problem I have

1.1 summary

Need to use stm32g0 Series MCU realizes firmware upgrade function , The upgrade scheme selected is STM32 USB DFU programme . Because we need to do product and firmware matching , There are other features , So I didn't choose the built-in boot, It's about writing boot, To implement inside usb dfu function .pc Client side usage st Official DfuSeDemo .

1.2 Problems encountered

According to the online process , Take advantage of the official cubemx Produced boot engineering , Configured with flash Read and write api,boot It's done. . During the test, I found that , When upgrading firmware on some computers , Random verification errors . Tips ： matching not good . first difference at address ... . Some computers appear very frequently , Some computers , The probability of occurrence is very low .

Two 、 Hardware connection

2.1 D+ D- Connect

2.2 pin Power supply

USB USB-PD, USB-MD Connected IO Need to pass through VDDIO2 Power supply ,VDDIO2 Need to provide a 1.6 ->3.6v The voltage of

2.3 VDDUSB IO

stay AN2606 In the document , mention VDDUSB IO Must receive 3.3v, But I couldn't find it VDDUSB IO.

3、 ... and 、 Use factory boot verification

boot The project is generated and slightly modified according to official tools , The circuit connection is also relatively simple , But still random error, verification error , Can it be the single chip computer usb There is a problem with its performance ？ To test this mcu Of usb performance , I decided to use the official usb dfu boot verification .
Here's the choice pc The upper computer is the latest version of the official website STM32CubeProgrammer , If it all goes wrong , The estimated probability is mcu Its own problem .

3.1 mcu How to access the built-in usb dfu boot ？

file AN2606 mention The STM32G0B1xx/0C1xx bootloader is activated by applying Pattern 11 , STM32G0B1 Series MCU , Use Pattern 11 Enter built-in Boot Pattern .Pattern 11 The definition is as follows ：

As shown in the figure above ,Pattern11 There are also several ways , You can choose , I chose the second way ： Through the first STM32CubeProgrammer take mcu Medium nBoot1(bit) Set to 1,nBOOT0_SEL(bit) Set to 0 , And then mcu Of Boot0（pin） Pick up 3.3v. Power on and restart , Access usb Line , Get into boot Pattern ;

3.2 Upgrade verification

With STM32CubeProgrammer For the upper computer , In different pc The upgrade verifies , There is no verification error .

3.3 Summary of this round

built-in boot The upgrade is normal , explain mcu Of itself usb The circuit is ok . Still need to find their own reasons . The reasons may be the following two ：

• Built by myself boot There is a problem .
• Selected upgrade client DfuSeDemo There is a problem .

Four 、 episode , Client not recognized

4.1 Problems encountered

The installation uses STM32CubeProgrammer after , Reuse DfuSeDemo , Find out DfuSeDemo Unable to identify the device （ STM Device in DFU Mode ） .

4.2 Problem finding

Turn on my computer -> Device manager , Found under the universal serial bus device ： STM32 Download Firmware Update This device .

4.3 solve

Right click on the STM32 Download Firmware Update , Select uninstall device , And delete the device driver .

take usb Line unplugging device , Then insert the device ,DfuSeDemo Re identify the device .

5、 ... and 、 Problem solving

Checked boot Code of each module of the project , Nothing unusual . Found behind STM32G0 The latest driver library is V1.5.1 , And I use V1.5.0 . Updated the latest driver library , Problem solved . Compared the two versions of code , Found in stm32g0xx_ll_usb.c This document has made a lot of changes , This happens to be usb Drive function library . No time for the moment , Knowledge reserve is not enough , Have the opportunity to analyze the differences in this file in detail .