Hi Joakim!
Thanks for the update! I’ll test it asap on PR #7181 which will need an update
since #7209 was merged.
I’ll keep you updated on the results.
Cheers,
--
Francisco Javier Acosta Padilla
Research Engineer at INRIA Saclay
INFINE Team
On 18 July 2017 at 09:47:13, Joakim Nohlgård
Hi again Francisco,
See https://github.com/RIOT-OS/RIOT/pull/7379 for an updated clocking
configuration for Kinetis boards. I think it will be more robust
against non-default starting values because it tries to go to a safe
mode (using the internal reference clock) before reconfiguring the
clock
Hi Joakim! Thanks for the hints.
Your proposed approach at a first sight it seemed to work, then I rebased on
your PRs and it didn’t work anymore. But more strange, I reverted your commits
and it doesn’t work either… However, with the clock configuration that I
proposed before it still works,
Hi,
I think the wisest choice is probably to switch to FEI mode first to use
the internal oscillator before booting a new image. That is the same mode
that the mcu comes up in after a hardware reset.
There are some relevant PRs open on GitHub for the Kinetis clocking:
Hi RIOT devs!
I’m currently working on the RIOT port for MCUBoot[1], which takes the
frdm-k64f board as a reference board, and that’s also supported by RIOT and
other OSs using MCUBoot.
My first goal is to provide a “bootable” image compiled in RIOT and booted by
MCUBoot built for mynewt.
