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

We have a few Industrial Beaglebone Black from Element 14. Rev C(PCB revision is B6). The Ethernet not coming up on every boot is faced in this version too. The OS used is QNX & hence the Software fix provided in Linux Kernel could not be used. Is there a solution? -Geetha On Wednesday, November

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

Which problem do you have? *IIRC* QNX may still use uboot or equivalent QNX can kill and restart a driver. Would require something to determine the Ethernet was not working and restart it. It seems like there are/were two problems: 1. Random RX characters on console/debug UART interrupting n

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

I notice from linked article that "QNX can kill and restart a driver. Would require something to determine the Ethernet was not working and restart it" is not going to work. However, you could replicate in QNX the Linux steps, assuming the source code is available for the Linux tools used. >Fr

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

Hi, I have read this thread as I'm currently having this problem happening to me on a BeagleBone Green. According to this thread, recent kernel versions should not have a problem as there is code that should be able to workaround the hardware problem. I am currently running: - U-Boot 2016.09-000

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

Any updates on this? I also have tried about a dozen brand new BeagleBone Greens with the latest Debian 8.7 2017-03-19 images and am still seeing the same problem - the Ethernet port occasionally does

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

So far we have 2 workarounds that seem effective... 1) Connect a GPIO pin to the SYS_RESETN pin (P9-10). Make sure the GPIO pin in set to be an input only with pull-up at boot time in the DT. After boot, have a script or service grep dmseg for the telltail `detected phy mask *fffb' *messag

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

FYI: The hardware fix described earlier in this thread give 100% success, first time, every time. On 27 April 2017 at 15:42, wrote: > If you have this problem and only care about solutions, jump to > "workarounds" below. > > ### RECAP > > For unlucky souls who come fresh upon this problem and do

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

This one: 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

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

If you have this problem and only care about solutions, jump to "workarounds" below. ### RECAP For unlucky souls who come fresh upon this problem and down want to read though a better part of a decade's worth of conflicting reports 1. Due to a design issue, the BeagleBone Black and descen

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

I opened a ticket with Microchip on this more then 6 months ago and just got the reply below. TLDR; "Since it took us so long to get to this issue, we assume you don’t care anymore that our silicon doesn’t work correctly”. Wow. -- AUTOMATED MESSAGE - SEE RESPONSE METHODS BELOW

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

Hi all, The problem seems to be influenced by the outside power supply. I run Debian Jessie with kernel 4.1.15-ti-rt-r43 on an 1month old element14 BBB (where do I find the revision??) and have the same issues. The BBB is getting its power from a custom carrier board which has a DC-DC on. Doing

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

Just a "me too" reply, echoing Ralf's comment. On my board, the Beaglebone is a "guest". The host board runs off +24 V, and provides two SMPS (5V and 3V3) to subsystems. The host 5V is hooked up to the BBB barrel jack pins on P9. The BBB's 3V3 supply is left unconnected, and the host board supp

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

I have encountered the same issue(s) on A6A boards. I couldn't find a patch, so I wrote this patch to update the device tree in the davinci_mdio driver in the 3.15.1 tree, it seems to correct it. I would welcome any input on a different approach. diff --git a/drivers/net/ethernet/ti/davinci_m

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

Guess this issue is solved, but this seems like the best place for my comment. I always see "davinci_mdio 4a101000.mdio: detected phy mask fffe", never "fffb", so that may be the critical part of your error. But I also always see - libphy: PHY 4a101000.mdio:01 not found net eth0:

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

Can I add in what I'm seeing on a A5C board. When the board boots either with or without an ethernet cable connected I don't get any lights on the ethernet socket. Whereas my older Beaglebone (white version) lights the orange ethernet LED almost immediately after power is applied. I can plug

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

Should C24 and C30 be removed from A5A BBBs that begin experencing strange Ethernet problems? I have two A5As that have both decided to keep their link lights on at all times (even without a cable). Also the Ethernet switch does not recognize either of the affected BBBs (tried several known goo

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

Robert Nelson wrote: > 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 poweri

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

The 5V is fine (maybe a little spike of 0.8V after 60 ms PS). However, the 3.3V gives a strange 2-stage powerup cycle. I compared a revision A5C to a revision A6, see plots below. As can be seen the A5C has a 'normal ' powerup cycle on the 3.3V, but the A6 a 2-stage powerup cycle. May this

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

Haha, I was looking at the wrong file (BB white A6). Sorry for the trouble; it seems our cape causes this difference between A5C and A6. On Tuesday, November 26, 2013 11:22:42 PM UTC+1, AndrewTaneGlen wrote: > > Hello, > > I have noticed very rare cases (~1/50) of the ethernet phy on the > Beagl

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

I have a BBB that sometimes fails to have a useable network interface at power up. Removing power and reapplying power does resolve the issue. Is there a fix for this issue? Would an upgrrade to Rev C fix this? > ... -- For more options, visit http://beagleboard.org/discuss --- You rec

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

> On a good phy boot I see the following: > [2.810749] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 > [2.817206] davinci_mdio 4a101000.mdio: detected phy mask fffe > [2.833517] libphy: 4a101000.mdio: probed > [2.837871] davinci_mdio 4a101000.mdio: phy[0]: device > 4a

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

Hi Jay, I've run into the same problem, so thank you much for your work. However it seems more natural to me to patch the cpsw driver to use the first MAC which is found rather than modifying the DT at runtime. Please see my suggestion (based on 3.12.30): diff -Naur linux.orig/arch/arm/boot/dt

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

Hi Josh, After the investigations made by our engineers. It was proven that nothing can be done as a software fix. The power management design of the beaglebone black/green would need a rework for this to be fixed. We ended up using another board that can cut the power to the BBG when the problem

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

On Tue, 5 Jun 2018 at 02:11, wrote: > I've come up with a software only workaround that can make sure a BBB will > always come up with a working Ethernet port - although it can take a few > minutes and require several automatic internal power cycles. > > You can read about it here... > > > https:

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

Anything connected to a BBB must not be powered up until the BBB is powered up so what you have done is correct On 6/14/2016 10:06 AM, tpkues...@gmail.com wrote: > Just a "me too" reply, echoing Ralf's comment. > > On my board, the Beaglebone is a "guest". The host board runs off +24 > V, and pro

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

Hi, I am using a BBB Rev C with latest Angstrom image and i have seen this issue with eth not getting detected at boot up. This came at the last stages of my project delivery. How can this be corrected. Does moving to the latest debian image solves this issue ? regards, Jerin George On Satu

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

As far as I know, and as already documented in this thread, the only reliable fix is to remove C24 and C30. On 4/11/2014 5:40 PM, "Jerin George" wrote: > Hi, > I am using a BBB Rev C with latest Angstrom image and i have seen this > issue with eth not getting detected at boot up. This came at th

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

From: Andrew Glen Reply-To: "beagleboard@googlegroups.com" Date: Monday, November 3, 2014 at 9:42 PM To: "beagleboard@googlegroups.com" Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot. > > As far as I know, and as already docu

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

early exhausted Murphy's law with our software. Andrew. On 4/11/2014 7:26 PM, "John Syn" wrote: > > From: Andrew Glen > Reply-To: "beagleboard@googlegroups.com" > Date: Monday, November 3, 2014 at 9:42 PM > To: "beagleboard@googlegroups.com" > Su

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

From: Andrew Glen Reply-To: "beagleboard@googlegroups.com" Date: Monday, November 3, 2014 at 11:36 PM To: "beagleboard@googlegroups.com" Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot. > > Yes, and reading the thread even

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

November 2014 01:23:28 UTC+5:30, john3909 wrote: > > > From: Andrew Glen > > Reply-To: "beagl...@googlegroups.com " < > beagl...@googlegroups.com > > Date: Monday, November 3, 2014 at 11:36 PM > To: "beagl...@googlegroups.com " > > Subject:

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

Hello, I am also experiencing the same issue here of etherenet not working on some boot-ups. I am using A6C board. My other problem is it is my requirement to use Android on beaglebone black only from internal storage i.e. eMMC. To support all necessary functionality of Android 4.2.2, I have to

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

m: Andrew Glen >> Reply-To: "beagl...@googlegroups.com" >> Date: Monday, November 3, 2014 at 11:36 PM >> To: "beagl...@googlegroups.com" >> Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy Not >> Detected on Boot. >> >> Y

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

x the issue for ever. >> I will keep you posted on the status. >> >> regards, >> Jerin >> >> On Wednesday, 5 November 2014 01:23:28 UTC+5:30, john3909 wrote: >>> >>> >>> From: Andrew Glen >>> Reply-To: "beagl...@google

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

hardware & also update the kernel to the latest version by >>> Robert. >>> Hopefully that will fix the issue for ever. >>> I will keep you posted on the status. >>> >>> regards, >>> Jerin >>> >>> On Wednesday, 5 November

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

Hello, I'm using BBB board A5C, and kernel version 3.15.3-bone3.1. I also see ethernet PHY is not detected. Log as below: Please refer detailed attached log. *[3.740457] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6* *[3.746859] davinci_mdio 4a101000.mdio: detected phy mask f

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

V3.15.3-bone3, I get the same problem you have. Regards, John From: Vishnu Patekar Reply-To: "beagleboard@googlegroups.com" Date: Saturday, July 5, 2014 at 11:01 AM To: "beagleboard@googlegroups.com" Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy

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

> V3.15.3-bone3, I get the same problem you have. > > Regards, > > John > > From: Vishnu Patekar > Reply-To: "beagleboard@googlegroups.com" > Date: Saturday, July 5, 2014 at 11:01 AM > To: "beagleboard@googlegroups.com" > Subject: Re: [beagleboard

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

e same problem you have. >> >> Regards, >> >> John >> >> From: Vishnu Patekar >> Reply-To: "beagleboard@googlegroups.com" >> Date: Saturday, July 5, 2014 at 11:01 AM >> To: "beagleboard@googlegroups.com" >> Subject:

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

nown* >>> >>> Next we are trying to find out why the network isn’t getting started. >>> Looks like something to do with cpsw. Using the same MLO, u-boot, uEnv.txt >>> and rootfs, V3.8.13-bone57 works just fine. Changing the kernel to >>> V3.15.3

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

gt;>> >>>> *3.758612] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, >>>> driver unknown* >>>> >>>> Next we are trying to find out why the network isn’t getting started. >>>> Looks like something to do with cpsw. Using the s

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

because you have >>>>> to mount the rootfs to load the kernel module. That will eliminate the >>>>> first issue: >>>>> >>>>> *3.758612] davinci_mdio 4a101000.mdio: phy[0]: device >>>>> 4a101000.mdio:00, driver unknown* >&

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

On Mon, Jul 7, 2014 at 2:52 AM, Micka wrote: > Hello, > > I'm on the Kernel 3.8.13-bone56 and I've still this problem : > > Scanning for Btrfs filesystems > systemd-fsck[202]: rootfs: clean, 110431/966656 files, 771069/3864576 blocks > [7.665617] libphy: PHY 4a101000.mdio:00 not found > [7

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

, 2014 at 11:01 AM > To: "beagleboard@googlegroups.com" > Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected > on Boot. > > Hello, > I'm using BBB board A5C, and kernel version 3.15.3-bone3.1. I also see > ethernet PHY is not detected. Log

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

From: Vishnu Patekar Reply-To: "beagleboard@googlegroups.com" Date: Monday, July 7, 2014 at 9:26 AM To: "beagleboard@googlegroups.com" Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot. > Hello John, > Thanks for info. > &g

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

From: Vishnu Patekar Reply-To: "beagleboard@googlegroups.com" Date: Monday, July 7, 2014 at 9:26 AM To: "beagleboard@googlegroups.com" Subject: Re: [beagleboard] Re: Beaglebone Black Ethernet Phy Not Detected on Boot. > Hello John, > Thanks for info. > &g

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

e3, I get the same problem you have. >>> >>> Regards, >>> >>> John >>> >>> From: Vishnu Patekar >>> Reply-To: "beagleboard@googlegroups.com" >>> Date: Saturday, July 5, 2014 at 11:01 AM >>> To: "beagleb

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

1000.mdio:00, >>>> driver unknown* >>>> >>>> Next we are trying to find out why the network isn’t getting started. >>>> Looks like something to do with cpsw. Using the same MLO, u-boot, uEnv.txt >>>> and rootfs, V3.8.13-bone57 works just fi

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

On Monday, July 7, 2014 5:17:12 PM UTC+2, RobertCNelson wrote: > > On Mon, Jul 7, 2014 at 2:52 AM, Micka > > wrote: > > Hello, > > > > I'm on the Kernel 3.8.13-bone56 and I've still this problem : > > > > Scanning for Btrfs filesystems > > systemd-fsck[202]: rootfs: clean, 110431/966656 fi

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

On Fri, Jul 18, 2014 at 5:42 AM, krd wrote: > > > On Monday, July 7, 2014 5:17:12 PM UTC+2, RobertCNelson wrote: >> >> On Mon, Jul 7, 2014 at 2:52 AM, Micka wrote: >> > Hello, >> > >> > I'm on the Kernel 3.8.13-bone56 and I've still this problem : >> > >> > Scanning for Btrfs filesystems >> > sys

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

On Friday, July 18, 2014 1:26:21 PM UTC+2, RobertCNelson wrote: > > On Fri, Jul 18, 2014 at 5:42 AM, krd > > wrote: > > > > > > On Monday, July 7, 2014 5:17:12 PM UTC+2, RobertCNelson wrote: > >> > >> On Mon, Jul 7, 2014 at 2:52 AM, Micka wrote: > >> > Hello, > >> > > >> > I'm on the Ker

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

When you see the repeating C's, I believe that is the ROM not finding u-boot. You have an issue with the mailbox drivers I use the following mailbox values for my kernel config CONFIG_MAILBOX=y # CONFIG_OMAP_MBOX is not set # CONFIG_OMAP2PLUS_MBOX is not set # CONFIG_OMAP_MBOX_KFIFO_SIZE

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

On Wednesday, July 23, 2014 3:54:00 PM UTC-7, cmid...@gmail.com wrote: > > The davinci mdio driver should report a phymask and that value is used to > update the device tree. > Back when I had this problem I tried hard to find out where the phymask comes from, and never succeeded. At that time p

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

They phymask comes from a hardware register read by the davinci_mdio driver, which gets passed to the linux phy libraries. The problem is that the cpsw driver gets the value from device tree, which is hardcoded to address 0. Usually the values are the same (address 0), but sometimes the phy ge

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

That is up to you if you want to rip parts off. I am not recommending it. Gerald On Fri, Feb 28, 2014 at 12:33 AM, wrote: > Should C24 and C30 be removed from A5A BBBs that begin experencing strange > Ethernet problems? > > I have two A5As that have both decided to keep their link lights on a

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

Where are you looking exactly? Gerald On Thu, Mar 20, 2014 at 8:51 AM, Kees k wrote: > > > The 5V is fine (maybe a little spike of 0.8V after 60 ms PS). > > However, the 3.3V gives a strange 2-stage powerup cycle. I compared a > revision A5C to a revision A6, see plots below. > > As can be se

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

I measure 3.3V on P9.3. USB powering shows the 'good' powercycle, 5V via P9.5 shows a 'bad' powercycle. Btw, I seen that in revision A6 and A4 there is an NCP349 chip between VDD_5V and pin 10 of the TPS65217b, which I cant see in revision A5. On Thursday, March 20, 2014 2:52:43 PM UTC+1, G

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

I did not use the NCP349 on the BBB. What board are you looking at? Gerald On Thu, Mar 20, 2014 at 8:58 AM, Kees k wrote: > I measure 3.3V on P9.3. > > USB powering shows the 'good' powercycle, 5V via P9.5 shows a 'bad' > powercycle. > > Btw, I seen that in revision A6 and A4 there is an NCP3

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

A cape. I hate capes. Maybe on the next revision I will just disable all of them! Thanks! Gerald On Thu, Mar 20, 2014 at 10:32 AM, Kees k wrote: > Haha, I was looking at the wrong file (BB white A6). Sorry for the > trouble; it seems our cape causes this difference between A5C and A6. > > On

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

I know our company appreciates the cape support, so thanks for supporting it :-) Been watching this thread anxiously for a while. So glad to see a fix was made, but we are using an Ubuntu 12.04 build for ARM (we really wanted to use Ubuntu to be consistent with our other field deployments). R

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

Not sure my original post got posted, so at risk of double-posting I'm going to post again (sorry). Gerald, my company loves the Cape support. Sorry, but thank you for supporting it! It has made what we're doing with the BeagleBone Black capable! Rob, regarding the OS patch - can you point u

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

No Capes! http://www.youtube.com/watch?v=Jy2YhxXn7NY On 3/20/2014 10:47 AM, Gerald Coley wrote: > A cape. I hate capes. Maybe on the next revision I will just disable all of > them! > > Thanks! > > Gerald > > > > On Thu, Mar 20, 2014 at 10:32 AM, Kees k wrote: > >> Haha, I was looking at t