-
Notifications
You must be signed in to change notification settings - Fork 71
Software Changes for New Platforms
Mark Fisher edited this page Feb 19, 2024
·
3 revisions
When Adding a new platform, the following must be add to fujinet-firmware repository in order for it to be built by the build tools and github autodeploy:
- a new entry in
build-platforms/
for the platformio.ini templating, just the files existence will make it work when anything refers to it, follow naming convention ofplatformio-{build_board}.ini
- a new entry in
data/webui/config
+data/webui/device_specific
for WebUI templating. Name it{build_board}.yaml
, this controls which parts of the WebUI are enabled when user configures it via web
The build_board
name should follow a similar pattern to other boards, e.g. fujinet-<host>-<board>
.
Once your build is stable, and devices working well, you can add the following to ensure it gets built on every code change to fujinet-firmware:
- a new entry in .github/workflows, and refer to the name in
autobuild.yml
for github autobuild.
Copyright 2024 Contributors to the FujiNetWIFI project.
Join us on Discord: https://discord.gg/7MfFTvD
- Home
- What is FujiNet?
- The Definition of Done
- Board bring up for FujiNet Platform.IO code
- The Complete Linux CLI Guide
- The Complete macOS CLI Guide
- Development Env for Apps
- FujiNet-Development-Guidelines
- System Quickstarts
- FujiNet Flasher
- Setting up a TNFS Server
- FujiNet Configuration File: fnconfig.ini
- AppKey Registry - SIO Command $DC Open App Key
- CP-M Support
- BBS
- Official Hardware Versions
- Prototype Board Revisions
- FujiNet Development Guidelines
- Atari Programming
- Apple Programming
- C64 Programming
- ADAM Programming
- Testing Plan
- Hacker List
- FujiNet VirtualMachine