RE: Program variable on the internal flash of MPC566 on runtime
Dobbin Allan-r11834 <[email protected]>
| Newsgroups | gmane.comp.hardware.motorola.microcontrollers |
|---|---|
| Message-ID | <45E41B46B1F8D81183E4000F20D7C40B0B568265@az33exm40-bu.am.freescale.net> |
Are you saying that you want to save the QADC conversion result to FLASH just because the SRAM is too small? This sounds like quite a lot of work just to save a couple of bytes of SRAM. If you want to store this result in FLASH so that it is available after reset, that is a valid reason. But if you want to save it to FLASH just to save a few bytes of SRAM, that sounds unreasonable and you may want to reconsider. Regards, Allan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of crbtfp Sent: Wednesday, April 20, 2005 2:22 PM To: [email protected] Subject: [MPC500] Program variable on the internal flash of MPC566 on runtime Hi I have axiom 566EVM. I use Code Warrior 8.0. I do the sampling of analog signal by QADC64E. Because SRAM is too small.I want to save this result in internal flash memory on runtime. Can I do that? I 've tried to program to flash on runtime by save the output result of QADC64E to a variable in SRAM then I want to program that variable to internal flash on runtime. The mpc566 ref. manual is unclear, how to write to address data latch and how to program to program data latch of MPC566. I can not make EHV bit go high(=1) Does anyone have recommendations? And Does anyone know how many times can I program to the internal flash memory? one manual said 1000 times another manual said 100000 times Thank you very much PS ----------------------------------------------------------- To learn more about Freescale Microcontrollers, please visit http://www.freescale.com/mcu Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/MPC500/ <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/