I wanted to make the ip address in each distro instance I test different so
that they will have different keys on my desktop
On Sun, Nov 2, 2014 at 4:14 PM, John Syn wrote:
>
> From: Milton Mobley
> Reply-To: "beagleboard@googlegroups.com"
> Date: Sunday, November 2, 2014 at 3:31 PM
> To: "bea
Hello all,
Still very new to the embedded systems world but really love the BBB so far!
I have a project in which I have to sample 4 analog inputs very quickly (at
least 44.1 kHz).
I initially thought of using an external ADC and hooking that up through
the BBB's McASP
interface, but on second
From: Milton Mobley
Reply-To: "beagleboard@googlegroups.com"
Date: Sunday, November 2, 2014 at 3:31 PM
To: "beagleboard@googlegroups.com"
Subject: [beagleboard] How to change the ip address reported to remote host
over usb on debian image?
> I found the file setup-ubuntu-armhf-3.8.13-bon
The shell file was in the scripts folder of the debian boot partition
On Sunday, November 2, 2014 2:31:51 PM UTC-8, Milton Mobley wrote:
>
> I found the file setup-ubuntu-armhf-3.8.13-bone30.sh, which appears to
> do closely related things, i.e. start dhcp server, start gadget, etc.
>
> How is t
Hello.
I am trying to figure out how to use I/O with my BBB running Debian, but
the more I try the more confused I get. For example: I try to read the
analog inputs using information I find on the web. Per instructions, I
enter
echo cape-bone-iio > /sys/devices/bone_capemgr.*/slots
which i
I found the file setup-ubuntu-armhf-3.8.13-bone30.sh, which appears to do
closely related things, i.e. start dhcp server, start gadget, etc.
How is this file used?
I am guessing it was executed on a Beagle running from sd card with this
image, and after shutdown, the sd card image was copied
t
I had to go to debian jessie (debian-jessie-DI-b2-i386-netinst.iso) to get
version DTC 1.4.
It works now.
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 th
On Nov 2, 2014 1:00 PM, "Peter Gregory" wrote:
>
> Just installed a new image debian-7.7.0-i386-netinst.iso.
>
> pgregory@debian:~/dtb-rebuilder$ dtc -v
> Version: DTC 1.3.0
>
> Is it too old?
> Do I need to compile the device tree under BBB?
Way to old, use 1.4+
>
> pgregory@debian:~/dtb-rebuil
Just installed a new image debian-7.7.0-i386-netinst.iso.
pgregory@debian:~/dtb-rebuilder$ dtc -v
Version: DTC 1.3.0
Is it too old?
Do I need to compile the device tree under BBB?
pgregory@debian:~/dtb-rebuilder$ make
DTC src/arm/am335x-base0033.dtb
dtc: invalid option -- 'i'
Usage:
dtc [o
On Sun, Nov 2, 2014 at 12:45 PM, Curt Carpenter <1cjcarpen...@att.net>
wrote:
> OK thank you -- I'll look for more information on read only rootfs. I
> guess I should plan on avoiding on-board compilation too, since I have no
> way of knowing if, for example, the GNU compilers are sensitive to th
OK thank you -- I'll look for more information on read only rootfs. I
guess I should plan on avoiding on-board compilation too, since I have no
way of knowing if, for example, the GNU compilers are sensitive to the disk
endurance issue.
--
For more options, visit http://beagleboard.org/discus
On Sun, Nov 2, 2014 at 10:38 AM, Peter Gregory wrote:
> I'm setting up my BBB for custom pins
>
> P9-39AIN0 Light Sensor A/D
> P8-19 gpio0[22] 22 0x820 EHRPWM2A RED LED PWM
> P8-13 pgio0[23] 23 0x824 EHRPWM2B GREEN LED PWM
> P9-14 gpio1[18] 50 0x848 EHRPWM1A BLUE LED PWM
>
I'm setting up my BBB for custom pins
P9-39AIN0 Light Sensor A/D
P8-19 gpio0[22] 22 0x820 EHRPWM2A RED LED PWM
P8-13 pgio0[23] 23 0x824 EHRPWM2B GREEN LED PWM
P9-14 gpio1[18] 50 0x848 EHRPWM1A BLUE LED PWM
P8-14 gpio0[26] 26 0x828 GPIO0_26 Sensor 1 Zero Crossing
P8-17 gpio0
You can use one of the overlays here to set the different
UARTS: https://github.com/gntoni/projectM/tree/master/devTree
A good way to test if it is working is to place a wire between pins Tx and
Rx.
You can use minicom
> sudo minicom -b 9600 -D /dev/ttyO1
and check that you can see what you ar
As an alternative you can use https://github.com/ungureanuvladvictor/BBBlfs
. It takes like ~5 mins to flash a fully debian image on the board. I know
a few people that use this tool for production boards. You can customize it
to flash whatever you want to the board.
On Sunday, November 2, 201
Great!
Thanks so much for the help.
Bill
On Sun, Nov 2, 2014 at 4:15 AM, TJF wrote:
>
>
> Am Sonntag, 2. November 2014 01:40:22 UTC+1 schrieb Bill Gray:
>>
>> Am I correct in assuming that the low latency pins are specific to one or
>> the other PRU? For example, should I assume that somethin
The one we use. The same one as everybody uses as users. Boot from the SD
card that flashes the eMMC.
Gerald
On Sunday, November 2, 2014, Srinivasan Shanmugam
wrote:
>
> Dear Beaglebone black Community,
>
> As am newbie to this beaglebone black development board & am stuck with
> this from many
Dear Beaglebone Community,
As am newbie to software update & recovery feature of bricked beaglebone
black in uboot , linux kernel & rootfs
As am trying to implement Software update feature
on ti-sdk-am335x-evm-07.00.00.00 BSPs for beaglebone black ie., automatic
software updates of uboot lin
btw: I miss also the path: "/sys/kernel/debug/omap_mux/"
I found some help in the internet, but all are using this path, what I
doesn´t has.
BBB is brand new.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
Hello!
I try to use the UARTS 1,2,4.
I set up an own device tree and have the files "/dev/ttyO1"
When I send "echo hello > /dev/ttyO1" I get no information out of my cape.
How can I check if the pins are correct in UART mode?
Thank you!
--
For more options, visit http://beagleboard.org/discuss
Dear beaglebone black community,
1. As am newbie in using ti-sdk-am335x-evm-07.00.00.00 where we have uboot
& source code , when am trying to modify the uboot & kernel source code
ie., am trying to add printks in the source code , compiled & flashed the
images onto SD card but am unable to see
Am Sonntag, 2. November 2014 01:40:22 UTC+1 schrieb Bill Gray:
>
> Am I correct in assuming that the low latency pins are specific to one or
> the other PRU? For example, should I assume that something like
> "pr1_pru1_pru_r31_6" is a low latency input that is exclusively available
> to PRU1?
Dear Beaglebone black Community,
As am newbie to this beaglebone black development board & am stuck with
this from many days, I found several links related to flashing the images
onto beaglebone black,
But could anybody please suggest me, In a production environment which is
the quick & reli
Thanks Jason,
I recently found this PRU presentation from the Embedded Linux Conference
Europe.
http://events.linuxfoundation.org/sites/events/files/slides/Enhancing%20RT%20Capabilities%20with%20the%20PRU%20final.pdf
Can't wait to see a bit more of this rpmsg driver framework!
Regards,
Jon
--
24 matches
Mail list logo
