Forum Post: RE: MSPM0G1519: TIMG12 capture using external 32MHz clock and external 1Hz latch signals

I think [Helic will correct me?] that Helic was describing using the 32MHz signal to provide one of the system clocks, and routing that to the timer as TIMCLK. I was describing using the 32MHz as a counter-trigger via the (e.g.) C1 pin. Digging a bit further, I think I see the terminology conflict: I think of this (the 32MHz via C1) as a "timer clock" since it drives the counter to tick; the designers consider this a Compare unit feature that (also) causes the counter to tick. Helic (and Sysconfig) are correct that the TIMCLK that runs the rest of the timer unit needs to be one of the system clocks. (This presumably needs to be >=32MHz; BUSCLK seems like a good bet.) The model for this is described in TRM (SLAU846B) Sec 27.2.3.2.1 and illustrated in example timx_timer_mode_compare_edge_count: https://dev.ti.com/tirex/explore/node?node=A__AAR6edrrZqUYodAtIjBtSQ__MSPM0-SDK__a3PaaoK__LATEST In the Example this is done in Driverlib via a (synthesized) mode "DL_TIMER_COMPARE_MODE_EDGE_COUNT" which does the things I described above. I'm not a Sysconfig wizard, but I didn't find a mechanism to Also set the other channel (C0) for Capture. I'm pretty sure the timer unit is capable of it.