View Source

10-20m

No test flights
Pick a lockdown date for code
Discuss Error State (Flag all errors that happen in prelaunch)
Get someone to keep track of what's going on with hardware
Create wiki page that has chart of all Pyxida versions we know of.
- Record date, version, etc. that we know of

80-90m

90-100m

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)

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