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

Developer

Forums

Forums:

My simulator hangs at startup at one of two places every time I try to run a simulation.
I have created an enirely new workspace in eclipse in which I created a brand new application and the simulator still hangs.

The two places are either at:
place 1:
Displayed in simulator console:
usbcompositortestapp.c:263 - SHELL_INIT notification

Last eclipse console output is usually something like:
ead symbols: File format not recognized.
Error while reading shared library symbols:
"C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\System.Xml\773a9786013451d3baaeff003dc4230f\System.Xml.ni.dll": can't read symbols: File format not recognized.

Place 2:
Displayed in simulator console:
MsgStore.c:493

Last eclipse console output is
warning: MsgStore.c:1346 - ==> MsgStore_Handle_MessageList

warning: MsgStore.c:493 - ==> MsgStore_DispatchEvent 6

In the first case, the simulator.exe becomes completely unresponsive and must be killed using Task Manager.
In the second case the simulator is still responsive but the screen is just black and nothing happens.

Anyone having a suggestion as to what might be wrong?

Hi Culumeon,
I'm checking with development on your issue.
Are you able to launch Simulator and then run app or does that also crash?
What version of SDK are you running?
Thanks,
Karina

Hi Culumeon,
I'm checking with development on your issue.
Are you able to launch Simulator and then run app or does that also crash?
What version of SDK are you running?
Thanks,
Karina

No, same problem arise when starting simulator without an application (using the launcher for example)
I use Brew MP 1.0 rev 4.5
Thanks
David

No, same problem arise when starting simulator without an application (using the launcher for example)
I use Brew MP 1.0 rev 4.5
Thanks
David

Reinstalling SDK and deleting registry entries in HKEY_USERS\S-1-5-21-1894710443-2060226866-1798098279-1692\Software\Qualcomm solved the problem.
Will try to only delete the registry entires next time teh error occurs.

Reinstalling SDK and deleting registry entries in HKEY_USERS\S-1-5-21-1894710443-2060226866-1798098279-1692\Software\Qualcomm solved the problem.
Will try to only delete the registry entires next time teh error occurs.

Thanks for your update. If you find out if deleting just the registry entries work, can you let me know? In the meantime I'll continue to look into this to see if there's anything that needs to be fixed on our end.
Thanks!
Karina

Thanks for your update. If you find out if deleting just the registry entries work, can you let me know? In the meantime I'll continue to look into this to see if there's anything that needs to be fixed on our end.
Thanks!
Karina

Thank you.
I will notify you if and when the error reoccurs.
//David

Thank you.
I will notify you if and when the error reoccurs.
//David

I found a note in the Known Issues for Brew MP 1.0 rev 4.5 that related to this issue:
Simulator
SDK Simulator hanging on startup (after previously launching the Simulator within AppCreator)
A hang will be experienced when trying to run the Simulator after previously running an application (Trig or Flash) in the AppCreator Simulator.
To get around this problem delete the file C:\Program Files\QUALCOMM\Brew MP 1.0 SDK Rev 4.5\tools\simulation\mod\BREWSim\BREWSim.dat, and then the Simulator will start up correctly.
This solved the problem when we tried it on my colleagues computer.
Sorry for reporting an already known problem.

I found a note in the Known Issues for Brew MP 1.0 rev 4.5 that related to this issue:
Simulator
SDK Simulator hanging on startup (after previously launching the Simulator within AppCreator)
A hang will be experienced when trying to run the Simulator after previously running an application (Trig or Flash) in the AppCreator Simulator.
To get around this problem delete the file C:\Program Files\QUALCOMM\Brew MP 1.0 SDK Rev 4.5\tools\simulation\mod\BREWSim\BREWSim.dat, and then the Simulator will start up correctly.
This solved the problem when we tried it on my colleagues computer.
Sorry for reporting an already known problem.