Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »



Target release
Epic

ELEC-7 - Getting issue details... STATUS

Document statusDRAFT
Document owner

Kevin Chen (Unlicensed)

Designer
Developers
QA


Goals

  • Simplifies inventory management and software, allowing a single core config for all boards
  • Simplifies board debugging - isolates issues to either the controller or carrier boards

Background and strategic fit

One of the biggest issues with MSXI's electrical system was its inconsistency in parts and pinouts. There were at least 3 variations of the CAN controller/transceiver circuit and which SPI bus they were connected to, making debugging difficult. Some used different footprints, while others used different parts. This also made inventory a challenge, as each board had its own very specific set of components.

To increase board consistency and ease debugging, we propose a controller board that consists of shared core components such as the microcontroller, CAN transceiver, and possibly some debug LEDs or IOs. These controller boards would likely use a mezzanine connector to allow breakouts to carrier boards, which should be much simpler.

Requirements

#TitleUser StoryImportanceNotes
1

Include CAN, SPI, UART, SWD protocols

CAN, UART, SWD will have headers onboard

CAN lines will be routed through the board, reducing the use of T-junctions

2Debug/Heartbeat LEDsThese LEDs will provide useful debug info but the I/O can still be used for carrier board purposes

3Connector and wire standardization All connectors should lock securely and be physically distinct from each other (i.e. you shouldn't be able to plug one into another), wire color should also be standardized according to their associated signals.  
4Switching regulatorSwitching regulators are much more efficient than LDOs (90% vs 30%)

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

UART/USB? If we use USB, may need serial-to-usb converters on-board (In-car debugging)

UART only (Serial-to-USB converters are cheap)

Daisy chaining 12V power or not (LV power granularity)No daisy chaining
Hermaphroditic board-to-board connectors or notCurrently evaluating

Switching regulator circuit or integrated DC-DC converter (board complexity, cost)

Switching regulator circuit due to price and component height

LQFP vs UFQFPN

LQFP for ease of routing

How many pins do we dedicate to 3.3V, 12V, and GND on the mezzanine?

Currently evaluating

Selected Parts

Part
Info
Digikey Link
Price
STM32F072CBT6

ARM Cortex-M0

Includes CAN controller, 37 IOs, 48-LQFP

497-14645-ND

 $5.03

TCAN332DR

CAN Transceiver

Replacement for the SN65HVD232DR

296-43711-1-ND

 $2.67
Molex CLIK-Mate Connectors

1.25mm pitch for signal, 1.5mm pitch for power

Off-board connectors used for CAN, power, SWD, UART.



Mezzanine connectorUsed to connect the controller board to a carrier boardTBD
Switching regulatorConverts 12v → 3.3vTBD
LEDsFor debugTBD
Debug headers (same as off-board?)For SWD and UART/USBTBD


  • No labels