U-boot build problem in LTIB and creating a new uSD card process

cancel
Showing results for 
Search instead for 
Did you mean: 

U-boot build problem in LTIB and creating a new uSD card process

3,890 Views
snirnisim
Contributor III

hello everyone,

for the past two weeks i tried learning how to make a new uSD card with minimal configuration to boot the QSB.

i've followed the "ltib_build_host_setup.pdf" document and now i'm having a PC running UBUNTU 10.04LTS with all relvant packages. i installed LTIB from "L2.6.35_11.09.01_ER_source" and followed the instruction (which i can't say i fully understand...) in the "i.MX53_START_Linux_BSP_UserGuide" PDF. for the beging i wanted to just compile the minimun configuration selecting the proper "LOCO" board.

i'm rapidly getting the error :

These packages failed to build:
u-boot

Build Failed

Exiting on error or interrupt

( full terminal plot in attached "log.txt" file).

i hope someone can help me solve this asap.

if someone can explain me please the proccess of moving the files (that LTIB will create when build will successed) to a uSD, which i inserted to the PC runinig linux, with a SD adapter and a usb to SD converter, and then which commands i have to use after i'm moving the card to the QSB in order to setenv for U-boot and properly boot the board.

sorry about the my english and i hope i'ts clearly enough.

thanks in advance,

snir

Labels (1)
73 Replies

325 Views
KrishnaPavan
Contributor II

Hi Vincent,

If you have got the bootloader loaded, then it's fine.

I think the problem is with the partitions made.

Either the initrd or kernel has some issues!

0 Kudos

325 Views
VincentChou1z
Contributor III

I did try to reformat the SD card and re-run the script to generate the image on the SD Card.  In addition, I plug in the SD card to the card reader in my NB running Ubuntu 10.04 and could see a boot partition on the SD card without problem.  Now I start to suspect that the board may be the cause instead of the SD card itself.  Is it possible that my board could only support the QSB image instead of SMD image?  

0 Kudos

325 Views
StevieRG
Contributor II

It seems you are missing some partitions on the SD card. The boot looks like it cannot find the partition with the linux kernel image on it.

Maybe these suggestions might help:

The shell script I posted has some paths defined in it, be sure your ltib build places the files into these paths, or change the paths in the script to match yours.

Also be sure the ltib build fits into the size of the partitions being created on the SD card.

On your Linux PC, can you see all the partitions on the SD card? And the Linux system dirs and files?

I remember some time ago I had an SD card in a strange state where it would not partition correctly no matter what I did, I think I caused this by ejecting the card one time before writing was finished. The fix was a full low-level reformat of the SD card.

Could you also try a new out-of-the-box SD card.

0 Kudos

325 Views
VincentChou1z
Contributor III

Hi!  Steve,

My bootargs are:

loadaddr=0x70800000

bootargs_base=setenv bootargs console=ttymxc0,115200

bootargs_mmc=setenv bootargs ${bootargs} ip=dhcp root=/dev/mmcblk0p1 rootwait rw

bootcmd_mmc=run bootargs_base bootargs_mmc;mmc read 0 ${loadaddr} 0x800 0x1800;bootm

bootcmd=run bootcmd_mmc

Any suggestion?

Vincent

0 Kudos

325 Views
StevieRG
Contributor II

Hello Vincent, could you please post your bootargs.

0 Kudos

325 Views
VincentChou1z
Contributor III

Hi!  Steve, 

I downloaded your flash_ltib.sh and it works wonderfully so far.  However, after I switch to L2.6.35_05 source bundle and the same "unable to mount rootfs" error!  The error message is like 

VFS: Cannot open root device "mmcblk0p1" or unknown-block(179,1)
Please append a correct "root=" boot option; here are the available partitions:
bxxx xxxxxxxx mmcblk0 driver: mmcblk
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)
[<80038538>] (unwind_backtrace+0x0/0xf0) from [<8040f8d4>] (panic+0x6c/0xe0)
[<8040f8d4>] (panic+0x6c/0xe0) from [<80008ddc>] (mount_block_root+0x1cc/0x20c)
[<80008ddc>] (mount_block_root+0x1cc/0x20c) from [<80009028>] (prepare_namespac)
[<80009028>] (prepare_namespace+0x11c/0x174) from [<800084a0>] (kernel_init+0x1)
[<800084a0>] (kernel_init+0x120/0x168) from [<800349e0>] (kernel_thread_exit+0x)

Have you had any experience you could share?  Why could the different source bundle have different outcome from the script?  Let me thank you beforehand!

Vincent 

0 Kudos

325 Views
StevieRG
Contributor II

It's good that you have found the community advice helpful and now have a booting system. Your next question is not related to bootup so maybe it's best to ask this in another discussion. By the way, you might first also want to do a Google for standard Linux commands that show you what modules are loaded or devices are mounted.

0 Kudos

325 Views
enaud
Contributor III

okkk it work... but on user_guide there arent setenv!

now work.. how i can view if sierra wireless driver is mounted correclty?

0 Kudos

325 Views
KrishnaPavan
Contributor II

@enaud
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm
bootargs_mmc=setenv bootargs ${bootargs} ip=dhcp root=/dev/mmcblk0p1 rootwait rw
bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x1800; bootm

These are the bootargs, that were responsible for error, which is the reason why you should have a USER_GUIDE & refer to it.

No one will Spoonfeed you, when a very good USER_GUIDE is available.

0 Kudos

325 Views
enaud
Contributor III

ok i set environment:

setenv lvds 'video=mxcdi0fb:RGB666,XGA ldb'
setenv lcd 'video=mxcdi0fb:RGB24,SEIKO-WVGA'
setenv vga 'video=mxcdi1fb:GBR24,VGA-XGA di1_primary tve'
setenv hdmi 'video=mxcdi0fb:RGB24,1024x768M@60'

setenv bootcmd_obds 'ext2load mmc 0:1 0x70800000 /unit_tests/obds.bin; go 70800000'

setenv bootargs_base 'setenv bootargs console=ttymxc0,115200 ${vga}'
setenv bootargs_nfs 'setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp'

setenv bootcmd_net 'run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm'

setenv bootargs_mmc 'set bootargs ${bootargs} root=/dev/mmcblk0p1 rw rootwait'

setenv bootcmd_mmc 'run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x1800; bootm'

setenv bootcmd 'run bootcmd_mmc'

saveenv

and after i reboot

 and now i have on minicom:

---------------------------

root filesystem built on Thu, 08 Mar 2012 15:29:23 +0100
Freescale Semiconductor, Inc.

freescale login: root
login[2260]: root login on 'ttymxc0'
root@freescale ~$ ls

-----------------------------

why ls not works?

0 Kudos

325 Views
StevieRG
Contributor II

It looks like your kernel is booting and your system is trying to get a DHCP address. If it seems to be hanging up just leave it and it will time out. It will do this if you don't have any environment set.

You might gain from reading this discussion, from the start, in which many contributors have posted suggestions on these same issues. May I suggest you to start with use the basic environment variables I posted, which will disable ethernet and you won't get these DHCP messages, then see if the boot gets further.

0 Kudos

325 Views
enaud
Contributor III

I have this 

printenv:

*** Warning - bad CRC or MMC, using default environment

In: serial
Out: serial
Err: serial
Serial reinitilized!
Net: got MAC address from IIM: 00:04:9f:01:f1:d1
FEC0 [PRIME]
Hit any key to stop autoboot: 0
MX53-LOCO U-Boot > printenv
bootdelay=3
baudrate=115200
loadaddr=0x70800000
netdev=eth0
ethprime=FEC0
uboot=u-boot.bin
kernel=uImage
nfsroot=/opt/eldk/arm
bootargs_base=setenv bootargs console=ttymxc0,115200
bootargs_nfs=setenv bootargs ${bootargs} root=/dev/nfs ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp
bootcmd_net=run bootargs_base bootargs_nfs; tftpboot ${loadaddr} ${kernel}; bootm
bootargs_mmc=setenv bootargs ${bootargs} ip=dhcp root=/dev/mmcblk0p1 rootwait rw
bootcmd_mmc=run bootargs_base bootargs_mmc; mmc dev 0; mmc read ${loadaddr} 0x800 0x1800; bootm
bootcmd=run bootcmd_mmc
stdin=serial
stdout=serial
stderr=serial
ethact=FEC0

0 Kudos

325 Views
enaud
Contributor III

i followed document: i.MX53 Start Linux User's Guide cap. 7:

$ sudo dd if=u-boot.bin of=/dev/sdb bs=512 && sync && sync
$ sudo dd if=uImage of=/dev/sdb bs=512 seek = 2048 && sync && sync

$ sudo fdisk /dev/sdb

u

d

n

p

1

8192

<enter>

w

$ sudo mkfs.ext3 /dev/sdb1

$ mkdir /home/giuseppe/mountpoint

$ sudo mount /dev/sdb1 /home/giuseppe/mountpoint

/ltib/rootfs$ sudo cp -rpa [A-z]* /home/giuseppe/mountpoint

I have same error:

U-Boot 2009.08 (Mar 08 2012 - 15:16:16)

CPU: Freescale i.MX53 family 2.1V at 800 MHz
mx53 pll1: 800MHz
mx53 pll2: 400MHz
mx53 pll3: 432MHz
mx53 pll4: 455MHz
ipg clock : 66666666Hz
ipg per clock : 33333333Hz
uart clock : 66666666Hz
cspi clock : 108000000Hz
ahb clock : 133333333Hz
axi_a clock : 400000000Hz
axi_b clock : 200000000Hz
emi_slow clock: 133333333Hz
ddr clock : 400000000Hz
esdhc1 clock : 80000000Hz
esdhc2 clock : 80000000Hz
esdhc3 clock : 80000000Hz
esdhc4 clock : 80000000Hz
nfc clock : 26666666Hz
Board: MX53-LOCO 1.0 Rev. B
Boot Reason: [POR]
Boot Device: SD
I2C: ready
DRAM: 1 GB
MMC: FSL_ESDHC: 0,FSL_ESDHC: 1
*** Warning - bad CRC or MMC, using default environment

In: serial
Out: serial
Err: serial
Serial reinitilized!
Net: got MAC address from IIM: 00:04:9f:01:f1:d1
FEC0 [PRIME]
Hit any key to stop autoboot: 0
mmc0 is current device

MMC read: dev # 0, block # 2048, count 6144 ... 6144 blocks read: OK
## Booting kernel from Legacy Image at 70800000 ...
Image Name: Linux-2.6.35.3-1129-g691c08a
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3008124 Bytes = 2.9 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.35.3-1129-g691c08a (giuseppe@giuseppe-K53SV) (gcc version 4.42
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX53 LOCO Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 250880
Kernel command line: console=ttymxc0,115200 ip=dhcp root=/dev/mmcblk0p1 rootwaiw
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 480MB 512MB = 992MB total
Memory: 998220k/998220k available, 17588k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xf9e00000 - 0xffe00000 ( 96 MB)
vmalloc : 0xe0800000 - 0xf4000000 ( 312 MB)
lowmem : 0x80000000 - 0xe0000000 (1536 MB)
pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
modules : 0x7f000000 - 0x7fe00000 ( 14 MB)
.init : 0x80008000 - 0x80033000 ( 172 kB)
.text : 0x80033000 - 0x807fa000 (7964 kB)
.data : 0x80818000 - 0x80870120 ( 353 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
NR_IRQS:368
MXC GPIO hardware
MXC IRQ initialized
MXC_Early serial console at MMIO 0x53fbc000 (options '115200')
bootconsole [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 999.42 BogoMIPS (lpj=4997120)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0xe0840000
IRAM READY
CPU is i.MX53 Revision 2.1
Using SDMA I.API
MXC DMA API initialized
IMX usb wakeup probe
IMX usb wakeup probe
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Freescale USB OTG Driver loaded, $Revision: 1.55 $

****************************** NOTICE *****************************
You have seen this notice as you have enabled OTG driver for mx53 LOCO board
For mx53 loco board, the OTG function is unavailable due to hardware limitation
So, Only one usb function (device or host) can be available for certain image
Please config your kernel to disable OTG and the usb function you don't want toe
And remain the other usb function you would like to use

Below OTG configs should be removed:
CONFIG_MXC_OTG, CONFIG_USB_OTG

Choose one of below configs for host or device function
But DO NOT choose them together

OTG host config
CONFIG_USB_EHCI_ARC_OTG

OTG device config
CONFIG_USB_GADGET

usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
Advanced Linux Sound Architecture Driver Version 1.0.23.
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
mc34708 Rev 2.4 FinVer 0 detected
PMIC MC34708 ID:0x14
regulator: SW1: 650 <--> 1437 mV at 1250 mV
regulator: SW1B: 650 <--> 1437 mV at 1100 mV
regulator: SW2: 650 <--> 1437 mV at 1300 mV
regulator: SW3: 650 <--> 1425 mV at 1200 mV
regulator: SW4A: 1200 <--> 3300 mV at 1500 mV
regulator: SW4B: 1200 <--> 3300 mV at 1500 mV
regulator: SW5: 1200 <--> 1975 mV at 1800 mV
regulator: SWBST:
regulator: VPLL: 1200 <--> 1800 mV at 1800 mV
regulator: VREFDDR:
regulator: VDAC: 2500 <--> 2775 mV at 2775 mV
regulator: VUSB:
regulator: VUSB2: 2500 <--> 3000 mV at 2500 mV
regulator: VGEN1: 1200 <--> 1550 mV at 1300 mV
regulator: VGEN2: 2500 <--> 3300 mV at 2500 mV
pmic 0-0008: Loaded
Switching to clocksource mxc_timer1
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
LPMode driver module loaded
Static Power Management for Freescale i.MX5
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
DI1 is primary
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
DVFS PER driver module loaded
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 1949
alg: No test for stdrng (krng)
cryptodev: driver loaded.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
regulator: get() with no identifier
By setting, SII driver will not be enabled
By setting, LDB driver will not be enabled
mxc_ipu mxc_ipu: Channel already disabled 9
mxc_ipu mxc_ipu: Channel already uninitialized 9
IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Console: switching to colour frame buffer device 128x48
mxc_ipu mxc_ipu: Channel already disabled 7
mxc_ipu mxc_ipu: Channel already uninitialized 7
mxc_ipu mxc_ipu: Channel already disabled 10
mxc_ipu mxc_ipu: Channel already uninitialized 10
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX
console [ttymxc0] enabled, bootconsole disabled
console [ttymxc0] enabled, bootconsole disabled
mxcintuart.1: ttymxc1 at MMIO 0x53fc0000 (irq = 32) is a Freescale i.MX
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale i.MX
mxcintuart.3: ttymxc3 at MMIO 0x53ff0000 (irq = 13) is a Freescale i.MX
mxcintuart.4: ttymxc4 at MMIO 0x63f90000 (irq = 86) is a Freescale i.MX
loop: module loaded
MXC MTD nand Driver 3.0
i.MX GPMI NFC
vcan: Virtual CAN interface driver
Freescale FlexCAN Driver
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 18, io base 0x53f80000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adaptes
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
MXC keypad loaded
input: mxc_power_key as /devices/virtual/input/input1
PMIC powerkey probe
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5
p1003_fwv33 2-0041: couldn't read panel infomation.
p1003_fwv33: probe of 2-0041 failed with error -5
DA9052 TSI Device Driver, v1.0
mxc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0
pmic rtc probe start
pmic_rtc mc34708_rtc.1: rtc core: registered mc34708_rtc as rtc1
pmic rtc probe succeed
i2c /dev entries driver
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: Registered device video0
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
APM Battery Driver
check mma8450 chip ID
mma8450 0-001c: build time Mar 8 2012 15:24:08
input: mma8450 as /devices/virtual/input/input2
add mma8450 i2c driver
MXC WatchDog Driver 2.0
MXC Watchdog # 0 Timer: initial timeout 60 sec
Bluetooth: Virtual HCI driver ver 1.3
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCIATH3K protocol initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
PMIC ADC start probe
VPU initialized
mxc_asrc registered
gpu mmu enabled
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 0 irq 1 INTERNAL DMA
mxsdhci: MXC SDHCI Controller Driver.
mmc1: SDHCI detect irq 203 irq 3 INTERNAL DMA
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Cirrus Logic CS42888 ALSA SoC Codec Driver
sgtl5000-i2c 1-000a: SGTL5000 revision 17
mxc_spdif mxc_spdif.0: MXC SPDIF Audio Transmitter
No device for codec mxc spdif
No device for DAI mxc spdif
No device for DAI imx-ssi-1-0
No device for DAI imx-ssi-1-1
No device for DAI imx-ssi-2-0
No device for DAI imx-ssi-2-1
No device for DAI imx-spdif-dai
DMA Sound Buffer Allocated: Playback UseIram=1 ext_ram=0 buf->addr=f8016000 buf6
DMA Sound Buffer Allocated: Capture UseIram=1 ext_ram=1 buf->addr=cf358000 buf6
asoc: SGTL5000 <-> imx-ssi-2-0 mapping ok
usb 2-1: new low speed USB device using fsl-ehci and address 2
mmc0: new high speed SDHC card at address 0002
mmcblk0: mmc0:0002 00000 3.70 GiB
mmcblk0: p1
DMA Sound Buffer Allocated: Playback UseIram=1 ext_ram=1 buf->addr=cf440000 buf6
asoc: mxc spdif <-> imx-spdif-dai mapping ok
ALSA device list:
#0: imx-3stack (SGTL5000)
#1: imx-3stack-spdif (mxc spdif)
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
input: mxc_ts as /devices/virtual/input/input3
mxc input touchscreen loaded
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
input: HID 046a:0021 as /devices/platform/fsl-ehci.1/usb2/2-1/2-1:1.0/input/inp4
generic-usb 0003:046A:0021.0001: input: USB HID v1.11 Keyboard [HID 046a:0021] 0
input: HID 046a:0021 as /devices/platform/fsl-ehci.1/usb2/2-1/2-1:1.1/input/inp5
generic-usb 0003:046A:0021.0002: input: USB HID v1.11 Device [HID 046a:0021] on1
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
Sending DHCP requests .
.....timed out! 

IP-Config: Reopening network devices...
eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=0:00, irq=-1)
Sending DHCP requests .

0 Kudos

325 Views
KrishnaPavan
Contributor II

That particular link has an example for i.MX53 EVK, You have to check in your user_guide and find respective variables.

I gave it just as an example to YOUR question " where i must set env.variables? and what is?"

enaud said:

what is EVK switchs? This is for IMX51 i have imx53

0 Kudos

325 Views
enaud
Contributor III

but is normal that it not load kernel?

0 Kudos

325 Views
StevieRG
Contributor II

You have no switches on the QSB, don't worry about that part of the document. You might benefit from looking at the start of this discussion - there is a lot of discussion about envorimnent variables and how to set them for a basic QSB.
 
enaud said:

what is EVK switchs? This is for IMX51 i have imx53

0 Kudos

325 Views
enaud
Contributor III

what is EVK switchs? This is for IMX51 i have imx53

0 Kudos

325 Views
StevieRG
Contributor II

It looks to me like the environment variables are not set at all. Can I suggest you look at the basic settings for env variables being talked about at the start of this discussion..

0 Kudos

325 Views
KrishnaPavan
Contributor II
0 Kudos

325 Views
KrishnaPavan
Contributor II

Do you have a user guide?

0 Kudos