Hi Benoit,

Wow, that was quick! This is very encouraging.

Hopefully, before too long, we will have a robust stack and HTTP server.

Paul

The library now works using interrupts, so now frames received by the EMAC are processed as they arrive, no need for polling. (still a lot of checks on parameters to add, I'll keep that for later and concentrate on functionalities for the moment).

Benoît.

How is it going Benoit?

Wish I knew enough out C and programming Ethernet to contribute.

I'm pretty good at networking and a competent programmer but never had the need to go to that sort of detail.

Keep up the good work chaps

Just a quick note: EMAC_ReadPacketBuffer() & EMAC_WritePacketBuffer() aren't zero-copy (see their code). While lwip copy data twice, your implementation still has looping copy at both receive & send paths.

Alex,

You are right, in fact the "zero copy" I had in mind was for my own code.

The CMSIS driver definitely does a copy of data to/from user buffers from/to DMA memory regions where the EMAC hardware module works.

Benoît.

That's a CMSIS-based reference driver supplied by NXP, but while ARM's CMSIS is almost MISRA 2004 compliant, that crappy code is far from it. NXP brands them as "cmsis drivers" but that's not quite related because CMSIS won't go as far as to describe APIs to device drivers.

Anyway, as a reference, it's a good point as it's hard to find better examples out there. But there are quality problems, and you seem to have spotted at least one yourself.

<quote> Anyway, as a reference, it's a good point as it's hard to find better examples out there </quote>

Not for long ;)

Andy,

I see you coming here, but I really needed a working udp socket api for my application, hence mbedNet, which provides the basic functionalities I missed.

I can't wait to give a try to your code!

Alex:

Talking about MISRA, that's funny, because today I submitted a project at work to PolySpace and am currently conforming my source code to it. Next will be the dynamic code checking part (the most enjoyable!).

Regards,

Benoît.

Benoît

It's coming along. Just sorting things out for FreeRTOS compat (not that Mbed users can currently use FreeRTOS until the powers that be sort out a library port for it). But if you have offline compiler (GCC I am using) then we'll have a full implementation for LWIP + FreeRTOS and a "Classic solution" for non-FreeRTOS (i.e. Mbed users).

I believe Daniel is looking at the NetServices layers and also Adam Green is looking at beta tests.

Mid next month I start a new job which will limit my available time so my target is to get the first beta release out before then :)

It has been a while since any updates. Is anyone working on this currently?

I have had problems with the current lwip tcp stack which seem to be related to failed retransmit attempts. There has been some talk on lwip's news page about improvements in this area.

Josh

I'm connecting my mbed to a Server (it's actually a Modem) which responds to an HTTP GET with a short header, and a payload of 170 bytes.

I've used mbed NetServices and HTTPClient to read it.

A timer measures 440ms response time for this HTTP GET request - it's 40ms from a PC. In each case it's consistent in 1000-back-to-back reads.

Is that the performance we can expect? Is there anything I can do to tweak it for the small size of packet, or anything else??

I'm sure looking forward to alternative implementations of TCP/IP !

Has there been any activity on this lately? When does TCP get added?

Thanks.

Any news on Andy Kirkham's lwip work?

Hi,

On my side, I fell back on an alternate solution to have a full and robust TCP/IP stack (got an Embest SBC6020), due to lack of time to continue the development of mBedNet on mbed :-(

Benoît.

Simon mentioned elsewhere on the forum that an official mbed plan was taking shape to issue an improved "net services".

I imagine that Andy is overworked in his new job!

I addressed the slow performance of the HTTP client (as reported, above), by using the lwIP raw API.

http://lwip.wikia.com/wiki/Raw/TCP

This works perfectly well, with excellent reliability, and you can get 100 (small) packets per second out of it, when you issue the HTTP GET for the next request within the receive callback of the packet-in-hand.

My conclusion is that the Ethernet driver, and lwIP port on mbed are in good shape for speed and reliability, but the net services layer does not reach the same standard.

My vote would go to the suggestion from Miro in the first post: to finish the driver to permit Integration of lwIP and QP, so that we can develop for hard real-time solutions.

Non-critical applications can use Net Services as-is, and the raw API method can be used for high-reliability. But the real opportunity is for hard real time designs, where the performance of the LPC1769 can tear the pants out of other single-chip solutions.

Hi all,

has anybody a sample for TCP with the mbednet? UDP works but i need TCP for http (Server).

Thanks

did anyone tried to implement this http://www.keil.com/download/docs/295.asp into the Mbed? it's a simple stack but may be better working

I built a simple http server on top of the existing mbed lwIP port found in NetServices. You can see an example of its usage here.

I plan to do a little more work on it in the future but I found the current version to be pretty reliable at hosting static content from a SD Card. It does drop packets sometimes but only when hitting it hard from multiple clients and pulling down data at rates higher than 40Mb/sec. I am pretty sure that this limitation is in the polling based ethernet driver.

-Adam

thanks i will try that besides i saw somebody with a lib for the w5200..

W5200 as in WizNet's chip/module?

indeed, connect it to the mbed and get a stable networkclient.

WIZ810 also can be used with a little modification

i will try anyway adam's solution in a few days and see how's that working

I use the Wiz5100 chips in a large project... nice to have the TCP/IP et al stack off-loaded, not consuming CPU, etc. The ARM chips (and others) that have the 802.3 PHY on-chip inspire people to put the entire TCP stack on the CPU. As if it were a Pentium chip. Not a good idea in many cases.

tried the lwipopt.h of adam today, but doesnt work

indeed w810 or his big brother 5100 will work fine together with the mbed

I'm not trying to hijack this thread, but I assume some of you might be able to help me with ideas on how to debug a UDP problem described in another thread: "unable to receive large UDP packets"

Any help is appreciated as it's blocking me really much.

Hi All,

Since I am new to mbed, reading through many posts, I am completely getting lost. Can somebody please explain how things like 'ARM, CMSIS, MISRA, (Free)RTOS' etc are related. I know my way around C programming and am just getting familiar with the mbed libs. All this other stuff is clouding my vision and I really want to get on with my project, however in the most effective way. So any help is appreciated! Thanx in advance!

It is daunting, how the user contributions are or are not organized/index and versioned.

Google can tell you what those acronyms mean. Here's a one-liner on each:

ARM is of course the company that owns the intellectual property for ARM microprocessor families licensed to/produced by many semiconductor companies in huge quantities.

CMSIS is an ARM-sanctioned standard code library suite for cross-vendor interoperability of I/O devices, CPU initialization, etc. and it began with the Cortex ARMs, not the older ARM7 TDMI products.

MISRA is a standard for embedded systems C code robustness, for mission critical / safety applications. Some of the better compiler vendors have MISRA-specific libraries/compiler mode.

FreeRTOS is a popular real time operating system for most all popular microprocessors - when it's needed. Note that CMSIS has an RTOS abstraction layer in the API.

Only the more complex projects need the above.

hope that helps.

Hi all, we finally have officially supported mbed IP libraries:

• /handbook/InternetProtocol
• /handbook/Ethernet-Interface
• /handbook/VodafoneK3770-Interface

You have to enable the beta mode to see this library.

We are still working on the documentation, example applications and a user friendly C++ API.

Ideally, from now on, thanks to the new collaboration system, we will be able to accept "pull requests" from mbed users. This will allow us to have a centralized "official" library containing all the bug fixes and improvements contributed by the mbed community.

Cheers, Emilio

Hi Emilio,

The link to lwIP library leads to "Page not found", would you have a working link?

Best Regards,

Benoît.

To see the library you have to enable the beta: visit http://mbed.org/betamode/ and click 'Enable betamode'.

Cheers, Emilio

Oops...shame on me, I didn't read your message carefully!

Thanks :)