TinyUSB on STM32F446 not working.

[HattonLe]

I just got hold of an STM32F446 board and am trying to get TinyUSB up and running as a HS device on it.
(I was running a STM32F103 but ran out of horse power, so upgraded to an STM32G431 but then ran out of flash... hence moving to F446 which has a substantially different USB interface).

a) Am I correct in thinking TinyUSB works for STM32F446? (its marked on the home page as working for STM32F4 - but does this include F446?

So far STM32F446 USB is not working, so have been stepping thru the TinyUSB init code to figure out what I am missing or have configured wrong - but I have found several disparities between the STM32F446 reference manual USB registers and the TinyUSB dwc2 code.

b) "dwc2_common.c" check_dwc2() uses registers gsnpsid, ghwcfg1..3 (offsets 040 .. 04C), but they are not listed in the STM32 manual (section 31.15.15, page 1127 of RM0390 Reference Manual, STM32F446xx).

c) "dcd_dwc2.c" dma_device_enabled() uses register ghwcfg2 (offset 48) to determine if DMA is enabled, but for the STM32F446 according to the manual the DMA flag is in the AHB configuration register gahbcfg (offset 08).

If someone can confirm TinyUSB will work for the STM32F446, or if its partially working at least it gives me an idea as to how to go forward (either figuring out an incorrect configuration for s/w or h/w, or implementing whats missing \ getting it to run full stop.

Thanks.

[HiFiPhile]

Do you use STM32F446 with an external phy, otherwise it only has FS.

Normally STM32F446 should work based on comments.

b) "dwc2_common.c" check_dwc2() uses registers gsnpsid, ghwcfg1..3 (offsets 040 .. 04C), but they are not listed in the STM32 manual (section 31.15.15, page 1127 of RM0390 Reference Manual, STM32F446xx).
c) "dcd_dwc2.c" dma_device_enabled() uses register ghwcfg2 (offset 48) to determine if DMA is enabled, but for the STM32F446 according to the manual the DMA flag is in the AHB configuration register gahbcfg (offset 08).

It's normal, ST only document a subset of registers, the full DWC2 core databook is under NDA.

You can try to use CubeMX to generate a USB enabled project and copy the clock/gpio settings.

[HattonLe]

Hi,
NDAs - the bane of OSS. Thanks for that info.

No external PHY. According to the STM32F446 manual, page 1065 -->
"OTG_HS supports the following PHY interfaces: An on-chip full-speed PHY... A ULPI interface for external high-speed PHY"

DOH ..... I misread that as 'yes it can' do HS onchip... but I see it says "on-chip full-speed", not "on-chip high-speed"!

Dang I'll have to add one into my PCB design (nice to find that one out before I had the PCB made).

I also fixed a config error in my code so now dma_device_enabled() is correctly returning true.

My F446 version app was generated from scratch using CubeMX (been down the changing processor rabbit hole before!) and then ported my G431 app across into it (same as I did for moving from F103 -> G431).

Thanks for being a sounding board - I've made progress (1 step forward, 1 step back), but I'm moving again LOL.

[HiFiPhile]

If you are not locked to ST I suggest you to take a look NXP LPC5528 or LPC55S69.

[HattonLe]

Thanks for the alternative NXP suggestion. My learning STM32 side project appears to have morphed into a year long major USB project so I'm sticking with STM32 for now. I found the STM32F723 has a built-in HS PHY - and that chip is a drop in substitute for a STM32H723 (a board for which is available on AliExpress from WeAct), so thats my next step forward on the hardware side.

[HiFiPhile]

Yeah STM32F723 is nice although a little expensive, I often test code on F723E-DISCO. If you need a working disconnection detection (tud_umount_cb callback) don't forget to connect Vbus pin.