Overview
Description
This is a debugging assistance tool for developing systems which use the TCP/IP. It supports the e² studio integrated development environment.
It is intended to reduce development effort of embedded systems incorporating the M3S-T4-Tiny software library for these communications protocols on RX family products which are suitable for TCP/IP.
Features
- The state of TCP communications can immediately be checked: [TCP Communication Path Info. (QE)] view
- The states of API errors occurring within the TCP/IP middleware can be checked: [TCP Communication Path Info. (QE)] view
- Learn More
Release Information
Target Devices
Downloads
|
|
|
|
|---|---|---|
| Type | Title | Date |
| Software & Tools - Other | [technical preview version] QE for TCP/IP V1.0.1
|
|
1 item
|
||
Documentation
|
|
|
|
|---|---|---|
| Type | Title | Date |
| Tool News - Notification |
PDF
265 KB
日本語
The TCP/IP protocol stack [M3S-T4-Tiny] is middleware for connecting RX MCUs and SH2A MCUs to the network. Support for this product ended on December 19, 2025. For alternative products, please refer to Tool News.
|
|
| Tool News - Note | PDF 153 KB 日本語 | |
| Application Note |
PDF
836 KB
日本語
AI-generated Summary:
The document details the mapping of socket APIs to T4 APIs for embedded TCP/IP communication within the RX Family. It lists functions such as opening, closing, sending, and receiving data through sockets, specifying corresponding T4 API calls. The module requires no hardware, depends on t4rx and t4driver_rx packages, and supports the Renesas RX Toolchain v2.05.00. Configuration options include setting UDP/TCP endpoints, buffer sizes, and work area sizes, with parameters defined in r_socket_rx_config.h for system customization.
|
|
| Manual - Development Tools | PDF 93 KB 日本語 | |
| Tool News - Release | PDF 100 KB 日本語 | |
5 items
|
||
Additional Details
Functions
The state of TCP communications can immediately be checked: [TCP Communication Path Info. (QE)] view
Since the state of a TCP connection between your system and another party in communications can be checked for each end-point, analyzing or breaking down problems in the form of communications not starting even when a connection has been made becomes easy.
![The state of TCP communications can immediately be checked: [TCP Communication Path Info. (QE)] view](https://www.renesas.com/sites/default/files/media/images/qe-for-tcp-ip-fig1.png)
The states of API errors occurring within the TCP/IP middleware can be checked: [TCP Communication Path Info. (QE)] view
When a problem in communications originates in TCP/IP, this product helps you to resolve it by quickly getting the answers to questions "Did the problem arise in the TCP/IP middleware?" and "When the problem arises, what kind of error is involved?"
Using QE for TCP/IP under the e² studio eases the debugging of TCP/IP systems, shortening development periods and lowering costs.
Supported Library
| Device | Middleware | Version |
|---|---|---|
| RX Family | Ultracompact TCP/IP protocol stack [high-speed version] : M3S-T4-Tiny | V2.02, V2.03, V2.05 |
Support
Support Communities
