FreeRTOS RTIC Embassy IDT Workspace

This repository is a VS Code multi-repository workspace for STM32F3Discovery embedded-system experiments using FreeRTOS, RTIC, and Embassy.

The workspace is intended to organize multiple related Git repositories in one VS Code window. Each project remains an independent Git repository, but this workspace provides a common parent folder, a VS Code workspace file, and batch scripts to clone and manage all repositories.

Repository Purpose

This workspace is used for embedded timing and latency experiments, including:

FreeRTOS task latency
FreeRTOS jitter
FreeRTOS interrupt response latency
RTIC task latency
RTIC jitter using async/await
RTIC jitter using timer interrupt
RTIC interrupt response latency
Embassy task jitter
Embassy task-switch latency
Embassy interrupt response latency
Crane LPV FreeRTOS, RTIC, and Embassy case-study projects

Expected Workspace Structure

After setup, the local folder should look similar to this:

FreeRTOS_RTIC_EmbassyIDT_Workspace/
├── FreeRTOS_RTIC_EmbassyIDT_Workspace.code-workspace
├── gitbatch.bat
├── gitpushall.bat
├── README.md
├── stm32f3_FreeRTOS_tasklatency_v2/
├── stm32f3_FreeRTOS_Jitter/
├── stm32f3_FreeRTOS_ISPLatency/
├── stm32f3_rticjitter/
├── stm32f3_rticjitter_int/
├── stm32f3_rtic_isp_latency/
├── stm32f3_rtic_tasklatency/
├── stm32f3-embassy-taskjitter/
├── stm32f3_embassy_isp_latency/
├── stm32f3-embassy-tasklatency/
├── Crane2026_LPV_task_Latency_Jitter2/
├── ISP_Latency_FreeRTOS/
├── Crane2026_FreeRTOS_iBus2PWM_Latency/
├── Crane2026_lpv_rtic_tim6int_jitter/
├── Crane2026_lpv_rtic_latency/
├── Crane2026_RTIC_ibus2pwm_Latency/
├── Crane2026_embassy_Jitter/
├── Crane2026_embassy_task_latency/
└── Crane2026_embassy_ibus2pwm_latency/

Each subfolder is an independent Git repository.

Requirements on the Remote Computer

Before using this workspace on another computer, install the following tools:

Git
Visual Studio Code
PowerShell or Windows Command Prompt
Rust embedded toolchain, if building the Rust projects
STM32 embedded tools, such as probe-rs, OpenOCD, or ST-LINK tools, depending on the project

Check that Git is available:

git --version

Check that VS Code command-line access is available:

code --version

If the code command is not recognized, open VS Code and enable it from the Command Palette using:

Shell Command: Install 'code' command in PATH

On Windows, this is normally available after installing VS Code.

Step 1: Clone This Workspace Repository

On the remote computer, open PowerShell and go to the folder where you want to place the workspace.

Example:

cd C:\Users\YourUserName\Documents

Clone this workspace wrapper repository:

git clone https://github.itap.purdue.edu/wang32/FreeRTOS_RTIC_EmbassyIDT_Workspace.git

Enter the workspace folder:

cd FreeRTOS_RTIC_EmbassyIDT_Workspace

At this point, only the workspace files are cloned. The individual project repositories are not cloned yet.

Step 2: Clone All Project Repositories

Run the batch file:

.\gitbatch.bat

This script clones all FreeRTOS, RTIC, Embassy, and Crane LPV repositories into the workspace folder.

If PowerShell blocks the script, run it from Command Prompt instead:

gitbatch.bat

Or from PowerShell using:

cmd /c gitbatch.bat

Step 3: Open the Workspace in VS Code

After all repositories are cloned, open the VS Code workspace:

code FreeRTOS_RTIC_EmbassyIDT_Workspace.code-workspace

Alternatively, open VS Code manually and select:

File → Open Workspace from File...

Then choose:

FreeRTOS_RTIC_EmbassyIDT_Workspace.code-workspace

Step 4: Work on Individual Repositories

Each project folder is still its own independent Git repository.

For example, to work on the Embassy task jitter project:

cd stm32f3-embassy-taskjitter
git status

To commit and push changes for that repository:

git add .
git commit -m "Update Embassy jitter experiment"
git push

Then return to the workspace root:

cd ..

Step 5: Push Changes from All Repositories

If gitpushall.bat is included, it can be used to check and push all repositories from the workspace root:

.\gitpushall.bat

This script enters each repository folder, checks for changes, commits modified files, and pushes them to the corresponding remote repository.

Use this carefully. For important changes, it is usually safer to enter each repository and commit with a specific commit message.

Important Notes

This workspace repository does not replace the individual project repositories.

The workspace repository stores only:

FreeRTOS_RTIC_EmbassyIDT_Workspace.code-workspace
gitbatch.bat
gitpushall.bat
README.md
.gitignore

The actual project source code remains in separate repositories.

This means that there are two levels of Git management:

The workspace wrapper repository
The individual project repositories inside the workspace

Updating the Workspace Repository

If the workspace file, README, or batch scripts are changed, commit those changes from the workspace root:

git status
git add .
git commit -m "Update workspace configuration"
git push

This only updates the workspace wrapper repository.

It does not push changes inside the individual project repositories.

Updating an Individual Project Repository

To update a project repository, enter that folder first.

Example:

cd stm32f3_rticjitter
git status
git add .
git commit -m "Update RTIC jitter measurement"
git push

Then return to the workspace root:

cd ..

Pulling Updates Later

To update the workspace wrapper files:

cd FreeRTOS_RTIC_EmbassyIDT_Workspace
git pull

To update one project repository:

cd stm32f3_rticjitter
git pull

To update all cloned project repositories, run:

for /d %D in (*) do @if exist "%D\.git" cmd /c "cd %D && git pull"

If using this command inside a .bat file, use double percent signs:

for /d %%D in (*) do (
    if exist "%%D\.git" (
        cd "%%D"
        git pull
        cd ..
    )
)

Recommended Workflow

A typical workflow on a new computer is:

git clone https://github.itap.purdue.edu/wang32/FreeRTOS_RTIC_EmbassyIDT_Workspace.git
cd FreeRTOS_RTIC_EmbassyIDT_Workspace
.\gitbatch.bat
code FreeRTOS_RTIC_EmbassyIDT_Workspace.code-workspace

A typical workflow after editing a project is:

cd project_folder_name
git status
git add .
git commit -m "Describe the project update"
git push

A typical workflow after editing the workspace configuration is:

cd FreeRTOS_RTIC_EmbassyIDT_Workspace
git status
git add .
git commit -m "Update workspace configuration"
git push

Troubleshooting

Problem: `git` is not recognized

Install Git for Windows and restart PowerShell.

Check again:

git --version

Problem: `code` is not recognized

Open VS Code and enable the command-line tool from the Command Palette.

Then restart PowerShell and check:

code --version

Problem: Authentication fails when cloning or pushing

Make sure you have access to Purdue GitHub Enterprise:

https://github.itap.purdue.edu

You may need to sign in through the browser, configure Git credentials, or use a personal access token depending on the current Purdue GitHub Enterprise authentication settings.

Problem: Some repositories already exist

If a folder already exists, git clone will skip or fail for that repository. This is normal.

You can enter that folder and update it manually:

cd repository_folder_name
git pull

Summary

This repository provides a convenient VS Code workspace for managing multiple FreeRTOS, RTIC, Embassy, and Crane LPV repositories.

Use this workspace to open all related repositories together, while keeping each project as an independent Git repository.

wang32/FreeRTOS_RTIC_EmbassyIDT_Workspace

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Contributors 0

Languages

Contributors