[beagleboard] eMMC

Hi! I'm about to make a copy of the BBB, the hardware. My intentions are to change the outline of the board so it can fit my use (i'm working on a controller for my heating system). But, Im more of a HW-person so SW is not my strong side. What if I use a different eMMC, e.g. MTFC4GACAJCN-1M WT,

Re: [beagleboard] MicroSD for removable storage on BBB?

I know this is 1.5 years later, but I seem to be running into the same issue and am having a hard time finding anything as to how to solve this: https://groups.google.com/d/msg/beagleboard/IeLSZ19NbMU/xeND-QH0AAAJ Interestingly, hot plug for the uSD card works for me on a 3.8.13 kernel under Deb

[beagleboard] Re: Reading BeagleBone Serial Number

Hi all, FWIW, based on the answers in this thread, and a little messing around with an element14 BBB rev C, the following command produces a result which seems to match the serial number printed on the bottom of the bar code sticker, attached to the left-most, outside edge of the P8 header.

Re: [beagleboard] Read analog inputs BBB running Debian Jessie

Right after I posted the last question I found the answer. this command cat /sys/bus/iio/devices/iio:device0/in_voltage5_raw got me the values from the AIN5 (p9.36) Problem solved. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscrib

Re: [beagleboard] Read analog inputs BBB running Debian Jessie

That has definitely gotten me one step closer, thank you. After using that command i typed cat /sys/devices/platform/bone_capemgr/slots and got this result 0: PF -1 1: PF -1 2: PF -1 3: PF -1 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,cape-universaln 5: P-O-L-

Re: [beagleboard] Re: Cape manager on linux 4.1: can't load bone_eqep2b cape

Robert, thank so much. -- 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...@googleg

[beagleboard] Re: Make a backup of contents of one beaglebone black and install said contents on a second BBB

Hi Wally Many thanks. I'll apologize in advance- there are terms I'm not familiar with; I fear I'll have to take small steps First question, is your system running from an SD card or the eMMC? Running the eMMC If running from an SD card, just "clone" or duplicate the card using Windows or Li

[beagleboard] Questions about boot configuration

Hello, I'm currently configuring a BeagleBoneBlack (Element14) to be used in a remote location to store a very large amount of sensor data at any given time. To do this, I wanted to boot directly from the SD card so I changed the boot flag on the eMMC. However, after using this setup for a fe

Re: [beagleboard] Re: Cape manager on linux 4.1: can't load bone_eqep2b cape

On Mon, Feb 1, 2016 at 12:56 PM, Robert Nelson wrote: > On Mon, Feb 1, 2016 at 12:37 PM, Soapy Smith wrote: >> # grep part-number bone_eqep2-00A0.dts >> part-number = "bone_eqep2"; >> # grep part-number bone_eqep2b.dts >> part-number = "bone_eqep2"; >> >> The source files for eqep2 and eqep2b bot

Re: [beagleboard] Re: Cape manager on linux 4.1: can't load bone_eqep2b cape

On Mon, Feb 1, 2016 at 12:37 PM, Soapy Smith wrote: > # grep part-number bone_eqep2-00A0.dts > part-number = "bone_eqep2"; > # grep part-number bone_eqep2b.dts > part-number = "bone_eqep2"; > > The source files for eqep2 and eqep2b both have the same part number? > The dts files are in > > /opt/so

[beagleboard] Re: Cape manager on linux 4.1: can't load bone_eqep2b cape

# grep part-number bone_eqep2-00A0.dts part-number = "bone_eqep2"; # grep part-number bone_eqep2b.dts part-number = "bone_eqep2"; The source files for eqep2 and eqep2b both have the same part number? The dts files are in /opt/source/bb.org-overlays/src/arm > -- For more options, visit http:

Re: [beagleboard] What limits Beagle Board Black HDMI resolution

Plug your numbers into this video timing calculator and you will see that given the AM3358 max pixel clock rate of 126MHz, you cannot do 60Hz. http://www.fccps.cz/download/adv/frr/video_timings/video_timings.xls Regards, John > On Feb 1, 2016, at 7:51 AM, micael.beron...@gmail.com wrote: >

Re: [beagleboard] Cape manager on linux 4.1: can't load bone_eqep2b cape

[ 2219.151241] bone_capemgr bone_capemgr: part_number 'bone_eqep2b', version 'N/A' [ 2219.151335] bone_capemgr bone_capemgr: slot #7: override [ 2219.151386] bone_capemgr bone_capemgr: Using override eeprom data at slot 7 [ 2219.151442] bone_capemgr bone_capemgr: slot #7: 'Override Board Name,

Re: [beagleboard] Cape manager on linux 4.1: can't load bone_eqep2b cape

On Mon, Feb 1, 2016 at 12:19 PM, Robert Nelson wrote: > On Mon, Feb 1, 2016 at 12:13 PM, Maksim Surov wrote: >> Hello. I installed the Ubuntu 14.04 on my BBB with kernel 4.1. After that I >> updated dtc according to this >> https://github.com/RobertCNelson/bb.org-overlays. >> Everything works exc

Re: [beagleboard] Cape manager on linux 4.1: can't load bone_eqep2b cape

On Mon, Feb 1, 2016 at 12:13 PM, Maksim Surov wrote: > Hello. I installed the Ubuntu 14.04 on my BBB with kernel 4.1. After that I > updated dtc according to this > https://github.com/RobertCNelson/bb.org-overlays. > Everything works except the eqep2b device: > > root@arm:~# echo bone_eqep2 > /sys

[beagleboard] Cape manager on linux 4.1: can't load bone_eqep2b cape

Hello. I installed the Ubuntu 14.04 on my BBB with kernel 4.1. After that I updated dtc according to this https://github.com/RobertCNelson/bb.org-overlays. Everything works except the eqep2b device: root@arm:~# echo bone_eqep2 > /sys/devices/platform/bone_capemgr/slots root@arm:~# cat /sys/devic

Re: [beagleboard] Re: BBB running Ubuntu 13.10, DHCP client very slow

I'm running a test. I turn on the beaglebone without cable attached to it, and when it finishes the boot process, I plug the cable, and it takes about 5 minutes for beaglebone to get the ip address.. 2016-02-01 14:41 GMT-02:00 Robert Nelson : > On Mon, Feb 1, 2016 at 10:26 AM, wrote: > > I have

Re: [beagleboard] Re: BBB running Ubuntu 13.10, DHCP client very slow

On Mon, Feb 1, 2016 at 10:54 AM, Renan MRG wrote: > kernel: 3.8.13-bone70 > > rootfs: > No LSB modules are available. > Distributor ID: Debian > Description: Debian GNU/Linux 7.8 (wheezy) > Release: 7.8 > Codename: wheezy > > I didn't change nothing on the way it's enabled, it's default.. Yeah, f

Re: [beagleboard] Re: BBB running Ubuntu 13.10, DHCP client very slow

On Mon, Feb 1, 2016 at 10:44 AM, Renan MRG wrote: > I'm running a test. I turn on the beaglebone without cable attached to it, > and when it finishes the boot process, I plug the cable, and it takes about > 5 minutes for beaglebone to get the ip address.. Doesn't seem un-normal... what kernel?

Re: [beagleboard] Re: BBB running Ubuntu 13.10, DHCP client very slow

On Mon, Feb 1, 2016 at 10:26 AM, wrote: > I have the same issue, is there any way to speed things up ? How long is it currently taking? Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subs

Re: [beagleboard] Re: What limits Beagle Board Black HDMI resolution

You cannot do 60Hz. The processor will not support 60Hz. http://www.elinux.org/Beagleboard:BeagleBoneBlack#BeagleBone_Black_Features Gerald On Mon, Feb 1, 2016 at 9:51 AM, wrote: > > > Den onsdag 22 maj 2013 kl. 23:51:06 UTC+2 skrev Robert P. J. Day: >> >> > (1920 x 1080 x 60Hz = 124416000 = 1

[beagleboard] Re: BBB running Ubuntu 13.10, DHCP client very slow

I have the same issue, is there any way to speed things up ? Em quarta-feira, 19 de março de 2014 19:21:11 UTC-3, c...@isbd.net escreveu: > > I'm running Ubuntu 13.10 on my BBB. It seems pretty stable with no > major issues, but it takes quite a long time for the system to get its > IP address

Re: [beagleboard] Re: What limits Beagle Board Black HDMI resolution

Den onsdag 22 maj 2013 kl. 23:51:06 UTC+2 skrev Robert P. J. Day: > > > (1920 x 1080 x 60Hz = 124416000 = 124.4MHz) > > > > the beaglebone black can generate up to 125MHz clock for video, > > however to this leaves no bandwidth for audio to be multiplexed into > > the hdmi protocol. > > so

Re: [beagleboard] Failure to recognize SD card inserted at runtime

Any chance someone has an idea what might be going wrong here? I’d be happy to reformat the card or take other destructive measures, but right now the device for the card is not even showing up under /dev when the card is inserted. Is it that the 4.1.15-ti-r40 kernel doesn’t support hot-plugging

[beagleboard] Re: Why is eclipse prompting me for password when trying to connnect to BBB through remote systems?

Assuming an unmodified Debian release. If you log in as 'debian', you need a password, which is given to you as part of the log-in dialog. If you log in as 'root', you do not need a password. --- Graham == On Monday, February 1, 2016 at 7:19:13 AM UTC-6, vinaydiv...@gmail.com wrote: > > > <

[beagleboard] debian testing: 2016-01-31 (Node-RED)

Howdy! So there's a little something new in this week's snapshot (lxqt not console): http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31 http://beaglebone.local:1880/ nodered.org v0.13.1 Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard

[beagleboard] PyBBIO development

Hi all - I just wanted to put it out there that I've been pretty short on time to work on PyBBIO (https://github.com/graycatlabs/PyBBIO), so if there's any BeagleBone + Python developers / enthusiasts out there interested I'd appreciate the help! Pull requests are always welcome, but I would lo

Re: [beagleboard] Re: Cannot install minicom with Jessie 8.3 lxqt

On Mon, Feb 1, 2016 at 4:55 AM, wrote: > Hello Robert, > > Thanks for your reply. > > I did the apt-get update and then apt-get install minicom and that worked > fine, thanks. > > I then tried to follow the instructions at > https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md > >

Re: [beagleboard] Cannot install minicom with Jessie 8.3 lxqt

> On Feb 1, 2016, at 5:55 AM, guy.sm...@netprobity.co.uk wrote: > > I type: > > sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots" > > and I get: > > sh: echo: I/O error Just to preclude the obvious, you are running this either as root or via sudo, right? -hilmar --

[beagleboard] Re: Cannot install minicom with Jessie 8.3 lxqt

I think there is a conflict you can see in the dts files for "exclusive-use", P9.26. Not sure, but I think this will cause the IO error message. The dts files are in /opt/source/bb.org-overlays/src/arm. cape-universaln: "P9.26", BB-UART1: exclusive-use = "P9.24", // uart1_txd "P9.26", //

[beagleboard] Re: Cannot install minicom with Jessie 8.3 lxqt

Hello Robert, Thanks for your reply. I did the apt-get update and then apt-get install minicom and that worked fine, thanks. I then tried to follow the instructions at https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md I type the following: git clone https://github.com/beag

[beagleboard] Why is eclipse prompting me for password when trying to connnect to BBB through remote systems?

Hi Eve

Re: [beagleboard] PRU signals on expansion headers of X-15?

You can find them listed in the datasheet of the processor. Use the signal name on the expansion header schematics to start.. Gerald On Mon, Feb 1, 2016 at 1:40 AM, Karl Karpfen wrote: > Hi, > > is there already an overview available which signals of the PRU(s) are > available at the expansion

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

*libkmod: ERROR ../libkmod/libkmod.c:554 kmod_search_moddep: could not open moddep file '/lib/modules/4.1.16-bone18/modules.dep.bin'* This error has been fixed after copying the '4.1.16-bone18' modules to ' */lib/modules*' path. */etc/rc.local: 14: /etc/rc.local: cannot create /sys/devices/bo

Re: [beagleboard] Building Kernel with cross-compiler and sharing through USB

Following this tutorial , kernel downloading could be started, but there have been some errors during the installation and finally it fails. *U-Boot# bootz ${loadaddr} - ${fdtaddr}* *Kernel image @ 0x8200 [ 0x000