Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rachel28 hardware project 1 complete #38

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2,257 changes: 2,257 additions & 0 deletions hardwareproject1/Template_v0.0.kicad_pcb

Large diffs are not rendered by default.

491 changes: 491 additions & 0 deletions hardwareproject1/Template_v0.0.kicad_pro

Large diffs are not rendered by default.

625 changes: 625 additions & 0 deletions hardwareproject1/Template_v0.0.kicad_sch

Large diffs are not rendered by default.

266 changes: 266 additions & 0 deletions hardwareproject1/Title_Block.kicad_wks

Large diffs are not rendered by default.

135 changes: 135 additions & 0 deletions hardwareproject1/fp-lib-table

Large diffs are not rendered by default.

208 changes: 208 additions & 0 deletions hardwareproject1/sym-lib-table

Large diffs are not rendered by default.

66 changes: 66 additions & 0 deletions hardwareproject1/template_v0.0_specs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
> This template is a general guideline for ISC board specifications. Your board spec should be a high-level overview of what functions the board must have. This document should describe the features of a board, not how the board will be made. This should read like something a non-engineer could look at and understand what this board will do.

> A well-designed board specification should also contain enough information that a reasonably experienced board designer could read the project requirements and design the PCB from scratch. The implementation details should be left up to the person that will actually be designing and making the board.


# Board Name
**Board Requirements**


## Overview and Description
- What is the primary function of this board?
- What does this board replace?
- One or two more bullets (if necessary) talking about other things this board does
- Other board integration (List other boards and communication protocols)
- Board 1 (CAN)
- Board 2 (USB)
- Wiki page: [add link to page]

## High-Level Requirements
- Microcontroller (list microcontroller if the board has one)
- Hyperlinked microcontroller name
- MCU must be either LPC154X (USB-enabled) or LPC151X (no USB) unless there is a necessary reason to use something else
- List any specific configuration requirements
- How will this board be programmed?
- List any buttons or switches that control signals to or from the microcontroller
- List any features this board must have
- Describe each feature in a general way
- (Optional) Describe any requirements this feature might need as open-ended as possible

## Communication Protocols
- List each communication protocol used to send data to/from other systems or boards
- Does this board need external components to process data using this protocol?
- List any requirements needed to properly implement this protocol on the board
- Do not list communication protocols that will be used to connect different components within this PCB unless there is a reason to restrict the board design to a specific protocol

## Connectors
- List any general requirements for connectors here (e.g. no through-hole, low-profile, minimum 1A current capacity, etc.)
- Then list each connector, specific type/requirements, and pinout such as:
- Power In (KK 2.54)
- GND
- +12V
- GND

## ICs
- Only list specific ICs if the board require this specific component to work
- If you do list an IC here, use the following format:
- Component part number
- Datasheet (must be direct hyperlink to datasheet)
- One-line description of part
- Communication protocols used (if any)

## Buttons/Switches
- If the board needs buttons, describe what they do and how they will connect to the board

## Power System
- List each source that the board will need to function within the scope of this document
- Where does this voltage originate?
- List what protection this power supply needs
- List any other requirements for this rail
- List specific details in the wiki documentation

## Test Points
- Which signals should have test points?

## LED Indicators
- List any functions that should have an LED to indicate they are doing something. Include the 4 default debug LEDs for ISC boards
1 change: 1 addition & 0 deletions hardwareproject1/~Template_v0.0.kicad_pcb.lck
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{"hostname":"LAPTOP-RACHEL","username":"rache"}