• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 100 subscribers
  • Views 1899 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.

DM368 DVR-RDK board- Bootup issue

srinivasa reddy
Prodigy 60 points
Other Parts Discussed in Thread: THS7303

This email is regarding an issue that we are facing while booting up DM368 DVR,

We would like to seek technical support to bring up the board.

 

 

Kindly support us.

 

Warning: unable to open an initial console.

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

 

Setting the U-boot arguments as this:

 

set ipaddr 192.168.1.201

set serverip 192.168.1.200

set nfshost 192.168.1.200

set gatewayip 192.168.1.1

set netmask 255.255.255.0

set commonargs console=ttyS0,115200n8 mem=60M ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):::off

video=davincifb:osd0=720x576x8,2500K:osd1=off:vid0=off:vid1=off

davinci_enc_mngr.ch0_mode=$(videostd)

setenv bootargs $(commonargs) root=/dev/mtdblock3 rw rootfstype=yaffs2 set bootcmd 'nboot 0x80700000 0 0x680000;bootm'

saveenv

 

 

Full Boot Log As below:

 

Loading from NAND 128MiB 3,3V 8-bit, offset 0x680000

   Image Name:   Linux-2.6.18_pro500-davinci_evm-

   Created:      2010-09-01  10:15:52 UTC

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1998000 Bytes =  1.9 MB

   Load Address: 80008000

   Entry Point:  80008000

## Booting kernel from Legacy Image at 80700000 ...

   Image Name:   Linux-2.6.18_pro500-davinci_evm-

   Created:      2010-09-01  10:15:52 UTC

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    1998000 Bytes =  1.9 MB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

OK

 

Starting kernel ...

 

Uncompressing Linux..............................................................................

............................................................................. done, booting the k ernel.

Linux version 2.6.18_pro500-davinci_evm-arm_v5t_le (root@localhost.localdomain) (gcc version 4.2.

0 (MontaVista 4.2.0-16.0.32.0801914 2008-08-30)) #1 PREEMPT Wed Sep 1 19:04:48 KST 2010

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

Machine: DaVinci DM365 DVR

Memory policy: ECC disabled, Data cache writeback DaVinci DM0365 variant 0x8

PLL0: fixedrate: 24000000, commonrate: 170000000, vpssrate: 340000000

PLL0: vencrate_sd: 27200000, ddrrate: 340000000 mmcsdrate: 48571428

PLL1: armrate: 432000000, voicerate: 86400000, 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: 8960 Kernel command line: mem=35M console=ttyS0,115200n8 root=/dev/mtdblock3 rw rootfstype=yaffs2 ip=1 92.168.1.200:192.168.1.60:192.168.1.1:255.255.255.0::eth0:off video=davincifb:osd0=720x576x8,2500

K:osd1=off:vid0=off:vid1=off davinci_enc_mngr.ch0_mode= 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: 35MB = 35MB total

Memory: 30300KB available (3413K code, 708K data, 920K 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

DM365 IPIPE initialized in Single Shot mode Generic PHY: Registered new driver ch0 default output "COMPOSITE", mode "NTSC"

VPBE Encoder Initialized

SCSI subsystem initialized

usbcore: registered new driver usbfs

usbcore: registered new driver hub

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

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 Sep  1 2010 19:11:18 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 davincifb davincifb.0: dm_osd0_fb: 736x480x8@0,0 with framebuffer size 2500KB

DAVINCI-WDT: DaVinci Watchdog Timer: heartbeat 60 sec facedetect major#: 253, minor# 0 facedetect driver registered imp serializer initialized davinci_previewer initialized davinci_resizer initialized

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 Davinci EMAC MII Bus: probed MAC address is 00:11:a1:98:a8:e5 TI DaVinci EMAC Linux version updated 4.0

netconsole: not configured, aborting

Linux video capture interface: v2.00

ths7303.c: detecting client on address 0x58 chip found @ 0x58 (DaVinci I2C adapter) Trying to register davinci display video device.

layer=c0bd8800,layer->video_dev=c0bd8960

Trying to register davinci display video device.

layer=c0bd8600,layer->video_dev=c0bd8760

davinci_init:DaVinci V4L2 Display Driver V1.0 loaded i2c /dev entries driver MDIN200 default input NTSC MDIN200 I2C version 0.4 (14-Aug-2009) nand_davinci nand_davinci.0: Using soft ECC NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 94 at 0x00bc0000 Creating 4 MTD partitions on "nand_davinci.0":

0x00000000-0x00660000 : "bootloader"

0x00660000-0x00680000 : "params"

0x00680000-0x00a80000 : "kernel"

0x00a80000-0x07f00000 : "filesystem"

nand_davinci nand_davinci.0: hardware revision: 2.3 Initializing USB Mass Storage driver...

usbcore: registered new driver usb-storage USB Mass Storage support registered.

usbcore: registered new driver usbkbd

drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver

usbcore: registered new driver usbmouse

drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver

musb_hdrc: version 6.0, cppi-dma, host, debug=0

musb_hdrc: USB Host mode controller at c2866000 using DMA, IRQ 12 musb_hdrc musb_hdrc: MUSB HDRC host driver musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected

mice: PS/2 mouse device common for all mice

input: dm365_dvr_keypad as /class/input/input0 DVR_RTC:Found external RTC dvr-rtc 0-0068: rtc intf: proc dvr-rtc 0-0068: rtc intf: dev (254:0) dvr-rtc 0-0068: rtc core: registered rtc-dvr as rtc0 Registered led device: func Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).

ASoC version 0.13.1

AIC3X Audio Codec 0.2

asoc: aic3x <-> davinci-i2s mapping ok

CQ0093 Voice Codec 0.1

asoc: cq93vc <-> davinci-vcif mapping ok ALSA device list:

  #0: DaVinci DM365 EVM (aic3x)

  #1: On-chip voice codec (cq93vc)

IPv4 over IPv4 tunneling driver

TCP bic registered

NET: Registered protocol family 1

NET: Registered protocol family 17

dvr-rtc 0-0068: setting the system clock to 2011-05-28 18:34:20 (1306607660)

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 usb 1-1: new high speed USB device using musb_hdrc and address 2 usb 1-1: configuration #1 chosen from 1 choice hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usb 1-1.4: new high speed USB device using musb_hdrc and address 3 usb 1-1.4: configuration #1 chosen from 1 choice scsi0 : SCSI emulation for USB Mass Storage devices

IP-Config: Complete:

      device=eth0, addr=192.168.1.200, mask=255.255.255.0, gw=192.168.1.1,

     host=192.168.1.200, domain=, nis-domain=(none),

     bootserver=192.168.1.60, rootserver=192.168.1.60, rootpath=

yaffs: dev is 32505859 name is "mtdblock3"

yaffs: passed flags ""

yaffs: Attempting MTD mount on 31.3, "mtdblock3"

block 11 is bad

yaffs_read_super: isCheckpointed 0

VFS: Mounted root (yaffs2 filesystem).

Freeing init memory: 920K

Warning: unable to open an initial console.

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

 

Please suggest solution to boot DM368 DVR device board.

  • 0
    TI__Mastermind 19985 points

    Hi,

    Looking at the log, it seems like there is some problem with the filesystem. Are you using the filesystem that was provided with DVR RDK or have you created your own YAFFS2 filesystem? Can you confirm if the sizes programmed on NAND are correct and as per the install guide?

    My first recommendation is to just use everythign that is available in the release package, as-is. We can then look into possible problems.

    Regards,

    Anshuman

     

  • 0 in reply to Anshuman Saxena
    Prodigy 60 points

     

    we are using the yaffs2 file system provided with DVR RDK.

    Programing on NAND as per the DVR RDK install guide .

    1. Assigning Static IP:

    DVR: setenv ipaddr  172.28.11.145
    DVR: setenv serverip 172.28.11.59

    2. Runing  following command to copy YAFFS2 filesysystem to the device:

    DVR: tftpboot 0x82000000 dvr_target_fs.yaffs   (This will download the yaffs2 filesystem image from TFTP directory to DVR DDR memory)

    3. Write the DVR filesystem image present in DDR memory to the NAND Flash as follows:
    DVR: nandecc sw
    DVR: nand erase 0xA80000 7480000
    DVR: nand write.yaffs 0x82000000 0xA80000 <file size>
    DVR: nandecc hw

     

  • 0 in reply to Anshuman Saxena
    Prodigy 60 points

     

    we are using the yaffs2 file system provided with DVR RDK.

    Programing on NAND as per the DVR RDK install guide as below .

    1. Assigning Static IP:

    DVR: setenv ipaddr  172.28.11.145
    DVR: setenv serverip 172.28.11.59

    2. Runing  following command to copy YAFFS2 filesysystem to the device:

    DVR: tftpboot 0x82000000 dvr_target_fs.yaffs   (This will download the yaffs2 filesystem image from TFTP directory to DVR DDR memory)

    3. Write the DVR filesystem image present in DDR memory to the NAND Flash as follows:
    DVR: nandecc sw
    DVR: nand erase 0xA80000 7480000
    DVR: nand write.yaffs 0x82000000 0xA80000  3ce2500(image size)
    DVR: nandecc hw

     

     

  • 0 in reply to srinivasa reddy
    TI__Mastermind 19985 points

    Hi,

    srinivasa reddy said:
    DVR: nand erase 0xA80000 7480000

    Can you change the above line as

    DVR: nand erase 0xA80000 0x7480000

    Also, please help by sharing the bootargs that you are using.

    Regards,

    Anshuman

     

  • 0 in reply to Anshuman Saxena
    Prodigy 60 points

    Hi,

    I changed nand erase  as above .. still i am getting the same error message.

    Following are options i tried to boot as below:

    Booting  using the updated uImage from NAND and NFS filesystem:

    • set ipaddr 172.28.11.145

    • set serverip 172.28.11.59

    • set nfshost 172.28.11.59

    • set gatewayip 172.28.11.1

    • set netmask 255.255.255.0

    • set rootpath  root/filesys (this the file system path in server pc that is 172.28.11.59 and exported in export file in /ete/export)

    • set commonargs mem=35M console=ttyS0,115200n8 ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):::off video=davincifb:osd0=720x576x8,2500K:osd1=off:vid0=off:vid1=off davinci_enc_mngr.ch0_mode=$(videostd)

    • set bootargs $(commonargs) root=/dev/nfs noinitrd rw nfsroot=$(nfshost):$(rootpath),nolock

    • set bootcmd 'nboot 0x80700000 0 0x680000;bootm'

    • saveenv

    Boot using the uImage and filesystem present in NAND :

    • set ipaddr 172.28.11.145

    • set serverip 172.28.11.59

    • set nfshost 172.28.11.59

    • set gatewayip 172.28.11.1

    • set netmask 255.255.255.0

    • set commonargs console=ttyS0,115200n8 mem=35M ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):::off
      video=davincifb:osd0=720x576x8,2500K:osd1=off:vid0=off:vid1=off davinci_enc_mngr.ch0_mode=$(videostd)

    • setenv bootargs $(commonargs) root=/dev/mtdblock3 rw rootfstype=yaffs2

    • set bootcmd 'nboot 0x80700000 0 0x680000;bootm'

    • saveenv


    Boot using the uImage from TFTP and filesystem present in NFS:

    • set ipaddr 172.28.11.145

    • set serverip 172.28.11.59

    • set nfshost 172.28.11.59

    • set gatewayip 172.28.11.1

    • set netmask 255.255.255.0

    • set rootpath  root/filesys (this the file system path in server pc that is 172.28.11.59 and exported in export file in /ete/export)

    • set bootfile uImage_DM368_DVR

    • set commonargs console=ttyS0,115200n8 mem=35M ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):::off
      video=davincifb:osd0=720x576x8,2500K:osd1=off:vid0=off:vid1=off davinci_enc_mngr.ch0_mode=$(videostd

    • set bootargs $(commonargs) root=/dev/nfs noinitrd rw nfsroot=$(nfshost):$(rootpath),nolock

    • set bootcmd 'dhcp;bootm'

    • saveenv

    Kindly help us to trouble-shoot this error.

    Request you to kindly provide your direct number, so that we can discuss over the phone and resolve this issue?

     









  • 0 in reply to Anshuman Saxena
    TI__Mastermind 19985 points

    Srinivasa,

    Do you see the same problem in all the modes that you mentioned in your post?

    I would be interested to see the boot log with TFTP based uImage booting and filesystem on NFS. Can you please share that?

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    TI__Expert 7225 points

    Hello Srinivasa,

     

    Can you try the changing the boot args and common args

    1. using ip addresses per se, instead of $(serverip) , $(netmask) etc.
    2. Paths of the nfs rootpath etc can also be actual instead of $(nfshost) and $(rootpath)

     

    Please let us know if that solves.

     

    Can you share the dumps as asked by Anshuman please?

     

    Thanks & Best Regards

    Feroz 

  • 0 in reply to K Md Feroz Irfan
    Prodigy 250 points

    Dear Feroz ,

       I ran into this problem occasionally and I figure it could be HW (flash) related when  writing to flash.  The solution is to do the same process again (repeat those same steps as indicated below) and you should be able to boot up the entire board till you see login prompt. Each time it occurred, I just repeat the process and it worked like a charm!

    DVR: tftpboot 0x82000000 dvr_target_fs.yaffs
    DVR: nandecc sw
    DVR: nand erase 0xA80000 7480000
    DVR: nand write.yaffs 0x82000000 0xA80000 0x3cf03c0 <---file size downloaded
    DVR: nandecc hw


  • 0 in reply to srinivasa reddy
    Prodigy 250 points

    If you have not resolved the problem, please see my comments below.

     

    Thanks,