Open AT Application Compilation Tips

Application Note
Open AT® Application

Compilation Tips
Reference: WM_DEV_OAT_APN_005
Revision: 001
Date: February 26, 2007
Open AT® Application Compilation Tips
Open AT® v3.0x
WM_DEV_OAT_APN_005-001
Author: Wavecom Support Consultant Date: 03th August 2006
APN Content Level BASIC INTERMEDIATE 9 ADVANCED Confidentiality Public 9 Private
Open AT® TCP/IP 3.00 C-GPS N/A

Compil Reference Hardware No
Software 3.01 Plug- Bluetoot ADS
FW: X50a IDE: Internet N/A N/A er Reference Software Yes
Compatibility* Ins: h GCC
M2mpower MQTT N/A M2MC N/A Used:
* refer to software compatibility matrix section for more detail
Plug & Play: M1306B 9 M2106B 9
Quik (CDMA): Q2438F Q2438R CM52
NOT E
Wireless CPU Q2400A 9 Q2406A 9 Q2406B 9 Q2426B 9 Q2501B 9
Compatibility Quik (GSM): GR64 GS64 Q2686H Q2687H
Q24 Classic Q24 Plus Q24 Extended Q24 Auto
Wireless Microprocessor WMP100 WMP150
APPLICATION
1 VERSION
Application Notes may be updated over their lifetime. To ensure you
design with the correct version, please check the application notes
page in the support section for www.wavecom.com.
2 INTRODUCTION
This document describes some tips which will prevent generally
®
encountered problems related to Open AT application compilation.
Some of the common problems encountered during compilation and

®
execution of an Open AT application can be attributed to incorrect
settings. These problems can be avoided by specifying correct Open
® ®
AT configuration settings. Open AT version 3.0x provides graphical
NOT E
wizards which enable the user to easily view and modify these
settings.
®
Graphical wizards could be used when the Open AT project is
compiled/linked using Visual C++ environment.
APPLICATION
For backward compatibility with application creation and compilation,
®
Open AT v3.0x also supports direct project creation and compilation
using Cygwin. This document also elucidates some of the commonly
encountered problems when Cygwin is used to create/build a project
along with the reasons and solution. As indicated by the error message, the cause of the error is missing
“xsltproc” package. This package is required by Cygwin to create a
®
3 Prerequisite: Proper Open AT new project.
This problem is a result of missing cygwin packages and this
Installation condition occurs when all the cygwin packages are not selected and
®
®
Correct and complete installation of Open AT will avoid some of installed during Open AT installation.
common errors and issues faced while creating and compiling Open Cygwin setup, by default does not install all the packages (including
®
AT applications. “xsltproc”) on the system. This is indicated by “Default” selection for
®
While installing Open AT all the associated tools and packages like “Select package” dialog box during installation. The following
Cygwin, SGT etc need to be selected and installed. Issues while screenshot shows this default setting.
NOT E
®
creating and compiling Open AT applications might occur if the
associated tools (Cygwin, SGT etc) are not installed correctly and
completely.
3.1 Problem related to missing Cygwin Packages.

APPLICATION
In case, all the Cygwin packages are not installed, problems will be
faced while creating new projects. A commonly encountered error is:
“Wmnew script error 5([wmsync] xsltproc package is not
installed on the system”.
This error message is encountered when a new project is to be
®
created using Open AT project wizard. The Wizard fails to create a
new project after receiving this error message. The following
screenshot pictorially describes the above scenario:
Usually, Cygwin provides a predefined default package installation

and in this option not all the packages are installed. The missing
packages create problems if it is the first time cygwin is installed on
the system, or if it is installed after deleting the Cygwin Folder as
“xsltproc” package is not installed. In order to avoid such problems,
© 2006 All rights reserved Page: 1 / 12

This document is the sole and exclusive property of WAVECOM. Not to be distributed or divulged without prior written agreement.
Ce document est la propriété exclusive de WAVECOM. Il ne peut être communiqué ou divulgué à des tiers sans son autorisation préalable.
Open AT® v3.0x
complete installation for all the packages should be done. This can
be done by selecting “ALL-Install” Option for “Select Packages”
dialog box.
NOT E
APPLICATION
®
In such cases, check if the path indicated by the “Open AT Settings
Wizard” exists or not. If it does not exist, it means that the
component is not installed. Hence, the corresponding component
should be reinstalled. (Select the corresponding component in the
®
Open AT Setup).
As a general rule, SGT and Add-on Libraries (like TCP/IP) must be
®
installed with each Open AT installation irrespective of whether they
This step while Installing Cygwin will prevent error due to missing are already installed in the system. This is because each version of
packages. ®
Open AT will have some changes incorporated in these modules
and problems might arise if previous versions of these modules
3.2 Problems due to missing Open AT® (SGT, TCP/IP etc) are made to run with the newer version of Open
NOT E
®
AT .
components
If some components (SGT etc) are not installed, problems will occur The screen below displays the setup screen and the options selected
while creating new project. In such scenarios, no project workspace during a first installation:
will be created. The screen below depicts the problem that occurs in
APPLICATION
this scenario (after creating a new project and launching
®
development environment with Open AT Wizard).
NOT E
APPLICATION
3.3 Problem related to Environment Variables.

In some Operating systems (like Windows XP, Windows NT, and
®
Problems of this kind can be solved by checking for Open AT path Windows 2000) some users are not allowed to change the
®
settings using Open AT Settings Wizard. (By clicking on the button environment variables due to security reasons. This depends upon
®
next to the textbox displaying path in Open AT Settings Wizard). the security policy of the Operating system being used. For example,
Windows NT distinguishes its users based upon their privileges.
Users having administrators rights will be provided complete access
to install or uninstall software, hardware and change the environment
variables etc. However, some users (like Guests, Operators etc) will
not be provided privileges to change the settings which have wide
influence on the system (like change of registry or setting of
®
environment variables). If Open AT is installed by a user having
restricted privileges (i.e. not having Administrative privileges), then
the environment variables may not be set properly. So for proper

Open AT® v3.0x
installation under Operating Systems such as Windows XP,

®
Windows NT or Windows 2000, Open AT installation must be
performed from a user account having all the privileges to set
environment variables and change system settings (preferably an
Administrative account). This will solve the problems related to
unavailability/improper setting of environment variables.
4 Examples: Commonly Encountered

application compilation and linking
NOT E
problems
®
Sometimes, the user experiences problems in compiling Open AT
application. Various kinds of errors might appear while trying to
®
compile an Open AT application. These errors fall under the
APPLICATION
following categories and due to the reasons explained as follows:
4.1 Compilation problems due to missing source

files
During project creation, if the source files are missing, the workspace
in the Visual Studio will not display any source code. As displayed above, the compiler is unable to open the include file
“ed_common.h”. In debug mode, similar errors can be avoided by
In such cases, following step should be taken: ®
using the file Open AT Project Wizard (“project_name.scs”)
1. Put all the sources file under folder “src” (if a file shouldn’t associated to the project.
be compiled rename it “name_file.c_old”) and put the
include files under “inc”.
®
4.4 Compilation and Linking problems in Target
2. Re-create the project workspace by using Open AT
wizard that will update all makefiles and scripts files with
Mode.
the correct list of source files. Compilation and linking problems can also arise when application is
NOT E
executed in the target mode. In this case too, the environment has to
be provided with the location of include and library files. The
4.2 Compilation problems due to wrong compiler following image depicts one such scenario in which the user has not
options: specified the include files.
The usage of wrong memory options (32 or 16) for A-type modules
APPLICATION
(16/2 MBits) or B-type modules (32/4 MBits) gives memory related
errors during program execution. In such cases, the module will reset
after giving AT+WOPEN=1 command and will give ARM exception
1xx.
To solve such problem correct memory option must be specified in
®
Open AT settings as displayed in the screen below.
NOT E
APPLICATION
As displayed above, the compiler is unable to open the include file

®
“ed_common.h”. Similar errors can be avoided by using Open AT
Project Wizard.
4.3 Compilation and Linking problems in Debug In target mode, similar errors can be avoided by using the file Open
®
Mode AT Project Wizard (“project_name.scs”) associated to the project
(see §3.5).
Most of the compilation and linking problems during the Debug mode
can be attributed to incorrect or missing path settings. The following
screenshot shows such scenario encountered during compilation 4.5 Solving compiling/linking problems by using
with Visual C++ environment. Open AT® Project Wizard
® ®
In Open AT v3.0x for both modes (debug and target), Open AT
Project wizard should be used to modify the compiling/linking
options.
The path of external libraries, root libraries, object files should also
be specified during the creation of new project (using –extlib, -rootlib

Open AT® v3.0x
®
and objname options respectively). Please refer to wmnew script 2. In Open AT Wizard: The wnew script additional options
help for more information on available options. are “otherlib TCPIP/v3.01”
When a new project is created using Project Wizard, a file The linking/compiling path that is set automatically for TCP/IP
“project_name.scs” is systematically generated. libraries and includes is the following
This file should be used to modify the compiling/linking options when C:\OpenAT\OtherLibs\TCPIP\v3.01.
the project has been already created.
When compiling / linking problems are encountered in target or 5 Problems due to Corrupted Cygwin
debug mode (under Visual C++ environment or Cygwin
environment), the following steps should be taken:
Files
• Close the project workspace (if the project is open under ®
If Open AT development environment is repeatedly installed and
NOT E
Visual C++) uninstalled on different drives on the computer, the contents of some
• Open the file “project_name.scs” corresponding to the internal files of Cygwin (group and passwd) might become invalid. In
current project (by double clicking the file). such cases, despite of having correct path settings and Cygwin
• Add or modify the options “wmnew script additional Packages, errors will be experienced. The following screenshot
options” shows one such error which is encountered due to incorrect contents
APPLICATION
• Click on OK to validate the modification, then the makefiles of group and passwd file.
will be updated automatically.
NOT E
APPLICATION
In order to get rid of such problems follow the following steps:
1. Delete the old Cygwin folder (with all its contents) and make the
complete installation of Cygwin (By selecting “Install” option for all
the packages).
2. Delete “passwd” and “group” files from “etc” folder of in newly
It can be noticed that for a target mode application, the library name created Cygwin directory. Also delete the “home” folder if present in
corresponding to the compiler type is not specified. In this case, the Cygwin directory.
application will link itself to the arm_xxx.lib or gcc_xxx.lib (where xxx 3. Open the Cygwin window (Or Cygwin.bat file from Cygwin
is the library name) in the library path depending upon the compiler directory) and execute the command
®
to be used. The compiler option is set using by Open AT Settings. “mkgroup –l > /etc/group. “
NOT E
(in the field “Default compiler”) Then execute the command
“mkpasswd –l > /etc/passwd.”
These commands will recreate “passwd” and “group” files in the “etc”
folder of “Cygwin” directory. Close the Cygwin window.
4. Now open the “group” file present in the “etc” directory in “Cygwin”
APPLICATION
folder
and add the following line in it:

Everyone:S-1-1-0:0:
This line should be the first line of “group” file. Save and close the
group file.
NB: In this sample

®
1. In Open AT settings: The Addon librairies path is
“C:\OpenAT\OtherLibs”

Open AT® v3.0x
However, this option requires thorough understanding of Cygwin

usage.
One important point to check before creating a new project is the

module reference. Based on memory configuration there are two
types of modules:
¾ A-type -16Mbits/2MBits which means it has 16 Mbits Flash
and 2 MBits RAM size (ex : Q2406A)
¾ B-type -32Mbits/4MBits which means it has 32 Mbits Flash
NOT E
and 4 MBits RAM size (ex : Q2406B)
For A-type modules GCC/ADS compiler -16 option must be used and
for B-type modules GCC/ADS compiler -32 option must be used.
APPLICATION
7 Examples: Commonly Encountered
Problems while using Cygwin
The first step for tackling any project creation and compilation issues
in Cygwin should be to find the cause of error. This can be done as
follows
Use “wmcheck” command to see the errors.
5. Open the “passwd” file present in the “etc” directory in Cygwin
NOT E
folder. This file will contain some entries starting with
VUSR_computername (for example VUSR_wavecom-regis4,
VUSR_wavecom-regis3 etc).
6. Edit one such line by replacing VUSR_computername (in
complete line) by the user login name. (For example replace
APPLICATION
VUSR_wavecom-regis4 by rma). Save and close the file.
If the “wmcheck” command displays “Error” in some of the paths, it

indicates that there is some problem in Cygwin Installation.
Following steps can be taken to solve this problem.
NOT E
7.1 Problem due to missing Cygwin packages
A problem can be the result of missing cygwin packages and this
condition occurs when all the cygwin packages are not selected and
7. Close any open Cygwin Shell Window. ®
installed during Open AT installation. Cygwin setup, by default does
8. Reopen the Cygwin windows (“By clicking on the Cygwin.bat file”) not install all the packages (including “xsltproc”) on the system. This
APPLICATION
and execute the command: is indicated by “Default” selection for “Select package” dialog box
“wmsetup” during installation.
This command will recreate a new “Home” folder in the “Cygwin”
Directory and will solve the problem. Solution:
The solution consists in reinstalling cygwin taking care of :
There is one more way to solve this problem. ®
1. Select the Cygwin component in the Open AT setup. The
Open Cygwin and type screen shot is shown below.
“cp .bashrc .bashrc_profile”
After executing this command, if user is inside a domain, a new local

user should be created having the same user name as the currently
logged in name but with administrative rights.
This procedure will also solve the problem.
6 Direct Project Creation and Build using

Cygwin
®
The Open AT application can also be directly compiled using
Cygwin. The project workspace can also be created using Cygwin.

Open AT® v3.0x
NOT E
APPLICATION
2. “ALL-Install” Option should be selected in “Select
Packages” dialog box. (see screen shot below)
NOT E
APPLICATION
The contents of
<compilerUsed>_<ApplicationName>_<MemoryOption>_err_lnk.tmp
(for instance gcc_appli_16_err_lnk.tmp) file showing the cause of
error is as follows:
It may happen that the “wmcheck” command does not show any
error but still the problems exist in project creation. In this case check
for two things:
1. Check Path settings using Export command. All paths
should be checked and set right.
2. Check the project name. There should not be any blank
space in it
NOT E
If the problem still exists then reinstall Cygwin.
7.2 Problems due to missing source files

During project creation missing source files leads to the creation of a
APPLICATION
workspace containing no source code (refer to screen shots below).

The screen shot of the Cygwin window depicting the error is shown
below.
Solution:
There are two ways to solve this problem:
1. The best and advised way: Create a new project
workspace with a “src” folder that contains all the source
files to be included. Then, follow the normal project

Open AT® v3.0x
®
creation process. (by launching Open AT Project Wizard The contents of gcc_appli_16_err_lnk.tmp file showing the root-
or executing “wmnew” script under Cygwin environment). cause is shown in the screen shot below.
2. The second way: Manually add the source file names

under “List of source files” in the mak file of the existing
workspace. The modified mak file is shown in the screen
shot below.
NOT E
APPLICATION
NOT E
APPLICATION
1. The best and advised way: Set the correct value for the
7.3 Problems due to incorrect compiler options ®
environment variables with “Open AT settings”, as it is
If wrong compiler options (32 or 16) for A-type modules (16/2 MBits) shown in the screen shot below.
or B-type modules (32/4 MBits) are used, it leads to memory related When the environment variables are set correctly, the
errors during compilation. compiling option shouldn’t be taped systematically under
This option must be correctly settled especially while linking ed.lib Cygwin environment.
library during project creation. Line command to execute:
If not, the compiler gives error stating “RAM_MAP full”. wmmake appli
The errors can be seen by opening
(for instance gcc_appli_16_err_lnk.tmp) file in the “out” folder of the
project (project\gcc\out).
The following example shows the error in case GCC-16/2 option is
used by error while compiling a project and linking ed.lib library.
NOT E
APPLICATION
2. The second way: When the environment variables are not

set correctly, the compiling options “GCC –32” should be
taped systematically under Cygwin environment.
Line command to execute:
wmmake appli –gcc -32
Note: the above example uses gcc compiler. Same steps apply if
ARM compiler is used.

Open AT® v3.0x
7.4 Problems related to linking of add-on libraries The add-on libraries path and C include files path must be specified
using various wmnew-options such as –otherlib,-extlib,-samplelib,
etc.
7.4.1 Under Cygwin environment
Sometimes the issues occur due to missing add-on libraries path and There are many ways to solve this problem:
®
C include files path. The compiler is not able to link the required add- 1. The best and advised way: Open the Open AT Project
on libraries and gives error. A screen shot depicting error due to Wizard file (“*.scs”) associated to the project and add the
missing C include files is shown below. compilation/linking options in “wmnew script additional
options” section. (as It is shown in the screen shot below).
The makefiles will be automatically modified and the whole
NOT E
project workspace (for target and remote mode) will be
completely synchronized.
Then, compile under Cygwin environment using wmmake
command line.
APPLICATION
NOT E
APPLICATION
2. The second way: Under Cygwin environment, tape the
The screen shot of
command line wmnew with all the linking options.
(i.e. gcc_appli_32_err_lnk.tmp)gcc_appli_16_err_lnk.tmp file
wmnew –name appli –otherlibs < add-on used library list
depicting the error due to missing add-on libraries path is shown
(as TCP/IP library, for example)>
below.
For example,to add TCPIP libraries path, write :
wmnew –name appli –otherlibs TCPIP/v3.00
Similarly to include any other add-on library, the user can
specify the path of the specified add-on library in the
wmnew command options.
NOT E
3. Another way: Modify directly the makefiles. But with this
way, the project workspace (for target and remote mode)
will not be synchronized.
In the main makefile, C include files path under “Path for

APPLICATION
include C files” list and TCPIP libraries path under “Add-on

used library list must be correctly provided.
This is described in the screen shot of the mak file below.

Open AT® v3.0x
7.4.2 Under Visual C++ environment
Most of the compilation and linking problems during the Target or

Debug mode are due to incorrect or missing path settings. The
following screenshot shows such scenario encountered during
compilation.
NOT E
APPLICATION
NOT E
The compiler is unable to open the include file “ed_common.h”.
Similar errors can be easily avoided by providing correct path
settings for including and library files.
APPLICATION
®
1. The best and advised way: Open the Open AT Project
Wizard file (“*.scs”) associated to the project and add the
compilation/linking options in “wmnew script additional
Note: options” section. The makefiles will be automatically
If the include files path is provided but add-on libraries (Otherlibs or modified with the right paths and the whole project
Extlibs) path is still missing then project.o file is not generated and workspace (for target and remote mode) will be completely
the following error occurs: synchronized.
NOT E
APPLICATION
2. The second way: Modify the path directly in Visual C++

environment.
The paths are set by clicking on “Tools->Options-
>Directories”.

Open AT® v3.0x
NOT E
APPLICATION
In the same way, if the application is using some other libraries (like
TCP/IP library), then the VC6/VC7 development environment must
be provided with the paths and names of such libraries. This is
because the linker needs to resolve all the referenced symbols which
are defined in the library file.
If not done properly, errors are displayed :
Along with the library name, the library path should also be specified
so that the VC6/VC7 development environment can conveniently
NOT E
locate the library. This name should be specified in the Options
Dialog box. (“Tools->Options->Directories”).
APPLICATION
NOT E
To resolve this problem, the VC6/VC7 environment has to be
provided with the name of library file along with the path where this
library file is stored. The library name should be specified using the
Link Tab in the Project Settings Dialog Box (Press ALT+F7 to get
Project Settings window).
APPLICATION
Same steps should be followed to link the application to any other

external library.
8 Open AT® compilation Tips under

Visual Studio .Net
Following steps should be taken to launch the Visual Studio .Net in
®
order to create and build an Open AT application.
Step1: : Set the correct value for the environment variables with
®
“Open AT settings”. Select the right “Synchronized Workspaces”.

Open AT® v3.0x
NOT E
APPLICATION
®
Step2: Use “Open AT Project Wizard” to create the project.
® ®
Select the menu Start> Wavecom > Open AT > Open AT Project
®
Wizard shortcut to launch the Open AT Project Wizard.
Set the options desired.
Select “Launch development environment” with Visual C++.Net to 8.2 Settings required before Executing the Open
launch Visual environment.
®
AT® application in remote mode
The Open AT project is created with the workspace settings file
(“*.sln file”) in the following folder “project_name\project_name.sln”. Step1: Set the project in remote mode as active project.
Step2: While executing the application the following dialog box is

displayed
NOT E
APPLICATION
Step 3: Click on the “Browse” option which will appear in the combo
box as shown below.
8.1 Compile an Open AT® project with Visual

C++.Net NOT E
Step 1: To launch the project, select the file associated to the
project: “project_name\project_name.sln”.
To see the File View go to the View menu. Then select Solution
APPLICATION
Explorer as shown below. It will show the File View in right side of
window.
Select as active project: the project in target mode (project_name) or
the project in remote mode (“project_name_rte”)
Step 4: Select the “kernel.exe” file from the “rte” folder in the
workspace as shown below.

Open AT® v3.0x
10 SUPPORT
For direct clients: contact your Wavecom FAE
For distributor clients: contact your distributor FAE
For distributors: contact your Wavecom FAE
11 DOCUMENT HISTORY
Level Date History Author
001 03/08/2006 Creation Wavecom Support Consultant
NOT E
12 LEGAL NOTICE
LICENCE RIGHTS
APPLICATION
Wavecom Asia Pacific Ltd hereby grant licence to users of their Open AT® development environment to use the source code in this
electronic file for the sole use of developing GSM, GSM/GPRS or GSM/GPRS/GPS cellular applications compatible with Wavecom
products. The source code may be modified by any Open AT® developer providing the application is not intended to be malicious or
detrimental to cellular operators or consumers of the application in any way. The licence also grants permission to copy and distribute this
source code so long as this licence header is maintained in all source code files. You hereby undertake to use the Software for your
interim development purposes only and under no circumstances shall you use the Software for commercial purposes. For the avoidance
of doubt, the Software may not be sold for a fee on diskette or CD-ROM, either alone or as part of a collection with other products without
prior written consent from Wavecom.
DISCLAIMER OF WARRANTY
This Software is provided free of charge on an 'as is' basis. No warranty whether expressed or implied is given by Wavecom in relation to
the Software of the uses to which it may be put by you, the user, or its performance or merchantability, fitness or suitability for any
particular purpose or conditions; and/or that the use of the Software and all documentation relating thereto (the “Documentation”) by the
Step 5: The following dialog box is displayed once the executable Licensee will not infringe any third party copyright or other intellectual property rights. Wavecom shall furthermore be under no obligation
to provide support of any nature for the Software and the Documentation.
file name is provided in the above box. Click on “OK”. LIMIT OF LIABILITY
In no event shall Wavecom be liable for any loss or damages whatsoever or howsoever caused arising directly or indirectly in connection
with this licence, the Software, its use or otherwise irrespective of whether Wavecom has had advance notice of the possibility of such
damages or not by your use of the Software. Notwithstanding the generality of the foregoing, Wavecom expressly excludes liability for
indirect, special, incidental or consequential loss or damage which may arise in respect of the Software or its use, or in respect of other
equipment or property, or for loss of profit, business, revenue, goodwill or anticipated savings.
INTELLECTUAL PROPERTY
For the avoidance of doubt, no right, title or interest in any intellectual property right in respect of the Software shall pass to you. Any and
all intellectual property rights in respect of the Software and Documentation shall at all times remain the sole and exclusive property of
Wavecom. The licence grant shall not include Intellectual Property not wholly owned by Wavecom and the customer shall exercise due
diligence to ensure that the use of the information in this document does not infringe any patents in the country of origin.
NOT E
APPLICATION
Step 6: Now you can execute the application or debug the
application by setting breakpoints as shown below.
NOT E
APPLICATION
9 SOFTWARE COMPATIBILITY MATRIX

List all current software configurations and compatibility with this
application note.
® ® ®
Open AT Firmware Open AT OS Open AT Plug-Ins
X50a V3.01 V3.00
X51 V3.02 V3.02
X51a / X52 V3.03 V3.03
X52a V3.04 V3.04

APPLICATION NOTE WAVECOM S.A. - 3 esplanade du Foncet - 92442 Issy-les-Moulineaux Cedex - France - Tel: +33(0)1 46 29 08 00 - Fax: +33(0)1 46 29 08 08
This document
Wavecom, isInc.
the -sole
430 and exclusive
Davis Dr. Suiteproperty of WAVECOM.
300 - Research TriangleNot to be
Park, NCdistributed
27709 - USAor -divulged without
Tel: +1 919 prior-written
237 4000 Fax: +1agreement.
919 237 4140
GR/GS64 Charging Interface Ce document
WAVECOM est laAsia
propriété
Pacificexclusive de201-207,
Ltd. - Unit
nd
2 Floor
WAVECOM.P Il ne -peut
P Bio-Informatics Centreou
être communiqué
Shatin - New Territories, Hong Kong - Tel: +852 2824 0254 - Fax: +852 2824 0255
- No. 2 Science
divulgué à desPark
tiersWest
sansAvenue - Hong Kong
son autorisation Science Park,
préalable
Page: 1/1

Open AT Application Compilation Tips

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Open AT Application Compilation Tips

Încărcat de

Drepturi de autor:

Formate disponibile

Application Note

Open AT® Application

APN Content Level BASIC INTERMEDIATE 9 ADVANCED Confidentiality Public 9 Private

Open AT® TCP/IP 3.00 C-GPS N/A

Some of the common problems encountered during compilation and

3.1 Problem related to missing Cygwin Packages.

Usually, Cygwin provides a predefined default package installation

© 2006 All rights reserved Page: 1 / 12

3.3 Problem related to Environment Variables.

© 2006 All rights reserved Page: 2 / 12

installation under Operating Systems such as Windows XP,

4 Examples: Commonly Encountered

4.1 Compilation problems due to missing source

As displayed above, the compiler is unable to open the include file

© 2006 All rights reserved Page: 3 / 12

and add the following line in it:

NB: In this sample

© 2006 All rights reserved Page: 4 / 12

However, this option requires thorough understanding of Cygwin

One important point to check before creating a new project is the

5. Open the “passwd” file present in the “etc” directory in Cygwin

If the “wmcheck” command displays “Error” in some of the paths, it

After executing this command, if user is inside a domain, a new local

6 Direct Project Creation and Build using

© 2006 All rights reserved Page: 5 / 12

7.2 Problems due to missing source files

workspace containing no source code (refer to screen shots below).

© 2006 All rights reserved Page: 6 / 12

2. The second way: Manually add the source file names

2. The second way: When the environment variables are not

© 2006 All rights reserved Page: 7 / 12

In the main makefile, C include files path under “Path for

include C files” list and TCPIP libraries path under “Add-on

© 2006 All rights reserved Page: 8 / 12

7.4.2 Under Visual C++ environment

Most of the compilation and linking problems during the Target or

2. The second way: Modify the path directly in Visual C++

© 2006 All rights reserved Page: 9 / 12

Same steps should be followed to link the application to any other

8 Open AT® compilation Tips under

© 2006 All rights reserved Page: 10 / 12

Step2: While executing the application the following dialog box is

8.1 Compile an Open AT® project with Visual

© 2006 All rights reserved Page: 11 / 12

9 SOFTWARE COMPATIBILITY MATRIX

© 2006 All rights reserved Page: 12 / 12

S-ar putea să vă placă și