Any reason why you can't look at the post you made yesterday ?
On Mon, Jan 2, 2017 at 12:17 PM, John Franey wrote:
> Black's hdmi connected to an hdmi-2-av external powered device connected
> to a power amplifier connected to speakers.
>
> In other words: Black -> hdmi-2-av
@beaglebone:~$ ls /dev |grep spidev
spidev1.0
spidev1.1
On Fri, Dec 30, 2016 at 5:25 PM, William Hermans <yyrk...@gmail.com> wrote:
> So I thought about it for a few minutes when not otherwise busy, and
> figured it out on my own.
>
>
> $ cd /opt/scripts/tools/developers/
17 at 4:21 PM, William Hermans <yyrk...@gmail.com> wrote:
> So, if you think "ah this is confusing . . ." it does get worse.
>
> The new future way( I suspect) to load overlays at boot will likely be
> through uboot. Robert has recently added this functionality into ubo
ut it some here:
https://groups.google.com/forum/#!searchin/beagleboard/HERE$20THERE$20BE%7Csort:relevance/beagleboard/W0QPDee5u2s/c1cbhzN4FAAJ
On Sun, Jan 1, 2017 at 4:04 PM, William Hermans <yyrk...@gmail.com> wrote:
> I meant to say I've not used SPI on any embedded Linux platform.
I'd probably try to run your executable through strace, and output into a
file.
On Sun, Jan 1, 2017 at 1:25 PM, John Franey wrote:
> I have hdmi audio working up until 10 minutes from boot time. Exactly 10
> minutes.every boot.
>
> I test with 'speaker-test'. Running
I meant to say I've not used SPI on any embedded Linux platform. I do have
plenty of experience with SPI on bare metal MCU's.
On Sun, Jan 1, 2017 at 3:35 PM, Greg wrote:
> Nice! I will add this as a reference to my project documentation.
>
> Regarding the fact that you
On Sun, Jan 1, 2017 at 2:08 PM, Greg wrote:
> Hi William, if you could point to an easily discoverable source which says
> that Universal IO is available in the latest images and encouraged to be
> used, then you could be correct.
> Being able to successfully manipulate
to at
least create my own overlay based off of existing overlays.
On Sun, Jan 1, 2017 at 12:12 PM, William Hermans <yyrk...@gmail.com> wrote:
> Just to be clear . . . The Hadron collider in Genva is the biggest
> engineering "feat" in the world . . .Involving over 10,000 scie
Just to be clear . . . The Hadron collider in Genva is the biggest
engineering "feat" in the world . . .Involving over 10,000 scientists from
over 100 countries, and I'm not sure how many engineers.
Passed that, it's not surprising the Beaglebone works at all. For instance,
you do realize that
Why the repost ? Wasn't it you who alread posted this exact same
information 2 days ago ?
On Sat, Dec 31, 2016 at 12:39 PM, Graham wrote:
> Clayton:
> Thanks for taking the time to post this summary.
> --- Graham
>
> ==
>
> On Saturday, December 31, 2016 at 1:23:13 PM
01 4b 46 7f ff 04 10 e8 : crc=e8 YES
1c 01 4b 46 7f ff 04 10 e8 t=17750
Everything working fine.
On Fri, Dec 30, 2016 at 2:07 PM, William Hermans <yyrk...@gmail.com> wrote:
> On Fri, Dec 30, 2016 at 11:03 AM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>>
On Fri, Dec 30, 2016 at 11:03 AM, Robert Nelson
wrote:
> Okay, time to push it out as default...
>
> First stable build is:
>
> U-Boot SPL 2017.01-rc2-3-ga4c7d45040 (Dec 30 2016 - 11:30:57)
> Trying to boot from MMC1
>
> U-Boot 2017.01-rc2-3-ga4c7d45040 (Dec 30
On Thu, Dec 29, 2016 at 6:25 PM, William Hermans <yyrk...@gmail.com> wrote:
> Robert, oh right the other bit of information I needed to let you know
> about . . .
>
> debian@beaglebone:~$ cd /opt/scripts/tools/developers/
> debian@beaglebone:/opt/scripts/tools/developers$
an apt-get update. But
somehow, I don't think that'd work ;)
On Thu, Dec 29, 2016 at 6:12 PM, William Hermans <yyrk...@gmail.com> wrote:
>
> On Thu, Dec 29, 2016 at 6:05 PM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>> You just stumbled on the biggest is
On Thu, Dec 29, 2016 at 6:05 PM, Robert Nelson
wrote:
> You just stumbled on the biggest issue...
>
> Debugging's going to be fun.. Specially if the end user doesn't have
> a usb-serial cable..
>
> After u-boot patches the device-tree, the kernel will never know..
>
29, 2016 at 5:53 PM, Robert Nelson <robertcnel...@gmail.com>
wrote:
> On Thu, Dec 29, 2016 at 6:31 PM, William Hermans <yyrk...@gmail.com>
> wrote:
> >
> >
> > On Thu, Dec 29, 2016 at 3:05 PM, Robert Nelson <robertcnel...@gmail.com>
> > wrote:
&g
le the
kernel / userspace cap manager, or the uboot cape manager? The later
doesn't make sense to me. what who says that it needs to ?
On Thu, Dec 29, 2016 at 5:36 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Thu, Dec 29, 2016 at 3:16 PM, Robert Nelson <robertcnel...@g
On Thu, Dec 29, 2016 at 3:16 PM, Robert Nelson
wrote:
> > First issue... Now the Kernel Cape Manager get's in the way, i need to
> > pass a global kill switch (or find the global disable), right now you
> > have to "disable" capes loaded by U-Boot.. (you don't have too,
On Thu, Dec 29, 2016 at 3:05 PM, Robert Nelson
wrote:
> Okay, second pass more things work, more corner cases to fix...
>
Does this replace the current method? Yes, I'm thinking for v4.10.x+ ;)
>
> What have you tested it on? Just BB-UART2-00A0.dtbo and then i wrote
Not to mention that redesigning the same processor with a different GPU in
it would cost a lot of money too. But that does not explain the newer
processors with integrated GPU's from the same company.
On Wed, Dec 28, 2016 at 6:42 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
&
On Wed, Dec 28, 2016 at 6:20 PM, Brett Sawyer
wrote:
> Thank you Robert! FBDEV is exactly what I need for this project so I'll
> start with option 1. I appreciate the work you have put into the
> beagleboard.org projects. I remember the beagleboard-xm had similar
>
ald
>
> On Wed, Dec 28, 2016 at 7:31 PM, evilwulfie <evilwul...@gmail.com> wrote:
>
>> why does this person repost these emails without adding any comments ? ?
>>
>> On 12/28/2016 5:44 PM, chao.ruth via BeagleBoard wrote:
>> > -------
Anyway, this is pretty slick. How long do you figure it'll take before this
functionality come into the default uboot ?
On Wed, Dec 28, 2016 at 9:36 AM, William Hermans <yyrk...@gmail.com> wrote:
> Robert,
>
> Have you created a script that removes all the unnecessary kernel m
Robert,
Have you created a script that removes all the unnecessary kernel modules
loaded superfluously at boot ? I mean there are a lot of them, and I'd say
that 99% of them in most cases will just be wasting a lot of memory . . .
On Wed, Dec 28, 2016 at 9:34 AM, William Hermans <y
asier to test, and something I could also test in hardware
> right away.
>
> On Wed, Dec 28, 2016 at 8:27 AM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>> On Wed, Dec 28, 2016 at 9:25 AM, William Hermans <yyrk...@gmail.com>
>> wrote:
>>
.
On Wed, Dec 28, 2016 at 8:27 AM, Robert Nelson <robertcnel...@gmail.com>
wrote:
> On Wed, Dec 28, 2016 at 9:25 AM, William Hermans <yyrk...@gmail.com>
> wrote:
> > On Wed, Dec 28, 2016 at 8:23 AM, Robert Nelson <robertcnel...@gmail.com>
> > wrote:
>
On Wed, Dec 28, 2016 at 8:10 AM, Kevin Cox wrote:
> Hello
>
> I am trying to enable and use eqep0 on my BBB (kernel 4.4.30-ti-r64) and
> am encountering a pin conflict (pin 107) between the eqep driver and mcasp
> driver
>
> From dmesg output:
>
> [ 41.150493] eqep
On Wed, Dec 28, 2016 at 8:23 AM, Robert Nelson <robertcnel...@gmail.com>
wrote:
> On Wed, Dec 28, 2016 at 9:10 AM, William Hermans <yyrk...@gmail.com>
> wrote:
> > So what you're telling me that testing for different boards is
> irrelevant ?
>
> That is correc
t; If not, eMMC probably messing with you..
>
> dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10
>
Is a bit heavy handed, and perhaps a bit too overboard.
On Wed, Dec 28, 2016 at 8:10 AM, William Hermans <yyrk...@gmail.com> wrote:
> So what you're telling me that testing for differ
So what you're telling me that testing for different boards is irrelevant ?
On Wed, Dec 28, 2016 at 6:14 AM, Robert Nelson <robertcnel...@gmail.com>
wrote:
> On Wed, Dec 28, 2016 at 4:07 AM, William Hermans <yyrk...@gmail.com>
> wrote:
> > By the way, I could test
By the way, I could test with 3 different boards. and A5A, an Element14
RevC, and an BBG.
On Wed, Dec 28, 2016 at 3:04 AM, William Hermans <yyrk...@gmail.com> wrote:
> So . . .
>
> On Fri, Dec 23, 2016 at 3:50 PM, Robert Nelson <robertcnel...@gmail.com>
> wrote:
>
>
So . . .
On Fri, Dec 23, 2016 at 3:50 PM, Robert Nelson
wrote:
> Okay, i have a version of u-boot with overlays enabled, ready for some
> basic testing..
>
> *Background***
>
> in u-boot we are doing:
>
> dtb= is loaded at
Generally, all you need is '&' to send the process to the background. So if
I had a Nodejs script called 'app.js' . . .
$ node app.js &
This would start app.js through node, then send the process into the
background. Giving me a PID which I could use later to kill the process.
On Tue, Dec 27,
On Mon, Dec 26, 2016 at 5:19 PM, Denis Cosmin wrote:
> I wanted to power an Arduino and I didn't want to use a relay.
>
Technically speaking, what you're asking I do think is possible. When using
a battery, the beaglebone will still continue running after the 5VDC input
On Fri, Dec 23, 2016 at 6:15 PM, Robert Nelson
wrote:
>
> the cpsw/eth0 is just broken. ;) i saw on github (irc zmatt) was looking
> at it:
>
> https://github.com/dutchanddutch/bb-kernel/commit/
> 0c720957b43a8cea423b80e9fa8772ddb41c186c
hmmm, I wonder if that works
On Fri, Dec 23, 2016 at 5:58 PM, Robert Nelson
wrote:
> For those interfaces, there's not a lot of overlay loading issues on
> the kernel side. The biggest change, you should see your pin's taken
> earlier and more consistently at bootup. You can also optimize your
>
Robert,
So, I have a custom overlay for a physical custom cape . . . as of this
moment, I have a few gpio's( I think around 22 ish ), 6 PWM's,, and
eventually I can put an ADC into that same overlay. Right, now for the ADC
I'm just loading the "stock" ADC overlay for ADC functionality.
On Fri, Dec 23, 2016 at 11:21 AM, John Dammeyer
wrote:
> Ah the vigilante police strike again with zero information and instead the
> usual "you're an idiot for posting here comment". I'm sorry you don't
> understand this question. If you don't have anything useful
On Fri, Dec 23, 2016 at 10:36 AM, John Dammeyer
wrote:
> My apologies Robert,
> I realize now after seeing your answer (sarcastic?) that the lack of a
> question mark at the end of the sentence left it as a statement rather than
> a question. So I'll start with the
On Wed, Dec 21, 2016 at 1:56 PM, roboknight <robokni...@gmail.com> wrote:
>
>
> On Tuesday, December 20, 2016 at 3:27:44 PM UTC-5, William Hermans wrote:
>>
>>
>>
>> On Tue, Dec 20, 2016 at 10:02 AM, roboknight <robok...@gmail.com> wrote:
>>
>
uch
> material!
>
> I'm wrapping up some documentation, want to get it done, RemoteProc
> shutdown is a secondary issue so I will put it on the backburner until I
> have another look at the kernel.
>
> On Wednesday, December 21, 2016 at 9:28:38 AM UTC-5, William Hermans wrote:
>>
Greg, have you read the remoteproc kernel documentation ? I did like a year
ago, and I do want to say there is a method to halt remoteproc. But I'm not
sure, and even if I did read that. There is no telling if it's actually
been implemented yet into our kernel / kernel modules . . .
On Wed, Dec
the power input to the beaglebone. Where the power is disconnected depends
on whether you're externally powering via Geralds, and mine( for that
matter ) preferred method. Or via a LiPO connected directly to the
beaglebone / PMIC.
On Wed, Dec 21, 2016 at 7:14 AM, William Hermans <yyrk...@gmail.com>
On Wed, Dec 21, 2016 at 7:00 AM, Jason van Belzen
wrote:
> I understand that an external battery cape is the best solution.
> Do you know if the following is possible from linux perspective:
>
>- We run on battery and DC power
>- If we detect DC power loss, we
On Wed, Dec 21, 2016 at 6:42 AM, Gerald Coley
wrote:
> In my experience, and external battery is the way to go. I designed a cape
> for that a log time ago. That let's you support multiple types of battery
> chemistry and multiple configurations.
>
> Gerald
>
> I think
On Wed, Dec 21, 2016 at 6:26 AM, Jason van Belzen
wrote:
> Thanks for your reply.
>
> How does this issue damage the processor?
>
> Jason
>
As Gerald already said, I do not believe it does either. What does happen
however is that the board when in this state through
On Dec 18,
> 2016, at 7:37 PM, 'Luther Goh Lu Feng' via
> BeagleBoard <beagleboard@googlegroups.com>
> wrote:
>
>
> On Monday, December 19, 2016 at
> 4:04:47 AM UTC+8, William Hermans wrote:
> On Sun, Dec 18, 2016 at
> 1:00 PM, 'Luther Goh Lu Feng' via BeagleBoard &l
On Tue, Dec 20, 2016 at 1:28 PM, Renzo Fabián wrote:
> Is there a repository that allows install libpruio using "apt-get install"
> in Debian 7 or 8?
>
> Thanks.
>
No. At least not form the official, or RCN repo's.
--
For more options, visit http://beagleboard.org/discuss
would need to be contacted for this type of
situation. But it's likely the maintainer for this part of the kernel.
On Tue, Dec 20, 2016 at 1:27 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Tue, Dec 20, 2016 at 10:02 AM, roboknight <robokni...@gmail.com> wrote:
On Tue, Dec 20, 2016 at 10:02 AM, roboknight wrote:
At the underlined point, I believe ep->desc is NULL because using the
kernel and an arm objdump variant,
>
> I located the assembly that is causing the NULL dereference. Inside of
> usb_endpoing_dir_out, it tries to
>
william@beaglebone:~$ uname -r
4.4.27-ti-r62
william@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-10-30
william@beaglebone:~$ head /uEnv.txt
##These are needed to be compliant with Angstrom's 2013.06.20 u-boot.
loadaddr=0x8200
fdtaddr=0x8800
rdaddr=0x8808
On Tue, Dec 20, 2016 at 7:16 AM, Jay Doobie wrote:
> Is there a power supply requirement difference between the BBB and a BBBW?
>
>
You should get, and read the SRM for the BBBW. But there almost certainly
is.
>
> The BBB works great outside of my machine connected to USB
ly that came with my 3d printer may
> either be faulty or at it's limit of what it can supply. Going to look
> into a slightly beefier supply.
>
> On Monday, December 19, 2016 at 3:42:01 PM UTC-5, William Hermans wrote:
>>
>> Well I do not have a BBBW, but I do have an rP
You know, I've had my hand on 4 BBB's and well over 40 BBG's and have yet
to see this problem manifest it's self.
On Mon, Dec 19, 2016 at 3:17 PM, wrote:
> Hi Gerald,
>
> I saw your comment in response to the question about another revision to
> the BBB. There is a
On Mon, Dec 19, 2016 at 3:02 PM, Ross Morrison wrote:
> On the latest images page(https://beagleboard.org/latest-images) has
> the IOT version replaced the plain jane console image? I would really
> like to build from the latest basic console image then add options as
> needed.
On Mon, Dec 19, 2016 at 1:40 PM, Graham wrote:
> I would recommend putting the BBB directly on the Ethernet network,
> Then connect to it via Ethernet.
>
> The USB-Bridge is useful only in certain simple connection configurations.
>
> --- Graham
>
Some people,
Well I do not have a BBBW, but I do have an rPI 3. Disabling power save at
boot is fairly easy.
william@rpi:~$ sudo nano /etc/rc.local
Add: /sbin/iw dev wlan0 set power_save off
william@rpi:~$ sudo reboot
william@rpi:~$ iwconfig wlan0
wlan0 IEEE 802.11bgn Mode:Master Tx-Power=31 dBm
On Sun, Dec 18, 2016 at 1:00 PM, 'Luther Goh Lu Feng' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> Noted your comments. In case it isn't clear, I am referring to Ubuntu
> Core[1], not Ubuntu. My use case, I am looking at deploying BBB as IoT
> gateway devices and I am assessing Ubuntu
I'm not sure I understand the rationale behind wanting to run Ubuntu on the
Beaglebone hardware. Doing so would present all sort of problems for the
end user attempting to replicate what others do with this platform using
Debian. Also, while this hardware platform *can* run a desktop environment.
beaglebones was built on a Raspberry Pi 3 running Raspbian Jessie, with gcc
4.9.x.
The point I'm trying to make here, is that this package would, and does
work for more than just the beaglebones.
On Sun, Dec 18, 2016 at 12:15 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
>
On Sun, Dec 18, 2016 at 11:56 AM, Stephane Charette <
stephanechare...@gmail.com> wrote:
> By default when I install a BB with one of the usual RCN builds, the repos
> as defined in /etc/apt/sources.list are set to the following:
>
> deb http://httpredir.debian.org/debian/ jessie main contrib
On Sun, Dec 18, 2016 at 5:05 AM, Elena ``of Valhalla'' <
elena.valha...@gmail.com> wrote:
>
> Other hardware that may be problematic of course is new hardware which
> requires a new kernel, and if you're not already using testing (as
> mentioned in the other email), usually there is always one in
On Sun, Dec 18, 2016 at 2:40 AM, Elena ``of Valhalla'' <
elena.valha...@gmail.com> wrote:
> On 2016-12-15 at 14:49:25 -0700, William Hermans wrote:
> > Debian, and Ubuntu use different init daemons, at least the last I
> > read. Although I've also read that Canonical was
>From my own perspective, it does not matter one single bit. I suscribe to
the beagleboard.org google group, i get all mails from that group. No idea
of sub groups, or whatever. . . .quite honestly I don;t even care. If i
know the answer or can give some clues, I'll answer, or give some clues. .
Jay,
So keep this in mind, 99% chance, what you've done, you've somehow screwed
up. Don't take this as a negative response please. But more or less a
realistic response. I've done "similar" myself. the whole time, I might be
thinking . .. "I'm going to let x.y.z have it on the groups . . ." only
Thats a case where you make the call.
On Fri, Dec 16, 2016 at 5:12 PM, Gregg Harrington wrote:
> Is this a case I should RMA it? Or should I just solder it down?
>
> Thanks,
>
> Gregg
>
>
> On Friday, December 16, 2016 at 2:43:52 PM UTC-8, RobertCNelson wrote:
>>
>>
lt on boot.
>
> /Jason
>
> On Friday, December 16, 2016 at 1:41:28 PM UTC-5, William Hermans wrote:
>>
>> So whatever way that works for you, is the right way. But yes, in my own
>>> opinion loading from uEnv.txt is the proper way. As the pin configurations
&
lopers$ sudo reboot
>
> Then your custom overlay will be "injected" into the initramfs, and
> properly load at boot.
>
On Fri, Dec 16, 2016 at 11:39 AM, William Hermans <yyrk...@gmail.com> wrote:
> Jay,
>
> If by "updating" you mean your overlay isn't loading
Jay,
If by "updating" you mean your overlay isn't loading at boot. That would be
because the overlay is not in the initramfs. Which is needed for the latest
images. I actually posted on the groups about this a few days go, so I'll
find my post and copy paste the procedure here.
If this is not
On Thu, Dec 15, 2016 at 8:40 PM, Jay Doobie wrote:
> Sadly this did not work. I'm using the default kernel/setup from the
> image bone-debian-8.6-lxqt-4gb-armhf-2016-11-06-4gb.img.xz
>
By the way . . .
Yes, I can read the dts files fairly easily. The problem is knowing which
> overlays are included for a given device.
>
Everything in /lib/firmware/
On Thu, Dec 15, 2016 at 6:18 PM, William Hermans <yyrk...@gmail.com> wrote:
>
>
> On Thu, Dec 15, 2016 a
On Thu, Dec 15, 2016 at 3:06 PM, codemonkey wrote:
> Your intuition seems to be very good. After much testing, I now can see
> that as soon as I enable "dtb=am335x-boneblack-emmc-overlay.dtb" and
> reboot, the system does come up but wlan0 is no longer known. By that I
> mean
If you load overlays that are already included in your image, then you do
not have to update the initramfs. But if you create your own custom
overlay, it will not be included in the initramfs.
On Thu, Dec 15, 2016 at 4:10 PM, Phil wrote:
> Thanks for the info. I am not so
cycle. Which by the way is why Debian is behind the curve
for software, and hardware support. If something does not "make the grade"
within a certain time frame, then that something does not make it into the
next stable release of the distro. Which many, many people prefer.
On Thu, Dec 15,
On Thu, Dec 15, 2016 at 12:36 PM, Phil wrote:
> On Thursday, December 15, 2016 at 11:20:13 AM UTC-6, Phil wrote:
>
I have written a device tree overlay that incorporates SPI0, SPI1 and the
> PRUSS, and where SPI1 uses a GPIO for a 2nd chip select. Can I load this in
> the
On Thu, Dec 15, 2016 at 12:03 PM, codemonkey wrote:
> Hello William, thank you for the prompt response. First of all, I have to
> say that I have very little experience with the device tree, although I did
> use dtb-rebuilder to enable SPI back in the linux v3.8 days. So, my
There's also a software package known as fake hwclock. It's not a real time
clock, and perhaps it'll even lose time over long periods. But it seems to
do a reasonable job of keeping time on a system close.
We actually use DS3232 on those devices that *need* to keep accurate time.
On Thu, Dec
On Thu, Dec 15, 2016 at 3:02 AM, Heinz Hummel
wrote:
> I don't know what the reason is but I personally prefer Ubuntu because it
> is easier to use, it has a bigger community which is more responsive and
> more friendly and one can choose to use a LTS version (and stay
Additionally, this is a reason for you to buy a serial debug cable, or
module. With such a device, you'd probably know exactly why the board fails
to boot, or at minimum have a really good idea based on uboot output.
On Wed, Dec 14, 2016 at 5:18 PM, William Hermans <yyrk...@gmail.com>
That cape does work on the Beaglebone green. However, the Beaglebone green,
and Beaglebone black both have ethernet, where the Beaglebone green
wireless has a wifi network interface. So, this is an assumption but here
are two points of contention:
1. Since the BBGW has wifi and the Beaglebone
IF you're using Windows, this is most likely a Windows issue. The thing
I've found in the past when dealing with the USB g_ether gadget driver. Is
that when upgrading from one image to another on the Beaglebone you may
have to upgrade the driver on the Windows host side. This is one place
where
You should not have to upgrade the device tree compiler( dtc ). As each
kernel version, as provided with the latest images have the proper device
tree compiler. However, assuming, running Wheezy, then upgrading to a newer
kernel( 3.8.x to 4.x ) the device tree compiler would have to be upgraded
at
The Logitech 920C I believe it is is reported to work very well with the
Beaglebone.
On Tue, Dec 13, 2016 at 10:37 AM, Andrew Goh wrote:
> On Sunday, July 14, 2013 at 7:08:45 PM UTC+8, James Richins wrote:
>>
>> Is it possible for there to be an interface board for the
0x05
>
>
> >;
> };
>
> };
> };
>
> //Allowed us to have the differents uio
> fragment@1{
> target = <>;
> __overlay__{
> status = "okay";
> pinctrl-
rease over time. The cost will come
down.
On Mon, Dec 12, 2016 at 12:39 PM, Ross Morrison <r...@buy-ei.com> wrote:
> On Mon, 12 Dec 2016 12:29:37 -0700
> William Hermans <yyrk...@gmail.com> wrote:
>
> > The beaglebone black wireless seems to have HDMI, where the beaglebo
Well, that, and the beaglebone black wireless also does not have the two
grove connectors. Which personally I found no use for.
On Mon, Dec 12, 2016 at 12:29 PM, William Hermans <yyrk...@gmail.com> wrote:
> The beaglebone black wireless seems to have HDMI, where the beaglebone
>
The beaglebone black wireless seems to have HDMI, where the beaglebone
green's do not.
On Mon, Dec 12, 2016 at 12:14 PM, Ross Morrison wrote:
> Now that the BBBW is out (in stock), my question is: Which one, the BBBW
> or the BBGW board for a project? This project will be small
I suspect that you need to make these changes in the overlay file you use
to initially configure the PRU's.
On Mon, Dec 12, 2016 at 9:39 AM, TJF wrote:
> Hi malkowki!
>
> Sorry, I cannot really help. Just some info: The same commands work well
> for me on several kernel
I use a combination of an NFS share, and a samba share. So . . .
Linux server == NFS share to BBB, and Samba share to Windows workstation.
What this nets me is the ability to edit files from Windows directly on the
BBB. Or more correctly on the Linux server, which also hosts a share to the
BBB.
There is no FAT partition in the images since . . . over a year now.
On Thu, Dec 8, 2016 at 4:56 AM, DragosP wrote:
>
> Hi,
>
> I run Debin beaglebone 4.4.36-ti-r72 on Beaglebone Black Rev C.
>
> I want to mount the FAT partition I see in Windows, to /media/folder_name
> in
Anyway, sorry if that "stings" but hey, it's pretty much the truth. People
have lives of their own and contribute what they can, when they can. But I
would assume most people are pretty busy doing stuff for people who
actually pay them. A lot of the time.
On Tue, Dec 6, 2016 at 10:10 P
Did you expect someone to do all the work for you ? But yes, I've
experienced the same thing. So "free" as in beer, open sourced software.
You get what you pay for. If you need something more, then it's up to you
to do that for yourself. Or pay someone else to do it for you.
On Tue, Dec 6, 2016
Nope, actually that persons overlay file is wrong. So yeah I don;t know
time to learn Linux and start troubleshooting your problems ;)
On Mon, Dec 5, 2016 at 8:47 PM, William Hermans <yyrk...@gmail.com> wrote:
> Actually the last bit probably wont work because:
>
> william@beagle
o bank.
On Mon, Dec 5, 2016 at 8:28 PM, William Hermans <yyrk...@gmail.com> wrote:
> On Mon, Dec 5, 2016 at 7:30 PM, acheesehead <acheeseh...@gmail.com> wrote:
>
>> Tried your workflow today without success. Everything is OK up to the
>> lsmod | grep w1 step. I only get
On Mon, Dec 5, 2016 at 7:30 PM, acheesehead wrote:
> Tried your workflow today without success. Everything is OK up to the
> lsmod | grep w1 step. I only get the w1_gpio entry. I am not a Linux kernel
> expert, so I don't know how to troubleshoot why the other entries
: crc=eb YES
19 01 4b 46 7f ff 07 10 eb t=17562
Anyway, dead horse . . . point made?
On Mon, Dec 5, 2016 at 6:41 PM, William Hermans <yyrk...@gmail.com> wrote:
> I repeated this process for P8.14, and it works fine. This is just to let
> others who may not be aware that
> gpios = < 28 GPIO_ACTIVE_HIGH>;
On Sat, Dec 3, 2016 at 3:11 PM, William Hermans <yyrk...@gmail.com> wrote:
> @ Sebastian
>
> Ah I forgot to mention loading capes from /boot/uEnv.txt. So . . .
>
> *william@beaglebone:~$* cat
@ Sebastian
Ah I forgot to mention loading capes from /boot/uEnv.txt. So . . .
*william@beaglebone:~$* cat /boot/uEnv.txt |grep cape
#cmdline=coherent_pool=1M quiet cape_universal=enable
video=HDMI-A-1:1024x768@60e
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=
or multiples, in order to pull that
off.
So having an emmc flasher image of some sort is probably the quickest and
least expensive way to go. Then you just put the sdcard into a board, and
boot -> flash to emmc. Then move on to the next system.
On Sat, Dec 3, 2016 at 2:29 PM, William Hermans &l
Robert uses rsync I think for his cloning image( emmc flasher images ).
But I think the best, easiest, and most consistent way to clone an image
would be to use dd. This has the benefit of creating a bit for bit exact
copy of the image in question. However, one downside to using dd is that if
501 - 600 of 4107 matches
Mail list logo