Skip to content

Commit

Permalink
Updated Version Number, README and CHANGELOG
Browse files Browse the repository at this point in the history
  • Loading branch information
Marus committed Jan 30, 2018
1 parent 28e172c commit a037752
Show file tree
Hide file tree
Showing 3 changed files with 22 additions and 5 deletions.
14 changes: 13 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,16 @@
#V0.1.10
# V0.1.11

* Improved SVD parsing:
* Fields now support bit ranges being defined with <msb> and <lsb> elements; This would have impacted SVD files supplied by Nordi Semiconductor, Fujitsu and Spansion
* Improved support for repeating fields/registers for "array" style repeats, versus explicitly named repeats; This would have impacted SVD files supplied by Nordic Semiconductor, Microchip/Atmel, and some of NXP's LPC line
* Support for register clusters, to group multiple closely related registers, within peripherals; This would have impacted SVD files supplied by Nordic Semiconductor and Microchip/Atmel
* Improved behaviour with the Disassembly View:
* Manual triggered disassembly names will now match those automatically generated by missing source/forced disassembly mode - prevents it from opening two copies of the disassembly.
* If there are multiple functions with the same symbol name (two static functions with the same name in two different compilation units) you can now choose between them when manually opening a disassembly view.
* If you are focused on a manual disassembly view for the current frame the debugger will use instruction level stepping, instead of source line level stepping.
* Added a "postLaunchCommands" property to the supported launch.json properties. This should be an array of GDB commands to send after the main launch/attach sequence (you do not need to include things like "target extended-remote ...", "load", or "monitor reset" as these are generated automatically).

# V0.1.10

* The update has a significant refactoring of code to make supporting the expanding list of GDB Servers more feasible. From the user side this necessitates updating your launch.json files as all debug types have now been combined into one common *cortex-debug* type
* The typical changes needed are to replace *"type": "<server>-gdb" in your launch.json file with "type": "cortex-debug" and "servertype" : "<server>";
Expand Down
11 changes: 8 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,17 @@ Debugging support for ARM Cortex-M Microcontrollers with the following features:
* In some cases the st-util GDB server can report incomplete/incorrect registers, so there may be some issues here.
* Peripheral Register Viewer (Defined through standard SVD file)
* SWO Decoding - "console" text output and binary data (signed and unsigned 32-bit integers, Q16.16 fixed point integers, single percision floating point values)
* Currently decoding of ITM Timestamp and Synchronization packets are not supported; these features will need to be disabled in the code for the microcontroller.
* The registers that are part of the DWT, TPIU, and ITM debug components will automatically be configured and do not need to be set in firmware.
* Firmware will still need to enable the SWO output pin (if necessary) - as this part of the setup is microcontroller dependant.
* Decoding ETM data over the SWO pin is not currently supported.
* Support for Custom ITM Data Decoders:
* Ability to define JavaScript modules to decode complex data formats streamed over a particular ITM port. Data can be printed to a output window, or sent to the graphing system.
* Live graphing of decoded ITM data.
* Raw Memory Viewer (From the command menu select Cortex-Debug: View Memory)
* Ability to view and step through the disassembled binary
* Raw Memory Viewer ("Cortex-Debug: View Memory" command)
* Ability to view and step through the disassembled binary. There are three ways that disassembled code will be shown:
* Disassembly code will automatically be shown if it cannot locate the corresponding source code.
* You can manually see the disassembly for a particular function ("Cortex-Debug: View Disassembly (Function)" command)
* You can set the debugger to always show show disassembly ("Cortex-Debug: Set Force Disassembly" command)
* Globals and Static scopes in the variables view

### In Progress Features
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -1246,5 +1246,5 @@
"vscode:prepublish": "tsc -p ./",
"watch": "tsc -watch -p ./"
},
"version": "0.1.10"
"version": "0.1.11"
}

0 comments on commit a037752

Please sign in to comment.