Hi Everybody,
I have a MC68332 board which has a FLASH (AM29F200B).
My problem is regarding the programming of the Flash. Is
any body aware of a method of programming it in circuit.
Alternatively is there a way to program the Flash using
the BDM cable meant for the 68332.
Thanks & Regards,
Philip Jones,
Engineer,
R&D Department,
ID Technologies. (A division of mark elektriks)
============================================================
B1/1, Sai Sahawas Apt., \ufffd|\ufffdPhone: +91-20-4003315, 4007158
Oppo. Corporation Bank, \ufffd|\ufffdTeleFax: +91-20-5410479
Maharshi Karvenagar, \ufffd \ufffd |\ufffdEmail: development@...
Hingne (Bk), \ufffd \ufffd \ufffd \ufffd \ufffd \ufffd | www.markelektriks.com
Pune - 411052. India. \ufffd \ufffd|
============================================================
-----Original Message-----
From: Melear Charles-rdph40 <charles.melear@...>
To: "'68300@yahoogroups.com'" <68300@yahoogroups.com>
Date: Thu, 4 Sep 2003 06:51:11 -0700
Subject: RE: [68300] M68332
> Sudha,
>
> When you are using the QSPI to program a serial EEPROM,
> you can use several different methods and this will
> depend on how you write your QSPI driver.
>
> I imagine that your QSPI driver is set up to send an
> address, a control byte and then the data to program a
> particular address in the EEPROM.
>
> Now, if you DO NOT use the "continuous" mode in the QSPI,
> you simply load up the Transmit Data RAM and the
> associated Command RAM bytes and start the QSPI. The
> QSPI will take the first byte at the location pointed to
> by the Start Queue Pointer and continue transmitting
> until the End Queue Pointer is reached. Whether you get
> an interrupt on not, the QSPI will finish the
> transmission.
>
> Now, it may be the case that you DO use the QSPI in the
> CONTINUOUS mode. In this case, once the QSPI is started,
> it will take the first byte from the location pointed to
> by the Start Queue Pointer, go to the End Queue Pointer
> and then loop back to the New Queue Pointer. In this
> case, the QSPI will just keep going regardless of whether
> you get an interrupt or not. When using the CONTINUOUS
> mode, your software will have to kill the QSPI process by
> clearing the CONT bit and then waiting for the SPE bit to
> self clear. (NOTE: very important -- you DO NOT want
> to kill a QSPI transmission by clearing the SPE bit.
> This will mess up the transmission of the byte that is
> currently being transmitted.)
>
>
> A TIMER interrupt is not going to affect the operation of
> the QSPI.
>
> The QSPI will just keep going if it is in the CONTINUOUS
> mode. The QSPI will finish transmitting the current
> buffer if it is NOT in the CONTINUOUS mode.
>
>
> So, the question becomes something like this: If I am
> programming the serial EEPROM and I get a TIMER
> interrupt, is it OK to go service the TIMER and then come
> back to the programming job.
>
> >From what I know about your application, this should be
> totally OK. If the QSPI is doing something, it will
> either complete the process (not in CONT mode) or the
> QSPI will just keep looping on a process (CONT mode
> enabled). So, when you come back from the TIMER ISR, you
> should just be able to continue from where you left off.
>
> Regards,
>
> Charlie
>
> -----Original Message-----
> From: sudha srinivasan [mailto:sudha_sri@...]
> Sent: Thursday, September 04, 2003 6:01 AM
> To: 68300@yahoogroups.com
> Subject: RE: [68300] M68332
>
>
> Charlie
> Thanks for your response.
> The scenario is like this.I am interfacing the SEEPROM
> with QSPI of
> M68332.The application calls for a Timer Interrupt
> occurring every 2 ms.In
> such a situation,if there is a need to write into the
> SEEPROM and the write
> takes more than 2ms,How does M68332 handle this?
> Is there a possibilty of doing a part of the QSPI
> operation, servicing the
> timer interrupt and then continuing the rest of the QSPI
> operation?If yes
> ,how do we go about this?
> Kindly respond
>
> Sudha
>
> -----Original Message-----
> From: Melear Charles-rdph40
> [mailto:charles.melear@...]
> Sent: Tuesday, September 02, 2003 7:06 PM
> To: '68300@yahoogroups.com'
> Subject: RE: [68300] M68332
>
>
> 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=eg
> roupweb/S=17065542
> <http://rd.yahoo.com/M=259395.3614674.4902533.1261774/D=e
> groupweb/S=17065542>
> 05:HM/A=1524963/R=0/SIG=12o885gmo/*
> http://hits.411web.com/cgi-bin/autoredir?
> <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.1
> 261774/D=egroupmai
> <http://us.adserver.yahoo.com/l?M=259395.3614674.4902533.
> 1261774/D=egroupmai>
> l/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>
> < 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/
> <http://docs.yahoo.com/info/terms/> > .
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ---------------------------------------------------
> 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
> http://docs.yahoo.com/info/terms/
> <http://docs.yahoo.com/info/terms/>
>
>
>
>
>
> Yahoo! Groups Sponsor
>
> ADVERTISEMENT
> <http://rd.yahoo.com/M=259538.3830715.5078802.1261774/D=
> egroupweb/S=1706554205:HM/A=1712983/R=0/SIG=11u38u3s2/*ht
> tp://hits.411web.com/cgi-bin/hit?page=1374-10595183833103
> 2> click here
>
> <http://us.adserver.yahoo.com/l?M=259538.3830715.5078802.
> 1261774/D=egroupmail/S=:HM/A=1712983/rand=821019471>
>
> ---------------------------------------------------
> 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]
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> ---------------------------------------------------
> 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
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>Message
Flash Programming
2003-09-05 by development