Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SystemCoreClock and USB clock settings dependency (STM32 series) #1408

Closed
Willem23 opened this issue Nov 3, 2015 · 6 comments
Closed

SystemCoreClock and USB clock settings dependency (STM32 series) #1408

Willem23 opened this issue Nov 3, 2015 · 6 comments

Comments

@Willem23
Copy link
Contributor

Willem23 commented Nov 3, 2015

In case you want to use the USB device (or host) features the core clockspeed has to have certain values otherwise you can not get the correct USB clock of 48 MHz. On the F103 for example you can run at 72 MHz core speed with 8MHz external clocks (PLL: 8x9 = 72, USB: 72/1.5=48), but you can only get a maximum of 48 MHz core speed using the 8 MHz HSI (PLL: (8/2)x12 = 48, USB: 48/1=48).
It would be nice to include #define settings for USB in system_stm32fxxx.c. It would be even better when these selections can be set without importing and modifying the mbed lib source.

See also discussion on issue #1096 regarding timeout for clock auto-select.

@ciarmcom
Copy link
Member

ciarmcom commented Aug 1, 2016

ARM Internal Ref: IOTMORF-231

@jeromecoutant
Copy link
Collaborator

@Willem23 please have a look on #4421
Regards,

@Willem23
Copy link
Contributor Author

Willem23 commented Jun 2, 2017

See comment for #4421

@jeromecoutant
Copy link
Collaborator

Update for NUCLEO_F103RB is in #4740
Clock source and USB configuration are now available in json files.

With default value :

  • HSE (at 72 MHz) is tried first, then HSI (at 64 MHz) in case of failure
  • USB is available with HSE, but not with HSI

@LMESTM
Copy link
Contributor

LMESTM commented Aug 17, 2017

#4740 has been merged - shall we close this issue ?

@0xc0170
Copy link
Contributor

0xc0170 commented Aug 17, 2017

@Willem23 reopen if still valid with new findings please

@0xc0170 0xc0170 closed this as completed Aug 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants