From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Roese Date: Thu, 8 Dec 2011 08:30:02 +0100 Subject: [U-Boot] How to test a new u-boot image over network? In-Reply-To: <629D989C137DD040A0A994BD21888F1E75E81DF9@MX29A.corp.emc.com> References: <629D989C137DD040A0A994BD21888F1E75E81D17@MX29A.corp.emc.com> <20111207205216.687CA1ECC5F@gemini.denx.de> <629D989C137DD040A0A994BD21888F1E75E81DF9@MX29A.corp.emc.com> Message-ID: <201112080830.03312.sr@denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Vikas, On Wednesday 07 December 2011 23:13:18 vikas.sontakke at emc.com wrote: > I do know that the board has NAND flash and it is seen by the u-boot. > > FLASH: 16 MB > NAND: 1024 MiB > > The vendor has told us that the actual flash is lot bigger than reported by > u-boot. Then the vendor U-Boot port is broken. > > (assuming your out-of-tree port supports NAND booting) > > How do I find this out? NAND booting required that chip-select 0 is connected to the NAND chip. If your board usually boots from NOR, then it is connected to the NOR FLASH chip. The AMCC/APM evaluation boards have a jumper to toggle this chip-select between NAND and NOR. If your custom board doesn't have such a means to toggle the CS0 then you have no chance to boot from NAND. Another idea would be to build a rambooting U-Boot target for your board. This is supported for Sequoia. But not for Canyonlands. You might want to take a look at that. Otherwise you need to burn the U-Boot image into your NOR FLASH and just hope that it works. A JTAG debugger would be handy if it doesn't work though. Best regards, Stefan -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de