RNDIS Winsock communication error

Takeshi Yuasa

Hi,

My understanding of RNDIS driver on LCr supports TCP/IP protocol and the LCr is as a Slave (client), PC is as a Host (server).
Is my understanding correct?

Since we still have not succeeded in Winsock communication such as returning an error "WSAECONNRESET(10054)", I'd like to confirm.
Our situation is as below. Isn't this communication error caused by the USB driver unstable connection stuff, is it?

- Connection OK
- Retrun w/ OK on Send command. But no change.
- To set Current Display Mode to "Internal Test Pattern", align the byte as below and "Send".

Byte command[1024];
// Check Sum: total transmit bytes
commandData[0] = 0x06;
// Payload Data: transmit data　0x01:Internal Test Pattern
commandData[1] = 0x01;
// Payload Length: transmit data length
commandData[2] = 0x00;
commandData[3] = 0x01;
// Flag: command flag　0x00:complete data
commandData[4] = 0x00;
// CMD2: command ID　Current Display Mode (0x01 0x01)
commandData[5] = 0x01;
// CMD1: command ID　Current Display Mode (0x01 0x01)
commandData[6] = 0x01;
// Packet Type: packet type　0x02:Host Write Command Packet
commandData[7] = 0x02;

[Host PC]
Windoes7 64Bit Proffesinal

Regards,
Takeshi

over 13 years ago

0 Sanjeev over 13 years ago

TI__Mastermind 30875 points

Hi Takeshi,

Your understanding is correct about TCP client and server.

Before you are attempting with communication to hardware via Winsock i recommend you to try the following.

1. Let us know if you are able to communicate with the LCr h/w via GUI. Try basic things like changing the Display modes and Reading the version info.

2. Your way of populating the data is reversed. Actually commandData[0] should hold PacketType. Is there any reason why you are putting command data in reverse order?

Regards,

Sanjeev

0 Takeshi Yuasa over 13 years ago in reply to Sanjeev

Expert 1230 points

Hi Sanjeev,

Thanks for your quick response.

1) Yes. We're able to access any communication with your GUI.

2) Since it is a Little endian, I reversed the bytes.

Regards,
Takeshi

0 Sanjeev over 13 years ago in reply to Takeshi Yuasa

TI__Mastermind 30875 points

Hi Takeshi,

1. OK.

2. Little endian apply to 16 or 32 bit data not for byte streams. As you see you are populating the data byte by byte there is no question of endianess here. Refer to DLP® LightCrafter™ DM365 Command Interface Guide for example Video Input Setting (02 00) command has two byte parameters like Input Resolution X. So for little endian the two bytes should be populated such that the LSB is first and then next byte is MSB.

We have put the sample code link in this thread http://e2e.ti.com/support/dlp__mems_micro-electro-mechanical_systems/f/850/p/198385/719734.aspx#719734 just add your WinSock function in tcp_client.c file you can test the demo functions.

Let me know if you still face any problem.

Regards,

Sanjeev

DLP®︎ products

DLP products forum

RNDIS Winsock communication error