On device debugging of Qt Application: SISX not installable with TRK

[axeljaeger]

Hello,
motivated by the usefull link in ltomuta's signature, I wanted to give on device debuggin a try. I went through the steps but because I debug a Qt application, my .mmp file has some more entries than the one shown in the video. I can build my application just fine and can install it using nokia software installer but I get an error about an expired certificate when trying to debug on the device. I get the same warning even when I uncheck "Do not show installer on phone" on the phonescreen then.

The device is a 5800 XM but I think the error is not related to the bug mentioned elsewhere about some software but because installing using nokia software installer works just fine.

I saw that in the video, the vendor id was commented out before on device debugging. I do not have such a line in my project but two other lines regarding UIDs:

UID 0x100039CE 0xE635F0EC
SECUREID 0xE635F0EC

I want to use self signed certificate for now.

Any ideas?

[ltomuta]

Ok, so the same sis file can be installed on the device through normal process but when installed through Carbide.c++ it gives a certificate expired error? What is the exact error message and is it displayed by the phone or by Carbide?

Also, is your phone's time in sync with the PC? You should make sure that the phone time is at least a few seconds ahead the PC, maybe a full minute. That would ensure that even if the file is sent to the phone soon after the certificate created the date would still be in the past and thus the certificate is valid.

[axeljaeger]

Setting the clock 2 minutes ahead did indeed solve my problem, thanks a lot. The development system is a vista vm on a macbook and I think both clocks get synced using an ntp-server. Now with on device debugging, developing will get more fun. So now I'm only wondering how to make Carbide only rebuild the executable when needed /only rebuild changed sources because now it compiles everything for every debug session which slows down development. I hoped that on-device-debugging would save me from using the emulator.

[ltomuta]

This article might help you improve your work with the emulator: http://wiki.forum.nokia.com/index.ph...arbide.c%2B%2B

As for Carbide building only what/when needed do have a look at Carbide/Project's settings, you will be able to tweak a thing or two. I don't have a Carbide.c++ on this laptop so I can't give you more guidance but at least the "when needed" part should be doable.

[axeljaeger]

I think checking "partial upgrade" did help a bit imroving build times.

[suresh.venkata]

You can configure carbide project settings to avoid building the project every time you launch the project in debugger, I observed this setting present at different menus for different carbide versions.

The carbide that i used has it in debug configurations :

Here is the debug configuration information of my console_app:

Symbian OS Emulation :
console_app Emulator Debug (WINSCW)

In Main tab :

Project : console_app
Process to launch : J:\epoc32\RELEASE\WINSCW\udeb\console_app.exe

Build (if required) before launching
(0) Disable auto build
(0) Enable auto build
(0) Use workspace settings

I always used the first option above to disable auto build. Don't know why, Carbide always builds the project even if nothing has changed in project from its previous launch.

I wish i could post screen shot of settings, "Insert image" option of forum asks for "http://.." address

[ltomuta]

You can host the screenshot somewhere else, like on http://share.ovi.com for example

[suresh.venkata]

axeljaeger: Screenshots

In debug configurations :

http://share.ovi.com/media/suresh122...resh1226.10001

In Window->Preferences :
http://share.ovi.com/media/suresh122...resh1226.10002

Un-check General options

-Suresh.

[Nokia Ron]

You need image file types to appear as inline images.

Ron