Possible bug in STM32F429ZIT6 Discovery1 board user manual?

[_LardDork _]

Posted on December 19, 2017 at 09:05

Hi folks,

I've been working on USB peripheral for like two weeks initially I picked up Discovery1 STM32F429x then later switched to Discovery STM32F407x and I'll explain why.

I tried running USB CDC Virtual Com Port on F429 using USB_FS which according to boards user manual is connected to the microUSB (CN6), code I generated using CubeMx and result was I couldn't see Com port when I did ''dmesg'' on the terminal.

Then few days after struggling I flashed USB CDC Virtual Com Port project for USB_HS and Com port showed up in the list but then again when I tried to send a string (pClassData in the descriptor was NULL so transmit function returned fail) it didn't work, but this is not something I'm trying to discuss here.

After this I further investigated about FS and

schematic shows USB_FS is what being also used by ST-Link.

USB_FS Pins: PA11 and PA12

USB_HS Pins: PB14 and PB15

and attached are two snapshots from Board's user manual.

Additional info: If I follow the exact same steps for STM32F407x with USB_FS and STM32F429x with USB_HS and again try to send a string over USB, it works for F407x but not for the F429x. I also did the diff no core differences, so difference must have been when control goes to USB_ISR.

So my question is am I the only one who's faced this issue, and is it an actual bug or am I'm doing something silly somewhere?

Document name: UM1670

Pages: 29 and 30

 

#stm32-f4 #usb-device #stm32f429-discovery #usb-cdc #discovery

[Uwe Bonnes]

Posted on December 19, 2017 at 10:52

Your question and problems are not really clear to me. However two circles in the picture below belong to the STM32F103Cx of the Stlink and have nothing to do with OTG-FS of the STM32F4.

[_LardDork _]

Posted on December 19, 2017 at 13:56

Hi Bonnes,

Thanks for pointing that out, very stupid of me not have noticed that. And problem I'm facing is with STM32F429x Discovery board, microUSB connector CN6 is connected USB_FS not USB_HS as seen from the schematic. But when I flash the USB_CDC example for HS Virtual Com port shows up in devices but when same done for FS is doesn't, which is counter of what is shown in schematic.That brings me to conclusion that HS is connected to microUSB CN6.

~ Brian.

[Uwe Bonnes]

Posted on December 19, 2017 at 17:57

To get USB HS, all STM32 beside STM32F72 need a HS transceiver, as you can see on F46x and F76x discovery. Without the external transceiver, the port can only do FS. So get an example for your board (f42 disco) and not something else.

[waclawek.jan]

Posted on December 19, 2017 at 18:13

I'd say you are right:

i.e. the signals are mis-named in the F429-DISCO manual, they should be OTG_HS_xx instead of OTG_FS_xx. 

Of course, they have to be renamed also on other schematics pages.

Chapter 6.7  USB OTG supported should mention, that OTG_HS is used but with the internal PHY, ie. in FS mode.

ST, when making changes, could you please modify also the pinout table (Tab.6) to the style this table is in the F407-DISCO now? Thanks.

JW

[Imen.D]

Posted on December 22, 2017 at 15:44

Hello All,

Thanks for bringing this to our attention.

Waclawek.Jan

: I have checked and raised all your feedback internally to update the UM16

Best Regards

Imen