Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - strange behavior when starting qconn from bsh script: Page 1 of 3 (3 Items)
   
strange behavior when starting qconn from bsh script  
Hi,

I'm starting qconn from the bsh script upon boot, but the target does not appear as active/connected on the host until I
 do a "ping <host>" from the target serial shell. Board is MPC8313.

I do the following:

io-pkt-v4 -dmpc85xx mac=000012345678 -ptcpip &
waitfor /dev/io-net/en0
waitfor /dev/socket 4
ifconfig en1 192.168.80.2
[other stuff]
qconn port=8000

But, as I wrote, Momentics only connects once I ping.

I tried to mechanize this and added this as the last command:
ping -c 5 192.168.80.1

Behavior of the five ping packets:
- ping
- ping
- ping
- no reply
- no reply

From the command line, ping always succeeds when called as soon as the shell prompt appears. How can this be?

After this, the target appears in Momentics, but i wonder nevertheless:
- how can I make it connect automatically without pinging
- why are the first three automated  pings succeeding, the two last automated pings not, and from the shell it's always 
successful?

Greetings,
 Marc