Reply
Thread Tools
Posts: 304 | Thanked: 176 times | Joined on Oct 2009
#1
Hello everyone, I've been having trouble with the Nokia QT SDK for Windows 7 64 bit. Can anyone suggest an alternative or solution to my problems?

I am developing an OpenGL ES 2.0 application using QT 4.7.

The first problem I'm having is that the USB Network connection between my desktop and my N900 continually disconnects. At most I can either get 1 or 2 builds sent to my N900 before it times out and complains about "Host not found." What I've been doing is disconnecting the usb connection and reconnecting it. This sometimes fixes the problem for a few mintes (I get to send a build or 2) but then it disconnects again.

When it's not disconnection issues it's rebooting issues. Whenever the N900 feels like connecting successfully, 50% of the time my N900 reboots automatically during the deployment stage when I try to run my application. Here's the output:

Code:
Cleaning up remote leftovers first ...
Initial cleanup done.
Files to deploy: C:/Users/XXXXXX/Documents/Visual Studio 2010/Projects/cityGLes2\citygles2_0.0.1_armel.deb.
*N900 REBOOTS HERE*
Deployment failed: Could not uplodad file 'C:/Users/XXXXXX/Documents/Visual Studio 2010/Projects/cityGLes2\citygles2_0.0.1_armel.deb':
I don't know what's causing this. This happens not only to my application but also every QT example application I build and run using this method.

My 3rd issue is that I'm unable to use the Maemo Emulator to test my OpenGL ES 2.0 application. First, is there a method to accelerate performance of the emulator? It's incredibly slow and choppy even on my beefy desktop (Less than 1 frame/sec in ui/menus). Also, although I successfully linked the emulator with QT creator, opengl es 2.0 applications are unable to run because the SDK complains about the emulator's drivers being 24bit and it's looking for a 16bit environment.
Edit: It's this
Code:
Warning: EGL suggested using X Visual ID 33 (ARGB0888) EGL config 1 (ARGB8888), but this is incompatable
That's outputted in the SDK. I then found this
http://bugreports.qt.nokia.com/browse/QTBUG-9444
Marked as invalid?

I've tried using esbox on a native linux installation but I'm having the same emulation issues (turtle emulation,etc.)

Nokia QT SDK is fully up to date and I've got the latest version of Mad Developer on my N900 (from extras, version same as devel).

Can anyone suggest any solutions/workarounds/alternatives? Thanks!

Last edited by jessi3k3; 2010-12-03 at 06:25.
 
ossipena's Avatar
Posts: 3,159 | Thanked: 2,023 times | Joined on Feb 2008 @ Finland
#2
can you use wlan for data transfer? I once tried with USB but forgot it as soon as I realized that I simply can connect my N900 to same wlan with my pc and voila....
__________________
Want to know something?
K.I.S.S. approach:
wiki category:beginners. Browse it through and you'll be much wiser!
If the link doesn't help, just use
Google Custom Search
 
Posts: 304 | Thanked: 176 times | Joined on Oct 2009
#3
Originally Posted by ossipena View Post
can you use wlan for data transfer? I once tried with USB but forgot it as soon as I realized that I simply can connect my N900 to same wlan with my pc and voila....
I'll give it a shot if I'm able to set an ad-hoc network between my desktop (I have a small usb 802.11g adapter) and my N900. That would at least maybe solve the disconnecting issue.

Edit: Well, that only took 30 seconds to configure. Wow! That gets rid of the first problem. No disconnection issues thus far *knock on wood*

Last edited by jessi3k3; 2010-12-03 at 05:56.
 
Posts: 440 | Thanked: 160 times | Joined on Aug 2010 @ Las Vegas, NV
#4
why not to try maemo emulator built in nokia qt sdk to test and test it in n900 only when there has been significant changes in code to test.
 
Posts: 304 | Thanked: 176 times | Joined on Oct 2009
#5
Ive been using the wireless connection and I havent had the first 2 problems I described. I'm guessing those 2 were inherited by using the problematic usb networking.

Originally Posted by Joseph9560 View Post
why not to try maemo emulator built in nokia qt sdk to test and test it in n900 only when there has been significant changes in code to test.
Many of my changes thus far have been visual (implementing new visual features, modifying/adding vertex+fragment shaders, etc.) and, as I described in problem 3, the program does not even start in the emulator because it fails to render the opengl window. It just hangs in the beginning and I have to manually halt the program through the sdk. I'm also aiming for smooth performance (>30 fps, right now it's 60-80+ avg with just primitives) and if the speed of ui in the emulator is an indication on how it will run then it wont be very useful.
 
Reply


 
Forum Jump


All times are GMT. The time now is 16:59.