adkaster/eece-capstone

Repository to store software work products for capstone

eece-capstone's Issues

Messaging library unit tests

• Get gtest compiling and running with CCS
• Write unit tests for Andrew's messaging library

This might require some refactoring of the messaging library to make it more testable.

Initial Design Review

Review the initial work done during co-op and compare to design drawings/flow charts

Power Board Driver

This is a nice-to-have if we have time (and I think we will).

BOOSTXL-BATPAKMKII datasheet

Includes the TI BQ27441-G1 Fuel Gauge on the i2c bus - this is where the driver work comes in. Datasheet

SOC is the big one, but there's some other interesting data we could pull off like temperature, current, and power.

Initial BMP280 Driver

BMP280 pressure sensor

Adafruit help page
Adafruit library

Initial BNO055 Driver

Write an example application using only FreeRTOS and the simplelink SDK (not the communications library) to talk to the BNO055 over (I2C or SPI? UART?) and report the data values over USB to a PC (Using TI's Display driver).

Broadcast communications

Debug and test broadcast communications between 2 MSP432 boards using the communications library.

• 1 Publisher, 1 Subscriber
• 1 Publisher, 2 Subscribers
• 2 Publishers, 2 Subscribers
• N Publishers, N Subscribers

Research launchpad booster pack format

Develop a working understanding of TI's booster pack headers and layout considerations therein.

Prototype some simple booster packs that have space for one sensor, power connections, and a board interconnect to hook up I2C connections for the communication library.

Identify Board Requirements

Checked items indicate things that have been decided.
Things to identify:

• What are the voltage domains in our system?
  • MSP432 boards are powered with 3v3. Do we need 5v? Any other voltage domains?
  • What is our battery voltage? Needs to be decided with the voltage regulators in mind.
  • Separate voltage domain for pyro FETs? Would prevent potential dropouts when pyros are fired.
  • Just 3v3. No 5v. Yes separate battery for pyro FET output.
• What will be on all the boards?
  • common connectors
    • 8 pin microfit connector
    • 2 of them, so that they can be daisy chained
    • 2 3v3 pins, 2 GND pins, SCL, SDA, RST, and TRIGGER/SYNC
      • TRIGGER/SYNC there for synchronization between boards - probably not actually implemented
• What will be on the power board?
  • 3v3 regulator
  • other regulators?
  • INA260 current/voltage/power monitor?
  • battery connector
  • COTS solution
• What will be on the attitude board?
  • BNO055
  • some sort of altimeter (I think we picked one, I just forgot)
    • BMP280
  • GPS?
• What will be on the pyro board?
  • 4x pyro MOSFETs
  • INA260 current/voltage/power monitor
  • Separate battery connector
  • screw terminal blocks for easy use
• What will be on the data board?
  • uSD card holder
  • Found a COTS solution

Pyro MOSFET Driver

Pretty simple driver.

Ability to turn on and off 4 GPIOs. Maybe when you turn one on, it times out after a certain number of seconds.

INA260 Driver

The INA260 is a current/power monitor IC. I put one on the pyro board so that we can monitor the current going to the pyrotechnics, because why not I guess. Needs a driver.