OpenAT 4.00 a03 doen't compile for debug

IoT Modules Development tools
1

Hi,

  1. I’m trying to get the OpenAT SDK for the Q2686 working, but no luck sofar. When trying to compile for debug I get the following error messages:

------ Skipped Build: Project: Hello_World, Configuration: Wismo Target Win32 ------

Project configuration skipped because it is not selected in this solution configuration

------ Build started: Project: Hello_World_rte, Configuration: Debug Win32 ------

Linking…
LINK : error LNK2001: unresolved external symbol _opecCustomerTaskInit
hello_world.obj : error LNK2019: unresolved external symbol _adl_atSendResponse referenced in function _HelloWorld_TimerHandler
hello_world.obj : error LNK2019: unresolved external symbol _adlint_osDebugTrace referenced in function _HelloWorld_TimerHandler
hello_world.obj : error LNK2019: unresolved external symbol __RTC_CheckEsp referenced in function _HelloWorld_TimerHandler
hello_world.obj : error LNK2001: unresolved external symbol __RTC_Shutdown
hello_world.obj : error LNK2001: unresolved external symbol __RTC_InitBase
hello_world.obj : error LNK2019: unresolved external symbol _adl_tmrSubscribe referenced in function _adl_main
LINK : error LNK2001: unresolved external symbol __DllMainCRTStartup@12
./rte/vc71/Debug/Hello_World_rte.dll : fatal error LNK1120: 8 unresolved externals

Build log was saved at “file://d:\MMOpenAtProject\rte\vc71\Debug\BuildLog.htm”
Hello_World_rte - 9 error(s), 0 warning(s)

---------------------- Done ----------------------

Build: 0 succeeded, 1 failed, 1 skipped

It looks to me as if some linker file is missing.

  1. Another issue is that I can place my source files on a local drive only. When placing the source files on a network drive I get “permission denied” errors when running the scripts

  2. Remote Task Environment doesn’t work either. The file and directorey rte\kernel.exe is nowhere to be found

Does someone have a solution?

Thanks in advance,

Marcel

2

Hello,

Lucky you to have such a new (and maybe bugfixed ;D) version…
I’m still struggling with 2.10 and 3.02 so I can’t say I have experience of your problem exactly…

But when I and many with me upgraded from 2.10 to 3.02 we stumbled into alot of trouble that was solved with some hands-on troubleshooting and alot of help from fellow forum members.
Take a look at the topics below (if you haven’t seen them yet…)

http://wavecom.profileo.com/modules/movie/scenes/forums/viewtopic.php?t=29
http://wavecom.profileo.com/modules/movie/scenes/forums/viewtopic.php?t=38
http://wavecom.profileo.com/modules/movie/scenes/forums/viewtopic.php?t=54

Maybe its something similar…

/Snoooze

3

Hello Snooze,

Thanks for your answers. In the meantime I received an answer from our distributor who talked to Wavecom. The development kit delivered with the new Q2686 modem is not working, in fact the development environment for this modem is not available yet. We are now negotiating to get a working development environment because we have a major problem now…
So We’re not so lucky anymore to have such a new version.

Regards,

Marcel

4

when i dubug the hello_world with F5 in vc6.0.it remote

debug assertion failed!

…

…

(press retry to debug the applicaion)

    what happend?


                    thank you 1