• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 1279 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.

Where can I find the ramdisk.gz when I design my DM8168 board.

zhu ted
Prodigy 160 points
Other Parts Discussed in Thread: PMP, TVP5158

Now , I get some problems when I try to boot my DM8168 board using jffs2 file system.

then I want to boot it from Ramdisk. But I found that there  is no ramdisk.gz file in the EZSDK  .

Does any one know where is the ramdisk.gz or is there any way to build one ? what tool do I need?

thanks.

ramdisk.gz file is noted here.

http://processors.wiki.ti.com/index.php/DM816x_AM389x_PSP_User_Guide#Booting_Linux_Kernel

TI8168_EVM# setenv autoload no
TI8168_EVM# dhcp
TI8168_EVM# setenv serverip <Server IP Address>
TI8168_EVM# tftp 0x81000000 uImage
TI8168_EVM# tftp 0x82000000 ramdisk.gz
TI8168_EVM# setenv bootargs 'mem=200M console=ttyO2,115200n8 root=/dev/ram0 initrd=0x82000000,40M ramdisk_size=45000 ip=dhcp'
TI8168_EVM# bootm 0x81000000
  • 0
    Genius 3120 points

    Hi Zhu,

    You can prepare ramdisk following this wiki page: http://processors.wiki.ti.com/index.php/Creating_a_RAMDISK

    Also, you can find the prebuild filesystem in "<ezsdk installation path>/filesystem/ezsdk-dm816x-evm-rootfs.tar.gz" which you will need to prepare ramdisk.

    Regards,

    Krunal

  • 0 in reply to Krunal Patil
    Prodigy 160 points

    Hi Krunal,

    Thanks for your help.Now I'm trying to boot with the ramdisk file system.But i still got some problems.

    The ramdisk still did not work.Here's the error print.

                                                                                                 ted zhu

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

    ## Booting kernel from Legacy Image at 81000000 ...
       Image Name:   Linux-2.6.37
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2455812 Bytes = 2.3 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    Linux version 2.6.37 (user@ubuntu.workshop.net) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #2 Tue Jan 10 22:34:37 PST 2012
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: ti8168_dvr
    bootconsole [earlycon0] enabled
    reserved size = 52428800 at 0x0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is TI8168 2.0
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 52224
    Kernel command line: mem=256M console=ttyO2,115200n8 root=/dev/ram0 rw initrd=0x82000000,50M earlyprintk
    PID hash table entries: 1024 (order: 0, 4096 bytes)
    Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
    Memory: 206MB = 206MB total
    Memory: 152188k/152188k available, 109956k reserved, 0K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
        vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)
        lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
          .init : 0xc0008000 - 0xc003a000   ( 200 kB)
          .text : 0xc003a000 - 0xc04a5000   (4524 kB)
          .data : 0xc04a6000 - 0xc04ea5c0   ( 274 kB)
    SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    NR_IRQS:375
    IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    Total of 128 interrupts on 1 active controller
    GPMC revision 6.0
    Trying to install interrupt handler for IRQ368
    Trying to install interrupt handler for IRQ369
    Trying to install interrupt handler for IRQ370
    Trying to install interrupt handler for IRQ371
    Trying to install interrupt handler for IRQ372
    Trying to install interrupt handler for IRQ373
    Trying to install interrupt handler for IRQ374
    Trying to install type control for IRQ375
    Trying to set irq flags for IRQ375
    OMAP clockevent source: GPTIMER1 at 27000000 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
    pid_max: default: 32768 minimum: 301
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    devtmpfs: initialized
    omap_voltage_early_init: voltage driver support not added
    regulator: core version 0.5
    regulator: dummy:
    NET: Registered protocol family 16
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    omap_mux_init: Add partition: #1: core, flags: 0
    _omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
    _omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
    3-wired eeprom init done. (H/W ver:00)
    registered ti816x_vpss device
    registered TI816x on-chip HDMI device
    registered ti816x_sr device
    registered ti81xx_vidout device
    pm_dbg_init: only OMAP3 supported
    Registered ti81xx_fb device
    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
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    pmbus 1-0038: no platform data supplied
    pmbus: probe of 1-0038 failed with error -5
    omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz
    Advanced Linux Sound Architecture Driver Version 1.0.23.
    Switching to clocksource gp timer
    musb-hdrc: version 6.0, host, debug=0
    musb-hdrc musb-hdrc.0: dma type: dma-cppi41
    musb-hdrc musb-hdrc.0: MUSB HDRC host driver
    musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb1: Product: MUSB HDRC host driver
    usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
    usb usb1: SerialNumber: musb-hdrc.0
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    musb-hdrc musb-hdrc.0: USB Host mode controller at d081e000 using DMA, IRQ 18
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    musb-hdrc musb-hdrc.1: MUSB HDRC host driver
    musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
    usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb2: Product: MUSB HDRC host driver
    usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
    usb usb2: SerialNumber: musb-hdrc.1
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    musb-hdrc musb-hdrc.1: USB Host mode controller at d0828800 using DMA, IRQ 19
    NET: Registered protocol family 2
    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
    TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
    TCP: Hash tables configured (established 8192 bind 8192)
    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.
    Trying to unpack rootfs image as initramfs...
    rootfs image is not initramfs (no cpio magic); looks like an initrd
    Freeing initrd memory: 51200K
    NetWinder Floating Point Emulator V0.97 (double precision)
    PMU: registered new PMU device of type 0
    omap-iommu omap-iommu.0: ducati registered
    omap-iommu omap-iommu.1: sys registered
    JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
    msgmni has been set to 397
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
    omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
    omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
    console [ttyO2] enabled, bootconsole disabled
    console [ttyO2] enabled, bootconsole disabled
    brd: module loaded
    loop: module loaded
    ahci ahci.0: forcing PORTS_IMPL to 0x3
    ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
    scsi0 : ahci_platform
    scsi1 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16
    omap2-nand driver initializing
    ONFI flash detected
    ONFI param page 0 valid
    NAND device: Maf ID: 0x2c, Chip ID: 0x38 (Micron, (null))
     erasesize: 0x80000, writesize: 4096, oobsize: 224
    Creating 5 MTD partitions on "omap2-nand.0":
    0x000000000000-0x000000200000 : "U-Boot"
    0x000000200000-0x000000300000 : "U-Boot Env"
    0x000000300000-0x000000800000 : "Kernel"
    0x000000800000-0x00000d100000 : "File System"
    0x00000d100000-0x000040000000 : "Reserved"
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    davinci_mdio davinci_mdio.0: detected phy mask fffffffd
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    mice: PS/2 mouse device common for all mice
    i2c /dev entries driver
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v1.0.0)
    OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    usbcore: registered new interface driver snd-usb-audio
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
    asoc: tvp5158-hifi <-> davinci-mcasp.0 mapping ok
    ALSA device list:
      #0: TI8168 DVR (AIC3x)
      #1: TI81XX DVR (TVP5158)
    TCP cubic registered
    NET: Registered protocol family 10
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    omap_voltage_late_init: Voltage driver support not added
    Power Management for TI81XX.
    smartreflex smartreflex: Driver initialized
    davinci_emac_probe: using random MAC addr: 0a:95:c0:08:cd:d8
    davinci_emac_probe: using random MAC addr: ca:61:e2:d0:91:cc
    ata2: SATA link down (SStatus 0 SControl 300)
    ata1: SATA link down (SStatus 0 SControl 300)
    RAMDISK: gzip image found at block 0
    RAMDISK: incomplete write (25324 != 32768)
    write error
    VFS: Mounted root (ext2 filesystem) on device 1:0.
    devtmpfs: mounted
    Freeing init memory: 200K
    INIT: version 2.86 booting
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: Entering runlevel: 5
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/etc/init.d/rc"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    attempt to access beyond end of device
    ram0: rw=0, want=65544, limit=65536
    EXT2-fs (ram0): error: ext2_get_inode: unable to read inode block - inode=7329, block=32771
    INIT: cannot execute "/sbin/getty"
    INIT: Id "S" respawning too fast: disabled for 5 minutes
    INIT: no more processes left in this runlevel

  • 0 in reply to zhu ted
    TI__Expert 5685 points

    Hi,

    Probably exceeding the ramdisk size.

    Can you try with appending "ramdisk_size=<size in KB>" (without quotes) to the bootargs? Replace size in KB with as value as large to accommodate ramdisk image (uncompressed) size in KB. 

       Hemant