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.

Sign up for GitHub

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

Jump to bottom

I, too, see the FTB #3

Merged
merged 3 commits into from
Sep 4, 2023
Merged

I, too, see the FTB #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ccc36ac
Applied Formatting Changes During GitHub Build
Sep 2, 2023
b244e87
Merge branch 'main' into feature/mjmagee991/new-rampup
mjmagee991 Sep 4, 2023
c4d588a
Added Detail to Markdown Files
mjmagee991 Sep 4, 2023
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 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,8 @@ UART.
matches what is output over UART.

### Suggestions
- Read the [FTB documentation](
https://sites.google.com/g.rit.edu/evt-home-page/firmware-team/device-documentation/firmware-test-board-ftb).
- Read the [I2C documentation](
https://sites.google.com/g.rit.edu/evt-home-page/firmware-team/communication-protocols/inter-integrated-circuit-i2c?authuser=0).
- Read the datasheets.md section about the TMP117 datasheet.
Expand Down
20 changes: 13 additions & 7 deletions datasheets/datasheets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,18 +63,24 @@ Here, it has the address written as "00h", but it means the same thing as 0x00.
The prefix "0x" and the suffix "h" are both just used to indicate that the
number is hexadecimal instead of decimal.

### Register Details
After the table, there are a few sections that go into detail about each
register. You will need this information in some cases, but here, the register
just stores a two-byte integer that we want to read, so it's straightforward.
just stores a two-byte integer that we want to read, so it's fairly
straightforward. You will just need to be sure you use the multi-byte
`readReg()` method of the `I2C` class, not the single-byte read.

### Implementation
Based on this information from the datasheet, you're going to want an I2C call
that looks something like `i2c.readReg(0x48, 0x00, &outputBuffer);`. This will
attempt to read the data in register 0x00 from the device at address 0x48.
`outputBuffer` should be a two-byte buffer used to store the output, which you
can create with `uint8_t outputBuf[2];`. If everything goes well, it will then
put the data into the `outputBuffer`. If you're having issues with this, set up
the Saleae to check if the signals being sent match the values in this call.
that looks something like
`i2c.readReg(0x48, registerBuffer, 1, outputBuffer, 2);`. This will attempt to
read from the slave device at address 0x48 on the I2C bus. From this device, it
will read the data at the address stored in `registerBuffer`, which you should
set to 0x00. `outputBuffer` should be a two-byte buffer used to store the
output, which you can create with `uint8_t outputBuf[2];`. If everything goes
well, it will then put the data into the `outputBuffer`. If you're having issues
with this, set up the Saleae to check if the signals being sent match the values
in this call.

## MAX22530 Datasheet

Expand Down
Loading