From mboxrd@z Thu Jan 1 00:00:00 1970 From: alfred steele Date: Thu, 30 Apr 2009 11:25:58 -0500 Subject: [U-Boot] U-boot -printk kernel crash dump using md on PDK In-Reply-To: <59b21cf20904300905o1abcbaccmdaa28d32316208cb@mail.gmail.com> References: <528f13590904262208s66b17bdekac218fba7994d177@mail.gmail.com> <59b21cf20904281031y1a81448dw2e750d335473d183@mail.gmail.com> <528f13590904281102k3a90e220n865dba306ee9fb@mail.gmail.com> <59b21cf20904281325x77290c67kf701ffee717e21e3@mail.gmail.com> <528f13590904281403g330e29a0r39278a99575fe064@mail.gmail.com> <59b21cf20904282312m4b5e5442k26d67f42c3fe433d@mail.gmail.com> <528f13590904290948g23609a6et634913c2542fabaf@mail.gmail.com> <59b21cf20904291052p4ec69d38g3b3414a9435ea48d@mail.gmail.com> <528f13590904291636w1005c7e5o4de701f0153cc401@mail.gmail.com> <59b21cf20904300905o1abcbaccmdaa28d32316208cb@mail.gmail.com> Message-ID: <528f13590904300925lb7148eapf2eda301bd5cc30@mail.gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Magnus, > If U-boot had full NAND support for i.MX31, NAND would be detected > somewhere between steps 7 and 8. Thanks for the elaborate explanation. I did not find any detailed documentation for the same in the u-boot readme's. > See my explanation above. CONFIG_SKIP* is defined when compiling > U-boot, but not when compiling SPL. That explains why i swa the #warning spit out. So you mean the CONFIG_SKIP_LOWLEVEL_INIT and CONFIG_SKIP_RELOCATE_UBOOT get toggled during compile time only. I am still struggling to get the NAND boot working. I am not even seeing U-boot spit out the first line on the console "U-boot " when i power up subsequently. This is what i did to build and run. i) make mx31_pdk_nand_config ii) make Take U-boot-nand.bin and burn it at physical offset 0x0 of the NAND using Redboot loaded via JTAG. When i reset, i see nothing on the console. I may be missing something which applying the patches then. Remote gdb does not allow me to debug. If i put printfs in _start_armboot in board.c, looks like its not ven entering that function. Has the standard output and the serial console dev been initiliazed before this point i.e start_armboot? Have you got a chance to post the patches to the mainline yet? Thanks, Alfred.