ColdFire/68K Microcontrollers and Processors中的主题 52235 - sprintf x violation access interrupt https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/52235-sprintf-x-violation-access-interrupt/m-p/145002#M3028 <HTML><HEAD></HEAD><BODY><DIV>Hello guys</DIV><DIV>I posted a SR (below) along Freescale today.</DIV><DIV>If you could provide me some help/comment I will appreaciate it a lot ..!!Thanks</DIV><DIV>&nbsp;</DIV><DIV>Hi Freescale.</DIV><DIV>&nbsp;I created a 1000 bytes console_buffer to serve as a console debug via serial port (only tx work).For each application event, I transmit a respective frame over the serial port in order the application can be observed through the hyperterminal screen.A pointer scheme was created to allow more then 1 event be generated at time, therefore pushing its frame over such console_buffer.The problem is, I am going to violation access interrupt vector (#2) frequently when a frame is been transnmitted at the same time sprintf is called to write the next frame in the console_buffer.Besides this vector#2, some variables are crashed without reasons, a typical stack size problem (currently 2Kbytes, enough I believe..).BUT, If I before the sprintf call I disable the interrupts (sr=2700 etc..), and so enable it back after the calling, the problem disappear.The interrupt serial TX function is very simple...just a comparsion between pointer and data size..I don´t know what kind of information I can provide, but..here I am...However keep on mind the detail about disable interrupts at sprintf call..Some special care about sprintf stack,timming,parameters?Realize such buffer is used at the same time by sprintf and tx interrupt</DIV></BODY></HTML> Mon, 12 Feb 2007 10:31:10 GMT Ricardo_RauppV 2007-02-12T10:31:10Z 52235 - sprintf x violation access interrupt https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/52235-sprintf-x-violation-access-interrupt/m-p/145002#M3028 <HTML><HEAD></HEAD><BODY><DIV>Hello guys</DIV><DIV>I posted a SR (below) along Freescale today.</DIV><DIV>If you could provide me some help/comment I will appreaciate it a lot ..!!Thanks</DIV><DIV>&nbsp;</DIV><DIV>Hi Freescale.</DIV><DIV>&nbsp;I created a 1000 bytes console_buffer to serve as a console debug via serial port (only tx work).For each application event, I transmit a respective frame over the serial port in order the application can be observed through the hyperterminal screen.A pointer scheme was created to allow more then 1 event be generated at time, therefore pushing its frame over such console_buffer.The problem is, I am going to violation access interrupt vector (#2) frequently when a frame is been transnmitted at the same time sprintf is called to write the next frame in the console_buffer.Besides this vector#2, some variables are crashed without reasons, a typical stack size problem (currently 2Kbytes, enough I believe..).BUT, If I before the sprintf call I disable the interrupts (sr=2700 etc..), and so enable it back after the calling, the problem disappear.The interrupt serial TX function is very simple...just a comparsion between pointer and data size..I don´t know what kind of information I can provide, but..here I am...However keep on mind the detail about disable interrupts at sprintf call..Some special care about sprintf stack,timming,parameters?Realize such buffer is used at the same time by sprintf and tx interrupt</DIV></BODY></HTML> Mon, 12 Feb 2007 10:31:10 GMT https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/52235-sprintf-x-violation-access-interrupt/m-p/145002#M3028 Ricardo_RauppV 2007-02-12T10:31:10Z Re: 52235 - sprintf x violation access interrupt https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/52235-sprintf-x-violation-access-interrupt/m-p/145003#M3029 <HTML><HEAD></HEAD><BODY><DIV>Hi peolple</DIV><DIV>This issue was solved by a Freescale SR..</DIV><DIV>The problem was that my universal interrupt entry point was stacking only A0/A1 and D0/D1, as I copied from a 5213 example...</DIV><DIV>The orientation I received from Freescale was to push all regsiters A0- to A7 and D0 to D6.</DIV><DIV>It worked perfectly....</DIV><DIV>Now on, I will allways stack all these registers instead of&nbsp;be concerned what exacltly I should stack...</DIV><DIV>If someone have a more elegant one...let us now ...</DIV><DIV>Thanks ...</DIV><DIV>&nbsp;</DIV></BODY></HTML> Sat, 03 Mar 2007 23:08:38 GMT https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/52235-sprintf-x-violation-access-interrupt/m-p/145003#M3029 Ricardo_RauppV 2007-03-03T23:08:38Z