writes:
>
>
> Hello all!I have been working on a code where in which I use the interrupt
PRU_EVTOUT_1 as a heartbeat from the PRU to the host. Currently, however, I
have not been able to clear the interrupt so that it can be sent again. A
(partial) minimal example is
I want to enable one or more of the available serial ports, in addition to
UART0, but I've been unable to find any guidance on how to do this. Any
help will be greatly appreciated.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
I still want to be able to understand how to enable the ports and use one wire
in the newer kernels. I can see the one wire driver being loaded on startup.
But I cannot see /sys/devices/w1_devices
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because
So, I'm finding the Really Simple Cape Manager anything but simple...
I made a Java DTO library that would use a JSON file
(https://github.com/DougEdey/SB_Elsinore_Server/blob/master/extras/beaglebone.json)
to create Device Tree Overlays that could be applied easily.
This created files that
OK, I'm still unclear as to how my old dts for one wire:
/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
* published by the Free
:32 PM UTC-5, RobertCNelson wrote:
On Thu, Nov 20, 2014 at 9:16 PM, Doug Edey doug...@gmail.com
javascript: wrote:
OK, I'm still unclear as to how my old dts for one wire:
/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free
The DTB doesn't match the hardware, it matches the kernel? That seems
odd...
I ran those. commands, uEnv still points at am335-boneblack.dtb, but I
don;t see any one wire devices, even though there is one connected in the
same configuration as the old kernel 3.8 that used the previous DTB
Then just:
sudo apt-get update
sudo apt-get install linux-image-3.8.13-bone67
sudo reboot
Running
What was the reason for the change away from capemgr? capemgr seemed to
work
Search the list, it's been explained too often.
Surely, as a fellow software dev, if you have to
On Thursday, November 20, 2014 11:32:13 PM UTC-5, RobertCNelson wrote:
On Thu, Nov 20, 2014 at 10:25 PM, Doug Edey doug...@gmail.com
javascript: wrote:
The DTB doesn't match the hardware, it matches the kernel? That
seems
odd...
I ran those. commands, uEnv still points
It appears the 3.16 Archlinux kernel does not have acpi turned on and the
power button is not working. Also a system shutdown does not turn off the
power led as it did in prior kernels. Anyone have any info on this? Will
this be supported in the future? I want to be able to gracefully power
Robert,
Do you know who the point of contact is for the archlinux kernel on the
Black? I am assuming this works fine in Debian? Have you used this kernel
yet in Debian?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the
Wait, the boot button has to be pressed every single time it powers off
and on? This isn't good at all, I have a cape on my board.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To
Oh those days are coming! Trust me, you'll enjoy the way i setup the
bootloader flashed to the eMMC in the new default debian based image.
It'll make things for Arch and other distro's much easier to control
boot, without messing with the eMMC.
Robert,
I am not sure what you are saying
Robert,
I don't think you get my point or maybe I am not understanding the BBB
evolution. We have a large number of individuals who have already
purchased rev B boards. They will not have any updated eMMC code. What is
there is there. On the other hand some will be purchasing the Rev C which
OK a couple of answers to those who responded.
Taking out initrd did not fix the problem. We are a little bit in the dark
though until we get the serial port hooked up to see what is going on.
Thanks for the explanation of the boot sequence.
It is becoming clear that there may not be a fix
a better way so we won't have to do that. I will
report back in a few days with any progress.
On Sunday, April 27, 2014 10:15:04 PM UTC-4, Doug wrote:
OK I asked this question before and I was never able to resolve it.
I have an image (application) on microSD card that I want to distribute
I have ArchLinux installed and it reboots fine - shutdown -r now - but if I
power down and restart it goes to four LED's and stops. If I hold down the
boot button and power it will then boot.
How do I get it to boot at power up always from the SD card? My boot
partition has the following
I don't know why anyone can't just give a concise answer here instead of
referring you to some other post where no real answer is given.
Here is my emmc - boot partition
[root@BBBdoug ~]# ls -als /mnt2
total 537
1 drwxr-xr-x 5 root root 1024 Dec 31 1969 .
4 drwxr-xr-x 18 root root
Robert,
Thanks. I know you are a busy guy. I just wish there was a better FAQ.
Maybe there is?
Anyhow next question.. is there a way to retain the fallback emmc boot
and still boot right off from the microsd without any intervention?
--
For more options, visit
but rather the uboot code on the emmc and/or SDcard.
Isn't there one place where this is answered without a lot of argument as
to how to do it?
On Friday, April 18, 2014 10:47:57 AM UTC-4, Doug wrote:
I have ArchLinux installed and it reboots fine - shutdown -r now - but if
I power down
the
eMMC.
On Friday, April 18, 2014 10:47:57 AM UTC-4, Doug wrote:
I have ArchLinux installed and it reboots fine - shutdown -r now - but if
I power down and restart it goes to four LED's and stops. If I hold down
the boot button and power it will then boot.
How do I get it to boot
Running Beagle Black with latest Debian release. I am trying to compile a
couple of programs against kernel source and I am having a problem.
I used the bb-get-rcn-kernel-source.sh script to download the kernel
headers, source and apply patches. The kernel is linux-3.8.13-bone43 which
matches
Well I am using the BBB headless so I suspect the gtk2 lockup bug would not
be an issue???
So I guess you are saying I can be assured the kernels are the same (source
and running kernel) and it would be a waste of time to try compiling the
source kernel, installing it, and try again?
--
For
I am trying to compile some code in the latest debian release. I got the
latest source by using --
wget
I burned the debian 7.4 3-37 image to SD. I am using a 5V supply and HDMI
and wireless keyboard and mouse.
It boots. I see the penguin. I get the login prompt. seconds later all
disappears. It looks like HDMI is still active but no video.
If I am quick I can type in a username so I know the
OK I will answer my own question here at least partially. Since I do not
need HDMI and I want to go headless anyhow I logged in using USB. I then
went into the /etc/network/interfaces file and found that the eth0 lines
were commented out. So that is why I had no Ethernet connection. I added a
OK so I understand the Black Debian install can still get packages using
'apt-get install' ? I would need a number of packages to build my
application.
Also if anyone is running the stock Debian install could you tell me if
snd-pcm-oss modules is available?
/sbin/modinfo snd-pcm-oss
I
Jason,
Thanks for the reply and answers to my questions.
On the emmc my understanding is that it had a more refined internal
controller that did wear leveling a little better than SD or mSD cards.
Whether or not this is the case when using the emmc with Linux it will
eventually fail. How
I just ordered my first Black today. I have been using RPi's for awhile but
due to the lousy USB interface I wanted to try the Black. Anyhow I have a
few questions.
I plan to run Debian and I see I have the option of running it in microSD
or the internal EMMC.
I am not clear on the
I am working with Android Jelly bean and am having some adb issues when it
comes to Windows 7. I can not get windows 7 to recognize the device as an
Android device and can not find it with adb. When I boot into my linux host
machine I can use adb to find the beagleboard.
I ran lsusb on the
I am working with Android Jelly bean and am having some adb issues when it
comes to Windows 7. I can not get windows 7 to recognize the device as an
Android device and can not find it with adb. When I boot into my linux host
machine I can use adb to find the beagleboard.
I ran lsusb on the
Is there a reason why overreading causes the issue? I've noticed I can
cause it by running a:
find /sys/devices -iname ain*
Which is really annoying!
On Friday, December 6, 2013 1:27:13 AM UTC-5, nax...@gmail.com wrote:
The problem seems to arise when I am trying to access ADC continuously
problematic... shortly don't expect it to work
reliably
Il giorno mercoledì 4 dicembre 2013 01:41:47 UTC+1, Doug Edey ha scritto:
Using Ubuntu 13.04 3.8.13-bone31
After approximately five minutes AIN* values go to Resource Temporarily
Unavailable
elsinore@brewery:~$ cat /sys/devices/ocp.2
I've got 3 DS18B20 sensors on my bus at the moment, providing you've got
the sensors running in non-parasitic mode, I think you'll be fine.
On Tuesday, December 3, 2013 8:13:31 PM UTC-5, lorena...@gmail.com wrote:
Thinking of replacing the dedicated microcontroller that runs my house
with a
You'd be better off using the DC Plugs to power the Beagleboards, get a
nice big brick and split the power out.
On Wednesday, December 4, 2013 6:32:11 AM UTC-5, ara...@gmail.com wrote:
Hello,
I have 10 beaglebone black boards and would like to put them nicely in
stack... I am looking for
Does anyone have any help on this? I'm getting this too, using Ubuntu on
the Beaglebone Black. I've upgrade to 3.8.13-bone31 (the only higher
version is 3.12 but I can't get the cape to load)
I get some valid readings (for maybe a few minutes after I load the cape)
then I get the resource
Using Ubuntu 13.04 3.8.13-bone31
After approximately five minutes AIN* values go to Resource Temporarily
Unavailable
elsinore@brewery:~$ cat /sys/devices/ocp.2/helper.13/AIN*
cat: /sys/devices/ocp.2/helper.13/AIN0: Resource temporarily unavailable
cat: /sys/devices/ocp.2/helper.13/AIN1:
]---
On Tuesday, December 3, 2013 7:24:54 PM UTC-5, Doug Edey wrote:
Does anyone have any help on this? I'm getting this too, using Ubuntu on
the Beaglebone Black. I've upgrade to 3.8.13-bone31 (the only higher
version is 3.12 but I can't get the cape to load)
I get some valid readings
38 matches
Mail list logo