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

Developer

Forums

Forums:

I was just curious to find out if there are any plans on Qualcomm's behalf to have on-device debugging any time soon. Maybe someone here has heard anything down those lines, or maybe a Qualcomm official could answer this, please.

Given the fact that the emulator has virtually nothing in common with the actual devices it would certainly make a lot of things easier to finally get the opportunity to run and debug code on the actual handsets. The outdated and overpriced Z800 solution is really not very interesting. A little stub that communicates with a remote debugger would go a long way and should really have been part of the 1.0 SDK already.

Oh that would be so great. A feature frequently asked for since day 1. I'm sure Metrowerks could get it going too--if only Metrowerks and Qualcomm could get it together with BREW Codewarrior. I'm not a GIANT Codewarrior fan, but I'd definitely buy a BREW version of it if it had on-device debugging like they do for Java (on select devices).
Ah....to sleep...perhance, to dream.

Oh that would be so great. A feature frequently asked for since day 1. I'm sure Metrowerks could get it going too--if only Metrowerks and Qualcomm could get it together with BREW Codewarrior. I'm not a GIANT Codewarrior fan, but I'd definitely buy a BREW version of it if it had on-device debugging like they do for Java (on select devices).
Ah....to sleep...perhance, to dream.

I'm not a fan of Metroworks' 70s technology either - as a matter of fact I try to steer clear of their software as good as I can - but if it offered Brew on-device debugging, like you, I would buy it for that feature alone.

I'm not a fan of Metroworks' 70s technology either - as a matter of fact I try to steer clear of their software as good as I can - but if it offered Brew on-device debugging, like you, I would buy it for that feature alone.

There are plans. See the tools presentation from BREW 2003:
http://www.qualcomm.com/brew/images/press_room/events/brew_2003/pdf/BREW...
(Pages 18-23.)

There are plans. See the tools presentation from BREW 2003:
http://www.qualcomm.com/brew/images/press_room/events/brew_2003/pdf/BREW...
(Pages 18-23.)

if only the tools were as cool as the PDF.

if only the tools were as cool as the PDF.

You're speaking my mind.

You're speaking my mind.

I think the on device debugger is due out early next year.

I think the on device debugger is due out early next year.

I would like even the simplest of on-device debuggers. it would help sooo much.
I hope QC's not waiting to make a really cool debugger before releasing what they demo'd at the '03 conf.
Nick

I would like even the simplest of on-device debuggers. it would help sooo much.
I hope QC's not waiting to make a really cool debugger before releasing what they demo'd at the '03 conf.
Nick

I've heard at GDC that they're actually REALLY close to releasing it. As a matter of fact I talked to someone who said "It's here!" though I could not yet corroborate that.

I've heard at GDC that they're actually REALLY close to releasing it. As a matter of fact I talked to someone who said "It's here!" though I could not yet corroborate that.

That's good news.
BREW will become much more attractive to my organization when the on device debugger is released.
We're game for beta testing it, even if it crashes horribly; any rudimentary on-device debugger would be beneficial to us this very second.
Dragon I hope your contact is right.

That's good news.
BREW will become much more attractive to my organization when the on device debugger is released.
We're game for beta testing it, even if it crashes horribly; any rudimentary on-device debugger would be beneficial to us this very second.
Dragon I hope your contact is right.

You know after all this time, I don't even need an on-device debugger that much any more. ;-) It's been so long that I've developed all sorts of other debug mechanisms... bizarre, isn't it? But still there are cases where it will save a lot of time and no development enironment is complete without proper target debugging.

You know after all this time, I don't even need an on-device debugger that much any more. ;-) It's been so long that I've developed all sorts of other debug mechanisms... bizarre, isn't it? But still there are cases where it will save a lot of time and no development enironment is complete without proper target debugging.

The BREW Debugger requires IPort, so it won't really be available until BREW 3.1.
However, it's looking mighty useful. :)

The BREW Debugger requires IPort, so it won't really be available until BREW 3.1.
However, it's looking mighty useful. :)

Just give me JTAG support and let me be :)

Just give me JTAG support and let me be :)

I see the JTAG port (under sticker) on the VX6000, does anybody have experience using JTAG on a BREW phone?

I see the JTAG port (under sticker) on the VX6000, does anybody have experience using JTAG on a BREW phone?

Rumor is that there will be a demo of the Debugger given at some point in the near future... ;)

Rumor is that there will be a demo of the Debugger given at some point in the near future... ;)

Thanks max. u r teh funny.
I hope to see you at the Conference!!!
;) Looking forward to it!

Thanks max. u r teh funny.
I hope to see you at the Conference!!!
;) Looking forward to it!

i use JTAG debugging, it works well.
But be aware just because a phone has a JTAG port, doesn't always mean the firmware has support for it, all the phones have a jtag socket, not all of them can use it, generally you have to get a phone thats setup for JTAG support, not an off the shelf one.

i use JTAG debugging, it works well.
But be aware just because a phone has a JTAG port, doesn't always mean the firmware has support for it, all the phones have a jtag socket, not all of them can use it, generally you have to get a phone thats setup for JTAG support, not an off the shelf one.

I am envious! Would a JTAG-compatible phone & debug setup be something I'd want to contact my carrier for?

I am envious! Would a JTAG-compatible phone & debug setup be something I'd want to contact my carrier for?

They might be able to help, there was company modifying Z800s to add JTAG and a debugger a while ago for $5000, I don't know if they are still doing it , still charging a ridculous amount or if they are using a newer phone, the details were in the old mailing list i think

They might be able to help, there was company modifying Z800s to add JTAG and a debugger a while ago for $5000, I don't know if they are still doing it , still charging a ridculous amount or if they are using a newer phone, the details were in the old mailing list i think

Can anybody help understerdand this :
http://brew.qualcomm.com/brew_bnry/pdf/events/brew_2003/BREWToolsOvervie...
"The On-Target Debugger allows the developer to execute classical
debugging commands (breakpoints, watches, etc) on GCC compiled code
running on the target platform. Composed of a client running on phone and
front-end UI on PC."
Does it means that is already available? has anyone tried something like this?

Can anybody help understerdand this :
http://brew.qualcomm.com/brew_bnry/pdf/events/brew_2003/BREWToolsOvervie...
"The On-Target Debugger allows the developer to execute classical
debugging commands (breakpoints, watches, etc) on GCC compiled code
running on the target platform. Composed of a client running on phone and
front-end UI on PC."
Does it means that is already available? has anyone tried something like this?

they'll just be just using gdb to debug with a stub, no doubt its not finished yet.
JTAG is considerably superior but theres a lot of paranoia about what you can do with it.

they'll just be just using gdb to debug with a stub, no doubt its not finished yet.
JTAG is considerably superior but theres a lot of paranoia about what you can do with it.