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.

APPRO DM368无法用浏览器查看ipnc



各位大大帮忙看看吧

串口启动信息如下:

M36x initialization passed!
TI UBL Base Version: 1.50
Boot Loader BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000008.
Boot Mode Task Completed

IPNC UBL Version: 2.0.0
Platform: DM368

Jumping to entry point at 0x81080000

U-Boot 1.3.4 (Jul 26 2012 - 01:58:46) DM368-IPNC-2.0.0

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
DM368 IPNC :>
DM368 IPNC :>
DM368 IPNC :>
DM368 IPNC :>
DM368 IPNC :>
DM368 IPNC :>
DM368 IPNC :>
DM368 IPNC :>boot

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:    2650052 Bytes =  2.5 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:    2650052 Bytes =  2.5 MB
   Load Address: 80008000
   Entry Point:  80008000
   Loading Kernel Image ... OK
OK

Starting kernel ...

[   89.020000] IP-Config: Reopening network devices...
[  178.290000] IP-Config: Auto-configuration of network failed.
INIT: version 2.86 booting
Creat queue id:0
queue id:0
FileMngThread created
Creat queue id:32769
queue id:32769
AlramThread created
Share memory init success
IPNC_DM368_3.0.0 (root@localhost.localdomain) (gcc version 4.2.
Creat queue id:65538
queue id:65538
queue id:32769
FileMng: Error Can't create system file
FileMng: Error Initialize fail (FileMgnInit)
FileMsgDrv: Error
Data read error
Kill queue id:32769
Error CleanupFileEnv is called
queue id:65538
Creat queue id:98305
queue id:98305
Setting up networking ...rm: unable to remove `/etc/network/run': Read-only file
 system
FileMsgDrv: Error
Data read error
Can't get system info!!
FileMsgDrv: Error
Data read error
log status
Starting portmap daemon: log status
portmapstart_daemon
/opt/ipnc/modules/init.d_ins/portmap: /opt/ipnc/modules/init.d_ins/portmap: 162:
 cannot create /var/run/portmap.pid: Read-only file system
log success
.
log status
log status
Starting mounting local filesystems: log status
mount none on /dev/shm type tmpfs (rw,size=5M)
none on /var/run type tmpfs (rw)
none on /tmp type tmpfs (rw,sync)
log success
log status
Starting hotplug subsystem:
   usb
   usb      [success]
   input
   input    [success]
done.
Starting internet superserver: inetd.
mkdosfs 3.0.6 (04 Oct 2009)
unable to get drive geometry, using default 255/63
/dev/sbulla has 255 heads and 63 sectors per track,
logical sector size is 512,
using 0xf8 media descriptor, with 1024 sectors;
file system has 2 12-bit FATs and 4 sectors per cluster.
FAT size is 1 sector, and provides 247 clusters.
Root directory contains 512 slots.
Volume ID is 6c9de456, no volume label.
queue id:0
TimeOut occure in boot_proc.
Program exit.
ApproDrvInit: 3
Creat queue id:131075
queue id:131075

其中在

Starting kernel ...上停留3分钟左右没有打印内核启动信息,请各位大侠指导一下,这个是什么原因?

  • 会不会是u-boot参数配置有问题呢

  • 你这kernel都还没起来呢。

    是否用的都是pre-build的binary?

    1. 尝试从ubl,uboot,kernel起全部重新烧写

    2. 贴你的bootcmd和bootargs上来瞧瞧

  • DM36x initialization passed!
    TI UBL Base Version: 1.50
    Boot Loader BootMode = NAND
    Starting NAND Copy...
    Valid magicnum, 0xA1ACED66, found in block 0x00000008.
    Boot Mode Task Completed

    IPNC UBL Version: 2.0.0
    Platform: DM368

    Jumping to entry point at 0x81080000

    U-Boot 1.3.4 (Mar 25 2013 - 12:12:53) DM368-IPNC-5.0.0

    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
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>
    DM368 IPNC :>print
    bootdelay=4
    baudrate=115200
    bootfile="uImage"
    verify=no
    bootcmd=nboot 0x80700000 0 0x500000;bootm 0x80700000
    bootargs=mem=48M console=ttyS0,115200n8 root=/dev/mtdblock3 rootfstype=squashfs
    ip=dhcp eth=$(ethaddr) lpj=1077248 cmemk.phys_start="0x83000000" cmemk.phys_end=
    "0x88000000" cmemk.phys_start_1="0x00001000"cmemk.phys_end_1="0x00008000" cmemk.
    pools_1="1x28672" cmemk.allowOverlap="1" quiet
    filesize=25EFC
    fileaddr=80700000
    ipaddr=192.168.1.168
    serverip=192.168.1.9
    gatewayip=192.168.1.2
    netmask=255.255.255.0
    dnsip=192.168.1.2
    dnsip2=192.168.1.3
    ethaddr=00:E0:0A:DD:00:00
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 1.3.4 (Mar 25 2013 - 12:12:53) DM368-IPNC-5.0.0

    Environment size: 678/131068 bytes
    DM368 IPNC :>boot

    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:    2650052 Bytes =  2.5 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:    2650052 Bytes =  2.5 MB
       Load Address: 80008000
       Entry Point:  80008000
       Loading Kernel Image ... OK
    OK

    Starting kernel ...

    [   89.020000] IP-Config: Reopening network devices...
    [  178.290000] IP-Config: Auto-configuration of network failed.
    INIT: version 2.86 booting
    Creat queue id:0
    queue id:0
    FileMngThread created
    Creat queue id:32769
    queue id:32769
    AlramThread created
    Share memory init success
    IPNC_DM368_3.0.0 (root@localhost.localdomain) (gcc version 4.2.
    Creat queue id:65538
    queue id:65538
    queue id:32769
    FileMng: Error Can't create system file
    FileMng: Error Initialize fail (FileMgnInit)
    FileMsgDrv: Error
    Data read error
    Kill queue id:32769
    Error CleanupFileEnv is called
    queue id:65538
    Creat queue id:98305
    queue id:98305
    FileMsgDrv: Error
    Data read error
    Can't get system info!!
    FileMsgDrv: Error
    Data read error
    Setting up networking ...rm: unable to remove `/etc/network/run': Read-only file
     system
    log status
    Starting portmap daemon: log status
    portmapstart_daemon
    /opt/ipnc/modules/init.d_ins/portmap: /opt/ipnc/modules/init.d_ins/portmap: 162:
     cannot create /var/run/portmap.pid: Read-only file system
    log success
    .
    log status
    log status
    Starting mounting local filesystems: log status
    mount none on /dev/shm type tmpfs (rw,size=5M)
    none on /var/run type tmpfs (rw)
    none on /tmp type tmpfs (rw,sync)
    log success
    log status
    Starting hotplug subsystem:
       usb
       usb      [success]
       input
       input    [success]
    done.
    Starting internet superserver: inetd.
    mkdosfs 3.0.6 (04 Oct 2009)
    unable to get drive geometry, using default 255/63
    /dev/sbulla has 255 heads and 63 sectors per track,
    logical sector size is 512,
    using 0xf8 media descriptor, with 1024 sectors;
    file system has 2 12-bit FATs and 4 sectors per cluster.
    FAT size is 1 sector, and provides 247 clusters.
    Root directory contains 512 slots.
    Volume ID is 04fe0826, no volume label.
    queue id:0
    TimeOut occure in boot_proc.
    Program exit.
    ApproDrvInit: 3
    Creat queue id:131075
    queue id:131075
    INIT: Entering runlevel: 5

     

     

     

     

     

     

     

     

     

     

     

     

     


    MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774)

    (none) login: root (automatic login)


    Welcome to MontaVista(R) Linux(R) Professional Edition 5.0.0 (0702774).

    login[608]: root login  on `ttyS0'

    #
    #
    #
    #
    #
    # ifconfig
    eth0      Link encap:Ethernet  HWaddr 00:E0:0A:DD:00:00
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
              Interrupt:52 Base address:0x7000

    eth0:avah Link encap:Ethernet  HWaddr 00:E0:0A:DD:00:00
              inet addr:169.254.4.140  Bcast:169.254.255.255  Mask:255.255.0.0
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              Interrupt:52 Base address:0x7000

    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

     

    你好,这里面有bootcmd、boottargs,还有启动后的信息,启动参数设置是按照appro提供的用户手册设置的,本人才接触,这个困惑我好久了,非常感谢能解决哦。

  • 你既然用的是Appro的原装的bootcmd,bootargs  

    那么检查一下机身上的拨码开关是否和文档里的要求完全一致?  

    (bianry是否也是预先烧写进去的?是否sensor和软件是对应的)