RE: Machine Check Exception

"Dobbin Allan-r11834" <[email protected]>
Newsgroups gmane.comp.hardware.motorola.microcontrollers
Message-ID <4147ED8B92A864498825C07E53594E4AD48787@az33exm20.fsl.freescale.net>
It could definately be RAM related.  Is it possible your BDM tool
configures the external RAM correctly before it uses it, but you don't
have that same setup running in the flash code before it tries to access
the RAM?  
 

	-----Original Message-----
	From: [email protected] [mailto:[email protected]] On
Behalf Of trailrunner23
	Sent: Friday, June 09, 2006 12:26 PM
	To: [email protected]
	Subject: [MPC500] Machine Check Exception
	
	

	Hello,
	
	We've got two revisions of a custom MPC555 control board. We've
had
	problems with machine check exceptions on the 2nd revision. We
are
	using different types of RAM on the two boards, but we never
have
	exceptions when running code from RAM (BDM), only when the code
is
	running from internal flash. Can anyone shed light on whether or
not
	this is clearly a problem of reading an instruction from
internal
	flash, or could it somehow be RAM-related? Any other ideas?
	
	Thanks very much,
	
	Joe Pasquariello
	
	

	 



[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~--> 
You can search right from your browser? It's easy and it's free.  See how.
http://us.click.yahoo.com/_7bhrC/NGxNAA/yQLSAA/dN_tlB/TM
--------------------------------------------------------------------~-> 

-----------------------------------------------------------
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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.