User guide

Redpine Signals, Inc. Proprietary and Confidential. Page 157
R
R
S
S
9
9
1
1
1
1
0
0
-
-
N
N
-
-
1
1
1
1
-
-
2
2
2
2
/
/
2
2
4
4
/
/
2
2
8
8
S
S
o
o
f
f
t
t
w
w
a
a
r
r
e
e
P
P
r
r
o
o
g
g
r
r
a
a
m
m
m
m
i
i
n
n
g
g
R
R
e
e
f
f
e
e
r
r
e
e
n
n
c
c
e
e
M
M
a
a
n
n
u
u
a
a
l
l
V
V
e
e
r
r
s
s
i
i
o
o
n
n
4
4
.
.
1
1
5
5
Payload Buffer
uSocketDescriptor uBufferLength uDataOffset stFrom_Address
Receive Frame Body
Payload
Offset
2 Bytes
4 Bytes
2 Bytes
uDataOffset = 2 + 2 + 4 + 2 + 6 + Offset (Offset = 38(TCP) or 26(UDP))
6 Bytes
Figure 34:Receive Frame Body
Note: The extra 2 in the equation for uDataOffset in the diagram above is the two
bytes included in the payload. Refer to Data payload for data frames (from Host to
module).
4.10.6 HTTP GET Request
1
Description
This command is used to transmit an HTTP GET request to an HTTP server. The HTTP
GET Request can be issued only in a serial manner meaning only if HTTP response is
obtained for the current request, the next Request can be issued.
Relevance
This command is relevant when the TCP/IP stack is enabled.
Frame Body
The following is the structure for the HTTP GET Request:
struct TCP_HTTP_Req
{
UINT16 ipaddr_len;
UINT16 url_len;
UINT16 header_len;
UINT16 data_len;
UINT8 buffer[1200];
}__attribute__((packed));
Structure Member
Name
Description
1
Please check the Release Notes of the individual modules‟ software/firmware
releases to check whether this feature is supported.