|
12/03/2008 7:25 PM
post17890
|
Hi,
I am having problems trying to perform debugging on the target (i.MX31 ADS board). Basically I frequently encounter the
two following issues:
* After launching a debug or run application on my target from withing QNX Momentics IDE, my target's serial terminal
connection gets affected in such a way that I have to double-type each letter (as if terminal-echoing was off). e.g. to
change to the dev directory I'd have to type it like "ccdd //ddeevv". The only way I know to fix the problem is to
reset the target board.
* After launching a couple debug or run applications on the target from within the IDE, then after stopping or
terminating the processes I find that my running instances of "qconn" and "io-pkt-v4" disappear and as a result I loose
connectivity with the board.
Does anyone know why this may be happening or how to fix this? Currently I am experiencing both of the above symptoms
continually when I am trying to debug simple pulse send and receive resource managers, making it virtually impossible
for me to do so.
Regards,
Radek.
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/03/2008 8:46 PM
post17892
|
RE: Help on target debugging
Hi Radek:
With regards to io-pkt-v4 disappearing, are you running slogger? Is there any information in sloginfo? Can you run
dumper and see if any core files are created? What network driver are you using? Does your application hit hardware in
any way?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wed 12/3/2008 7:25 PM
To: momentics-community
Subject: Help on target debugging
Hi,
I am having problems trying to perform debugging on the target (i.MX31 ADS board). Basically I frequently encounter the
two following issues:
* After launching a debug or run application on my target from withing QNX Momentics IDE, my target's serial terminal
connection gets affected in such a way that I have to double-type each letter (as if terminal-echoing was off). e.g. to
change to the dev directory I'd have to type it like "ccdd //ddeevv". The only way I know to fix the problem is to
reset the target board.
* After launching a couple debug or run applications on the target from within the IDE, then after stopping or
terminating the processes I find that my running instances of "qconn" and "io-pkt-v4" disappear and as a result I loose
connectivity with the board.
Does anyone know why this may be happening or how to fix this? Currently I am experiencing both of the above symptoms
continually when I am trying to debug simple pulse send and receive resource managers, making it virtually impossible
for me to do so.
Regards,
Radek.
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post17890
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/04/2008 9:25 AM
post17914
|
RE: Help on target debugging
Hi Radek,
Also, does this happen with any project you debug or only your resource
manager?
-Wade
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: December 3, 2008 8:47 PM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek:
With regards to io-pkt-v4 disappearing, are you running slogger? Is
there any information in sloginfo? Can you run dumper and see if any
core files are created? What network driver are you using? Does your
application hit hardware in any way?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wed 12/3/2008 7:25 PM
To: momentics-community
Subject: Help on target debugging
Hi,
I am having problems trying to perform debugging on the target (i.MX31
ADS board). Basically I frequently encounter the two following issues:
* After launching a debug or run application on my target from withing
QNX Momentics IDE, my target's serial terminal connection gets affected
in such a way that I have to double-type each letter (as if
terminal-echoing was off). e.g. to change to the dev directory I'd have
to type it like "ccdd //ddeevv". The only way I know to fix the
problem is to reset the target board.
* After launching a couple debug or run applications on the target from
within the IDE, then after stopping or terminating the processes I find
that my running instances of "qconn" and "io-pkt-v4" disappear and as a
result I loose connectivity with the board.
Does anyone know why this may be happening or how to fix this?
Currently I am experiencing both of the above symptoms continually when
I am trying to debug simple pulse send and receive resource managers,
making it virtually impossible for me to do so.
Regards,
Radek.
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post17890
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post17892
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/05/2008 1:08 AM
post17986
|
RE: Help on target debugging
Hi Robert and Wade,
Yes I have slogger running. Sloginfo has the following:
Time Sev Major Minor Args
Jan 01 00:00:00 5 14 0 tcpip starting
Jan 01 00:00:00 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:00:00 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:00:00 1 7 0 CTRL_DLL_INIT: imx31ads
Jan 01 00:00:01 2 19 900 devb-umass 1.00A (Oct 20 2008 23:28:34)
Jan 01 00:00:01 2 5 0 libcam.so (Oct 20 2008 23:22:15) bver 6040001
Jan 01 00:00:01 5 27 0 MME:mme_main(322): MME Version 1.1 built at Oct 21 2008 09:57:26
Jan 01 00:00:02 2 27 0 MME:slot_info_get(200): Got 0 rows from slot table for path "/dev/shmem"; expected 1.
Jan 01 00:00:03 2 5 100 cam-disk.so (Oct 20 2008 23:22:39)
Jan 01 00:00:03 2 5 0 scsi_interpret_sense: path=0, target=0, lun=0, cam_status=c4, scsi_status=2, flag=
000000c0,
vuflag=0008, cmd=0, error=70, sense=6,
asc=28, ascq=0
Jan 01 00:00:04 2 20 1 io-media-generic/trackplayer: Error 1:
Jan 01 00:00:04 2 20 1 io-media-generic/trackplayer: get_trkinfo: Problem with URL specified.
Jan 01 00:00:04 2 27 0 MME:getFileMetadata(82): Failed iom_get_track_info, errno = 5
Jan 01 00:01:48 5 21 0 run fault pid 5 tid 2 signal 11 code 1 ip 0x14402c proc/boot/io-pkt-v4
I have also attached the core dump for io-pkt-v4. I know I have experienced this a few times while debugging over the
last couple
of months, however I cannot recall if it was always when I was debugging resource managers. The one I am using at the
moment to
produce the problem is just a very simple pulse send/receive which is created from a few QNX examples. It is contained
within the
zip file for your reference.
Regards,
Radek.
-----Original Message-----
From: Wade Hawkins [mailto:community-noreply@qnx.com]
Sent: Friday, December 05, 2008 1:26 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek,
Also, does this happen with any project you debug or only your resource
manager?
-Wade
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: December 3, 2008 8:47 PM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek:
With regards to io-pkt-v4 disappearing, are you running slogger? Is
there any information in sloginfo? Can you run dumper and see if any
core files are created? What network driver are you using? Does your
application hit hardware in any way?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wed 12/3/2008 7:25 PM
To: momentics-community
Subject: Help on target debugging
Hi,
I am having problems trying to perform debugging on the target (i.MX31
ADS board). Basically I frequently encounter the two following issues:
* After launching a debug or run application on my target from withing
QNX Momentics IDE, my target's serial terminal connection gets affected
in such a way that I have to double-type each letter (as if
terminal-echoing was off). e.g. to change to the dev directory I'd have
to type it like "ccdd //ddeevv". The only way I know to fix the
problem is to reset the target board.
* After launching a couple debug or run applications on the target from
within the IDE, then after stopping or terminating the processes I find
that my running instances of "qconn" and "io-pkt-v4" disappear and as a
result I loose connectivity with the board.
Does anyone know why this may be happening or how to fix this?
Currently I am experiencing both of the above symptoms continually when
I am trying to debug simple pulse send and receive resource managers,
making it virtually impossible for me to do so.
Regards,
Radek.
_______________________________________________
QNX Momentics Community...
View Full Message
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/05/2008 7:32 AM
post17992
|
RE: Help on target debugging
Hi Radek:
Just to be sure, can you also send us a copy of your io-pkt-v4 and driver dll binaries for us to look at?
Thanks,
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Fri 12/5/2008 1:08 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Robert and Wade,
Yes I have slogger running. Sloginfo has the following:
Time Sev Major Minor Args
Jan 01 00:00:00 5 14 0 tcpip starting
Jan 01 00:00:00 3 14 0 Unable to attach to pci server: No such file or directory
Jan 01 00:00:00 3 14 0 Using pseudo random generator. See "random" option
Jan 01 00:00:00 1 7 0 CTRL_DLL_INIT: imx31ads
Jan 01 00:00:01 2 19 900 devb-umass 1.00A (Oct 20 2008 23:28:34)
Jan 01 00:00:01 2 5 0 libcam.so (Oct 20 2008 23:22:15) bver 6040001
Jan 01 00:00:01 5 27 0 MME:mme_main(322): MME Version 1.1 built at Oct 21 2008 09:57:26
Jan 01 00:00:02 2 27 0 MME:slot_info_get(200): Got 0 rows from slot table for path "/dev/shmem"; expected 1.
Jan 01 00:00:03 2 5 100 cam-disk.so (Oct 20 2008 23:22:39)
Jan 01 00:00:03 2 5 0 scsi_interpret_sense: path=0, target=0, lun=0, cam_status=c4, scsi_status=2, flag=
000000c0,
vuflag=0008, cmd=0, error=70, sense=6,
asc=28, ascq=0
Jan 01 00:00:04 2 20 1 io-media-generic/trackplayer: Error 1:
Jan 01 00:00:04 2 20 1 io-media-generic/trackplayer: get_trkinfo: Problem with URL specified.
Jan 01 00:00:04 2 27 0 MME:getFileMetadata(82): Failed iom_get_track_info, errno = 5
Jan 01 00:01:48 5 21 0 run fault pid 5 tid 2 signal 11 code 1 ip 0x14402c proc/boot/io-pkt-v4
I have also attached the core dump for io-pkt-v4. I know I have experienced this a few times while debugging over the
last couple
of months, however I cannot recall if it was always when I was debugging resource managers. The one I am using at the
moment to
produce the problem is just a very simple pulse send/receive which is created from a few QNX examples. It is contained
within the
zip file for your reference.
Regards,
Radek.
-----Original Message-----
From: Wade Hawkins [mailto:community-noreply@qnx.com]
Sent: Friday, December 05, 2008 1:26 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek,
Also, does this happen with any project you debug or only your resource
manager?
-Wade
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: December 3, 2008 8:47 PM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek:
With regards to io-pkt-v4 disappearing, are you running slogger? Is
there any information in sloginfo? Can you run dumper and see if any
core files are created? What network driver are you using? Does your
application hit hardware in any way?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wed 12/3/2008 7:25 PM
To: momentics-community
Subject: Help on target debugging
Hi,
I am having problems trying to perform debugging on the target (i.MX31
ADS board). Basically I frequently encounter the two following issues:
* After launching a debug or run application on my target from withing
QNX Momentics IDE, my target's serial terminal connection gets affected
in such a way that I have to double-type each letter (as if
terminal-echoing was off). e.g. to change to the dev directory I'd have
to type it like "ccdd //ddeevv". The only way I know to fix the
problem is to reset the target board.
* After launching a couple debug or run applications on the target from
within the IDE, then after stopping or terminating the processes I find
that my running instances of "qconn" and "io-pkt-v4" disappear and as a
result I loose connectivity with the board.
Does anyone know why this may be happening or how to fix...
View Full Message
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/05/2008 3:32 PM
post18053
|
RE: Help on target debugging
I gave the test case a shot on my 640 Windows host targeting an
i.MX31ADS board and I don't see the same problem you are. So how about
we try setting up the same environment you have. Would you mind passing
me the build file you use to create the target image? Is your
development system stock 640?
-Wade
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: December 5, 2008 7:32 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek:
Just to be sure, can you also send us a copy of your io-pkt-v4 and
driver dll binaries for us to look at?
Thanks,
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Fri 12/5/2008 1:08 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Robert and Wade,
Yes I have slogger running. Sloginfo has the following:
Time Sev Major Minor Args
Jan 01 00:00:00 5 14 0 tcpip starting
Jan 01 00:00:00 3 14 0 Unable to attach to pci server: No such
file or directory
Jan 01 00:00:00 3 14 0 Using pseudo random generator. See
"random" option
Jan 01 00:00:00 1 7 0 CTRL_DLL_INIT: imx31ads
Jan 01 00:00:01 2 19 900 devb-umass 1.00A (Oct 20 2008 23:28:34)
Jan 01 00:00:01 2 5 0 libcam.so (Oct 20 2008 23:22:15) bver
6040001
Jan 01 00:00:01 5 27 0 MME:mme_main(322): MME Version 1.1
built at Oct 21 2008 09:57:26
Jan 01 00:00:02 2 27 0 MME:slot_info_get(200): Got 0 rows from
slot table for path "/dev/shmem"; expected 1.
Jan 01 00:00:03 2 5 100 cam-disk.so (Oct 20 2008 23:22:39)
Jan 01 00:00:03 2 5 0 scsi_interpret_sense: path=0,
target=0, lun=0, cam_status=c4, scsi_status=2, flag=000000c0,
vuflag=0008, cmd=0, error=70, sense=6,
asc=28, ascq=0
Jan 01 00:00:04 2 20 1 io-media-generic/trackplayer: Error 1:
Jan 01 00:00:04 2 20 1 io-media-generic/trackplayer:
get_trkinfo: Problem with URL specified.
Jan 01 00:00:04 2 27 0 MME:getFileMetadata(82): Failed
iom_get_track_info, errno = 5
Jan 01 00:01:48 5 21 0 run fault pid 5 tid 2 signal 11 code 1
ip 0x14402c proc/boot/io-pkt-v4
I have also attached the core dump for io-pkt-v4. I know I have
experienced this a few times while debugging over the last couple
of months, however I cannot recall if it was always when I was debugging
resource managers. The one I am using at the moment to
produce the problem is just a very simple pulse send/receive which is
created from a few QNX examples. It is contained within the
zip file for your reference.
Regards,
Radek.
-----Original Message-----
From: Wade Hawkins [mailto:community-noreply@qnx.com]
Sent: Friday, December 05, 2008 1:26 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek,
Also, does this happen with any project you debug or only your resource
manager?
-Wade
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: December 3, 2008 8:47 PM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek:
With regards to io-pkt-v4 disappearing, are you running slogger? Is
there any information in sloginfo? Can you run dumper and see if any
core files are created? What network driver are you using? Does your
application hit hardware in any way?
Robert.
-----Original Message-----
From: Radek Pesina [mailto:community-noreply@qnx.com]
Sent: Wed 12/3/2008 7:25 PM
To: momentics-community
Subject: Help on target debugging
Hi,
I am having problems trying to perform debugging on the target (i.MX31
ADS board). Basically I frequently encounter the two following issues:
* After launching a debug or run application on my target from withing
QNX Momentics IDE, my target's serial terminal connection gets affected
in such a way that I have to double-type each letter...
View Full Message
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/07/2008 5:32 PM
post18086
|
RE: Help on target debugging
Hi Robert and Wade,
I have attached my build files and binaries. Let me know if you need anything else. In terms of OS yes I am using the
standard
install of QNX 6.4.0 with Aviage Multimedia Suite 1.1.0 added on. The QNX Momentics IDE Build id is: I20081019.
Regards,
Radek.
-----Original Message-----
From: Wade Hawkins [mailto:community-noreply@qnx.com]
Sent: Saturday, December 06, 2008 7:33 AM
To: momentics-community
Subject: RE: Help on target debugging
I gave the test case a shot on my 640 Windows host targeting an
i.MX31ADS board and I don't see the same problem you are. So how about
we try setting up the same environment you have. Would you mind passing
me the build file you use to create the target image? Is your
development system stock 640?
-Wade
-----Original Message-----
From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: December 5, 2008 7:32 AM
To: momentics-community
Subject: RE: Help on target debugging
Hi Radek:
Just to be sure, can you also send us a copy of your io-pkt-v4 and
driver dll binaries for us to look at?
Thanks,
Robert.
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post18053
|
|
|
|
|
|
|
Re: Help on target debugging
|
|
12/08/2008 5:50 PM
post18175
|
Re: Help on target debugging
Can I ask why aren't you running a serial driver? The default /dev/text is a rather primitive debug device, and very
expensive (it uses the debug callouts,
char by char).
Colin
Radek Pesina wrote:
> Hi Robert and Wade,
>
> I have attached my build files and binaries. Let me know if you need anything else. In terms of OS yes I am using
the standard
> install of QNX 6.4.0 with Aviage Multimedia Suite 1.1.0 added on. The QNX Momentics IDE Build id is: I20081019.
>
> Regards,
> Radek.
>
>
>
> -----Original Message-----
> From: Wade Hawkins [mailto:community-noreply@qnx.com]
> Sent: Saturday, December 06, 2008 7:33 AM
> To: momentics-community
> Subject: RE: Help on target debugging
>
> I gave the test case a shot on my 640 Windows host targeting an
> i.MX31ADS board and I don't see the same problem you are. So how about
> we try setting up the same environment you have. Would you mind passing
> me the build file you use to create the target image? Is your
> development system stock 640?
>
> -Wade
>
> -----Original Message-----
> From: Robert Craig [mailto:community-noreply@qnx.com]
> Sent: December 5, 2008 7:32 AM
> To: momentics-community
> Subject: RE: Help on target debugging
>
>
> Hi Radek:
> Just to be sure, can you also send us a copy of your io-pkt-v4 and
> driver dll binaries for us to look at?
>
> Thanks,
> Robert.
>
>
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post18053
>
>
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post18086
--
cburgess@qnx.com
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/08/2008 7:23 PM
post18176
|
RE: Help on target debugging
Hi Colin and Elena,
I'm not sure I understand fully what you mean. I am using the serial driver for the ksh terminal and if I type "pidin
fd" then I
can see that each relevant process is using /dev/ser1. How should I configure it to not start /dev/text?
I have attached the tracelogger file. It covers executing the demo programs on the target and yes the connection
dropped-out at the
end. I could extract the kev file via USB mass storage.
Regards,
Radek
-----Original Message-----
From: Colin Burgess [mailto:community-noreply@qnx.com]
Sent: Tuesday, December 09, 2008 9:51 AM
To: momentics-community
Subject: Re: Help on target debugging
Can I ask why aren't you running a serial driver? The default /dev/text is a rather primitive debug device, and very
expensive (it
uses the debug callouts,
char by char).
Colin
Radek Pesina wrote:
> Hi Robert and Wade,
>
> I have attached my build files and binaries. Let me know if you need anything else. In terms of OS yes I am using
the standard
> install of QNX 6.4.0 with Aviage Multimedia Suite 1.1.0 added on. The QNX Momentics IDE Build id is: I20081019.
>
> Regards,
> Radek.
>
>
>
> -----Original Message-----
> From: Wade Hawkins [mailto:community-noreply@qnx.com]
> Sent: Saturday, December 06, 2008 7:33 AM
> To: momentics-community
> Subject: RE: Help on target debugging
>
> I gave the test case a shot on my 640 Windows host targeting an
> i.MX31ADS board and I don't see the same problem you are. So how about
> we try setting up the same environment you have. Would you mind passing
> me the build file you use to create the target image? Is your
> development system stock 640?
>
> -Wade
>
> -----Original Message-----
> From: Robert Craig [mailto:community-noreply@qnx.com]
> Sent: December 5, 2008 7:32 AM
> To: momentics-community
> Subject: RE: Help on target debugging
>
>
> Hi Radek:
> Just to be sure, can you also send us a copy of your io-pkt-v4 and
> driver dll binaries for us to look at?
>
> Thanks,
> Robert.
>
>
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post18053
>
>
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post18086
--
cburgess@qnx.com
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post18175
|
|
|
|
|
|
|
Re: Help on target debugging
|
|
12/08/2008 10:29 AM
post18124
|
Re: Help on target debugging
Is there qconn core file as well? Can you attached qconn binary and core if it is generated?
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/08/2008 5:25 PM
post18172
|
RE: Help on target debugging
Hi Elena,
From memory there was no qconn core dump file. Of course now that I want it to crash, it won't therefore I'm having
trouble
confirming. However after starting a debug session the terminal is still going funny on me (requiring me to type each
letter twice)
and I am loosing connectivity with the board. Although even once connectivity is lost io-pk4-v4 and qconn are still
running. The
qconn binary is within the zip file of my reply on 12/07/2008 5:32 PM.
Regards,
Radek.
-----Original Message-----
From: Elena Laskavaia [mailto:community-noreply@qnx.com]
Sent: Tuesday, December 09, 2008 2:30 AM
To: momentics-community
Subject: Re: Help on target debugging
Is there qconn core file as well? Can you attached qconn binary and core if it is generated?
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post18124
|
|
|
|
|
|
|
Re: Help on target debugging
|
|
12/08/2008 5:34 PM
post18173
|
Re: Help on target debugging
Can you run tracelogger for last seconds of debugging session, I am not sure what exactly going on there.
Create a Log session from IDE that lasts maybe 20 seconds in Wide mode for your target, save it but not launch yet.
Start debugging.
Just before ending debug session start logging session, quickly switch to debug session and stop it. If connectivity is
lost you probably won't get trace back
but log file will be stored on target (.kev file). Can you get this file some-how so we can see it?
Radek Pesina wrote:
> Hi Elena,
>
> From memory there was no qconn core dump file. Of course now that I want it to crash, it won't therefore I'm having
trouble
> confirming. However after starting a debug session the terminal is still going funny on me (requiring me to type each
letter twice)
> and I am loosing connectivity with the board. Although even once connectivity is lost io-pk4-v4 and qconn are still
running. The
> qconn binary is within the zip file of my reply on 12/07/2008 5:32 PM.
>
> Regards,
> Radek.
>
> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: Tuesday, December 09, 2008 2:30 AM
> To: momentics-community
> Subject: Re: Help on target debugging
>
> Is there qconn core file as well? Can you attached qconn binary and core if it is generated?
>
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post18124
>
> _______________________________________________
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post18172
>
|
|
|
|
|
|
|
Re: Help on target debugging
|
|
12/11/2008 4:49 PM
post18450
|
Re: Help on target debugging
I checked the kev file. Qconn get blocked on devc-sermx1. It sends a message and does not get a reply so it is toasted
unless you re-start this driver. Probably your double enter of symbols is related to the same driver.
Is it standard qnx driver?
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/11/2008 4:58 PM
post18453
|
RE: Help on target debugging
Hi Elena,
Yes devc-sermx1 is a standard QNX driver -supplied with the i.MX31 ADS BSP.
Regards,
Radek.
-----Original Message-----
From: Elena Laskavaia [mailto:community-noreply@qnx.com]
Sent: Friday, December 12, 2008 8:50 AM
To: momentics-community
Subject: Re: Help on target debugging
I checked the kev file. Qconn get blocked on devc-sermx1. It sends a message and does not get a reply so it is toasted
unless you
re-start this driver. Probably your double enter of symbols is related to the same driver.
Is it standard qnx driver?
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post18450
|
|
|
|
|
|
|
Re: Help on target debugging
|
|
12/11/2008 5:13 PM
post18455
|
Re: Help on target debugging
Are you debugging through serial connection or via TCP/IP?
Radek Pesina wrote:
> Hi Elena,
>
> Yes devc-sermx1 is a standard QNX driver -supplied with the i.MX31 ADS BSP.
>
> Regards,
> Radek.
>
>
|
|
|
|
|
|
|
RE: Help on target debugging
|
|
12/11/2008 5:41 PM
post18457
|
RE: Help on target debugging
Hi Elena,
I am using the serial port for the terminal/ksh. Debugging is being performed over TCP/IP using the Ethernet connection
.
Regards,
Radek.
-----Original Message-----
From: Elena Laskavaia [mailto:community-noreply@qnx.com]
Sent: Friday, December 12, 2008 9:13 AM
To: momentics-community
Subject: Re: Help on target debugging
Are you debugging through serial connection or via TCP/IP?
Radek Pesina wrote:
> Hi Elena,
>
> Yes devc-sermx1 is a standard QNX driver -supplied with the i.MX31 ADS BSP.
>
> Regards,
> Radek.
>
>
_______________________________________________
QNX Momentics Community Support
http://community.qnx.com/sf/go/post18455
|
|
|
|
|
|
|
Re: Help on target debugging
|
|
12/12/2008 8:57 AM
post18487
|
Re: Help on target debugging
Can you try to debug without using serial terminal? Using telnet instead for example?
Radek Pesina wrote:
> Hi Elena,
>
> I am using the serial port for the terminal/ksh. Debugging is being performed over TCP/IP using the Ethernet
connection.
>
> Regards,
> Radek.
>
>
|
|
|
|
|
|