You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://github.com/apertus-open-source-cinema/AXIOM-Remote/actions/workflows/firmware-build.yml)
```/Archive/``` contains old outdated projects related to the AXIOM Remote.
28
28
29
-
```/AXIOM_Remote_Firmware_Visualizer/``` contains the AXIOM Remote Visualizer - a tool to emulate the actual code running on the PIC32 and pixels displayed on the 320x240 LCD on a PC.
29
+
```/AXIOM_Remote_Firmware_Visualizer/``` contains the AXIOM Remote Visualizer - a tool to emulate the actual code running on the RP2040 and pixels displayed on the 320x240 LCD on a PC.
30
30
31
-
```/Bootloader/``` The Bootloader will be used for handling of periphery (LCD, USB-UART, I2C) and updating the firmware of the main PIC32 and also the east and west PIC16s (key managers) without a dedicated programming hardware.
31
+
```/Bootloader/``` The Bootloader will be used for handling of periphery (LCD, USB-UART, I2C) and updating the firmware.
32
32
33
33
```/Common/``` contains general code and definition that are used in several projects in this repository.
34
34
@@ -42,11 +42,11 @@ for details see: LICENSE.txt
42
42
43
43
## Build instructions
44
44
45
-
### Fetch the Microchip XC32/XC32++ compiler for your OS
45
+
### Setup RP2040 Build Environment
46
46
47
-
[https://www.microchip.com/mplab/compilers](https://www.microchip.com/mplab/compilers). We have tested the code up to compiler version 3.0.
47
+
Before building, you need to set up the Raspberry Pi Pico SDK and toolchain. Please follow the official guide for your operating system: [https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf](https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf)
48
48
49
-
To be able to build, the variable **XC32_PATH** in the Makefile of firmware and bootloader has to be adjusted to the actual install path of XC32.
49
+
Ensure the `PICO_SDK_PATH` environment variable is set correctly.
50
50
51
51
### Bootloader
52
52
@@ -57,35 +57,19 @@ To be able to build, the variable **XC32_PATH** in the Makefile of firmware and
57
57
58
58
### Firmware
59
59
60
-
- Open **Firmware** folder in terminal
61
-
- Execute **make** or when rebuilding **make clean && make**
62
-
-**HEX** and **ELF** files would placed in the **build** folder
60
+
- Open the **Firmware** folder in a terminal.
61
+
- Create a build directory: `mkdir build`
62
+
- Change into the build directory: `cd build`
63
+
- Run CMake: `cmake ..`
64
+
- Run Make: `make`
65
+
- The build output, including the `axiom_remote.uf2` file, will be in the `build` folder.
63
66
64
67
## Flash instructions
65
68
66
-
Note that with the current hardware the PICKit2 needs to stay connected for normal operation even when flashing has been completed as the PICkit2 pulls down the RESET signal.
67
-
68
-
### IPE
69
-
70
-
- Open IPE and connect to your PICKit3 or later, drag and drop the HEX file into the IPE window
71
-
- Click **Program**, after a moment it should be finished and main menu with 6 buttons shown
72
-
73
-
### pic32prog
74
-
75
-
- Acquire binary or build from source from: <https://github.com/sergev/pic32prog> to flash with PICKit2
76
-
- run **pic32prog yourfile.hex** and you should see a progress bar of the flashing/verification process
77
-
78
-
If ```pic32prog``` only works with ```sudo``` add your user to the plugdev group and add the following udev rule to /etc/udev/rules.d/26-microchip.rules (create file if it does not exist) and reboot:
The idVendor should be looked up with ```lsusb```, in case of the PICkit2 it looks like this:
85
-
86
-
```
87
-
Bus 003 Device 002: ID 04d8:0033 Microchip Technology, Inc. PICkit2
88
-
```
69
+
- Connect the AXIOM Remote to your computer via USB while holding down the `BOOTSEL` button on the RP2040 board.
70
+
- It will mount as a mass storage device named `RPI-RP2`.
71
+
- Drag and drop the `Firmware/build/Axiom_Remote_Firmware.uf2` file onto the `RPI-RP2` volume.
72
+
- The board will automatically reboot and run the new firmware.
89
73
90
74
## Development Environment
91
75
@@ -94,7 +78,6 @@ This means its important to open the root folder of this repo in VS code.
94
78
95
79
We recommend installing the VsCode Action Buttons extension: <https://marketplace.visualstudio.com/items?itemName=seunlanlege.action-buttons> and configurations (.vscode/settings.json) to add buttons to compile and flash the AXIOM Remote.
96
80
97
-
98
81
### Developing inside Docker container
99
82
100
83
To avoid the need to install all the required and helpful tools, you can also use a Docker container we provide for development. Follow the steps to set it up in VSCode:
0 commit comments