2007-04-23 04:24 AM
Message for all curious about end of write interrupt
2007-04-06 12:24 AM
Sorry, I completely forgot about that file. I got the file from other sources, can't remember now where from exactly.
Here it is. Regards, - mike ________________ Attachments : iostr710.h.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HtKH&d=%2Fa%2F0X0000000aLc%2FZiySTSD800VWs7gIKhHgHJM5PRgcXmLZAo.jhkO.zsE&asPdf=false2007-04-09 02:36 AM
Hello Volius,
Could you please tell me the purpose of the adjustable delay just after the dummy write? The most important is the adjustable delay between enabling the interrupt and disabling it? Thank you & regards, Najoua.2007-04-13 06:01 PM
Hi Najoua,
Sorry for replying late. The idea is to enable the acceptance of the flash interrupt for a short time only to see if the flash IRQ line is asserted in that time window. The length of the second delay defines the size of that window. I played around with the second delay a bit to choose the best value to highlight the problem; it also gives an indication of the length of the IRQ pulse from the flash controller. Regards, - mike2007-04-23 12:35 AM
Hello mike,
In your example, APB2 divider factor is DIV2. Could you please try to change this divider (use DIV4 etc...) and the main frequency and tell me their impact on the interrupt occurrence? Waiting for your feedback, Best regards, Najoua.2007-04-23 04:24 AM
I ran a few more test with different CPU and APB clock frequencies. Here are the results:
Code:
CPU/APB(MHz): Result (indices of the non-zero values in triggered[])
--------------------------------------------------------------------- 50/25: 82..86 (1 run), 81..85 (3 runs) 37.5/18.75: 60..63 (a few runs) 60/30: {126,128} (1 run), {125,127} (2 runs), {126,127} (2 runs) 50,12.5: {80,82,83} (1 run), 79..83 (2 runs), 80..83 (1 run), {85} (1 run), {81} (1 run), no triggering (2 runs) 50,6.25: no triggering (6 runs)Regards, - mike