Daniel Peter

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

11 years, 4 months ago.

PicoTCP HelloWorld

Hi

I've imported the HelloWorld program (revision 14):

Import programTCPSocket_HelloWorld_PicoTCP

Fork of mbed official TCPSocket_Helloworld using PicoTCP

Last commit 03 Jul 2013 by Daniele Lacamera

The online compiler generates 68 warnings. When run on my network connected mbed, the result is as follows:

Lpc init : 10002828
DHCP callback : 0
IP assigned : 192.168.1.104
Default gateway assigned : 192.168.1.254
Unlocking
Returning
dhcp wake up!
IP Address is 192.168.1.254

There is no Hello World text and the router rather than device IP address is given.

I then update lpc1768-picotcp-eth to revision 6, mbed-rtos to revision 12, PicoTCP to revision 36, and mbed to revision 63.

The online compiler generates 73 warnings and 1 info.

 *** PicoTCP initialized ***
Lpc init : 10002908
 Full duplex mode ! -- @ 100 MBPS
DHCP callback : 0
IP assigned : 192.168.1.104
Default gateway assigned : 192.168.1.254
Unlocking
dhcp wake up!
IP Address is 192.168.1.104
Returning
Added socket (open)
Socket closed!

The IP address is now correct but there is still no Hello World text.

I've published the program with updated libraries:

Import programTCPSocket_HelloWorld_PicoTCP

lpc1768-picotcp-eth to revision 8, PicoTCP to revision 41 (mbed-rtos to revision 12, mbed to revision 63)

Last commit 16 Jul 2013 by Daniel Peter

Are my results reproducible?

Thanks
Daniel

Hi Daniel,

we are still busy implementing the last features of the Socket API properly. Currently, the problem with this test is that we have not yet integrated the required DNS call to resolve the server address within TCPSocket.connect() before actually connecting. Passing an IP address instead would be the way to make it work for now, but we are going to fix this immediately. We'll post an answer to this question when a new PicoTCP with the fix is released.

posted by TASS Belgium 30 Jun 2013

1 Answer

TASS Belgium
11 years, 4 months ago.

This should be now fixed, tested with PicoTCP r37 and lpc-picotcp-eth r7.

Thanks!