Ethernet TCP Port problem

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Ethernet TCP Port problem

1,101 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Jeff Adams on Mon Feb 03 08:03:05 MST 2014
Hi All,

this is my first posting on this forum, so please forgive me if I've picked the wrong area.

I have an odd problem with Ethernet comms at the moment. I can give full details, but I thought I would explain in general terms first, just in case someone has seen this before and can answer immediately.

I have an LPC1768, running on the code red RDB1768V2R4 development board, with the uip_tcp library from Xpresso 6.1.0_164.

According to wireshark, if I attempt to open a socket from the LPC1768, nominating any port other than port 80, the destination port appears to be set more or less randomly.

It seems unlikely that there would be such a problem with the library, but at the moment I'm struggling to get any further.

I'll add my code on the next post, but for now, has anyone seen this issue before? If not, I can assume it's my code that's not right. But if it is a known problem, it will save me some effort!

Jeff
Labels (1)
0 Kudos
Reply
3 Replies

1,065 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by leluno on Mon Feb 10 08:05:11 MST 2014
i think uip is ok, if you are able to work with protothreads. I tried some hours without getting to the point of state, you have the feeling its doing exatlly the things you want.

I than tried an AVR-Webserver to change for ARM. You can look at the result under leluno.selfhost.eu . You can see the temperature in my office Temp0  and switch Led1 + 2. I would not be able to make such with uip. But if you can work with Protothreads yur sure can do this too.
0 Kudos
Reply

1,065 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by Jeff Adams on Mon Feb 10 03:03:45 MST 2014
Thanks for that Leluno.

Do you think that the uip stack is 'hard to understand' but otherwise OK, or should we just look elsewhere?

Jeff
0 Kudos
Reply

1,065 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by leluno on Sat Feb 08 06:35:09 MST 2014
i also have tried with lpx1768 and uip. uip is special code for small controller. There is no need to take uip for an lpc1768. uip worked on my board but it is very difficult to understand protothreads and make changes. There are better stacks then uip for ARMs.
0 Kudos
Reply