Hi, The problem seems from nfs module, I tried various settings and it only worked if: 1. Disable nfs client (ver 3) or 2. Enable both nfs client (ver. 3) and ipv6 support. I only know that it stucks before initiazation of coldfire console module.
I am using your nommu mainstream (chip mcf5271). Just see that you've recently merged the kernel. I will test with that soon. Thanks for the support, On Wed, Mar 9, 2011 at 8:51 AM, Greg Ungerer <g...@snapgear.com> wrote: > > Hi Viet, > > On 24/02/11 22:02, Viet Nguyen wrote: >> >> Hi, >> The problem due to MAC address. >> I fixed by reading MAC address from flash, write to FEC_ADDR_LOW/HIGH, >> then dhcp, boa,... just worked fine. >> However, if I turn off the board for a while (15s), the boot progress >> just hang right after u-boot transfers the control to linux. > > What ColdFire CPU model is this one? > What version of the kernel are you running/loading? > > >> ===== >> Verifying Checksum ... OK >> kernel data at 0xff840040, len = 0x001f2000 (2039808) >> ## No init Ramdisk >> ramdisk start = 0x00000000, ramdisk end = 0x00000000 >> Loading Kernel Image ... OK >> OK >> kernel loaded at 0x00020000, end = 0x00212000 >> ## cmdline at 0x00f886f0 ... 0x00f88733 >> ## kernel board info at 0x00f886b0 >> memstart = 0x00000000 >> memsize = 0x01000000 >> flashstart = 0xFF800000 >> flashsize = 0x00800000 >> flashoffset = 0x00000000 >> sramstart = 0x20000000 >> sramsize = 0x00001000 >> mbar = 0x40000000 >> cpufreq = 100 MHz >> busfreq = 50 MHz >> ethaddr = 00:e0:0c:bc:e5:60 >> ip_addr = 192.168.2.200 >> baudrate = 115200 bps >> ## initrd_high = 0xffffffff, copy_to_ram = 1 >> ramdisk load start = 0x00000000, ramdisk load end = 0x00000000 >> ## Transferring control to Linux (at address 00020000) ... >> ===== >> u-boot source: arch/m68k/lib/bootm.c: >> (*kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end); >> >> The problem does not happen if from u-boot, I download something from >> tftp to ram (not flash), then reset the board (turn off in 5s). >> I tried to set value to a IO port in setup_arch() >> (...)m68knommu/kernel/setup.c but that function has not executed. >> >> So may the problem is from bootloader or kernel? How to confirm the >> kernel is executed or not? >> Any suggestion about debugging it. > > It is quite likely uboot doesn't set the MAC address into the FEC > registers unless it actually has to load something through the > eth interface. But still, the Linux FEC driver doesn't really care > if it has a MAC address at init time - you can set it with ifconfig > from user space when your kernel is up and running. So in other > words not having a MAC address in the FEC registers shouldn't stop > Linux booting. > > (I assume you are not using nfs root though?) > > Regards > Greg > > > ------------------------------------------------------------------------ > Greg Ungerer -- Principal Engineer EMAIL: g...@snapgear.com > SnapGear Group, McAfee PHONE: +61 7 3435 2888 > 8 Gardner Close FAX: +61 7 3217 5323 > Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com > _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
