possible workaround for BeagleBone Ethernet PHY problems
1,065 views
Skip to first unread message
Bjoern Krombholz
Jan 10, 2012, 8:25:53 AM1/10/12
to beagl...@googlegroups.com
Hi,
though I don't own a BeagleBone (yet) I noticed a lot of issues being
reported regarding non working or faulty Ethernet ports.
We are building a AM3503/17 based boards which AFAIK use the same
Ethernet block, we are also using the LAN8720A PHY which is nearly
identical to the LAN8710A used on the Bone.
I remember seeing similar problems with our device. Sometimes it just
worked, sometimes it didn't and often the link detection was just
extremely unreliable.
I can't guarantee that my solution will work for the bone problem, but I
think it's worth a try. The required change can be found at
<https://github.com/pironex/pia-linux-kernel/commit/bd65d378c5b152ea4bde127f9d3684b0c5c0737c>
(to get the patch, just add ".patch" to the URL.)
It simply disables the automatic "powerdown via link energy detection"
feature (which doesn't seem to work as expected) for the PHY.
Hope I could help
Bjï¿œrn
Andrew Bradford
Jan 10, 2012, 11:11:10 AM1/10/12
to Beagle Board
Interesting...
I've not personally seen this issue pop up on my Bones but I've not
yet played with them extensively with the Ethernet link going up and
down often. For applications where power consumption isn't critical,
your patch seems to achieve the goal.
Do you know if this is an SMSC PHY errata that should be published?
Or could layout of the PHY traces or magnetics selection have an
impact? I'm interested to learn more if you're willing to share more
of what you've found hardware wise.
Thanks,
Andrew
On Jan 10, 8:25 am, Bjoern Krombholz <pir...@gmail.com> wrote:
> Hi,
>
> though I don't own a BeagleBone (yet) I noticed a lot of issues being
> reported regarding non working or faulty Ethernet ports.
>
> We are building a AM3503/17 based boards which AFAIK use the same
> Ethernet block, we are also using the LAN8720A PHY which is nearly
> identical to the LAN8710A used on the Bone.
>
> I remember seeing similar problems with our device. Sometimes it just
> worked, sometimes it didn't and often the link detection was just
> extremely unreliable.
>
> I can't guarantee that my solution will work for the bone problem, but I
> think it's worth a try. The required change can be found at
> <https://github.com/pironex/pia-linux-kernel/commit/bd65d378c5b152ea4b...>
>
> --http://www.pironex.de
I've not personally seen this issue pop up on my Bones but I've not
yet played with them extensively with the Ethernet link going up and
down often. For applications where power consumption isn't critical,
your patch seems to achieve the goal.
Do you know if this is an SMSC PHY errata that should be published?
Or could layout of the PHY traces or magnetics selection have an
impact? I'm interested to learn more if you're willing to share more
of what you've found hardware wise.
Thanks,
Andrew
On Jan 10, 8:25 am, Bjoern Krombholz <pir...@gmail.com> wrote:
> Hi,
>
> though I don't own a BeagleBone (yet) I noticed a lot of issues being
> reported regarding non working or faulty Ethernet ports.
>
> We are building a AM3503/17 based boards which AFAIK use the same
> Ethernet block, we are also using the LAN8720A PHY which is nearly
> identical to the LAN8710A used on the Bone.
>
> I remember seeing similar problems with our device. Sometimes it just
> worked, sometimes it didn't and often the link detection was just
> extremely unreliable.
>
> I can't guarantee that my solution will work for the bone problem, but I
> think it's worth a try. The required change can be found at
> (to get the patch, just add ".patch" to the URL.)
>
> It simply disables the automatic "powerdown via link energy detection"
> feature (which doesn't seem to work as expected) for the PHY.
>
> Hope I could help
> Bj rn
>
> It simply disables the automatic "powerdown via link energy detection"
> feature (which doesn't seem to work as expected) for the PHY.
>
> Hope I could help
>
> --http://www.pironex.de
Jason Kridner
Jan 10, 2012, 5:27:22 PM1/10/12
to beagl...@googlegroups.com
Thanks for sharing! I've applied this patch to the BeagleBone kernel
[1]. It would be great to collect some data points from people seeing
this issue. I'm not currently reproducing it, but it could be my
network just has too much traffic. Can folks seeing this issue try
out my pre-built kernel [2] by copying uImage-beaglebone.bin as uImage
into the FAT partition?
[1] http://groups.google.com/group/beagleboard/browse_thread/thread/776a4ca8ca3c06e/09e25371b09eb2a4#09e25371b09eb2a4
[2] www.beagleboard.org/~share/beaglebone-debug-20120110/
>
>
> Hope I could help
> Björn
>
> --
> http://www.pironex.de
Björn Krombholz
Jan 11, 2012, 8:05:57 AM1/11/12
to beagl...@googlegroups.com
On 01/10/2012 05:11 PM, Andrew Bradford wrote:
> Interesting...
> I've not personally seen this issue pop up on my Bones but I've not
> yet played with them extensively with the Ethernet link going up and
> down often. For applications where power consumption isn't critical,
> your patch seems to achieve the goal.
>
> Do you know if this is an SMSC PHY errata that should be published?
> Interesting...
> I've not personally seen this issue pop up on my Bones but I've not
> yet played with them extensively with the Ethernet link going up and
> down often. For applications where power consumption isn't critical,
> your patch seems to achieve the goal.
>
> Do you know if this is an SMSC PHY errata that should be published?
I was not able to find one and stopped looking, because power
consumption was not essential for our project. On the other hand, I
remember not recognizing any measurable difference in overall system
consumption after applying the patch.
> Or could layout of the PHY traces or magnetics selection have an
> impact? I'm interested to learn more if you're willing to share more
> of what you've found hardware wise.
Unfortunately we couldn't find any hardware related issues outside the
PHY IC. I noticed the behaviour on 2 different board layouts with
different transmitters.
--
Bj�rn Krombholz
pironex GmbH -- http://www.pironex.de
Jorgen
Jan 11, 2012, 10:49:39 AM1/11/12
to Beagle Board
I have had problems with my ethernet port, as I have described on
another thread.
I have replaced uImage with your uImage-beaglebone.bin, and so far it
is working. But since it was an intermittent fault, it will take a few
days before I know for sure whether your patch makes a difference.
I'll leave the board running, and report back in a couple of days.
On Jan 10, 11:27 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:
> On Tue, Jan 10, 2012 at 8:25 AM, Bjoern Krombholz <pir...@gmail.com> wrote:
> > Hi,
>
> > though I don't own a BeagleBone (yet) I noticed a lot of issues being
> > reported regarding non working or faulty Ethernet ports.
>
> > We are building a AM3503/17 based boards which AFAIK use the same Ethernet
> > block, we are also using the LAN8720A PHY which is nearly identical to the
> > LAN8710A used on the Bone.
>
> > I remember seeing similar problems with our device. Sometimes it just
> > worked, sometimes it didn't and often the link detection was just extremely
> > unreliable.
>
> > I can't guarantee that my solution will work for the bone problem, but I
> > think it's worth a try. The required change can be found at
> > <https://github.com/pironex/pia-linux-kernel/commit/bd65d378c5b152ea4b...>
another thread.
I have replaced uImage with your uImage-beaglebone.bin, and so far it
is working. But since it was an intermittent fault, it will take a few
days before I know for sure whether your patch makes a difference.
I'll leave the board running, and report back in a couple of days.
On Jan 10, 11:27 pm, Jason Kridner <jkrid...@beagleboard.org> wrote:
> On Tue, Jan 10, 2012 at 8:25 AM, Bjoern Krombholz <pir...@gmail.com> wrote:
> > Hi,
>
> > though I don't own a BeagleBone (yet) I noticed a lot of issues being
> > reported regarding non working or faulty Ethernet ports.
>
> > We are building a AM3503/17 based boards which AFAIK use the same Ethernet
> > block, we are also using the LAN8720A PHY which is nearly identical to the
> > LAN8710A used on the Bone.
>
> > I remember seeing similar problems with our device. Sometimes it just
> > worked, sometimes it didn't and often the link detection was just extremely
> > unreliable.
>
> > I can't guarantee that my solution will work for the bone problem, but I
> > think it's worth a try. The required change can be found at
> > (to get the patch, just add ".patch" to the URL.)
>
> > It simply disables the automatic "powerdown via link energy detection"
> > feature (which doesn't seem to work as expected) for the PHY.
>
> Thanks for sharing! I've applied this patch to the BeagleBone kernel
> [1]. It would be great to collect some data points from people seeing
> this issue. I'm not currently reproducing it, but it could be my
> network just has too much traffic. Can folks seeing this issue try
> out my pre-built kernel [2] by copying uImage-beaglebone.bin as uImage
> into the FAT partition?
>
> [1]http://groups.google.com/group/beagleboard/browse_thread/thread/776a4...
>
> > It simply disables the automatic "powerdown via link energy detection"
> > feature (which doesn't seem to work as expected) for the PHY.
>
> Thanks for sharing! I've applied this patch to the BeagleBone kernel
> [1]. It would be great to collect some data points from people seeing
> this issue. I'm not currently reproducing it, but it could be my
> network just has too much traffic. Can folks seeing this issue try
> out my pre-built kernel [2] by copying uImage-beaglebone.bin as uImage
> into the FAT partition?
>
Jorgen
Jan 11, 2012, 11:06:57 AM1/11/12
to Beagle Board
Well that was fast, the PHY is once again not responding.
If I reboot the board (either soft or hard), I get a kernel message:
[ 21.001710] PHY 0:00 not found
See also:
http://groups.google.com/group/beagleboard/browse_thread/thread/a84133aef678f1c9/58847ee0f33b060b?lnk=gst&q=ethernet#58847ee0f33b060b
If I reboot the board (either soft or hard), I get a kernel message:
[ 21.001710] PHY 0:00 not found
See also:
http://groups.google.com/group/beagleboard/browse_thread/thread/a84133aef678f1c9/58847ee0f33b060b?lnk=gst&q=ethernet#58847ee0f33b060b
Gerald Coley
Jan 11, 2012, 11:11:43 AM1/11/12
to beagl...@googlegroups.com
I suggest you send it in under an RMA so we can look at it from an electrical point of view.
Gerald
--
You received this message because you are subscribed to the Google Groups "Beagle Board" group.
To post to this group, send email to beagl...@googlegroups.com.
To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beagleboard?hl=en.
Jorgen
Jan 11, 2012, 11:22:42 AM1/11/12
to Beagle Board
I'd rather not. I'm in Europe (Denmark), and I looked up the shipping
cost of returning the board. It is quite a bit more than I paid for
the board (incl. shipping) in the first place :-(
On Jan 11, 5:11 pm, Gerald Coley <ger...@beagleboard.org> wrote:
> I suggest you send it in under an RMA so we can look at it from an
> electrical point of view.
>
> Gerald
>
>
>
>
>
>
>
> On Wed, Jan 11, 2012 at 10:06 AM, Jorgen <jsabraham...@gmail.com> wrote:
> > Well that was fast, the PHY is once again not responding.
>
> > If I reboot the board (either soft or hard), I get a kernel message:
> > [ 21.001710] PHY 0:00 not found
> > See also:
>
> >http://groups.google.com/group/beagleboard/browse_thread/thread/a8413...
cost of returning the board. It is quite a bit more than I paid for
the board (incl. shipping) in the first place :-(
On Jan 11, 5:11 pm, Gerald Coley <ger...@beagleboard.org> wrote:
> I suggest you send it in under an RMA so we can look at it from an
> electrical point of view.
>
> Gerald
>
>
>
>
>
>
>
> On Wed, Jan 11, 2012 at 10:06 AM, Jorgen <jsabraham...@gmail.com> wrote:
> > Well that was fast, the PHY is once again not responding.
>
> > If I reboot the board (either soft or hard), I get a kernel message:
> > [ 21.001710] PHY 0:00 not found
> > See also:
>
Gerald Coley
Jan 11, 2012, 11:24:43 AM1/11/12
to beagl...@googlegroups.com
I suggest you do it. Just put in the RMA request and see what happens.
Gerald
Jorgen
Jan 11, 2012, 11:45:38 AM1/11/12
to Beagle Board
I have had the board in our lab, and tried to measure if there were
any obvious problems. The only thing I found was that nRST is at about
1.4V, so it looks like the reset signal is not being driven. The PHY
is also not sending link pulses, but doesn't necessarily need to be
because of the reset signal, the PHY coould be in powerdown mode. But
ss can be seen from the kernel message (PHY 0:00 not found) it is not
responding on the management interface, which definitely should not
happen unless the part is reset.
I'm going to try to solder a pullup on the reset signal, that should
help. But I won't have time until tomorrow. I'll let you know the
result.
any obvious problems. The only thing I found was that nRST is at about
1.4V, so it looks like the reset signal is not being driven. The PHY
is also not sending link pulses, but doesn't necessarily need to be
because of the reset signal, the PHY coould be in powerdown mode. But
ss can be seen from the kernel message (PHY 0:00 not found) it is not
responding on the management interface, which definitely should not
happen unless the part is reset.
I'm going to try to solder a pullup on the reset signal, that should
help. But I won't have time until tomorrow. I'll let you know the
result.
Jason Kridner
Jan 11, 2012, 12:12:24 PM1/11/12
to beagl...@googlegroups.com
On Wed, Jan 11, 2012 at 10:49 AM, Jorgen <jsabra...@gmail.com> wrote:
> I have had problems with my ethernet port, as I have described on
> another thread.
>
> I have replaced uImage with your uImage-beaglebone.bin, and so far it
> is working. But since it was an intermittent fault, it will take a few
> days before I know for sure whether your patch makes a difference.
> I'll leave the board running, and report back in a couple of days.
> I have had problems with my ethernet port, as I have described on
> another thread.
>
> I have replaced uImage with your uImage-beaglebone.bin, and so far it
> is working. But since it was an intermittent fault, it will take a few
> days before I know for sure whether your patch makes a difference.
> I'll leave the board running, and report back in a couple of days.
Thanks!
Octavio
Jan 11, 2012, 2:49:55 PM1/11/12
to Beagle Board
I left the BeagleBone on last night to try to reproduce the PHY
problem again (without the new patch). It took about 19 hours for it
to go down.
root@beaglebone:~# dmesg | tail
[ 7.154876] gadget: high speed config #1: Linux File-Backed
Storage
[ 17.944933] eth0: no IPv6 routers present
[ 6514.724823] gpio_request: gpio-56 (sysfs) status
-16
[ 6514.724848] export_store: status
-16
[ 6677.539971] gpio_request: gpio-38 (sysfs) status
-16
[ 6677.539996] export_store: status
-16
[ 6677.542518] gpio_request: gpio-56 (sysfs) status
-16
[ 6677.542539] export_store: status
-16
[70308.135033] PHY: 0:00 - Link is
Down
[70308.188652] ip_tables: (C) 2000-2006 Netfilter Core
Team
root@beaglebone:~#
uptime
19:21:24 up 19:43, 1 user, load average: 0.00, 0.01,
0.05
I have now uploaded the new patched kernel and I'll see what happens.
problem again (without the new patch). It took about 19 hours for it
to go down.
root@beaglebone:~# dmesg | tail
[ 7.154876] gadget: high speed config #1: Linux File-Backed
Storage
[ 17.944933] eth0: no IPv6 routers present
[ 6514.724823] gpio_request: gpio-56 (sysfs) status
-16
[ 6514.724848] export_store: status
-16
[ 6677.539971] gpio_request: gpio-38 (sysfs) status
-16
[ 6677.539996] export_store: status
-16
[ 6677.542518] gpio_request: gpio-56 (sysfs) status
-16
[ 6677.542539] export_store: status
-16
[70308.135033] PHY: 0:00 - Link is
Down
[70308.188652] ip_tables: (C) 2000-2006 Netfilter Core
Team
root@beaglebone:~#
uptime
19:21:24 up 19:43, 1 user, load average: 0.00, 0.01,
0.05
I have now uploaded the new patched kernel and I'll see what happens.
Alistair
Jan 11, 2012, 5:37:52 PM1/11/12
to Beagle Board
I suffer faulty Ethernet but only on the latest demo build or daily
build of the software, currently I'm running 2011.12.13, nothing newer
works.
build of the software, currently I'm running 2011.12.13, nothing newer
works.
Jorgen
Jan 12, 2012, 4:20:51 AM1/12/12
to Beagle Board
As I mentioned before, I found that on my board nRST to the PHY was
only 1.4V. According to the LAN8710A datasheet, Vih(min) is also 1.4V,
so it is not surprising that the PHY sometimes starts up, and
sometimes doesn't, since there is no noise margin at all.
It turns out that the reset signal is driven by an open-collector
buffer U16A, with a 10K pull to VDD_3V3A. I measured the VDD_3V3A
supply to be 3.3V. I replaced R23 with a 3.6K resistor, and now I
measure 2.5V for nRST. The board is currently running, and I am going
to leave it on for a couple of days to be sure that the ethernet does
not shut down again.
There must be an internal pull down on the reset pins on either the
LAN8710A or the AM3359 (perhaps both), nothing else is connected to
this net. There is no mention of an internal pull resistor in the
LAN8719A DC specs. I haven't checked the 3359 datasheet.
I would suggest that you check the nRST voltage on some more boards,
if they all have marginal values, you should change the value of R23
to something lower.
only 1.4V. According to the LAN8710A datasheet, Vih(min) is also 1.4V,
so it is not surprising that the PHY sometimes starts up, and
sometimes doesn't, since there is no noise margin at all.
It turns out that the reset signal is driven by an open-collector
buffer U16A, with a 10K pull to VDD_3V3A. I measured the VDD_3V3A
supply to be 3.3V. I replaced R23 with a 3.6K resistor, and now I
measure 2.5V for nRST. The board is currently running, and I am going
to leave it on for a couple of days to be sure that the ethernet does
not shut down again.
There must be an internal pull down on the reset pins on either the
LAN8710A or the AM3359 (perhaps both), nothing else is connected to
this net. There is no mention of an internal pull resistor in the
LAN8719A DC specs. I haven't checked the 3359 datasheet.
I would suggest that you check the nRST voltage on some more boards,
if they all have marginal values, you should change the value of R23
to something lower.
Jorgen
Jan 12, 2012, 6:11:15 AM1/12/12
to Beagle Board
My fix, where I replaced R23 (10K) with 3.6K only worked for a short
while. The initial reset voltage was ~2.5V, but after perhaps half an
hour it fallen to 1.6V, and the Ethernet port was once again not
working. I then replaced the pull-up resistor with 340R, and measured
3.1V for reset. This time I put a scope on the signal, and found that
the reset signal was toggling between ~3.1V and ~2.6V. I am pretty
sure that if I replaced R23 with 3.6K again, I would see the voltage
toggling between 3.3V and 1.6V (the average of these is pretty close
to the 2.5V I measured with a multimeter).
One explanation for this is that there may be a manufacturing defect
on the board, shorting the reset signal to another signal. Another
possibility is that the CPU is driving the reset signal from the
NRESET_INOUT pin, because it can't be the U16A buffer, which should
easily be able to drive the reset signal to ground, even with a 340
ohm pull to 3.3V.
I have sent full details, including a scope shot, to beagleboard RMA.
I will also be returning the board in a couple of days, so they can
take a look at it.
while. The initial reset voltage was ~2.5V, but after perhaps half an
hour it fallen to 1.6V, and the Ethernet port was once again not
working. I then replaced the pull-up resistor with 340R, and measured
3.1V for reset. This time I put a scope on the signal, and found that
the reset signal was toggling between ~3.1V and ~2.6V. I am pretty
sure that if I replaced R23 with 3.6K again, I would see the voltage
toggling between 3.3V and 1.6V (the average of these is pretty close
to the 2.5V I measured with a multimeter).
One explanation for this is that there may be a manufacturing defect
on the board, shorting the reset signal to another signal. Another
possibility is that the CPU is driving the reset signal from the
NRESET_INOUT pin, because it can't be the U16A buffer, which should
easily be able to drive the reset signal to ground, even with a 340
ohm pull to 3.3V.
I have sent full details, including a scope shot, to beagleboard RMA.
I will also be returning the board in a couple of days, so they can
take a look at it.
Gerald Coley
Jan 12, 2012, 9:20:09 AM1/12/12
to beagl...@googlegroups.com
Yes, there may be a manufacturing defect. That is why we want the board back. We have shipped 4500 boards so far, on only have a few that show this issue, and none of them are in our possession. We may have something that we are missing in our production testing. In order to fix it, we have to figure out what it is. And based on what it is we can figure out how to test for it and resolve the issue.
Gerald
Jorgen
Jan 13, 2012, 5:49:45 AM1/13/12
to Beagle Board
I shipped the board today. I expect the 'Beagle Hospital' ;-) will
receive it on Monday.
receive it on Monday.
Gerald Coley
Jan 13, 2012, 7:18:04 AM1/13/12
to beagl...@googlegroups.com
Thank you!
Gerald
Octavio Tapia
Jan 13, 2012, 9:34:32 PM1/13/12
to Beagle Board
For me, at least, the patch seems to have worked. I have been running
the patched kernel for 48+ hours on an idle BeagleBone and the
ethernet still works. This is the longest I have been able to run it
without the ethernet dropping.
Thanks,
Octavio
the patched kernel for 48+ hours on an idle BeagleBone and the
ethernet still works. This is the longest I have been able to run it
without the ethernet dropping.
Thanks,
Octavio
Octavio Tapia
Jan 14, 2012, 11:31:50 AM1/14/12
to Beagle Board
After a reboot this morning the ethernet stopped working again. I will
send it back also.
send it back also.
Grzegorz G
Dec 12, 2016, 4:57:20 PM12/12/16
to BeagleBoard
I wonder if the ethernet problems (link is down) has been resolved?
Robert Nelson
Dec 12, 2016, 5:03:09 PM12/12/16
to Beagle Board, grzeg...@gmail.com
On Mon, Dec 12, 2016 at 1:10 PM, Grzegorz G <grzeg...@gmail.com> wrote:
> I wonder if the ethernet problems (link is down) has been resolved?
>
We have a software workaround, depending on your kernel version (uname
> I wonder if the ethernet problems (link is down) has been resolved?
>
-r)... Otherwise if your designing your own hardware, make sure you
tie a gpio line the phy's reset line..
On the bbb design, the phy reset is tied to the processor reset...
Regards,
--
Robert Nelson
https://rcn-ee.com/
Gerald Coley
Dec 12, 2016, 5:08:23 PM12/12/16
to beagl...@googlegroups.com, grzeg...@gmail.com
GPIO line as a reset only works it you configure all the lines on the MII as inputs before you pulse the GPIO line..
Gerald
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYi%3Dsc%3Dp5U_02uUe8HJCX6urRj9h%2B9HN3tTM07bH1oA%3D%2Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Grzegorz G
Dec 13, 2016, 2:36:18 AM12/13/16
to BeagleBoard, grzeg...@gmail.com
I don't have my design hardware, I've bought many bbb boards and some of them with ethernet issues after many hours working without any problems link becomes down. Does the kernel with -bone60 or greater suffix is the SW workaround? Is the power management of the LAN chip couse the problem?
below log from kernel when problems occur:
Dec 6 14:22:17 beaglebone kernel: [709664.393005] libphy: 4a101000.mdio:00 - Link is Down
Dec 6 14:22:20 beaglebone kernel: [709666.620148] net eth0: initializing cpsw version 1.12 (0)
Dec 6 14:22:20 beaglebone kernel: [709666.622540] net eth0: phy 4a101000.mdio:00 not found on slave 0
Dec 6 14:22:20 beaglebone kernel: [709666.628940] libphy: PHY 4a101000.mdio:01 not found
Dec 6 14:22:20 beaglebone kernel: [709666.634052] net eth0: phy 4a101000.mdio:01 not found on slave 1
Dec 6 14:22:20 beaglebone kernel: [709666.644534] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
and when no problems - at boot time:
Jan 1 01:00:13 beaglebone kernel: [ 6.183325] net eth0: initializing cpsw version 1.12 (0)
Jan 1 01:00:13 beaglebone kernel: [ 6.187580] net eth0: phy found : id is : 0x7c0f1
Jan 1 01:00:13 beaglebone kernel: [ 6.187608] libphy: PHY 4a101000.mdio:01 not found
Jan 1 01:00:13 beaglebone kernel: [ 6.192679] net eth0: phy 4a101000.mdio:01 not found on slave 1
Jan 1 01:00:13 beaglebone kernel: [ 6.224917] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 1 01:00:13 beaglebone kernel: [ 6.580019] omap_rng 48310000.rng: base address of priv is -97452032
Jan 1 01:00:13 beaglebone kernel: [ 6.614128] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
Jan 1 01:00:13 beaglebone kernel: [ 10.333416] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 1 01:00:13 beaglebone kernel: [ 10.333488] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Today I'll check current kernel version of the board with ethernet issues.
Regards
Grzegorz
lorriane...@yahoo.com
Dec 13, 2016, 3:00:52 AM12/13/16
to beagl...@googlegroups.com
--------------------------------------------
On Tue, 12/13/16, Grzegorz G <grzeg...@gmail.com> wrote:
Subject: Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems
To: "BeagleBoard" <beagl...@googlegroups.com>
Cc: grzeg...@gmail.com
Date: Tuesday, December 13, 2016, 9:36 AM
I
don't have my design hardware, I've bought many bbb
boards and some of them with ethernet issues after many
hours working without any problems link becomes down. Does
the kernel with -bone60 or greater suffix is the SW
workaround? Is the power management of the LAN chip couse
the problem?
below log from
kernel when problems occur:Dec 6 14:22:17
beaglebone kernel: [709664.393005] libphy: 4a101000.mdio:00
[709666.620148] net eth0: initializing cpsw version 1.12
(0)Dec 6 14:22:20 beaglebone kernel:
[709666.622540] net eth0: phy 4a101000.mdio:00 not found on
slave 0Dec 6 14:22:20 beaglebone kernel:
[709666.628940] libphy: PHY 4a101000.mdio:01 not
foundDec 6 14:22:20 beaglebone kernel:
[709666.634052] net eth0: phy 4a101000.mdio:01 not found on
slave 1Dec 6 14:22:20 beaglebone kernel:
[709666.644534] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not
ready
and when
no problems - at boot time:Jan 1 01:00:13
beaglebone kernel: [ 6.183325] net eth0: initializing
cpsw version 1.12 (0)Jan 1 01:00:13 beaglebone
ready
and when
no problems - at boot time:Jan 1 01:00:13
beaglebone kernel: [ 6.183325] net eth0: initializing
kernel: [ 6.187580] net eth0: phy found : id is :
0x7c0f1Jan 1 01:00:13 beaglebone kernel: [
6.187608] libphy: PHY 4a101000.mdio:01 not
foundJan 1 01:00:13 beaglebone kernel: [
6.192679] net eth0: phy 4a101000.mdio:01 not found on
slave 1Jan 1 01:00:13 beaglebone kernel: [
6.224917] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not
readyJan 1 01:00:13 beaglebone kernel: [
6.580019] omap_rng 48310000.rng: base address of priv is
-97452032Jan 1 01:00:13 beaglebone kernel: [
6.614128] omap_rng 48310000.rng: OMAP Random Number
Generator ver. 20Jan 1 01:00:13 beaglebone
kernel: [ 10.333416] libphy: 4a101000.mdio:00 - Link is
Up - 100/FullJan 1 01:00:13 beaglebone kernel:
[ 10.333488] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link
becomes ready
Today
I'll check current kernel version of the board with
ethernet issues.
Regards
Grzegorz
W
dniu poniedziałek, 12 grudnia 2016 23:03:09 UTC+1
użytkownik RobertCNelson napisał:On Mon, Dec 12, 2016 at 1:10 PM,
Grzegorz G <grzeg...@gmail.com> wrote:
> I wonder if the ethernet problems
(link is down) has been resolved?
>
We have a software workaround, depending on
your kernel version (uname
-r)... Otherwise if your designing your own
hardware, make sure you
tie a gpio line the phy's reset line..
On the bbb design, the phy reset is tied to
the processor reset...
Regards,
--
Robert Nelson
https://rcn-ee.com/
becomes ready
Today
I'll check current kernel version of the board with
ethernet issues.
Regards
Grzegorz
W
dniu poniedziałek, 12 grudnia 2016 23:03:09 UTC+1
użytkownik RobertCNelson napisał:On Mon, Dec 12, 2016 at 1:10 PM,
Grzegorz G <grzeg...@gmail.com> wrote:
> I wonder if the ethernet problems
(link is down) has been resolved?
>
We have a software workaround, depending on
your kernel version (uname
-r)... Otherwise if your designing your own
hardware, make sure you
tie a gpio line the phy's reset line..
On the bbb design, the phy reset is tied to
the processor reset...
Regards,
--
Robert Nelson
https://rcn-ee.com/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to beagleboard...@googlegroups.com.
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9bb027f6-8bcd-4b19-8baf-cb238f3bb1bd%40googlegroups.com.
liati s-a intronat in lume principiile de drept si umanitate pentru toate neamurile si cand in urma
Grzegorz G
Dec 13, 2016, 3:54:27 AM12/13/16
to BeagleBoard, grzeg...@gmail.com
current kernel version: Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 armv7l GNU/Linux
so it's above bone60 and problem exsist
Micka
Dec 13, 2016, 4:24:43 AM12/13/16
to BeagleBoard, grzeg...@gmail.com
You should switch to kernel 4.4. Robert Nelson said that the ethernet is working better. I have a modified hardware so I can't tell.
Micka,
On Tue, Dec 13, 2016, 09:54 Grzegorz G <grzeg...@gmail.com> wrote:
current kernel version: Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 armv7l GNU/Linuxso it's above bone60 and problem exsist
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6caaca8f-b893-460b-80c8-2988fd690621%40googlegroups.com.
Grzegorz G
Dec 13, 2016, 2:22:53 PM12/13/16
to BeagleBoard, grzeg...@gmail.com
cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-kernel --lts-4_4
Generated error while upgrading:
E: Unable to locate package ti-sgx-es8-modules-4.4.38-bone14
E: Couldn't find any package by regex 'ti-sgx-es8-modules-4.4.38-bone14'
There is no ti-sgx-es8-modules-4.4.38-bone14 for kernel 4.4.38-bone14 ?
Regards
Grzegorz
Robert Nelson
Dec 13, 2016, 2:52:27 PM12/13/16
to Beagle Board, grzeg...@gmail.com
re-sync'ed out..
lorriane...@yahoo.com
Dec 13, 2016, 5:19:08 PM12/13/16
to beagl...@googlegroups.com
--------------------------------------------
On Tue, 12/13/16, Robert Nelson <robert...@gmail.com> wrote:
Subject: Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems
To: "Beagle Board" <beagl...@googlegroups.com>
Subject: Re: [beagleboard] Re: possible workaround for BeagleBone Ethernet PHY problems
Cc: grzeg...@gmail.com
Date: Tuesday, December 13, 2016, 9:51 PM
--
For more options, visit http://beagleboard.org/discuss
---
You received this message
because you are subscribed to the Google Groups
"BeagleBoard" group.
To
unsubscribe from this group and stop receiving emails from
it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjv%2BGeDcPgnCKA2WHc3cLTR%3DrV9Nb5HMW3AMr0oJgVChg%40mail.gmail.com.
For more options, visit http://beagleboard.org/discuss
---
You received this message
because you are subscribed to the Google Groups
"BeagleBoard" group.
To
unsubscribe from this group and stop receiving emails from
it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit
0 sept. - Semnarea Tratatului de pace de la Saint-Germain-en-Laye cu Austria. 19 nov. - Senatul S.U.A. respinge Tratatu1 de la Versailles si se opune constituiri Societatii Natiunilor. 27 nov. - Semnarea Tratatului de pace de la Neuilly-sur-Seine cu Bulgaria.
Reply all
Reply to author
Forward
0 new messages