[beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hello, I have noticed very rare cases (~1/50) of the ethernet phy on the Beaglebone Black not being detected on boot, and requiring a hard reset (as opposed to calling 'reset' from the command line) to get it to work/be detected again. This problem has been mentioned in a couple of other threa

[beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I just purchased a Beaglebone Black Revision C and I appear to be having this problem. I can't even use the ethernet port but my wireless dongle works just fine. Has any progress been made to resolve this problem? I can use WiFi for now but I prefer to use ethernet. Thanks. John -- For more o

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I am just now looking at this issue. The A6 revision was not put in place to fix this issue. Gerald On Tue, Nov 26, 2013 at 4:22 PM, AndrewTaneGlen wrote: > Hello, > > I have noticed very rare cases (~1/50) of the ethernet phy on the > Beaglebone Black not being detected on boot, and requiring

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

We are experiencing the same issue, using the A5 version. Roughly 1% to 3% of the times on boot up, the unit fails to find the PHY. On next boot up works fine.On very very rare occasions, it will fail to find the PHY 2x in a row, but haven't seen that in a few days now since started driving SY

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Try removing C24. See if that helps. Gerald On Sat, Dec 7, 2013 at 7:01 AM, wrote: > We are experiencing the same issue, using the A5 version. Roughly 1% to 3% > of the times on boot up, the unit fails to find the PHY. On next boot up > works fine.On very very rare occasions, it will fail to

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi All, After removing C24 and C30 (next to the large unpopulated 20-pin header P2 on the bottom of the board) we ran 1000 power cycles and had a 100% success rate - i.e. board booted and phy detected every time. We used a programmable power supply and some scripts processing the uart output to

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I am runnung Debian 8.2 Linux beaglebone 4.1.12-ti-r29 I modified /etc/network/interfaces to make eth0 to be static, but every time after reboot, the IP still changed, why? Thanks, Kevin - # The primary network interface auto eth0 iface eth0

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Does the C24 value change in revision A6A suppose to fix this problem? I still got this issue on my two BBB A6A. Do we need to increase C24 further, or have it removed completely since U16 is added? On Saturday, December 7, 2013 11:50:06 AM UTC-8, Gerald wrote: > > Try removing C24. See if that

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

>From some earlier correspondence with Gerald @ BeagleBoard: "Rev A6 was not changed to fix this issue. It has a reset fix, but not for this. Whatever change I come up with will not show up for months. I don't know what the version will be. It is not clear how the Rev A6 revision will affect this

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi, Gerald: > > Try removing C24. See if that helps. > We saw the same problem. After removing C24 and C30 it seems to be solved! Our board is revision B. Robert -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Correct. You can also solve the issue by using the correct SW as well. The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Also, removing these caps will also create issues where the boar

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Gerald: > > Correct. You can also solve the issue by using the correct SW as well. The > issue is that the processors interferes with the default address settings > when the PHY reads the pins. If the SW looks for the other addresses, it > works fine. > > Also, removing these caps will also cr

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

My SW guy is currently out. There is a change that needs to be made. I will get with him next week to make sure the change gets done. Gerald On Tue, Mar 11, 2014 at 8:26 AM, Robert Kuhn wrote: > > > Gerald: > >> Correct. You can also solve the issue by using the correct SW as well. >> The issu

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Tue, Mar 11, 2014 at 8:26 AM, Robert Kuhn wrote: > > > Gerald: >> >> Correct. You can also solve the issue by using the correct SW as well. The >> issue is that the processors interferes with the default address settings >> when the PHY reads the pins. If the SW looks for the other addresses, i

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Gerald said: The issue is that the processors interferes with the default address settings when the PHY reads the pins. If the SW looks for the other addresses, it works fine. Could we get a clue about which "addresses" are the problem? Maybe the addresses 4a10 vs. 4a101000? davinci_mdio 4

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

The base address of the PHY. Only one address per PHY. I believe it is 0 to 7. It is my understanding that the fix was pushed up a week ago. Robert's image should handle this. It is not the MAC address. PHY NOT FOUND means that at the one address of 00 the PHY did not respond because the PHY has a

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Look in the LAN 8710A data sheet from SMSC. I would cut an paste it, but Microchip has cut and paste blocked. http://www.microchip.com/wwwproducts/Devices.aspx?product=LAN8710A Section 3.7.1 Gerald On Tue, Mar 11, 2014 at 2:52 PM, Gerald Coley wrote: > The base address of the PHY. Only one ad

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Got it! (Chrome print to PDF, copy from the print...) - 3.7.1 PHYAD[2:0]: PHY Address Configuration The PHYAD[2:0] configuration straps are driven high or low to give each PHY a unique address. This address is latched into an internal register at the end of a hardware reset (default = 000b)

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I know what I have seen. I know what I have replicated. And I know the SW fix takes care of it. I also know it does not happen on every board and doe snot happen every time. Do keep in mind that the board reset is not a HW reset. It is a SW reset. The fix is in the latest image from Robert. http

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

If anyone has any further information on the software fix/patch for this issue I would be very interested in hearing about it (and backporting into the kernel from late last year I am using) - or even the best way to search for patches to particular files. Regards, Andrew. On 12 March 2014 11:41,

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

fwiw, I'm seeing what *appears* to be this same issue on the latest board I've bought - occasionally there is no Ethernet connectivity on power-up, a physical power off/on always resolves it... This is a rev B board, running the latest Debian test image with beta 3.13 kernel, and has happened o

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Does anyone happen to know if the 3.8 kernel compiled as per these instructions here http://eewiki.net/display/linuxonarm/BeagleBone+Black also contains the fix? I have a root file system already that I want to use but would like to update my kernel to fix this problem. Thanks. On Tuesday, M

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Wed, Mar 19, 2014 at 2:47 PM, wrote: > Does anyone happen to know if the 3.8 kernel compiled as per these > instructions here http://eewiki.net/display/linuxonarm/BeagleBone+Black also > contains the fix? I have a root file system already that I want to use but > would like to update my kernel

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

FWIW I have seen the "PHY problem" repeatedly using the 3.8 kernel, but not yet with the RCN 3.13 kernel. Regards, Dave. On 03/19/2014 02:52 PM, Robert Nelson wrote: On Wed, Mar 19, 2014 at 2:47 PM, wrote: Does anyone happen to know if the 3.8 kernel compiled as per these instructions her

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I have seen this problem repeatedly by A6 revision hardware, but not with revision A5C hardware (I am running exactly the same software on both). Noteworthy is that the "PHY problem" only appears when powering the BBB via the headers. Powering via USB does not give any problems. I tried the fol

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Thu, Mar 20, 2014 at 4:48 AM, Kees k wrote: > I have seen this problem repeatedly by A6 revision hardware, but not with > revision A5C hardware (I am running exactly the same software on both). > > Noteworthy is that the "PHY problem" only appears when powering the BBB via > the headers. Poweri

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

After upgrading to the new kernel I setup a script to constantly soft reboot a revision B beaglebone black and have not seen the ethernet lockup once after some 800 consecutive reboots. With the old kernel I did see the ethernet lockup after soft reboots on the same board. I did however see th

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

All the SW has to do itvwrite to the registers and not rely on the straps. Hmm I have been saying that for 3+ years now. Gerald On Friday, November 21, 2014, wrote: > Hi Gerald, > > I meant "strap values", not connections on the board. As far as I > understand it, correct strappings alone canno

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

But the SW can do that only when the transceiver chip is always in a "writable" state, which is unfortunately not the case. On Saturday, November 22, 2014 1:38:54 AM UTC+1, Gerald wrote: > > All the SW has to do itvwrite to the registers and not rely on the straps. > Hmm I have been saying that

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

As suggested in this discussion i moved to 3.14.1 kernel and everything went well for the first 48 hours. After that i could see that the ETH stopped responding for close to 10 seconds. Then it came back. Test set up:- I'm using BBB for Data acquisition thru ETH. For testing i have connected

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

It appears that the issue is known for a long time: several registers of the LAN8710A Ethernet transceiver sometimes get wrong values at power-up, in spite of correct pin strapping configurations. One of those wrong values is PHYAD (PHY address in the Special Modes Register), which is erroneousl

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Well, may be you can add your mdio command inside u-boot source code's default bootcmd and rebuild the u-boot. In my case, I updated my cpsw platform data (I use 3.2 kernel, so no device tree) inside kernel dynamically to fix this problem. It seems to be working for me. Regards, Pratik On Mon

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I also believe the issue mentioned here : http://e2e.ti.com/support/arm/sitara_arm/f/791/t/366351.aspx is the same as we are facing in bbb. Regards, Pratik On Monday, 24 November 2014 21:12:50 UTC+5:30, alexschn...@gmail.com wrote: > > It appears that the issue is known for a long time: severa

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Ok, so this just happened to me. What I think ultimately caused it in my case is the OS hung on shutdown, so I had to hard-power-off the board with the power button. When it came back up, no network :/ Connected via the serial terminal and was seeing the same things as others had reported. I ha

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Pratik, Thank you very much for sharing you experience with this issue. Could you please provide more details on what and how you changed in cpsw platform data? Actually, rebuilding the kernel sounds a bit dangerous to me, because it may have some side effects, in my opinion. For instance, tha

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

to myersco...@gmail.com: Hi, I noticed that simply pushing RESET button actually helps sometimes, in my recent experiments. At the same time, pushing POWER button may not help sometimes. I have an impression that this issue is a bit different by different people. Have you tried resetting the

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi! I would assume that things would be fine without going into single-user mode. If it happens again, I can try as you suggested and post back :) On Saturday, November 29, 2014, wrote: > to myersco...@gmail.com > : > > Hi, > > I noticed that simply pushing RESET button actually helps sometimes

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Is there a finished flash-image available, which fixes the sw issues? (I wont solder on my board so there must be a sw only solution!) So i'm still wondering, why also the last revision has still sw on hw and sw, after so long time. Its very annoying having a nstable hw and so for this old pro

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, What I tried to say that the fix I applied had same logic which was described by "Jay @ Control Module Industries" in this discussion. Since I can not use device tree features of latest kernels, I made the changes which can fit in kernel 3.2 which is supplied by TI Android code. In my

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Pratik, As I studied the latest kernel code (3.8.13-bone67), I noticed that the patch mentioned by "Jay @ Control Module Industries" is already there, but apparently it doesn't help. After a lot of experiments with U-Boo

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, In past couple days, I went through the same path as you did. However, with my limited tests, I see improvement on 3.8.13-bone68. I have BBB Rev C from Element14 with a generic 5V 2.8A switch power supplier. - with 3.8.13-bone47 (the original image) power cycle 50 times, there were 2

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi KeOu, I guess with 3.8.13-bone67 I had "phy not found" as frequently as with the original image. On one board with 3.8.13-bone67, I had just one occurrence of "phy not found" in 50 power-on resets. On the other board with the same kernel I had 22 "phy not found" out of 50 power-on resets. Th

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Alex, I did more testing by using a remote power switch; using 3 BBBs with 3 different Kernel, no modification on U-Boot, Kernel. - 3.8.13-bone47 - that came with the board - 3.8.13-bone68 - upgrade via on board script /opt/scripts/tools/update_kerenl.sh - 3.14.22-ti-r31 - download from run-ee.

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

KeOu, Thank you for the data. It looks like "phy not found" does not happen very often with your boards. I also run that "update_kernel.sh" to update the kernel to 3.8.13-bone68. And I tried 3.14.22-ti-r31 too, and had a lot of "phy not found" in this case as well. In all my experiments the c

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

>From my experience: "Phy not found" doesn't mean that your network is not working ... I don't know what Robert Nelson is doing at boot, but it's possible that he fix this problem by using the register PRCM.PRM_RSTTIME= 0x ? Micka, Le Tue Dec 09 2014 at 21:40:11, a écrit : > KeOu, > > Tha

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Where I can find the variable CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC ? Did you try to increase it Robert Nelson ? Normally this should fix the problem with the phy not detected. If not, why ? Thx you, Le Wed Dec 10 2014 at 12:13:11, Micka a écrit : > From my experience: "Phy not found" d

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

I remember a thread in TI's forum stating that this issue can't be resolved by software. There is a hardware problem with the PHY which requires either a power cycle or a reset of PHY. And for BBB the reset line isn ot connected. To solve this issue via software a connection from one GPO to thi

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

OK, I found the thread I mentioned: http://e2e.ti.com/support/arm/sitara_arm/f/791/t/347189 Am Donnerstag, 11. Dezember 2014 12:34:10 UTC+1 schrieb Karl Karpfen: > > I remember a thread in TI's forum stating that this issue can't be > resolved by software. There is a hardware problem with the PH

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Alex, This is very interesting; in your case, the debug connection did not make any difference. Assuming there is a difference on the TTL connection, can you try (c), with patch between GPIO and debug port. In my case, with this patch, I do not see any ethernet failure. P9 1 (GND) to J1 (seria

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Alex, This is very interesting; in your case, the debug connection did not make any difference. Assuming there is a difference on the TTL connection, can you try (c), with patch between GPIO and debug port. In my case, with this patch, I do not see any ethernet failure. P9 1 (GND) to J1 (seria

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

KeOu, I made the connections you described and powered the board up, but still had that "phy not found", 7 times out of 10. Also, I did another interesting experiment: in U-Boot, I manually changed the PHY address of the transceiver to 2, after it had started successfully with the address 0 ("

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Micka, Yes, you're right, the network can still work after "Phy not found" was shown, although I observed this situation very rarely (I guess, only once), when I simply powered the board up. But this situation can be created artificially, if you intentionally change PHY address to a non-zero va

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Karl, Thank you for the link. So, according to that thread, we cannot start the board reliably without modifying the hardware. But what about doing something with nRESETIN_OUT pin? The datasheet says that the pin can be used to reset external devices, although it recommends using the pin as in

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, when I understand schematics of BBB correct, this input is hard-wired to the boards reset line only, so there is no chance to toggle that pin without a hard reboot of the whole board (means even a simple software reset of the CPU is not enough). Karl 2014-12-12 10:20 GMT+01:00 : > > Ka

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Karl, The topic starter there reported that a reboot via watchdog didn't work. But the AM335x reference manual says that the watchdog can generate a reset pulse, that "causes the PRCM module to generate global WARM reset of the device, which cau

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

2014-12-12 17:10 GMT+01:00 : > > The topic starter there reported that a reboot via watchdog didn't work. > I tried the same (from within a bare-metal application) and noticed the same. Once the PHY is in this state also a watchdog-triggered reset does not help, my software was trapped in an endle

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi, I have 10 boards (newest rev. C). When I use some older Ubuntu with Ubuntu and kernel Linux arm 3.13.6-bone7 eth0 is detected on one of the ten. When I use the pre-configured image with Debian and kernel Linux beaglebone 3.8.13-bone47 the eth0 is there all the time. Strange. Am Samstag,

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi, I assume this happens because those older kernels cannot cope with the situation when the transceiver just gets a non-zero PHY address at reset. This is solved in recent kernels by updating the device tree with actual P

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi, thanks for the answer. > So far, the only working solution seems to be removing C24 and C30 > capacitors, which is not good for a variety of reasons, as was mentioned > in some previous messages here. > So they are selling Beaglebones even most(?) of them fail and have ethernet problems

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Robert, I don't know. Someone marked this topic as complete, apparently because the problem with the wrong PHY address is solved by that patch. But I don't think it's complete, because there is another problem, which also manifests itself by "Phy not found", as I wrote above. Could you please

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

TI is not responsible for this problem. It's a problem of hardware design. Which is done by Gerald Coley if I'm not wrong. Micka, Le Tue Dec 16 2014 at 08:44:53, Robert Kuhn a écrit : > Hi, > > thanks for the answer. > > >> So far, the only working solution seems to be removing C24 and C30 >>

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Micka, I guess Michrochip is responsible for this problem, because their chip LAN8710A often doesn't start in a right way, in spite of correct strappings. But they don't admit that, according to the last message in this thread

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

But Texas Instrument replied by : This is a known issue. The problem is that the AM335X nRESET_INOUT (or warm reset) is released at approximately the moment that the PHY latches internally it's bootstrap resistors. Once in a while this happens too soon and the PHY doesn't come out of reset correc

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

> > Once in a while this happens too soon and the PHY doesn't come out of > reset correctly. > Then, without capacitors C24 and C30, things would get only worse, because nRESET_INOUT is released even earlier without those caps. On the contrary, removing caps helps. It looks like the slope of

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

http://e2e.ti.com/support/arm/sitara_arm/f/791/t/335017 i have same issue, sometimes jump phy id, sometimes no detection. on my custom board with 8710A. suspect interference with RESET pin. I have altered my design, everything is better now. correct: [ 1.206085] CAN bus driver for Bosch D_CAN co

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

This: 2014-12-16 10:09 GMT+01:00 Micka : > > > This is a known issue. The problem is that the AM335X nRESET_INOUT (or > warm reset) is released at approximately the moment that the PHY latches > internally it's bootstrap resistors. Once in a while this happens too soon > and the PHY doesn't come o

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

c2h2, Could you please tell us what change you did in your design to make it better? Regards Alex -- 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 s

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, We have also made many variation boards, including 2 PHY design, dual gigabit phy, etc. We massively produce our own core boards www.ariaboard.com, We found out on some early revision of our boards there may exist strange "PHY not found" and "PHY 0:0x" jumping issue, the audio (TLV320AIC

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

reboot multiple time and try to get the orange Led ! Le Mon Dec 22 2014 at 14:44:00, a écrit : > I just purchased a Beaglebone Black Revision C and I appear to be having > this problem. I can't even use the ethernet port but my wireless dongle > works just fine. Has any progress been made to res

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Try my solution a couple of posts up - basically, just hit the reset button on the board with the board booted and Ethernet plugged in. On Monday, December 22, 2014, Micka wrote: > reboot multiple time and try to get the orange Led ! > > Le Mon Dec 22 2014 at 14:44:00, > a écrit : > >> I just

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Thanks for the suggestions. I reflashed the eMMC today with a very recent version of Debian (12/19). This version appears to be reasonably stable. But after rebooting and trying your suggestion, Ethernet was still not available. I even tried booting without an Ethernet cable installed and then

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

As I continue to struggle with this problem and asking myself if I wasted my money on a product that is not working as advertised, I was wondering if it is possible to reset the ethernet interface on the board after the OS has booted, either via a script or some other means. Anyone try this at

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Based on all the comments and discussions I've seen before and after purchasing my BBB, I'm sure someone will figure out how to fix the issue. However, unfortunately my knowledge isn't that advanced yet, so while I can understand what folks are saying (usually,) I'm not at the level to be able to f

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hello everybody, After I and my colleagues had fruitlessly tried many things, our hardware developer came up with a working solution: delaying the PHY initialization performed by the U-Boot we use (v2014.10, git checksum c43fd23cf619856b0763a64a6a3bcf3663058c49). This ensured that U-Boot code

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Thursday, February 5, 2015 at 11:16:55 AM UTC-7, alexschn...@gmail.com wrote: > After I and my colleagues had fruitlessly tried many things, our hardware > developer came up with a working solution: delaying the PHY initialization > performed by the U-Boot we use (v2014.10, git checksum >

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

If this ends up being the solution, can you please post a guide for those not as up to speed as you on precisely how to implement this fix? Thanks On Thursday, February 5, 2015 at 1:16:55 PM UTC-5, alexschn...@gmail.com wrote: > > Hello everybody, > > After I and my colleagues had fruitlessly tr

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, I added this delay 1 second idea on the u-boot version v2015.01 and did the power on / off test on BBB. I did 263 board boot up. Among them 254 times Ethernet interface successfully started up. The other 9 times the u-boot just could not detect Phy. Below is the u-boot log comparison b

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Fri, Feb 13, 2015 at 11:58 AM, John Zhang wrote: > Hi Alex, > > I added this delay 1 second idea on the u-boot version v2015.01 and did the > power on / off test on BBB. I did 263 board boot up. Among them 254 times > Ethernet interface successfully started up. The other 9 times the u-boot > ju

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

If a changed ID is a problem, why does the network work after changing that ID manually in U-Boot and then rebooting, as I described here ? Alex On Friday, February 13, 2015 at 8:45:08 PM UTC+1, RobertCNelson wrote: > > On Fr

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi John, Thank you for doing this experiment. Did you power off your board right after checking for "Phy 0 not found" in U-Boot console, without booting Linux? Have you ever tried to let Linux boot after seeing that "Phy 0 not found"? Regards, Alex On Friday, February 13, 2015 at 6:58:46 PM

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Bill, Thank you for doing that experiment. I run two automated tests with the "delayed PHY initialization", each one with 130 power-ups over 130 minutes (one power-up per minute), where I still saw a few "Phy 0 not found" messages. In the first test, BBB periodically reset itself by means o

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Robert, Instead of trying to port the patch to u-boot, I updated my kernel from the BBB stock v3.8.13-bone47 to the latest v3.8.13-bone70. Then re-doing the power on/off test right now. Currently there are about 200 times power cycling and 8 times u-boot reported "Phy 0 not found". But for a

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, My test is to power on the BBB for 1 minute. Right after the kernel boots up BBB starts to ping another PC connected to the same Ethernet switch to show whether the Ethernet interface successfully started or not. My first software combination was "u-boot v2015.10 with the 1-second eth

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Sat, Feb 14, 2015 at 1:04 AM, John Zhang wrote: > Hi Robert, > > Instead of trying to port the patch to u-boot, I updated my kernel from the > BBB stock v3.8.13-bone47 to the latest v3.8.13-bone70. Then re-doing the > power on/off test right now. Currently there are about 200 times power > cycl

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi Alex, In my test, like John Zhang, I also had my BBB sending a ping after boot to confirm that Ethernet was working. In my experience the "Phy 0 not found" log message will occur even when the Ethernet seems to work normally. Regards, Bill -- For more options, visit http://beagleboard.org/

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

You can also fix most strapping options, including the PHY address, by writing to mdio register 0x12 (see datasheet page 60). This whole issue still sounds really weird though. The RXD3/PHYAD2 line has internal pull-down in the PHY, in

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Saturday, 25 April 2015 07:26:28 UTC+2, Matthijs van Duin wrote: > > The RXD3/PHYAD2 line > Sorry I meant RXCLK/PHYAD1 of course, though exactly the same is true for that line. > The inverted link led is *really* weird though: according to the phy > datasheet it corresponds to the REGOFF s

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Update. I have now witnessed the problem on RCS's 3.13.x kernels :( On Wednesday, March 19, 2014 3:31:00 PM UTC-5, David wrote: > > FWIW I have seen the "PHY problem" repeatedly using the 3.8 kernel, but > not yet with the RCN 3.13 kernel. > > > Regards, > > Dave. > > On 03/19/2014 02:52 PM,

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On 04/16/2014 08:46 AM, David wrote: Update. I have now witnessed the problem on RCS's 3.13.x kernels :( Update #2 FWIW when this occurs I cannot use the Ethernet interface even from uboot. It needs a hard reset to get out of this condition. Dave. On Wednesday, March 19, 2014 3:31:00 PM UTC

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Wednesday, March 19, 2014 8:52:36 PM UTC+1, RobertCNelson wrote: > > On Wed, Mar 19, 2014 at 2:47 PM, > > wrote: > > Does anyone happen to know if the 3.8 kernel compiled as per these > > instructions here http://eewiki.net/display/linuxonarm/BeagleBone+Black > also > > contains the fix? I

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Just found this thread, adding my 2cents. We are using kernel 3.8.13-bone30. We have seen many cases of ethernet issues, usually that the ethernet port does not come up at all (no lights). I would say it happens one out of every 20 boots. We are using a cape, but just to extend i/o and provide

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Wed, Jun 4, 2014 at 4:20 PM, Eric wrote: > Just found this thread, adding my 2cents. > > We are using kernel 3.8.13-bone30. We have seen many cases of ethernet > issues, usually that the ethernet port does not come up at all (no lights). > I would say it happens one out of every 20 boots. We ar

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi, I'm a newbie in a Beaglebone world, I have Beaglebone black rev. B, no capes, usb power. Yesterday I downloaded and flashed debian instead of angstrom Debian (BeagleBone Black - 2GB eMMC) 2014-05-14 an

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hello, This problem happens to me as well, I have 3 beaglebones black Rev C, with the latest kernel, 3.8.13-bone70. Anyone knows how to resolve this problem? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Tue, May 19, 2015 at 3:24 PM, Fernando Derkoski wrote: > Hello, > > This problem happens to me as well, I have 3 beaglebones black Rev C, with > the latest kernel, 3.8.13-bone70. Anyone knows how to resolve this problem? unlikely... show us the output off: dmesg | grep mdio sudo ifconfig -a

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

Hi, first thank you for the response, *here is the output where the network did not work:* root@beaglebone:~# dmesg | grep mdio [1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffb [1.047217] libphy: 4a10100

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski wrote: > Hi, first thank you for the response, here is the output where the network > did not work: > > root@beaglebone:~# dmesg | grep mdio > [1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 > [1.040439] davinci_mdio 4a101

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

But the network interface seems to be working fine. What nameserver is listed in /etc/resolv.conf under "nameserver" ? If it is different from your network, then you should probably change it to be accurate. Then try to ping local IPs again . . . On Tue, May 19, 2015 at 1:56 PM, Robert Nelson w

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

As an aside, is this in fact the problem, it would probably be listed as "nameserver 192.168.1.1" Which seems to be the default value as "shipped" On Tue, May 19, 2015 at 2:44 PM, William Hermans wrote: > But the network interface seems to be working fine. > > What nameserver is listed in /etc/r

Re: [beagleboard] Beaglebone Black Ethernet Phy Not Detected on Boot.

name servers have nothing to do with anything when pinging with IP numbers. On 5/19/2015 2:45 PM, William Hermans wrote: > As an aside, is this in fact the problem, it would probably be listed > as "nameserver 192.168.1.1" Which seems to be the default value as > "shipped" > > On Tue, May 19, 201

  1   2   >