This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Arago Linux in Omap-l138 doesn't boot

Other Parts Discussed in Thread: OMAP-L138, DA8XX, PMP

Hi everyone,

I have a problem with the board omap-l138. Since a few days ago, when i booted the board following the Quick Start Guide, Arago Linux started without problems.

This morning Arago Linux didn't boot. I try to copy the boot messages here:

NAND:  512 MiB
MMC:   davinci: 0
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock : 456000000 Hz
DDR Clock : 150000000 Hz
Net:   Ethernet PHY: GENERIC @ 0x07
DaVinci-EMAC
Hit any key to stop autoboot:  0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

2040348 bytes read
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-3.1.10
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2040284 Bytes = 1.9 MiB
   Load Address: c0008000
   Entry Point:  c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.1.10 (root@VPC-U1104) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #7 PREEMPT Fri May 11 11:15:57 CDT 2012
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: AM18x/OMAP-L138 LCDK
Memory policy: ECC disabled, Data cache writeback
DaVinci da850/omap-l138/am18x variant 0x1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 125856k/125856k available, 5216k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xff000000 - 0xffe00000   (  14 MB)
    vmalloc : 0xc8800000 - 0xfea00000   ( 866 MB)
    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc0396218   (3641 kB)
      .init : 0xc0397000 - 0xc03ba000   ( 140 kB)
      .data : 0xc03ba000 - 0xc03db160   ( 133 kB)
       .bss : 0xc03db184 - 0xc03f4c1c   ( 103 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 227.32 BogoMIPS (lpj=1136640)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 144 gpio irqs
NET: Registered protocol family 16
EMAC: MII PHY configured
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
Switching to clocksource timer0_1
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
msgmni has been set to 245
io scheduler noop registered (default)
da8xx_lcdc da8xx_lcdc.0: GLCD: Found VGA_Monitor panel
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a 16550A
serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a 16550A
serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a 16550A
console [ttyS2] enabled
brd: module loaded
ahci ahci: forcing PORTS_IMPL to 0x1
ahci ahci: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x01e18000-0x01e19fff] port 0x100 irq 67
davinci_mdio davinci_mdio.0: davinci mdio revision 1.5
davinci_mdio davinci_mdio.0: detected phy mask ffffff7f
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[7]: device 0:07, driver unknown
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 1
Waiting for USB PHY clock good...
ohci ohci.0: irq 59, io mem 0x01e25000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DA8xx OHCI
usb usb1: Manufacturer: Linux 3.1.10 ohci_hcd
usb usb1: SerialNumber: ohci.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: RTC power up reset detected
i2c /dev entries driver
davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
asoc: tlv320aic3x-hifi <-> davinci-mcasp.0 mapping ok
ALSA device list:
  #0: DA850/OMAP-L138 EVM
TCP cubic registered
NET: Registered protocol family 17
davinci_emac davinci_emac.1: using random MAC addr: 2e:b5:0e:18:8d:eb
mmc0: new SDHC card at address 1234
console [netcon0] enabled
netconsole: network logging started
mmcblk0: mmc0:1234 SA04G 3.63 GiB
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
 mmcblk0: p1 p2 p3 < p5 >
ata1: SATA link down (SStatus 0 SControl 300)
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
kjournald starting.  Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 140K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udevd (946): /proc/946/oom_adj is deprecated, please use /proc/946/oom_score_adj instead.
Remounting root file system...
Caching udev devnodes
Populating dev cacheFAT-fs (mmcblk0p3): invalid media value (0x1f)
FAT-fs (mmcblk0p3): Can't find a valid FAT filesystem
mv: cannot rename '/tmp/devices': No such file or directory
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
Configuring network interfaces... davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:07, id=7c0f1)
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0      no wireless extensions.

udhcpc (v1.13.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
done.
Setting up IP spoofing protection: rp_filter.
Tue Apr 10 18:57:00 UTC 2012

HERE the boot process stops indefinitely

 


Couls anyone help me? I'm really stuck!

  • Hello,

    This question is out of the scope of this forum. Could you please post it in the dedicated OMAP-L13x forum: http://e2e.ti.com/support/dsp/omap_applications_processors/f/42.aspx ?

    I am no expert on OMAP-L13x devices (since they are out of the scope of OMAP Application Processors Forum), but here are a couple of suggestions:
     
      1. This seems like an error in the file system. Have you changed anything in the FS or the linux kernel?

      2. For some omap application devices there is the following limitation/issue: OMAPS00305059: Omap5 is not getting booted if the ethernet cable is not connected. 

      So you can try changing ip=dhcp in your bootargs & connect ethernet cable to the port. Maybe there is some similar limitation of OMAP-L138 SDK (I am not familiar with it).

    Best Regards,

    Yordan

  • Hi Yordan thank you for your answer.


    I'm new with this board and i'm looking to learn something. The linux kernel was read into a micro sd card: the only think that i think is that the file could be corrupted... Now i'll try to post in the relative section.

  • Hi Robert,

    Indeed, posting in the OMAP-L13x Forum would be the best way to work out your issue.

    Just FYI, the simplest way (but it might be a bit time consuming) to verify that files on the sdcard are (or aren't) corrupted is to reformat your card and copy the relevant bootloader & kernel images, and the filesystem files.  You should have a sequence that describes the process of reformatting and copying files to the sdcard on the relevant SDK wiki page or developers guide document.

    Best Regards,

    Yordan