Developer Studio (M2M Studio) 1.0.0 Release note

Features M2M Studio 1.0.0

Develop

• Project Management : Project Creation Wizard / Import Project / Import Wavecom Software Package
• Source Code Editor
• Readability : Explicit syntax colour coding
• Views : Project View / Function call hierarchy view / Include file hierarchy view
• Searching : Indexation engine and shortcuts
• Writing : Word completion

Build

• Compiler : GCC Native / ADS Compliant / RVDS Compliant
• Compilation Flags : Managed for full project or file by file
• Compilation Options : Managed for full project or file by file
• Compilation Tool Chain : MinGW
• Incremental Build
• Build Reporting : Explicit error and warning message / Direct access to source code linked to errors and warnings

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

Miscellaneous

• Integrated Help
• Integrated Software Update
• Windows® Platform Support : Windows® XP

Known limitations & bugs

Generic

• Needs an external Java environment previously installed (JAVA 1.6)

Build system / Open AT Projects management

• Paths with space characters are not supported
• ARM ELF GCC build fails if path to SPM Registry is too long (>~125 characters, ie. workspace path >~75 characters with default settings)
• C++ language not supported
• Incremental build not functional
• Library projects dependencies are not managed automatically
• No synchronization check between the Open AT Firmware version used in a project, and the one running on the connected Wireless CPU

Target management

• 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

• A console view is allocated and takes the focus on each run session
• 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"
• Sometimes, breakpoints cannot be added during the session, but have to be set prior to launch the debug