From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Loeliger Date: Thu, 17 May 2007 10:35:10 -0500 Subject: [U-Boot-Users] CFG_MONITOR_BASE < CFG_FLASH_BASE In-Reply-To: <464B8F93.7010005@freescale.com> References: <20070516220434.ABD38352650@atlas.denx.de> <464B818F.60509@freescale.com> <406A31B117F2734987636D6CCC93EE3C017BA2D5@ehost011-3.exch011.intermedia.net> <464B8F93.7010005@freescale.com> Message-ID: <1179416110.23707.3.camel@ld0161-tx32> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wed, 2007-05-16 at 18:11, Timur Tabi wrote: > Can you give me some details as to how this works? I'm trying to figure out if this > approach is meaningful for boards based on Freescale 8xxx CPUs. I'm guessing it's not, > and that the code I see in the board header files is some left-over legacy from a > completely different CPU that no one ever bothered to think about. Timur, There are test-bed environments, for example, that are capable of setting up some LAWs, configuring DDR, and injecting a new test image into RAM via a JTAG or scan device. From there it is an obvious "boot from RAM" situation useful for rapid turn testing. jdl