Thread: [libopenstm32-devel] STM32F Connectivity line, USB Bootloader and HSE crystal Frequency
Status: Inactive
Brought to you by:
uh1763
Menu
▾
▴
libopenstm32-devel
|
From: Uwe B. <bo...@el...> - 2011-07-11 18:41:28
|
Hello, on my STM32F107 board, the USB bootloader enumerates much faster with a 25 MHz crystal then with a 8 MHz crystal. With the 8 MHz crystal, there are several unseuccessfull attempts like: Jul 11 20:27:34 hertz kernel: [35078.633123] hub 1-1:1.0: unable to enumerate USB device on port 1 Jul 11 20:27:34 hertz kernel: [35079.024836] usb 1-1.1: new full speed USB device using ehci_hcd and address 20 Jul 11 20:27:34 hertz kernel: [35079.096942] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:34 hertz kernel: [35079.272932] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:34 hertz kernel: [35079.448542] usb 1-1.1: new full speed USB device using ehci_hcd and address 21 Jul 11 20:27:35 hertz kernel: [35079.520403] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:35 hertz kernel: [35079.696887] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:35 hertz kernel: [35079.872366] usb 1-1.1: new full speed USB device using ehci_hcd and address 22 Jul 11 20:27:35 hertz kernel: [35080.280050] usb 1-1.1: device not accepting address 22, error -32 Jul 11 20:27:35 hertz kernel: [35080.352571] usb 1-1.1: new full speed USB device using ehci_hcd and address 23 Jul 11 20:27:36 hertz kernel: [35080.760031] usb 1-1.1: device not accepting address 23, error -32 Jul 11 20:27:36 hertz kernel: [35080.760406] hub 1-1:1.0: unable to enumerate USB device on port 1 Jul 11 20:27:40 hertz kernel: [35084.912351] usb 1-1.1: new full speed USB device using ehci_hcd and address 24 Jul 11 20:27:40 hertz kernel: [35084.984331] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:40 hertz kernel: [35085.160821] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:40 hertz kernel: [35085.336555] usb 1-1.1: new full speed USB device using ehci_hcd and address 25 Jul 11 20:27:40 hertz kernel: [35085.408543] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:41 hertz kernel: [35085.584900] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:41 hertz kernel: [35085.760503] usb 1-1.1: new full speed USB device using ehci_hcd and address 26 Jul 11 20:27:41 hertz kernel: [35086.168037] usb 1-1.1: device not accepting address 26, error -32 Jul 11 20:27:41 hertz kernel: [35086.240459] usb 1-1.1: new full speed USB device using ehci_hcd and address 27 Jul 11 20:27:42 hertz kernel: [35086.648047] usb 1-1.1: device not accepting address 27, error -32 Jul 11 20:27:42 hertz kernel: [35086.648428] hub 1-1:1.0: unable to enumerate USB device on port 1 Jul 11 20:27:44 hertz kernel: [35089.264398] usb 1-1.1: new full speed USB device using ehci_hcd and address 28 Jul 11 20:27:44 hertz kernel: [35089.336639] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:45 hertz kernel: [35089.512870] usb 1-1.1: device descriptor read/64, error -32 Jul 11 20:27:45 hertz kernel: [35089.688480] usb 1-1.1: new full speed USB device using ehci_hcd and address 29 Jul 11 20:27:45 hertz kernel: [35089.781713] usb 1-1.1: New USB device found, idVendor=0483, idProduct=df11 Jul 11 20:27:45 hertz kernel: [35089.781722] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 11 20:27:45 hertz kernel: [35089.781728] usb 1-1.1: Product: STM32 0x418 DFU Bootloade Jul 11 20:27:45 hertz kernel: [35089.781733] usb 1-1.1: Manufacturer: STMicroelectronics Jul 11 20:27:45 hertz kernel: [35089.781737] usb 1-1.1: SerialNumber: STM32 Is this expected behaviour? Is my 8 MHaz crystal broken? Thanks -- Uwe Bonnes bo...@el... Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- |
|
From: Jan P. <jan...@gm...> - 2011-07-11 20:03:36
|
Hi, I think there is the possibility to select different internal clocks and output them on a pin. That way you can measure the frequency and check if it's ok for USB. > Hello, > > on my STM32F107 board, the USB bootloader enumerates much faster with a 25 > MHz crystal then with a 8 MHz crystal. With the 8 MHz crystal, there are > several unseuccessfull attempts like: > > Jul 11 20:27:34 hertz kernel: [35078.633123] hub 1-1:1.0: unable to enumerate USB device on port 1 > Jul 11 20:27:34 hertz kernel: [35079.024836] usb 1-1.1: new full speed USB device using ehci_hcd and address 20 > Jul 11 20:27:34 hertz kernel: [35079.096942] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:34 hertz kernel: [35079.272932] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:34 hertz kernel: [35079.448542] usb 1-1.1: new full speed USB device using ehci_hcd and address 21 > Jul 11 20:27:35 hertz kernel: [35079.520403] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:35 hertz kernel: [35079.696887] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:35 hertz kernel: [35079.872366] usb 1-1.1: new full speed USB device using ehci_hcd and address 22 > Jul 11 20:27:35 hertz kernel: [35080.280050] usb 1-1.1: device not accepting address 22, error -32 > Jul 11 20:27:35 hertz kernel: [35080.352571] usb 1-1.1: new full speed USB device using ehci_hcd and address 23 > Jul 11 20:27:36 hertz kernel: [35080.760031] usb 1-1.1: device not accepting address 23, error -32 > Jul 11 20:27:36 hertz kernel: [35080.760406] hub 1-1:1.0: unable to enumerate USB device on port 1 > Jul 11 20:27:40 hertz kernel: [35084.912351] usb 1-1.1: new full speed USB device using ehci_hcd and address 24 > Jul 11 20:27:40 hertz kernel: [35084.984331] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:40 hertz kernel: [35085.160821] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:40 hertz kernel: [35085.336555] usb 1-1.1: new full speed USB device using ehci_hcd and address 25 > Jul 11 20:27:40 hertz kernel: [35085.408543] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:41 hertz kernel: [35085.584900] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:41 hertz kernel: [35085.760503] usb 1-1.1: new full speed USB device using ehci_hcd and address 26 > Jul 11 20:27:41 hertz kernel: [35086.168037] usb 1-1.1: device not accepting address 26, error -32 > Jul 11 20:27:41 hertz kernel: [35086.240459] usb 1-1.1: new full speed USB device using ehci_hcd and address 27 > Jul 11 20:27:42 hertz kernel: [35086.648047] usb 1-1.1: device not accepting address 27, error -32 > Jul 11 20:27:42 hertz kernel: [35086.648428] hub 1-1:1.0: unable to enumerate USB device on port 1 > Jul 11 20:27:44 hertz kernel: [35089.264398] usb 1-1.1: new full speed USB device using ehci_hcd and address 28 > Jul 11 20:27:44 hertz kernel: [35089.336639] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:45 hertz kernel: [35089.512870] usb 1-1.1: device descriptor read/64, error -32 > Jul 11 20:27:45 hertz kernel: [35089.688480] usb 1-1.1: new full speed USB device using ehci_hcd and address 29 > Jul 11 20:27:45 hertz kernel: [35089.781713] usb 1-1.1: New USB device found, idVendor=0483, idProduct=df11 > Jul 11 20:27:45 hertz kernel: [35089.781722] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > Jul 11 20:27:45 hertz kernel: [35089.781728] usb 1-1.1: Product: STM32 0x418 DFU Bootloade > Jul 11 20:27:45 hertz kernel: [35089.781733] usb 1-1.1: Manufacturer: STMicroelectronics > Jul 11 20:27:45 hertz kernel: [35089.781737] usb 1-1.1: SerialNumber: STM32 > > Is this expected behaviour? Is my 8 MHaz crystal broken? > > Thanks |
|
From: Gareth M. <ga...@bl...> - 2011-07-12 07:08:11
|
On Tue, Jul 12, 2011 at 6:41 AM, Uwe Bonnes <bo...@el...> wrote: > on my STM32F107 board, the USB bootloader enumerates much faster with a 25 > MHz crystal then with a 8 MHz crystal. With the 8 MHz crystal, there are > several unseuccessfull attempts like: I have two boards both enumerate correctly and reliably with 8MHz crystals. Check your crystal, but I think it's more likely a software problem. If you send me a pcap file (capture with wireshark) I'll have a look at it. Does the device work after enumeration? Regards, Gareth -- Black Sphere Technologies Ltd. Web: www.blacksphere.co.nz Mobile: +64 27 777 2182 Tel: +64 9 478 8885 Skype: gareth.mcmullin LinkedIn: http://nz.linkedin.com/in/gsmcmullin |
|
From: Uwe B. <bo...@el...> - 2011-07-12 08:28:46
|
>>>>> "Gareth" == Gareth McMullin <ga...@bl...> writes:
Gareth> On Tue, Jul 12, 2011 at 6:41 AM, Uwe Bonnes
Gareth> <bo...@el...> wrote:
>> on my STM32F107 board, the USB bootloader enumerates much faster with
>> a 25 MHz crystal then with a 8 MHz crystal. With the 8 MHz crystal,
>> there are several unseuccessfull attempts like:
Gareth> I have two boards both enumerate correctly and reliably with
Gareth> 8MHz crystals. Check your crystal, but I think it's more likely
Gareth> a software problem. If you send me a pcap file (capture with
Gareth> wireshark) I'll have a look at it.
I am not talking about user software. I talk about the system software, when
booting with Boot1==0 and Boot0 ==1, and I have not influence on the
software.
After enumeration, dfu-util did see the device, I did no further test for
now.
Bye
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
|
From: Uwe B. <bo...@el...> - 2011-07-21 12:44:22
|
>>>>> "Uwe" == Uwe Bonnes <bo...@el...> writes:
>>>>> "Gareth" == Gareth McMullin <ga...@bl...> writes:
Gareth> On Tue, Jul 12, 2011 at 6:41 AM, Uwe Bonnes
Gareth> <bo...@el...> wrote:
>>> on my STM32F107 board, the USB bootloader enumerates much faster
>>> with a 25 MHz crystal then with a 8 MHz crystal. With the 8 MHz
>>> crystal, there are several unseuccessfull attempts like:
Gareth> I have two boards both enumerate correctly and reliably with
Gareth> 8MHz crystals. Check your crystal, but I think it's more likely
Gareth> a software problem. If you send me a pcap file (capture with
Gareth> wireshark) I'll have a look at it.
Uwe> I am not talking about user software. I talk about the system
Uwe> software, when booting with Boot1==0 and Boot0 ==1, and I have not
Uwe> influence on the software.
Uwe> After enumeration, dfu-util did see the device, I did no further
Uwe> test for now.
AN3156 clearly describes the effect:
For USB DFU bootloader V2.0, the device first tries the 25 MHz
configuration, then, if it fails, the 14.7456 MHz configuration, and
finally, if it fails, the 8 MHz configuration. If it still fails, this
operation is repeated with a large timeout value (the three configurations
are tested again). If the second trial also fails, a system reset is
generated.
So it should be normal to see two failing enumeration tries before the
succeeding third try when running on a 8 MHz crystal.
--
Uwe Bonnes bo...@el...
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X