-
Notifications
You must be signed in to change notification settings - Fork 3k
Closed
Description
Description of defect
Need to configure an external clock source in targets.json and mbed_app.json
Building for TARGET_MTS_MDOT_F411RE will always use the internal clock source. Our hardware has a 26MHz external clock to ensure an accurate system clock.
Target(s) affected by this defect ?
TARGET_MTS_MDOT_F411RE
TARGET_MTS_DRAGONFLY_F411RE
Toolchain(s) (name and version) displaying this defect ?
GCC and ARMCC
What version of Mbed-os are you using (tag or sha) ?
mbed-os-6.8.0 works correctly
mbed-os-6.9.0 and later have changed clock settings for STMF411xE targets
What version(s) of tools are you using. List all that apply (E.g. mbed-cli)
mbed cli 1.10.4
How is this defect reproduced ?
Building an application that uses the event queue or timeout to record internal timing to compare to a real clock source with show that the system is not running realtime.
#include "mbed.h"
bool test = false;
void flip()
{
test = !test;
}
Thread t;
int main()
{
// creates a queue with the default size
EventQueue queue;
t.start(callback(&queue, &EventQueue::dispatch_forever));
// events are simple callbacks
queue.call_every(2000ms, flip);
// events are executed by the dispatch method
// queue.dispatch_forever();
//
Timer timer;
timer.start();
while (true) {
if (test) {
printf("hello %lu\n", timer.read_ms());
test = false;
}
}
}