32MS250 Oscillator failure

[QMESAR]

Thank you so much Ben I will be very happy if we could find the problem

[Benj]

Hi Peter,

Right here is a slightly modified definition file that will allow you to enter 80000000 as the clock speed.

32MX250F128B.fcdx

(39.08 KiB) Downloaded 229 times

Hopefully this is all that is needed and it is me reading the datasheets wrong, it says 40MHz is the max speed but there is a divide by 2 so it kind of makes sense that 80 is the right speed. We shall see...

Let me know if this helps to bring any more sense to the situation.

[QMESAR]

Ben still running at half the speed

Thanks for the help

update
The following I noticed the interrupt fires as before more or less at half speed then I removed the Interrupt and used again a delay block with the new 80Mhz setting that seems to be 1/10 of what it should be 10mSec = 100Hz I measure 12Hz

I give up

[QMESAR]

Right here is a slightly modified definition file that will allow you to enter 80000000 as the clock speed.

Hi Ben

Update :
I was confusing myself yesterday I think I did not restart FC after I installed your new fcdx file sorry about that however after going threw the whole situation again today
I can say that the timing seems to be correct now as my interrupt fires exactly on the set times with the OSC setting at 80000000 Hz ,However as mentioned once or twice before the delay blocks seems to be out why that is I have no idea

Just thought I will inform you about the new fcdx file is there no one here that is working with this device just to verify my findings especially the issue with the delays it seems I am working against myself with this at the moment if I am incorrect it would be nice to know that

Thanks so much for all your help