Zane
Thank you for your feedback,
In my experience with the other tools is that the peripheral clock is set to divider 1 and as you have seen is that the clock speed is correct as the peripheral clock matches the input clock ,now it is the situation that to calculate the buad rate for example the UART you take now the peripheral clock speed and calculate that for the value that should go into UART baudrate register .for me when Peripheral clock match input clock value and the UART baud is incorrect then FC uses the wrong clock speed or calculate it incorrectly ,I have worked with a few PIC32 and I have not seen this issue on them at all I have used PIC32MX460,534 and 795 in another tool chain ,I will try to run your FC chart with me some time this week as tomorrow and Tuesday I will be at the hospital.(will run your FC chart on my hardware and analyse what you have seen
) With me on my hardware I have not seen the interrupt run correctly unless I set the Peripheral divider to 2, strange this here happening I am lost
Unfortunately I do not have PIC32MX270F256B device only PIC32MX250F128B I will order one tomorrow.
You can test my theory by setting the clock speed to 50% in the project settings then your baud should be correct and your interrupt might go off again
In my opinion and experince so far with PIC32 is that this timing issue is not a PIC32 problem more a misunderstanding or something small incorrect in FC that is causing this and with your help mine and Ben sure we will solve it
We have the hardware and Ben the knowledge