Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - For ever frozen: (4 Items)
   
For ever frozen  
While the system profiler is uploading the trace event file ,the target networking component dies.  On the IDE  side 
there is no way to close the the dialog  showing the progress of the download.  The cancel button is grayed out.  The 
details button works though.  

Only solution is to exit from the IDE.

If anyone heard of qconn making networking die I'm interested because that is the only way I can make it die (no more 
interrupts genereated).  Any other type of network activity is ok.  I can copy the .kev file manually no problem, if I 
manually run tracelogger ...
RE: For ever frozen  
I will send pr about it to IDE, because it should just cancel download when
network timeout occurs... 
I had network driver die before (on x86 board), you probably should post
this issue on networking or bsp forum, maybe they have some patches for that
driver you have.
Which method you are using for tracelogging from IDE - save on target and
download or streaming?
Re: RE: For ever frozen  
> I will send pr about it to IDE, because it should just cancel download when
> network timeout occurs... 
> I had network driver die before (on x86 board), you probably should post
> this issue on networking or bsp forum, maybe they have some patches for that
> driver you have.
> Which method you are using for tracelogging from IDE - save on target and
> download or streaming?


Save on target and download.  
Re: RE: For ever frozen  
> I will send pr about it to IDE, because it should just cancel download when
> network timeout occurs... 
> I had network driver die before (on x86 board), you probably should post
> this issue on networking or bsp forum, maybe they have some patches for that
> driver you have.
> Which method you are using for tracelogging from IDE - save on target and
> download or streaming?


I just tried streaming and this time the IDE didn't freeze even though the network driver died anyway.

The IDE didn't seem to have detected the driver died though.  It's only when it tried to display the data that it showed
 some error.