Zippy2 expansion Ethernet Port help
Julianne Kingery
I am very new to all of this, so any information you can give me is
greatly apprecaited!
I got Angstrom loaded on the BeagleBoard, and it is now recognizing
the Zippy2 extension board, but I cannot figure out how to set up the
ethernet port on the Zippy2.
Do I need to set a special boot argument? Or install a special driver
I need to install on the memorycard that I have inserted into the
BeagleBoard? Does the Zippy2 need to have a SD card inserted in it? Is
there some special path I have to take in Angstrom to set up the
connection?
If anyone can lead me in the right direction I would GREATLY
appreciate it!
Thank you!
Texas Instruments X-Loader 1.4.4ss (Apr 13 2010 - 22:36:28)
Beagle Rev C4
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2010.03 (Jun 25 2010 - 14:31:23)
OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max clock-720Mhz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Probing for expansion boards, if none are connected you'll see a
harmless I2C er
ror.
Recognized Tincantools Zippy expansion board (rev 1 )
Beagle Rev C4
Die ID #5abc00020000000004031eda1100c01c
Hit any key to stop autoboot: 0
mmc1 is available
reading uImage
3194800 bytes read
## Booting kernel from Legacy Image at 80300000 ...
Image Name: Angstrom/2.6.32/beagleboard
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3194736 Bytes = 3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Bill Purcell
Julianne Kingery
hmmmm.. did you have to set up any sort of connection through the
Angstrom GUI, or did it just recognize it right away?
here is what I got from 'ifconfig -a':
root@beagleboard:~# ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)
usb0 Link encap:Ethernet HWaddr A2:08:7F:39:1E:D2
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Thank you for your help!!!
>
> - Show quoted text -
Bill Purcell
> yours worked out of the box?
>
> hmmmm.. did you have to set up any sort of connection through the
> Angstrom GUI, or did it just recognize it right away?
from the serial connection or from the terminal if your in the GUI just type
ifconfig eth0 192.168.0.2
where eth0 is the network interface and 192.168.0.2 is the IP you want
the BB to have. I usually use my laptop as the router and set usb0 on
my laptop to 192.168.0.1 and my BB as 192.168.0.2. Then I have my
Zippy ethernet interface set up with an IP within my home network,
i.e. 192.168.1.112 in case I am somewhere in the house that has a
ethernet connection readily available.
> here is what I got from 'ifconfig -a':
>
> root@beagleboard:~# ifconfig -a
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:12 errors:0 dropped:0 overruns:0 frame:0
> TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)
>
> usb0 Link encap:Ethernet HWaddr A2:08:7F:39:1E:D2
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Looks like to me the Zippy ethernet interface is not seen. Are you
able to use the second MMC slot or maybe the second serial port? (to
verify other hardware on the Zippy is working)
BP
Julianne Kingery
On Jul 19, 11:39 am, Bill Purcell <will...@whpiv.net> wrote:
> On Mon, Jul 19, 2010 at 07:36:36AM -0700, Julianne Kingery wrote:
> > yours worked out of the box?
>
> > hmmmm.. did you have to set up any sort of connection through the
> > Angstrom GUI, or did it just recognize it right away?
>
> from the serial connection or from the terminal if your in the GUI just type
>
> ifconfig eth0 192.168.0.2
>
> where eth0 is the network interface and 192.168.0.2 is the IP you want
> the BB to have. I usually use my laptop as the router and set usb0 on
> my laptop to 192.168.0.1 and my BB as 192.168.0.2. Then I have my
> Zippy ethernet interface set up with an IP within my home network,
> i.e. 192.168.1.112 in case I am somewhere in the house that has a
> ethernet connection readily available.
>
>
>
root@beagleboard:~# ifconfig eth0 172.22.7.2
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
>
>
> > here is what I got from 'ifconfig -a':
>
> > root@beagleboard:~# ifconfig -a
> > lo Link encap:Local Loopback
> > inet addr:127.0.0.1 Mask:255.0.0.0
> > inet6 addr: ::1/128 Scope:Host
> > UP LOOPBACK RUNNING MTU:16436 Metric:1
> > RX packets:12 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)
>
> > usb0 Link encap:Ethernet HWaddr A2:08:7F:39:1E:D2
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> Looks like to me the Zippy ethernet interface is not seen. Are you
> able to use the second MMC slot or maybe the second serial port? (to
> verify other hardware on the Zippy is working)
moved the serial cable to the RS232 serial header on the Zippy2
extension board and booted. Everything ran smoothly, but nothing was
displayed in HyperTerminal to indicate that something had been
connected like it does when connected to the RS232 header on the
begleboard. Could this be a sign that the extension board may not be
functioning correctly? Could I have done something wrong when
soldering the two boards together?
>
> BP- Hide quoted text -
Bill Purcell
I will continue to try until someone who really knows what they're
doing chimes in.
On Mon, Jul 19, 2010 at 02:13:28PM -0700, Julianne Kingery wrote:
> here is what I got:
>
> root@beagleboard:~# ifconfig eth0 172.22.7.2
> SIOCSIFADDR: No such device
> eth0: unknown interface: No such device
This is definitely to be expected since the ethernet is not picked up
in ifconfig -a.
> I dont have a second SD card to check the second MMC slot with, but
> I moved the serial cable to the RS232 serial header on the Zippy2
> extension board and booted. Everything ran smoothly, but nothing
> was displayed in HyperTerminal to indicate that something had been
> connected like it does when connected to the RS232 header on the
> begleboard. Could this be a sign that the extension board may not be
> functioning correctly?
You won't see anything because the stdout and sterr are pointed to the
BB serial which is ttyS2. The zippy serial is ttyS1 (I think, atleast
that is what it is on Zippy I'm not sure about Zippy2.)
> Could I have done something wrong when soldering the two boards
> together?
I'm not really sure that we have enough evidence to deem your
soldering faulty. Are you using an external power supply other than
USB? I had some trouble powering my Zippy with just USB power. A
standard USB port doesn't have enough power.
BP
Einzig
check this out!
http://groups.google.com/group/beagleboard/browse_thread/thread/9e9487b63e31d834/6d982e15913977d3
My Zippy2 board had wrong identifiers stored in the serial EPROM.
Maybe that's your case, since U-boot recognizes Zippy but not Zippy 2.
Julianne Kingery
On Jul 19, 5:41 pm, Bill Purcell <will...@whpiv.net> wrote:
> I think this might be a little bit of the blind leading the blind but
> I will continue to try until someone who really knows what they're
> doing chimes in.
>
> On Mon, Jul 19, 2010 at 02:13:28PM -0700, Julianne Kingery wrote:
> > here is what I got:
>
> > root@beagleboard:~# ifconfig eth0 172.22.7.2
> > SIOCSIFADDR: No such device
> > eth0: unknown interface: No such device
>
> This is definitely to be expected since the ethernet is not picked up
> in ifconfig -a.
>
> > I dont have a second SD card to check the second MMC slot with, but
> > I moved the serial cable to the RS232 serial header on the Zippy2
> > extension board and booted. Everything ran smoothly, but nothing
> > was displayed in HyperTerminal to indicate that something had been
> > connected like it does when connected to the RS232 header on the
> > begleboard. Could this be a sign that the extension board may not be
> > functioning correctly?
>
> You won't see anything because the stdout and sterr are pointed to the
> BB serial which is ttyS2. The zippy serial is ttyS1 (I think, atleast
> that is what it is on Zippy I'm not sure about Zippy2.)
out the fuctionality of the board?
>
> > Could I have done something wrong when soldering the two boards
> > together?
>
> I'm not really sure that we have enough evidence to deem your
> soldering faulty. Are you using an external power supply other than
> USB? I had some trouble powering my Zippy with just USB power. A
> standard USB port doesn't have enough power.
USB hub. Does the Zippy2 need additional power than just that? Does it
need to use the battery slot to have enough power?
Thank you for your help!!
>
> BP
Bill Purcell
> Should I change the bootargs somehow to use the Zippy2 serial to test
> out the fuctionality of the board?
You could try that.
> I am using the 5V power jack on the BeagleBoard with a self-powered
> USB hub. Does the Zippy2 need additional power than just that?
It might be worth trying a 5V wall socket power source. Something
that can provide more power. I have a 2A source which is more than
what you need.
> Does it need to use the battery slot to have enough power?
The batter slot is just for maintaining the hardware clock.
Bill
Julianne Kingery
This was exactly the problem!
The internet is up and running on my board now!
On Jul 20, 5:04 am, Einzig <e1n...@gmail.com> wrote:
> check this out!
>
> http://groups.google.com/group/beagleboard/browse_thread/thread/9e948...
Julianne Kingery
is encountering the same issue.
I was using the latest Angstrom distro on a BB C4
I followed the guidelines from Einzig in the thread at
http://www.google.com/url?sa=D&q=http://groups.google.com/group/beagleboard/browse_thread/thread/9e9487b63e31d834/6d982e15913977d3&usg=AFQjCNFDOyR-pYpdA6g8RMQ3_G3-cbhI5w
-I used a jumper to shortcircuit JP1
-I used a USB stick to download and install to the board the i2c-tools
package from the Angstrom feeds at http://www.angstrom-distribution.org/repo/?pkgname=i2c-tools.
You could maybe try putting the package on the SD card to install, but
this messed up my SD card and threw me off track, so I reccomend using
a USB stick.
@Einzig, Thank you again for all of your help!