This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Kindly suggest right KNX Transreceiver for Gateway Application (Home/Building Automation)  TI E2E support forums


We need to design the Gateway for Home/Building automation, all related requirement/feature information's are explained in the attached file, PFA FYI. You can ignore the any other modules if you feel not related to this topic, in such case, i can raise a new post for other modules.

TI having KNX Transreceiver?

Kindly check our requirement/application and suggest the right KNX Transreceiver and EVM board for the same.

  • Should work with Microprocessor (Microprocessor work environment listed below, FYI)
  • Should support KNX over IP
  • Should natively support KNX over Twisted Pair
  • Should have UART/RS485 for communicating with Processor.

Microprocessor will be interfacing with Ethernet, WiFi, Bluetooth, Zigbee, KNX tranreceiver. and Microprocessor should have the following feature:

  • Should work with Linux OS
  • Communicate with/over BLE/BLE Mesh devices, WiFi/WiFi Mesh devices, Zigbee devices.
  • Communicate with KNX devices include Sensors, actuators, supported devices
  • Communicate over Ethernet, should support BACnet IP.
  • MQTT Client libraries and AES libraries


  • Must support secure-boot with OTPROM based core root of trust
  • Build procedure to sign the bootloader OS and application binaries with a RSA private key.
  • Secure boot verification by establishing chain of trust from OTPROM till application layer.
  • OS should be Secure Linux.
  • Storing passwords, user names, keys in a secure storage

This is one of the most important Project, We need your support to built efficient product. kindly help us.

Thanks and regards,

Naveen K

Gateway Requirement.pdf

  • Hello Naveen,

    Here you can find a reference block diagram for a Building Security Gateway:

    This shows the different key blocks that you have mentioned above and their interconnections.  If you click one of the blocks (for example, "Wireless interface") the right side of the figure will be populated with device recommendations.  I think this will be a good starting point for selecting components for your design.

    This block diagram doesn't specifically address KNX.  TI does not produce PHY solutions for twisted-pair KNX but it is possible to use our microcontrollers to run the communications stack and pair them with an external transceiver.  This app note provides more details on that approach and gives a few reference solutions:

    I hope this is helpful to you!


  • Hi Max,

    Thank you for the information.

    1. Can we interface KNX transceiver directly to host MPU(AM437x) or dedicated MCU required?

    2. Stack will be integrated on host MPU or on dedicated MCU?

    3. TI will provide the Stacks or who can be provide the stack?

    4. Only stack will be available or its a package with Stack+MCU+KNX?

    5. How we can expect TI support on this KNX integration development? 

    Thanks and regards,

    Naveen K

  • Hi Naveen,

    We're trying to provide feedback as soon as we can.

    Thanks for your patience.



  • Hello Naveen,

    Note that the MSP430 solution Max pointed to above does not run in Linux.

    I do not see any KNX drivers or stacks provided by TI on AM335x or AM437x. However, these devices are running generic Linux. So if another company has developed KNX drivers / stacks for Linux, I would expect them to work on our devices. We will continue to ask around and update you if we hear anything else from our developers.



  • I'm not aware of TI offering a KNX twisted pair transceiver, we do have a wireless KNX RF tranceiver but I understood this use case to look for twisted pair KNX. The KNX transceiver would likely use UART to interface to a Sitara device like AM437x (as shown in the block diagram). Most likely the vendor of the transceiver also provides a Linux driver.