22 Dec
2017
22 Dec
'17
1:46 p.m.
On Thu, Dec 21 2017, Vít Krátký wrote:
Hello,
the problem persists at least at some boards.
Used commands and corresponding outputs: -> sysClkRateSet(1001) value = -1 = 0xffffffff -> sysClkRateSet(1000) value = 0 = 0x0
You are right. Now it's really fixed and tested as well. The problem was that maximum clock rate can be set at two places: BSP and kernel configuration. Previously we set it in BSP, but kernel configuration overrides the BSP value. Best regards, -Michal Sojka