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

Developer

Forums

Forums:

I am using an application as an extension with my main application.
On starting the application, i get the error message flashed on the screen

EXCEPTION
Undef Inst

lr = FFICE128
tk= 010E1E04

Could you please help me to sort the problem out.....

Are you compiling the application in proper endian? Have you tried debugging to see where this app is crashing?

Are you compiling the application in proper endian? Have you tried debugging to see where this app is crashing?

:mad: Hi Jonathan,
Could you please give me some helpful links regarding this proper endian thing. I have run the application on the emulator, its working perfectly fine on the emulator, then where do i need to debug for the handset?
Thanks
Robin

:mad: Hi Jonathan,
Could you please give me some helpful links regarding this proper endian thing. I have run the application on the emulator, its working perfectly fine on the emulator, then where do i need to debug for the handset?
Thanks
Robin

Well the DDS claims the endianess of the device, but I doubt that is your issue.
I would first try setting debug statements throughout your code to see where it is crashing. :rolleyes:

Well the DDS claims the endianess of the device, but I doubt that is your issue.
I would first try setting debug statements throughout your code to see where it is crashing. :rolleyes:

:) Hey,
I had not included the extension's class ID in the dependencies of the main application. Now i have done the same and the application is running properly on the handset. However, on the emulator i m able to connect to the server, but on the handset (Verizon service), the set is unable to connect to the server. Any known issues....??
Thanks,
Robin

:) Hey,
I had not included the extension's class ID in the dependencies of the main application. Now i have done the same and the application is running properly on the handset. However, on the emulator i m able to connect to the server, but on the handset (Verizon service), the set is unable to connect to the server. Any known issues....??
Thanks,
Robin

What error values are you seeing? Maybe a host to net byte order issue.

What error values are you seeing? Maybe a host to net byte order issue.

Hi,
The application is for LGVx7000 and is tested on the client's end cz we dont have the operators supporting the handset here, so i can not tell the error codes received.
However, I tried the same application on a low resolution handset, Kyocera KX414 with Tata, but on this handset i am still facing the same problem ,
UNDEF INST.....and i have to restart the handset
cant i test the application at my end using the Kyocera handset?
If yes then why am i facing the problem. I loaded the same application here on LGVx7000 without any operator. The application exectued properly.
Thanks,
Robin

Hi,
The application is for LGVx7000 and is tested on the client's end cz we dont have the operators supporting the handset here, so i can not tell the error codes received.
However, I tried the same application on a low resolution handset, Kyocera KX414 with Tata, but on this handset i am still facing the same problem ,
UNDEF INST.....and i have to restart the handset
cant i test the application at my end using the Kyocera handset?
If yes then why am i facing the problem. I loaded the same application here on LGVx7000 without any operator. The application exectued properly.
Thanks,
Robin

What SDK are you compiling against? Have you tried debugging to see where the code is crashing? Without the code in front of me, it's kind of hard to guess...

What SDK are you compiling against? Have you tried debugging to see where the code is crashing? Without the code in front of me, it's kind of hard to guess...

Hi,
I am compiling the application using BREW 2.1.0. Not using any new API's that are not in 2.0.x (guess Kyocera KX 414 supports 2.0.3) . So i dont think it is creating any problem. I Dont know whether CONVERTBMP is supported in 2.0.3.
If it is supported in 414, then, at least the application should run, images and the screen may be garbled...and one more thng... i tried on KX414 simulator, it is working properly on KX414 simulator, then on the handset, why does the application even fail to start?
Thanks

Hi,
I am compiling the application using BREW 2.1.0. Not using any new API's that are not in 2.0.x (guess Kyocera KX 414 supports 2.0.3) . So i dont think it is creating any problem. I Dont know whether CONVERTBMP is supported in 2.0.3.
If it is supported in 414, then, at least the application should run, images and the screen may be garbled...and one more thng... i tried on KX414 simulator, it is working properly on KX414 simulator, then on the handset, why does the application even fail to start?
Thanks

you can not compile an app in 2.1 and run it on a 2.0 handset. It may work sometimes, but it is likely to cause a crash.

you can not compile an app in 2.1 and run it on a 2.0 handset. It may work sometimes, but it is likely to cause a crash.

but the same is running successfully on LGVx7000.....

but the same is running successfully on LGVx7000.....

brew.com wrote:but the same is running successfully on LGVx7000.....
How is your extensioned named? Some phones have a shorter
name allowance than others -- and you can rename it to
something shorter without changing anyting else since the
class id will be what the app is looking for.

brew.com wrote:but the same is running successfully on LGVx7000.....
How is your extensioned named? Some phones have a shorter
name allowance than others -- and you can rename it to
something shorter without changing anyting else since the
class id will be what the app is looking for.

The extension is only named as "tt".....dont think this would be an issue due to this reason....

The extension is only named as "tt".....dont think this would be an issue due to this reason....

still the issue persits... :eek: :(

still the issue persits... :eek: :(

brew.com wrote:still the issue persits... :eek: :(
Sounds like you need to bring on a consultant.

brew.com wrote:still the issue persits... :eek: :(
Sounds like you need to bring on a consultant.

brew.com wrote:but the same is running successfully on LGVx7000.....
So you are compiling an extension against the 2.1 libraries. It is runngin properly on 2.1 devices, but crashing on 2.0... :rolleyes:
As I said before, you need to compile against the 2.0 libraries if you are going to run on a 2.0 device

brew.com wrote:but the same is running successfully on LGVx7000.....
So you are compiling an extension against the 2.1 libraries. It is runngin properly on 2.1 devices, but crashing on 2.0... :rolleyes:
As I said before, you need to compile against the 2.0 libraries if you are going to run on a 2.0 device

so, now i did the same against 2.0, but the problem couldnt be sorted out....what can be the reason now.....

so, now i did the same against 2.0, but the problem couldnt be sorted out....what can be the reason now.....