Re: [beagleboard] Static IP Trouble for internet connection
It should be gateway NOT getaway On 01/31/2015 11:44 AM, greedman wrote: I've added the getaway (the address of my router), and the same thing, it works in my LAN, but it doesn't work outside my LAN. # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 inet static #name Ethernet alias LAN card address 192.168.0.89 netmask 255.255.255.0 network 192.168.0.1 broadcast 192.168.0.255 getaway 192.168.0.1 On Friday, 30 January 2015 00:23:30 UTC+1, David wrote: Just a guess, but you do not have a gateway defined. Maybe that is the issue? On 01/29/2015 04:53 PM, greedman wrote: Hi all, I use a BBB, with Debian, to transfer files through a SSH connection, and I have been configuring it to have a static IP. I have configured it modifying the file “/etc/network/interfaces”, where I've added: # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 inet static #name Ethernet alias LAN card address 192.168.0.89 netmask 255.255.255.0 network 192.168.0.1 broadcast 192.168.0.255 And I've also modified the file “/etc/resolv.conf”, where I've added: nameserver 192.168.0.1 nameserver 8.8.8.8 On the inTRAnet it works perfectly, but when I try to connect from the internet to the BBB it doesn't work (with the original configuration, without static ip, the connection is established). I think the trouble is due to the “interfaces” file changes, but I do not know why. I've used the next links: https://sheldondwill.wordpress.com/2013/12/14/beaglebone-black-ubuntu-change-to-static-ip-address/ https://sheldondwill.wordpress.com/2013/12/14/beaglebone-black-ubuntu-change-to-static-ip-address/ https://www.howtoforge.com/debian-static-ip-address https://www.howtoforge.com/debian-static-ip-address Thanks in advance -- 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 javascript:. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Static IP Trouble for internet connection
Just a guess, but you do not have a gateway defined. Maybe that is the issue? On 01/29/2015 04:53 PM, greedman wrote: Hi all, I use a BBB, with Debian, to transfer files through a SSH connection, and I have been configuring it to have a static IP. I have configured it modifying the file “/etc/network/interfaces”, where I've added: # The primary network interface auto eth0 #iface eth0 inet dhcp iface eth0 inet static #name Ethernet alias LAN card address 192.168.0.89 netmask 255.255.255.0 network 192.168.0.1 broadcast 192.168.0.255 And I've also modified the file “/etc/resolv.conf”, where I've added: nameserver 192.168.0.1 nameserver 8.8.8.8 On the inTRAnet it works perfectly, but when I try to connect from the internet to the BBB it doesn't work (with the original configuration, without static ip, the connection is established). I think the trouble is due to the “interfaces” file changes, but I do not know why. I've used the next links: https://sheldondwill.wordpress.com/2013/12/14/beaglebone-black-ubuntu-change-to-static-ip-address/ https://www.howtoforge.com/debian-static-ip-address Thanks in advance -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Netinstall errors
On 01/06/2015 11:53 AM, Robert Nelson wrote: On Tue, Jan 6, 2015 at 11:27 AM, David Lambert d...@lambsys.com wrote: I have just recently experienced errors with RCN's netinstall as follows: Debootstrap Error │ ┌─│ Couldn't retrieve dists/wheezy/main/binary-armhf/Packages. This may │ │ │ be due to a network problem or a bad CD, depending on your │ │ │ installation method. I have exhausted all methods for testing my network (cables, packet loss monitoring, changing mirrors, etc.) This seems to happen with either wheezy or jessie. Is there some maintenance going on right now? I am puzzled. Odd, I just fired up a wheezy netinstall too.. Not seeing that on my end. I know 7.8 is scheduled for this weekend, so the repo might have been in a mid update to move any wheezy updates into the archive. Regards, Seems to be OK now. I think you may be right about the repo update. It was certainly giving multiple errors fro around 9 last night up to 10 this morning. Cheers, Dave. -- 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] Netinstall errors
I have just recently experienced errors with RCN's netinstall as follows: Debootstrap Error │ ┌─│ Couldn't retrieve dists/wheezy/main/binary-armhf/Packages. This may │ │ │ be due to a network problem or a bad CD, depending on your │ │ │ installation method. I have exhausted all methods for testing my network (cables, packet loss monitoring, changing mirrors, etc.) This seems to happen with either wheezy or jessie. Is there some maintenance going on right now? I am puzzled. Dave. -- 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] running ntpdate to get time
It seems like your name resolver (DNS) may not be set up correctly. Try something like ping google.com. If that doesn't work, then look at /etc/resolv.conf which should contain the IP addresses of your nameservers. BTW sudo is only necessary to run a command that needs root privileges from a non-root account. In your case it appears that you are running as root (the # prompt). HTH, Dave. On 01/02/2015 07:56 PM, rjc2827 wrote: I'm new, so there's some early step that I've overlooked, but I can't set the time, and I don't know why. I'm running the Ver C BBB with Debian pre-installed. I have flashed the newest OS version, and have found PuTTY to get me access to the SSH shell. I've even got a single LED to light up with some sample code that I've found. I now want to apt-get update and install, but I've been told to get my date set up first so that the update/install goes smoothly, but ... Both of: root@beaglebone:~# ntpdate pool.ntp.org root@beaglebone:~# sudo ntpdate pool.ntp.org get me a response of: Error resolving pool.ntp.org: Name or service not known (-2) 15 May 07:34:42 ntpdate[5292]: Can't find host pool.ntp.org: Name or service not known (-2) 15 May 07:34:42 ntpdate[5292]: no servers can be used, exiting While we're at it, when should sudo be used or avoided ... I'm really not clear on this. Thanks rjc -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] which program language is better for BBB
I can't resist adding the expression - Go Forth and Multiply ;) On 12/20/2014 05:48 PM, Robert Nelson wrote: On Sat, Dec 20, 2014 at 5:30 PM, rwrma...@gmail.com wrote: I was just following Robert's lead. Sorry... ;) It was interesting however to see that a relatively current Open Source COBOL project actually exists. That's just what I do. Say something like that and I have to go look. Lol... Considering we have forth for the pru... Maybe we need a COBOL port for the pru.. ;) A banking language tied to the Programmable Realtime Unit, just think how fast we could trade! pru schwab anyone? Regards, -- 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] BBB 3.18.0 kernel lockups
I have been using 3.18.0 without issue for the last few days. I am using the default config. Dave. On 12/12/2014 02:51 PM, Christof Meerwald wrote: Hi, 3.18.0 kernel locks up my BBB after a few seconds of maxing out the Ethernet connection - unfortunately, there is no output on the serial console. Kernel 3.17.1 on the other hand is fine. Anyone else seeing this or having an idea what could have caused this in 3.18? Christof -- 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] Complete newbie -- Stupid question
You are currently in the directory /root/ that has no files. Try ls -Ralg /. HTH, Dave. On 09/19/2014 09:46 PM, jacksonwr.ra...@gmail.com wrote: I got the Beagle Bone to get back into computing so I'm very new at linux. I just powered the board up and got it connected to my MAC via SSH. I'm able to login to root and get the following prompt: Last login: Wed Apr 23 20:20:36 2014 from 192.168.7.1 root@beaglebone:~# From here I can run some basic linux commands but I'm not seeing any directories or files. Is this what I should see? I thought I would at least see some basic directory structures and files at this point. Thoughts? Thanks for your help. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Beaglebone Black Rebooting Several Times Every Day
I agree, serial cable is a must. Here's one a bit cheaper and on Amazon Prime: http://www.amazon.com/gp/product/B008AGDTA4/ref=oh_aui_detailpage_o02_s00?ie=UTF8psc=1 On 09/14/2014 04:53 PM, William Hermans wrote: Greg, buying a serial debug cable really is necessary if you intend to do anything serious with the BBB. However . . . http://www.ebay.com/itm/like/351093728732?lpid=82 According to the PL2303HX datasheet it is 3v3 TTL, but double check for yourself. I've seen these cheap USB-Serial converters go for as low as 2-3 USD. Cables, 6 bux US is about as low as I remember having seen them. From what I understand they're also supposed to be fairly decent, but as with anything else YMMV. You said something about having other cables / modules just wrong header ? why not whip an adapter up ? Not that hard to make / use jumper wires . . . does matter if it looks pretty so long as it serves it's purpose. On Sun, Sep 14, 2014 at 2:42 PM, William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com wrote: Oh, and right, only time I've had my beaglebone black reset, is when it loses power ( we switch from generator, and back to solar ). Or I've intentionally reset it. Mostly I reset my own board because I make lots of changes to various things, and I want to make sure it comes back up as intended from a reset. On Sun, Sep 14, 2014 at 2:40 PM, William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com wrote: william@arm:~$ uptime 14:38:02 up 4 days, 4:31, 1 user, load average: 0.04, 0.03, 0.05 And this is a small uptime. I've had it run for months at a time. Others yet have had longer uptimes. One thing you have not mentioned, or at least i have not seen you mention is if you're connecting anything on the IO pins. IF so, what. On Sun, Sep 14, 2014 at 12:17 PM, Greg Kelley suekkel...@gmail.com mailto:suekkel...@gmail.com wrote: Another reset early this afternoon, so I have shutdown and removed the 5v2a cheapo PS and replaced it with a Garmin 5v1a PS I have that uses the mini USB instead of the banana plug. I want to eliminate the current PS as the problem. All my PS are in two power strips plugged into an APC Battery Backup so power is conditioned, filtered, and constant. I'm spending waaa too much time with this since my RasPi has been set up same way and running 24/7 since I plugged it in with zero issues. Am I the only one with constant resets on a BBB? I'm hesitant to drop $24 on a serial debug cable that I'll use maybe two days to capture data that might or might not shed light on the issue. On Saturday, September 13, 2014 8:14:05 AM UTC-4, Greg Kelley wrote: Update: the BBB just reset again at 7:49am. That's interesting, because it reset twice yesterday at almost the same times 7:35am and 8:13am and today at 7:13am and 7:49am. cron daily runs at 6:25am and I have no ctontab jobs at those times. Appears to be some sort of pattern due to the daily reset times being so close, but there is nothing is syslog except cron.hourly until the new boot sequence starts. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Boot sequence on netinstall image
I just decided to update my image using RCN's netinstall sudo ./mk_mmc.sh --mmc /dev/sdd --dtb am335x-boneblack --firmware --no-swap --serial-mode Now I realize that I do not understand how this system boots. I used to believe that the onchip ROM looked for the file MLO in the boot partition, but there no longer appears to be one! Could someone direct me as to how the initial boot sequence works?? Best regards, Dave. -- 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] Boot sequence on netinstall image
Thanks so much for your very informative reply :) On 09/12/2014 12:06 PM, Robert Nelson wrote: On Fri, Sep 12, 2014 at 12:01 PM, David Lambert d...@lambsys.com wrote: I just decided to update my image using RCN's netinstall sudo ./mk_mmc.sh --mmc /dev/sdd --dtb am335x-boneblack --firmware --no-swap --serial-mode Now I realize that I do not understand how this system boots. I used to believe that the onchip ROM looked for the file MLO in the boot partition, but there no longer appears to be one! Could someone direct me as to how the initial boot sequence works?? The MLO/u-boot.img files are now dd'ed to the disk: dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k So a 'vfat' partition is no longer needed. So, only the location of MLO/u-boot.img changed, everything else is relatively the same. Regards, -- 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] Beaglebone Black Rebooting Several Times Every Day
If you have a serial interface, I suggest turn on logging and post the results here. On 09/02/2014 06:44 AM, Greg Kelley wrote: Got my first BBB last week, installed latest Debian. USB Hot Plug was completely hosed in Kernel 3.8 so I upgraded to 3.16 (latest non-rc version). Currently running CUPS print services (including Airprint) and weewx. It appears that the BBB is rebooting three or four times between 10pm and 1am, this has happened the last two days. I discovered it because weewx was going into an ftp loop because the system clock time was getting whacked (it is time/date sensitive to process weather data). Nothing in the log files unusual. Powered with a 5v 2a supply. Ethernet cable attached and external USB Hub (has external power but not used) with printer (turned off) and Weather Data Logger attached (has it's own power). Before I start experimenting with removing USB Hub, plugging in just Weather Data Logger, etc. thought I'd check here first. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] best kernel version for bbb
Robert, I seem to have an issue with my am335x-boneblack-cape-bone-argus.dts in 3.16.0-rc7-bone1. This time it appears that there is a clash with the Ethernet subsystem. Has something changed in this area from 3.15? Regards, Dave. On 07/16/2014 08:13 AM, David Lambert wrote: Thanks Robert. That works fine! Regards, Dave. On 07/15/2014 07:04 PM, Robert Nelson wrote: On Tue, Jul 15, 2014 at 6:52 PM, David Lambert d...@lambsys.com wrote: On 07/15/2014 04:40 PM, Robert Nelson wrote: On Tue, Jul 15, 2014 at 4:35 PM, David Lambert d...@lambsys.com wrote: Thanks so much Robert - I think you nailed it! Unfortunately I did not inherit this change as I could not import am335x-bone-common.dtsi due to the clash: /*pinctrl-0 = clkout2_pin; clash with argus-ups */ I'll clean that up in a bit and push it.. I have another patch from John for audio too, so i'll get a new bone tag released this evening.. Regards, Also I found this one. /*pinctrl-0 = ecap0_pin_p9_42; clash with Argus */ Here's what i came up for the v3.15.x branch. This should make usb work now.. https://github.com/RobertCNelson/bb-kernel/commit/e34510a7b5c6712386590818ba84e8ea8752f7f0 Not sure of the best way to handle these sort of situations. Currently I am just copying then editing the contents of am335x-bone-common.dtsi into my dts. This is obviously a very messy hack. Maybe am335x-bone-common.dtsi could be subdivided into smaller chunks Yeah, it needs to be cleaned up badly.. It's only getting worse with more patches on linux-omap.. We just need a weekend, few kegs and do a cleanup.. 1: am335x-bone-common.dtsi (only common stuff and all pinmux's) 2: am335x-boneblack-common.dtsi (no eMMC/HDMI/HDMI Audio) 3: am335x-boneblack-eMMC.dtsi 4: am335x-boneblack-HDMI.dtsi 5: am335x-boneblack-HDMIA.dtsi am335x-bone.dtb = (1) am335x-boneblack.dtb = (1+2+3+4+5) Then it should be easy to expand on am335x-boneblack-common.dtsi and enable your cape. Regards, -- 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] best kernel version for bbb
Robert,
For your perusal, I have attached my patch to get my cape
peacefully coexisting (I hope) with the changes in 3.16.
Best regards,
Dave.
On 07/31/2014 01:32 PM, David Lambert wrote:
Robert,
I seem to have an issue with my
am335x-boneblack-cape-bone-argus.dts in 3.16.0-rc7-bone1. This time it
appears that there is a clash with the Ethernet subsystem. Has
something changed in this area from 3.15?
Regards,
Dave.
On 07/16/2014 08:13 AM, David Lambert wrote:
Thanks Robert. That works fine!
Regards,
Dave.
On 07/15/2014 07:04 PM, Robert Nelson wrote:
On Tue, Jul 15, 2014 at 6:52 PM, David Lambert d...@lambsys.com
wrote:
On 07/15/2014 04:40 PM, Robert Nelson wrote:
On Tue, Jul 15, 2014 at 4:35 PM, David Lambert d...@lambsys.com
wrote:
Thanks so much Robert - I think you nailed it! Unfortunately I
did not
inherit this change as I could not import am335x-bone-common.dtsi
due to
the
clash:
/*pinctrl-0 = clkout2_pin; clash with argus-ups */
I'll clean that up in a bit and push it.. I have another patch from
John for audio too, so i'll get a new bone tag released this
evening..
Regards,
Also I found this one.
/*pinctrl-0 = ecap0_pin_p9_42; clash with Argus */
Here's what i came up for the v3.15.x branch. This should make usb
work now..
https://github.com/RobertCNelson/bb-kernel/commit/e34510a7b5c6712386590818ba84e8ea8752f7f0
Not sure of the best way to handle these sort of situations.
Currently I am
just copying then editing the contents of am335x-bone-common.dtsi
into my
dts. This is obviously a very messy hack. Maybe
am335x-bone-common.dtsi
could be subdivided into smaller chunks
Yeah, it needs to be cleaned up badly.. It's only getting worse with
more patches on linux-omap.. We just need a weekend, few kegs and do a
cleanup..
1: am335x-bone-common.dtsi (only common stuff and all pinmux's)
2: am335x-boneblack-common.dtsi (no eMMC/HDMI/HDMI Audio)
3: am335x-boneblack-eMMC.dtsi
4: am335x-boneblack-HDMI.dtsi
5: am335x-boneblack-HDMIA.dtsi
am335x-bone.dtb = (1)
am335x-boneblack.dtb = (1+2+3+4+5)
Then it should be easy to expand on am335x-boneblack-common.dtsi and
enable your cape.
Regards,
--
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.
From 97426cfbbf2ae9942ad36682e10a6f3f7ac0867e Mon Sep 17 00:00:00 2001
From: Dave Lambert d...@lambsys.com
Date: Thu, 31 Jul 2014 14:33:48 -0500
Subject: Updated dts to be in line with 3.16 changes.
---
.../boot/dts/am335x-boneblack-cape-bone-argus.dts | 215 +---
1 file changed, 186 insertions(+), 29 deletions(-)
diff --git a/arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dts b/arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dts
index fd864e3..a3e300a 100644
--- a/arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dts
+++ b/arch/arm/boot/dts/am335x-boneblack-cape-bone-argus.dts
@@ -59,7 +59,15 @@
};
};
- vmmcsd_fixed: fixedregulator@0 {
+ vbat: fixedregulator@0 {
+ compatible = regulator-fixed;
+ regulator-name = vbat;
+ regulator-min-microvolt = 500;
+ regulator-max-microvolt = 500;
+ regulator-boot-on;
+ };
+
+ vmmcsd_fixed: fixedregulator@1 {
compatible = regulator-fixed;
regulator-name = vmmcsd_fixed;
regulator-min-microvolt = 330;
@@ -101,6 +109,20 @@
;
};
+ uart1_pins: pinmux_uart1_pins {
+ pinctrl-single,pins =
+ 0x180 (PIN_INPUT_PULLUP | MUX_MODE0) /* uart1_rxd.uart1_rxd */
+ 0x184 (PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* uart1_txd.uart1_txd */
+ ;
+ };
+
+ uart2_pins: pinmux_uart2_pins {
+ pinctrl-single,pins =
+ 0x150 0x21 /* spi0_sclk.uart2_rxd | MODE1 */
+ 0x154 0x01 /* spi0_d0.uart2_txd | MODE1 */
+ ;
+ };
+
uart4_pins: pinmux_uart4_pins {
pinctrl-single,pins =
0x070 0x26 /* gpmc_wait0.uart4_rxd | MODE6 */
@@ -108,6 +130,13 @@
;
};
+ uart5_pins: pinmux_uart5_pins {
+ pinctrl-single,pins =
+ 0x0C4 0x24 /* lcd_data9.uart5_rxd | MODE4 */
+ 0x0C0 0x04 /* lcd_data8.uart5_txd | MODE4 */
+ ;
+ };
+
clkout2_pin: pinmux_clkout2_pin {
pinctrl-single,pins =
0x1b4 (PIN_OUTPUT_PULLDOWN | MUX_MODE3) /* xdma_event_intr1.clkout2 */
@@ -173,6 +202,47 @@
0x160 (PIN_INPUT | MUX_MODE7) /* GPIO0_6 */
;
};
+ emmc_pins: pinmux_emmc_pins {
+ pinctrl-single,pins =
+ 0x80 (PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn1.mmc1_clk */
+ 0x84 (PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_csn2.mmc1_cmd */
+ 0x00 (PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad0.mmc1_dat0 */
+ 0x04 (PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad1.mmc1_dat1 */
+ 0x08 (PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad2.mmc1_dat2 */
+ 0x0c (PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad3.mmc1_dat3 */
+ 0x10 (PIN_INPUT_PULLUP | MUX_MODE1) /* gpmc_ad4.mmc1_dat4
Re: [beagleboard] best kernel version for bbb
Robert, What is a rt? Regards, Dave. On 07/14/2014 04:39 PM, Robert Nelson wrote: On Mon, Jul 14, 2014 at 4:34 PM, Maxim Podbereznyy lisar...@gmail.com wrote: Hi guys! I can see Robert offers 3 kernel vesions for bbb: 1) v3.8.x 2) v3.13.x 3) v3.15.x who can tell pros and cons for each of them? I need one to prepare something stable/reliable for my client. v3.8.x = capemgr v3.13.x = working sgx v3.15.x = it's going to be short lived, planing to moving to v3.16.x pretty soon, as that'll have a rt and it should be the default for jessie Regards, -- 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] best kernel version for bbb
Thanks Robert. That works fine! Regards, Dave. On 07/15/2014 07:04 PM, Robert Nelson wrote: On Tue, Jul 15, 2014 at 6:52 PM, David Lambert d...@lambsys.com wrote: On 07/15/2014 04:40 PM, Robert Nelson wrote: On Tue, Jul 15, 2014 at 4:35 PM, David Lambert d...@lambsys.com wrote: Thanks so much Robert - I think you nailed it! Unfortunately I did not inherit this change as I could not import am335x-bone-common.dtsi due to the clash: /*pinctrl-0 = clkout2_pin; clash with argus-ups */ I'll clean that up in a bit and push it.. I have another patch from John for audio too, so i'll get a new bone tag released this evening.. Regards, Also I found this one. /*pinctrl-0 = ecap0_pin_p9_42; clash with Argus */ Here's what i came up for the v3.15.x branch. This should make usb work now.. https://github.com/RobertCNelson/bb-kernel/commit/e34510a7b5c6712386590818ba84e8ea8752f7f0 Not sure of the best way to handle these sort of situations. Currently I am just copying then editing the contents of am335x-bone-common.dtsi into my dts. This is obviously a very messy hack. Maybe am335x-bone-common.dtsi could be subdivided into smaller chunks Yeah, it needs to be cleaned up badly.. It's only getting worse with more patches on linux-omap.. We just need a weekend, few kegs and do a cleanup.. 1: am335x-bone-common.dtsi (only common stuff and all pinmux's) 2: am335x-boneblack-common.dtsi (no eMMC/HDMI/HDMI Audio) 3: am335x-boneblack-eMMC.dtsi 4: am335x-boneblack-HDMI.dtsi 5: am335x-boneblack-HDMIA.dtsi am335x-bone.dtb = (1) am335x-boneblack.dtb = (1+2+3+4+5) Then it should be easy to expand on am335x-boneblack-common.dtsi and enable your cape. Regards, -- 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] best kernel version for bbb
Thanks John. Further investigation revealed that something has changed that causes my cape dtb to interfere with USB :-( Dave. On 07/15/2014 01:05 AM, John Syn wrote: On 7/14/14, 7:41 PM, David Lambert d...@lambsys.com wrote: I don't see any mention of 3.14. I have been using 3.14.8-bone5 for quite a few weeks now. I could never get USB to work on 3.15.x. Should I revert to 3.13.x?? USB is working fine for me on V3.15.4-bone4. What is it that you are trying to do that does not work? Here is an example of USB working on V3.15: I have a Ortek Wireless keyboard and mouse connected to a powered USB Hub. root@arm:~# lsusb Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 05a4:2000 Ortek Technology, Inc. WKB-2000 Wireless Keyboard with Touchpad Now I insert a SanDisk USB flash drive: root@arm:~# [23389.316005] usb 2-1.2: new high-speed USB device number 4 using musb-hdrc [23389.416641] usb 2-1.2: device v0781 p5575 is not supported [23389.422448] usb 2-1.2: New USB device found, idVendor=0781, idProduct=5575 [23389.429756] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [23389.437477] usb 2-1.2: Product: Cruzer Glide [23389.441974] usb 2-1.2: Manufacturer: SanDisk [23389.446499] usb 2-1.2: SerialNumber: 20043515931AE20186C5 [23389.454569] usb-storage 2-1.2:1.0: USB Mass Storage device detected [23389.462767] scsi0 : usb-storage 2-1.2:1.0 [23390.467381] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Glide 1.26 PQ: 0 ANSI: 5 [23390.481964] sd 0:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB) [23390.502368] sd 0:0:0:0: [sda] Write Protect is off [23390.515109] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [23390.551041] sda: sda1 sda2 [23390.565653] sd 0:0:0:0: [sda] Attached SCSI removable disk So plugplay works fine. Confirm the SanDisk drive was recognized correctly: root@arm:~# lsusb Bus 002 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0781:5575 SanDisk Corp. Bus 002 Device 003: ID 05a4:2000 Ortek Technology, Inc. WKB-2000 Wireless Keyboard with Touchpad Mount the Drive: root@arm:/media# mount /dev/sda1 diska mount: block device /dev/sda1 is write-protected, mounting read-only Display drive contents: root@arm:/media# ls diska autorun.inf doc install pool README.txt boot efi install.amd README.html setup.exe css firmware isolinux README.mirrors.html tools debian g2ldr md5sum.txt README.mirrors.txt win32-loader.ini dists g2ldr.mbr pics README.source Regards, John Dave. On 07/14/2014 04:39 PM, Robert Nelson wrote: On Mon, Jul 14, 2014 at 4:34 PM, Maxim Podbereznyy lisar...@gmail.com wrote: Hi guys! I can see Robert offers 3 kernel vesions for bbb: 1) v3.8.x 2) v3.13.x 3) v3.15.x who can tell pros and cons for each of them? I need one to prepare something stable/reliable for my client. v3.8.x = capemgr v3.13.x = working sgx v3.15.x = it's going to be short lived, planing to moving to v3.16.x pretty soon, as that'll have a rt and it should be the default for jessie Regards, -- 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. -- 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] best kernel version for bbb
Thanks so much Robert - I think you nailed it! Unfortunately I did not inherit this change as I could not import am335x-bone-common.dtsi due to the clash: /*pinctrl-0 = clkout2_pin; clash with argus-ups */ Regards, Dave. On 07/15/2014 12:38 PM, Robert Nelson wrote: On Tue, Jul 15, 2014 at 12:33 PM, David Lambert d...@lambsys.com wrote: Thanks John. Further investigation revealed that something has changed that causes my cape dtb to interfere with USB :-( Dave. I think the usb node address register changed in v3.15.x. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/am335x-bone-common.dtsi?id=a2f8d6b303213a98436455aece7e14cdd1240629 Regards, -- 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] best kernel version for bbb
On 07/15/2014 04:40 PM, Robert Nelson wrote: On Tue, Jul 15, 2014 at 4:35 PM, David Lambert d...@lambsys.com wrote: Thanks so much Robert - I think you nailed it! Unfortunately I did not inherit this change as I could not import am335x-bone-common.dtsi due to the clash: /*pinctrl-0 = clkout2_pin; clash with argus-ups */ I'll clean that up in a bit and push it.. I have another patch from John for audio too, so i'll get a new bone tag released this evening.. Regards, Also I found this one. /*pinctrl-0 = ecap0_pin_p9_42; clash with Argus */ Not sure of the best way to handle these sort of situations. Currently I am just copying then editing the contents of am335x-bone-common.dtsi into my dts. This is obviously a very messy hack. Maybe am335x-bone-common.dtsi could be subdivided into smaller chunks Regards, -- 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] best kernel version for bbb
I don't see any mention of 3.14. I have been using 3.14.8-bone5 for quite a few weeks now. I could never get USB to work on 3.15.x. Should I revert to 3.13.x?? Dave. On 07/14/2014 04:39 PM, Robert Nelson wrote: On Mon, Jul 14, 2014 at 4:34 PM, Maxim Podbereznyy lisar...@gmail.com wrote: Hi guys! I can see Robert offers 3 kernel vesions for bbb: 1) v3.8.x 2) v3.13.x 3) v3.15.x who can tell pros and cons for each of them? I need one to prepare something stable/reliable for my client. v3.8.x = capemgr v3.13.x = working sgx v3.15.x = it's going to be short lived, planing to moving to v3.16.x pretty soon, as that'll have a rt and it should be the default for jessie Regards, -- 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] Build linux kernel from source need help
On 06/27/2014 11:25 AM, Robert Nelson wrote: On Fri, Jun 27, 2014 at 11:05 AM, Kanchy Kang kan...@gmail.com wrote: Hello all, I use Debian (BeagleBone Black - 2GB eMMC) 2014-05-14 for my BBB. Now i want to build linux kernel 3.13/3.14 from source. Is there any guide? Also i feel confused about the difference between git://github.com/beagleboard/kernel.git and https://github.com/RobertCNelson/stable-kernel. which one should i follow? For the bone, use this repo: https://github.com/RobertCNelson/bb-kernel I know I have posted this before, but it is still bugging me. Whenever I try the 3.15 kernel, I cannot see USB devices. On my development machine: git clone https://github.com/RobertCNelson/bb-kernel cd bb-kernel/ git checkout origin/am33x-v3.15 -b tmp ./build_kernel.sh (all default configurations) ./tools/install_kernel.sh Then on the BBB: uname -a Linux trax-jdal 3.15.2-bone2 #1 Fri Jun 27 15:39:41 CDT 2014 armv7l GNU/Linux lsusb unable to initialize libusb: -99 Any help would be appreciated. Regards, Dave. The full overview is here: http://eewiki.net/display/linuxonarm/BeagleBone+Black Since you have the bootloader/debian installed, just use the kernel directions. Regards, -- 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] Can't saveenv
I am not an expert in this, but if this is a Beaglebone, I don't think there is any NAND, so saveenv will not work. I think modifications to environment go in uEnv.txt or must be compiled into U-Boot. HTH, Dave. On 06/21/2014 07:51 PM, Lucas Tanure wrote: I can't saveenv. I got this: U-Boot# saveenv Saving Environment to NAND... Erasing NAND... Attempt to erase non block-aligned data -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Hotplug in Debian
It appears that the Ethernet hotplug in a fresh rcn netinstall does not trigger ifupdown: ifconfig eth0 Link encap:Ethernet HWaddr c8:a0:30:af:93:56 inet addr:192.168.1.196 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::caa0:30ff:feaf:9356/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:260 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:43917 (42.8 KiB) TX bytes:7630 (7.4 KiB) Interrupt:40 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Cable unplugged root@argus:~# [ 305.814940] libphy: 4a101000.mdio:00 - Link is Down ifconfig eth0 Link encap:Ethernet HWaddr c8:a0:30:af:93:56 inet addr:192.168.1.196 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::caa0:30ff:feaf:9356/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:279 errors:0 dropped:0 overruns:0 frame:0 TX packets:81 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:45588 (44.5 KiB) TX bytes:7630 (7.4 KiB) Interrupt:40 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Note that eth0 is still up, so I tried udevadm: root@argus:~# udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent [ 431.041873] libphy: 4a101000.mdio:00 - Link is Up - 100/Full [ 435.129578] libphy: 4a101000.mdio:00 - Link is Down [ 439.350691] libphy: 4a101000.mdio:00 - Link is Up - 100/Full There appear to be kernel printouts but no udev events? Any ideas? -- 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] USB on kernel 3.15
I am still having trouble with USB on 3.15 kernels. I have tried both: git://github.com/RobertCNelson/linux-dev.git and: https://github.com/RobertCNelson/bb-kernel.git but USB appears not to work with either: 'lsusb' gives the message: unable to initialize libusb: -99 3.13 and 3.14 appear to work OK. Any pointers as to how I should be compiling 3.15 kernels? Regards, Dave. -- 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] RCN kernel USB question on 3.15.0-rc5-bone0.1
On 05/31/2014 12:34 PM, Robert Nelson wrote:
On Sat, May 31, 2014 at 12:15 PM, David Lambert d...@lambsys.com wrote:
Robert,
Excuse my ignorance, but what are the intended uses/audiences of:
git://github.com/RobertCNelson/linux-dev.git
and:
https://github.com/RobertCNelson/bb-kernel.git
Just curious?
Well the plan was it would be in linux-dev shorterm, and eventually
pushed into my multiplatform.. So now that i have three git HEAD's
(armv7, armv7-lpae, bone) it's just easier to maintain it in it's
seperate repo. (i do all my main work off linux-dev's head)
Regards,
I'm still a bit confused. The bb-kernel repository appears to be ahead
of linux-dev:
diff ../bb-kernel/version.sh version.sh -u
--- ../bb-kernel/version.sh2014-06-15 09:59:25.366029431 -0500
+++ version.sh2014-06-15 15:35:16.343316349 -0500
@@ -20,19 +20,17 @@
config=omap2plus_defconfig
#toolchain=gcc_linaro_eabi_4_8
-#toolchain=gcc_linaro_eabi_4_9
#toolchain=gcc_linaro_gnueabi_4_6
#toolchain=gcc_linaro_gnueabihf_4_7
toolchain=gcc_linaro_gnueabihf_4_8
-#toolchain=gcc_linaro_gnueabihf_4_9
#Kernel/Build
KERNEL_REL=3.15
-KERNEL_TAG=${KERNEL_REL}
-BUILD=bone1.1
+KERNEL_TAG=${KERNEL_REL}-rc5
+BUILD=bone0.1
#v3.X-rcX + upto SHA
-#KERNEL_SHA=
+#KERNEL_SHA=e6036c0b88962df82a8853971b86a55f09faef40
#git branch
BRANCH=am33x-v3.15
Which repository should I be using?
Regards,
Dave.
--
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] RCN kernel USB question on 3.15.0-rc5-bone0.1
Thanks Robert, I built 3.15-rc7-bone1 (by editing version.sh in your scripts), but still get the same behavior. Any suggestions? Are the KERNEL_TAG, and BUILD variables all I need to edit? Regards, Dave. On 05/30/2014 11:21 AM, Robert Nelson wrote: On Fri, May 30, 2014 at 11:15 AM, David Lambert d...@lambsys.com wrote: I just compiled RCN kernel 3.15.0-rc5-bone0.1. All seemed to work well until I realized I could not access any USB devices; 'lsusb' gives the message: unable to initialize libusb: -99 Anyone have any suggestions, or is my adoption of 3.15 premature? Hi Dave, There were usb bugs initially due changes in the dts files during v3.15-rcX's development, but usb should work with the 3.15-rc7-bone1 tag.. I know my builders are still on rc6, (takes a few days to migrate).. http://rcn-ee.homeip.net:81/dl/farm/gcc/archive/20140528-23:21-git379770f-gcc-4_9-branch-am335x-boneblack-512mb-1/dmesg-gcc-4_9-branch-3.15.0-rc6-bone1.log Regards, -- 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] RCN kernel USB question on 3.15.0-rc5-bone0.1
On 05/31/2014 09:10 AM, Robert Nelson wrote: On Sat, May 31, 2014 at 8:35 AM, David Lambert d...@lambsys.com wrote: Thanks Robert, I built 3.15-rc7-bone1 (by editing version.sh in your scripts), but still get the same behavior. Any suggestions? Are the KERNEL_TAG, and BUILD variables all I need to edit? Oh you can edit version.sh, but also check the diff against the tag: https://github.com/RobertCNelson/bb-kernel/tree/3.15-rc7-bone1 Ouch my bad. I assumed that just changing the version would automagically fix all :-[ Regards, -- 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] RCN kernel USB question on 3.15.0-rc5-bone0.1
Robert, Excuse my ignorance, but what are the intended uses/audiences of: git://github.com/RobertCNelson/linux-dev.git and: https://github.com/RobertCNelson/bb-kernel.git Just curious? Regards, Dave. On 05/31/2014 11:49 AM, David Lambert wrote: On 05/31/2014 09:10 AM, Robert Nelson wrote: On Sat, May 31, 2014 at 8:35 AM, David Lambert d...@lambsys.com wrote: Thanks Robert, I built 3.15-rc7-bone1 (by editing version.sh in your scripts), but still get the same behavior. Any suggestions? Are the KERNEL_TAG, and BUILD variables all I need to edit? Oh you can edit version.sh, but also check the diff against the tag: https://github.com/RobertCNelson/bb-kernel/tree/3.15-rc7-bone1 Ouch my bad. I assumed that just changing the version would automagically fix all :-[ Regards, -- 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] RCN kernel USB question on 3.15.0-rc5-bone0.1
Robert,
I tried the following:
git clone https://github.com/RobertCNelson/bb-kernel.git
cd bb-kernel/
git checkout origin/am33x-v3.15 -b tmp
less version.sh
...snip...
#Kernel/Build
KERNEL_REL=3.15
KERNEL_TAG=${KERNEL_REL}-rc7
BUILD=bone1
...snip...
./build_kernel.sh
./tools/install_kernel.sh
Then on target:
root@trax-jdal:~# lsusb
unable to initialize libusb: -99
root@trax-jdal:~# uname -a
Linux trax-jdal 3.15.0-rc7-bone1 #1 Sat May 31 12:56:17 CDT 2014 armv7l
GNU/Linux
I am attaching a console screenlog. Any ideas?
Thanks for your attention.
Best regards,
Dave.
On 05/31/2014 11:49 AM, David Lambert wrote:
On 05/31/2014 09:10 AM, Robert Nelson wrote:
On Sat, May 31, 2014 at 8:35 AM, David Lambert d...@lambsys.com wrote:
Thanks Robert,
I built 3.15-rc7-bone1 (by editing version.sh in your
scripts), but
still get the same behavior. Any suggestions? Are the KERNEL_TAG,
and BUILD
variables all I need to edit?
Oh you can edit version.sh, but also check the diff against the tag:
https://github.com/RobertCNelson/bb-kernel/tree/3.15-rc7-bone1
Ouch my bad. I assumed that just changing the version would
automagically fix all :-[
Regards,
--
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.
Starting kernel ...
[0.00] Booting Linux on physical CPU 0x0
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.15.0-rc7-bone1 (dlambert@development) (gcc
version 4.8.3 20140401 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2014.04 -
Linaro GCC 4.8-2014.04) ) #1 Sat May 31 12:56:17 CDT 2014
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instruction cache
[0.00] Machine model: TI AM335x BeagleBone
[0.00] Memory policy: Data cache writeback
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.0 (sgx neon )
[0.00] Built 1 zonelists in Zone order, mobility grouping on. Total
pages: 129792
[0.00] Kernel command line: console=ttyO0,115200n8 init=/bin/systemd
VIDEO_DISPLAY root=/dev/mmcblk0p5 ro rootfstype=ext4 rootwait fixrtc
[0.00] PID hash table entries: 2048 (order: 1, 8192 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] allocated 1048576 bytes of page_cgroup
[0.00] please try 'cgroup_disable=memory' option if you don't want
memory cgroups
[0.00] Memory: 504376K/523264K available (5676K kernel code, 593K
rwdata, 3132K rodata, 304K init, 979K bss, 1K reserved, 0K highmem)
[0.00] Virtual kernel memory layout:
[0.00] vector : 0x - 0x1000 ( 4 kB)
[0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB)
[0.00] vmalloc : 0xe080 - 0xff00 ( 488 MB)
[0.00] lowmem : 0xc000 - 0xe000 ( 512 MB)
[0.00] pkmap : 0xbfe0 - 0xc000 ( 2 MB)
[0.00] modules : 0xbf80 - 0xbfe0 ( 6 MB)
[0.00] .text : 0xc0008000 - 0xc08a24bc (8810 kB)
[0.00] .init : 0xc08a3000 - 0xc08ef210 ( 305 kB)
[0.00] .data : 0xc08f - 0xc0984468 ( 594 kB)
[0.00].bss : 0xc0984468 - 0xc0a7920c ( 980 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] IRQ: Found an INTC at 0xfa20 (revision 5.0) with 128
interrupts
[0.00] Total of 128 interrupts on 1 active controller
[0.00] OMAP clockevent source: timer2 at 2400 Hz
[0.10] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every
178956969942ns
[0.25] OMAP clocksource: timer1 at 2400 Hz
[0.000174] Console: colour dummy device 80x30
[0.000195] Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736)
[0.089578] pid_max: default: 32768 minimum: 301
[0.089638] Security Framework initialized
[0.089708] AppArmor: AppArmor disabled by boot time parameter
[0.089716] Yama: becoming mindful.
[0.089878] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.089887] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.090369] Initializing cgroup subsys memory
[0.090393] Initializing cgroup subsys devices
[0.090401] Initializing cgroup subsys freezer
[0.090409] Initializing cgroup subsys net_cls
[0.090415] Initializing cgroup subsys blkio
[0.090422] Initializing cgroup
Re: [beagleboard] Re: /dev/mmcblk0p2 does not exist
Just a wild guess, it may be a device tree issue. Try looking at the initial boot before zImage, for example: Loaded environment from uEnv.txt Importing environment from mmc ... using: am335x-boneblack-cape-bone-argus.dtb... Checking if uenvcmd is set ... gpio: pin 56 (gpio 56) value is 1 Running uenvcmd ... reading zImage This is from my system so the line in red should be different on your system. HTH, Dave. On 05/31/2014 04:02 PM, Nikos wrote: OK, fiddled a bit with the relevant kernel configuration options, and seems I have stepped forward. I now have an operational root filesystem and several devices, but I cannot see my i2c devices (e.g. eeprom) or USB devices (although I have no dmesg errors about the bringing up of the USB subsystem). Could anyone suggest what information I would need to provide to get some help on this? Thanks -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] RCN kernel USB question on 3.15.0-rc5-bone0.1
I just compiled RCN kernel 3.15.0-rc5-bone0.1. All seemed to work well until I realized I could not access any USB devices; 'lsusb' gives the message: unable to initialize libusb: -99 Anyone have any suggestions, or is my adoption of 3.15 premature? Regards, Dave. -- 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] Custom Beaglbone Black from Circuitco
Well said Gerald! The BBB is so much more than just a reference design. It has been instantiated at a very low cost. I get sick when I hear of so much crap being thrown at the team, just because its huge success has caused some supply issues. Rant over. Dave. On 05/29/2014 08:00 AM, Gerald Coley wrote: I gave you the design for free. All the schematics, CAD files, and BOM. You are free to build it yourself at any place you want. There is no NRE charge. No license. Sorry that I can't be your personal engineering and manufacturing operation. Gerald On Thu, May 29, 2014 at 7:50 AM, Eric Fort eric.f...@gmail.com mailto:eric.f...@gmail.com wrote: Hey, wait! Gerald does not suck! Gerald, and the entire beagleboard team are awesome and totally rock! We as a community probably give Gerald the most workload and highest amount of stress though. Yes, we have been given a great foundation in beagle on which to build. If you need something substantially more custom you've got much of the work already completed, and any rework and redesign not only is your own but really ought be contributed back to the community as well (if you do a derivitive work of the board rather than a clean sheet) Eric On Thu, May 29, 2014 at 4:38 AM, David Farning dfarn...@gmail.com mailto:dfarn...@gmail.com wrote: I agree completely. With the understanding that there are shops which can do small custom orders at reasonable prices, the conversation shifts from BeagleBoard.orc / Circuit Co / Gerald sucks for not meeting my specific needs... to how can I build on the foundation that BeagleBoard.org et. al have laid to needs. David On Wed, May 28, 2014 at 11:58 PM, Eric Fort eric.f...@gmail.com mailto:eric.f...@gmail.com wrote: While CircuitCo incurs some risk in expanding production capacity on a board that anyone can step in and manufacture a clone of, and Embedest *is* making a clone of as a second source I will still hold out when purchasing beagleboard products for those sourced from CircuitCo as their quality has always been consistant and of the highest degree and their servive has been excellent. So long as others make the same observation that does help lessen some of the risk. As far as getting circa 100 boards made, I know there are shops that will do single quantities and with that the case a quantity of 100 is not unreasonable, just gotta shop around a bit. I may know a few places to get you going so if interested, pm me. then again at a qty of 100 http://www.digikey.com/product-detail/en/BB-BBLK-100/BB-BBLK-100-REVC-ND/4842545 may be an option. On Wed, May 28, 2014 at 6:19 PM, David Farning dfarn...@gmail.com mailto:dfarn...@gmail.com wrote: Some shops are really good at churning out small (100 to 10,000 units) runs of a product. They have perfected the art of retooling the line. In the current situation, it appears that our beaglebone friends are in the process of convincing the money people to make the investment to increase manufacturing capacity. The new equipment required to increase capacity costs serious money. When one considers that the BBB is open and anyone can step in and manufacture a clone and bypass then RD costs TI and Circuit Co have already invested, the risks start getting pretty high. What might seemed antagonizing slow to us on the outside, requires serious thought and planing on the inside. It can be challenging to communicate this when companies work as part of communities. On Wed, May 28, 2014 at 6:32 PM, William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com wrote: Gerald, I am just curious. Hypothetically speaking, what would it take to retool to make a custom board ? I am not looking for an IN or anything I am just curious. I'm thinking it would be a huge hassle to say the least. I've never worked in a PCB fab before, but worked for a CNC shop many moons ago, and retooling for even the most basic part ( door lock keyways ), would take a full day or two just for the setup, and a week or slightly longer to shake out the bugs. Meanwhile, the company is losing money until things are running smoothly again. On Wed, May 28, 2014 at 1:42 PM, Gerald Coley ger...@beagleboard.org mailto:ger...@beagleboard.org wrote: 100 boards is not a lot of boards. Especially when you have distributors screaming for 50,000 boards to fill their large POs.. Gerald On Wed, May 28, 2014 at 3:38 PM, sixvolts drewko...@gmail.com mailto:drewko...@gmail.com wrote: There are plenty of things that get
Re: [beagleboard] Re: Interconnecting two Beagle Bone Blacks
On 05/22/2014 11:50 PM, foreverska wrote: I'm not 100% that the driver for that exists in ArmHF. What's dmesg say after you plug it in? At any rate why not a crossover cable? or through your home router? Or a cheap switch, such as: http://www.amazon.com/TP-LINK-TL-SF1005D-5-port-100Mbps-Desktop/dp/B000FNFSPY/ref=sr_1_1?s=pcie=UTF8qid=1400852081sr=1-1keywords=ethernet+switch On Thursday, May 22, 2014 7:38:09 AM UTC-5, Rasmus Prentow wrote: Hi I'm trying to connect two beagle bones, such that they can communicate using TCP. My first attempt is to use the USB cable by plugin the USB-cable into USB port one one machine and the MicroUSB port on the other. The machine with the main USB port does not add the interface for the USB as it normally would on any other linux machine. Here is the ifconfig root@beaglebone:~# ifconfig eth0 Link encap:Ethernet HWaddr 1c:ba:8c:a7:ac:26 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:40 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:63312 errors:0 dropped:0 overruns:0 frame:0 TX packets:63312 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5546794 (5.2 MiB) TX bytes:5546794 (5.2 MiB) usb0 Link encap:Ethernet HWaddr 96:9f:43:e9:77:c6 inet addr:192.168.7.2 Bcast:192.168.7.3 Mask:255.255.255.252 inet6 addr: fe80::949f:43ff:fee9:77c6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7244 errors:0 dropped:0 overruns:0 frame:0 TX packets:6820 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:377882 (369.0 KiB) TX bytes:906342 (885.0 KiB) I run debian on both BBBs. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] BBB UVC/DMA crash kernel 3.13.6-bone7.1
Robert, I just tried your 3.14.4-bone4 kernel. Thanks for including my Argus UPS cape patches:-) . It appears that the UVC DMA is getting better, but I am getting the following warning messages when I issue any UVC controls. The good news is that the system still continues to work fine apart from these messages. Close, but no cigar :-\ Please pass on words of encouragement to the developers responsible for this. Regards, Dave. On 03/14/2014 11:20 AM, Robert Nelson wrote: On Fri, Mar 14, 2014 at 11:14 AM, David Lambert d...@lambsys.com wrote: The USB DMA still appears to have problems when used with USB cameras. It appears that whenever I attempt to issue controls via UVC to a camera that is capturing, then I get the attached crash. PIO mode works fine. Could I suggest that the default defconfig selects PIO mode until DMA mode works reliably? I hope this is the right place to post. If not, please excuse my intrusion, and suggest another. Done: https://github.com/RobertCNelson/linux-dev/commit/182589d51ae7ecc82c1ba9ef2b6440edf2d9 I don't see it getting completely fixed anytime soon either Regards, uname -a Linux trax-jdal 3.14.4-bone4 #1 SMP Mon May 19 15:25:52 CDT 2014 armv7l GNU/Linux root@trax-jdal:~# [ 238.501234] [ cut here ] [ 238.506128] WARNING: CPU: 0 PID: 498 at drivers/dma/cppi41.c:605 cppi41_dma_control+0x2a0/0x2f0() [ 238.515429] Modules linked in: rtc_ds1307 snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi uvcvideo snd_seq_device snd_pcm videobuf2_vmalloc snd_timer videobuf2_memops snd videobuf2_core soundcore ftdi_sio usbserial omap_aes omap_sham rtc_omap uio_pdrv_genirq uio loop [ 238.540705] CPU: 0 PID: 498 Comm: python Tainted: GW 3.14.4-bone4 #1 [ 238.548403] [c0015218] (unwind_backtrace) from [c0011bbc] (show_stack+0x10/0x14) [ 238.556539] [c0011bbc] (show_stack) from [c06c8788] (dump_stack+0x80/0x90) [ 238.564121] [c06c8788] (dump_stack) from [c003f014] (warn_slowpath_common+0x70/0x8c) [ 238.572607] [c003f014] (warn_slowpath_common) from [c003f0cc] (warn_slowpath_null+0x1c/0x24) [ 238.581822] [c003f0cc] (warn_slowpath_null) from [c03bc900] (cppi41_dma_control+0x2a0/0x2f0) [ 238.591051] [c03bc900] (cppi41_dma_control) from [c04dfa78] (cppi41_dma_channel_abort+0xc8/0x13c) [ 238.600723] [c04dfa78] (cppi41_dma_channel_abort) from [c04db2a8] (musb_cleanup_urb.isra.12+0x40/0x10c) [ 238.610942] [c04db2a8] (musb_cleanup_urb.isra.12) from [c04db5b4] (musb_urb_dequeue+0xe8/0x128) [ 238.620440] [c04db5b4] (musb_urb_dequeue) from [c04c0bd0] (usb_hcd_unlink_urb+0x4c/0x84) [ 238.629292] [c04c0bd0] (usb_hcd_unlink_urb) from [c04c1d74] (usb_kill_urb+0x50/0xcc) [ 238.637818] [c04c1d74] (usb_kill_urb) from [bf0b8c08] (uvc_uninit_video+0x34/0x60 [uvcvideo]) [ 238.647147] [bf0b8c08] (uvc_uninit_video [uvcvideo]) from [bf0baff0] (uvc_video_enable+0x18/0x168 [uvcvideo]) [ 238.657926] [bf0baff0] (uvc_video_enable [uvcvideo]) from [bf0b7fbc] (uvc_v4l2_do_ioctl+0x5b8/0x1180 [uvcvideo]) [ 238.668979] [bf0b7fbc] (uvc_v4l2_do_ioctl [uvcvideo]) from [c0517560] (video_usercopy+0x194/0x53c) [ 238.678742] [c0517560] (video_usercopy) from [c0513344] (v4l2_ioctl+0x114/0x13c) [ 238.686872] [c0513344] (v4l2_ioctl) from [c0156d60] (do_vfs_ioctl+0x400/0x5c4) [ 238.694813] [c0156d60] (do_vfs_ioctl) from [c0156f90] (SyS_ioctl+0x6c/0x7c) [ 238.702484] [c0156f90] (SyS_ioctl) from [c000e1a0] (ret_fast_syscall+0x0/0x30) [ 238.710420] ---[ end trace 4b907c08f9a1b69e ]--- [ 238.715257] [ cut here ] [ 238.720099] WARNING: CPU: 0 PID: 498 at drivers/dma/cppi41.c:629 cppi41_dma_control+0x28c/0x2f0() [ 238.729397] Modules linked in: rtc_ds1307 snd_usb_audio snd_usbmidi_lib snd_hwdep snd_rawmidi uvcvideo snd_seq_device snd_pcm videobuf2_vmalloc snd_timer videobuf2_memops snd videobuf2_core soundcore ftdi_sio usbserial omap_aes omap_sham rtc_omap uio_pdrv_genirq uio loop [ 238.754654] CPU: 0 PID: 498 Comm: python Tainted: GW 3.14.4-bone4 #1 [ 238.762324] [c0015218] (unwind_backtrace) from [c0011bbc] (show_stack+0x10/0x14) [ 238.770448] [c0011bbc] (show_stack) from [c06c8788] (dump_stack+0x80/0x90) [ 238.778024] [c06c8788] (dump_stack) from [c003f014] (warn_slowpath_common+0x70/0x8c) [ 238.786509] [c003f014] (warn_slowpath_common) from [c003f0cc] (warn_slowpath_null+0x1c/0x24) [ 238.795722] [c003f0cc] (warn_slowpath_null) from [c03bc8ec] (cppi41_dma_control+0x28c/0x2f0) [ 238.804939] [c03bc8ec] (cppi41_dma_control) from [c04dfa78] (cppi41_dma_channel_abort+0xc8/0x13c) [ 238.814611] [c04dfa78] (cppi41_dma_channel_abort) from [c04db2a8] (musb_cleanup_urb.isra.12+0x40/0x10c) [ 238.824829] [c04db2a8] (musb_cleanup_urb.isra.12) from [c04db5b4] (musb_urb_dequeue+0xe8/0x128) [ 238.834317] [c04db5b4] (musb_urb_dequeue) from [c04c0bd0] (usb_hcd_unlink_urb+0x4c/0x84) [ 238.843169] [c04c0bd0] (usb_hcd_unlink_urb) from [c04c1d74] (usb_kill_urb+0x50/0xcc) [ 238.851664
Re: [beagleboard] debian and networking
On 04/30/2014 10:21 AM, Robert Nelson wrote: On Apr 30, 2014 8:16 AM, Charles Steinkuehler char...@steinkuehler.net mailto:char...@steinkuehler.net wrote: On 4/30/2014 10:04 AM, Jerry Davis wrote: $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.7.0 0.0.0.0 255.255.255.252 U 0 0 0 usb0 You have no default route. Try running: ip route add default via 192.168.7.1 dev usb0 This would be setup by the usb0 entry in /etc/network/interfaces, but I think Robert changed the underlying network configuration in order to improve the boot speed. You probably have to edit a wicd config file or something...I don't use the USB port so I'm not sure. The usb0 didn't change, it was statically defined so it didn't mess with Boot times. eth0 on the other hand, with dhcp enabled it delayed everything. Although I just switched eth0 to allow-hotplug vs auto. Which fixed the main delay, but wicd was still a few seconds faster. Doesn't changing eth0 from auto to allow-hotplug, mean that rebooting with the cable plugged in will not automatically connect on eth0? -- Charles Steinkuehler char...@steinkuehler.net mailto:char...@steinkuehler.net -- 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 mailto:beagleboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] debian and networking
On 04/30/2014 11:44 AM, Robert Nelson wrote: The usb0 didn't change, it was statically defined so it didn't mess with Boot times. eth0 on the other hand, with dhcp enabled it delayed everything. Although I just switched eth0 to allow-hotplug vs auto. Which fixed the main delay, but wicd was still a few seconds faster. Doesn't changing eth0 from auto to allow-hotplug, mean that rebooting with the cable plugged in will not automatically connect on eth0? I haven't seen that happen yet. The biggest thing, serial console doesn't wait for an ip from dhcp. (This was only for Debian) I just tried it (on Debian). For me if I don't have auto eth0 in my /etc/network/interfaces, then eth0 does not activate until I manually do ifup eth0 explicitly. Also plugging/unplugging eth0 cable is ignored until I manually activate the interface. I am using your netinstall with kernel 3.13.10-bone9. Puzzled? Cheers, Dave. -- 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] Installing GNUPlot on BeagleboneBlack
On 04/24/2014 08:08 AM, Aswin wrote: Thanks, I didn't know that. Is there a version of GNUPlot or any data plotting software written for ARM architecture? Yes - on Debian BBB, apt-cache search returns: apt-cache search gnuplot amanda-client - Advanced Maryland Automatic Network Disk Archiver (Client) amanda-server - Advanced Maryland Automatic Network Disk Archiver (Server) bonnie++ - Hard drive benchmark suite. cdck - tool for verifying the quality of written CDs/DVDs chiark-scripts - chiark system administration scripts circos - plotter for visualizing data collectl - Utility to collect Linux performance data ctioga2 - polymorphic plotting program devscripts - scripts to make the life of a Debian Package maintainer easier gausssum - parse and display Gaussian, GAMESS, and etc's output gnuplot - Command-line driven interactive plotting program gnuplot-doc - Command-line driven interactive plotting program. Doc-package gnuplot-nox - Command-line driven interactive plotting program. No-X package gnuplot-qt - Command-line driven interactive plotting program. QT-package gnuplot-x11 - Command-line driven interactive plotting program. X-package gnuplot-mode - Yet another Gnuplot mode for Emacs jed-extra - collection of useful Jed modes and utilities libchart-gnuplot-perl - module for generating two- and three-dimensional plots libfinance-bank-ie-permanenttsb-perl - perl interface to the PermanentTSB Open24 homebanking libgraphics-gnuplotif-perl - dynamic Perl interface to gnuplot mathomatic - portable Computer Algebra System (CAS) libgnuplot-ocaml-dev - OCaml interface to the gnuplot utility plotdrop - A minimal GNOME frontend to GNUPlot libploticus0 - script driven business graphics library libploticus0-dev - Development files for the ploticus library ploticus - script driven business graphics package octave-plplot - Octave support for PLplot, a plotting library probcons-extra - Extra programs from the probcons package pstoedit - PostScript and PDF files to editable vector graphics converter python-gnuplot - A Python interface to the gnuplot plotting program pyxplot - data plotting program producing publication-quality output pyxplot-doc - documentation for pyxplot data plotting program rlplot - GUI application for generating publication quality graphs libgnuplot-ruby - Transitional package for ruby-gnuplot libgnuplot-ruby1.8 - Transitional package for ruby-gnuplot ruby-gnuplot - Ruby library to interact with gnuplot scidavis - application for scientific data analysis and visualization python-scitools - Python library for scientific computing stda - simple tools for data analysis (stda) tcptrace - Tool for analyzing tcpdump output texlive-pictures - TeX Live: Graphics packages and programs texlive-latex-extra - TeX Live: LaTeX supplementary packages On Thursday, April 24, 2014 5:55:50 PM UTC+5:30, RobertCNelson wrote: On Thu, Apr 24, 2014 at 6:43 AM, Aswin asp...@gmail.com javascript: wrote: Hi, Can you guide me how to install GNUPlot on BBB? I'm running Angstrom (2013.09.04). This is the error I got: root@beaglebone:/etc# opkg install http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/gnuplot_4.6.0-2_ar71xx.ipk http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/gnuplot_4.6.0-2_ar71xx.ipk Downloading http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/gnuplot_4.6.0-2_ar71xx.ipk http://downloads.openwrt.org/snapshots/trunk/ar71xx/packages/gnuplot_4.6.0-2_ar71xx.ipk. Unknown package 'gnuplot'. Collected errors: * pkg_hash_fetch_best_installation_candidate: Packages for gnuplot found, but incompatible with the architectures configured ar71xx is a MIPS architecture, so that's the error you'd expect to see on an ARM architecture. Regards, -- Robert Nelson http://www.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+unsubscr...@googlegroups.com mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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: What OS to use?
On 04/22/2014 07:15 PM, William Hermans wrote: Actually, the best is the one you want to use most. So, in other words, you're asking a subjective question. The kernel between Ubuntu and Debian is the same, the only difference is the rootfs, where Ubuntu uses upstart, while Debian uses a more traditional init.d init daemon. If you do not have much hands on with either, then either would probably work fine for you. My own personal preference is Debian, because I have had years of hands on with it. Also with Debian, you can use systemd. Just add the option to uEnv.txt as follows: #Optional arguments optargs=init=/bin/systemd On Tue, Apr 22, 2014 at 5:09 PM, rh_ richard_hubb...@lavabit.com mailto:richard_hubb...@lavabit.com wrote: You'll have to define best better. On Tue, 22 Apr 2014 16:49:31 -0700 Jerry Davis jdaw...@gmail.com mailto:jdaw...@gmail.com wrote: Just got my B^3 and have heard that Angstrom is not a very good OS. I will be using it for projects (I2C, A/D, and GPIO), with Adafruit's GPIO python module. Which one is the best? Ubuntu, Debian, other? Jerry -- Extra Ham Operator: K7AZJ Registered Linux User: 275424 Raspberry Pi and Arduino developer There are 10 kinds of people in the world: Those who can read binary and those who can't. -- 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 mailto:unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -- 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 mailto:beagleboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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: What OS to use?
IMHO for me, the best compromise between stability and some UI friendliness is CruchBang http://crunchbang.org/ On 04/22/2014 11:34 PM, John Syn wrote: From: William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Date: Tuesday, April 22, 2014 at 8:44 PM To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: What OS to use? Very little John, but know that MINT has two inner distro's You have regular which is based on Ubuntu, and LMDE which is Linux Mint Debian Edition( testing branch). I tried LMDE and was not impressed. Debian IMHO isn't meant as a desktop OS, although some people use it as such and it works very well for them. For me Debian is perfect for how I personally think the BBB *should* be used. Which is to say, not a desktop replacement. Thanks William. Ubuntu would be perfect for me if they only dropped Unity. I hate Unity, but I haven't found anything that works better. At the moment, I'm using a tool that is based on QT and it crashes when I use the file dialog (open, save, etc). It doesn't crash every time, but more often than not. Apparently this is a known issue with QT and Ubuntu. The vendor was able to reproduce the error, but when they loaded QT debug symbols, they cannot reproduce the error. I loaded QT debug symbols and it still crashes for me. What a nightmare. The vendor says the tools is stable in Debian so that was my I was looking at Debian. Regards, John On Tue, Apr 22, 2014 at 8:36 PM, John Syn john3...@gmail.com mailto:john3...@gmail.com wrote: From: William Hermans yyrk...@gmail.com mailto:yyrk...@gmail.com Reply-To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Date: Tuesday, April 22, 2014 at 7:32 PM To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Subject: Re: [beagleboard] Re: What OS to use? To be sure, there is more than what little i mentioned. In the PC world Ubuntu is known as the user friendly Debian based distro, where Debian is light weight, known to be super solid and preferred for servers / mission critical applications. However in the case of the BBB I think the differences are considerably blurred by comparison. Since we're not very likely to run Compiz for a beautiful desktop on our BBB's, and numerous other points. I've always used Ubuntu for my Desktop and over the last few releases, Ubuntu has become more flaky so I had heard that Debian is rock solid as you said. I started out with Debian Wheezy 7.4 and noticed that the kernel was still at V3.2 which seems really old. What I also noticed is the Debian package manager isn't as comprehensive as Ubuntu and I have to track down tons of third party repos to get the packages I needed. I also had issues with the nouveau driver for my Nvidia 670 card so I installed the Nvidia native driver and that seemed to work better. From what I've read, the Debian Testing repo is also very reliable (better than Ubuntu) so I updated and now the kernel is v3.13. BTW, I found Gnome on Debian to be flaky (both on Wheezy and Sid). For example, updating the desktop background causes a segfault. This is a known issue and there are several suggesting workarounds, but no fixes yet. Maybe I'm missing something here. Debian is my preferred solution for BBB, but for now I think I'm going to stick with flaky Ubuntu for my Desktop. Anyone have any experience with MINT? Regards, John On Tue, Apr 22, 2014 at 7:02 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: On 04/22/2014 07:15 PM, William Hermans wrote: Actually, the best is the one you want to use most. So, in other words, you're asking a subjective question. The kernel between Ubuntu and Debian is the same, the only difference is the rootfs, where Ubuntu uses upstart, while Debian uses a more traditional init.d init daemon. If you do not have much hands on with either, then either would probably work fine for you. My own personal preference is Debian, because I have had years of hands on with it. Also with Debian, you can use systemd. Just add the option to uEnv.txt as follows: #Optional arguments optargs=init=/bin/systemd On Tue, Apr 22, 2014 at 5:09 PM, rh_ richard_hubb...@lavabit.com
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-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, Robert Nelson wrote: On Wed, Mar 19, 2014 at 2:47 PM, bko...@scanimetrics.com mailto:bko...@scanimetrics.com wrote: Does anyone happen to know if the 3.8 kernel compiled as per these instructions here http://eewiki.net/display/linuxonarm/BeagleBone+Black 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. Sorry, the fix is too generic of a term, therefore I can neither confirm nor deny it. Either way, that 3.8 branch listed is the one currently used in all debian/ubuntu images being shipped. Regards, -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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: BBB GLIBC6 version issue
On 04/15/2014 08:03 AM, A P wrote: OK still no progress with Angstrom, but I thought I would give the new Debian image for SD card a try. This is miles easier to use than the previous - USB works out of the box :) . However the libc6 library was 2.13 after updating etc, however I stumbled across the following bash script |#!/bin/sh echo deb http://ftp.debian.org/debian sid main /etc/apt/sources.list apt-get update apt-get -t sid install libc6 libc6-dev libc6-dbg echo Please remember to hash out sid main from your sources list. /etc/apt/sources.list| Which installed a test version of 2.18 This worked fine. Now I just have to get the other bits I had working, working again on this image, oh and speed up the boot time significantly. If you add the following to your /boot/uBoot/uEnv.txt, you will use systemd as the init process. This will speed up boot time significantly. #Optional arguments optargs=init=/bin/systemd -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] AIN max voltage exceeded
On 04/10/2014 07:57 AM, Gerald Coley wrote: Does it go to 220V? I mean if it is to be found people will try to connect it! LOL - nor to mention xxKv of static, etc! Gerald On Thu, Apr 10, 2014 at 1:38 AM, Bas Laarhoven s...@xs4all.nl mailto:s...@xs4all.nl wrote: On 10-4-2014 2:03, Padawan wrote: Sounds like someone needs to make a surge protector cape for people like us... I'd buy that. My current Zener diode monstrosity design isn't particularly effective. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. With the current shortage and future price increase, it may be worth investing in BeagleBone protection again ;-) This 'surge protector' cape you mention already exists! Shameless plug: Have a look at the BeBoPr series of boards and the current BeBoPr++. The analogue inputs are designed to handle shorts against a 12 Volt supply. Besides the over voltage protection you also get an extra (better) ADC, protected digital inputs, both TTL and high current outputs, a 12-24 Volt to 5 Volt step down converter, I2C level shifter, etc. Oh, and you can also use it to control some stepper motors, e.g. to build a 3D printer, or a laser cutter, or a router, or something I haven't thought of yet. There's a picture and manual available for download via this link: https://github.com/modmaker/BeBoPr-plus-plus. -- Bas -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Cyclic kernel crash on BBB RCN kernel 3.13.6-bone8
The following crash happens on occasions when I attempt to alter eth0 status. The only way out seems to be reboot. Has anyone else experience this, any ideas? Regards, Dave. ifdown eth0 Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/c8:a0:30:af:93:56 Sending on LPF/eth0/c8:a0:30:af:93:56 Sending on Socket/fallback DHCPRELEASE on eth0 to 192.168.1.1 port 67 send_packet: Network is unreachable send_packet: please consult README file regarding broadcast address. [ 306.733018] [ cut here ] [ 306.737912] WARNING: CPU: 0 PID: 1385 at drivers/net/ethernet/ti/cpsw.c:633 cpsw_rx_handler+0x10c/0x138() [ 306.747930] Modules linked in: rtc_ds1307 ftdi_sio snd_usb_audio snd_hwdep snd_usbmidi_lib uvcvideo snd_rawmidi videobuf2_vmalloc snd_seq_device videobuf2_memops videobuf2_core usbserial rtc_omap uio_pdrv_genirq uio loop [ 306.768510] CPU: 0 PID: 1385 Comm: ip Tainted: GW 3.13.6-bone8 #1 [ 306.775929] [c001415c] (unwind_backtrace+0x0/0xdc) from [c0010ef8] (show_stack+0x10/0x14) [ 306.784866] [c0010ef8] (show_stack+0x10/0x14) from [c06fe55c] (dump_stack+0x70/0x8c) [ 306.793349] [c06fe55c] (dump_stack+0x70/0x8c) from [c0039a28] (warn_slowpath_common+0x64/0x88) [ 306.802736] [c0039a28] (warn_slowpath_common+0x64/0x88) from [c0039adc] (warn_slowpath_null+0x18/0x20) [ 306.812853] [c0039adc] (warn_slowpath_null+0x18/0x20) from [c04ef904] (cpsw_rx_handler+0x10c/0x138) [ 306.822698] [c04ef904] (cpsw_rx_handler+0x10c/0x138) from [c04edbbc] (__cpdma_chan_process+0x110/0x128) [ 306.832905] [c04edbbc] (__cpdma_chan_process+0x110/0x128) from [c04edcf0] (cpdma_chan_stop+0xd0/0x16c) [ 306.843018] [c04edcf0] (cpdma_chan_stop+0xd0/0x16c) from [c04edde4] (cpdma_ctlr_stop+0x58/0xa8) [ 306.852498] [c04edde4] (cpdma_ctlr_stop+0x58/0xa8) from [c04f1a44] (cpsw_ndo_stop+0xc8/0x178) [ 306.861808] [c04f1a44] (cpsw_ndo_stop+0xc8/0x178) from [c06080ec] (__dev_close_many+0x94/0xb8) [ 306.871198] [c06080ec] (__dev_close_many+0x94/0xb8) from [c060814c] (__dev_close+0x3c/0x74) [ 306.880316] [c060814c] (__dev_close+0x3c/0x74) from [c060e49c] (__dev_change_flags+0x8c/0x140) [ 306.889704] [c060e49c] (__dev_change_flags+0x8c/0x140) from [c060e568] (dev_change_flags+0x18/0x48) [ 306.899548] [c060e568] (dev_change_flags+0x18/0x48) from [c061a448] (do_setlink+0x2b8/0x784) [ 306.908755] [c061a448] (do_setlink+0x2b8/0x784) from [c061b470] (rtnl_newlink+0x250/0x460) [ 306.91] [c061b470] (rtnl_newlink+0x250/0x460) from [c061b81c] (rtnetlink_rcv_msg+0x19c/0x1b0) [ 306.927439] [c061b81c] (rtnetlink_rcv_msg+0x19c/0x1b0) from [c06314b0] (netlink_rcv_skb+0x58/0xac) [ 306.937189] [c06314b0] (netlink_rcv_skb+0x58/0xac) from [c061a04c] (rtnetlink_rcv+0x18/0x24) [ 306.946394] [c061a04c] (rtnetlink_rcv+0x18/0x24) from [c0630b84] (netlink_unicast+0xac/0x18c) [ 306.955689] [c0630b84] (netlink_unicast+0xac/0x18c) from [c06312e0] (netlink_sendmsg+0x5e0/0x65c) [ 306.965352] [c06312e0] (netlink_sendmsg+0x5e0/0x65c) from [c05f67b0] (sock_sendmsg+0x88/0xa4) [ 306.974651] [c05f67b0] (sock_sendmsg+0x88/0xa4) from [c05f7a0c] (___sys_sendmsg.part.11+0x17c/0x200) [ 306.984586] [c05f7a0c] (___sys_sendmsg.part.11+0x17c/0x200) from [c05f88c0] (__sys_sendmsg+0x4c/0x70) [ 306.994611] [c05f88c0] (__sys_sendmsg+0x4c/0x70) from [c000d900] (ret_fast_syscall+0x0/0x30) [ 307.003811] ---[ end trace ecd16f73a44784d1 ]--- [ 307.009117] [ cut here ] [ 307.013973] WARNING: CPU: 0 PID: 1385 at drivers/net/ethernet/ti/cpsw.c:633 cpsw_rx_handler+0x10c/0x138() [ 307.023987] Modules linked in: rtc_ds1307 ftdi_sio snd_usb_audio snd_hwdep snd_usbmidi_lib uvcvideo snd_rawmidi videobuf2_vmalloc snd_seq_device videobuf2_memops videobuf2_core usbserial rtc_omap uio_pdrv_genirq uio loop [ 307.044551] CPU: 0 PID: 1385 Comm: ip Tainted: GW 3.13.6-bone8 #1 [ 307.051942] [c001415c] (unwind_backtrace+0x0/0xdc) from [c0010ef8] (show_stack+0x10/0x14) [ 307.060877] [c0010ef8] (show_stack+0x10/0x14) from [c06fe55c] (dump_stack+0x70/0x8c) [ 307.069354] [c06fe55c] (dump_stack+0x70/0x8c) from [c0039a28] (warn_slowpath_common+0x64/0x88) [ 307.078741] [c0039a28] (warn_slowpath_common+0x64/0x88) from [c0039adc] (warn_slowpath_null+0x18/0x20) [ 307.088857] [c0039adc] (warn_slowpath_null+0x18/0x20) from [c04ef904] (cpsw_rx_handler+0x10c/0x138) [ 307.098700] [c04ef904] (cpsw_rx_handler+0x10c/0x138) from [c04edbbc] (__cpdma_chan_process+0x110/0x128) [ 307.108906] [c04edbbc] (__cpdma_chan_process+0x110/0x128) from [c04edcf0] (cpdma_chan_stop+0xd0/0x16c) [ 307.119021] [c04edcf0] (cpdma_chan_stop+0xd0/0x16c) from [c04edde4] (cpdma_ctlr_stop+0x58/0xa8) [ 307.128501] [c04edde4] (cpdma_ctlr_stop+0x58/0xa8) from [c04f1a44] (cpsw_ndo_stop+0xc8/0x178) [ 307.137799] [c04f1a44] (cpsw_ndo_stop+0xc8/0x178) from [c06080ec]
Re: [beagleboard] Journalctl apparently does not save logs before last boot
http://www.freedesktop.org/software/systemd/man/journald.conf.html If you look in the section Storage you will find many options for persistence/volatility. On 03/28/2014 12:00 AM, kfree...@gmail.com wrote: I've noticed that journalctl does not show logs from before the last boot sequence. Is there a way to save these logs or to view them if they are already saved? -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] eMMC data corruption due to power removal?
I have had a long and painful history using flash in general, and have come to the conclusion that asynchronous removal of power is a very bad thing. The following link shows one low level phenomenon called unstable bits. This seems to be getting worse the more bits that are stuffed into a cell (pretty obvious) :-[ http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits Some other studies suggest that very high density chips may exhibit similar problems even when *_reading_* during a power fail! My conclusions lean to removing power only when ALL accesses to flash have completed. HTH, Dave. On 03/27/2014 04:10 PM, John Syn wrote: From: Brandon I brandon.ir...@gmail.com mailto:brandon.ir...@gmail.com Reply-To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Date: Wednesday, March 26, 2014 at 6:46 PM To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Subject: Re: [beagleboard] eMMC data corruption due to power removal? Here's a good read: http://www.embeddedarm.com/about/resource.php?item=459 I had a lng discussion about this with a colleague of mine after we started seeing boards die. Basically you're eventually doomed unless you mount the whole disk as read only since the wear leveling algorithms in the flash have no knowledge of what a partition is and will eventually end up with suppesed-to-be-read-only data mixed in with the writable partition erase blocks. If you're writing to flash, it will eventually fail by unfortunate design. It tooks his previous company 6 months of fighting to come to terms with this in their last product. They had to write data, so eventually used usb flash that the customer could easily replace when things eventually died. They tried every flash card they could get their hands on, read only partitions, etc and eventually had to give up. Use the SD card you say! Any micro SD card you can put in the slot is absolutely not meant for continuous writing. The SD card spec has a very specific use case in mind (video and images), and logging or using it as a sparse write file system goes completely against the intended SD card design specs. Industrial grade write-tolerant flash will cost you hundreds of dollars more than something on Amazon. With our current product, I told my boss that I was worried about corruption and that we would eventually go to read only once we debugged the boards. Within two weeks of only log messages, all of our boards started dyeing. The next day, all disks were mounted as read only and issues are debugged with the in-memory log files. We haven't seen any failures in 6 months now. The easy solution is trying to force the answer of why are you writing anything to persistent storage? to be there's no good reason since it eventually bricks our product. If you want something that will last forever, you will not write to standard flash media. If you can't, then maybe use a usb flash drive (MUCH better life than a micro sd card) and count the days until it corrupts or someone pulls the power at an inopportune time. You could always use a battery backup to get rid of the power off issue. :-\ This is all doom and gloom, but it's a consequence of inconsistent power, buffers, and the destruction nature of quantum tunneling. What you say is mostly correct. However, you can use supercaps based power supply which will enable you to store data stored in RAM to Non-Volatile storage such as SDCard or eMMC when a power fail is detected. Also, when Linux goes through an orderly shutdown, no corruption occurs. This way, you only write to flash during a power failure so you won't see any flash failures. The supercaps don't have a limited number of charge cycles which is common in Lithium Iron batteries so these systems should be good for 10 years or more. Plan for about 90 Seconds to write data to flash and Linux shutdown. Regards, John -Brandon On Wednesday, March 26, 2014 2:45:57 PM UTC-7, Sungjin Chun wrote: How about making system partition be mounted as read-only and data partition be mounted after booting and checking? In this case, only data partition has possibility of corruption. Sent from my iPad On Mar 26, 2014, at 9:53 PM, Yiling Cao yilin...@gmail.com javascript: wrote: Hi I have some my products deployed with am335x with Micron eMMC 2GB, but my products allow users to unplug power as they wish. My linux app very rarely writes to the eMMC. and my /etc/fstab specifies /var/log and /tmp to tempfs; fstab mount all partitions with noatime properties. But around 2 months of deployment, I found that around 1-2% am335x machines, have some sort of data corruption, resulting fail to boot
Re: [beagleboard] Re: eMMC data corruption due to power removal?
On 03/27/2014 07:04 PM, rh_ wrote: On Thu, 27 Mar 2014 16:25:29 -0500 David Lambert d...@lambsys.com wrote: I have had a long and painful history using flash in general, and have come to the conclusion that asynchronous removal of power is a asynchronous? Like pulling the plug and not pushing it? Yes. very bad thing. The following link shows one low level phenomenon called unstable bits. This seems to be getting worse the more bits that are stuffed into a cell (pretty obvious) :-[ low-level phenomenon? You mean a manufacturer defect? An inherent defect in the flash design? Implementation defect? All flash is inherently error prone. That's why long ECC codes are employed as recommended by the flash chip manufacturers Some other studies suggest that very high density chips may exhibit similar problems even when *_reading_* during a power fail! Ouch. My conclusions lean to removing power only when ALL accesses to flash have completed. What technologies were used to reach your conclusion? Filesystems, flash device, etc. From the mid 1990s. Everything from raw NAND, NOR flash chips with ASIC or software ECC controllers/wear leveling. USB/SD/CompactFlash. File systems UBIFS, XFS, Ext2/3/4, FAT, and some proprietary sequential only file systems with embedded EDC/ECC. Why is this technology wide spread if it's got an inherent flaw? Cheap, and with the right controllers, reliable. Wikipedia has a good basic introduction to the technology with some more authoritative citations. For greater depth some of the manufacturers' data sheets may be helpful. http://en.wikipedia.org/wiki/Flash_memory http://www.micron.com/products/nand-flash -- 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] Debian netinstall image - network interfaces file - eth0 not auto?
I just performed a fresh of Debian on BBB installation using git clone git://github.com/RobertCNelson/netinstall.git I notice that the /etc/network/interfaces file does not declare eth0 as auto by default. This means that restarting the networking service does not re-enable eth0. Is this intentional, and if so why? Just curious. Regards, Dave. -- 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] Debian netinstall image - network interfaces file - eth0 not auto?
On 03/24/2014 11:43 AM, Robert Nelson wrote: On Mon, Mar 24, 2014 at 11:37 AM, David Lambert d...@lambsys.com wrote: I just performed a fresh of Debian on BBB installation using git clone git://github.com/RobertCNelson/netinstall.git I notice that the /etc/network/interfaces file does not declare eth0 as auto by default. This means that restarting the networking service does not re-enable eth0. Is this intentional, and if so why? Currently the Netinstall script does not modify /etc/network/interfaces in any way. So that default setting is just the way the upstream Debian Developers set it in the debian-installer for all the architectures. Regards, Thanks for your confirmation Robert. That's what I had suspected. Regards, Dave. -- 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] Kernel/device tree road-map for the BBB
Robert, It appears that the GPIO label numbering scheme has been changed from the device tree overlay's 1 to n+1, to the more con-formant 0 to n; I fell into this trap :-[ . I will send you my consolidated patch directly, once I had time to check it out further. Sorry for the confusion. Regards, Dave. On 03/20/2014 12:33 PM, David Lambert wrote: Robert, It looks like I spoke too soon. Although my device tree appears to get loaded and my driver entry point is called with correct parameters, the pinmux does not appear to get set up correctly. Where do I look in 3.13 kernel based systems to debug the pinmux settings? Best regards, Dave. On 03/06/2014 03:11 PM, Robert Nelson wrote: On Thu, Mar 6, 2014 at 3:03 PM, David Lambert d...@lambsys.com wrote: Just a suggestion. If the dtb for the cape does not exist or is corrupted, could the device tree default to the base, for example am335x-boneblack.dtb? You read my mind, there is a new file test function, i'd like to backport to v2014.01 http://git.denx.de/?p=u-boot.git;a=commit;h=e5e897c01b1cd496187ca56a38ff5559d27f951c Then yes, we can set it to use the default *.dtb. Regards, -- 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] Kernel/device tree road-map for the BBB
Robert, It looks like I spoke too soon. Although my device tree appears to get loaded and my driver entry point is called with correct parameters, the pinmux does not appear to get set up correctly. Where do I look in 3.13 kernel based systems to debug the pinmux settings? Best regards, Dave. On 03/06/2014 03:11 PM, Robert Nelson wrote: On Thu, Mar 6, 2014 at 3:03 PM, David Lambert d...@lambsys.com wrote: Just a suggestion. If the dtb for the cape does not exist or is corrupted, could the device tree default to the base, for example am335x-boneblack.dtb? You read my mind, there is a new file test function, i'd like to backport to v2014.01 http://git.denx.de/?p=u-boot.git;a=commit;h=e5e897c01b1cd496187ca56a38ff5559d27f951c Then yes, we can set it to use the default *.dtb. Regards, -- 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] 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, bko...@scanimetrics.com 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 to fix this problem. Sorry, the fix is too generic of a term, therefore I can neither confirm nor deny it. Either way, that 3.8 branch listed is the one currently used in all debian/ubuntu images being shipped. Regards, -- 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] Ethernet interface failure
On 03/14/2014 06:44 PM, Mark Grosen wrote: Which kernel are you using? I've been running a BBB on Ethernet 24x7 using the Debian distro plus the 3.13 kernel with no networking issues for several weeks. I agree - the 3.13 kernel seems to have fixed the PHY problem. Mark Mark On Fri, Mar 14, 2014 at 9:12 AM, atomik...@gmail.com mailto:atomik...@gmail.com wrote: This is not an isolated instance. We have SEVERAL Beagles 10+ all bought at different times, and all showing the same issue. This is not one specific Beagle that needs to be RMA'd On Friday, March 14, 2014 11:33:48 AM UTC-4, Gerald wrote: So if the board never works again, have you sent it in for repair via an RMA? Gerald On Fri, Mar 14, 2014 at 10:28 AM, atom...@gmail.com wrote: The BeagleBone Black ethernet interface will fail after a few hours of operation. As an example, we did a fresh install of both Debian and Ubuntu on two Beagles (Newest updates for the Arm OS), connected them to the network and sure enough the next morning, both of the interfaces had failed. Several people have apparently noticed this issue, but I can't find any suggestions on possible fixes. It appears to potentially be a hardware or Kernel issue. Has anyone out there had any experience with this and discovered a fix? -- 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 https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] BBB UVC/DMA crash kernel 3.13.6-bone7.1
The USB DMA still appears to have problems when used with USB cameras. It appears that whenever I attempt to issue controls via UVC to a camera that is capturing, then I get the attached crash. PIO mode works fine. Could I suggest that the default defconfig selects PIO mode until DMA mode works reliably? I hope this is the right place to post. If not, please excuse my intrusion, and suggest another. Best regards, Dave. -- 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. root@argus-dev:~# [ 60.007731] [ cut here ] [ 60.012617] WARNING: CPU: 0 PID: 702 at drivers/dma/cppi41.c:605 cppi41_dma_control+0x230/0x2ac() [ 60.021920] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 nfsd deflate ctr des_generic cbc ecb cmac af_key xfrm_algo uvcvideo snd_usb_audio videobuf2_vmalloc videobuf2_memops snd_hwdep snd_usbmidi_lib videobuf2_core snd_rawmidi snd_seq_device ti_am335x_adc kfifo_buf industrialio rtc_omap uio_pdrv_genirq uio loop [ 60.053997] CPU: 0 PID: 702 Comm: python Not tainted 3.13.6-bone7.1 #2 [ 60.060878] [c001413c] (unwind_backtrace+0x0/0xdc) from [c0010ed8] (show_stack+0x10/0x14) [ 60.069817] [c0010ed8] (show_stack+0x10/0x14) from [c0700c00] (dump_stack+0x70/0x8c) [ 60.078298] [c0700c00] (dump_stack+0x70/0x8c) from [c0039a44] (warn_slowpath_common+0x64/0x88) [ 60.087685] [c0039a44] (warn_slowpath_common+0x64/0x88) from [c0039af8] (warn_slowpath_null+0x18/0x20) [ 60.097799] [c0039af8] (warn_slowpath_null+0x18/0x20) from [c040ea98] (cppi41_dma_control+0x230/0x2ac) [ 60.107925] [c040ea98] (cppi41_dma_control+0x230/0x2ac) from [c05170bc] (cppi41_dma_channel_abort+0x104/0x140) [ 60.118771] [c05170bc] (cppi41_dma_channel_abort+0x104/0x140) from [c0512828] (musb_cleanup_urb.isra.7+0x44/0xe4) [ 60.129887] [c0512828] (musb_cleanup_urb.isra.7+0x44/0xe4) from [c05129bc] (musb_urb_dequeue+0xf4/0x114) [ 60.140190] [c05129bc] (musb_urb_dequeue+0xf4/0x114) from [c04fafb0] (usb_hcd_unlink_urb+0x5c/0x7c) [ 60.150033] [c04fafb0] (usb_hcd_unlink_urb+0x5c/0x7c) from [c04fbd60] (usb_kill_urb+0x50/0xc4) [ 60.159462] [c04fbd60] (usb_kill_urb+0x50/0xc4) from [bf0994b8] (uvc_uninit_video+0x34/0x60 [uvcvideo]) [ 60.169706] [bf0994b8] (uvc_uninit_video+0x34/0x60 [uvcvideo]) from [bf09b538] (uvc_video_enable+0x18/0x124 [uvcvideo]) [ 60.181391] [bf09b538] (uvc_video_enable+0x18/0x124 [uvcvideo]) from [bf099160] (uvc_v4l2_do_ioctl+0xd20/0xff4 [uvcvideo]) [ 60.193343] [bf099160] (uvc_v4l2_do_ioctl+0xd20/0xff4 [uvcvideo]) from [c05499cc] (video_usercopy+0x2ac/0x3e8) [ 60.204200] [c05499cc] (video_usercopy+0x2ac/0x3e8) from [c05453b4] (v4l2_ioctl+0x60/0x124) [ 60.213319] [c05453b4] (v4l2_ioctl+0x60/0x124) from [c012ebbc] (do_vfs_ioctl+0x4c8/0x588) [ 60.52] [c012ebbc] (do_vfs_ioctl+0x4c8/0x588) from [c012ecc8] (SyS_ioctl+0x4c/0x78) [ 60.231002] [c012ecc8] (SyS_ioctl+0x4c/0x78) from [c000d8e0] (ret_fast_syscall+0x0/0x30) [ 60.239839] ---[ end trace 936578196fc420af ]--- [ 60.244668] [ cut here ] [ 60.249505] WARNING: CPU: 0 PID: 702 at drivers/dma/cppi41.c:629 cppi41_dma_control+0x278/0x2ac() [ 60.258791] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 nfsd deflate ctr des_generic cbc ecb cmac af_key xfrm_algo uvcvideo snd_usb_audio videobuf2_vmalloc videobuf2_memops snd_hwdep snd_usbmidi_lib videobuf2_core snd_rawmidi snd_seq_device ti_am335x_adc kfifo_buf industrialio rtc_omap uio_pdrv_genirq uio loop [ 60.290795] CPU: 0 PID: 702 Comm: python Tainted: GW 3.13.6-bone7.1 #2 [ 60.298638] [c001413c] (unwind_backtrace+0x0/0xdc) from [c0010ed8] (show_stack+0x10/0x14) [ 60.307572] [c0010ed8] (show_stack+0x10/0x14) from [c0700c00] (dump_stack+0x70/0x8c) [ 60.316048] [c0700c00] (dump_stack+0x70/0x8c) from [c0039a44] (warn_slowpath_common+0x64/0x88) [ 60.325433] [c0039a44] (warn_slowpath_common+0x64/0x88) from [c0039af8] (warn_slowpath_null+0x18/0x20) [ 60.335546] [c0039af8] (warn_slowpath_null+0x18/0x20) from [c040eae0] (cppi41_dma_control+0x278/0x2ac) [ 60.345662] [c040eae0] (cppi41_dma_control+0x278/0x2ac) from [c05170bc] (cppi41_dma_channel_abort+0x104/0x140) [ 60.356505] [c05170bc] (cppi41_dma_channel_abort+0x104/0x140) from [c0512828] (musb_cleanup_urb.isra.7+0x44/0xe4) [ 60.367620] [c0512828] (musb_cleanup_urb.isra.7+0x44/0xe4) from [c05129bc] (musb_urb_dequeue+0xf4/0x114) [ 60.377918] [c05129bc] (musb_urb_dequeue+0xf4/0x114) from [c04fafb0] (usb_hcd_unlink_urb+0x5c/0x7c) [ 60.387760] [c04fafb0] (usb_hcd_unlink_urb+0x5c/0x7c) from [c04fbd60] (usb_kill_urb+0x50/0xc4) [ 60.397161] [c04fbd60]
Re: [beagleboard] BBB UVC/DMA crash kernel 3.13.6-bone7.1
On 03/14/2014 11:20 AM, Robert Nelson wrote: On Fri, Mar 14, 2014 at 11:14 AM, David Lambert d...@lambsys.com wrote: The USB DMA still appears to have problems when used with USB cameras. It appears that whenever I attempt to issue controls via UVC to a camera that is capturing, then I get the attached crash. PIO mode works fine. Could I suggest that the default defconfig selects PIO mode until DMA mode works reliably? I hope this is the right place to post. If not, please excuse my intrusion, and suggest another. Done: https://github.com/RobertCNelson/linux-dev/commit/182589d51ae7ecc82c1ba9ef2b6440edf2d9 I don't see it getting completely fixed anytime soon either That's a shame. I guess it is a known problem then. Just no one working on it? :-( Regards, -- 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] Kernel 3.12.x / GPMC
I don't think capemgr/device tree overlays are supported anymore. Robert
Nelson has proposed another solution with 3.13.x kernels that seems to
work for me:
https://github.com/RobertCNelson/linux-dev/commit/685b182ca956dcd8396ca69af5c678c43a102d03
HTH,
Dave.
On 03/11/2014 05:05 AM, quikcj...@gmail.com wrote:
I have done some tests initializing the device tree. The file I have
used does work in kernel 3.8.13 without any issues. However, kernel
3.12.13 causes lots of trouble.
My .dts file is as follows:
/*
* optargs=capemgr.disable_partno=BB-BONE-EMMC-2G
* arch/arm/boot/dts/am335x-boneblack.dts, find the section starting
* with mmc2 { and in section change status = okay into disabled.
* do once : mmc dev 1
* mmc rstn 1
* in uBoot or in uEnv and then delete
*/
/dts-v1/;
/plugin/;
/ {
compatible = ti,beaglebone, ti,beaglebone-black;
/* identification */
part-number = BB-BONE-MARK1;
version = 00A1;
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
P8.25,/* gpmc: gpmc_ad0 */
P8.24,/* gpmc: gpmc_ad1 */
P8.5,/* gpmc: gpmc_ad2 */
P8.6,/* gpmc: gpmc_ad3 */
P8.23,/* gpmc: gpmc_ad4 */
P8.22,/* gpmc: gpmc_ad5 */
P8.3,/* gpmc: gpmc_ad6 */
P8.4,/* gpmc: gpmc_ad7 */
P8.19,/* gpmc: gpmc_ad8 */
P8.13,/* gpmc: gpmc_ad9 */
P8.14,/* gpmc: gpmc_ad10 */
P8.17,/* gpmc: gpmc_ad11 */
P8.12,/* gpmc: gpmc_ad12 */
P8.11,/* gpmc: gpmc_ad13 */
P8.16,/* gpmc: gpmc_ad14 */
P8.15,/* gpmc: gpmc_ad15 */
P9.13,/* gpmc: gpmc_wpn */
P8.21,/* gpmc: gpmc_csn1 */
P8.18,/* gpmc: gpmc_clk */
P8.7,/* gpmc: gpmc_advn_ale */
P8.8,/* gpmc: gpmc_oen_ren */
P8.10,/* gpmc: gpmc_wen */
P8.9,/* gpmc: gpmc_ben0_cle */
P9.18,
P9.22,
gpmc,
/* the reset pin */
eMMC_RSTn;
#address-cells = 1;
#size-cells = 1;
fragment@0 {
target = am33xx_pinmux;
__overlay__ {
gpmc_pins: pinmux_gpmc_pins {
pinctrl-single,pins =
0x000 0x30/* gpmc_ad0.gpmc_ad0 MODE0 | INPUT |
PULLUP */
0x004 0x30/* gpmc_ad1.gpmc_ad1 MODE0 | INPUT |
PULLUP */
0x008 0x30/* gpmc_ad2.gpmc_ad2 MODE0 | INPUT |
PULLUP */
0x00C 0x30/* gpmc_ad3.gpmc_ad3 MODE0 | INPUT |
PULLUP */
0x010 0x30/* gpmc_ad4.gpmc_ad4 MODE0 | INPUT |
PULLUP */
0x014 0x30/* gpmc_ad5.gpmc_ad5 MODE0 | INPUT |
PULLUP */
0x018 0x30/* gpmc_ad6.gpmc_ad6 MODE0 | INPUT |
PULLUP */
0x01C 0x30/* gpmc_ad7.gpmc_ad7 MODE0 | INPUT |
PULLUP */
0x020 0x30/* gpmc_ad8.gpmc_ad8 MODE0 | INPUT |
PULLUP */
0x024 0x30/* gpmc_ad9.gpmc_ad9 MODE0 | INPUT |
PULLUP */
0x028 0x30/* gpmc_ad10.gpmc_ad10 MODE0 | INPUT
| PULLUP */
0x02C 0x30/* gpmc_ad11.gpmc_ad11 MODE0 | INPUT
| PULLUP */
0x030 0x30/* gpmc_ad12.gpmc_ad12 MODE0 | INPUT
| PULLUP */
0x034 0x30/* gpmc_ad13.gpmc_ad13 MODE0 | INPUT
| PULLUP */
0x038 0x30/* gpmc_ad14.gpmc_ad14 MODE0 | INPUT
| PULLUP */
0x03C 0x30/* gpmc_ad15.gpmc_ad15 MODE0 | INPUT
| PULLUP */
0x080 0x08/* gpmc_cscn1.gpmc_cscn1 MODE0 |
OUTPUT */
0x08C 0x28/* gpmc_clk.gpmc_clk MODE0 | OUTPUT */
0x090 0x08/* gpmc_advn_ale.gpmc_advn_ale MODE0
| OUTPUT */
0x094 0x08/* gpmc_oen_ren.gpmc_oen_ren MODE0 |
OUTPUT */
0x098 0x08/* gpmc_wen.gpmc_wen MODE0 | OUTPUT */
0x09C 0x08/* gpmc_ben0_cle.gpmc_ben0_cle MODE0
| OUTPUT */
0x078 0x08/* gpmc_ben1_cle.gpmc_ben1_cle MODE0
| OUTPUT */
;
};
fpga_config_pins: pinmux_fpga_config_pins {
pinctrl-single,pins =
/* config clk and data */
0x158 0x17 /* spi1_d1 MODE3 | INPUT | PULLUP
, serial data config */
0x150 0x17/* spi1_sclk MODE3 | INPUT | PULLUP,
serial clock config */
;
};
};
};
fragment@1 {
target = gpmc;
depth = 1;/* only create devices on depth 1 */
/* stupid warnings */
#address-cells = 1;
#size-cells = 1;
__overlay__ {
status = okay;
#address-cells = 2;
#size-cells = 1;
pinctrl-names = default;
pinctrl-0 = gpmc_pins;
/* chip select
[beagleboard] USB hot-plug error messages on 3.13.6-bone7
I keep getting the following error messages when hot-unplugging a USB camera on BBB 3.13.6-bone7 with DMA disabled (PIO only). The system seems to recover fine otherwise. Regards, Dave. -- 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. [ 435.326452] uvcvideo: Non-zero status (-71) in video completion handler. [ 435.333626] uvcvideo: Non-zero status (-71) in video completion handler. [ 435.340688] uvcvideo: Non-zero status (-71) in video completion handler. [ 435.347806] uvcvideo: Non-zero status (-71) in video completion handler. [ 435.354926] uvcvideo: Non-zero status (-71) in video completion handler. [ 435.526961] usb 2-1.4: USB disconnect, device number 7 [ 435.644690] [ cut here ] [ 435.649736] WARNING: CPU: 0 PID: 1521 at fs/sysfs/group.c:214 sysfs_remove_group+0x4c/0xfc() [ 435.658619] sysfs group c0b23da0 not found for kobject 'event0' [ 435.664816] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 nfsd deflate ctr des_generic cbc ecb cmac af_key xfrm_algo snd_usb_audio snd_hwdep uvcvideo snd_usbmidi_lib videobuf2_vmalloc videobuf2_memops snd_rawmidi snd_seq_device videobuf2_core rtc_omap uio_pdrv_genirq uio loop [ 435.693594] CPU: 0 PID: 1521 Comm: python Tainted: GW 3.13.6-bone7 #1 [ 435.701421] [c001413c] (unwind_backtrace+0x0/0xdc) from [c0010ed8] (show_stack+0x10/0x14) [ 435.710386] [c0010ed8] (show_stack+0x10/0x14) from [c06feddc] (dump_stack+0x70/0x8c) [ 435.71] [c06feddc] (dump_stack+0x70/0x8c) from [c0039a44] (warn_slowpath_common+0x64/0x88) [ 435.728293] [c0039a44] (warn_slowpath_common+0x64/0x88) from [c0039a94] (warn_slowpath_fmt+0x2c/0x3c) [ 435.738333] [c0039a94] (warn_slowpath_fmt+0x2c/0x3c) from [c017ea1c] (sysfs_remove_group+0x4c/0xfc) [ 435.748195] [c017ea1c] (sysfs_remove_group+0x4c/0xfc) from [c046bdf0] (device_del+0x34/0x16c) [ 435.757519] [c046bdf0] (device_del+0x34/0x16c) from [c0521310] (evdev_disconnect+0x18/0x40) [ 435.766635] [c0521310] (evdev_disconnect+0x18/0x40) from [c051d5d8] (__input_unregister_device+0xac/0x140) [ 435.777165] [c051d5d8] (__input_unregister_device+0xac/0x140) from [c051d6c0] (input_unregister_device+0x4c/0x6c) [ 435.788361] [c051d6c0] (input_unregister_device+0x4c/0x6c) from [bf049294] (uvc_delete+0x20/0x11c [uvcvideo]) [ 435.799164] [bf049294] (uvc_delete+0x20/0x11c [uvcvideo]) from [c054370c] (v4l2_device_release+0xb8/0xd8) [ 435.809588] [c054370c] (v4l2_device_release+0xb8/0xd8) from [c046b3c8] (device_release+0x5c/0x90) [ 435.819272] [c046b3c8] (device_release+0x5c/0x90) from [c03c4704] (kobject_cleanup+0x58/0x6c) [ 435.828587] [c03c4704] (kobject_cleanup+0x58/0x6c) from [c0543464] (v4l2_release+0x5c/0x68) [ 435.837721] [c0543464] (v4l2_release+0x5c/0x68) from [c01200d8] (__fput+0xd4/0x1dc) [ 435.846118] [c01200d8] (__fput+0xd4/0x1dc) from [c0054334] (task_work_run+0xac/0xc4) [ 435.854617] [c0054334] (task_work_run+0xac/0xc4) from [c0010988] (do_work_pending+0x88/0x9c) [ 435.863839] [c0010988] (do_work_pending+0x88/0x9c) from [c000d920] (work_pending+0xc/0x20) [ 435.872873] ---[ end trace c0499242b34808eb ]--- [ 435.881321] [ cut here ] [ 435.886191] WARNING: CPU: 0 PID: 1521 at fs/sysfs/group.c:214 sysfs_remove_group+0x4c/0xfc() [ 435.895166] sysfs group c0b23da0 not found for kobject 'input3' [ 435.901404] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 nfsd deflate ctr des_generic cbc ecb cmac af_key xfrm_algo snd_usb_audio snd_hwdep uvcvideo snd_usbmidi_lib videobuf2_vmalloc videobuf2_memops snd_rawmidi snd_seq_device videobuf2_core rtc_omap uio_pdrv_genirq uio loop [ 435.930321] CPU: 0 PID: 1521 Comm: python Tainted: GW 3.13.6-bone7 #1 [ 435.938195] [c001413c] (unwind_backtrace+0x0/0xdc) from [c0010ed8] (show_stack+0x10/0x14) [ 435.947134] [c0010ed8] (show_stack+0x10/0x14) from [c06feddc] (dump_stack+0x70/0x8c) [ 435.955641] [c06feddc] (dump_stack+0x70/0x8c) from [c0039a44] (warn_slowpath_common+0x64/0x88) [ 435.965046] [c0039a44] (warn_slowpath_common+0x64/0x88) from [c0039a94] (warn_slowpath_fmt+0x2c/0x3c) [ 435.975087] [c0039a94] (warn_slowpath_fmt+0x2c/0x3c) from [c017ea1c] (sysfs_remove_group+0x4c/0xfc) [ 435.984947] [c017ea1c] (sysfs_remove_group+0x4c/0xfc) from [c046bdf0] (device_del+0x34/0x16c) [ 435.994268] [c046bdf0] (device_del+0x34/0x16c) from [c051d6c0] (input_unregister_device+0x4c/0x6c) [ 436.004078] [c051d6c0] (input_unregister_device+0x4c/0x6c) from [bf049294] (uvc_delete+0x20/0x11c [uvcvideo]) [ 436.014877] [bf049294] (uvc_delete+0x20/0x11c [uvcvideo]) from [c054370c] (v4l2_device_release+0xb8/0xd8) [ 436.025317]
Re: [beagleboard] BeagleBone Black and an abrupt loss of power
On 03/10/2014 03:33 PM, Tomaso E wrote: Thanks Dave for your post. It was very helpful, especially the link to the unstable-bits article. I have a follow-up question, if power is lost abruptly, does the unstable bits simply result in lost data, or does the file system become corrupted and could previously stored data get damaged? Or does are the results unpredictable? In my limited experience, the results are unpredictable. There was a commercial flash file system a few years ago (I think the name was FlashFX) but I could not get good answers as their system was proprietary. I think I might have to build a shield or external circuit as you are considering doing, to provide continuous power to the unit in spite of fluctuations in the external power supply. Thanks again for your help! Tomaso On Monday, March 10, 2014 3:56:07 PM UTC-4, David wrote: On 03/10/2014 02:43 PM, Tomaso E wrote: Hi All, I'm considering using a Beagle Bone Black for a project that I am working on. I have some basic experience working with a couple of different microcontrollers/computers but I really like the specs of the Beagle Bone Black. I love that it can run various Linux distributions and the hardware profile matches my project requirements pretty closely. One concern that I have is regarding the Beagle Bone Black's ability to tolerate a sudden loss of power. On many embedded Linux systems, if power is lost abruptly, the file system can become corrupt, and the device will not be able to boot, unless the file system is completely rebuilt. With rotating media, journaling file systems such as ext3/4 handle sudden asynchronous power losses fine. The problem seems to be that flash sub systems such as SSD/eMMC contain internal controllers which handle wear leveling/bad-block management etc. Here the issue becomes worse as the file system has no knowledge of these internal processes. I have worked with native flash file systems such as UBIFS, but they also suffer from phenomena such as unstable-bits http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits. For these reasons, I am in the process developing a cape which provides short term battery backup and intelligence to perform an orderly shutdown. Other features include an independent watchdog and POE supprt. Can the Beagle Bone Black tolerate an abrupt loss of power and not be bricked? Ideally, for my project, the device would be powered down properly, but I can think of instances where the board might lose power suddenly. I was wondering if I would have to worry about having the device get bricked if this happened. The BBB would not be bricked, but any file systems on the eMMC/SD may be corrupted. Thanks in advance! Tomaso HTH, Dave. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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] Kernel/device tree road-map for the BBB
Just a suggestion. If the dtb for the cape does not exist or is corrupted, could the device tree default to the base, for example am335x-boneblack.dtb? Dave. On 03/05/2014 08:07 PM, Robert Nelson wrote: On Wed, Mar 5, 2014 at 7:01 PM, David Lambert d...@lambsys.com wrote: On 03/05/2014 06:52 PM, Robert Nelson wrote: I just fixed this last friday, the 'cape' variable was used in the wrong spot in u-boot so it never got used.. cd /opt/scripts/ git pull ./tools/update_bootloader.sh I am confused, where is this script? I have searched netinstall and linux-dev trees? yeah, that's on my todo list, I need to add it to the netinstall by default. sudo mkdir -p /opt/scripts/ sudo chown -R (user):(user) /opt/scripts git clone git://github.com/RobertCNelson/boot-scripts /opt/scripts It's a git repo where i'm stashing help beagle scripts. Regards, -- 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/groups/opt_out.
Re: [beagleboard] Loading CAN cape on startup
I had a similar experience with the Debian 3.8 kernel. Never figured it out and wrote a simple startup service (systemd) to do the echo... Now I am using 3.13 and using Robert Nelson's excellent ideas (see the thread Kernel/device tree road-map for the BBB) Hope this helps, Dave. On 03/06/2014 03:37 PM, sixvolts wrote: Using the new Debian builds on my beaglebone white, I'm trying to load a device tree overlay for the CAN cape on startup, but it seems to fail to load automatically (but try), however, I can load the device tree overlay manually and it seems to work just fine. What am I doing wrong? I even tried putting the following entry in uEnv.txt: optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G capemgr.enable_partno=BB-BONE-SERL-01 I don't know of any hardware conflicts, and the same hardware works fine on Angstrom. I really want to migrate to Debian for several reasons. Here's the command and successful load manually: debian@arm:~$ sudo sh -c echo BB-BONE-SERL-01 /sys/devices/bone_capemgr.8/slots [sudo] password for debian: [ 99.355373] bone-capemgr bone_capemgr.8: part_number 'BB-BONE-SERL-01', version 'N/A' [ 99.365522] bone-capemgr bone_capemgr.8: slot #5: generic override [ 99.372251] bone-capemgr bone_capemgr.8: bone: Using override eeprom data at slot 5 [ 99.380404] bone-capemgr bone_capemgr.8: slot #5: 'Override Board Name,00A0,Override Manuf,BB-BONE-SERL-01' [ 99.391261] bone-capemgr bone_capemgr.8: slot #5: Requesting part number/version based 'BB-BONE-SERL-01-00A0.dtbo [ 99.402199] bone-capemgr bone_capemgr.8: slot #5: Requesting firmware 'BB-BONE-SERL-01-00A0.dtbo' for board-name 'Override Board Name', version '00A0' [ 99.434783] bone-capemgr bone_capemgr.8: slot #5: dtbo 'BB-BONE-SERL-01-00A0.dtbo' loaded; converting to live tree [ 99.448201] bone-capemgr bone_capemgr.8: slot #5: #2 overlays [ 99.456729] platform 481d.d_can: alias fck already exists [ 99.468434] bone-capemgr bone_capemgr.8: slot #5: Applied #2 overlays. debian@arm:~$ [ 99.538154] CAN device driver interface [ 99.562768] c_can_platform 481d.d_can: invalid resource [ 99.568915] c_can_platform 481d.d_can: control memory is not used for raminit [ 99.580927] c_can_platform 481d.d_can: c_can_platform device registered (regs=fa1d, irq=71) debian@arm:~$ cat /sys/devices/bone_capemgr.8/slots 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 5: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-SERL-01 debian@arm:~$ sudo ip link set can0 type can bitrate 5 debian@arm:~$ sudo ifconfig can0 up [ 248.574278] c_can_platform 481d.d_can can0: setting BTR=1c1d BRPE= debian@arm:~$ candump can0 Also, what is getting overridden and making the slots claim Override Board Name,00A0,Override Manuf etc? -Andrew -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Re: Custom DT overlay only loads at runtime on 3.18.13-40
I am confused by the reference to 3.18.13-40. Should this be 3.8.13-40? I don't think there is a cape manager in later kernels such as 3.13.x?? Dave. On 03/05/2014 10:30 AM, Robert Nelson wrote: On Wed, Mar 5, 2014 at 10:19 AM, porkupan vladimir.bor...@gmail.com wrote: Yeah, I was thinking about something like this. But since I am making a video controller overlay, it is better if it had been loaded at kernel initialization, and not as part of the init scripts. I'd like the display to be available to show some kernel startup. So I will either just overwrite the cape-bone-dvi-00A0.dts with my own stuff (and make a custom Sunhillo-only patch), or will add a new overlay to KERNEL/firmware/Makefile. It seems that a lot of people got confused by this issue (long discussion here). The problem is, the available documentation for 3.8 kernel seems to imply that the /lib/firmware overlay files are available for startup load, so it would be helpful if qualification was added. If you disable CONFIG_FIRMWARE_IN_KERNEL in the kernel build it should search /lib/firmware/*.dtbo Last i tried it caused a significant bootup delay, so i oped to just build them all in by default.. Regards, -- 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/groups/opt_out.
Re: [beagleboard] Kernel/device tree road-map for the BBB
On 02/12/2014 12:56 PM, Robert Nelson wrote: The path i'm going to start heading for v3.13.x/v3.14.x is just to do separate major cape dtb's.. So in u-boot: fdtbase=am335x-bone or am335x-boneblack cape=xzy (defined in uEnv.txt (lcd4-a1/etc)) Then it'll just load: $fdtbase-$cape.dtb on bootup.. Using 3.13.5-bone5.1 on my BBB I have edited my uEnv.txt to include the line: cape=cape-bone-argus and I have the file: /boot/uboot/dtbs/am335x-boneblack-cape-bone-argus.dtb The above dtb does not load regardless of $cape. However if I copy am335x-boneblack-cape-bone-argus.dtb to am335x-boneblack.dtb, all works fine. Any pointers? Regards, Dave. -- 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/groups/opt_out.
Re: [beagleboard] Kernel/device tree road-map for the BBB
On 03/05/2014 06:52 PM, Robert Nelson wrote: I just fixed this last friday, the 'cape' variable was used in the wrong spot in u-boot so it never got used.. cd /opt/scripts/ git pull ./tools/update_bootloader.sh I am confused, where is this script? I have searched netinstall and linux-dev trees? Dave. -- 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/groups/opt_out.
Re: [beagleboard] Kernel/device tree road-map for the BBB
On 03/05/2014 08:07 PM, Robert Nelson wrote: yeah, that's on my todo list, I need to add it to the netinstall by default. sudo mkdir -p /opt/scripts/ sudo chown -R (user):(user) /opt/scripts git clone git://github.com/RobertCNelson/boot-scripts /opt/scripts It's a git repo where i'm stashing help beagle scripts. Regards, Thanks Robert. That worked fine! I will send you a patch file of my cape code for inclusion in 3.13 shortly. Again, thanks for all your help Regards, Dave. -- 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/groups/opt_out.
Re: [beagleboard] USB with kernel 3.13.5-bone5
I am still having issues with 3.13.5-bone5 USB particulary with UVC video in DMA mode. I found switching to PIO only worked much better. On 03/04/2014 04:02 PM, l...@ansync.com wrote: I recall USB support being limited with kernel 3.8, but I'm using Debian with 3.13.5-bone5 (Robert's), and it still seems to have issues. Should 3.13 be working properly (hotplug, etc.), or is it still a little rough? I need to connect my BBB to five USB devices--will I have to have them all plugged into the hub at startup time? Should I expect other problems besides hotplug? -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Kernel/device tree road-map for the BBB
Any updates on this? On 02/12/2014 12:56 PM, Robert Nelson wrote: c) Any other pointers? I might have some free time this weekend.. The path i'm going to start heading for v3.13.x/v3.14.x is just to do separate major cape dtb's.. So in u-boot: fdtbase=am335x-bone or am335x-boneblack cape=xzy (defined in uEnv.txt (lcd4-a1/etc)) Then it'll just load: $fdtbase-$cape.dtb on bootup.. Regards, -- Robert Nelson http://www.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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
[beagleboard] RCN kernel 3.13.4-bone5 UVC issue
I don't know if this is an issue specific to the 3.13 kernel, but I have not seen this on 3.8.13. It appears whenever I attempt to stop UVC video acquisition. I suspect it is something to do with DMA vs. PIO. Please let me know if I should post this elsewhere, or if this is the correct place. Regards, Dave [ 8892.908975] [ cut here ] [ 8892.913866] WARNING: CPU: 0 PID: 661 at drivers/dma/cppi41.c:605 cppi41_dma_control+0x230/0x2ac() [ 8892.923168] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 nfsd deflate ctr des_generic cbc ecb cmac af_key xfrm_algo uvcvideo snd_usb_audio videobuf2_vmalloc snd_hwdep videobuf2_memops snd_usbmidi_lib snd_rawmidi videobuf2_core snd_seq_device ti_am335x_adc kfifo_buf industrialio rtc_omap uio_pdrv_genirq uio loop [ 8892.955243] CPU: 0 PID: 661 Comm: python Not tainted 3.13.4-bone5 #1 [ 8892.961944] [c001413c] (unwind_backtrace+0x0/0xdc) from [c0010ed8] (show_stack+0x10/0x14) [ 8892.970895] [c0010ed8] (show_stack+0x10/0x14) from [c06ffd8c] (dump_stack+0x70/0x8c) [ 8892.979391] [c06ffd8c] (dump_stack+0x70/0x8c) from [c003997c] (warn_slowpath_common+0x64/0x88) [ 8892.988793] [c003997c] (warn_slowpath_common+0x64/0x88) from [c0039a30] (warn_slowpath_null+0x18/0x20) [ 8892.998922] [c0039a30] (warn_slowpath_null+0x18/0x20) from [c040e7d8] (cppi41_dma_control+0x230/0x2ac) [ 8893.009062] [c040e7d8] (cppi41_dma_control+0x230/0x2ac) from [c0516578] (cppi41_dma_channel_abort+0x104/0x140) [ 8893.019924] [c0516578] (cppi41_dma_channel_abort+0x104/0x140) from [c0511ce4] (musb_cleanup_urb.isra.7+0x44/0xe4) [ 8893.031056] [c0511ce4] (musb_cleanup_urb.isra.7+0x44/0xe4) from [c0511e78] (musb_urb_dequeue+0xf4/0x114) [ 8893.041374] [c0511e78] (musb_urb_dequeue+0xf4/0x114) from [c04fa494] (usb_hcd_unlink_urb+0x5c/0x7c) [ 8893.051233] [c04fa494] (usb_hcd_unlink_urb+0x5c/0x7c) from [c04fb244] (usb_kill_urb+0x50/0xc4) [ 8893.060674] [c04fb244] (usb_kill_urb+0x50/0xc4) from [bf0994b8] (uvc_uninit_video+0x34/0x60 [uvcvideo]) [ 8893.070934] [bf0994b8] (uvc_uninit_video+0x34/0x60 [uvcvideo]) from [bf09b538] (uvc_video_enable+0x18/0x124 [uvcvideo]) [ 8893.082635] [bf09b538] (uvc_video_enable+0x18/0x124 [uvcvideo]) from [bf097bb0] (uvc_v4l2_release+0x40/0xc4 [uvcvideo]) [ 8893.094338] [bf097bb0] (uvc_v4l2_release+0x40/0xc4 [uvcvideo]) from [c0544718] (v4l2_release+0x30/0x68) [ 8893.104564] [c0544718] (v4l2_release+0x30/0x68) from [c011ffb0] (__fput+0xd4/0x1dc) [ 8893.112972] [c011ffb0] (__fput+0xd4/0x1dc) from [c005421c] (task_work_run+0xac/0xc4) [ 8893.121465] [c005421c] (task_work_run+0xac/0xc4) from [c003bf70] (do_exit+0x3f0/0x930) [ 8893.130138] [c003bf70] (do_exit+0x3f0/0x930) from [c003c528] (do_group_exit+0x4c/0xc4) [ 8893.138819] [c003c528] (do_group_exit+0x4c/0xc4) from [c00496b0] (get_signal_to_deliver+0x558/0x5bc) [ 8893.148769] [c00496b0] (get_signal_to_deliver+0x558/0x5bc) from [c0010528] (do_signal+0xa8/0x38c) [ 8893.158444] [c0010528] (do_signal+0xa8/0x38c) from [c0010954] (do_work_pending+0x54/0x9c) [ 8893.167389] [c0010954] (do_work_pending+0x54/0x9c) from [c000d920] (work_pending+0xc/0x20) [ 8893.176421] ---[ end trace 7ebc29db0c0c9333 ]--- [ 8893.181259] [ cut here ] [ 8893.186102] WARNING: CPU: 0 PID: 661 at drivers/dma/cppi41.c:629 cppi41_dma_control+0x278/0x2ac() [ 8893.195402] Modules linked in: xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 nfsd deflate ctr des_generic cbc ecb cmac af_key xfrm_algo uvcvideo snd_usb_audio videobuf2_vmalloc snd_hwdep videobuf2_memops snd_usbmidi_lib snd_rawmidi videobuf2_core snd_seq_device ti_am335x_adc kfifo_buf industrialio rtc_omap uio_pdrv_genirq uio loop [ 8893.227454] CPU: 0 PID: 661 Comm: python Tainted: GW 3.13.4-bone5 #1 [ 8893.235127] [c001413c] (unwind_backtrace+0x0/0xdc) from [c0010ed8] (show_stack+0x10/0x14) [ 8893.244073] [c0010ed8] (show_stack+0x10/0x14) from [c06ffd8c] (dump_stack+0x70/0x8c) [ 8893.252562] [c06ffd8c] (dump_stack+0x70/0x8c) from [c003997c] (warn_slowpath_common+0x64/0x88) [ 8893.261963] [c003997c] (warn_slowpath_common+0x64/0x88) from [c0039a30] (warn_slowpath_null+0x18/0x20) [ 8893.272091] [c0039a30] (warn_slowpath_null+0x18/0x20) from [c040e820] (cppi41_dma_control+0x278/0x2ac) [ 8893.282223] [c040e820] (cppi41_dma_control+0x278/0x2ac) from [c0516578] (cppi41_dma_channel_abort+0x104/0x140) [ 8893.293084] [c0516578] (cppi41_dma_channel_abort+0x104/0x140) from [c0511ce4] (musb_cleanup_urb.isra.7+0x44/0xe4) [ 8893.304217] [c0511ce4] (musb_cleanup_urb.isra.7+0x44/0xe4) from [c0511e78] (musb_urb_dequeue+0xf4/0x114) [ 8893.314529] [c0511e78] (musb_urb_dequeue+0xf4/0x114) from [c04fa494] (usb_hcd_unlink_urb+0x5c/0x7c) [ 8893.324385] [c04fa494] (usb_hcd_unlink_urb+0x5c/0x7c) from [c04fb244] (usb_kill_urb+0x50/0xc4) [ 8893.333799] [c04fb244] (usb_kill_urb+0x50/0xc4) from [bf0994b8] (uvc_uninit_video+0x34/0x60 [uvcvideo]) [ 8893.344045] [bf0994b8]
Re: [beagleboard] RCN kernel 3.13.4-bone5 UVC issue
On 02/23/2014 03:17 PM, Robert Nelson wrote: On Sun, Feb 23, 2014 at 3:06 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: I don't know if this is an issue specific to the 3.13 kernel, but I have not seen this on 3.8.13. It appears whenever I attempt to stop UVC video acquisition. I suspect it is something to do with DMA vs. PIO. Please let me know if I should post this elsewhere, or if this is the correct place. Hi Dave, Is this the classic white or black beaglebone? Black I'd try with disabling: CONFIG_USB_TI_CPPI41_DMA and enabling CONFIG_MUSB_PIO_ONLY That was the next thing on my list. I'll keep you posted. The cpu will do all the transfers... Regards, -- Robert Nelson http://www.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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] RCN kernel 3.13.4-bone5 UVC issue
On 02/23/2014 03:22 PM, David Lambert wrote: On 02/23/2014 03:17 PM, Robert Nelson wrote: On Sun, Feb 23, 2014 at 3:06 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: I don't know if this is an issue specific to the 3.13 kernel, but I have not seen this on 3.8.13. It appears whenever I attempt to stop UVC video acquisition. I suspect it is something to do with DMA vs. PIO. Please let me know if I should post this elsewhere, or if this is the correct place. Hi Dave, Is this the classic white or black beaglebone? Black I'd try with disabling: CONFIG_USB_TI_CPPI41_DMA and enabling CONFIG_MUSB_PIO_ONLY That was the next thing on my list. I'll keep you posted. The cpu will do all the transfers... That worked fine. I was hoping the DMA was mature enough to offload the CPU. Evidently, not yet :-\ Regards, Dave. -- 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/groups/opt_out.
[beagleboard] Kernel/device tree road-map for the BBB
I am contemplating moving from 3.8.x to 3.13.x kernels due to the apparent improvement in USB support. I am confused, however, as to the state of device trees/overlays and their relationship with capes. It appears to me that 3.8.x kernels use device tree overlays managed by an internal kernel cape manager, whereas 3.13.x kernels handle capes using Robert Nelson's Really Simple Cape Manager to patch and recompile the base BBB device tree. My questions are: a) Are the above assumptions correct? b) Will the 3.8.x cape manager be ported to 3.13.x kernel or is RCN's rscm here to stay. c) Any other pointers? Any help would be appreciated. Regards, Dave. -- 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/groups/opt_out.
Re: [beagleboard] Kernel/device tree road-map for the BBB
Thanks Robert. That sounds like a good plan. Dave. On 02/12/2014 12:56 PM, Robert Nelson wrote: On Wed, Feb 12, 2014 at 12:32 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: I am contemplating moving from 3.8.x to 3.13.x kernels due to the apparent improvement in USB support. I am confused, however, as to the state of device trees/overlays and their relationship with capes. It appears to me that 3.8.x kernels use device tree overlays managed by an internal kernel cape manager, whereas 3.13.x kernels handle capes using Robert Nelson's Really Simple Cape Manager to patch and recompile the base BBB device tree. My questions are: a) Are the above assumptions correct? b) Will the 3.8.x cape manager be ported to 3.13.x kernel or is RCN's rscm here to stay. sadly, it only works for 'simple' things. c) Any other pointers? I might have some free time this weekend.. The path i'm going to start heading for v3.13.x/v3.14.x is just to do separate major cape dtb's.. So in u-boot: fdtbase=am335x-bone or am335x-boneblack cape=xzy (defined in uEnv.txt (lcd4-a1/etc)) Then it'll just load: $fdtbase-$cape.dtb on bootup.. Regards, -- Robert Nelson http://www.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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Re: NFS server on beaglebone black
Try cat /proc/filesystems. If nfs doesn't show, then that is your problem. For example: ~# cat /proc/filesystems nodev sysfs nodev rootfs nodev bdev nodev proc nodev cgroup nodev tmpfs nodev devtmpfs nodev debugfs nodev securityfs nodev sockfs nodev pipefs nodev anon_inodefs nodev rpc_pipefs nodev devpts ext3 ext2 ext4 nodev ramfs vfat msdos nodev nfs nodev nfs4 nodev autofs fuseblk nodev fuse nodev fusectl btrfs f2fs nodev mqueue nodev mtd_inodefs nodev nfsd On 02/03/2014 09:28 AM, Andrea Pola wrote: I'm in the same situation, anyone solved? It's seems that there is no kernel-module-nfsd for BBB on Angstrom repo... Il giorno venerdì 13 dicembre 2013 18:01:08 UTC+1, cwrse...@gmail.com ha scritto: On Friday, December 13, 2013 4:21:36 AM UTC, Olive wrote: Hello, I managed to run a NFS server on a Beaglebone a couple of years ago by simply installing the following module. /opkg nfs-utils install / Revisiting the idea with the Beaglebone black I get the following message when installing the package /nfs-utils: unsatisfied recommendation for kernel-module-nfsd/ / / It looks as if the kernel doesn't have NFS configured; you'll have to rebuild it. (See if there's a /sys/module/nfsd present.) Will -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Re: Beaglebone Black doesn't obtain 169.254.xxx.xxx IP
Use avahi-autoipd http://linux.die.net/man/8/avahi-autoipd On 01/16/2014 07:08 AM, Efecan Yilmaz wrote: I found the solution. I can give a static IP to my Beaglebone via shell scripts (or adb): ifconfig eth0 up 169.254.13.13 On Thursday, 16 January 2014 11:58:41 UTC+2, Efecan Yilmaz wrote: If i connect my Beaglebone Black, which runs on Angstrom, to my computer via ethernet cable, It obtains an IP address, which starts with 169.254.xxx.xxx, for communication purposes. And I can communicate with it using TCP protocols. I can see that IP address when I use ifconfig command in terminal. But If it runs on Android, it doesn't obtain an IP address. Since there isn't ifconfig command in Android terminal, I'm using netcfg to see IP information and it shows that Beaglebone doesn't have an IP address. I need to somehow force my Beaglebone Black to obtain an IP address (like 169.254.xxx.xxx). How can I fix that? -- 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/groups/opt_out. -- 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/groups/opt_out.
[beagleboard] netinstall or image-builder?
First of all I would like to thank Robert for all his good work on moving the Debian system forward on the BBB. I am a little confused, however regarding building a minimal system. What is the relationship between netinstall and image-builder? I am looking to build a minimal system where I can cherry-pick packages. Netinstall has rudimentary menus that allow some choice, but image-builder appears to only build a system that has many features that I do not want, such as nodejs, apache, X, etc. The Angstrom system had recipes for console only images. Is there a similar image for Debian? Best regards, Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] debian: test images (2014-01-10)
On 01/13/2014 10:06 AM, Robert Nelson wrote: On Sat, Jan 11, 2014 at 7:40 AM, David Lambert d...@lambsys.com wrote: On 01/10/2014 04:11 PM, Robert Nelson wrote: It's Friday and everyone is probally kicking back and enjoying a cold beverage... Well enough of that crap, time to start actually testing something... ;) First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases Still not confirmed on the bug tracker, but I see this panic on halt: root@beaglebone:~# halt Broadcast message from root@beaglebone (ttyO0) (Fri Jan 10 17:17:21 2014): The system is going down for system halt NOW! root@beaglebone:~# Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... Unmounting file systems. Unmounted /sys/fs/fuse/connections. Unmounted /dev/mqueue. Unmounted /sys/kernel/debug. Unmounted /sys/kernel/security. Disabling swaps. Detaching loop devices. Detaching DM devices. [ 40.057138] (NULL device *): gadget not registered. [ 40.072972] Power down. [ 40.079180] Kernel panic - not syncing: Attempted to kill init! exitcode=0x [ 40.079180] [ 40.088830] [c0013270] (unwind_backtrace+0x0/0xe0) from [c0630514] (panic+0x84/0x1e0) [ 40.097438] [c0630514] (panic+0x84/0x1e0) from [c0040364] (do_exit+0x470/0x88c) [ 40.105501] [c0040364] (do_exit+0x470/0x88c) from [c004ed30] (sys_reboot+0x128/0x1b4) [ 40.114106] [c004ed30] (sys_reboot+0x128/0x1b4) from [c000d580] (ret_fast_syscall+0x0/0x30) [ 40.123242] drm_kms_helper: panic occurred, switching back to text console Just added this as: http://bugs.elinux.org/issues/39 (i'm not sure how to approve people to the bug tracker either..) I can confirm the issue on my board too.. However, since the board does actually shutdown. (5volt 0amps) I think we'll just leave that bug. wonder if it exists in 3.13-rc8? Just tried a quick test on 3.13-rc8 - no panic, but no shutdown either! Regards, Regards, -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] Custom kernel with Angstrom
Also: bitbake -c devshell This spawns a development shell as a useful sandbox with all the patches applied. On 01/12/2014 01:25 PM, John Syn wrote: From: smith.winston@gmail.com mailto:smith.winston@gmail.com Reply-To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Date: Saturday, January 11, 2014 at 5:26 PM To: beagleboard@googlegroups.com mailto:beagleboard@googlegroups.com Subject: [beagleboard] Custom kernel with Angstrom Anyone know how build a custom kernel with/for Angstrom using the OE/bitbake instructions? bitbake virtual/kernel Then make whatever changes to the kernel source bitbake --c build virtual/kernel Regards, John Thanks. -- 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 mailto:beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] debian: test images (2014-01-10)
On 01/10/2014 04:11 PM, Robert Nelson wrote: It's Friday and everyone is probally kicking back and enjoying a cold beverage... Well enough of that crap, time to start actually testing something... ;) First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases Still not confirmed on the bug tracker, but I see this panic on halt: root@beaglebone:~# halt Broadcast message from root@beaglebone (ttyO0) (Fri Jan 10 17:17:21 2014): The system is going down for system halt NOW! root@beaglebone:~# Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... Unmounting file systems. Unmounted /sys/fs/fuse/connections. Unmounted /dev/mqueue. Unmounted /sys/kernel/debug. Unmounted /sys/kernel/security. Disabling swaps. Detaching loop devices. Detaching DM devices. [ 40.057138] (NULL device *): gadget not registered. [ 40.072972] Power down. [ 40.079180] Kernel panic - not syncing: Attempted to kill init! exitcode=0x [ 40.079180] [ 40.088830] [c0013270] (unwind_backtrace+0x0/0xe0) from [c0630514] (panic+0x84/0x1e0) [ 40.097438] [c0630514] (panic+0x84/0x1e0) from [c0040364] (do_exit+0x470/0x88c) [ 40.105501] [c0040364] (do_exit+0x470/0x88c) from [c004ed30] (sys_reboot+0x128/0x1b4) [ 40.114106] [c004ed30] (sys_reboot+0x128/0x1b4) from [c000d580] (ret_fast_syscall+0x0/0x30) [ 40.123242] drm_kms_helper: panic occurred, switching back to text console Regards, Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] Device tree overlays and kernel versions
On 01/10/2014 08:57 AM, Robert Nelson wrote: On Fri, Jan 10, 2014 at 8:45 AM, David Lambert d...@lambsys.com wrote: I am considering moving from RCN kernel 3.8.13-bone35.1 to 3.13.0-rc7 to take advantage of some USB updates. It appears that device tree overlays are not yet supported in the latter. My questions are: 1) Are my observations correct? 2) If this is true, then are device tree overlays being dropped in later kernel versions? dropped is really the wrong word to use... NO ONE has taken up the effort to fully port the 3.8 overlays to 3.13... Personally, i'm working on a workaround that works for me and for most cape users. Thanks Robert. I was thinking of a workaround also, but did not want to reinvent a wheel. Could you point me to your thoughts? It seems to me that the major issue is setting up the pinmux and associated resource allocation. I'm just guessing, but the guy who originally wrote the 3.8 overlay system would probably take cash in trade to keep working on it.. When/if I have cash - I'll keep this in mind ;) Regards, Regards, -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] debian: test images (2014-01-10)
On 01/10/2014 04:11 PM, Robert Nelson wrote: 4GB standalone image that can be flashed to any 4GB or greater. [bone-debian-7.3-2014-01-10-4gb.img.xz] http://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz 096915309ec4a8fe41b1e8076a0c436b bone-debian-7.3-2014-01-10-4gb.img.xz It takes about 20-30 Minutes to dd microSD (4GB) OK It only took my system a tad over 8 minutes to a Transcend 8G SD: time xzcat /home/dlambert/downloads/bone-debian-7.3-2014-01-10-4gb.img.xz | dd bs=10M of=/dev/sdc 0+345858 records in 0+345858 records out 393216 bytes (3.9 GB) copied, 493.82 s, 8.0 MB/s real8m13.823s user0m38.910s sys0m6.756s First impressions great, came right up systemd, avahi, etc. I will keep on testing over the weekend. BTW is the kernel the same as the default in git://github.com/RobertCNelson/linux-dev.git? Any hints yet on how to handle pinmux GPIO etc. now that capemgr is not yet there? Regards, Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] debian: test images (2014-01-10)
On 01/10/2014 04:11 PM, Robert Nelson wrote: It's Friday and everyone is probally kicking back and enjoying a cold beverage... Well enough of that crap, time to start actually testing something... ;) First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases OK I registered, but awaiting approval. In the meantime, I got the following: Uncompressing Linux... done, booting the kernel. [0.369399] omap2_mbox_probe: platform not supported [0.526579] tps65217-bl tps65217-bl: no platform data provided [0.591595] bone-capemgr bone_capemgr.9: slot #0: No cape found [0.628702] bone-capemgr bone_capemgr.9: slot #1: No cape found [0.665810] bone-capemgr bone_capemgr.9: slot #2: No cape found [0.702918] bone-capemgr bone_capemgr.9: slot #3: No cape found [0.718940] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI) [0.728585] bone-capemgr bone_capemgr.9: slot #6: Failed verification [0.735360] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2) [0.752808] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed [0.814570] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8 [0.826308] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22 [0.833623] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single Don't know whether this is a bug or not, but I am also a bit confused as I thought the capemgr was not yet in 3.13? Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] debian: test images (2014-01-10)
On 01/10/2014 05:36 PM, Robert Nelson wrote: Should i also push out a 8GB image? it's all zero's and it just compresses very well.. I know but I think most of the time is writing to the SD, so it would be nice if there was a good way to resize the root using parted or something? specifially: 3.8.13-bone35 Any hints yet on how to handle pinmux GPIO etc. now that capemgr is not yet there? By default it's still 3.8 so that all books/guides/etc written for Angstrom work.. Down the road it'll be v3.13.. Yes, I know how to do that on 3.8, but I'm lost with 3.13. Looks like I will have to roll my own pinmux for now to get the USB improvements ;) Regards, -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] debian: test images (2014-01-10)
On 01/10/2014 05:52 PM, David Lambert wrote: On 01/10/2014 05:36 PM, Robert Nelson wrote: Should i also push out a 8GB image? it's all zero's and it just compresses very well.. I know but I think most of the time is writing to the SD, so it would be nice if there was a good way to resize the root using parted or something? I just used parted - it worked fine: root@beaglebone:~# df Filesystem 1K-blocksUsed Available Use% Mounted on rootfs 7537984 1220976 5930864 18% / udev 10240 0 10240 0% /dev tmpfs 101464 548100916 1% /run /dev/mmcblk0p2 7537984 1220976 5930864 18% / tmpfs 253652 0253652 0% /dev/shm tmpfs 253652 0253652 0% /sys/fs/cgroup tmpfs 102400 0102400 0% /run/user tmpfs 5120 0 5120 0% /run/lock /dev/mmcblk0p1 98094 70260 27834 72% /boot/uboot specifially: 3.8.13-bone35 Any hints yet on how to handle pinmux GPIO etc. now that capemgr is not yet there? By default it's still 3.8 so that all books/guides/etc written for Angstrom work.. Down the road it'll be v3.13.. Yes, I know how to do that on 3.8, but I'm lost with 3.13. Looks like I will have to roll my own pinmux for now to get the USB improvements ;) Regards, -- 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/groups/opt_out. attachment: dave.vcf
[beagleboard] Systemd service failure in Debian BBB with RCN kernel 3.8.13-bone34
I know that systemd is not officially supported yet, but I am puzzled by the following error: root@argus-dev:~# systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Sat, 01 Jan 2000 01:12:01 +; 14 years and 0 months ago Process: 199 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-modules-load.service root@argus-dev:~# /lib/systemd/systemd-modules-load could not find module by name='�' Failed to insert 'loop': Function not implemented HTH, Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] Systemd service failure in Debian BBB with RCN kernel 3.8.13-bone34
On 01/03/2014 02:14 PM, Robert Nelson wrote: On Fri, Jan 3, 2014 at 10:13 AM, David Lambert d...@lambsys.com wrote: I know that systemd is not officially supported yet, but I am puzzled by the following error: root@argus-dev:~# systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Sat, 01 Jan 2000 01:12:01 +; 14 years and 0 months ago Process: 199 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-modules-load.service root@argus-dev:~# /lib/systemd/systemd-modules-load could not find module by name='�' Failed to insert 'loop': Function not implemented seems to be working here: root@beaglebone:~# uname -a Linux beaglebone 3.8.13-bone34 #1 SMP Fri Jan 3 01:18:17 UTC 2014 armv7l GNU/Linux root@beaglebone:~# systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Fri, 03 Jan 2014 20:07:45 +; 4min 29s ago Main PID: 211 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/systemd-modules-load.service how did you install the kernel? maybe a 'sudo depmod -a' and a reboot... Regards, I installed the kernel using your tools/install_kernel.sh. depmod -a did not help. If I comment out the reference to loop in /etc/modules-load.d/modules.conf, the error disappears. Other modules deem to load fine. I cannot find any reference to the loop module?? root@argus-dev:~# find /lib -name loop* root@argus-dev:~# The original modules.conf file (which is a symlink to ../modules) is: # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. # Parameters can be specified after the module name. loop Any more suggestions? Regards, Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] Systemd service failure in Debian BBB with RCN kernel 3.8.13-bone34
On 01/03/2014 04:13 PM, Robert Nelson wrote: On Fri, Jan 3, 2014 at 3:55 PM, Robert Nelson robertcnel...@gmail.com wrote: I installed the kernel using your tools/install_kernel.sh. depmod -a did not help. If I comment out the reference to loop in /etc/modules-load.d/modules.conf, the error disappears. Other modules deem to load fine. I cannot find any reference to the loop module?? root@argus-dev:~# find /lib -name loop* root@argus-dev:~# It's built-in: CONFIG_BLK_DEV_LOOP=y The original modules.conf file (which is a symlink to ../modules) is: # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. # Parameters can be specified after the module name. loop debian 'upstream' builds it as a module by default.. https://github.com/RobertCNelson/linux-dev/blob/master/patches/debian-armmp#L1577 we can change it to match... So weird.. haven't tweaked the config but.. I just did: ./build_kernel.sh ./tools/install-kernel.sh to verify it before the change.. That works as is.. Regards, This is very strange. I just started from scratch with a fresh clone of linux-dev. I still get a failure as follows: root@argus-dev:~# systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: failed (Result: exit-code) since Sat, 01 Jan 2000 00:00:04 +; 14 years and 0 months ago Process: 203 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-modules-load.service root@argus-dev:~# uname -a Linux argus-dev 3.8.13-bone35 #1 SMP Fri Jan 3 17:18:01 CST 2014 armv7l GNU/Linux root@argus-dev:~# cat /etc/modules-load.d/modules.conf # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. # Parameters can be specified after the module name. loop If I comment out the loop line as below - all works fine. # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with # are ignored. # Parameters can be specified after the module name. # loop root@argus-dev:~# systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Sat, 01 Jan 2000 00:00:04 +; 14 years and 0 months ago Process: 199 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/systemd-modules-load.service Regards, Dave. -- 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/groups/opt_out. attachment: dave.vcf
Re: [beagleboard] Angstrom Abandoned for BBB? Rumor + a Rant
On 01/02/2014 05:00 PM, Robert Nelson wrote: No, just asking because I read that there is no qt4-embedded package on Debian. The full qt4 is available thou. :) As a recent convert to Debian on the BBB. I am pleased to find the full versions of applications. With specifically embedded distributions I found it irksome to have cut-down busybox versions of programs such as less. The BBB has plenty of memory and CPU cycles to handle the full versions. Progress is great, but sometimes confusing ;-) . Regards, Dave. Regards, -- 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/groups/opt_out.
Re: [beagleboard] Angstrom Abandoned for BBB? Rumor + a Rant
Well said William! Initially, I adopted Angstrom as it seemed to be the official way that the Beagle community was heading. About a month, however, ago I felt that Angstrom was not meeting my needs as far as stability and support, so I changed to Debian. No big deal. It only took a day or two, with some kind help from Robert Nelson. I have not regretted the change. Over the past few years, I have used Snapgear, uCLinux, Buildroot, as appropriate. IMHO developing embedded systems requires me to have some flexibility to go with the flow, and not to get too upset if the flavor of the month changes from my favorite. My experience with the Beagleboards has been generally very positive, and I have learned to live with the few wrinkles I have found. Nuff said. Happy New Year to all. Dave. On 01/01/2014 03:42 PM, William Hermans wrote: You know what I find funny ? That here is one hell of a piece of hardware ( complete system ), that costs $45( very good price ), that works very well if you're willing to spend some time working on it ( software ). And all a bunch of people on this list can do is complain, find conspiracy theories, or otherwise just try to find something wrong with it or the situation. There is *NOTHING* better out there right now as a learning platform. PERIOD. In fact, not only is it a very good learning platform, there are people I know for a fact who use MANY of these in commercial type applications. I have talked to 1-2 people who claimed to have purchased 100 or more of these, and have talked with several people who have over 10. Here, we own 2, and eventually we will probably own many more. Is the BBB perfect ? Well that is debatable, and really depends on your needs, but I would say no. Nothing ever is. But for the price, there really is nothing to complain about. Now if you're incapable of working with the hardware to make it do what you want. You know what, that is your own fault. Compulsive buyer is probably how I would initially label these types. These people can try and twist words from this source and that, but the truth of the matter is that this system is a learning platform, with very good potential. *IF YOU'RE WILLING TO WORK AT IT. *Or does every one else here think we're able to have a complete Dell like support situation for $45 ? Right . . . keep dreaming. Now if these people would come on the list asking for help stating that x-y-z does not work with x-y-z platform, using x-y-z software etc. Many people would offer to try and help, even myself. But the same situation with the exception of complaining about it, pointing fingers, trying to find conspiracy . . . yeah I have absolutely zero sympathy. You know what else, I have no idea who works for TI (still ? ), who does not, and what the motivation is for this project for ANY of the companies involved. Go out, take the schematics / gerber files etc. Send them off to some PCB fab company, and TRY to have even just the PCB's made for the same price as what circuitco sells the PCBA for . . . Gratitude for ya . . . Now to the guy talking about the Cortex M3 MCU's, and how they seemingly went out of production overnight. If you had paid attention to the errata for these processors in the first place you never would have thought about using it. Not for anything serious anyway. TI replaced these with Cortex M4's very quickly, not to mention there are other Cortex equivalents ( geared towards safety, automotive etc. ). Anyway, I need to stop as I am starting to scare myself by sounding too much like a TI Evangelist ( which I am not) But some of you seriously need to wake up to a fresh cup of reality. On Wed, Jan 1, 2014 at 1:11 PM, David Anders danders@gmail.com mailto:danders@gmail.com wrote: On Wednesday, January 1, 2014 6:55:38 AM UTC-6, Anguel wrote: On Wednesday, January 1, 2014 1:37:02 PM UTC+1, Elena Grandi wrote: This theory has a problem: Beagleboard.org was born in 2008 or so, much earlier than the Raspberry (which started to be known to the public in 2011, and was available in 2012). Ok, I admit I am not much aware of the way Beagleboard.org worked before the lower-cost Beaglebones were introduced, but it has always been driven by marketing, initially aimed at colleges, according to Wikipedia. I just want to make clear that big companies don't do anything without profit. here is the thing: TI has nothing to do with beagleboard.org http://beagleboard.org other than they sell the processors to circuitco to make the boards - that's it. have a quick read - http://beagleboard.org/about Of course the success of the Raspberry did influence BB.org's products: back in 2008 the standard price for this kind of boards was around 150$ (e.g. the original BeagleBoard)
Re: [beagleboard] Angstrom Abandoned for BBB? Rumor + a Rant
Excellent summary Paulo. I would add one level: 0) Novice user level - Expects a shrink wrapped system to just work like Windows, but without the crashes ;) A very Happy New Year to all, Dave. On 12/30/2013 03:13 AM, Paulo Ferreira wrote: On 30/12/2013, at 02:03, Mike Bremford m...@bfo.com wrote: Where is this documented? And why should I care? The above two paragraphs are unintelligible to anyone that hasn't been involved in embedded Linux for some time. It seems you are barking at the wrong tree. Unix is a tool. A powerful tool. As all powerful tools, power should come after some knowledge and practice. Think of a razor sharp kitchen knife, a chainsaw, an arc welding machine, a forklift, a pickup truck. All those are examples of very useful tools, but they only can be used in a productive way, after some practice time, and after having acquired some knowledge about how they work, and how to use them correctly. The standard phrase is that Unix is very user friendly, but picky about the friends... You can approach Unix at several levels: 1) User level - command line use of the Unix utilities, and understanding of shell scripts 2) Admin level - know how to manage users, programs, networking 3) Programmer - know the POSIX programming model and all the UNIX programming tools (config, make, gcc, etc...) 4) Kernel developer - all of the previous ones + how to compile a kernel If you want to work with BeagleBone, you must at least understand that many people are doing all those levels on the cutting edge of technology, and that knowledge takes time, because you need to make things, to understand how they work. The saddest thing, is that people want things done (or instant gratification) without being involved. Open Source does not work that way, and most important, life does not work that way. In order to do things, in order to get what you want, you need to involve yourself. Happy New Year to All Paulo Ferreira -- 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/groups/opt_out.
Re: [beagleboard] BBB Ethernet over usb on Debian using RCN kernel
Thanks - worked like a charm! On 12/23/2013 05:20 PM, William Hermans wrote: http://eewiki.net/display/linuxonarm/BeagleBone+Black scroll down to - usb gadget (http access to beaglebone black over usb) On Sun, Dec 22, 2013 at 6:29 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: This may seem to be a trivial question, but how do I enable Ethernet over USB (usb0:) on Debian using RCN kernel on BBB? Regards, Dave. -- 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 mailto:beagleboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] running BASH commands from C++
Have you tried looking at the return status of the system call. That
may give a clue. Also it may be worth explicitly giving the path for echo:
int status;
status = *system(/bin/echo cape-bone-iio
/sys/devices/bone_capemgr.9/slots);
*printf(status = %d\n, status);
HTH,
Dave.
On 12/21/2013 10:49 AM, Dhanushka Jayaweera wrote:
im getting nothing.. no errors. but it wont write the file either :(
im pretty new to BBB, its just my 5th day of using it... and I did
some googling, couldn't find a solution yet..
im using *echo cape-bone-iio /sys/devices/bone_capemgr.9/slots *to
create the file for ADC. right now i have to execute the bash command
manually before i execute the c++ file which I wrote to read ADC values
Btw what is writing the proper text directly to the slots file ??
im kinda lost
On Saturday, December 21, 2013 10:07:30 PM UTC+5:30, Bas Laarhoven wrote:
On 21-12-2013 17:24, Dhanushka Jayaweera wrote:
both commands work in the terminal
So you know what to do, now find out how to do it :-)
What is the result from the system() call?
-- Bas
BTW: You can also try writing the proper text directly to the
slots file!
On Saturday, December 21, 2013 9:52:27 PM UTC+5:30, Dhanushka
Jayaweera wrote:
well i tried this
*system(echo cape-bone-iio
/sys/devices/bone_capemgr.9/slots);*
*
*
still the same
On Saturday, December 21, 2013 9:40:04 PM UTC+5:30, Bas
Laarhoven wrote:
On 21-12-2013 17:04, Dhanushka Jayaweera wrote:
hey guys,
I want to add this bash command to my c++ program.
*echo cape-bone-iio /sys/devices/bone_capemgr.*/slots*
i tried this
*#includecstdio*
*#includecstdlib*
*#includeunistd.h*
*using namespace std;*
*int main() {*
* system(echo cape-bone-iio
/sys/devices/bone_capemgr.*/slots);*
* return 0;*
*}*
but it does not work.
Can someone help me with this?
--
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
https://groups.google.com/groups/opt_out
https://groups.google.com/groups/opt_out.
Have you verified that the system command does wildcard
expansion?
(Replace the asterisk in the command by the proper number
and verify whether that works)
-- Bas
--
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 javascript:.
For more options, visit https://groups.google.com/groups/opt_out
https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
[beagleboard] netinstall question
I have a question regarding the mk_mmc.sh script in Robert Nelson's netinstall. It appears that even if I request no swap space: sudo conf_swapsize_mb=0 ./mk_mmc.sh --mmc /dev/sdc --dtb am335x-boneblack --firmware --serial-mode the script insists on making a minimal swap partition: Device Boot Start End Blocks Id System /dev/mmcblk0p1 *2048 198655 98304e W95 FAT16 (LBA) /dev/mmcblk0p2 20070215642623 77209615 Extended /dev/mmcblk0p5 20070415394815 7597056 83 Linux /dev/mmcblk0p61539686415642623 122880 82 Linux swap / Solaris Is this really essential, or even desirable on a system residing on SD card? If my embedded system runs out of RAM, I would prefer it to crash and restart, rather than thrashing the SD card to death ;) I can change this by editing the mk_mmc.sh script, but I am concerned that I may be missing a critical point. Regards, Dave. -- 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/groups/opt_out.
Re: [beagleboard] netinstall question
On 12/12/2013 12:09 PM, Robert Nelson wrote: Hi Dave, you can setup the partition layout anyway you want at the debian-installer partition stage, just don't tweak the initial 100Mb fat partition.. No fear! Just don't be too creative, the script at the end of install can figure out what most people setup: https://github.com/RobertCNelson/netinstall/blob/master/lib/debian-finish.sh#L37 Regards, Thanks Robert. I was more concerned as to _why__default_ a swap partition on media with a limited write life? Regards, Dave. -- 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/groups/opt_out.
Re: [beagleboard] netinstall question
On 12/12/2013 01:11 PM, Robert Nelson wrote: Thanks Robert. I was more concerned as to why default a swap partition on media with a limited write life? Well it was enabled back in the day, with my 128Mb beagleboard and it just ran much smoother with gnome with swap. ;) Never really gave it much thought since.. Regards, Thanks for the honest answer Robert. Unfortunately I have been the victim of SD cards wearing out due to multiple writes, usually in systems installed in remote locations :-( Since then, I have been very frugal on what writes to SD. Regards, Dave. -- 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/groups/opt_out.
Re: [beagleboard] netinstall question
On 12/12/2013 01:25 PM, Robert Nelson wrote: How about this. ;) https://github.com/RobertCNelson/netinstall/commit/0ff008b13a6f819755416375004fd5d4962613d3 Regards, Excellent!!! -- 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/groups/opt_out.
Re: [beagleboard] netinstall question
On 12/12/2013 01:25 PM, Robert Nelson wrote:
How about this. ;)
https://github.com/RobertCNelson/netinstall/commit/0ff008b13a6f819755416375004fd5d4962613d3
Regards,
Oops:
dlambert@development ~/netinstall $ sudo ./mk_mmc.sh --mmc /dev/sdc
--dtb am335x-boneblack --firmware --no-swap --serial-mode
./mk_mmc.sh: line 922: syntax error near unexpected token `else'
I am no shell guru, but maybe there should be a 'then' for the 'else'?
--- a/mk_mmc.sh
+++ b/mk_mmc.sh
@@ -910,7 +910,7 @@ finish_installing_device () {
setup_parition_recipe () {
#This (so far) has been leaving the first Partition Alone...
- if [ x${no_swap} = xenabled ] ;
+ if [ x${no_swap} = xenabled ] ; then
cat ${TEMPDIR}/initrd-tree/partition_recipe -__EOF__
500 1000 -1 ext4
method{ format } format{ }
--
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/groups/opt_out.
Re: [beagleboard] Switching from Angstrom to Debian for the BBB
Thanks Micka. I was considering just removing the request to capemgr via uEnv.txt, and writing a service to populate the slot. Ultimately the loading should be taken care of via the EEPROM signature, but that has not yet been implemented. I was just curious as to what was the difference between Debian and Angstrom which makes capemgr.enable_partno not work reliably on Debian. Best regards, Dave. On 12/10/2013 01:53 AM, Micka wrote: Why not disabling the cap manager at the boot (is it possible?) and later push yourself the config that you want in the slot? Micka, On Dec 10, 2013 5:50 AM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: On 12/09/2013 05:12 PM, Robert Nelson wrote: On Mon, Dec 9, 2013 at 2:15 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: In desperation, I added a printk to capemgr to print out the return value from request_firmware. I get -2 ENOENT, but the file name is in /lib/firmware exactly as printed in the error line. Another thought is that Debian appears to use initrd, whereas I don't think Angstrom does? Could this be the issue? Any ideas would be very welcome. You could try updating the initrd.. sudo /boot/uboot/tools/update_boot_files.sh Regards, Thanks for the suggestion Robert. That is good to know, unfortunately it did not fix the problem :-( I now suspect that the firmware load request from capemgr is happening before /lib/firmware is accessible, but this is just a WAG. I need to understand the way capemgr works before I can offer any logical explanation :-[ Regards, Dave. -- 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 mailto:beagleboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Switching from Angstrom to Debian for the BBB
Robert, I switched to systemd, but the problem still exists. Is there a guide on debugging the cape manager? The only messages I see are: [2.559511] bone-capemgr bone_capemgr.9: failed to load firmware 'argus-ups-00A0.dtbo' [2.567868] bone-capemgr bone_capemgr.9: loader: failed to load slot-7 argus-ups:00A0 (prio 0) I would like to find out some more information as to why this failure. Regards, Dave. On 12/06/2013 03:20 PM, William Hermans wrote: Something like that, Robert would know better than I. I do have years of Debian experience, but much of the low level details I am unfamiliar with. This would be one of those cases. On Fri, Dec 6, 2013 at 2:13 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: On 12/06/2013 03:02 PM, William Hermans wrote: Perhaps the HDMI video and audio are not being disabled quickly enough for your module to load. Another way to load your module would be to write a startup service. Which you can then load at any point in the Debian startup cycle. I have a write up of an example here :http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/ I think you may be right William. There may be a race condition here. Sometimes when I boot, I get: root@debian:~# cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 7: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups But the module is not loaded. Other times I get nothing in slot 7. I think one difference between my Angstrom system may be that Angstrom uses systemd, and Debian uses System V init??? Anyway, I will try your suggestion. Thanks, Dave. Turns out the reason why I wrote this short article was a goof on my part. Also, the reasons why I did this may not seen sane to some. Meaning, there could be a much easier way to do the same things . . . but . . . whatever the case the example is perfectly usable for different situations. -- 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 mailto:beagleboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Switching from Angstrom to Debian for the BBB
In desperation, I added a printk to capemgr to print out the return value from request_firmware. I get -2 ENOENT, but the file name is in /lib/firmware exactly as printed in the error line. Another thought is that Debian appears to use initrd, whereas I don't think Angstrom does? Could this be the issue? Any ideas would be very welcome. Thanks, Dave. On 12/09/2013 11:50 AM, David Lambert wrote: Robert, I switched to systemd, but the problem still exists. Is there a guide on debugging the cape manager? The only messages I see are: [2.559511] bone-capemgr bone_capemgr.9: failed to load firmware 'argus-ups-00A0.dtbo' [2.567868] bone-capemgr bone_capemgr.9: loader: failed to load slot-7 argus-ups:00A0 (prio 0) I would like to find out some more information as to why this failure. Regards, Dave. On 12/06/2013 03:20 PM, William Hermans wrote: Something like that, Robert would know better than I. I do have years of Debian experience, but much of the low level details I am unfamiliar with. This would be one of those cases. On Fri, Dec 6, 2013 at 2:13 PM, David Lambert d...@lambsys.com mailto:d...@lambsys.com wrote: On 12/06/2013 03:02 PM, William Hermans wrote: Perhaps the HDMI video and audio are not being disabled quickly enough for your module to load. Another way to load your module would be to write a startup service. Which you can then load at any point in the Debian startup cycle. I have a write up of an example here :http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-init-scripts-default-gatewayand-ntpdate/ I think you may be right William. There may be a race condition here. Sometimes when I boot, I get: root@debian:~# cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI 6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN 7: ff:P-O-L Override Board Name,00A0,Override Manuf,argus-ups But the module is not loaded. Other times I get nothing in slot 7. I think one difference between my Angstrom system may be that Angstrom uses systemd, and Debian uses System V init??? Anyway, I will try your suggestion. Thanks, Dave. Turns out the reason why I wrote this short article was a goof on my part. Also, the reasons why I did this may not seen sane to some. Meaning, there could be a much easier way to do the same things . . . but . . . whatever the case the example is perfectly usable for different situations. -- 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 mailto:beagleboard%2bunsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out. -- 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/groups/opt_out.
Re: [beagleboard] Switching from Angstrom to Debian for the BBB
On 12/05/2013 03:53 PM, Robert Nelson wrote: Well, the best option is to write a patch against: https://github.com/beagleboard/kernel/tree/3.8 and then i'll merge it into both tree's and push out a new debian/ubuntu kernel build. .;) So everyone get's the patch and supports your new cape out of the box... Regards, Well I got my module and dtb to compile and install cleanly, but I am now confused by the uEnv.txt. It appears to be much more complex than the one I used for Angstrom (attached). I would like to disable the HDMI virtual cape and enable mine. Is there a wiki that explains how to do this with Debian? Regards, Dave. -- 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/groups/opt_out. optargs=run_hardware_tests \ capemgr.disable_partno=BB-BONELT-HDMIN,BB-BONELT-HDMI \ capemgr.enable_partno=argus-ups
Re: [beagleboard] Switching from Angstrom to Debian for the BBB
I may be barking up the wrong tree here, but I also notice that the
uboot partition contains dtbs (see below). Do I need to put my cape's
dtb here? Also I am attaching the uEnv.txt from the Debian system. I am
particularly confused by the line:
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}
I have been looking for some documentation on this without success.
Best regards,
Dave.
root@debian:~# ls -R /boot/uboot/dtbs/
/boot/uboot/dtbs/:
am335x-boneblack.dtb omap3430-sdp.dtb omap4-panda.dtb
am335x-bone.dtbomap3-beagle.dtb omap4-panda-es.dtb
am335x-evm.dtb omap3-beagle-xm.dtb omap4-sdp.dtb
am335x-evmsk.dtb omap3-devkit8000.dtb omap4-sdp-es23plus.dtb
am335x-tester.dtb omap3-evm.dtb omap4-var-som.dtb
am3517-evm.dtb omap3-igep0020.dtbomap5-evm.dtb
am3517_mt_ventoux.dtb omap3-igep0030.dtbomap5-uevm.dtb
am43x-epos-evm.dtb omap3-tobi.dtb
omap2420-h4.dtbomap4-panda-a4.dtb
On 12/06/2013 11:58 AM, William Hermans wrote:
Errr, that is as long as the file names have not changed . . .
I also wanted to point out that that technically uEnv.txt and uboot
have *nothing* to do with the OS in particular. However in this case
optargs are passed to the kernel when it starts up so . ..
On Fri, Dec 6, 2013 at 10:55 AM, William Hermans yyrk...@gmail.com
mailto:yyrk...@gmail.com wrote:
optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
On Fri, Dec 6, 2013 at 10:48 AM, David Lambert d...@lambsys.com
mailto:d...@lambsys.com wrote:
On 12/05/2013 03:53 PM, Robert Nelson wrote:
Well, the best option is to write a patch against:
https://github.com/beagleboard/kernel/tree/3.8
and then i'll merge it into both tree's and push out a new
debian/ubuntu kernel build. .;) So everyone get's the
patch and
supports your new cape out of the box...
Regards,
Well I got my module and dtb to compile and install cleanly,
but I am now confused by the uEnv.txt. It appears to be much
more complex than the one I used for Angstrom (attached). I
would like to disable the HDMI virtual cape and enable mine.
Is there a wiki that explains how to do this with Debian?
Regards,
Dave.
--
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
mailto:beagleboard%2bunsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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/groups/opt_out.
--
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/groups/opt_out.
#Normal Boot
initrd_high=0x
fdt_high=0x
kernel_file=zImage
initrd_file=initrd.img
console=ttyO0,115200n8
mmcroot=/dev/mmcblk0p5 ro
mmcrootfstype=ext4 rootwait fixrtc
loadkernel=load mmc ${mmcdev}:${mmcpart} 0x8030 ${kernel_file}
loadinitrd=load mmc ${mmcdev}:${mmcpart} 0x8160 ${initrd_file}; setenv
initrd_size ${filesize}
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}
boot_classic=run loadkernel; run loadinitrd
boot_fdt=run loadkernel; run loadinitrd; run loadfdt
video_args=setenv video VIDEO_DISPLAY
device_args=run video_args; run expansion_args; run mmcargs
mmcargs=setenv bootargs console=${console} ${optargs} ${video} root=${mmcroot}
rootfstype=${mmcrootfstype} ${expansion}
expansion_args=setenv expansion
#Classic Board File Boot:
#uenvcmd=run boot_classic; run device_args; bootz 0x8030
0x8160:${initrd_size}
#New Device Tree Boot:
uenvcmd=run boot_fdt; run device_args; bootz 0x8030
0x8160:${initrd_size} 0x815f
Re: [beagleboard] Switching from Angstrom to Debian for the BBB
Thanks Robert. This make perfect sense now. Sorry for the dumb question :-[
Regards,
Dave.
On 12/06/2013 12:19 PM, Robert Nelson wrote:
I'm not sure on your confusion. With Angstrom the bootloader/uEnv.txt
matched each other and since they programmed them at the factory they
had a 100% guarantee of what was installed. In my case, I have to
deal with the original factory u-boot/MLO, and i also support a good
dozen more boards. So for my sanity the uEnv.txt has a lot of generic
options that override some of the factory defaults for this board.
So if you compare with a board that has no factory (NAND/eMMC) like
the orignal bone, the uEnv.txt is a lot simpler:
http://eewiki.net/display/linuxonarm/BeagleBone#BeagleBone-uEnv.txtbasedbootscript
So back to the line:
loadfdt=load mmc ${mmcdev}:${mmcpart} 0x815f /dtbs/${fdtfile}
For the bone (this image will boot on board boards):
ftdfile: (set by u-boot.img)
am335x-boneblack.dtb
am335x-bone.dtb
you can also override this with fdtfile=am335x-mycape.dtb (all
dtb's are in a single directory in the fat partition)
mmcdev:
0: microSD
1: eMMC
mmcpart:
1: (fat partition..) (i don't use 2, ext4)
In your case, follow William's example and add:
optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
To the top of the uEnv.txt..
Regards,
--
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/groups/opt_out.
