Developer Studio (M2M Studio) 1.1.2 Release note

Upgrade/Install instructions.
Features.
Known Limitations.
Bugs Fixed :

• Developer Studio 1.1.2
• Developer Studio 1.1.1
• Developer Studio 1.1.0
• Developer Studio 1.0.2
• Developer Studio 1.0.1

---

Developer Studio 1.1.2 Upgrade/Install instructions

First time install

Please use the provided installer and just follow the steps in order to install Developer Studio for the first time.

Upgrade

Updates are automatically checked at each Developer Studio launch, and it is possible to upgrade to the new version just by following the instructions. It is also possible to start the updates checking job by using the Help > Check for Updates menu.

Note:
If you are currently using Developer Studio version 1.1.0 or older, it is not possible to upgrade it to 1.1.2 release; you have to use the provided Software Installer instead, in order to install it in an empty new directory.

Installation over an Eclipse platform

It is possible to install Developer Studio as a set of plug-ins over an existing Eclipse platform.

• Prerequisites: Developer Studio 1.1.2 requires Eclipse Galileo (3.5) version. Download it from http://eclipse.org/downloads
  (Best choice to start is Eclipse for C/C++ Developers)
  Developer Studio plug-ins can be installed on Win32 and Linux platforms
• Go to Help > Install New Software
• Add both following URLs as new update sites (drag'n drop the URLs to the Eclipse dialog box):

http://www.wavecom.com/eclipseUpdates/m2mstudio

http://www.wavecom.com/eclipseUpdates/m2mstudioProduct

• In the drop-down list, select the http://www.wavecom.com/eclipseUpdates/m2mstudio site
• Check the Developer Studio feature, click Install and follow the steps.

---

Features- Developer Studio 1.1.2

Packages management

• [New in 1.1.2] Capability to explore packages resources directory with the system explorer
• Package Manager perspective, allowing to manage package repositories and installed packages.
• Capability to download and install packages from remote update sites.
• Packages documentation integrated in the Developer Studio help.
• Capability to configure the installed packages location.

Develop

• [New in 1.1.2] Lua projects support (bytecode generation from .lua files)
• [New in 1.1.2] Outline support in Lua source code editor
• [New in 1.1.2] Project creation wizard with Target Platform configuration and easy access to samples documentation
• C/C++ support
• Project Management: Project Creation Wizard / Import Project / Import Open AT Software Packages
• C/C++ Source Code Editor
• Readability: Explicit syntax color coding
• Views: Project View / Function call hierarchy view / Include file hierarchy view
• Searching: Indexation engine and shortcuts
• Writing: Word completion
• Lua source code editor
• Application settings editor and code generation
• Project dependencies management (automated compiler/linker settings update when adding/removing a project dependency)

Build

• [New in 1.1.2] RVDS 4.0 ARM Toolchain support
• [New in 1.1.2] New GCC 4.4.1 Toolchain (EABI compatible) support
• C/C++ compilers support
• Additional build steps support
• Compiler: GCC Native / MinGW / ADS Compliant / RVDS Compliant
• Compilation Flags: Managed for full project or file by file
• Compilation Options: Managed for full project or file by file
• Incremental Build
• Build Reporting: Explicit error and warning message / Direct access to source code linked to errors and warnings
• Batch build capability (invoke a project build from the command line)
• Open AT Plug-ins packaging facility (through scripts), for distribution to the community.
• Enhanced build configuration wizard.
• Automatically embeds information on integrated components version (Open AT OS and Plug-ins) in the application binary
  This information is readable thanks to the ATI9 command (available starting from Firmware version R7.4)
• Paths to GCC/MinGW compilers are configurable (capability to use an external distribution)
• MinGW build support under Linux
  (only if i586-mingw32msvc-gcc cross-compiler toolchain is installed on the system)

Test

• Download
• File Type: Application Binary / Wavecom Firmware binary / Wavecom Boot loader binary
• File Format: DWL
• Target Info View: Target Serial Number / Target Mode / Wireless CPU Identification / Embedded Software Identification
• Shell: AT Console

Debug

• Trace: Trace Filtering / Time Stamp / Log
• Memory: Memory Status
• Remote Task Environment
• JTAG
• Possibility to bypass target presence check before launching a JTAG session

Miscellaneous

• Software Updates automatically checked on start-up
• Generic Software installer allowing to download an install latest software versions
• Based on Eclipse Galileo 3.5.1 (What's new) and CDT 6.0.1 (What's new)
• CVS and SVN repositories connection support
• Integrated Help
• Integrated Software Update
• Windows® Platform Support: Windows® XP, Windows® Vista, Windows® 7
• Linux support (except for Target Management features)
  Available only by installing over an existing Eclipse platform.
• Developer Studio source code available
  Available only by installing over an existing Eclipse platform.

---

Known limitations & bugs-1.1.2

Generic

• Needs an external Java environment previously installed (JAVA 1.6) when using the installer. Once installed, Developer Studio is standalone

Build system / Open AT Projects management

• Workspace paths with space characters are not supported
• No synchronization check between the Firmware version used in a project, and the one running on the connected Module

Target management

• Developer Studio sometimes crash suddenly on operations related to Target management (connect, baudrate autodetection, download)
  Seems to be related to USB-Serial converter usage
• Backtraces decoding is not supported
• Heap memory status does not contain links to source code
• Trace logging is disabled as soon as the target resets
• Baudrate autodetection is not configurable
• Target info view is not automatically refreshed

Run & Debug

• JTAG Debug relies on third-party non-integrated software (Open OCD)
• JTAG Debug works only is the download step is skipped in the Run configuration
• No check if the connected Wireless CPU is "JTAG-able"
• Breakpoints cannot be added during a debug session while the program is running (they have to be added when the execution has stopped on another breakpoint)

---

Bugs fixed and minor enhancements- 1.1.2

Packages management

• Implemented: background install procedure + "proportional" progress monitor
• Package column in Installed Packages view is now resizable (to show full package name when it is too long)
• Release note tab added in Properties view when selecting a package in Installed Packages view
• Added a confirmation dialog when deleting a repository from Available Packages view
• Fixed: Software Updates were not working after a package installation
• Fixed: Exception when trying to install new package while updates checking job was running

Develop

• Generated files names & paths are now changeable in the Application Settings editor.
• Application Settings editor reworded for clarification
• Bugs fixed concerning application settings editor content reseted when project properties are modified
• Used plug-in version selection bug fixed (both old and new versions were kept until old version was unselected again in the UI)
• New project location edit box not cleared anymore when default checkbox is unselected
• Code editor: grayed sections are now matching with the currently active build configuration

Build

• Error parsers enhanced to report missing errors wrt. the console output
• Added graphical decorator on the currently active build configuration output folder in the project explorer
• Configure ARM license variables definition in a separated preference page
• Fix usage of tcc with RVDS; now use armcc with the relevant option to choose Thumb or ARM mode

Run & Debug

• Fixed: launch configuration was locked when previous launch was canceled due to compilation errors
• Fixed: "Label error" issue on breakpoint stop in RTE

Miscellaneous

• Added Windows® 7 support

Headless mode / Packages integration

• Add -mem option support in wmnew.opt files for samples integration
• Add requiredMemTypeID property support for packages integration, to force a required memory type on project creation, when depending on the integrated package
• Add stackSizeProcessingRequired property support for packages integration, to declare if integrated samples source codes already manage stack size declaration according to the used toolchain, or not.
• Add helpBooks property support for packages integration, to declare a list of HTML help books to be integrated
• Bug fixed: when creating in headless mode a sample project depending on a sample library (e.g. Application_Download), the dependency reference was not correctly set and the project was not building correctly.
• Modified default RVDS options to make link possible with new EABI compatible GCC.

---

Developer (M2M) Studio 1.1.1

Install / General

• Issues fixed regarding install/uninstall of some packages

Build system / Open AT Projects management

• Popup error messages when project package dependencies are missing have been replaced by error markers in the Problems view
• When changing a project's dependency on an SDK profile, all packages dependencies are modified (including plug-ins)
• ATI9 info was not always updated when modifying project dependencies
• Sometimes, "An internal error occurred during: "C/C++ Indexer" message war appearing at project creation/import.
• Library projects dependencies are now managed automatically
• It is now possible to import a project created under a Windows Developer Studio into a Linux Developer Studio

Run & Debug

• Trace and shell views were closed when launching a new Run/Debug session

---

Developer (M2M) Studio 1.1.0

Install / General

• Uninstall of packages was refused if used by at least one project.
• Help > Software Update menu was not enabled on 1.0.2
• Fix display/indexing issues on Traditional Chinese OS and others

Build system / Open AT Projects management

• Developer Studio created project was unable to build after import if it had dependencies on other workspace projects
• ARM ELF GCC / MinGW build was failing if path to SPM Registry is too long (>~100 characters, ie. workspace path >~50 characters with default settings)
  Now embedded compilers are managed in Developer Studio install location, and a warning is displayed in Developer Studio preferences if the install path is too long.
• Cleaning of unnecessary files on project import from IDE V1/creation from a sample

Target management

• Debug traces logging to file feature was not usable ("cyclic buffer" behavior, beginning of the file was lost after some time)
• Confirmation messages removed on connection/download success
• Text AT commands (a.g. AT+CMGW) were not supported in shell (Ctrl-Z did not work)

Run & Debug

• Warning message when trying to start several launch session at the same time.
• Automatic connection to the target (if not already done) when launching for the first time.

---

Developer (M2M) Studio 1.0.2

Install / General

• Desktop/Start menu shortcuts added for all users
• Online update site available for software update
• "Out of memory" error fixed

Build system / Open AT Projects management

• Build errors fixed with ARM ELF GCC & MinGW under Windows Vista
• Remove useless Release configuration for application projects in RTE mode
• Default configurations at project creation time are new Target ARM ELF GCC and RTE MinGW

Target management

• DUMP frames sent by the Firmware were not correctly decoded

Run & Debug

• Launch configurations (Run/Debug) can be simply created by using the Run/Debug toolbar button
• Automatic switch to Target Management perspective when running a project in RTE

---

Developer (M2M) Studio 1.0.1

Install

• Desktop/Start menu shortcuts added by the Developer Studio light installer
• Windows Vista support issues

Build system / Open AT Projects management

• No need anymore to take care about the libraries order on the ARM ELF GCC linker command line
• Some plug-ins samples (e.g. from C-GPS plug-in) dependencies to other plug-ins not correctly managed
• It was not possible to change the current OS version in a library project
• Bad symbol name generation for C-GPS plug-in (makes the build fail with ARM compilers)
• Incremental build was not working (relink of the application was performed on each build request)
• Added by default the -fno-profile option on ARM ELF GCC compiler command line
• IDE V1 project import was not working when source paths out of the project directory were referenced
• IDE V1 library project import was not working
• IDE V1 project import did not import symbols declared with the -flag option
• Several issues fixed concerning IDE V1 projects import depending on library projects

Target management

• Target Management Toolbar icons strange behaviour when an automatic build is triggered
• Empty trace levels configuration box after an undetected target reset
• Traces containing a %u format character not correctly displayed
• COM port identifier not correctly configured if greater than 9
• Target management doesn't go anymore to "connected" state if the COM settings are incorrect
• New toolbar button in the trace view usable to force the target back to Debug after an undetected reset