I upgraded to BeagleBone Black 8.4 and the problem went away. After a
week of testing, I can't get the error any more.I don't see any fixes
in the 8.4 release notes. But I'll call this fixed unless I see it again.
On Wednesday, June 22, 2016 at 8:15:55 AM UTC-7, William Hermans wrote:
>
Thanks, I think I'll start over!
Is there a way to install/execute big programs (like cheese) on the
sd-card?In the past I've mounted the sd card, but I've never been able
to boot from the emmc while then installing and running apps from the
sd-card?
On Monday, June 27, 2016 at
On Tue, Jun 28, 2016 at 6:11 PM, Greg Wilson-Lindberg
wrote:
> Does anyone know how to get in touch with Robert C Nelson? The Digikey
> TechXchange has been down for at least a week, and TechXchange has been
> removed from the Digikey main page.
>
> I've got some questions
Well, I don't know where to start. A detailed diagram of the entire system
hookup would help.
Gerald
On Tue, Jun 28, 2016 at 7:11 PM, Wally Bkg wrote:
> It happened again, my Beaglebone White crashed as a thunderstorm moved
> through the area. It is on a UPS, the same
It happened again, my Beaglebone White crashed as a thunderstorm moved through
the area. It is on a UPS, the same UPS as my router ASUS RT-AC56 and Raspberry
Pi2, neither of which glitched in any way.
It does have a lot of interface wiring hooked up but these are very thoroughly
EMP protected
Does anyone know how to get in touch with Robert C Nelson? The Digikey
TechXchange has been down for at least a week, and TechXchange has been
removed from the Digikey main page.
I've got some questions about the kernel that is used in Debian and need to
get in touch with him.
Regards,
Greg
Hello,
I'm using the beaglebone black using Debian Wheezy currently on the website.
I'm trying to allocate memory in ddr for PRU to write data to. Inside
"/sys/class/uio/uio0/maps/map1/size" it report a hex of 0x4 or 262144
bytes of data. I try changing the size using "modprobe uio_pruss
Hi,
Hope you doing Well !!!
Here is our *Implementing partner **Requirement*, Please go through the
below requirement and send us suitable consultant with their *updated
resume, rates and Contact details ..*
*Role:*
* Test Engineer With Point of Sale Location: Jacksonville(FL)*
*Work
Hi William,I want the kernel tree so that I can build a kernel module. I'll follow your advise and start with a working image. It might be easier that way to get a working tree of the kernel instead of bothering
I followed all the steps explained by lucas. But at make it is saying that
there are no targets specified. which one should i specify?
On Tuesday, March 1, 2016 at 6:54:32 AM UTC-5, lucas wrote:
>
> Wow, I think it works. Thanks a bunch :)
>
> This is what I did.
>
> In uEnv.txt:
> 1.)
How did you solve the failed gettin mclk error?
On Wednesday, August 19, 2015 at 9:40:27 AM UTC-4, Dileep D R wrote:
>
> [ 15.986046] tlv320aic32x4 2-0018: Failed getting the mclk. The current
> implementation does not support the usage of this codec without mclk
> ..
> [ 16.156996]
@TJF, I didn’t copy the PRU developers because I believe there is nothing in
your response that would be of interest to them.
It is hard to keep up with your changing priorities. Addressing your security
issues, you never answered my original question. How are you going to install
PRU
BY the way, the latest console image for me, with Nodejs 4.6.2 and npm 3.10
only weights in at around 400M total. I'd expect before Nodejs sme where
aroudn 280M maybe slightly less. I didn't check . . .
On Tue, Jun 28, 2016 at 6:53 AM, William Hermans wrote:
> Hesham,
>
> I
Hesham,
I think at this point, the safest thing to do is to get the newest
standalone( non flasher ) console image, boot it, and observe the serial
debug output.
After that, check out the file structure, and perhaps rip out some needed
files to put into your system.
Question though. Is there a
There is nothing but the /boot/uEnv.txt that I sent you earlier. Also,
there is no initrd.img as well in the tree.
I followed the steps in the eewiki page but this is what I got!
On Monday, June 27, 2016 at 1:57:33 PM UTC-4, William Hermans wrote:
>
> Ok, no nothing there s critical for
Hello Przemek!
Thanks for joining this discussion.
Am Montag, 27. Juni 2016 18:00:16 UTC+2 schrieb Przemek Klosowski:
>
> This is a valid design pattern and you did very impressive things with
> it, but it's not compatible with the basic design of Linux hardware
> integration: I don't know of
With this line in uEnv.txt I solved my problems with pins configuration of
PWM and SPI interfaces:
cape_enable=bone_capemgr.enable_partno=BB-SPIDEV1,am33xx_pwm,BB-PWM0
Frankly, I don't know why now it is not possible to load these DTOs from
Linux shell.
I hope this will help.
Best regards,
17 matches
Mail list logo