Sudha, This is a hard question to answer because I am not sure what is going on. However, I will take a stab at it. If the QSPI is in the middle of a transmission, nothing will change because another module caused an interrupt. Once the QSPI is set up and a transmission is started, the transmission will go until it is completed. In other words, if the CONT mode is NOT selected and the transmission starts, the QSPI will continue sending data until the End Queue Pointer is reached. Why do you think that an interrupt will modify the QSPI behavior. If I haven't answered your question, post me some more info and I will try again. Charlie -----Original Message----- From: sudha srinivasan [mailto:sudha_sri@...] Sent: Monday, September 01, 2003 6:30 AM To: 68300@yahoogroups.com Subject: [68300] M68332 Dear all, Please help me with the following info : If QSPI is enabled and if an external interrupt or a timer interrupt occurs, the program control is transferred to the SIM module. In this context, will the QSPI operation be resumed ,after servicing the ISR.(Please note that the QSPI is not in interrupt mode). Will the SCK from QSPI to the serial device ,stop as soon as the interrupt is encountered? Thanks Sudha Yahoo! Groups Sponsor <http://rd.yahoo.com/M=259395.3614674.4902533.1261774/D=egroupweb/S=1706554205:HM/A=1524963/R=0/SIG=12o885gmo/*http://hits.411web.com/cgi-bin/autoredir?camp=556&lineid=3614674&prop=egroupweb&pos=HM> <http://us.adserver.yahoo.com/l?M=259395.3614674.4902533.1261774/D=egroupmail/S=:HM/A=1524963/rand=611877966> --------------------------------------------------- To unsubscribe from this group, send an email to: 68300-unsubscribe@yahoogroups.com To learn more about Motorola Microcontrollers, please visit http://www.motorola.com/mcu <http://www.motorola.com/mcu> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> . [Non-text portions of this message have been removed]
Message
RE: [68300] M68332
2003-09-02 by Melear Charles-rdph40
Attachments
- No local attachments were found for this message.