Forums | developer.brewmp.com Forums | developer.brewmp.com

Developer

Forums

Forums:

Hi Guys,

I have another challenging question. I have an application running on v9m that connects though PPP (inetmgr) to a server, but i need an application to do a trace of how the ppp/chap connection is being established, so as to trace my connection via the operator's network to my server. I tried to use hyperterminal and applogger but did not give me what i want. Any help?

" .... i hope i will replies to this question... i dont usually get enough replies to my questions..."

Thanks.

Ola.

Is my question offline? Please let someone reply me.
Thanks

Is my question offline? Please let someone reply me.
Thanks

ola wrote:Hi Guys,
I have another challenging question. I have an application running on v9m that connects though PPP (inetmgr) to a server, but i need an application to do a trace of how the ppp/chap connection is being established, so as to trace my connection via the operator's network to my server. I tried to use hyperterminal and applogger but did not give me what i want. Any help?
Thanks.
Ola.
By using BREW debug sequences, a BREW developer may have an easier time diagnosing the cause of application errors.Use debug modes to print debug messages.
For eg:
Memory validation (Debug number 1 on all BREW versions)
Network debugging (Debug number 2 on all BREW versions)
BREW-directed SMS debug (Debug number 11 on BREW 3.1.0+)
Launch debug app (Debug number 324 on BREW 3.1.5+) - This one is particularly useful to print deug messages from AEE layer API's which otherwise is disabled..
Quote:Many BREW APIs print helpful debug messages using DBGPRINTF(), but these messages are typically disabled in official BREW releases. Starting in BREW 3.1.5 these debug messages can be selectively turned on through the debug app. Entering this debug mode will launch the debug application allowing a developer to change the debug message settings for various BREW APIs.
This link has all information
BREW Debug Sequences
https://brewx.qualcomm.com/bws/websites/dx/en/brew31/ad/kb/running_apps/...
If you cannot access this document, the below document in BREW conference'08 is good enough - more or less the same information (you can say this one is the latest)
PROG-601 - BREW Debugging for Developers & OEMs
http://brew.qualcomm.com/brew_bnry/pdf/brew_2008/PROG-601.pdf
This will work if the OEM has not changed the default sequence code for handset, if not you might have to get that information from somewhere.. Probably someone might have posted that info in the forum.
Search in this form for "debug sequence" or "debug modes", you will get useful information.

ola wrote:Hi Guys,
I have another challenging question. I have an application running on v9m that connects though PPP (inetmgr) to a server, but i need an application to do a trace of how the ppp/chap connection is being established, so as to trace my connection via the operator's network to my server. I tried to use hyperterminal and applogger but did not give me what i want. Any help?
Thanks.
Ola.
By using BREW debug sequences, a BREW developer may have an easier time diagnosing the cause of application errors.Use debug modes to print debug messages.
For eg:
Memory validation (Debug number 1 on all BREW versions)
Network debugging (Debug number 2 on all BREW versions)
BREW-directed SMS debug (Debug number 11 on BREW 3.1.0+)
Launch debug app (Debug number 324 on BREW 3.1.5+) - This one is particularly useful to print deug messages from AEE layer API's which otherwise is disabled..
Quote:Many BREW APIs print helpful debug messages using DBGPRINTF(), but these messages are typically disabled in official BREW releases. Starting in BREW 3.1.5 these debug messages can be selectively turned on through the debug app. Entering this debug mode will launch the debug application allowing a developer to change the debug message settings for various BREW APIs.
This link has all information
BREW Debug Sequences
https://brewx.qualcomm.com/bws/websites/dx/en/brew31/ad/kb/running_apps/...
If you cannot access this document, the below document in BREW conference'08 is good enough - more or less the same information (you can say this one is the latest)
PROG-601 - BREW Debugging for Developers & OEMs
http://brew.qualcomm.com/brew_bnry/pdf/brew_2008/PROG-601.pdf
This will work if the OEM has not changed the default sequence code for handset, if not you might have to get that information from somewhere.. Probably someone might have posted that info in the forum.
Search in this form for "debug sequence" or "debug modes", you will get useful information.

The above mentioned note helps you to see useful debug messages related to networking.
To capture PPP logs, you need another Qualcomm tool known as QXDM. BREW logger is a basic version of message logging without additional support. With QXDm, you can capture PPP logs from the messages printed by handset and use Wireshark/Ethereal to analyse the PPP logs.

The above mentioned note helps you to see useful debug messages related to networking.
To capture PPP logs, you need another Qualcomm tool known as QXDM. BREW logger is a basic version of message logging without additional support. With QXDm, you can capture PPP logs from the messages printed by handset and use Wireshark/Ethereal to analyse the PPP logs.

Thanks.
Pls, where can I get the QAXM tool for download?

Thanks.
Pls, where can I get the QAXM tool for download?