README update, I2C addr update
All checks were successful
EIVE/eive-obsw/pipeline/pr-develop This commit looks good
All checks were successful
EIVE/eive-obsw/pipeline/pr-develop This commit looks good
This commit is contained in:
parent
ee6bb4df3b
commit
a855920fb2
16
README.md
16
README.md
@ -1108,11 +1108,19 @@ cat /proc/tty/driver
|
||||
|
||||
## I2C
|
||||
|
||||
Getting information about I2C device
|
||||
````
|
||||
Getting information about some I2C device
|
||||
|
||||
```sh
|
||||
ls /sys/class/i2c-dev/i2c-0/device/device/driver
|
||||
````
|
||||
This shows the memory mapping of /dev/i2c-0
|
||||
```
|
||||
This shows the memory mapping of `/dev/i2c-0`.
|
||||
|
||||
You can use the `i2cdetect` utility to scan for I2C devices.
|
||||
For example, to do this for bus 0 (`/dev/i2c-0`), you can use
|
||||
|
||||
```sh
|
||||
i2cdetect -r -y 0
|
||||
```
|
||||
|
||||
## CAN
|
||||
|
||||
|
@ -128,8 +128,8 @@ void ObjectFactory::createTmpComponents() {
|
||||
{objects::TMP1075_HANDLER_TCS_1, addresses::TMP1075_TCS_1},
|
||||
{objects::TMP1075_HANDLER_PLPCDU_0, addresses::TMP1075_PLPCDU_0},
|
||||
{objects::TMP1075_HANDLER_PLPCDU_1, addresses::TMP1075_PLPCDU_1},
|
||||
{objects::TMP1075_HANDLER_IF_BOARD, addresses::TMP1075_IF_BOARD},
|
||||
{objects::TMP1075_HANDLER_OBC_IF_BOARD, addresses::TMP1075_OBC_IF_BOARD},
|
||||
{objects::TMP1075_HANDLER_IF_BOARD, addresses::TMP1075_IF_BOARD_0},
|
||||
{objects::TMP1075_HANDLER_OBC_IF_BOARD, addresses::TMP1075_IF_BOARD_1},
|
||||
}};
|
||||
std::vector<I2cCookie*> tmpDevCookies;
|
||||
|
||||
|
@ -50,8 +50,8 @@ enum i2cAddresses : address_t {
|
||||
TMP1075_TCS_1 = 0x49,
|
||||
TMP1075_PLPCDU_0 = 0x4A,
|
||||
TMP1075_PLPCDU_1 = 0x4B,
|
||||
TMP1075_IF_BOARD = 0x4C,
|
||||
TMP1075_OBC_IF_BOARD = 0x4D
|
||||
TMP1075_IF_BOARD_0 = 0x4C,
|
||||
TMP1075_IF_BOARD_1 = 0x4D
|
||||
};
|
||||
|
||||
enum spiAddresses : address_t {
|
||||
|
Loading…
Reference in New Issue
Block a user