Open enjoychang opened 9 years ago
Ctn use i2c with too high speed - this may be a problem with higher clocks.
Unfortunately i don't work on this project for a very long time so i can't really answer this, however what @CopterFail seems reasonable, the prescalers will go a bit crazy with cpu overclock, so you will have to compensate for that.
OK. Thanks, that make sense. Also I found the pwm output for esc doesn’t work with overclock either.
Chang
Chang Liu Aeronautics, Astronautics and Computational Engineering Group Faculty of Engineering and the Environment Engineering Centre of Excellence Building 176, Room 5001, Table 103 Boldrewood Campus University of Southampton Southampton SO16 7QF Mobile: +44(0)7859400775
Background:
https://sites.google.com/site/changliuuav/home http://www.southampton.ac.uk/engineering/postgraduate/research_students/cl21g11.page?#background http://blog.soton.ac.uk/robotics/ https://www.linkedin.com/profile/view?id=151520195&trk=nav_responsive_tab_profile
On 23 Jul 2015, at 07:15, CopterFail notifications@github.com wrote:
Ctn use i2c with too high speed - this may be a problem with higher clocks.
— Reply to this email directly or view it on GitHub https://github.com/cTn-dev/Phoenix-FlightController/issues/5#issuecomment-123989302.
Looks like this firmware only works with maximum 72MHz Compilation. Any progress on updated code for overclocked compilations, like 96 or 120 MHz?
Thanks.