• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 97 subscribers
  • Views 974 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP-l138 experimenter - problem with booting linux

Jarosław Żdan
Prodigy 80 points
Other Parts Discussed in Thread: OMAP-L138, DA8XX, PMP

I am new to dsp programming in particular omapl-l138.  went through QSG and read a lot of articles on the OMAP-l138 from e2e.ti and processors.wiki.ti .In QSG  there is written that the U-Boot bootloader, Linux kernel, and file system are burned to flash memory (SPI1) during manufacture. There is also written that if I set properly S7[5:8] dipswitches and connect board with my PC using null-modem serial cable, after pressing reset button i should see u-boot command line in my terminal emulator and if I don't push any other button, after 3 seconds should start booting linux kernel.  I did everything like was written in QSG, but after 3 seconds after u-boot command line(I not press any button) linux kernel won't start. What em i doing wrong? Here is printscreen of my terminal emulator; 

 

  • 0
    TI__Mastermind 27585 points

    It looks like your boot images got corrupted. You should go through and reflash the UBL and UBOOT on the SPI flash according to the instructions on the wiki.

    The best solution for you would be to download the SDK4.0 software package. This includes handy scripts which will automate the process of getting Linux booted.

    Jeff

  • 0 in reply to jc-ti
    Prodigy 80 points

    Thanks for reply.

    I reflash SPI flash and for now everything work.

  • 0 in reply to Jarosław Żdan
    Prodigy 80 points

    Now i have another problem. I try boot linux using nfs. I have installed DVSDK 4 and setup nfs using  script witch i find in bin directory of DVSDK 4 root directory. It seems that nfs works fine - server starts without errors(only when i try to re-start server, i need to use sudo privileges, otherwise server fail to starts ), but when linux is booting in console appear error like this;

    U-Boot > boot


    Using device
    TFTP from server 192.168.200.2; our IP address is 192.168.200.1
    Filename 'uImage-2.6.33-rc4'.
    Load address: 0xc0700000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #######################
    done
    Bytes transferred = 2113796 (204104 hex)
    ## Booting kernel from Legacy Image at c0700000 ...
    Image Name: Arago/2.6.32+2.6.33-rc4-psp03.20
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2113732 Bytes = 2 MB
    Load Address: c0008000
    Entry Point: c0008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    Linux version 2.6.33-rc4 (sdk@nemo) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMP
    T Thu Jan 13 01:09:44 CST 2011
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    CPU: VIVT data cache, VIVT instruction cache
    Machine: DaVinci DA850/OMAP-L138/AM18xx EVM
    Memory policy: ECC disabled, Data cache writeback
    DaVinci da850/omap-l138 variant 0x0
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
    Kernel command line: console=ttyS2,115200n8 noinitrd rw ip=off root=/dev/nfs nfsroot=192.168.200.
    2:/home/jarek/targetfs,nolock mem=32M
    PID hash table entries: 128 (order: -3, 512 bytes)
    Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
    Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
    Memory: 32MB = 32MB total
    Memory: 27972KB available (4012K code, 315K data, 148K init, 0K highmem)
    SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    Hierarchical RCU implementation.
    NR_IRQS:245
    Console: colour dummy device 80x30
    Calibrating delay loop... 149.50 BogoMIPS (lpj=747520)
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    DaVinci: 144 gpio irqs
    regulator: core version 0.5
    NET: Registered protocol family 16
    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
    regulator: VDCDC1: 3200 <--> 3300 mV at 3300 mV
    regulator: VDCDC2: 1750 <--> 3300 mV at 3300 mV
    regulator: VDCDC3: 950 <--> 1375 mV at 1200 mV
    regulator: LDO1: 1800 mV
    regulator: LDO2: 1150 <--> 1300 mV at 1200 mV
    pca953x 1-0020: failed reading register
    i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)
    Switching to clocksource timer0_1
    musb_hdrc: version 6.0, cppi4.1-dma, host, debug=0
    Waiting for USB PHY clock good...
    musb_hdrc: USB Host mode controller at fee00000 using DMA, IRQ 58
    musb_hdrc musb_hdrc: MUSB HDRC host driver
    musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 1024 (order: 1, 8192 bytes)
    TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
    TCP: Hash tables configured (established 1024 bind 1024)
    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 udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    EMAC: MII PHY configured, RMII PHY will not be functional
    JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
    msgmni has been set to 54
    io scheduler noop registered (default)
    da8xx_lcdc da8xx_lcdc.0: GLCD: Found Sharp_LK043T1DG01 panel
    Console: switching to colour frame buffer device 60x34
    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 SATA mode
    ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc
    scsi0 : ahci
    ata1: SATA max UDMA/133 irq 67
    spi_davinci spi_davinci.1: DaVinci SPI driver in EDMA mode
    Using RX channel = 18 , TX channel = 19 and event queue = 1
    m25p80 spi1.0: m25p64 (8192 Kbytes)
    Creating 4 MTD partitions on "m25p80":
    0x000000000000-0x000000040000 : "U-Boot"
    0x000000040000-0x000000050000 : "U-Boot Environment"
    0x000000050000-0x0000007f0000 : "Linux"
    0x0000007f0000-0x000000800000 : "MAC Address"
    Read MAC addr from EEPROM: 00:08:ee:03:5a:ed
    spi_davinci spi_davinci.1: Controller at 0xfef0e000
    console [netcon0] enabled
    netconsole: network logging started
    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 2
    ohci ohci.0: irq 59, io mem 0x01e25000
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    input: TPS6507x Touchscreen as /devices/platform/i2c-gpio.1/i2c-1/1-0048/input/input0
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    omap_rtc: RTC power up reset detected
    omap_rtc: already running
    i2c /dev entries driver
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v0.1.0)
    watchdog watchdog: heartbeat 60 sec
    cpuidle: using governor ladder
    cpuidle: using governor menu
    davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    Advanced Linux Sound Architecture Driver Version 1.0.21.
    usbcore: registered new interface driver snd-usb-audio
    No device for DAI tlv320aic3x
    asoc: tlv320aic3x <-> davinci-i2s mapping ok
    ALSA device list:
    #0: DA850/OMAP-L138 EVM (tlv320aic3x)
    TCP cubic registered
    NET: Registered protocol family 17
    Clocks: disable unused i2c1
    Clocks: disable unused emac
    Clocks: disable unused aemif
    Clocks: disable unused spi0
    Clocks: disable unused mcbsp0
    Clocks: disable unused mcbsp1
    Clocks: disable unused vpif
    ata1: SATA link down (SStatus 0 SControl 300)
    regulator_init_complete: incomplete constraints, leaving LDO2 on
    regulator_init_complete: incomplete constraints, leaving LDO1 on
    regulator_init_complete: incomplete constraints, leaving VDCDC3 on
    regulator_init_complete: incomplete constraints, leaving VDCDC2 on
    regulator_init_complete: incomplete constraints, leaving VDCDC1 on
    emac-mii: probed
    omap_rtc omap_rtc: setting system clock to 2000-01-01 01:13:19 UTC (946689199)
    Looking up port of RPC 100003/2 on 192.168.200.2
    rpcbind: server 192.168.200.2 not responding, timed out
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on 192.168.200.2
    rpcbind: server 192.168.200.2 not responding, timed out
    Root-NFS: Unable to get mountd port number from server, using default
    Root-NFS: Server returned error -101 while mounting /home/jarek/targetfs
    VFS: Unable to mount root fs via NFS, trying floppy.
    VFS: Cannot open root device "nfs" or unknown-block(2,0)
    Please append a correct "root=" boot option; here are the available partitions:
    1f00 256 mtdblock0 (driver?)
    1f01 64 mtdblock1 (driver?)
    1f02 7808 mtdblock2 (driver?)
    1f03 64 mtdblock3 (driver?)
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
    Backtrace:
    [<c0031730>] (dump_backtrace+0x0/0x114) from [<c0320420>] (dump_stack+0x18/0x1c)
    r7:00008000 r6:c1c13000 r5:c0025a08 r4:c0446f38
    [<c0320408>] (dump_stack+0x0/0x1c) from [<c0320488>] (panic+0x64/0x13c)
    [<c0320424>] (panic+0x0/0x13c) from [<c0008fec>] (mount_block_root+0x1e0/0x220)
    r3:00000001 r2:00000001 r1:c1c23f60 r0:c03b5856
    [<c0008e0c>] (mount_block_root+0x0/0x220) from [<c00090f0>] (mount_root+0xc4/0xfc)
    r8:00000000 r7:00000000 r6:00000000 r5:00000000 r4:00200000
    [<c000902c>] (mount_root+0x0/0xfc) from [<c0009298>] (prepare_namespace+0x170/0x1c8)
    r5:c0025a08 r4:c0446a20
    [<c0009128>] (prepare_namespace+0x0/0x1c8) from [<c00084c8>] (kernel_init+0xf0/0x12c)
    r5:00000000 r4:c04467e0
    [<c00083d8>] (kernel_init+0x0/0x12c) from [<c0045424>] (do_exit+0x0/0x6b4)
    r5:00000000 r4:00000000

    I see that there is trouble with nfs mounting, but now i have no idea how resolve this problem.

    Any suggestions?

  • 0 in reply to Jarosław Żdan
    Prodigy 80 points

    I sloved my problem. I have bad bootargs. I rewrite them from UserGuide, where they look like this; setenv
    bootargs console=ttyS2,115200n8 nfsroot=${nfshost}:${rootpath},nolock mem=32M,. i have static ip's on OMAP-L138 and on server, but I do not know why i set ip=off insteda ip=$ipaddr. When i set ip=$ipaddr linux boot with nfs without problems.