Help on symbol synchronization issue, thanks - VxWorks

This is a discussion on Help on symbol synchronization issue, thanks - VxWorks ; vxWorker, I'm using Tornado 2.0.2 on winXP & vxWorks 5.3.1. I met a problem when I was trying to make symbol synchronization between my host and target.There's a "Fatal WTX error (0x1012f), synchronization stopped" message printed on tShell. I've found ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Help on symbol synchronization issue, thanks

  1. Help on symbol synchronization issue, thanks


    vxWorker,
    I'm using Tornado 2.0.2 on winXP & vxWorks 5.3.1. I met a problem when
    I was trying to make symbol synchronization between my host and
    target.There's a "Fatal WTX error (0x1012f), synchronization stopped"
    message printed on tShell. I've found tips posted before and so that
    I've set my Tornado Registry ip address to my own PC ip address, not
    "localhost",but the problem still occurs. I noticed that when I start my
    target server ,the "tSymSync" task was spawned but it's always in a
    "PEND + T" status. and after a while, the message above was printed and
    this task disappeared.

    Who can tell me what this error message means and how to solve this
    problem? Surely I can ping my target from host. Any tip is really much
    appreciated.

    --


  2. Re: Help on symbol synchronization issue, thanks

    When I've seen this before, it means that the vxWorks image I'm
    downloading (from some other machine) via my bootrom/vxWorks boot
    parameters does not match the vxWorks image pointed to by the target
    shell. Make sure they are the same.

    Ke.Zou wrote:
    > vxWorker,
    > I'm using Tornado 2.0.2 on winXP & vxWorks 5.3.1. I met a problem when
    > I was trying to make symbol synchronization between my host and
    > target.There's a "Fatal WTX error (0x1012f), synchronization stopped"
    > message printed on tShell. I've found tips posted before and so that
    > I've set my Tornado Registry ip address to my own PC ip address, not
    > "localhost",but the problem still occurs. I noticed that when I start my
    > target server ,the "tSymSync" task was spawned but it's always in a
    > "PEND + T" status. and after a while, the message above was printed and
    > this task disappeared.
    >
    > Who can tell me what this error message means and how to solve this
    > problem? Surely I can ping my target from host. Any tip is really much
    > appreciated.
    >
    > --



  3. Re: Help on symbol synchronization issue, thanks


    > When I've seen this before, it means that the vxWorks image I'm
    > downloading (from some other machine) via my bootrom/vxWorks boot
    > parameters does not match the vxWorks image pointed to by the target
    > shell. Make sure they are the same.
    >
    > Ke.Zou wrote:
    > > vxWorker,
    > > I'm using Tornado 2.0.2 on winXP & vxWorks 5.3.1. I met a problem
    > > when
    > > I was trying to make symbol synchronization between my host and
    > > target.There's a "Fatal WTX error (0x1012f), synchronization
    > > stopped"
    > > message printed on tShell. I've found tips posted before and so that
    > > I've set my Tornado Registry ip address to my own PC ip address, not
    > > "localhost",but the problem still occurs. I noticed that when I
    > > start my
    > > target server ,the "tSymSync" task was spawned but it's always in a
    > > "PEND + T" status. and after a while, the message above was printed
    > > and
    > > this task disappeared.
    > >
    > > Who can tell me what this error message means and how to solve this
    > > problem? Surely I can ping my target from host. Any tip is really
    > > much
    > > appreciated.
    > >
    > > --


    Thanks for your reply. But I've checked the image I was using in my
    host, it does match the one in the target. (otherwise the warning
    message will be printed on my target server, right?).
    I used ethereal ( an ethernet monitor tool ) to get some information, &
    I found
    that when I launch the target server with symbol synchronization flag,
    there
    are some UDP and TCP packets, the UDP packets are all right, but TCP
    connection is founded with an ethernet frame check sequence
    (FCS)error...and the connection is terminated immediately after two
    "PSH, ACK" packets...I have no idea if this is related to my symbol
    synchronization error....any tips?

    --


+ Reply to Thread