#greybus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #greybus, aggregated by home.social.
-
TIL about BeagleConnect™, which makes it possible for #mikroBUS based Click boards to be connected wirelessly (e.g. via #6LoWPAN over
802.15.4) to a #linux gateway.A virtual bus is created on the Linux gateway (e.g. /dev/i2c3) that sends "bridged PHY" #greybus messages to the remote #IoT node. The remote node runs #zephyr firmware on an MCU that speaks the Greybus protocols and translates those messages into I2C, SPI, GPIO, etc on the Click sensor (no drivers on MCU!)
-
TIL about BeagleConnect™, which makes it possible for #mikroBUS based Click boards to be connected wirelessly (e.g. via #6LoWPAN over
802.15.4) to a #linux gateway.A virtual bus is created on the Linux gateway (e.g. /dev/i2c3) that sends "bridged PHY" #greybus messages to the remote #IoT node. The remote node runs #zephyr firmware on an MCU that speaks the Greybus protocols and translates those messages into I2C, SPI, GPIO, etc on the Click sensor (no drivers on MCU!)
-
TIL about BeagleConnect™, which makes it possible for #mikroBUS based Click boards to be connected wirelessly (e.g. via #6LoWPAN over
802.15.4) to a #linux gateway.A virtual bus is created on the Linux gateway (e.g. /dev/i2c3) that sends "bridged PHY" #greybus messages to the remote #IoT node. The remote node runs #zephyr firmware on an MCU that speaks the Greybus protocols and translates those messages into I2C, SPI, GPIO, etc on the Click sensor (no drivers on MCU!)
-
TIL about BeagleConnect™, which makes it possible for #mikroBUS based Click boards to be connected wirelessly (e.g. via #6LoWPAN over
802.15.4) to a #linux gateway.A virtual bus is created on the Linux gateway (e.g. /dev/i2c3) that sends "bridged PHY" #greybus messages to the remote #IoT node. The remote node runs #zephyr firmware on an MCU that speaks the Greybus protocols and translates those messages into I2C, SPI, GPIO, etc on the Click sensor (no drivers on MCU!)
-
TIL about BeagleConnect™, which makes it possible for #mikroBUS based Click boards to be connected wirelessly (e.g. via #6LoWPAN over
802.15.4) to a #linux gateway.A virtual bus is created on the Linux gateway (e.g. /dev/i2c3) that sends "bridged PHY" #greybus messages to the remote #IoT node. The remote node runs #zephyr firmware on an MCU that speaks the Greybus protocols and translates those messages into I2C, SPI, GPIO, etc on the Click sensor (no drivers on MCU!)