Re: [beagleboard] ETH over USB on Debian
On Friday, May 23, 2014 3:35:38 PM UTC+2, RobertCNelson wrote: > > On Fri, May 23, 2014 at 7:44 AM, krd > > wrote: > > Hey, > > > > I'm trying for a while to set a network connection to my BBB over USB, > but > > still with no success. I have already tried a few different distros, > BBBs > > and HOWTOs - details bellow. I've even compiled my own kernels. It seems > my > > desktop computer is ready for such connection - I'm running there an > Ubuntu > > 3.13.0-24-generic - as when I'm connecting BBB running default Angstrom, > > everything works well automatically and both of my devices can see each > > other. Can you give me some hints and directions on how to enable this > > feature on Debian? Which config settings are important to this? What > modules > > have to be loaded? Do i need to make any more adjustments? > > > > I'm making my efforts on BBB rev B and A5C. System is running from SD > card. > > Versions of Debian already tried: 7.2-armhf-3.8.13-bone30, > > 7.4-2014-04-23-2gb and 7.5-2014-05-14-2gb and my recompiled version of > > 3.14.4 - its .config is in an attachment to this post. > > An usb0 interface is present and configured propperly(?)(addr: > 192.168.7.2/24 > > bcast 192.168.7.255) in all OS except the first one. > > Plugging an USB cable to BBB has no effect on my desktop - no new USB > > device, no sign in syslog. > > HOWTOs tried: > > > http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-usbgadget%28httpaccesstobeagleboneblackoverusb%29 > > > Well, if the "debian" image here: > http://beagleboard.org/latest-images > > Doesn't create a usb-eth link on your host system on bootup. There is > either a problem with the usb cable or your host system. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > None of these, as it turned out. The problem was in BBB itself. Probably some electrical flaw of miniUSB port. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Capes under 3.15 kernel
Hey, I'm testing a new kernel - 3.15.0-rc5-bone0.1 from RCN's github - for my BBB under Debian. What I've found out recently is lack of /sys/devices/bone_capemgr.* directory. Also my atempts to turn off hdmi via uEnv file fizzle out. Is it me doing something wrong or this is how it should be? Is there a way to get back my control over uarts, and ability to turn off hdmi under new kernel? Regards, Karol -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] control over uarts and capes under kernel v. 3.15
Hey, I'm testing a new kernel - 3.15.0-rc5-bone0.1 from RCN's github - for my BBB under Debian. What I've found out recently is lack of /sys/devices/bone_capemgr.* directory. Also my atempts to turn off hdmi via uEnv file fizzle out. Is it me doing something wrong or this is how it should be? Is there a way to get back my control over uarts, and ability to turn off hdmi under new kernel? Regards, Karol -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] control over uarts and capes under kernel v. 3.15
On Wednesday, June 4, 2014 4:50:44 PM UTC+2, RobertCNelson wrote: > > On Wed, Jun 4, 2014 at 9:29 AM, krd > > wrote: > > Hey, > > > > I'm testing a new kernel - 3.15.0-rc5-bone0.1 from RCN's github - for my > BBB > > under Debian. What I've found out recently is lack of > > /sys/devices/bone_capemgr.* directory. Also my atempts to turn off hdmi > via > > uEnv file fizzle out. Is it me doing something wrong or this is how it > > should be? Is there a way to get back my control over uarts, and ability > to > > turn off hdmi under new kernel? > > capemgr hasn't been ported fully from 3.8 > > Use this repo: > > https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.15 > > > You can enable extra usarts by adding this to uEnv.txt > > cape=ttyO1 > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > I have switched to the image you've recommended and succeeded only with enabling ttyO1, The other ones are not enabled. I've defined them like that in uEnv.txt: *cape=ttyO1cape=ttyO4cape=ttyO2cape=ttyO5* Is there a way to disable HDMI? cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN in uEnv.txt is not working, but since you said that capemgr had not been ported to new kernel I'm not surprised. If it's not possible to do in some other way, which image is the latest where capemgr works? -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] control over uarts and capes under kernel v. 3.15
On Wednesday, June 4, 2014 4:50:44 PM UTC+2, RobertCNelson wrote: > > On Wed, Jun 4, 2014 at 9:29 AM, krd > > wrote: > > Hey, > > > > I'm testing a new kernel - 3.15.0-rc5-bone0.1 from RCN's github - for my > BBB > > under Debian. What I've found out recently is lack of > > /sys/devices/bone_capemgr.* directory. Also my atempts to turn off hdmi > via > > uEnv file fizzle out. Is it me doing something wrong or this is how it > > should be? Is there a way to get back my control over uarts, and ability > to > > turn off hdmi under new kernel? > > capemgr hasn't been ported fully from 3.8 > > Use this repo: > > https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.15 > > > You can enable extra usarts by adding this to uEnv.txt > > cape=ttyO1 > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > I have switched to the image you've recommended and succeeded only with enabling ttyO1, The other ones are not enabled. I've defined them like that in uEnv.txt: *cape=ttyO1cape=ttyO4cape=ttyO2cape=ttyO5* Is there a way to disable HDMI? cape_disable=capemgr.disable_ partno=BB-BONELT-HDMI,BB-BONELT-HDMIN in uEnv.txt is not working, but since you said that capemgr had not been ported to new kernel I'm not surprised. If it's not possible to do in some other way, which is the latest system where capemgr works? -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] control over uarts and capes under kernel v. 3.15
On Wednesday, June 11, 2014 11:33:25 AM UTC+2, krd wrote: > > > > On Wednesday, June 4, 2014 4:50:44 PM UTC+2, RobertCNelson wrote: >> >> On Wed, Jun 4, 2014 at 9:29 AM, krd wrote: >> > Hey, >> > >> > I'm testing a new kernel - 3.15.0-rc5-bone0.1 from RCN's github - for >> my BBB >> > under Debian. What I've found out recently is lack of >> > /sys/devices/bone_capemgr.* directory. Also my atempts to turn off hdmi >> via >> > uEnv file fizzle out. Is it me doing something wrong or this is how it >> > should be? Is there a way to get back my control over uarts, and >> ability to >> > turn off hdmi under new kernel? >> >> capemgr hasn't been ported fully from 3.8 >> >> Use this repo: >> >> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.15 >> >> >> You can enable extra usarts by adding this to uEnv.txt >> >> cape=ttyO1 >> >> Regards, >> >> -- >> Robert Nelson >> http://www.rcn-ee.com/ >> > > > I have switched to the image you've recommended and succeeded only with > enabling ttyO1, The other ones are not enabled. I've defined them like that > in uEnv.txt: > > > > *cape=ttyO1cape=ttyO4cape=ttyO2cape=ttyO5* > > Is there a way to disable HDMI? cape_disable=capemgr.disable_ > partno=BB-BONELT-HDMI,BB-BONELT-HDMIN in uEnv.txt is not working, but > since you said that capemgr had not been ported to new kernel I'm not > surprised. If it's not possible to do in some other way, which is the > latest system where capemgr works? > Ok, I managed to switch off hdmi by removing all hdmi-related entries from dts files and recompile the kernel. That's not the most elegant solution for sure, but it works;) The uarts' issue still waits for the solution. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] control over uarts and capes under kernel v. 3.15
On Thursday, June 12, 2014 4:52:51 PM UTC+2, Miguel Aveiro wrote:
>
> Em 12-06-2014 07:04, krd escreveu:
>
> On Wednesday, June 11, 2014 11:33:25 AM UTC+2, krd wrote:
>>
>>
>>
>> On Wednesday, June 4, 2014 4:50:44 PM UTC+2, RobertCNelson wrote:
>>>
>>> On Wed, Jun 4, 2014 at 9:29 AM, krd wrote:
>>> > Hey,
>>> >
>>> > I'm testing a new kernel - 3.15.0-rc5-bone0.1 from RCN's github - for
>>> my BBB
>>> > under Debian. What I've found out recently is lack of
>>> > /sys/devices/bone_capemgr.* directory. Also my atempts to turn off
>>> hdmi via
>>> > uEnv file fizzle out. Is it me doing something wrong or this is how it
>>> > should be? Is there a way to get back my control over uarts, and
>>> ability to
>>> > turn off hdmi under new kernel?
>>>
>>> capemgr hasn't been ported fully from 3.8
>>>
>>> Use this repo:
>>>
>>> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v3.15
>>>
>>>
>>> You can enable extra usarts by adding this to uEnv.txt
>>>
>>> cape=ttyO1
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> http://www.rcn-ee.com/
>>>
>>
>>
>> I have switched to the image you've recommended and succeeded only with
>> enabling ttyO1, The other ones are not enabled. I've defined them like that
>> in uEnv.txt:
>>
>>
>>
>> *cape=ttyO1 cape=ttyO4 cape=ttyO2 cape=ttyO5*
>>
>> Is there a way to disable HDMI? cape_disable=capemgr.disable_
>> partno=BB-BONELT-HDMI,BB-BONELT-HDMIN in uEnv.txt is not working, but
>> since you said that capemgr had not been ported to new kernel I'm not
>> surprised. If it's not possible to do in some other way, which is the
>> latest system where capemgr works?
>>
>
> Ok, I managed to switch off hdmi by removing all hdmi-related entries from
> dts files and recompile the kernel. That's not the most elegant solution
> for sure, but it works;) The uarts' issue still waits for the solution.
>
> Well, I think there is a better solution, but since you already
> recompiled the kernel, I did just like you and edited
> "am335x-boneblack.dts":
>
> /*
> * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
> *
> * This program is free software; you can redistribute it and/or modify
> * it under the terms of the GNU General Public License version 2 as
> * published by the Free Software Foundation.
> */
> /dts-v1/;
>
> #include "am33xx.dtsi"
> #include "am335x-bone-common.dtsi"
>
> &ldo3_reg {
> regulator-min-microvolt = <180>;
> regulator-max-microvolt = <180>;
> regulator-always-on;
> };
>
> &mmc1 {
> vmmc-supply = <&vmmcsd_fixed>;
> };
>
> &mmc2 {
> vmmc-supply = <&vmmcsd_fixed>;
> pinctrl-names = "default";
> pinctrl-0 = <&emmc_pins>;
> bus-width = <8>;
> status = "okay";
> ti,vcc-aux-disable-is-sleep;
> };
>
> &uart2 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart2_pins>;
>
> status = "okay";
> };
>
> &uart4 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart4_pins>;
>
> status = "okay";
> };
>
> &uart5 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart5_pins>;
>
> status = "okay";
> };
>
> &am33xx_pinmux {
> };
>
>
> / {
> cpus {
> cpu@0 {
> cpu0-supply = <&dcdc2_reg>;
> /*
> * To consider voltage drop between PMIC and SoC,
> * tolerance value is reduced to 2% from 4% and
> * voltage value is increased as a precaution.
> */
> operating-points = <
> /* kHzuV */
> 1001325000
> 80130
> 60 1112000
> 30 969000
> >;
> };
> };
>
> };
>
>
Thanks a lot! Your solution works very nice.
--
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
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 files, 771069/3864576 > blocks > > [7.665617] libphy: PHY 4a101000.mdio:00 not found > > [7.670642] net eth0: phy 4a101000.mdio:00 not found on slave 0 > > [7.676834] libphy: PHY 4a101000.mdio:01 not found > > [7.681844] net eth0: phy 4a101000.mdio:01 not found on slave 1 > > > > > > I've to reboot many times to get lucky . > > Hey Micka, > > how about the newly pushed out bone60? > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > I am using 3.15.0-rc8-bone1 kernel and I am experiencing the same problem with loosing eth occasionally. For some reasons I don't want to use 3.8.* kernels. Can you recommend me some of these new kernel that do not replicate the issue? I am thinking of giving a try to the latest 3.16-rc5... -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
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 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.670642] net eth0: phy 4a101000.mdio:00 not found on slave 0 > >> > [7.676834] libphy: PHY 4a101000.mdio:01 not found > >> > [7.681844] net eth0: phy 4a101000.mdio:01 not found on slave 1 > >> > > >> > > >> > I've to reboot many times to get lucky . > >> > >> Hey Micka, > >> > >> how about the newly pushed out bone60? > >> > >> Regards, > >> > >> -- > >> Robert Nelson > >> http://www.rcn-ee.com/ > > > > > > > > I am using 3.15.0-rc8-bone1 kernel and I am experiencing the same > problem > > with loosing eth occasionally. For some reasons I don't want to use > 3.8.* > > kernels. Can you recommend me some of these new kernel that do not > replicate > > the issue? I am thinking of giving a try to the latest 3.16-rc5... > > Well, I added that patch in "3.15.4-bone4" so "3.15.0-rc8-bone1" > doesn't include it. The latest from that branch is "3.15.6-bone5" > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > I updated my kernel to 3.15.6-bone5, just as you've said. But, as it seems, this does not fix the issue completely. What I'm observing is lack of ethernet connection after some boots. They characterise with initial hangup, I can see 'C' being put on the console until a watchdog located on cape connected to my BBB reboots the BBB. It happens on its own, without any extraordinary operation being run on this system. For example two times last night. I have to plug out and in the power cable to fix the issue, SW reboot doesn't help. Power is delivered to BBB via our cape. Another way to reproduce it is to plug out the sd card and wait for watchdog to reboot BBB. After that, 'C' are printed to the console(OS on eMMC is not bootable), and when I insert back the sd it instantly boots from it. No connection after that too. Do you have any ideas on what's going on and how to fix this? Below I'm attaching the log from this: Welcome to minicom 2.7 OPTIONS: I18n Compiled on Jan 1 2014, 17:13:19. Port /dev/ttyUSB0, 14:22:11 Press CTRL-A Z for help on special keys CCC U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) reading args spl_load_image_fat_os: error reading image args, err - -1 reading u-boot.img reading u-boot.img U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54) I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment Net:not set. Validating first E-fuse MAC Could not get PHY for cpsw: addr 0 cpsw, usb_ether Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt 1696 bytes read in 6 ms (275.4 KiB/s) gpio: pin 55 (gpio 55) value is 1 Loaded environment from uEnv.txt Importing environment from mmc ... using: am335x-boneblack.dtb... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImaget it. After that, 'C' are printed to the console(OS on eMMC is not bootable), and when i insert back the sd it instantly boots from it. No ethernet after that too. Below I'm attaching the log f 6224648 bytes read in 343 ms (17.3 MiB/s) reading initrd.img 2957458 bytes read in 218 ms (12.9 MiB/s) reading /dtbs/am335x-boneblack.dtb 31128 bytes read in 11 ms (2.7 MiB/s) Kernel image @ 0x8200 [ 0x00 - 0x5efb08 ] ## Flattened Device Tree blob at 8800 Booting using the fdt blob at 0x8800 Using Device Tree in place at 8800, end 8800a997 Starting kernel ... [0.581100] omap_init_mbox: hwmod doesn't have valid attrs [2.361161] ti_reset_probe: missing 'resets' child node. [2.381165] pinctrl-single 44e10800.pinmux: pin 44e10950.0 already requested by 48024000.serial; cai [2.393187] pinctrl-single 44e10800.pinmux: pin-84 (4803.spi) status -22 [2.400599] pin
