That has been good points. I've tried both, but with no result so far.
boot_nfs_nand=tftpboot 0x80000000 uImage; set bootargs
${bootargs_fs1}; run addip; bootm 0x80000000 ethaddr=00:11:22:33:44:55
bootcmd=run boot_nfs_nand
bootargs=mem=128M console=ttyO2,115200 noinitrd root=/dev/mtdblock6
rootfstype=jffs2
bootargs_fs1=mem=128M console=ttyO2,115200 noinitrd
root=/dev/mtdblock6 rootfstype=jffs2 debug earlyprintk
- Arno
2011/7/28 Felipe Balbi <ba...@ti.com>:
> On Thu, Jul 28, 2011 at 03:15:20PM +0200, Arno Steffen wrote:
>> Maybe you are so kind to give me a hint:
>>
>> Try to migrate from Kernel 33 to 37. Currently I don't see any message after
>>
>> Verifying Checksum ... OK
>> Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> From what I understand kernel starts with start_kernel()).
>> What is best way to find out which part is failing? At which point I
>> do a printk to see what's going on, or at least set a GPIO Pin of the
>> processor?
>> How to debug without any external tools like JTAG.
>
> try to enable CONFIG_DEBUG_LL and CONFIG_EARLY_PRINTK, then add "debug
> earlyprintk" to your command line. See if that helps showing more debug
> messages.
>
> --
> balbi
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
