diff --git a/Node Firmware/Bin/NucleoCC2.bin b/Node Firmware/Bin/NucleoCC2.bin deleted file mode 100644 index f359f00..0000000 Binary files a/Node Firmware/Bin/NucleoCC2.bin and /dev/null differ diff --git a/Node Firmware/Platforms/How to import a platform into STM32CubeIDE.pdf b/Node Firmware/Platforms/How to import a platform into STM32CubeIDE.pdf deleted file mode 100644 index 875f613..0000000 Binary files a/Node Firmware/Platforms/How to import a platform into STM32CubeIDE.pdf and /dev/null differ diff --git a/Node Firmware/Platforms/NucleoCC2.zip b/Node Firmware/Platforms/NucleoCC2.zip deleted file mode 100644 index 21edaa0..0000000 Binary files a/Node Firmware/Platforms/NucleoCC2.zip and /dev/null differ diff --git a/Node Firmware/Platforms/Read.ME b/Node Firmware/Platforms/Read.ME deleted file mode 100644 index 6ca72f9..0000000 --- a/Node Firmware/Platforms/Read.ME +++ /dev/null @@ -1,2 +0,0 @@ -Please note that in this version, and going forward, the Nucleo code has been renamee to 'NucleoCC2', to reflect is commercial -product number. diff --git a/Node Firmware/Readme.md b/Node Firmware/Readme.md index 3a52d42..543d31c 100644 --- a/Node Firmware/Readme.md +++ b/Node Firmware/Readme.md @@ -1,21 +1,9 @@ # Node Firmware This directory contains the code sources. The current source code is at Rev level 1.1. -Setting up a CubeIDE development project has several steps: -1. Download the code from this site. -2. Unzip it after the download -3. Navigate to the 'platforms' directory, and unzip the project for the appropriate platform. -4. Import the project into CubEIDE and Add the source code to it (see .pfd doc for instructions). -5. Build the code and download. +Due to a new release of CubeIDE, the platform code is out of date and has been temporarily removed until +a new release is ready, which is imminent. -The reasoning behind it is because goign forward several platforms are being supported, the code iteself -is platform independent, so it can be shared between them. The platform code has the device specifics -and should not need to be updated each time a release is made, however it is probably good practice to -update it each time. +If you need a copy rignt away, please email me VE6VH at ve6vh dot org -There are pre-built binaries in the Bin directory for platforms that support a download. -Currently supported platforms: -Nucleo CC Experimenter node - -Release notes are in the node software document in the documentation directory. diff --git a/README.md b/README.md index caa862a..e07240c 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,14 @@ Welcome to the IP400 project. -The directories here have been restructured. The code directory contains the hardware abstraction for several platforms, +The directories here have been restructured. The Node Firmware directory contains the hardware abstraction for several platforms, and the source directory contains code that is common to all. +The platform code and precompiled binaries have been temporarily removed, due to a new repease of the CubeIDE from ST, and +a pending new release of the node firmware. + +The Raspberry Pi code is now available on the disk image, which can be downloaded from the project website, ip400.adrcs.org, +from the 'Getting Started' link on the hardware page. + The current revision level is 1.0 See the release notes in the 'IP400 Node Software' document. diff --git a/Raspberry Pi/Read.Me b/Raspberry Pi/Read.Me deleted file mode 100644 index bc32a84..0000000 --- a/Raspberry Pi/Read.Me +++ /dev/null @@ -1,2 +0,0 @@ -This code can now be found on the Pi Zero disc image, which is in the -files directory of the ip400 group on groups.io.