I have created a device tree (DT) overlay file based on the examples in
/lib/firmware for a GPIO pin to be used to control a relay that powers a
peripheral. As long as the GPIO is output/high the relay is closed and the
peripheral has power, So consequentially, I need the GPIO pin to have a
Last time I built OE for the BBB, the recommendation was to
use angstrom-v2012.12-yocto1.3 as angstrom-v2013.06-yocto1.4 didn't
compile. That was in August, now I see that there's
a angstrom-v2013.12-yocto1.5 in
https://github.com/Angstrom-distribution/meta-angstrom/blob/master/README
1) Does
On Friday, October 11, 2013 11:03:16 AM UTC-4, smith.wi...@gmail.com wrote:
>
> Last time I built OE for the BBB, the recommendation was to
> use angstrom-v2012.12-yocto1.3 as angstrom-v2013.06-yocto1.4 didn't
> compile. That was in August, now I see that there's
> a angstrom-v2013.12-yocto1.5
On Monday, October 14, 2013 6:31:12 AM UTC-4, rchrd...@gmail.com wrote:
>
> How does one use git to select angstrom-v2013.06. I would hope this later
> branch has USB driver fixes included (ie babble and hotplug).
>
>>
>>
It's just a question of which branch you're in, after step #2 in your list,
On Sunday, October 13, 2013 9:56:20 PM UTC-4, steview...@gmail.com wrote:
>
> I'm kind of a newbie, just got a brand new BBB.
>
> I installed the FTDI driver that shipped with the BBB. Checked the
> Info.plist, file was patched. Rebooted computer, reconnected BBB USB,
> waited for BBB to boot, ch
On Thursday, July 25, 2013 10:27:57 AM UTC-4, Tsvetan wrote:
>
> our AM3352-SOM prototypes were assembled today
>
> http://olimex.wordpress.com/2013/07/25/am3352-som-module-with-1ghz-sitara-cortex-a8-soc-prototypes-are-ready/
>
> we test them now and they boot Debian hf for BeagleBoneBlack succe
On Tuesday, October 15, 2013 4:15:53 PM UTC-4, Jesper We wrote:
>
> I am thinking somewhere out there there is someone who has a nice 2D CAD
> drawing of what a Cape PCB should look like
>
> I'm looking for a file to import to my PCB layout S/W. Board outline,
> connector and hole positions w
On Wednesday, October 16, 2013 8:39:30 PM UTC-4, steview...@gmail.com wrote:
>
> Thank you very much for the info, it really helped me understand whats
> going on. It looks like it would be nice to have one of those FTDI-USB
> adapters.
>
> I have another question now - what the difference betwee
I've been through the expansion header pinouts trying to come up with a
.dts configuration that enables a UART with hardware flow control (so TXD,
RXD, CTS and RTS) but does NOT break any of i2c2, HDMI or the eMMC.
- uart0: Serial console, I need that already! (but it doesn't have
RTS/CT
On Tuesday, August 27, 2013 9:46:04 AM UTC-4, Gerald wrote:
>
> There is work going on to create such a tool. It just sin't ready, And no,
> I have mo idea when it will be ready. We uses the SD card to flash the eMMC
> and a flashing tool already exists for the SD card.
>
Do you have any more in
On Thursday, October 31, 2013 2:15:28 AM UTC-4, Will Kostelecky wrote:
>
> I am struggling to get an RTC to work on my BBB. I see the 0x68 address
> in i2cdetect but it shows as UU (In Use?). When I do a "modprobe
> rtc-ds3231" it returns "FATAL: Module rtc-ds3231 not found." I have this
> s
On Thursday, October 31, 2013 7:49:27 AM UTC-4, Will Kostelecky wrote:
>
> It's on i2c-1. The frustrating thing is that the HW works with another
> image that I built a while ago. I am now trying to build a clean new image
> (post all my development messing around) and it is not working with t
On Thursday, October 31, 2013 1:45:16 PM UTC-4, Dacobi wrote:
>
> But how do I translate this to pin numbers on P8 and P9?
>
Take a look at this thread/post, it should help:
https://groups.google.com/d/msg/beagleboard/v9r8UkN7klk/h3rFKFJDLnUJ
--
For more options, visit http://beagleboard.org/di
If you're curious as to how to figure out what I2C interface maps to which
bus, take a look at this post I wrote yesterday:
https://groups.google.com/d/msg/beagleboard/v9r8UkN7klk/h3rFKFJDLnUJ
On Friday, November 1, 2013 11:02:44 AM UTC-4, Jason Kridner wrote:
>
> On Fri, Nov 1, 2013 at 12:09 A
On Saturday, October 26, 2013 2:38:27 PM UTC-4, Joshua Datko wrote:
>
>
> In the default Debian imagine, can any I2C bus be used from the P9
> expansion header, without rebuilding the kernel? If so, which pins? (19 &
> 20, or 17 & 18?)
>
> When I run i2cdetect, I have two I2C buses, but I'm not
I'm trying to sync up with the latest & greatest image-builder work by
Robert Nelson. So far so good, I have my debian jessie 4.1.10-ti-r21 BBB
image built and flashed; I've converted my .dts *back* into an overlay for
the 4.1 capemgr with the kernels.
The cape EEPROM is properly flashed, but
On Wednesday, October 14, 2015 at 11:16:28 PM UTC-4, RobertCNelson wrote:
>
> This isn't an issue anymore.. Make sure your *.dtbo is under
> /lib/firmware then run:
>
> sudo update-initramfs -uk `uname -r`
>
> to make sure the *.dtbo get's copied to the intrd. (it'll still read
> it from the /
At some point recently, the newer Beaglebone Blacks (made by Element 14)
have swapped out the older barcode for a small data matrix code sticker.
Previously, the barcode looked like it was the same or similar to the
serial number, but now the numbers on the datamatrix code don't seem to
mean
On Monday, April 25, 2016 at 4:55:47 PM UTC-4, Gerald wrote:
>
> Best bet would be to ask on the E14 forums what it means.
>
Thanks, it looks almost identical to the data matrix on the bottom of a RPi
Model B+ (I think also made by Element14).
--
For more options, visit http://beagleboard.org
I'm looking for something where I can "drop in" a cape for testing and
flashing the CAT24C256 eeprom that has little to no insertion/removal force
-- there's a lot of friction with the BBB headers and I keep bending the
pins etc. when removing the capes).
Has anyone come across a 46x2 0.1" Zero
On Tuesday, January 7, 2014 12:30:39 PM UTC-5, evan...@gmail.com wrote:
>
> I'm creating a custom device tree file to work with the PRU, and whenever
> I try to add the name of the part number to the uEnv.txt file, boot will
> hang for about 3-5 minutes then run correctly. The device tree file wo
I'm using the standard instructions for building the BBB Angstrom image, in
particular I'm building for Angstrom 13.12/yocto1.5. For the standard
system images, this works quite nicely.
Can anyone give me any pointers on how to create a custom bitbake recipe
that can modify the kernel config
Anyone know how build a custom kernel with/for Angstrom using the
OE/bitbake instructions?
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 s
On Tuesday, November 19, 2013 9:36:02 AM UTC-5, RobertCNelson wrote:
>
> Either create a pull request against the 3.8/3.12 branch or post your
> patches to this list..
>
>
Hi Robert,
Do you have any pointers on building cape support into a custom kernel? I
have built the Angstrom image and c
On Sunday, May 26, 2013 1:53:01 PM UTC-4, woss...@gmail.com wrote:
>
> I'd like to find a good and detailed source of information on how to
> create a well-integrated BBB Cape design. I have put together a bare-bones
> cape which is just an EEPROM chip running off the BBB's 3.3v line. The
>
On Monday, January 13, 2014 12:22:55 PM UTC-5, RobertCNelson wrote:
>
> >I would like to know when will be the next official release
> of
> > Angstrom image for Beaglebone black.
> > We have developed a camera cape board
> > (http://www.radiumboards.com/HD_Camera_Cape_fo
On Sunday, January 12, 2014 8:18:43 PM UTC-5, David Marquart wrote:
>
> if you are using Roberts kernel building scripts all you need to do is add
> the DTS file to /KERNEL/firmware/capes and add it to the build list in
> /KERNEL/firmware/Makefile . Then run ./tools/rebuild.sh and
> ./install
On Friday, January 10, 2014 5:11:09 PM UTC-5, RobertCNelson 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... ;)
>
>
Firstly, many thanks for your hard work here!
Now that the
On Wednesday, January 15, 2014 1:05:33 PM UTC-5, RobertCNelson wrote:
>
> The easiest thing to do, is first just fork the repo, then:
>
> cp beagleboard.org_image.sh custom_image.sh
>
> Then edit the "chroot_script" line, so you can run your own chroot
> customization script..
>
> For example
On Thursday, January 16, 2014 12:10:35 PM UTC-5, smith.wi...@gmail.com
wrote:
>
>
> Fantastic, thanks for this, I'm in the process of running my first build.
>
>
Success! ... I think. Don't seem to have working ethernet, here's the
console output:
[0.361322] omap2_mbox_probe: platform not s
On Thursday, January 16, 2014 3:01:17 PM UTC-5, RobertCNelson wrote:
>
> On Thu, Jan 16, 2014 at 1:41 PM, >
> wrote:
>
> Give it a few more seconds, currently "wicd" is under control of eth0
> (not /etc/network/interfaces) on 3.8 it takes wicd about 2-3 calls
> before it gets it..
>
> The onl
On Thursday, January 16, 2014 9:33:13 PM UTC-5, RobertCNelson wrote:
>
> > 1) Setting user_name in .project (or the main build script) gets
> overwritten
> > with 'debian'
>
> Yeah, for some reason it's not sourcing it from ".project" correctly
> at the moment..
>
> https://github.com/RobertCN
On Wednesday, January 15, 2014 1:05:33 PM UTC-5, RobertCNelson wrote:
>
> > With the new scripts, I'm looking to do a number of things:
> >
> > 3) Build a custom kernel (to include a .dts)
>
Any thoughts on adding a custom .dts to the build script to be included in
the kernel?
I have some not
On Thursday, January 16, 2014 4:42:34 PM UTC-5, RobertCNelson wrote:
>
> Know Issues:
> wicd: can only handle eth0 or wlan0, not both at the same time..
>
> Questions? Should we switch to connman?
Yes. Definitely! I need both WLAN and ETH, also connman seems more
established. Finally, conn
I see that FreeBSD RELEASE-10 is out and runs on the BBB. I have it
running in a VirtualBox VM (x64 version) and I'm interested enough to try
it on the BBB along with my cape & device tree overlay.
Does anyone have *any* idea how to get my cape(s) working:
* Does it support some kind of device
On Wednesday, January 22, 2014 11:23:25 AM UTC-5, pushu...@gmail.com wrote:
>
> BBB Board running Angstrom v2012.12 and Linux beaglebone 3.8.13 #1 SMP Tue
> Jun 18 02:11:09 EDT 2013 armv7l GNU/Linux
>
> Trying to run command "echo > $SLOTS" results in error "-su:
> echo: write error: No such fil
On Monday, January 20, 2014 8:48:50 PM UTC-5, RobertCNelson wrote:
>
> > Yes. Definitely! I need both WLAN and ETH, also connman seems more
> > established. Finally, connman has better dbus integration for interface
> > configuration.
>
> Does the version of connman (1.15) we have in the re
On Tuesday, January 21, 2014 10:54:50 PM UTC-5, rchrd...@gmail.com wrote:
>
> FreeBSD does have an ARM port available. It does use device trees to
> specify hardware, but I don't know if the grammar is the same as that used
> in ARM linux. There is a specific FreeBSD port for Raspberry Pi, but I
On Wednesday, January 22, 2014 7:38:23 PM UTC-5, RobertCNelson wrote:
>
> > On the capemgr front..I am looking into ways to get the dtbo files
> > accessible at boot time.
> > Option 1) Get capemgr to find /lib/firmware on startup
> > Option 2) Put dtbo files into boot partition
>
> Couples
On Wednesday, January 22, 2014 12:23:34 AM UTC-5, tsfl...@gmail.com wrote:
>
> This is actually a very basic question, but I'm kind of lost right now.
> I was working on a school project with the Beagle bone black. It controls
> a bunch of motors and sensors, etc. We essentially wrote everything
On Wednesday, January 22, 2014 10:42:49 PM UTC-5, Richard Lyon wrote:
>
> The problem starts with the version of u-boot they are using. By cloning
> some of the functionality of u-boot-denx you might be able to get it to
> work. But ... it's a lot of work. Then you face the issues with the kernel
On Monday, January 27, 2014 2:18:04 PM UTC-5, Gerald wrote:
>
> Arrow is showing 500 boards in stock. We have people buying boards to go
> into products, something we cannot plan for. When will that be fixed? I
> have no idea. We cannot plan for something we don't know about.
>
>
Thank you! I'v
On Sunday, January 26, 2014 9:56:27 AM UTC-5, Kevin McQuown wrote:
>
> I just received my new BBB and wanted to upgrade it to the latest Angstrom
> version. I have followed the instructions to the letter. When I insert
> the SD card into my mac using it's SD card reader (not a separate SD Card
On Wednesday, January 29, 2014 4:25:22 PM UTC-5, RobertCNelson wrote:
>
> Lets keep this going, round 4...
>
>
This is great, thanks again for your hard work. I'll take a look tonight.
You had previously mentioned adding .dtbo scripts to the /boot partition
(or was it initrd.img) to allow over
On Wednesday, January 29, 2014 10:04:50 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Jan 29, 2014 at 8:03 PM, >
> wrote:
> > You had previously mentioned adding .dtbo scripts to the /boot partition
> (or
> > was it initrd.img) to allow overlays to be detected via EEPROM and
> loaded
> > withou
On Thursday, January 30, 2014 1:29:30 PM UTC-5, RobertCNelson wrote:
>
> > So presumably, this isn't detecting capes via EEPROM; it's effectively
> the
> > equivalent of doing:
> >
> > echo cape-bone-proto > /sys/devices/bone_capemgr.9/slots
> >
> > In a startup script?
>
> Yeap.
Ok, so I
On Tuesday, February 4, 2014 6:21:15 AM UTC-5, Kenji Nakasone wrote:
>
> Well, that!
>
> I´m having trouble setting my clock, wifi, adafriut python library ..etc
> so I was thinking to update my Distro.
>
>
ntpdate time.nist.gov
Should set the clock. Note that although the BBB has an RTC, it has
On Thursday, February 6, 2014 8:38:45 AM UTC-5, Kenji Nakasone wrote:
>
> I follow:
> http://derekmolloy.ie/automatically-setting-the-beaglebone-black-time-using-ntp/
> but still cant set my time. I think that is why I cant get Adafruit
> library etc.
>
I've also tried to get ntp to work, but it
I have a couple of things I'm working on with the image-builder:
* Cape support: I need a way to get dtbo loaded at boot, preferably without
custom kernel (e.g. via initrd or by putting the .dtbo's in mmcblp0p1)
* Custom image: Building a customized version of the beagleboard.org image
For the l
On Friday, February 7, 2014 8:41:25 AM UTC-5, RobertCNelson wrote:
>
> * Custom image: Building a customized version of the beagleboard.org image
>>
>> I don't have any personal plans to do that yet. If you look closely, all
> the frontend scripts do is create a ".project" file and call
> ./Root
I am using RCN's image-builder to build jessie images for the BBB (was
previously using Wheezy). So far so good, I now need to create a custom
dtb to enable ttyO1,ttyO2,ttyO4 and ttyO5. I cloned RCN's dtb-rebuilder
and created a .dts with the following contents:
/dts-v1/;
#include "am33xx.dt
On Monday, March 9, 2015 at 1:22:09 PM UTC-4, RobertCNelson wrote:
>
>
> I've been seeing that locally too, but i see the issue...
>
> CONFIG_SERIAL_8250_NR_UARTS=4
> CONFIG_SERIAL_8250_RUNTIME_UARTS=4
>
> So... yeah.. next kernel build ;)
Ah! So r55 then?
--
For more options, visi
On Monday, March 9, 2015 at 1:22:09 PM UTC-4, RobertCNelson wrote:
> I've been seeing that locally too, but i see the issue...
>
> CONFIG_SERIAL_8250_NR_UARTS=4
> CONFIG_SERIAL_8250_RUNTIME_UARTS=4
>
>
One other thing I noticed, I see entries in dmesg output like this:
[2.656184] bone-pinm
Turning my attention now to enabling GPIO for Jessie/3.14. I merged my
prior DTS/overlay into my custom .dts for use with dtb-rebuilder So far I
have this:
&ocp {
P9_15_pinmux {
// GPIO_A
mode = "P9_15_gpio_pin";
};
P9_16_pinmux {
// GPIO_B
mode = "
On Thursday, March 12, 2015 at 12:36:33 PM UTC-4, Enoch wrote:
> Is there some /etc/init.d script or equivalent to manipulate the pin mux?
> If not, links to where to start dealing with the source would be
> appreciated.
>
You need a DTB with the UARTs enabled. See:
https://github.com/RobertC
I have a MAX3232 connected to UART5 on a BBB. During power up; presumably
before the dtb has been loaded to set the pinmux for the UART, I see a
"break" sequence being sent. A break sequence is defined as "tx held low
for a duration longer than 1 frame".
Seems like pinmuxing won't help becaus
On Monday, April 6, 2015 at 2:32:55 PM UTC-4, star...@gmail.com wrote:
>
> Hello there, I have been working on a robotics project using the
> beaglebone black and have just run into some difficulty.
>
> I am using a protocape for holding all of my circuitry to various sensors.
> While the protob
On Tuesday, April 7, 2015 at 5:36:55 PM UTC-4, Graham wrote:
> The GPIO pins on most processors, are open inputs until configured.
> So a weak pull up resistor to +3.3V (not the switched +3.3V) on the TX
> line between the Sitara pin and the MAX3232 input would likely fix your
> problem.
> Once
On Wednesday, April 8, 2015 at 10:14:23 AM UTC-4, Robert P. J. Day wrote:
>
> seeing differing opinions online ... if you read this:
>
> https://e2e.ti.com/support/arm/sitara_arm/f/791/t/233139
>
> i should be able to display the first few bytes of the BBB's EEPROM
> from u-boot using:
>
>
On Thursday, April 9, 2015 at 11:48:35 PM UTC-4, William Hermans wrote:
> *The 10K pull-up didn't work. I didn't think it would, the am335x drives
>> the pins low during initialization and this is overcoming the pull-up [the
>> outputs were never free-floating]. I think I should have used a MA
On Thursday, April 9, 2015 at 7:46:49 AM UTC-4, Robert P. J. Day wrote:
>
>
> > It works on both Debian (Jessie) and FreeBSD! It uses ioctl()'s to
> > read 28 bytes from slave addr 0x50 on i2c-0.
>
> ah, very nice, thanks.
>
The nice thing is that you don't have to be root to use it -- just
On Thursday, April 9, 2015 at 11:05:15 PM UTC-4, William Hermans wrote:
>
> *One question though: Does the cable management get in the way of the
>> cape?*
>
>
> This is something I was wondering about too. But at the time I did not
> want to come off as really negative.
>
Same here.
I have
On Wednesday, April 8, 2015 at 6:10:48 PM UTC-4, Clark Leach wrote:
> If it were me, I would interface to the 1-wire bus with one of the handy
> interface devices available from Maxim. The DS2482-100 and DS2482-800 are
> I2C to 1-wire and I2C to 1-wire X 8 interfaces respectively.
>
The DS2482
On Saturday, May 10, 2014 4:09:24 PM UTC-4, Christopher Longbottom wrote:
>
> I'm struggling to talk to a modem over the UART. The UARTs in question are
> 1 and 2, which I enabled using the Adafruit python library.
>
> They can talk to each other fine so I presume they are set up fine.
>
> The pro
On Thursday, May 8, 2014 7:02:05 AM UTC-4, jay071...@gmail.com wrote:
>
> how to cross compiler the mDNSResponder for AM335X TI SDK6.0 ??
>
>
> Not sure what you mean by "SDK 6.0", but if you have a Linux based BBB,
you can install avahi-daemon for Bonjour support.
--
For more options, visit htt
Hi Robert,
I built a set of images using the latest image-builder (from the master
branch), after booting from the SD card, the image fails to flash. There
doesn't appear to be a log file, but after running the
beaglebone-black-eMMC-flasher.sh script with -x, it seems that it's failing
in the
On Wednesday, May 14, 2014 11:40:23 PM UTC-4, RobertCNelson wrote:
>
> Yeah.. I was debugging blank eMMC's at CircuitCo i ended up breaking
> everyone else's..
>
> cd /opt/scripts/tools/
> git pull
>
> and you'll get all the fixes from tonight..
>
> It should work, I'll fire up a new build tomorro
I have a custom .conf for image-builder that's based on the beaglebone
ones, except that I have a handful of extra packages and copy some extra
files into the image. Periodically, I update this against
image-builder:master. I've been using jessie with a 4.4 kernel for a while
quite successful
On Sunday, April 8, 2018 at 1:03:57 PM UTC-4, RobertCNelson wrote:
> Ah, you found a fun bug in the old path.. I'll fix it up for the next
> person, but you can go down the new path with your setup...
>
> [snip...]
>
> in /boot/uEnv.txt
>
> remove your: dtb=am335x-boneblack-emmc-overlay.dtb
>
I built a debian stretch image (with 4.14.67-ti-r73) kernel using the
current image-builder -- I used the rcn-ee_console_debian_stretch_armhf
configuration.
Once I've flashed it, when it comes up, I notice the green LED on the
ethernet is blinking quickly. Once it comes up, it ends up with a
On Thursday, September 6, 2018 at 5:18:07 PM UTC-4, RobertCNelson wrote:
>
>
> Just to confirm details, please restate the steps you did from the output
> of the image builder script to sdcard.
>
Sure!
This is based on a pull of github.com/beagleboard/image-builder over the
long weekend (whic
On Thursday, September 6, 2018 at 5:48:39 PM UTC-4, smith.wi...@gmail.com
wrote:
>
> Just for sanity I will rebuild the rcn-ee_console_debian_stretch_armhf but
> with a flasher and retry that.
>
I rebuilt from scratch and generated an eMMC flasher, installed and I get
the same results as with
On Friday, September 7, 2018 at 12:43:22 AM UTC-4, smith.wi...@gmail.com
wrote:
>
>
> Next up, I'll retry without btrfs (i.e. omitting the --rootfs btrfs on
> the sdcard_setup step).
>
FWIW: Without btrfs, I see the same network problems.
--
For more options, visit http://beagleboard.org/dis
On Friday, September 7, 2018 at 12:43:22 AM UTC-4, smith.wi...@gmail.com
wrote:
>
> On Thursday, September 6, 2018 at 5:48:39 PM UTC-4, smith.wi...@gmail.com
> wrote:
>
>>
>> Just for sanity I will rebuild the rcn-ee_console_debian_stretch_armhf
>> but with a flasher and retry that.
>>
>
> I r
74 matches
Mail list logo
