VxWorks boot error in VmWare - VxWorks

This is a discussion on VxWorks boot error in VmWare - VxWorks ; Network interfaces configuration: LAN : 192.168.80.169 VMnet1 : 192.168.80.1 VMnet8 : 192.168.80.8 vxworks vm ethernet : Bridged Platform : WINXP SP2 [VxWorks Boot]: @ boot device : lnPci unit number : 0 processor number : 0 host name : T60 ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: VxWorks boot error in VmWare

  1. VxWorks boot error in VmWare

    Network interfaces configuration:
    LAN : 192.168.80.169
    VMnet1 : 192.168.80.1
    VMnet8 : 192.168.80.8

    vxworks vm ethernet : Bridged

    Platform : WINXP SP2

    [VxWorks Boot]: @

    boot device : lnPci
    unit number : 0
    processor number : 0
    host name : T60
    file name : d:\vxWorks
    inet on ethernet (e) : 192.168.80.254
    host inet (h) : 192.168.80.169
    user (u) : user
    ftp password (pw) : user
    flag (f) : 0x0
    target name (tn) : target

    Attached TCP/IP interface to lnPci0.
    Warning: no netmask specified.
    Attached network interface lo0... done.
    Loading...

    Error loading file : errno = 0x3c

    When vxworks vm is started, the above error message will be prompted
    in a minute.
    And ftp server outputs no log message, i.e. target does not connect to
    host.

    While I am sure ftp server is started, because I can login ftp server
    and get responding
    log messages.

    What's wrong?


  2. Re: VxWorks boot error in VmWare

    Now when start vm, ftp server reports 2 times the following messages.

    [L 0009] 05/12/07 13:14:14 Connection accepted from 192.168.80.254
    [C 0009] 05/12/07 13:14:14 QUIT or close - user logged out
    [L 0010] 05/12/07 13:14:44 Connection accepted from 192.168.80.254
    [C 0010] 05/12/07 13:14:44 QUIT or close - user logged out


  3. Re: VxWorks boot error in VmWare

    The AMD NIC driver from windriver has some problems in applying it to
    vmware.
    Try to find another one from AMD HP.


+ Reply to Thread