Flash

Flash: 2048 B at once??

Flowcharts

Sensor overflows etc.

Main problem:

6.1 wasn't working because barometer is not written

6.0 trying to operate in radio free environment, config cumbersome (compiling required), and not well documented.

Also, didn't know what firmware does when powered on after the launch.

Downloading the data is completely documented, there is a python script somewhere, but we should integrate that in firmware.

Also, some commented out stuff in the firmware for flash downloading.

We shouldn't erase flash in general.

A lot of data corruption happening.

Maybe implement forward error correction?

 

Beginning of flash: write the structure of a logFrame in the header. Definitely write down diagnostic information.

Data logging is the core feature.

 

SPI flash: single vs dual vs quad FLASH mode - important to talk about for the new flight computer.

Cameras

Cameras have UART, not on the mini USB, but inside. Two pins of the USB aren't connected to anything, so we could port UART through there.

Could we use USB 3.0 A on the BBC side? That would just be decreasing the strength of the connection. Dennis tried to replace the connectors 

 

We should parse camera UART output on a different MCU, not Pyxida, as it could take away cycles we need.

 

Cameras might not have UART, so in that case, we need to do the LED solution.

 

We could check out STM32s.

 

One option: LED option

4 cameras

IO expander (MCP23017)

Talk over I2C

 

2nd option: embed ATMEGA

as an IO expander

Same as 1st, we get rid of processing lights on pyxida

 

3rd option: STM32 option

 

 

  • No labels