This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RM48L952: Implementing an Ethernet Stack without an OS

Part Number: RM48L952
Other Parts Discussed in Thread: HALCOGEN

We are working with the RM48x development board and are trying to Implement a TCP/IP Ethernet stack without using an OS.

We are using LwIP along with the HALCOGEN libraries.

http://www.nongnu.org/lwip/2_0_x/raw_api.html

So far, we have successful compiles, a successful ping test, and successful Ethernet transfers for receive and transmit.

However, we are struggling a good bit with the "Interrupt" Driven of the raw API.

Can anyone comment on this approach?

Has LwIP been successfully used as a "bare metal" TCP/IP stack on the RM48x?

Are there any alternatives to LwIP that don't require an OS?

Are these alternatives also "interrupt" driven like LwIP?

  • Hi Neil,

    Can you elaborate on the issues you are struggling with the interrupt driven version? Due to the bandwidth requirements of the LWIP code, I think that the interrupts are necessary to manage the response times and CPU loading.

    You might also want to have a look at the LWIP web site and support group to see if any generic solutions might be posted there or others may have similar issues they have needed resolved. The official website for the lwIP developer is savannah.nongnu.org/.../ and you will also find a support group there for lwIP specific issues.
  • Chuck,

    Thanks for the website link!

    Is LwIP commonly used for "bare metal" Ethernet programming on the RM48x or other Hercules MCUs?

    Thanks,

    Neil

  • Neil,

    I am not certain what you mean by "bare metal" Ethernet programming on the RM48x. Are you using lwIP as a programming interface in a boot loader?

    If this is the case, it isn't unheard of. There is actually a TI design that provides a reference design of an Ethernet based device programming implementation.

    Otherewise, I don't know how common it is to use the lwIP as a bare metal Ethernet driver. For certain, it isn't uncommon as most posts I am familiar with are referencing the lwIP as a non-OS implemented application.

  • Thanks Chuck!

    Thanks again for the link!

    You answered my question.

    We aren't using LwIP as a boot loader, but we are using it to support an Ethernet interface without using an Operating system.

    Our application is pretty simple. We want to use the RM48x as a safety certifiable SPI to Ethernet converter. The data coming into the SPI interface will get processed and sent out to the rest of the system via Ethernet.

    It looks like using LwIP is a reasonable approach to use based on your answer:

    "it [LwIP] isn't uncommon as most posts I am familiar with are referencing the lwIP as a non-OS implemented application."

    Currently, we are struggling with handling the Interrupts. But, it looks like we are heading down the correct path, overall.