AM3517EVM Starting kernel fails

Hi,

     Can you post the set environment variables?

      Typing "printenv" in the u-boot prompt provides all the necessary information.

Regards,

N.S.SriHarsha

Hi,

Sorry for this oversight...

Texas Instruments X-Loader 1.46 (Jan 22 2011 - 01:46:00)
Starting X-loader on MMC
Reading boot sector

214940 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...


U-Boot 2009.11 (Mar 19 2010 - 19:46:20)

OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
AM3517EVM Board + LPDDR/NAND
I2C:   ready
DRAM:  256 MB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Die ID #0736000100000000015da3960e01f01d
Net:   davinci_emac_initialize
Ethernet PHY: GENERIC @ 0x00
DaVinci EMAC
Hit any key to stop autoboot:  0
AM3517_EVM # printenv
bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi
bootdelay=10
baudrate=115200
bootfile=uImage
loadaddr=0x82000000
console=ttyS2,115200n8
mmcargs=setenv bootargs console=${console} root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
nandargs=setenv bootargs console=${console} root=/dev/mtdblock4 rw rootfstype=jffs2
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
stdin=serial
stdout=serial
stderr=serial
dieid#=0736000100000000015da3960e01f01d
ethact=DaVinci EMAC

Environment size: 859/131068 bytes
AM3517_EVM #

Regards,

JF_Sor

I've seen that happen when the machine type enumeration is different between the U-Boot image and Linux kernel image. The machine type is in generated file called mach-types.h. U-Boot just silently stops the kernel boot without a message.

This might not be the source of your problem though.

Hi,

        The boot arguments look fine, i reckon it is something to do with the kernel image. Can you enable earlyprintk in the kernel -> menuconfig -> kernel hacking -> kernel low level debugging functions and post the log.

Regards,

N.S.SriHarsha