I would like to ask some questions about setting up a networking connect to the ekc-lm3s9b92 board.
this is not an elu specific question but i think its preventing elua from working correctly. i have dell 6400 laptop with a wireless card and a single ethernet connector in the back of the back of laptop. i have not to this date been able to establish a network connect to ekc-lm3s9b92 board buy connecting directly from the mcu to the laptop using the supplied spring loaded ether cable that came with the kit. i have also tried using a usb to ethernet adapter but that has not worked. i personally dont think the binary is at issue but some ethenet setting that is preventing connectivity. james _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
On Sat, Nov 19, 2011 at 11:39 AM, james osburn <[hidden email]> wrote:
> I would like to ask some questions about setting up a networking connect to > the ekc-lm3s9b92 board. > this is not an elu specific question but i think its preventing elua from > working correctly. > > i have dell 6400 laptop with a wireless card and a single ethernet connector > in the back of the back > of laptop. i have not to this date been able to establish a network connect > to ekc-lm3s9b92 board > buy connecting directly from the mcu to the laptop using the supplied spring > loaded ether cable > that came with the kit. i have also tried using a usb to ethernet adapter > but that has not worked. If you have a router handy that you can try plugging things into that will provide an IP address on a private subnet (i.e.: 10.x.x.x or 192.x.x.x)? This would be one way to double check any results since this should work in most cases as a solution. That said I'll provide at least a few comments here as far as possibilities are concerned: 1) If you're plugging the cable directly from the MCU to the laptop, make sure you're at least getting a negotiated link. I think that the MCU supports Auto-MDIX so the cross-over cable issue may be moot. You can use something like ethtool under Linux (as I recall you're under Fedora?) to check on the link status. 2) If there's a negotiated link, things get a little bit complicated in terms of Linux networking depending on what you want to do. The image I generated for you earlier will look for a DHCP server, which Linux won't be running by default for you. On Mac OS X or Windows the "internet connection sharing" features can be useful to configure a port so that a device that's plugged into it will see a DHCP server and then have any outgoing traffic NAT'd automatically. If your distro comes with some sort of similar feature that would allow you to share, say, an existing other wired connection or wireless connection with the MCU, it likely will work similarly to the feature on other platforms (run DHCP + NAT), otherwise it might be fairly involved to set this up. Something like this might work: http://www.techerator.com/2010/01/how-to-setup-internet-connection-sharing-in-fedora-12/ That said, I don't know how it will configure its routing tables or what IP it will hand out to the MCU. Using "arp -a" might be useful? An easier alternative if that doesn't work would be: Configure a static ip/subnet on the port being used so that they match up with a similar static configuration on the MCU (so a static IP image might be easier to work with). This should be fairly easy and is either doable through your distro's GUI tools for configuring network interfaces or on the command line. You can probably just match everything that the MCU has for IP information except the actual IP address which you would want to differ for the desktop. Note: eLua won't have access to the internet through this configuration. You can also bridge the connection that the MCU is attached to another connection that would provide it with DHCP and internet, but this is also not perfectly straight forward to explain how to do if one isn't comfortable with mucking around with one's networking configuration :-) > > i personally dont think the binary is at issue but some ethenet setting that > is preventing connectivity. > james > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > > eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
I have some success but not with elua though.
i purchased a small usb to ethernet adapter and configured the ip address on that adapter to be 192.168.0.1 with a net mask 255.255.255.0. once done i compiled one of the stellarsware lwip examples and then set in the software to 192.168.0.2. i was then able to connect to device and watched the network traffic on wireshark. traffic was indeed going back and forth between the laptop and lm3s9b92. this confirms that the device isnt broken. james On Sat, Nov 19, 2011 at 6:24 PM, James Snyder <[hidden email]> wrote:
_______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
On Sat, Nov 19, 2011 at 7:36 PM, james osburn <[hidden email]> wrote:
> I have some success but not with elua though. > i purchased a small usb to ethernet adapter and configured the ip > address on that adapter to be 192.168.0.1 with a net mask 255.255.255.0. > once done i compiled one of the stellarsware lwip examples and then set > in the software to 192.168.0.2. i was then able to connect to device and > watched > the network traffic on wireshark. traffic was indeed going back and > forth between the laptop and lm3s9b92. this confirms that the device > isnt broken. Good to know. I did load on the bin image I provided a link to before (on dropbox), which was configured to look for an IP via DHCP, and I can confirm that that image does work for me when tied to a router. I noticed earlier today that some recent adjustments done during a merge in the last week were probably preventing networking from working correctly on LM3S for some target types, and that should now be corrected. I'm not sure which version of eLua you might have been using either building from master, the image I posted before or something different, but I've build some fresh static images from the current master as of when this was sent (e6eca3cd). I've uploaded a 9B92 image to dropbox with a static IP of 192.168.0.20 here: http://dl.dropbox.com/u/169337/elua_9b92/static/elua_lua_lm3s9b92.bin http://dl.dropbox.com/u/169337/elua_9b92/static/platform_conf.h Best. -jsnyder > > james > > On Sat, Nov 19, 2011 at 6:24 PM, James Snyder <[hidden email]> > wrote: >> >> On Sat, Nov 19, 2011 at 11:39 AM, james osburn <[hidden email]> wrote: >> > I would like to ask some questions about setting up a networking connect >> > to >> > the ekc-lm3s9b92 board. >> > this is not an elu specific question but i think its preventing elua >> > from >> > working correctly. >> > >> > i have dell 6400 laptop with a wireless card and a single ethernet >> > connector >> > in the back of the back >> > of laptop. i have not to this date been able to establish a network >> > connect >> > to ekc-lm3s9b92 board >> > buy connecting directly from the mcu to the laptop using the supplied >> > spring >> > loaded ether cable >> > that came with the kit. i have also tried using a usb to ethernet >> > adapter >> > but that has not worked. >> >> If you have a router handy that you can try plugging things into that >> will provide an IP address on a private subnet (i.e.: 10.x.x.x or >> 192.x.x.x)? This would be one way to double check any results since >> this should work in most cases as a solution. >> >> That said I'll provide at least a few comments here as far as >> possibilities are concerned: >> 1) If you're plugging the cable directly from the MCU to the laptop, >> make sure you're at least getting a negotiated link. I think that the >> MCU supports Auto-MDIX so the cross-over cable issue may be moot. You >> can use something like ethtool under Linux (as I recall you're under >> Fedora?) to check on the link status. >> >> 2) If there's a negotiated link, things get a little bit complicated >> in terms of Linux networking depending on what you want to do. The >> image I generated for you earlier will look for a DHCP server, which >> Linux won't be running by default for you. On Mac OS X or Windows the >> "internet connection sharing" features can be useful to configure a >> port so that a device that's plugged into it will see a DHCP server >> and then have any outgoing traffic NAT'd automatically. If your distro >> comes with some sort of similar feature that would allow you to share, >> say, an existing other wired connection or wireless connection with >> the MCU, it likely will work similarly to the feature on other >> platforms (run DHCP + NAT), otherwise it might be fairly involved to >> set this up. Something like this might work: >> >> http://www.techerator.com/2010/01/how-to-setup-internet-connection-sharing-in-fedora-12/ >> >> That said, I don't know how it will configure its routing tables or >> what IP it will hand out to the MCU. >> >> Using "arp -a" might be useful? >> >> An easier alternative if that doesn't work would be: >> Configure a static ip/subnet on the port being used so that they match >> up with a similar static configuration on the MCU (so a static IP >> image might be easier to work with). This should be fairly easy and >> is either doable through your distro's GUI tools for configuring >> network interfaces or on the command line. You can probably just >> match everything that the MCU has for IP information except the actual >> IP address which you would want to differ for the desktop. >> Note: eLua won't have access to the internet through this configuration. >> >> You can also bridge the connection that the MCU is attached to another >> connection that would provide it with DHCP and internet, but this is >> also not perfectly straight forward to explain how to do if one isn't >> comfortable with mucking around with one's networking configuration >> :-) >> >> > >> > i personally dont think the binary is at issue but some ethenet setting >> > that >> > is preventing connectivity. >> > james >> > >> > _______________________________________________ >> > eLua-dev mailing list >> > [hidden email] >> > https://lists.berlios.de/mailman/listinfo/elua-dev >> > >> > >> _______________________________________________ >> eLua-dev mailing list >> [hidden email] >> https://lists.berlios.de/mailman/listinfo/elua-dev > > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > > eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
Free forum by Nabble | Edit this page |