Clock speed on teensy31 defaults to 168000000L

[hamslabs]

Because clock speeds higher than 96MHz are defined in teensy boards.txt (168MHz, 144MHz and 120MHz) and Teensy.mk uses the highest defined clock speed, 168Mhz is selected for F_CPU and this doesn't work. I tested by defining F_CPU in my Makefile and with F_CPU=96000000L the code uploaded and ran properly.

[tuna-f1sh]

I haven't used Teensy so don't have experience with the different boards but Teensy.mk sets to 168 MHz when it chooses the last entry if multiple speeds are defined and no BOARD_SUB has been defined: https://github.com/sudar/Arduino-Makefile/blob/master/Teensy.mk#L47

If your board doesn't work at 168 MHz, is it a subcategory of board?

edit: it looks like the BOARD_SUB is used to define the CPU selection so you could set BOARD_SUB=96

[hamslabs]

I actually think it's a bit of an oversight by the Teensy people. Boards.txt for the Teensy 3.1 has the configuration items for the Arduino menu commented out for the higher clock speeds but keeps the config item for the actual clock speed. I'll log an issue against that and see if Paul will fix it. I'm OK with things right now but I'd hate to see people try your awesome makefile and have it not work. On Feb 1, 2018 1:44 AM, "John Whittington" <notifications@github.com> wrote: I haven't used Teensy so don't have experience with the different boards but Teensy.mk sets to 168 MHz since it chooses the last entry it multiple speeds are defined and no BOARD_SUB has been defined: https://github.com/sudar/Arduino-Makefile/blob/master/Teensy.mk#L47 If your board doesn't work at 168 MHz, is it a subcategory of board? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#552 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAknHr4EgHwdaq8k-fhQHzaPeYXPlcj1ks5tQWtegaJpZM4R06Be> .