Ethernet Shield from nuelectronics

Hello, I use this shield with arduino with success: http://www.nuelectro...1&products_id=4 May I use this shield with netduino ? My question is essentially regarding hardware, For the software, I have already see that lwIP have some enc28j60 driver, Many thanks for all, Pascal I'm currently waiting to receive my netduino, somewhere between Canada & France ....

Hello,

I use this shield with arduino with success:
http://www.nuelectro...1&products_id=4

May I use this shield with netduino ?

My question is essentially regarding hardware,
For the software, I have already see that lwIP have some enc28j60 driver,

Many thanks for all,
Pascal

I'm currently waiting to receive my netduino, somewhere between Canada & France ....

Yes, you can use it, but there are no drivers for it currently.

Yes, you can use it, but there are no drivers for it currently.

Thanks for your reply,

I have a experience on .NET Framework, .NET Compact Framework and on Arduino, but not on .NET Micro Framework,

What do you mean by no drivers ?

If I look at the Porting Kit, it's not possible to use this ? :
C:\MicroFrameworkPK_v4_1\DeviceCode\Drivers\Ethernet\enc28j60
Or this, if I plan to use lwIP ? :
C:\MicroFrameworkPK_v4_1\DeviceCode\Drivers\Ethernet\enc28j60_lwip

Pascal

What do you mean by no drivers ?

If I look at the Porting Kit, it's not possible to use this ? :
C:\MicroFrameworkPK_v4_1\DeviceCode\Drivers\Ethernet\enc28j60

Hi Pascal,

I think what Chris Seto was talking about was supported C# drivers (or drivers built into the Netduino firmware). Today (stressing the "today" part), there are no networking features compiled into the Netduino firmware...we're evaluating a few ways to support network connectivity on the Netduino and are welcoming community feedback as we build out support.

That said...If you have experience with native C++ code and writing drivers, Netduino is open source--so you have full control. You can build the enc28j60 drivers, integrate them into your own custom firmware, etc. And if you do, I know that many members of the community would love it if you shared your experiences.

If you're not comfortable going down that road, we will have at least one or two good networking options available in the near future. We will continue adding new capabilities (and new tutorials) for the Netduino. Thanks for joining us on the journey.

Chris

Hi Pascal,

I think what Chris Seto was talking about was supported C# drivers (or drivers built into the Netduino firmware). Today (stressing the "today" part), there are no networking features compiled into the Netduino firmware...we're evaluating a few ways to support network connectivity on the Netduino and are welcoming community feedback as we build out support.

That said...If you have experience with native C++ code and writing drivers, Netduino is open source--so you have full control. You can build the enc28j60 drivers, integrate them into your own custom firmware, etc. And if you do, I know that many members of the community would love it if you shared your experiences.

If you're not comfortable going down that road, we will have at least one or two good networking options available in the near future. We will continue adding new capabilities (and new tutorials) for the Netduino. Thanks for joining us on the journey.

Chris

Thanks Chris & Chris,

In case of success, I will share my experience,

Pascal

Hi Pascal,

I think what Chris Seto was talking about was supported C# drivers (or drivers built into the Netduino firmware). Today (stressing the "today" part), there are no networking features compiled into the Netduino firmware...we're evaluating a few ways to support network connectivity on the Netduino and are welcoming community feedback as we build out support.

That said...If you have experience with native C++ code and writing drivers, Netduino is open source--so you have full control. You can build the enc28j60 drivers, integrate them into your own custom firmware, etc. And if you do, I know that many members of the community would love it if you shared your experiences.

If you're not comfortable going down that road, we will have at least one or two good networking options available in the near future. We will continue adding new capabilities (and new tutorials) for the Netduino. Thanks for joining us on the journey.

Chris

The MAC control lines are not connected so far as I can see from the schematics. So you have a choice between the ENC28J60 or the Wiz5100.

I'd suggest going the Wiz5100 route and integrating the device at the PAL layer in the SOCK_* functions. This avoids the issue of bringing MSSTACK into the firmware. It's getting tight on the chip with only 512K flash.

The Audino ethernet shield uses the Wiz5100 for pretty much that reason. That, and a full TCP/IP stack implementation is not for the faint hearted on an embedded device!

Given the bloaty nature of GCC I would vote for keeping the stack out of the firmware.

Jeremy

The MAC control lines are not connected so far as I can see from the schematics. So you have a choice between the ENC28J60 or the Wiz5100.

I'd suggest going the Wiz5100 route and integrating the device at the PAL layer in the SOCK_* functions. This avoids the issue of bringing MSSTACK into the firmware. It's getting tight on the chip with only 512K flash.

The Audino ethernet shield uses the Wiz5100 for pretty much that reason. That, and a full TCP/IP stack implementation is not for the faint hearted on an embedded device!

Given the bloaty nature of GCC I would vote for keeping the stack out of the firmware.

Jeremy

I understand your point, but I'm working with IPv6 ... because I'm using multiple 802.15.4 sensors using 6lowPAN ...

Pascal

I'm pretty sure you are out of luck using IPV6. See http://msdn.microsof...y/ee433082.aspx There is no support for it out of the box in the micro framework. You can buy the EBSNet stack with IPV6 support in it.

You'd need to use an external networking device via a library to do IPv6. I believe that lwIP supports IPv6, so there's a chance we could enable a scenario natively in the future... Would be cool.

This seems to be the biggest problem with Netduino to me. There are currently many, many, many drivers for a plethora of devices out there written in C that can be easily #include'd into an Arduino project (or your own DIY AVR tool-chain). There are probably not many that you can just use in Netduino/C#. Maybe in a few years this will change?

Unless I'm missing something, I don't see what the problem is. For example I'm currently porting an Arduino library that interfaces with the DS1309 RTC by using an instance of Mcrosoft.SPOT.Hardware.I2CDevice to talk to it. Still waiting on my board to arrive ... but the problem is?

This seems to be the biggest problem with Netduino to me. There are currently many, many, many drivers for a plethora of devices out there written in C that can be easily #include'd into an Arduino project (or your own DIY AVR tool-chain). There are probably not many that you can just use in Netduino/C#. Maybe in a few years this will change?

Very true. Luckily, we've got some strong support built in and a very active community building samples and drivers.

All the basics (GPIO, SPI, I2C, UART, ADC, PWM) are baked into the firmware, so in most cases it will be a case of putting together a bit of C# code and making a "driver" for the peripherals using one of these standards. Between the drivers that we're working on at Secret Labs and the drivers that community members are building, we'll have a pretty good set built very, very soon (this year)...

We're also investigating ways to integrate native C++ code into Netduino C# projects. There are a lot of good reasons to write drivers in C#, but there are some places where this will make more sense. More on this as it develops.

What kinds of drivers/features are you looking for today? Maybe some of us can pitch in and help make it happen together... [As far as networking goes, we're on it.]

Chris

Me personally? No features I'm looking for. I have an old Atmel board tossing around somewhere I wrote some simple C code for a few years ago. This netduino looks interesting in that it's built on the .net foundation. I was reading elsewhere about the lack of 1-wire bus support on the netduino, though. This seemed to be due to the use of the .net framework and the inability for it to deliver strict timing delays. I guess you'd need to get the C++ integration you mentioned to get 1-wire support? Either way, the Netduino is an interesting idea - relatively cheap, and looks like it could pack many hours of fun due to the C# ease-of-use factor.

Either way, the Netduino is an interesting idea - relatively cheap, and looks like it could pack many hours of fun due to the C# ease-of-use factor.

Well, stick around and we'll welcome you as part of the community. I'm pretty confident you can find many hours of enjoyment in the Netduino. And as our talented community shares their projects and drivers (and as the Netduino adds native support for additional accessories), you'll have more and more to enjoy over time.

Thanks for your contributions in the forums,

Chris