Scope

As part of RDKM Broadband team we want to bringup IoT Barton on a platform of choice and make it available as reference for the community,The platform should be broader enough to support all IoT use cases so that depending on operator requirement he/she can test their specific use cases

Technical capabilities of Barton

  • Discovery
  • Pairing
  • Configuration
  • Firmware Management
  • Control
  • Eventing

Product requirements

  • Matter SDK
  • Zigbee 
  • OTBR
  • BlueZ/BLE
  • Wi-Fi
  • USB 

Platform requirements

  • Multiple USB Ports(More than 3 Minimum)
  • Wi-Fi support with atleast one radio (2.4Ghz)
  • In Built Bluetooth/BLE (or) USB BT support
  • In built Zigbee support (or) USB Zigbee support
  • In built Thread support (or)  USB Thread support

Protocols supported

  • Matter
  • Zigbee
  • Thread
  • OpenHome (Referred in one of the page,to be confirmed)

Available platforms in RDKM RDK-B platforms and One - One Mapping

  • Platform NameBluetooth/BLEZigbeeThreadWi-FiNumber of USB PortsReferences
    Banana Pi R4No Inbuilt BT & supported only through  USB / USB3.0 hubNo Inbuilt support (Supported through USB 3.0 hub)No Inbuilt supportSupported through USB 3.0 hub,Update got from Austin team)Yes1 (can be used for BT)

    BT Integration in BPI R4

    Raspberry Pi 4YesSupported through USBTBD through USBYes4



Banana Pi R4

  • Does USB 3.0 hub can be used to connect USB Bluetooth,USB Zigbee,USB Thread dongles

single USB dongle for Zigbee,Matter 

  •  Yes - Silab's xG24 Explorer Kit (brd2703a)

High level Expectation

  • Barton

Thread EFR32 integration reference in BPI R5

Bluetooth EFR32 integration in BPI R4

References

Child pages

Appendix



  • No labels

3 Comments

  1. Unknown User (daniel_finnegan@comcast.com)

    Reference to Thomas Lea's current notes (June 12, 2024) over at Comcast wiki → https://etwiki.sys.comcast.net/pages/viewpage.action?spaceKey=~tlea200&title=Zilker+IoT+Open+Source+2024

    Slides as presented on June 11, 2024 → 


  2. Daniel Finnegan

    Placeholder for potential demo use cases (prior to product/real-world use cases) after any public/community-wide communication of Barton's existence. 

  3. Daniel Finnegan

    Arch diagram above needs another concentric square around "Barton Internal Dashboard" to stand for executable application layer.

    That app layer is what interacts with BSP, USP, etc NOT barton directly as it's a set of libraries.

    Tagging Thomas Lea  for awareness