Running bare-metal on the TWRVF65GS10 with DS-5, most of the MQX 4.0.2 examples are running fine, however for the RTCS eth_to_serial demo, it goes up to "Waiting for incoming connection..." and then just sits there. IP is configured manually on WIN7 and HyperTerminal returns: "Unable to connect to 192.168.1.202: port 23" and it's the same result with either A5 or M4.
When running httpsrv, I can ping to itself but not to the PC.
Also I followed the "General Technical MQX FAQ" guidelines.
Has anyone managed to get those demos to work on the VF6 without modifications ? with modifications ?
Many thanks in advance
Solved! Go to Solution.
Hi Pato,
I just ran the eth-to-serial demo on my Tower Vybrid kit with TWR-SER card.
I had setup my RTOS to use interrupt mode for the UART. For my Rev F board that is "ittyb". Your board revision might have a different UART as FYI.
I plugged into my home network that also uses 192.168.1. as the gateway/router. I pinged the 192.168.1.202 to make sure no other device was using it.
Then I ran the eth-to-serial demo and got the following:
Waiting for the incoming connection...OK
Then I pinged it from my laptop and got:
Sending ICMP ECHO REQUEST to module
Received ICMP ECHO REPLY
Then when I did the connect to the 192.168.1.202:23 the Terminal showed:
Serial <-> Ethernet bridge
And the TCP window showed:
Connecting to 192.168.1.202 ...
Connected to 192.168.1.202
Ethernet <-> Serial bridge
If I type something in one window it will show up on the other (unfortunately there was no echo back to the window I type from so that can be confusing).
If you still have issues you might refer to the following Doc Section 7 to make sure your jumpers are configured correctly:
C:\Freescale\Freescale_MQX_4_0_2\doc\FSL_MQX_getting_started.pdf
Regards,
David
Hi Pato,
I just ran the eth-to-serial demo on my Tower Vybrid kit with TWR-SER card.
I had setup my RTOS to use interrupt mode for the UART. For my Rev F board that is "ittyb". Your board revision might have a different UART as FYI.
I plugged into my home network that also uses 192.168.1. as the gateway/router. I pinged the 192.168.1.202 to make sure no other device was using it.
Then I ran the eth-to-serial demo and got the following:
Waiting for the incoming connection...OK
Then I pinged it from my laptop and got:
Sending ICMP ECHO REQUEST to module
Received ICMP ECHO REPLY
Then when I did the connect to the 192.168.1.202:23 the Terminal showed:
Serial <-> Ethernet bridge
And the TCP window showed:
Connecting to 192.168.1.202 ...
Connected to 192.168.1.202
Ethernet <-> Serial bridge
If I type something in one window it will show up on the other (unfortunately there was no echo back to the window I type from so that can be confusing).
If you still have issues you might refer to the following Doc Section 7 to make sure your jumpers are configured correctly:
C:\Freescale\Freescale_MQX_4_0_2\doc\FSL_MQX_getting_started.pdf
Regards,
David
Thanks so lot for your reply David, that's all I wanted to know. I don't think it's a big problem, but before starting to dig, I wanted to make sure someone got it working as is with DS-5.
Hi,
Is the IP address on your PC configured to static IP on the same subnet (e.g. 192.168.1.x )?
MacL
Hi MacL,
Yes it is.