We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Very strange things occur on release build: when sysclk is greater that pclk1, for example:
sysclk
pclk1
let clocks = rcc.cfgr.sysclk(96.MHz()).pclk1(48.MHz()).freeze();
led does not flashing, but debug build is fine.
I tested this combination:
let clocks = rcc.cfgr.sysclk(16.MHz()).pclk1(16.MHz()).freeze(); let clocks = rcc.cfgr.sysclk(32.MHz()).pclk1(32.MHz()).freeze(); let clocks = rcc.cfgr.sysclk(48.MHz()).pclk1(48.MHz()).freeze();
It's work fine, at both debug and release builds.
But, What occurs when i follow CubeMX suggestion(frequency), I don't understand.
I little modify example from this crate - PA5 for NUCLEO- F767ZI by default not connected from factory - https://github.com/chessnokov/pfm/blob/master/bin/pfm.rs
PA5
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Very strange things occur on release build:
when
sysclk
is greater thatpclk1
, for example:led does not flashing, but debug build is fine.
I tested this combination:
It's work fine, at both debug and release builds.
But, What occurs when i follow CubeMX suggestion(frequency), I don't understand.
I little modify example from this crate -
PA5
for NUCLEO- F767ZI by default not connected from factory - https://github.com/chessnokov/pfm/blob/master/bin/pfm.rsThe text was updated successfully, but these errors were encountered: