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.

Booting issues on DM368



 

 

HI,

 

i am working on DM368-IPNC reference design but i am facing some issues:

 

 

1.I have made by own uimage and cramfs image but i am not able to boot the board using my images.

The board boots fine when uimage and cramfs that come with the package are installed.

The boot process is getting stuck before the login prompt .

Also when i am trying to mount the filesystem on the board using nfs using the userguide section 2.4.4

2.4.4 Booting from Flash Using NFS File System

i am getting the following output.

IP-Config: No network devices available.                                       
Looking up port of RPC 100003/2 on 10.17.8.125                                 
portmap: RPC call returned error 101                                           
Root-NFS: Unable to get nfsd port number from server, using default            
Looking up port of RPC 100005/1 on 10.17.8.125                                 
portmap: RPC call returned error 101                                           
Root-NFS: Unable to get mountd port number from server, using default          
mount: RPC call returned error 101                                             
Root-NFS: Server returned error -101 while mounting /home/mayank/DM36x/ipnc/tars
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                                    
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) 

 

It is highly unfortunate that steps given in user guide are totally incomplete and they don't

discuss the issues which developers can face while implementing the steps.

Even after trying for several days i am not able to install my own uimage and cramfs imagems on DM368

on DM368 board and boot the board properly and run the algorithms.

If anyone has faced similar problem in the past he can help me.

 

Is there any other method(other than building own cramfs and installing it on the board and mounting filesystem through nfs)

to execute any of the code or any algorithms on DM368 Board.

Thanks and Regards,

Mayank

  • Mayank,

    Could you please post your u-boot environment variables (i.e. output of printenv command)?

    Could you add 'earlyprintk' to your bootargs and then post the complete boot log?

    Thanks,
    Carlos.

     

     

  • Hi Mayank,

    >>>IP-Config: No network devices available.

    In your boot log, i can see that there is no network interface identified. This is the reason why NFS is not mounting. I think the user guide refers to use kernel defconfig which is in debug mode (defconfig_dbg). In the standard uImage that is provided in IPNC Ref Design, we disable the network interface during boot up so that we can boot faster. We enable the network interface in the application startup.

    In debug mode of the kernel defconfig, we keep the network interface enabled by default.

    For your question on the right environment for testing your algorithms, the best option is to have the NFS system mounted on the target. This is the fastest way, you can get your algorithms validated.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  •  

    Hi,

     

    My printenv is as follows:

    bootdelay=4
    baudrate=115200
    setboot=setenv bootargs $(bootargs)
    bootamd=nboot 0x80700000 0 0x500000;bootm
    bootfile=""
    ethaddr=00:0C:0C:A0:FF:FA
    eth=00:0C:0C:A0:07:Ea
    rootpath=/home/mayank/DM36x/ipnc/target/filesys
    bootcmd=nboot 0x80700000 0 0x500000;bootm
    nfshost=10.17.8.125
    filesize=1C76B8
    fileaddr=80700000
    ipaddr=10.17.8.131
    serverip=10.17.8.125
    bootargs=console=ttyS1,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.17.8.125:/home/mayank/DM36x/ipnc/target/filesys,nolock mem=48M
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 1.3.4 (Dec  9 2010 - 17:44:14) DM368-IPNC-1.0.1

    Environment size: 590/131068 bytes

    and i have build new uimage in debug mode:

    tftpboot 0x80700000 uImage_ipnc_DM368_IMX036
    nand erase 0x500000 0x200000
    nand write 0x80700000 0x500000 0x200000
    setenv bootargs'console=ttyS1,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.1.21:/home/mayank/DM36x/ipnc/target/filesys,nolock mem=48M ip=dhcp'
    setenv eth '00:0C:0C:A0:07:Ea'

    and after doing saveenv mode and booting the board i am getting the following output:

    Kernel sysnc error:

    I2C:   ready
    DRAM:  128 MB
    NAND:  NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    Bad block table found at page 65472, version 0x01
    Bad block table found at page 65408, version 0x01
    128 MiB
    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock :- 432MHz
    DDR Clock :- 340MHz
    Ethernet PHY: GENERIC @ 0x01
    Hit any key to stop autoboot:  0

    Loading from NAND 128MiB 3,3V 8-bit, offset 0x500000
       Image Name:   Linux-2.6.18_pro500-davinci_IPNC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1818408 Bytes =  1.7 MB
       Load Address: 80008000
       Entry Point:  80008000
    ## Booting kernel from Legacy Image at 80700000 ...
       Image Name:   Linux-2.6.18_pro500-davinci_IPNC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1818408 Bytes =  1.7 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Linux version 2.6.18_pro500-davinci_IPNC_DM368_2.6.0 (root@localhost.localdomain) (gcc version 4.2.0 (MontaVista 4.2.0-16.0.32.0801914 2008-08-30)) #1 PREEM1
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    Machine: DaVinci DM368 IPNC
    Memory policy: ECC disabled, Data cache writeback
    DaVinci DM0365 variant 0x8
    PLL0: fixedrate: 24000000, commonrate: 170000000, vpssrate: 340000000
    PLL0: vencrate_sd: 75555555, ddrrate: 340000000 mmcsdrate: 48571428
    PLL1: armrate: 432000000, voicerate: 20571428, vencrate_hd: 27000000
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Built 1 zonelists.  Total pages: 12288
    Kernel command line: console=ttyS1,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=10.17.8.125:/home/mayank/DM36x/ipnc/target/filesys,nolock mem=48M
    PID hash table entries: 256 (order: 8, 1024 bytes)
    Clock event device timer0_0 configured with caps set: 07
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
    Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
    Memory: 48MB = 48MB total
    Memory: 44672KB available (3117K code, 647K data, 176K init)
    Security Framework v1.0.0 initialized
    Capability LSM initialized
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    NET: Registered protocol family 16
    DaVinci: 104 gpio irqs
    MUX: initialized GPIO20
    MUX: initialized I2C_SCL
    Generic PHY: Registered new driver
    ch0 default output "COMPOSITE", mode "NTSC"
    VPBE Encoder Initialized
    SCSI subsystem initialized
    NET: Registered protocol family 2
    IP route cache hash table entries: 512 (order: -1, 2048 bytes)
    TCP established hash table entries: 2048 (order: 1, 8192 bytes)
    TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
    TCP: Hash tables configured (established 2048 bind 1024)
    TCP reno registered

     ***davinci_spi_board_init()!<6>
     ***davinci_spi_board_init_End(0)!<5>VFS: Disk quotas dquot_6.5.1
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    squashfs: version 3.1 (2006/08/19) Phillip Lougher
    JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
    yaffs Jun 30 2011 15:45:25 Installing.
    SGI XFS with no debug enabled
    Initializing Cryptographic API
    io scheduler noop registered
    io scheduler anticipatory registered (default)
    LTT : ltt-facilities init
    LTT : ltt-facility-core init in kernel
    DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec
    Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO map 0x1c20000 mem 0xfbc20000 (irq = 40) is a 16550A
    serial8250.0: ttyS1 at MMIO map 0x1d06000 mem 0xfbd06000 (irq = 41) is a 16550A
    RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
    Linux video capture interface: v2.00
    Trying to register davinci display video device.
    layer=c0545a00,layer->video_dev=c0545b60
    Trying to register davinci display video device.
    layer=c0545800,layer->video_dev=c0545960
    davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
    i2c /dev entries driver
    nand_davinci nand_davinci.0: Using 4-bit hardware ECC
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
    Creating 7 MTD partitions on "nand_davinci.0":
    0x00000000-0x00300000 : "bootloader"
    0x00300000-0x00500000 : "params"
    0x00500000-0x00700000 : "kernel"
    0x00700000-0x02700000 : "filesystem"
    0x02700000-0x02900000 : "data1"
    0x02900000-0x02d00000 : "Calibration"
    0x02d00000-0x08000000 : "data2"
    nand_davinci nand_davinci.0: hardware revision: 2.3
    MUX: initialized SPI0_SCLK
    MUX: initialized SPI0_SDO)
    dm_spi.0: davinci SPI Controller driver at 0xc3866000 (irq = 42) use_dma=0
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc intf: proc
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc intf: dev (254:0)
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc core: registered rtc_davinci_dm365 as rtc0
    Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
    ASoC version 0.13.1
    CQ0093 Voice Codec 0.1
    asoc: cq93vc <-> davinci-vcif mapping ok
    ALSA device list:
      #0: On-chip voice codec (cq93vc)
    IPv4 over IPv4 tunneling driver
    TCP bic registered
    NET: Registered protocol family 1
    NET: Registered protocol family 17
    Time: timer0_1 clocksource has been installed.
    Clock event device timer0_0 configured with caps set: 08
    Switched to high resolution mode on CPU 0
    rtc_davinci_dm365 rtc_davinci_dm365.0: setting the system clock to 2000-01-01 06:25:50 (946707950)
    IP-Config: No network devices available.
    Looking up port of RPC 100003/2 on 10.17.8.125
    portmap: RPC call returned error 101
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on 10.17.8.125
    portmap: RPC call returned error 101
    Root-NFS: Unable to get mountd port number from server, using default
    mount: RPC call returned error 101
    Root-NFS: Server returned error -101 while mounting /home/mayank/DM36x/ipnc/target/filesys
    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
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

     

    Please help me to debug this issue:

     

    Thanks and REgards,

    Mayank