...
- Currently able to flag the firmware to upload to the flash, but worried that we cannot do that with the debugger for the first time
- The debugger generates a hex file and uses ozone & Jlink
- Even if it doesn’t work the first time, we can use programmer to flash all the boards for the first time and then use the debugger
- Have 5 devices that can program on pyxida
- Next time, talk about better handling of launches for firmware, more detailed specification on how we configure boards, how we read the flash
- Also, clean Github issues
- Want to be able to inspect stuff through CLI, so that when you connect USB, you can control stuff, read out flash/config
- Currently, pyxida check during startup if USB is connected, if so, then it goes into a state where you can issue some commands (not well-defined though and needs to be fixed)
- Tasks for firmware:
- Downloading flask through ground station
- Configuring from ground station (in any state we’re at)
- Some way to read out configuration values and modify them/update them to pyxida, also need to have default config values
- Need the ram values for configuration to be updated
- All of this needs to be relayed back to ground station in messages, letting us know when something has been modified/updated
100-110m
- Work on ground station needs to happen.
- We need someone working on ground station.
- Need to implement configuring through ground station. There's a firmware task here too.
- Connect to pyxida and read/write config values.
- Pyxida will need some way to restart after this
- There is no official way to get data from Pyxida
- There might exist a script that might help us read from flash.
- We still need to figure out how to merge all of the features
- moving to the next hardware iteration?
- We need to figure out if current code is compatible with new hardware