DSPRelated.com
Forums

Network problem for DM648

Started by "Li, Zhilie (US - MGTTS)" August 1, 2011
I have a problem with network for DM648. I use NDK to implement the TCP/IP on our own design board. The board is connected the network router (DHCP enabled). The application program runs on a PC. The PC is also connected to the router. The problem is that sometimes the application can't connect to the board through TCP/IP when start the application, it failed 1-2 times every 10 times try.
1. Can anybody give me advises about this problem?
2. How to sniffer the network traffic data on this node?

Thanks.
________________________________
This email may contain proprietary information and/or copyright material. This email is intended for the use of the addressee only. Any unauthorized use may be unlawful. If you receive this email by mistake, please advise the sender immediately by using the reply facility in your email software.

Information contained in and/or attached to this document may be subject to export control regulations of the European Community, USA, or other countries. Each recipient of this document is responsible to ensure that usage and/or transfer of any information contained in this document complies with all relevant export control regulations. If you are in any doubt about the export control restrictions that apply to this information, please contact the sender immediately.

Be aware that Meggitt may monitor incoming and outgoing emails to ensure compliance with the Meggitt IT User policy.
Zhilie Li,

On 8/1/2011 1:50 PM, Li, Zhilie (US - MGTTS) wrote:
>
> I have a problem with network for DM648. I use NDK to implement the
> TCP/IP on our own design board. The board is connected the network
> router (DHCP enabled). The application program runs on a PC. The PC is
> also connected to the router. The problem is that sometimes the
> application can't connect to the board through TCP/IP when start the
> application, it failed 1-2 times every 10 times try.
>

1. It sounds like you have an app on each end. Is this correct??
2. How are you accessing the DM648?? By name??
3. Can you ping the device 20 out of 20 times?? [use by name if that is
how you access??]
The goal is [before you 'start sniffing'] to try to identify 'which end'
is at fault [it is remotely possible that it is both].

I am not an ethernet expert, but I have seen similar problems when the
protocol stack is integrated. It usually occurs when recoverable errors
get lumped in with unrecoverable errors, errors that are stubbed out to
be fixed later, etc.

mikedunn

> 1. Can anybody give me advises about this problem?
> 2. How to sniffer the network traffic data on this node?
>
> Thanks.
>
>
> This email may contain proprietary information and/or copyright
> material. This email is intended for the use of the addressee only.
> Any unauthorized use may be unlawful. If you receive this email by
> mistake, please advise the sender immediately by using the reply
> facility in your email software.
>
> Information contained in and/or attached to this document may be
> subject to export control regulations of the European Community, USA,
> or other countries. Each recipient of this document is responsible to
> ensure that usage and/or transfer of any information contained in this
> document complies with all relevant export control regulations. If you
> are in any doubt about the export control restrictions that apply to
> this information, please contact the sender immediately.
>
> Be aware that Meggitt may monitor incoming and outgoing emails to
> ensure compliance with the Meggitt IT User policy.
Hi everyone.

I am trying to sign in at c6x group but I got Wrong username. Please try
again.I dont know why.

Zhilie Li,

With the problem of Network problem for DM648

I suggest that You should decide which side works wrong. The DSP side or
the router side .

1) You can connect your computer directly to your customized board
through Ethernet wire.

2) Install a program named dhcp turboon Microsoft windows instead
of use a router. DHCP Turbo is a DHCP server program.

3) Use the wireshark(previously ethereal) to capture packages .

You can figure out the problem. It could be the DSP side have not send the
DHCP discover ,also it could be the DHCP server have not send the DHCP
offer.

Kind regards.

Tianli

BUAA,Beijing china

: c... [mailto:c...] mikedunn
ʱ 201182 12:42
: Li, Zhilie (US - MGTTS)
: c...
: Re: [c6x] Network problem for DM648

Zhilie Li,

On 8/1/2011 1:50 PM, Li, Zhilie (US - MGTTS) wrote:

I have a problem with network for DM648. I use NDK to implement the TCP/IP
on our own design board. The board is connected the network router (DHCP
enabled). The application program runs on a PC. The PC is also connected to
the router. The problem is that sometimes the application cant connect to
the board through TCP/IP when start the application, it failed 1-2 times
every 10 times try.


1. It sounds like you have an app on each end. Is this correct??
2. How are you accessing the DM648?? By name??
3. Can you ping the device 20 out of 20 times?? [use by name if that is how
you access??]
The goal is [before you 'start sniffing'] to try to identify 'which end' is
at fault [it is remotely possible that it is both].

I am not an ethernet expert, but I have seen similar problems when the
protocol stack is integrated. It usually occurs when recoverable errors get
lumped in with unrecoverable errors, errors that are stubbed out to be fixed
later, etc.

mikedunn

1. Can anybody give me advises about this problem?
2. How to sniffer the network traffic data on this node?

Thanks.

_____

This email may contain proprietary information and/or copyright material.
This email is intended for the use of the addressee only. Any unauthorized
use may be unlawful. If you receive this email by mistake, please advise the
sender immediately by using the reply facility in your email software.

Information contained in and/or attached to this document may be subject to
export control regulations of the European Community, USA, or other
countries. Each recipient of this document is responsible to ensure that
usage and/or transfer of any information contained in this document complies
with all relevant export control regulations. If you are in any doubt about
the export control restrictions that apply to this information, please
contact the sender immediately.

Be aware that Meggitt may monitor incoming and outgoing emails to ensure
compliance with the Meggitt IT User policy.
Thanks everybody.

I tried to connect the board to the PC that the application runs on through a crossover cable. The problem is still there. I can assign IP in the firmware so we dont need to use dhcp server program.

When it happened, the ping command works (actually, ping first and then run application failed). The sniffer shows no response from the board when it is in trouble. I doubt if the application really sends the connection packet out. That is why I want to capture the data on the remote port (remote means the port is on the different machine). I hope you to give us suggestion to do this, by the way, we tried to set the port of the network switch as mirror port, it doesnt work.

I have information below for you.

1. ping command works. It sends the message to IP level.
2. fdselect (as select in regular stack) doesnt return (blocked) or returns with 0 (timeout is set).
3. the first time after power on always works.

Do you have any idea?

Thanks.

________________________________
From: tianli [mailto:t...@gmail.com]
Sent: Wednesday, August 03, 2011 7:38 AM
To: 'mikedunn'; Li, Zhilie (US - MGTTS)
Cc: c...
Subject: [c6x] Network problem for DM648
Hi everyone.

I am trying to sign in at c6x group but I got Wrong username. Please try again.I dont know why.
Zhilie Li,

With the problem of Network problem for DM648

I suggest that You should decide which side works wrong. The DSP side or the router side .

1) You can connect your computer directly to your customized board through Ethernet wire.

2) Install a program named dhcp turboon Microsoft windows instead of use a router. DHCP Turbo is a DHCP server program.

[cid:image003.jpg@01CC51F1.D9C3FC90]

3) Use the wireshark(previously ethereal) to capture packages .

[cid:image004.jpg@01CC51F1.D9C3FC90]

You can figure out the problem. It could be the DSP side have not send the DHCP discover ,also it could be the DHCP server have not send the DHCP offer.

Kind regards.

Tianli

BUAA,Beijing china

: c... [mailto:c...] mikedunn
ʱ 201182 12:42
: Li, Zhilie (US - MGTTS)
: c...
: Re: [c6x] Network problem for DM648

Zhilie Li,

On 8/1/2011 1:50 PM, Li, Zhilie (US - MGTTS) wrote:

I have a problem with network for DM648. I use NDK to implement the TCP/IP on our own design board. The board is connected the network router (DHCP enabled). The application program runs on a PC. The PC is also connected to the router. The problem is that sometimes the application cant connect to the board through TCP/IP when start the application, it failed 1-2 times every 10 times try.

1. It sounds like you have an app on each end. Is this correct??
2. How are you accessing the DM648?? By name??
3. Can you ping the device 20 out of 20 times?? [use by name if that is how you access??]
The goal is [before you 'start sniffing'] to try to identify 'which end' is at fault [it is remotely possible that it is both].

I am not an ethernet expert, but I have seen similar problems when the protocol stack is integrated. It usually occurs when recoverable errors get lumped in with unrecoverable errors, errors that are stubbed out to be fixed later, etc.

mikedunn
1. Can anybody give me advises about this problem?
2. How to sniffer the network traffic data on this node?
Thanks.

________________________________
This email may contain proprietary information and/or copyright material. This email is intended for the use of the addressee only. Any unauthorized use may be unlawful. If you receive this email by mistake, please advise the sender immediately by using the reply facility in your email software.

Information contained in and/or attached to this document may be subject to export control regulations of the European Community, USA, or other countries. Each recipient of this document is responsible to ensure that usage and/or transfer of any information contained in this document complies with all relevant export control regulations. If you are in any doubt about the export control restrictions that apply to this information, please contact the sender immediately.

Be aware that Meggitt may monitor incoming and outgoing emails to ensure compliance with the Meggitt IT User policy.
Li,

You mention that the application works on the first time after power-up and
fails afterwards...

That is a very good indication that the application is leaving the communication
channel in the wrong status.

Does the application close the connection?
Does the application close the file?

I would try reading the connection attributes before the first run, then at the
end of the first run of the application.

Then run the application again and compare the connection attributes.

It should be relatively easy to set the connection attributes at the start of a
run to match the original connection attributes.

R. Williams
---------- Original Message -----------
From: "Li, Zhilie (US - MGTTS)"
To: tianli , "'mikedunn'"
Cc: "c..."
Sent: Wed, 3 Aug 2011 19:30:05 +0000
Subject: RE: [c6x] Network problem for DM648

> Thanks everybody.
>
> I tried to connect the board to the PC that the application runs on
> through a crossover cable. The problem is still there. I can assign IP
> in the firmware so we don’t need to use dhcp server program.
>
> When it happened, the ping command works (actually, ping first and
> then run application failed). The sniffer shows no response from the
> board when it is in trouble. I doubt if the application really sends
> the connection packet out. That is why I want to capture the data on
> the remote port (“remote” means the port is on the different machine)
> . I hope you to give us suggestion to do this, by the way, we tried to
> set the port of the network switch as mirror port, it doesn’t work.
>
> I have information below for you.
>
> 1. ping command works. It sends the message to IP level.
>
> 2. fdselect (as select in regular stack) doesn’t return (blocked)
> or returns with 0 (timeout is set).
> 3. the first time after power on always works.
>
> Do you have any idea?
>
> Thanks.
>
> ________________________________
> From: tianli [mailto:t...@gmail.com]
> Sent: Wednesday, August 03, 2011 7:38 AM
> To: 'mikedunn'; Li, Zhilie (US - MGTTS)
> Cc: c...
> Subject: 答复: [c6x] Network problem for DM648
>
> Hi everyone.
>
> I am trying to sign in at c6x group but I got “Wrong username. Please
> try again.”I don’t know why.
Zhilie Li,
>
> With the problem of “Network problem for DM648”
>
> I suggest that You should decide which side works wrong. The DSP side
> or the router side .
>
> 1) You can connect your computer directly to your customized
> board through Ethernet wire.
>
> 2) Install a program named “dhcp turbo”on Microsoft windows
> instead of use a router. DHCP Turbo is a DHCP server program.
>
> [cid:image003.jpg@01CC51F1.D9C3FC90]
>
> 3) Use the” wireshark”(previously ethereal) to capture
> packages .
>
> [cid:image004.jpg@01CC51F1.D9C3FC90]
>
> You can figure out the problem. It could be the DSP side have not send
> the DHCP discover ,also it could be the DHCP server have not send the
> DHCP offer.
>
> Kind regards.
>
> Tianli
>
> BUAA,Beijing china
>
> 发件人: c... [mailto:c...] 代表 mikedunn
> 发送时间: 2011年8月2日 12:42
> 收件人: Li, Zhilie (US - MGTTS)
> 抄送: c...
> 主题: Re: [c6x] Network problem for DM648
>
> Zhilie Li,
>
> On 8/1/2011 1:50 PM, Li, Zhilie (US - MGTTS) wrote:
>
> I have a problem with network for DM648. I use NDK to implement the
> TCP/IP on our own design board. The board is connected the network
> router (DHCP enabled). The application program runs on a PC. The PC is
> also connected to the router. The problem is that sometimes the
> application can’t connect to the board through TCP/IP when start the
> application, it failed 1-2 times every 10 times try.

> 1. It sounds like you have an app on each end. Is this correct??
> 2. How are you accessing the DM648?? By name??
> 3. Can you ping the device 20 out of 20 times?? [use by name if that
> is how you access??]
The goal is [before you 'start sniffing'] to try
> to identify 'which end' is at fault [it is remotely possible that it
> is both].
>
> I am not an ethernet expert, but I have seen similar problems when the
> protocol stack is integrated. It usually occurs when recoverable
> errors get lumped in with unrecoverable errors, errors that are
> stubbed out to be fixed later, etc.
>
> mikedunn
>
> 1. Can anybody give me advises about this problem?
> 2. How to sniffer the network traffic data on this node?
> Thanks.
>
> ________________________________
> This email may contain proprietary information and/or copyright
> material. This email is intended for the use of the addressee only.
> Any unauthorized use may be unlawful. If you receive this email by
> mistake, please advise the sender immediately by using the reply
> facility in your email software.
>
> Information contained in and/or attached to this document may be
> subject to export control regulations of the European Community, USA,
> or other countries. Each recipient of this document is responsible to
> ensure that usage and/or transfer of any information contained in this
> document complies with all relevant export control regulations. If you
> are in any doubt about the export control restrictions that apply to
> this information, please contact the sender immediately.
>
> Be aware that Meggitt may monitor incoming and outgoing emails to
> ensure compliance with the Meggitt IT User policy.
------- End of Original Message -------

_____________________________________
Hi, there!

We are also using DM648 now, and we found similar problems of DM468's ethernet: when first running the program, the system will often halt and you must restart the program and then it runs ok. I then found at TI's community that it is a bug of NDK2.0.0, there is a patch you can add to your code, the dicussion is list at http://e2e.ti.com/support/embedded/f/355/t/64939.aspx and there is also a link to NDK patch.

Hope this helps.

2011-08-10

shengkai.sun