bladox.com Forum Index bladox.com
Turbo SIM Toolkit Adapter Forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Debugger output

 
Post new topic   Reply to topic    bladox.com Forum Index -> General
View previous topic :: View next topic  
Author Message
Kl0f
Guest
PostPosted: Wed Nov 17, 2004 1:29 pm    Post subject: Debugger output Reply with quote
Hi guys

I an using the debugger tool allot for tracking STK bugs in handsets, I would like to suggest a easier way of displaying the trace data on screen, rather then the current 'flow' of hex.

Here is a screenshot of another trace tool I use, it give a very good overview of the communication, and then you can view details of each command if you click the tree-structure, nice.

Now, I know this would be allot of work for you, coding an actual client for tracing, I just wanted to give you inspiration for future work.

BR
Per
Back to top
pz
Guest
PostPosted: Thu Nov 18, 2004 12:11 pm    Post subject: Re: Debugger output Reply with quote
Kl0f wrote:
Hi guys

I an using the debugger tool allot for tracking STK bugs in handsets, I would like to suggest a easier way of displaying the trace data on screen, rather then the current 'flow' of hex.

Here is a screenshot of another trace tool I use, it give a very good overview of the communication, and then you can view details of each command if you click the tree-structure, nice.

Now, I know this would be allot of work for you, coding an actual client for tracing, I just wanted to give you inspiration for future work.

BR
Per


This should be fairly easy, only that we are the worst gui and windows developers you can imagine (ok, not that bad but it's not priority). It could be just post-processor for the hex output.

What we find pretty on the plain text output is that you can:
- easily add notes with your favourite editor
- use "diff" and "grep" utilities to compare/search output files
We do both all the time.

Anyway if you needed anything to be added into the hex/text output (e.g. some stamps for postprocessing) feel free to ask/demand/request/bug.

Thanks for idea.
Back to top
Guest
PostPosted: Thu Nov 18, 2004 1:34 pm    Post subject: Reply with quote
Im not really a hardcore GUI coder myself Smile
And besides that, im a Linux noob, so I didnt think of the grep/diff possibilities, but ill get familiar with the Linux commands!

Thanks!

Br
Per
Back to top
Nand Kumar
Guest
PostPosted: Tue Jan 10, 2006 8:28 am    Post subject: Re: Debugger output Reply with quote
Kl0f wrote:
Hi guys

I an using the debugger tool allot for tracking STK bugs in handsets, I would like to suggest a easier way of displaying the trace data on screen, rather then the current 'flow' of hex.

Here is a screenshot of another trace tool I use, it give a very good overview of the communication, and then you can view details of each command if you click the tree-structure, nice.

Now, I know this would be allot of work for you, coding an actual client for tracing, I just wanted to give you inspiration for future work.

BR
Per




Hi
May I know which debugger is this and from where it can be downloaded.
Or what are methods for debugging in Turbo Programmer.

Thanks in Advance
Nand Kumar.
Back to top
pz
Guest
PostPosted: Wed Jan 11, 2006 8:41 am    Post subject: Re: Debugger output Reply with quote
Nand Kumar wrote:
Kl0f wrote:
Hi guys

I an using the debugger tool allot for tracking STK bugs in handsets, I would like to suggest a easier way of displaying the trace data on screen, rather then the current 'flow' of hex.

Here is a screenshot of another trace tool I use, it give a very good overview of the communication, and then you can view details of each command if you click the tree-structure, nice.

Now, I know this would be allot of work for you, coding an actual client for tracing, I just wanted to give you inspiration for future work.

BR
Per




Hi
May I know which debugger is this and from where it can be downloaded.
Or what are methods for debugging in Turbo Programmer.

Thanks in Advance
Nand Kumar.


This output is not from our "dbg" utility, it's someone else product. We (bladox) have few different debug kernels for turbo sim toolkit adapter:
- L1 debug kernel - prints all SIM<->Turbo<->ME communication in hex, incl turbo interferences (modifications)
- L2 debug kernel - as L1 but more readable output with some 11.11 and 11.14 parsing
- L1 raw debug kernel - as L1 but without any turbo interferences, just pass thru

"dbg" has '-t' option to meassure time elapsed
Back to top
Display posts from previous:   
Post new topic   Reply to topic    bladox.com Forum Index -> General All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group