From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by ozlabs.org (Postfix) with ESMTP id BA904DDDDF for ; Tue, 2 Dec 2008 19:55:33 +1100 (EST) Message-ID: <4934F7FC.2030105@aimvalley.nl> Date: Tue, 02 Dec 2008 09:55:24 +0100 From: Norbert van Bolhuis MIME-Version: 1.0 To: linuxppc-dev@ozlabs.org, u-boot@lists.denx.de Subject: NAND only (no NOR) Content-Type: text/plain; charset=ISO-8859-1; format=flowed List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Nowadays, do many (PowerPC) embedded devices already risk omitting NOR flash and use a NAND device solely for booting and storing images ? I'm talking about systems with 10 years life-cycle (so no MP3-players nor medical systems but somewhere in between). We have a MPC8313E-RDB and I know booting from NAND is possible. U-boot seems to support it well, I assume it can read the kernel, ramdisk and dtb from NAND in memory and bootm this. However, having no NOR flash means: - NAND should be programmable via JTAG (BDI3000 doesn't support this, Lauterbach/trace32 does) - Critical software images (u-boot, kernel, dtb) stored on NAND, while there's no NAND 'scrubbing', etc.. Thoughts/comments are welcome.