Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Community/Discussion/QNX Momentics Community Support/Loss of debug connectivity/List of Posts
Forum Topic - Loss of debug connectivity: (10 Items)
   
Update
Alan Braddy
10/28/2011 3:46 AM
post89711
Loss of debug connectivity   
I'm getting an odd effect with respect to the Momentics debug connection.
I'm running IDE 4.7 (windows hosted) talking to an x86 target running Momentics 6.5 over an ethernet connection.

Everything has been going fine until a few days ago, now when viewing the target navigator the expansion (+) indicator 
next tho the target disapears after 3-5 minutes and I can't acess the target via the IDE debugger.

Ping works from both target and host, and the Target navigator doesn't show the target as (not-connected).

I've tried it with both fixed and dynamic IP addresses with the same result, and a contractor who is working with me has
 the same issue on a completely different set of hardware.

I've removed all of my software, so the target system is just sitting there with phioton up.

Any pointers as to where to start looking would be appreciated.

(At the moment I'm assuming it's something I've done on building the target).
Alan Braddy
10/28/2011 5:22 AM
post89713
Re: Loss of debug connectivity   
> I'm running IDE 4.7 (windows hosted) talking to an x86 target running 
> Momentics 6.5 over an ethernet connection.

Oops that should read running Neutrino 6.5 of course
Elena Laskavaia
10/28/2011 10:46 AM
post89733
Re: Loss of debug connectivity   
Is qconn running on target? Can you re-start it and see if fixes the problem?

On 10/28/2011 05:22 AM, Alan Braddy wrote:
>> I'm running IDE 4.7 (windows hosted) talking to an x86 target running 
>> Momentics 6.5 over an ethernet connection.
> 
> Oops that should read running Neutrino 6.5 of course
> 
> 
> 
> _______________________________________________
> 
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post89713
>
Andy Jin(deleted)
10/28/2011 7:51 AM
post89719
Re: Loss of debug connectivity   
This is not debug issue. Is your qconn running on target when you see the
"target navigator the expansion (+) indicator next tho the target
disapears after 3-5 minutes"?



On 11-10-28 3:46 AM, "Alan Braddy" <community-noreply@qnx.com> wrote:

>I'm getting an odd effect with respect to the Momentics debug connection.
>I'm running IDE 4.7 (windows hosted) talking to an x86 target running
>Momentics 6.5 over an ethernet connection.
>
>Everything has been going fine until a few days ago, now when viewing the
>target navigator the expansion (+) indicator next tho the target
>disapears after 3-5 minutes and I can't acess the target via the IDE
>debugger.
>
>Ping works from both target and host, and the Target navigator doesn't
>show the target as (not-connected).
>
>I've tried it with both fixed and dynamic IP addresses with the same
>result, and a contractor who is working with me has the same issue on a
>completely different set of hardware.
>
>I've removed all of my software, so the target system is just sitting
>there with phioton up.
>
>Any pointers as to where to start looking would be appreciated.
>
>(At the moment I'm assuming it's something I've done on building the
>target).
>
>
>
>_______________________________________________
>
>QNX Momentics Community Support
>http://community.qnx.com/sf/go/post89711
>
Alan Braddy
10/28/2011 9:18 AM
post89725
Re: Loss of debug connectivity   
Yes, QConn is still running when I lose the indicatoraccording to pidin
Andy Jin(deleted)
10/28/2011 9:28 AM
post89726
Re: Loss of debug connectivity   
You mentioned "Everything has been going fine until a few days ago, and
your colleague also has the same issue". What had changed? Did you install
a firewall in your network? Is your network become congested?


On 11-10-28 9:18 AM, "Alan Braddy" <community-noreply@qnx.com> wrote:

>Yes, QConn is still running when I lose the indicatoraccording to pidin
>
>
>
>_______________________________________________
>
>QNX Momentics Community Support
>http://community.qnx.com/sf/go/post89725
>
Alan Braddy
10/28/2011 9:43 AM
post89728
Re: Loss of debug connectivity   
I've tried running this on both our LAN (which isn't normally particularly busy) and direct from a second network card 
(cross-over cable) on my PC with the same results, my collegue is using it from a second network card with a switch & 
straight cables. 

There doesn't appear to be any sign of network congestion even on the LAN (no-one in the office is screaming about a 
slow network).
Andy Jin(deleted)
10/28/2011 9:50 AM
post89730
Re: Loss of debug connectivity   
Ok if network is not a problem, are you using the same Neutrino target
machine as the one used before the problem arise? If not is there any
change in the target machine especially in the network configuration?

On 11-10-28 9:43 AM, "Alan Braddy" <community-noreply@qnx.com> wrote:

>I've tried running this on both our LAN (which isn't normally
>particularly busy) and direct from a second network card (cross-over
>cable) on my PC with the same results, my collegue is using it from a
>second network card with a switch & straight cables.
>
>There doesn't appear to be any sign of network congestion even on the LAN
>(no-one in the office is screaming about a slow network).
>
>
>
>_______________________________________________
>
>QNX Momentics Community Support
>http://community.qnx.com/sf/go/post89728
>
Alan Braddy
11/01/2011 5:18 AM
post89788
Re: Loss of debug connectivity   
Killing and restarting QConn does clear the problem for a few minutes, after which it returns. I can't do this on our 
target system though, as it's headless.

(Clarification - I have two systems here, a Kontron development system with keyboard & monitor, and our custom target 
system which is only accessible via ethernet. I can swap the (programmed) processor / disk module between the two 
systems.)

As far as changes are concerned, I have a number of systems avaialble, my main development board is (as far as I am 
aware) unchanged, the others have the same Neutrino build (6.5 generic x86 from the distribution DVD) but may have 
slight differences in the configuration files. The new boards are a slightly later hardware build, BIOS version is the 
same on all.

All the targets show the same behaviour.

I suspect this may either be something I've inadvertantly changed in a config file, or a side-effect on the development 
system of a windows update - but these are just guesses.
Alan Braddy
11/16/2011 5:00 AM
post90122
Re: Loss of debug connectivity   
I've reconfigured our headless target system to allow remote photon access via phindows, this now allows me to slay 
qconn on that board.

Like the development system slaying qconn resolves the problem for a few minutes then I lose the target navigator tree 
again and the debugger fails. 

Unfortunately the problem occurs so regularly I can't get any worthwhile debug time on my target.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems