🔰 First start

On the first start, VSCode EPuck2 should lock something likes this:

On the left is a bar containing 5 tabs:

1. File explorer tab
2. Search tab
3. Source control (Git) tab
4. Run and debug tab
5. Extensions tab

On the bottom is an:

6. Information bar

And finally in the center is:

7. Editing area

Let's now do a quick tour of the IDE

1. 📁 File explorer

When you open VSCode EPuck2 for the first time, nothing is shown in the file explorer. In order to investigate a bit that tab, you can open the Lib folder that is located in the workspace. If you need help, you can check here how to do it.

The content of the Lib folder can be divided in 3 parts:

1. .vscode/ : Stores all the workspace's specific settings used by VSCode EPuck2

   • c_cpp_properties.json : set include path and definition required by Intellisense
   • launch.json : properties for debug
   • settings.json : the only settings you should modify, used to set the programmer/debugger COM port of the EPuck2 (GDB-Server)
   • tasks.json : properties to launch compilation

2. e-puck2_main-processor/ : stores ChibiOS library, click 👉 here for more info about ChibiOS. This is going to be useful from TP3 onwards, and you will have an introduction during the course.

3. ST/ : stores the ST HAL library, click 👉 here for more info about STM32, useful now!

2. 🔍 Search and replace

• Just a classical search and replace but with workspace global capabilities
• For a file wide search and replace functionality, type Ctrl+ F (Cmd+ F for MacOS) in an opened file
• To do this on all workspace, add Shift to the previous shortcuts
• To do this on a dedicated folder, select this folder on File explorer tab, then type Shift + Alt + F (Shift + Option + F on MacOS)

3. 🐈 Source control

• This tab is a graphical frontend to git
• For more information on git, click 👉 here

4. 🐛 Run and Debug

• This tab is a graphical frontend to GDB (GNU Debugger)
• 💡 Click 👉 here for more info about debugging the EPuck2 using the IDE

5. 🔌 Extensions

This tab, as the name suggests, is the place where you can manage extensions. In your case, there should be 5 extensions already installed.

[!WARNING]

• The Cortex-Debug extension should NOT be updated to a version more recent than the 1.4.4.
• In the case the extension version is not 1.4.4, you must change it by selecting the right one:

Github Copilot 🔍

👉 Installation

1. Claim the Student Developper Pack: https://education.github.com/pack
2. Install the VSCode extensions Github Copilot and Github Copilot Chat within the EPuck2 VSCode IDE
3. The extension will ask for you to sign-in with your Github account

Usage 💡

Here is a short video showing how to use this exciting tool!

💡 Further readings

• VSCode documentation New