Difference between revisions of "STM32 Scan I²C bus"
Jump to navigation
Jump to search
| Line 47: | Line 47: | ||
0x1e = 30 = 0b00011110 | 0x1e = 30 = 0b00011110 | ||
| + | |||
0b00011110 << 1 = 60 = 0x3c | 0b00011110 << 1 = 60 = 0x3c | ||
So the write addres is 0x3c while the read address is 0x3d. | So the write addres is 0x3c while the read address is 0x3d. | ||
Revision as of 04:59, 4 June 2021
Scanning an I2C bus using HAL is really simple. First configure I²C in Stm32CubeMX:
Once the I²C has been configured, scanning the bus for slaves become a simple matter:
// Go through all possible i2c addresses
for (uint8_t i = 0; i < 128; i++) {
if (HAL_I2C_IsDeviceReady(&hi2c1, (uint16_t)(i<<1), 3, 5) == HAL_OK) {
// We got an ack
printf("%2x ", i);
} else {
printf("-- ");
}
if (i > 0 && (i + 1) % 16 == 0) printf("\n");
}
printf("\n");
The HAL_I2C_IsDeviceReady will return HAL_OK if it receives an ACK or an error if not.
Output from above could be:
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 1e -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 53 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 77 -- -- -- -- -- -- -- --
Notice that I²C addresses are a bit peculiar.
The address itself is shifted 1 bit left and the last (LSB) bit indicates read or write. So - if looking at the above table:
0x1e = 30 = 0b00011110
0b00011110 << 1 = 60 = 0x3c
So the write addres is 0x3c while the read address is 0x3d.