Does the increment of a timer on pic is equal for a pic16 and pic32?

The question is because in porting code from a PIC16F15324T using MCC to a project using a PIC 32MX470F512L.

There are portions of code where i have code like this:

    TMR1 = 0; // Starts counting
while (TMR1 < TIME_BIG_PULSE_CONFIRM) // Minimum time to be considered big pulse
{

if (!data_in_get_value()) {
if (!data_in_get_value()) { // Simple debounce - confirm twice
break; // Get out of the while
}
}
}


This may seem like a noob question, but are do the increments of TMR happen what same time if i configure both timers for 8us? Of course i know that the pic with the higher frequency is supposed to execute instrutions a lot faster (that would be true if MCC was optimized for the pic32)

PIC16 MCC:

PIC32 MCC:

• what does PIC32 MCC say if you request 8MHz? – Bruce Abbott Jun 8 '19 at 3:22
• @bruceabbott hi, you mean if I don't use pll? It works. MCC doesn't give a warning. – Nmaster88 Jun 8 '19 at 16:32
• "MCC doesn't give a warning" - if it calculates a period of 8us then it should be fine (the period count will be different of course, due to the higher PBCLK frequency). – Bruce Abbott Jun 8 '19 at 21:35
• @bruceabbott I think that is really my doubt! How can I count period count then? Because I was assuming that if the calculated period is equal for both that the period count would happen at the same time. – Nmaster88 Jun 9 '19 at 9:59
• MCC calculates the required count to get the period you want. This count then has to go in the timer setup code (either automatically generated or manually if you are writing your own routines). If the clock frequencies are different then the timers have to be set up differently to get the same period. The 8 bit and 16 bit timers have a slightly different setups, but MCC takes care of it for you.. – Bruce Abbott Jun 9 '19 at 11:00