On 2017-05-10 05:31, Robert Nelson wrote:
On Tue, May 9, 2017 at 9:16 PM, Riko Ho wrote:
Hi Robert,
Is that possible that I have "verbose" in "dd", I can not see what it's
doing when writing ??
No, not with dd directly.. With another tool called "pv" indirectly..
Use google.com to look it u
On Tue, May 9, 2017 at 10:49 PM, Riko Ho wrote:
> Hi Robert,
> after I modify it, how can I hook it with my beagle ?
Hook what up?
I'm sorry, but it's pretty obvious..
You need to start with something "WAY" smaller.
LXDE is going to be too much of a project for your "first" build/hookup/etc..
On Tue, May 9, 2017 at 10:48 PM, Riko Ho wrote:
> Hmmin that case, I want to run qemu on my ubuntu host
Nice thought, BUT the image-builder script is already using "qemu"
when you run it on an x86. So your not actually doing or changing
anything..
> I tried to rebuild debian 8 now...and
On Tue, May 9, 2017 at 10:35 PM, Riko Ho wrote:
> so I copy img-builder and run it on my beagle board ?
I personally use, WandBoard's, omap5_uevm's, X15's, or Jetson's tk as
they have more ram and more processing power then teh BBB..
But if you want to run it on the BBB go right ahead..
> how
On Tue, May 9, 2017 at 9:11 PM, Riko Ho wrote:
> do you mean that I need to run qemu service on my ubuntu host system ? how
> to do that ?
>
No, it means qemu (google qemu to see what it is) choked on the armhf
-> x86 translation.. which is why the readme in the image-builder
project says to use
On Tue, May 9, 2017 at 9:16 PM, Riko Ho wrote:
> Hi Robert,
>
> Is that possible that I have "verbose" in "dd", I can not see what it's
> doing when writing ??
No, not with dd directly.. With another tool called "pv" indirectly..
Use google.com to look it up, but it's not accurate as it'll say 1
On May 9, 2017 8:47 PM, "Riko Ho" wrote:
Hi Robert, after ./setup_sdcard.sh command :
root@bianchi-HP-Pavilion-dv6-Notebook-PC:/home/bianchi/
Documents/image-builder/deploy/debian-7.11-lxde-armhf-2017-05-09# sudo
./setup_sdcard.sh --img-2gb bone-debian-7.11-2017-05-10 --dtb beaglebone \
> ^C
ro
On May 9, 2017 8:36 PM, "Riko Ho" wrote:
Hello everyone,
I have question related with this command in https://github.com/
beagleboard/image-builder :
sudo ./setup_sdcard.sh --img-4gb BBB-eMMC-flasher-debian-7.X-201Y-MM-DD \
--dtb beaglebone --enable-systemd --bbb-flasher \
--bbb-old-bootloader-i
I have to read from ADC at 20khz in a continuous manner. Maybe I need to
use DMA and Timer (or another way).
I read some documents, but I still don't know how to deal with ADC, DMA and
Timer interrupt from linux filesystem.
Very helpful if I have some clues. Thank for advance.
--
For more opti
Hello everyone,
I have question related with this command in
https://github.com/beagleboard/image-builder :
|sudo ./setup_sdcard.sh --img-4gb BBB-eMMC-flasher-debian-7.X-201Y-MM-DD
\ --dtb beaglebone --enable-systemd --bbb-flasher \
--bbb-old-bootloader-in-emmc|
which file is being used rel
On Monday, May 8, 2017 at 8:01:11 PM UTC-5, RobertCNelson wrote:
>
> On Mon, May 8, 2017 at 7:17 PM, Mark Copper > wrote:
> >
> >> btw, one issue with this new setup, WiFi is slower with the dual
> >> connections, in my testing switching from v4.4.x -> v4.9.x saw an
> >> increase from 55kb/s
On Tue, May 9, 2017 at 11:20 AM, William Hermans wrote:
> I'm noticing on the second system spi_omap2_mcspi is loading as well. One
> thing I have also noticed is that with recent TI kernels,kernel modules
> seem to remove themselves when not needed, or possibly conflicting with
> another driver.
I'm noticing on the second system spi_omap2_mcspi is loading as well. One
thing I have also noticed is that with recent TI kernels,kernel modules
seem to remove themselves when not needed, or possibly conflicting with
another driver. Which is a good thing, but also, could potentially be a bad
thing
On Tue, May 9, 2017 at 1:08 PM, Gaurav wrote:
> Hello,
> Where does uboot log what capes have been loaded? clearly dmesg | grep bone
> does not show any capes loaded by uboot.
It gives a hint:
[2.376544] bone_capemgr bone_capemgr: slot #0: "auto loading
handled by U-Boot"
plug in a serial a
On Tue, May 9, 2017 at 12:50 PM, Gaurav S wrote:
> Hello,
> http://elinux.org/4D_4.3_LCD_CAPE
>
> Thanks for the reference Robert, that solved the issue. Apparently I should
> not be mixing uboot with "bone_capemgr.enable". I am not sure why did the
> /dev/spidev* work on the system without the LC
Hello,
Where does uboot log what capes have been loaded? clearly dmesg | grep bone
does not show any capes loaded by uboot.
Thanks
Gaurav
Gaurav
On Tue, May 9, 2017 at 12:50 PM, Gaurav S wrote:
> Hello,
> http://elinux.org/4D_4.3_LCD_CAPE
>
> Thanks for the reference Robert, that solved the i
Hello,
http://elinux.org/4D_4.3_LCD_CAPE
Thanks for the reference Robert, that solved the issue. Apparently I should
not be mixing uboot with "bone_capemgr.enable". I am not sure why did the
/dev/spidev* work on the system without the LCD.
Thanks again,
gaurav
On Tuesday, May 9, 2017 at 12:38
Which lcd?
For spidev please read:
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Override_external_capes
On May 9, 2017 12:16 PM, "Gaurav S" wrote:
Hello All,
With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone
boards one with LCD plugged in (SYS1) and the
Hell,
Thanks for the response. Seems like spidev available on both systems.
For sys1 (beaglebone+LCD)
debian@beaglebone:~$ lsmod
Module Size Used by
omap_aes_driver23912 0
omap_sham 26513 0
omap_rng5544 0
rng_core9066 1 o
On Tue, May 9, 2017 at 10:16 AM, Gaurav S wrote:
> Hello All,
> With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone
> boards one with LCD plugged in (SYS1) and the other stand alone beagle bone
> (SYS2), both running latest debian lxqt 2gb image (may 7 2017). The curious
> t
Hello All,
With LCD, it seems like SPI is behaving awkwardly. I have two beagle bone
boards one with LCD plugged in (SYS1) and the other stand alone beagle bone
(SYS2), both running latest debian lxqt 2gb image (may 7 2017). The curious
thing over here is that before u-boot spi was working just
A few things about your code.
First, if you're concerned about performance, you're using the wrong
language. Wrong type of a language for that matter. You should be using C,
C++, or ASM. *IF* you're concerned about performance.
Secondly, calling a time() related function in your main loop, every
On Tue, May 9, 2017 at 1:47 AM, wrote:
> Hi there,
>
> I´m pretty new to Linux and the BBB. I´m using Debian Jessie and
> struggling with the DTO. I think I have an little idea now how it works. I
> try to export a dtbo to the slots.
>
> this is what i get when i cat the slotsfile:
>
> debian@bea
hello to every one,here is Yangyang.I want to know,how can test the
polling-frequency of I/O-port on beaglebone black,and what is the maximum
speed of the frequency ? The max. speed what I test is around 27kHz. Hope
there is anyone can help me
contact via ahfy...@gmail.com. Thanks.
Here is my
Hi there,
I´m pretty new to Linux and the BBB. I´m using Debian Jessie and struggling
with the DTO. I think I have an little idea now how it works. I try to
export a dtbo to the slots.
this is what i get when i cat the slotsfile:
debian@beaglebone:/lib/firmware$ cat
/sys/devices/platform/bone
firstly thanks for your response, although i was actually more interested
in a suggestion of a register, maybe, that could show me the status of the
interrupts..meaning if there is a register showing if there is an interrupt
produced or not...
To return to the problem, i have tried with a counte
On May 9, 2017 12:43 AM, "deepan muthusamy" wrote:
Hi,
Iam using beaglebone blue
I wrote the sdcard using the image dowloaded from this site() and
inserted the sdcard into the board and powerup the board. booting process
takes place. After all LED,S went off, i disconnected power a
On May 9, 2017 2:44 AM, "Riko Ho" wrote:
Everyone,
I tried to run :
./beagleboard.org_jessie_image.sh, and at the end I got below :
Processing triggers for libc-bin (2.19-18+deb8u9) ...
Processing triggers for initramfs-tools (0.120+deb8u3-1rcnee0~bpo80+20170219)
...
update-initramfs: Generati
i am able to named pipe my stream to a file and then CLI ffmpeg it from
h264es to mp4 no problem,
but when i launch the same ffmpeg command using execv()
char* execargs[]={PATH_TO_FFMPEG,"-loglevel","debug","-framerate","30","-y",
"-f","h264","-i","/tmp/fifocam1.h264","-c:v","copy","-an","-video_s
Everyone,
I tried to run :
./beagleboard.org_jessie_image.sh, and at the end I got below :
Processing triggers for libc-bin (2.19-18+deb8u9) ...
Processing triggers for initramfs-tools
(0.120+deb8u3-1rcnee0~bpo80+20170219) ...
update-initramfs: Generating /boot/initrd.img-4.4.62-ti-r99
Proces
30 matches
Mail list logo
