Theremingenieur
Senior Member+
I've tried to understand the K66 reference manual and to make the link with what happens in the mk20dx128.c file, but I don't get it sorted...
Running the T3.6 at 180MHz would normally not allow USB operation since there is no fitting clock divider. That's why a 48MHz helper clock is used to generate the USB clock. So far, so good.
My problem seems a little more complex: I'd like to run the T3.6 as quick as possible without over clocking (180MHz) and have a high PDB clock which is not too far beyond the specs, but it would have to be a multiple of 192kHz, for example 57.6MHz or 48MHz, which would be acceptable in case it was easy to re_route IRC48M to the PDB0 while the other peripherals (FTMs etc) would ideally run with a bus clock around 60MHz.
Paul, Frank, any suggestion from the clock gurus?
Running the T3.6 at 180MHz would normally not allow USB operation since there is no fitting clock divider. That's why a 48MHz helper clock is used to generate the USB clock. So far, so good.
My problem seems a little more complex: I'd like to run the T3.6 as quick as possible without over clocking (180MHz) and have a high PDB clock which is not too far beyond the specs, but it would have to be a multiple of 192kHz, for example 57.6MHz or 48MHz, which would be acceptable in case it was easy to re_route IRC48M to the PDB0 while the other peripherals (FTMs etc) would ideally run with a bus clock around 60MHz.
Paul, Frank, any suggestion from the clock gurus?