#mikrobus — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mikrobus, aggregated by home.social.
-
Tiny Calixto Systems AM62L STAMP SOM targets industrial automation, HMI applications, EV chargers
-
Coralboard features Synaptics Astra SL2619 Edge AI SoC, supports Google Gemma 3 inference
-
Telink TL3228 – Low-power, low-latency dual-core RISC-V wireless MCU supports Bluetooth 6.0, 802.15.4, and 2.4 GHz proprietary
-
Telink TL3228 – Low-power, low-latency dual-core RISC-V wireless MCU supports Bluetooth 6.0, 802.15.4, and 2.4 GHz proprietary
-
Telink TL3228 – Low-power, low-latency dual-core RISC-V wireless MCU supports Bluetooth 6.0, 802.15.4, and 2.4 GHz proprietary
-
Telink TL3228 – Low-power, low-latency dual-core RISC-V wireless MCU supports Bluetooth 6.0, 802.15.4, and 2.4 GHz proprietary
-
Telink TL3228 – Low-power, low-latency dual-core RISC-V wireless MCU supports Bluetooth 6.0, 802.15.4, and 2.4 GHz proprietary
-
Renesas RA6W1/RA6W2 Cortex-M33 wireless MCUs offer dual-band Wi-Fi 6, BLE, Matter, 15-year availability
-
Renesas RA6W1/RA6W2 Cortex-M33 wireless MCUs offer dual-band Wi-Fi 6, BLE, Matter, 15-year availability
-
Renesas RA6W1/RA6W2 Cortex-M33 wireless MCUs offer dual-band Wi-Fi 6, BLE, Matter, 15-year availability
-
AMD Spartan UltraScale+ SU35P FPGA evaluation kit supports Raspberry Pi, Arduino, Mikrobus, and Pmod expansion
-
Nuvoton NuMicro M55M1 low-power Arm Cortex-M55 MCU enables on-device AI with Ethos-U55 NPU
-
Banana Pi BPI-R4 Lite #MediaTek #MT7987A Open Source #Router board public sale.
2GB RAM and 8G eMMC,2.5G #SFP + 2.5G RJ45 WAN (#PoE-ready),Wi-Fi 7 NIC & #5G via M.2 and miniPCIe,2x8 PIN #MikroBUS for expansion
https://www.banana-pi.org/en/product-news/579.html
#bananapi #raspberrypi #WiFi #WiFi7 #OpenWrt -
#Unboxing the #OpenWrtOne #Router with open #Software and open #Hardware and with the coolest #features at the moment!
The only instructions you receive are printed directly on the packaging. A great extension option is the #MikroBus: https://www.mikroe.com/mikrobus - It has both a #serial and an #I2C bus via which #IoT sensors can be connected.
There is also the option of connecting an #SSD, which I used immediately. I would also like to use the router as a #weather #monitoring station via appropriate sensors and then save the data on the SSD and have it evaluated and displayed via a #web #server.
The accessories supplied include a power supply unit, antennas, some screws and jumpers as well as a screwdriver. However, the screws on the case were so tight that I needed a better tool to open it.
I plan to provide my neighborhood with free #wifi via the router. I also want to run some web applications there and make them publicly accessible on the #Internet. So stay tuned and I will tell you here about the #configuration, #installation and results ...
#foss #floss #network #linux -
#Altstadtmobil #inklusiv #muenchen #mikrobus natürlich haben wir das gleich ausprobiert - sehr cool! Mutige Projektpartner, die einfach mal machen. So geht innovativer #Nahverkehr. Lustig: kostenlose Angebote irritieren Menschen.
@[email protected] war da was mit verödender Innenstadt?
https://muenchenunterwegs.de/angebote/altstadtmobil -
#Altstadtmobil #inklusiv #muenchen #mikrobus natürlich haben wir das gleich ausprobiert - sehr cool! Mutige Projektpartner, die einfach mal machen. So geht innovativer #Nahverkehr. Lustig: kostenlose Angebote irritieren Menschen.
@[email protected] war da was mit verödender Innenstadt?
https://muenchenunterwegs.de/angebote/altstadtmobil -
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!)