SLAAEN9A September   2024  – August 2025

 

  1.   1
  2. 1 Description
  3. 2 Required Peripherals
  4. 3 Design Steps
  5. 4 Design Considerations
  6. 5 Software Flow Charts
  7. 6 Required UART Packet
  8. 7 Device Configuration
  9. 8 Application Code
  10. 9 Additional Resources
  11. 10E2E
  12. 11Revision History
  13. 12Trademarks

4 Design Considerations

  • Communication Speeds: Increasing speeds increases data throughput and decreases chances of collision. Adjusting the external pullup resistors according to I2C specifications is necessary to allow for communication if I2C speeds are increased. Optimizations include higher device operating speeds, multiple transfer buffers, header size reduction, or state machine simplification.
  • UART Header: The UART packer header and start byte are customizable for the application. Texas Instruments recommends assigning values that are less likely to occur during the start of typical data transfers.
  • Error Handling: Correspond the error values to ASCII numerical values if monitoring UART bus with a computer terminal. Make sure the host UART device can read error values and know the associated meanings so appropriate action can be taken by the host. Add additional error types by modifying the ErrorFlags structure type and add additional error detection code within the Uart_Bridge(). The current implementation detects limited errors and reports back the corresponding code on the UART interface. The application code then breaks from the current communication state machine. Users can add additional error handling code to change the behavior of the bridge when an error occurs. For example, re-sending an I2C packet after a NACK occurs.