Engineers who have pressed F7 to build for fifteen years keep their keys. The module has presets for Keil uVision, IAR Embedded Workbench and the Eclipse-based vendor IDEs (STM32CubeIDE, MCUXpresso IDE, Code Composer Studio, e2 studio), and debug layouts that open the windows those IDEs open when a debug session starts.
How it is offered
When a workspace holds a Keil .uvprojx, an IAR .ewp, or a .cproject written by one of the Eclipse-based IDEs above (in the folder or its direct subfolders), the Editor offers once, naming the project and a few of its keys:
- Keys and Debug Windows: the keymap and the debug layout;
- Keys Only: the keymap;
- Show the Shortcuts: the list below;
- Don't Show Again.
When a workspace mixes them, the vendor of most projects is offered, Keil and IAR before Eclipse on a tie.
To choose at any time, run Select Vendor Keymap and Debug Layout (Keil, IAR, Eclipse). It sets two settings:
| Setting | Values |
|---|---|
neuralInverse.embedded.keymap | none (default), keil, iar, eclipse |
neuralInverse.embedded.debugLayout | ide (default: nothing opens or closes), keil, iar, eclipse |
Show Vendor Keyboard Shortcuts and Debug Layouts lists every shortcut with the vendor's menu command, the command it runs here, and the source it was read from, marked "Vendor source" or "Unverified, secondary source". Pick one to run it.
The shortcuts
| Vendor | Key | Vendor command | Runs here | Source |
|---|---|---|---|---|
| Keil | F7 | Project > Build Target | Build Firmware | Published example project notes |
| Keil | F8 | Flash > Download | Flash Firmware (with its confirmation) | Published example project notes |
| Keil | Ctrl+F5 | Debug > Start/Stop Debug Session | Start or Stop Firmware Debugging | Published example project notes |
| Keil | F5 | Debug > Run | Continue | Published example project notes |
| Keil | F11, F10, Ctrl+F11 | Step, Step Over, Step Out | Step Into, Step Over, Step Out | Unverified, secondary source |
| IAR | F7 | Project > Make | Build Firmware | IAR's example projects |
| IAR | Ctrl+D | Project > Download and Debug | Flash and Debug Firmware | IAR's example projects and guides |
| IAR | F5 | Debug > Go | Continue | IAR's example projects |
| IAR | Ctrl+Shift+D, F10, F11, Shift+F11 | Stop Debugging, Step Over, Step Into, Step Out | Stop, Step Over, Step Into, Step Out | Unverified, secondary source |
| IAR | Alt+F7 | Project > Options | No counterpart in the keymap; use Open Vendor Project Options | IAR's guides |
| Eclipse | Ctrl+B | Project > Build All | Build Firmware | Eclipse Platform default key bindings |
| Eclipse | F11 | Run > Debug | Flash and Debug Firmware | Eclipse Platform default key bindings |
| Eclipse | F5, F6, F7, F8 | Step Into, Step Over, Step Return, Resume | Step Into, Step Over, Step Out, Continue | Eclipse Platform default key bindings |
| Eclipse | Ctrl+F2, Ctrl+R, Ctrl+Shift+B | Terminate, Run to Line, Toggle Breakpoint | Stop, Run to Cursor, Toggle Breakpoint | Eclipse Platform default key bindings |
Ctrl is Cmd on macOS. Build, flash and debug keys keep their confirmations: F8 in the Keil keymap still asks before flashing.
Debug layouts
| Layout | When a firmware debug session starts | When it ends |
|---|---|---|
keil | Run and Debug with Registers and Peripherals, the Debug Console (uVision's Command window), and Disassembly beside the source at the first stop | The Disassembly view the layout opened closes and the Explorer comes back, as uVision returns to its edit layout |
iar | As Keil (the Debug Console stands for C-SPY's Debug Log) | As Keil |
eclipse | Run and Debug with Registers and Peripherals, and the Debug Console (Eclipse's Console), as the Debug perspective | Nothing changes |
The layouts open the same windows as the vendor's debug mode, not at the same screen positions.
State
Unit and Electron tests on Linux, and used in the running app on Linux with a QEMU session: the IAR offer, F7, F5, F10, Ctrl+Shift+D and the IAR layout. The Eclipse keys and layout were checked against the Eclipse Platform's own default key files and perspective code. The Keil keys and the IAR debug keys marked unverified come from secondary sources, and no vendor install was checked. Not verified on Windows.
Agents can read the presets (Read the Vendor Keymaps and Debug Layouts) and choose one (Choose a Vendor Keymap and Debug Layout), which writes your user settings only after you confirm.