- Setup focused on Windows only - All Windows notes from within this page
- Setup focused on macOS only - All macOS notes from within this page
- Setup focused on RPi only - All Raspberry Pi notes from within this page
NOTE: This page describes creating tasks common to all of your projects/workspaces. If, instead, you wish to have your P2 compile and download tasks unique to each your projects then go to the Project Tasks page.
This document is being developed over time as we prove-out a working environment for each of our target platforms.
To date, we have installations, compilation and downloading from Windows, MacOS, and RaspiOS (the Raspberry Pi OS - a Debian derived distribution). This RaspiOS method should also work for any other Debian derived distribution such as Ubuntu or, of course, Debian itself.
Also, to date, we have building and download for flexprop and PNut (PNut is widows or windows emulator only.) with direct USB-attached boards.
In the future, we are also expecting to document building and download with via Wifi with the Wx boards attached to our development board, and with more compilers as they come ready for multi-platform use, etc.
On this Page:
- VSCode development of P2 Projects - basic development life-cycle
- P2 Code Development with flexprop on macOS - setting up
- P2 Code Development with flexprop on Windows - setting up
- P2 Code Development with flexprop on Raspberry Pi - setting up
- P2 Code Development with PNut on Windows - setting up
- Being consistent in your machine configuration - why we are doing things this way
- Installation and Setup - preparing your machine for P2 development using tools from within vscode
- Tasks in VScode - this provides more detail about vscode tasks and lists work that is still needing to be done
Additional pages:
- TOP Level README - Back to the top page of this repo
- Setup focused on Windows only - All Windows notes from within this page
- Setup focused on macOS only - All macOS notes from within this page
- VSCode REF: Tasks - Offsite: VSCode Documentation for reference
NOTE: The "P2 Code Development..." sections below provide step-by-step setup instructions
Latest Updates:
18 Jul 2023
- Adopting formal install locations
- Made FlexProp and PNut setup the same steps for each
10 Apr 2023
- Added Windows specific setup page
15 Mar 2023
- Added macOS specific setup page
20 Dec 2022
- Raspberry Pi instructions tested and ready for use!
- Windows instructions tested and ready for use (both flexprop and PNut)!
- (PNut tasks are now merged into our task list. They just don't do anyting on non-windows platforms)
19 Dec 2022
- Started this page
- MacOS instructions tested and ready for use!
- Testing underway for Raspberry Pi then Windows
By choosing to adopt the Custom Tasks described in this document along with the keybindings your work flow is now quite sweet.
- Create a new project
- Add existing files you have already created or are using from P2 Obex.
- Create your new top-level file.
- Add
{projectDir}/.vscode/settings.json3-line file to identify the top-level file for the build tasks.
Iterate until your project works as desired:
- Make changes to file(s)
- Compile the files to see if they compile cleanly (cmd-shift-B) on which ever file you are editing
- Once the files compile cleanly
- Download and test (ctrl-shift-D, F10) [if you use keybindings shown in examples on this page]
- Alternatively, download your project to FLASH and test (ctrl-shift-F, F11) [if you use keybindings shown in examples on this page]
To complete your setup so you can use flexprop on your mac under VScode you'll need to:
One time:
- Install FlexProp for all users to use on your Mac
- Add our tasks to the user tasks.json file (works across all your P2 projects)
(Make sure the paths to your compiler and loader binaries are correct) - Install our common keybinding (works across all your P2 projects)
- Optionally add a couple of VSCode extensions if you wish to have the features I demonstrated
- "Error Lens" which adds the compile errors messages to the associated line of code
- "Explorer Exclude" which allows you to hide file types (e.g., .p2asm, .binary) from the explorer panel
For each P2 Project:
- Install a settings.json file identiyfing the project top-level file
- Make sure the name of your top-level file is correctly placed in this settings.json file
To complete your setup so you can use flexprop on your Windows machine under VScode you'll need to:
One time:
- Install FlexProp for all users to use on your windows machine
- Add our tasks to the user tasks.json file (works across all your P2 projects)
(Make sure the paths to your compiler and loader binaries are correct) - Install our common keybinding (works across all your P2 projects)
- Optionally add a couple of VSCode extensions if you wish to have the features I demonstrated
- "Error Lens" which adds the compile errors messages to the associated line of code
- "Explorer Exclude" which allows you to hide file types (e.g., .p2asm, .binary) from the explorer panel
For each P2 Project:
- Install a settings.json file identiyfing the project top-level file
- Make sure the name of your top-level file is correctly placed in this settings.json file
To complete your setup so you can use flexprop on your Raspberry Pi under VScode you'll need to:
One time:
- Install FlexProp for all users to use on your RPi
- Enable USB PropPlug recognition on RPi
- Add our tasks to the user tasks.json file (works across all your P2 projects)
(Make sure the paths to your compiler and loader binaries are correct) - Install our common keybinding (works across all your P2 projects)
- Optionally add a couple of VSCode extensions if you wish to have the features I demonstrated
- "Error Lens" which adds the compile errors messages to the associated line of code
- "Explorer Exclude" which allows you to hide file types (e.g., .p2asm, .binary) from the explorer panel
For each P2 Project:
- Install a settings.json file identiyfing the project top-level file
- Make sure the name of your top-level file is correctly placed in this settings.json file
To complete your setup so you can use PNut on your Windows machine under VScode you'll need to install PNut and then:
One time:
- Install a tasks.json file (works across all your P2 projects)
- Make sure the names of your compiler and loader binaries are correct (we use the .bat file to run PNut, we don't refer to PNut.exe directly!)
- Install a common keybinding (works across all your P2 projects)
- Optionally add a couple of VSCode extensions if you wish to have the features I demonstrated
- "Error Lens" which adds the compile errors messages to the associated line of code
- "Explorer Exclude" which allows you to hide file types (e.g., .p2asm, .binary) from the explorer panel
For each P2 Project:
- Install a settings.json file identiyfing the project top-level file
- Make sure the name of your top-level file is correctly placed in this settings.json file
I have mostly macs for development but I also have a Windows machine and a number of Raspberry PIs (derived from Debian Linux Distribution (distro.)) and even some larger Ubuntu Machines (also derived from Debian Linux distro.). If you, like me, intend to be able to run VSCode on many of your development machines and you want to make your life easier then there are a couple of things we know already that can help you.
-
Synchronize your VSCode settings and extensions automatically by installing and using the Settings Sync VScode extension. Any changes you make to one machine then will be sync'd to your other VScode machines.
-
Be very consistent in where you install tools for each type of OS. (e.g., for all Windows machines make sure you install say, FlexProp, in the same location on each Windows machine.) By being consistent your tasks will run no matter which machine your are running on. There is nothing worse than trying to remember where you installed a specific tool on the machine you are currently logged into. Because you install say FlexProp in the same place on all your Raspberry Pi's you will know where to find it no matter which RPi you are logged in to.
- All like operating systems should have a specific tool installed in the same location on each. (e.g., all Windows machines have FlexProp installed in one location, all macOS machines have FlexProp installed in a different location that on Windows but it is the same location across all Macs, etc.)
- During the first-time installation of a tool on a machine, finish the process by configuring the PATH to the tool so that terminals/consoles can access the tool by name. This allows VSCode to run the tool from its build tasks.json file without needing to know where the tool is installed! On Windows machines this is done by editing the User Environment PATH variable from within the Settings Application. On Mac's and Linux machines (RPi's) this is done by editing the shell configuration file (e.g., Bash you edit the ~/.bashrc file) and adjusting the
export PATH=...line/lines.
On the Raspberry Pi platform we'll use git(1) to download the FlexProp souce, but on the MacOS and Windows machines we get the latest binaries by downloading a flexprop-{version}.zip file from the FlexProp Releases Page and upacking the zip file to produce a flexprop folder containing the new version.
NOTE: The flexprop toolset does not have a standard install location. So we will likely have many locations amongst all of us P2 users. You have to take note of where you installed it and then adjust the following examples to point to where your binaries ended up on your file system. Alternatively, it should be safe to just follow what I do in these instructions explictly. This has the benefit that more of us will be able to help each other out with tools problems as more of us will be set up the same.
Next we move this new version into place depending upon our OS. Follow the instructions below for your particular platform.
On my Mac's, I install the FlexProp into a folder which I've created at /Applications/flexprop and I set the PATH to point to the /Applications/flexprop/bin directory. I move all of the content of the flexprop folder (created during the unzip) to the /Applications/flexprop folder.
If I'm updating to a new verison I do the following:
- Remove
/Applications/flexprop-prior - Rename the
/Applications/flexpropto/Applications/flexprop-prior - Create a new empty
/Applications/flexpropfolder - Move all of the content of the
flexpropfolder (created during the unzip) to the/Applications/flexpropfolder
On my raspberry Pi's I run rspios as distributed by raspberrypi.org from the downloads page
I tend to want the best performance from my gear so on my RPi-3's and RPi-4's I tend to run the 64bit raspios.
I've been doing this for quite a while and have a small farm of RPi's. I tend to place the image on a uSD card and then boot from it initially with a keyboard and screen attached. I then "welcome" my new machine to my network and time zone and give it a hostname unique and generally fortelling of this purpose of this new RPi. I also end up running the classic update sequence to ensure my new machine has the latest software available as well as all the latest security patches:
# my update process which I run each time when I first log into my machine after a bit of time away
$ sudo apt-get update
$ sudo apt-get dist-upgradeAfter the new RPi can boot and automatically attach to my network I then remove the screen and keyboard. I run most my RPi's remotely and "headless" (meaning no screen/keyboard attached.)
The Parallax PropPlug has a custom parallax VID:PID USB pair and as such is not, by default, recognized by raspiOS when you first plug in the PropPlug.
The fix is to add a custom udev rules file as decribed in FTDI Technical Note 101
I added the file /etc/udev/rules.d/99-usbftdi.rules
$ sudo vi /etc/udev/rules.d/99-usbftdi.rulesand then added the content:
# For FTDI FT232 & FT245 USB devices with Vendor ID = 0x0403, Product ID = 0x6001
SYSFS{idProduct}==”6001”, SYSFS{idVendor}==”0403”, RUN+=”/sbin/modprobe –q ftdi- sio product=0x6001 vendor=0x0403”After this file was saved, I rebooted the RPi. After the RPi came back up I plugged in the PropPlug I saw /dev/ttyUSB0 appear as my PropPlug.
Installing the flexprop toolset on the Raspberry Pi (raspos, or any debian derivative, Ubuntu, etc.) is a breeze when you follow Eric's instructions that just work!
In my case, I used Eric's suggestion to instruct the build/install process to install to /opt/flexprop. When you get to the build step in his instructions use:
# build flexprop then install flexprop in /opt/flexprop
sudo make install INSTALL=/opt/flexprop(NOTE We use sudo because the normal user is not able to write in the /opt tree.)
Additionally, I added a new PATH element in my ~/.profile file to point to the flexprop bin directory. Now if you are running interactively on this RPi you can reference the flexprop or loadp2 executables by name and they will run.
If I'm updating to a new verison I do the following:
# remove old prior version
sudo rm -rf /opt/flexprop-prior
# move current to prior
sudo mv /opt/flexprop /opt/flexprop-prior
# navigate to source tree
cd ~/src/flexprop
# erase prior build
make clean
# update to latest in repo
git pull
# build flexprop then install flexprop in /opt/flexprop
sudo make install INSTALL=/opt/flexprop[Optional] if you want to remote into your windows machine from a another desktop running VSCode on your network then you want to install OpenSSH client and server by following: Install OpenSSH.
Get the latest binaries by downloading a flexprop-{version}.zip file from the FlexProp Releases Page.
Create a directory called "flexprop" (or whatever you'd like) and unpack the .zip file into that directory. Make sure the directory you create is writable, so do not unpack into a system directory like "Program Files". Use your desktop or a folder directly under "C:" instead.
Finish up by then add a new PATH element and make sure to also create the new Environment Variable FlexPropDir. The User Tasks expect this environment variable to exist. They use it to locate the flash utility binary file.
Like we do on the other platforms here's the suggested update strategy:
- Download and zip the latest version from FlexProp Releases Page
- Remove any
{flexPropFolder}-prior(the prior version of flexprop) - Rename your existing folder to
{flexPropFolder}-prior - Unpack the .zip into a newly created
{flexPropFolder}
The PNut compiler/debug tool does not have a standard install location. So we will likely have many locations amongst all of us P2 users. You have to take note of where you installed PNut and then add a new PATH element using the windows settings app. to point to where your binaries ended up on your file system.
Download the latest .zip file from PNut/Spin2 Latest Version Forum thread into my Downloads folder. Unpack the .zip into its own folder.
Propeller Tool installs into C:\Program Files (x86)\Parallax Inc\Propeller Tool\. So I just created a sibling directory: C:\Program Files (x86)\Parallax Inc\PNut\ and copy all of the unpacked files into that directory.
NOTE: if you experience problems with the tasks running PNut it is generally that the .bat files are not identifying the pnut executable by the correct name. At each install check the content of \PNut\pnut_shell.bat and \PNut\pnut_report.bat and make sure the pnut versioned name is correct with what's in the folder. Occasionally Chip forgets to modify these .bat files before release.
I right-mouse on the PNut_{version}.exe file and select "Pin to taskbar".
I then add a new PATH element using the windows settings app. to point to where your binaries ended up on your file system. In my case I added a path segment pointing to C:\Program Files (x86)\Parallax Inc\PNut\.
I haven't found the need to keep any prior version. I simply:
- Download the latest version of PNut from PNut/Spin2 Latest Version into my Downloads folder
- Unpack the .zip file
- In my taskbar I right-mouse on the PNut icon and select "Unpin from taskbar"
- Select all content within
C:\Program Files (x86)\Parallax Inc\PNut\and Delete it - Move all of unpacked content into the now empty folder
C:\Program Files (x86)\Parallax Inc\PNut\ - I right-mouse on the newly copied PNut_{version}.exe file and select "Pin to taskbar".
NOTE: if you experience problems with the tasks running PNut it is generally that the .bat files are not identifying the pnut executable by the correct name. At each install check the content of \PNut\pnut_shell.bat and \PNut\pnut_report.bat and make sure the pnut versioned name is correct with what's in the folder. Occasionally Chip forgets to modify these .bat files before release.
On windows the search path for programs is maintained by the Windows Settings App. Open Window Settings and search for "environment" and you should see two choices: "Edit the system environement variables" and "Edit enviroment variables for your account". If you want the tools to work for all users on this Windows machine then adjust the PATH values by editing the system environment variables. If, instead, you only need the tools to work for your account then edit the enviroment variables for your account.
You will do this for each of FlexProp and PNut (which ever ones you use.)
If you are using FlexProp, in addition to modifying the PATH variable, you will also need to add a new Environment Variable which points to the FlexProp install folder.
In the same section you modified for path (system environment or your account environment) using [New...] add a new environment variable FlexPropPath which you will set to your install folder using the [Browse Directory...] button after pressing [New...] and typing in the FlexPropPath name. The tasks we define will use this environment variable to locate the binary file it needs when downloading to FLASH.
NOTE the above is referring to Windows 10 settings names. On earlier versions of Windows the concept is the same. Locate the environment values and make the appropriate changes.
On MacOS this is really shell dependent. I tend to stick with Bash as I've used it for many 10s of years now. zsh (ZShell) is the new shell on the block (well, new to mac's not a new shell.) I avoided moving to it but the concepts are the same.
On my Macs I install the flexprop folder into my /Applications folder. I then edit my .bash_profile and add the following line. (I have multiple lines such as this for various tools I've installed.)
export PATH=${PATH}:/Applications/flexprop/binFrom here on when I start new terminal windows we can invoke the flexprop binaries by name without using the path to them.
On my raspberry Pi's I run rspios which is a Debain GNU Linux derived distribution. [Fun! See The Periodic Table of Liux Distros]
So, as you might have guessed, I use Bash here too. On RPi I tend to install special tools from others, as well as those I make, under /opt. So, in the case of flexprop I install it on all my RPis into /opt/flexprop/.
Unlike my Macs which have .bash_profile, my RPis have, instead, a .profile file. So here I edit the RPi ~/.profile. I'm using the pattern for "optionally installed tools" so that I can sync this .profile between my many RPi's.
I edit my ~/.profile and add the path to flexprop. (I have multiple groups of lines such as this for various tools I've installed.)
# set PATH so it includes optional install of flexprop/bin if it exists
if [ -d "/opt/flexprop/bin" ] ; then
PATH="$PATH:/opt/flexprop/bin"
fiFrom here on when I start new terminal windows we can invoke the flexprop binaries by name without using the path to them.
A Task is how we integrate with External tools in VScode.
See: VSCode "Tasks" Reference Page
There are a number of types of tasks and places Task definitions live. These include Auto-detected Tasks, User level tasks, and Custom Tasks. Tasks when run, can be crafted to depend upon the running of other tasks See: Compound Tasks Some tasks can be run in background such as file watchers which execute when a file has been changed.
When you run VScode on multiple operating systems and want to be able to run a projects tasks on whichever machine you are on then you can specify os-specific alternatives to be used withing the task. See Operating system specific properties
Another VSCode mechanism we are determining if it will be useful is the: Task Provider Extension. If we find this is useful we can add a Task Provder element to our existing extension in order to facilitate our updating task files we use for P1 and P2 development.
...More TBA...
Tasks can be invoked with the search, identify, run technique or they can have keyboard shortcuts assigned to them.
A project can have a single default build task which is, by default, invoked with command-shift-B.
We'll configure our compileP2 task to be the default.
We'll add a downloadP2 task and assign command-shift-D to it. It will depend upon the compile task which makes it run first and then we download the newly compiled result.
We'll add a flashP2 task and assign command-shift-F to it. It will depend upon the compile task which makes it run first and then we download the newly compiled result and write it to FLASH.
TODO-1: We need to ensure download or flash doesn't proceed if compile fails
TODO-2: We'll also test using the file-watch technology to automatically compile and download our project files when they are modified.
To define the tasks we are going to use with our P2 development in most of our projects we place the task definitions in a central "User Tasks" .json file.
To get to this file type in Ctrl+Shift+P (Cmd+Shift+P on mac) to get to the command search dialog. Then type in "tasks". Lower down in the resulting filtered list you should now see "Tasks: Open User Tasks". Select it and you should now have a file open in the editor which should contain at least:
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
]
}In between the [] you can place your new task definitions. You should end up with something like:
{
"version": "2.0.0",
"tasks": [
{
"label": "compileP2",
"type": "shell",
"osx": {
"command": "/Applications/flexprop/bin/flexspin.mac"
},
"windows": {
"command": "flexspin.exe"
},
"linux": {
"command": "/opt/flexprop/bin/flexspin"
},
"args": ["-2", "-Wabs-paths", "-Wmax-errors=99", "${fileBasename}"],
"problemMatcher": {
"owner": "Spin2",
"fileLocation": ["autoDetect", "${workspaceFolder}"],
"pattern": {
"regexp": "^(.*):(\\d+):\\s+(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
},
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "compileTopP2",
"type": "shell",
"osx": {
"command": "/Applications/flexprop/bin/flexspin.mac"
},
"windows": {
"command": "flexspin.exe"
},
"linux": {
"command": "/opt/flexprop/bin/flexspin"
},
"args": ["-2", "-Wabs-paths", "-Wmax-errors=99", "${config:topLevel}.spin2"],
"problemMatcher": {
"owner": "Spin2",
"fileLocation": ["autoDetect", "${workspaceFolder}"],
"pattern": {
"regexp": "^(.*):(\\d+):\\s+(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
},
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "downloadP2",
"type": "shell",
"osx": {
"command": "/Applications/flexprop/bin/loadp2.mac",
"args": ["-b230400", "${config:topLevel}.binary", "-t"]
},
"windows": {
"command": "loadp2.exe",
"args": ["-b230400", "${config:topLevel}.binary", "-t"]
},
"linux": {
"command": "/opt/flexprop/bin/loadp2",
"args": ["-b230400", "${config:topLevel}.binary", "-t", "-p/dev/ttyUSB0"]
},
"problemMatcher": [],
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "test",
"isDefault": true
},
"dependsOn": ["compileTopP2"]
},
{
"label": "flashP2",
"type": "shell",
"osx": {
"command": "/Applications/flexprop/bin/loadp2.mac",
"args": ["-b230400", "@0=/Applications/flexprop/board/P2ES_flashloader.bin,@8000+${config:topLevel}.binary", "-t", "-k"]
},
"windows": {
"command": "loadp2.exe",
"args": ["-b230400", "@0=${env:FlexPropPath}/board/P2ES_flashloader.bin,@8000+${config:topLevel}.binary", "-t", "-k"]
},
"linux": {
"command": "/opt/flexprop/bin/loadp2",
"args": ["-b230400", "@0=/opt/flexprop/board/P2ES_flashloader.bin,@8000+${config:topLevel}.binary", "-t", "-p/dev/ttyUSB0"]
},
"problemMatcher": [],
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "test",
"isDefault": true
},
"dependsOn": ["compileTopP2"]
},
{
"label": "compilePNut2",
"type": "shell",
"command": "echo",
"args": ["Avail on windows only!"],
"windows": {
"command": "pnut_shell.bat",
"args": ["${fileBasename}", "-c"]
},
"problemMatcher": {
"owner": "Spin2",
"fileLocation": ["autoDetect", "${workspaceFolder}"],
"pattern": {
"regexp": "^(.*):(\\d+):\\s*(warning|error):\\s*(.*)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
},
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "compileTopPNut2",
"type": "shell",
"command": "echo",
"args": ["Avail on windows only!"],
"windows": {
"command": "pnut_shell.bat",
"args": ["${config:topLevel}.spin2", "-c"]
},
"problemMatcher": {
"owner": "Spin2",
"fileLocation": ["autoDetect", "${workspaceFolder}"],
"pattern": {
"regexp": "^(.*):(\\d+):\\s+(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
},
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "build",
"isDefault": true
}
},
{
"label": "downloadPNut2",
"type": "shell",
"command": "echo",
"args": ["Avail on windows only!"],
"windows": {
"command": "pnut_shell.bat",
"args": ["${config:topLevel}.spin2", "-r"]
},
"problemMatcher": {
"owner": "Spin2",
"fileLocation": ["autoDetect", "${workspaceFolder}"],
"pattern": {
"regexp": "^(.*):(\\d+):\\s+(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
},
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "test",
"isDefault": true
}
},
{
"label": "flashPNut2",
"type": "shell",
"command": "echo",
"args": ["Avail on windows only!"],
"windows": {
"command": "pnut_shell.bat",
"args": ["${config:topLevel}.spin2", "-f"]
},
"problemMatcher": {
"owner": "Spin2",
"fileLocation": ["autoDetect", "${workspaceFolder}"],
"pattern": {
"regexp": "^(.*):(\\d+):\\s+(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"severity": 3,
"message": 4
}
},
"presentation": {
"panel": "shared",
"focus": true
},
"group": {
"kind": "test",
"isDefault": true
}
}
]
}This provides the following Build and Test tasks:
Under Task: Run Build Task:
- CompileP2 - Compile current file [ctrl-shift-B]
- CompilePNut2 - Compile current file using PNut (Windows only)
- CompileTopP2 - Compile the top-file of this project
- CompileTopPNut2 - Compile the top-file of this project using PNut (Windows only)
Under Task: Run Test Task:
- DownloadP2 - Download the binary to RAM in our connected P2
- DownloadPNut2 - Download the binary to RAM using PNut (Windows only)
- FlashP2 - Download and write the binary to FLASH in our connected P2
- FlashPNut2 - Download and write the binary to FLASH using PNut (Windows only)
As written, downloadP2 and flashP2 for flexpsin will always be preceeded by a compileTopP2, while the downloadPNut2 and flashPNut2 do not have any depedencies as they do their own build of the top-level file.
The downloadPNut2 and flashPNut2 tasks do NOT enable debug support. The option -r is run without debug while -rd is run with debug. Likewise, the option -f is compile and flash without debug while -fd is compile and flash with debug. Please adjust these values in the task args: sections to your need (using debug or not)
TODO let's make debug a custom VSCode setting and use the setting in this script to enable/disable debug compilation/use??
To add our custom key bindinds we place new content in the keybindings.json file.
To get to this file type in Ctrl+Shift+P (Cmd+Shift+P on mac) to get to the command search dialog. Then type in "keyboard". Lower down in the resulting filtered list you should now see "Preferences: Open Keyboard Shortcuts (JSON)". Select it and you should now have a file open in the editor which should contain at least:
// Place your key bindings in this file to override the defaultsauto[]
[
]In between the [] you can place your new key bindings. You should end up with something like:
NOTE: in the following you may wish to use cmd in place of ctrl for macOS to remain consistent with other VSCode settings on your Mac!
// Place your key bindings in this file to override the defaultsauto[]
[
{
"key": "ctrl+shift+d",
"command": "workbench.action.tasks.runTask",
"args": "downloadP2"
},
{
"key": "ctrl+shift+f",
"command": "workbench.action.tasks.runTask",
"args": "flashP2"
},
{
"key": "F8",
"command": "workbench.action.tasks.build",
"args": "compileP2"
},
{
"key": "F10",
"command": "workbench.action.tasks.runTask",
"args": "downloadP2"
},
{
"key": "F11",
"command": "workbench.action.tasks.runTask",
"args": "flashP2"
}
]This adds new keyboard short cuts to our tasks:
- CompileP2 - Compile current file [ctrl-shift-B], [F8]
- CompileTopP2 - Compile the top-file of this project
- DownloadP2 - Download the binary to RAM in our connected P2 [ctrl+shift+d] or [F10]
- FlashP2 - Download and write the binary to FLASH in our connected P2 [ctrl+shift+f] or [F11]
NOTE: you can see that these key bindings only refer to the FlexProp tasks. In, instead, you'd like them to use the PNut tasks then you can replace the P2 command suffix with PNut2 causing the PNut versions to be run for the shortcuts.
In order to support our notion of top-level file and to prevent us from occassionally compiling and downloading a file other than the project top-level file we've adopted the notion of adding a CompileTopP2 build task a DownloadP2 download task, and in some cases a FlashP2 task.
When we request a download or flash the automation will first compile the top-level project source which produces a new binary. It is this new binary that will be downloaded/flashed.
We have multiple tasks that need to know the name of our top-level file. So we add a new settings file with a topLevel value to our project:
.vscode/settings.json file contains the following contents:
{
"topLevel": "jm_p2-es_matrix_control_demo",
}
Once we have this file in place, then our tasks.json file can access this value using the form: ${config:topLevel}
Now our CompileTopP2 task can create the toplevel filename using ${config:topLevel}.spin2
You need to find the line containing "jm_p2-es_matrix_control_demo" and replace this name with the name of your top-level file.
And our DownloadP2 task can reference the binary file using ${config:topLevel}.binary
NOTE the PNut flasher is special in that it wants the .spin2 filename not a .binary filename so you'll see ${config:topLevel}.spin2 being used in the FlashPNut2 task.
Copyright © 2023 Iron Sheep Productions, LLC.
Licensed under the MIT License.
Follow these links for more information: