Hi averyone,
Is it possible to change LCD data pins to another GPIO? The fact is that my
cape does not allow the Beaglebone Black to boot normally, because LCD
pins are used when BBB boot. Although if I connect it after boot BBB, then
it works well. I tried to reconfigure the pins in the
I do agree! https://www.theproche.com/
On Wednesday, January 23, 2019 at 8:00:12 PM UTC+5:30, Farooque Mustafa
wrote:
>
> I have to use air control sensor PMS5003 (plantower) with BBBW. I was able
> to find datasheet for sensor and C library. I require datasheet of BBBW to
> understand how can
Hello..
I am first time work on beaglebone.I want to generate Clock of 3Khz on
timer7 (P8_8)pin og beaglebone.
here is my code.
import Adafruit_BBIO.GPIO as GPIO
import time
outpin="P8_8"
GPIO.setup(outpin,GPIO.OUT)
GPIO.setclock(outpin,3000)
while True:
GPIO.output(outpin,GPIO.HIGH)
Hello.
I am first time work on beaglebone. I want to generate 3Khz clock on
the timer7 (P8_8)pin of beaglebone.
my python code is.
import Adafruit_BBIO.GPIO as GPIO
import time
outpin="P8_8"
GPIO.setup(outpin,GPIO.OUT)
GPIO.setclock(outpin,3000)
while True:
Beaglebone Friends and Family, Robert;
We would like assistance in getting the BBONE-GATEWAY-CAPE running properly.
As is known, there were some design trade-offs on this particular cape that
resulted in it not being granted 100% BeagleBoard.org support, but it is
understood that the beagle
Thank you;
Changing init_console did the trick.
I am now getting console output while booting into linux - For a while.
Unfortunately instantly after the Linux eqep Linux Printk's console IO
ceases.
It appears the board is still doing something - as the USR0 and USR2 LED's
are active,
On Mon, Jan 28, 2019 at 7:05 AM wrote:
>
> Beaglebone Friends and Family, Robert;
>
> We would like assistance in getting the BBONE-GATEWAY-CAPE running properly.
> As is known, there were some design trade-offs on this particular cape that
> resulted in it not being granted 100%
Robert,
I thank you very much for any insight you can provide. For now, here are
some comments.
Thanks again,
Chris
-
They can't apparently run the BB with the cape installed. Once attached it
fails to boot. It is the WL1837MOD board. There is also a mention that to
run it, it must
Hello,
I bought the BBB_PRU_CAPE Rev 1.2A from TI and I am trying to follow this
guide to get started:
http://processors.wiki.ti.com/index.php/PRU_Cape_Getting_Started_Guide
In the "Setup your BeagleBone Black" section, it states to plug in the PRU
cape to the BBB and then plug in the FTDI
Robert,
I spoke a little too soon; some progress being made...Chris.
-
Currently booted with cape in place! Here are the results of the version.sh
…
debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
[sudo] password for debian:
On Mon, Jan 28, 2019 at 4:48 PM Lee wrote:
>
> Hello,
> I bought the BBB_PRU_CAPE Rev 1.2A from TI and I am trying to follow this
> guide to get started:
> http://processors.wiki.ti.com/index.php/PRU_Cape_Getting_Started_Guide
>
> In the "Setup your BeagleBone Black" section, it states to plug
On Mon, Jan 28, 2019 at 6:52 AM wrote:
>
> Hello..
> I am first time work on beaglebone.I want to generate Clock of 3Khz on
> timer7 (P8_8)pin og beaglebone.
> here is my code.
>
> import Adafruit_BBIO.GPIO as GPIO
> import time
> outpin="P8_8"
> GPIO.setup(outpin,GPIO.OUT)
>
On Wed, Jan 23, 2019 at 7:09 AM david rediger wrote:
>
> I found a Beagebone for Dummies post and figured out why I could not write to
> protected files. I had to log in as a Superuser. Once I did that did that I
> wrote the workaround in. Unfortunately the drivers file lacked the r8188eu
>
On 1/28/2019 12:33 PM, Dave wrote:
> Thank you;
>
> Changing init_console did the trick.
>
> I am now getting console output while booting into linux - For a while.
>
> Unfortunately instantly after the Linux eqep Linux Printk's console IO
> ceases.
>
> It appears the board is still doing
Does this mean it's something that is being worked on to be fixed for an
upcoming 4.19 kernel update or are UIO folks completely SOL and stuck on
4.14 kernels?
Dan
On Monday, January 28, 2019 at 2:15:48 PM UTC-5, RobertCNelson wrote:
>
> On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp >
>
..and then there's always the JTAG cable! :)
Another option Dave There was a guy in here who consistently talks about
toggling GPIOs and LESs. I'D ask him where to place these to shed light on
what's going
Sent from Yahoo Mail on Android
On Mon, Jan 28, 2019 at 4:10 PM, Charles
On Monday, January 28, 2019 at 1:57:56 PM UTC-5, Daniel Kulp wrote:
>
>
> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone
> kernel and ran into a big problem: uio_pruss is not configured in as it is
> with 4.14. Is this an oversight? Is there anyone I need to
Hello,
I wonder that what happens when I try to reach to a node where it is in
non-line of sight position for me. I have to make some number of 'hops'
over nodes in my line of sight to reach to non-line of sight node for me. I
wonder that, if ad-hoc is not supported, can I reach to node where it
I tried to update our app image from the 4.14 bone kernel to the 4.19 bone
kernel and ran into a big problem: uio_pruss is not configured in as it is
with 4.14. Is this an oversight? Is there anyone I need to contact to try
and convince them to re-enable uio_pruss? I'd like to
get
On Mon, Jan 28, 2019 at 1:33 PM Daniel Kulp wrote:
>
>
> Does this mean it's something that is being worked on to be fixed for an
> upcoming 4.19 kernel update or are UIO folks completely SOL and stuck on 4.14
> kernels?
Sorry, it's not something "i'm" personally working on. Patches
welcome,
Chris,
I've used the E14 cape on multiple customer projects. They have been both
debian based and TI SDK based. From memory its just been a case of picking
up the correct dtb file in u-boot. I've never touch the CC device on it
though as I've just needed Wi-Fi and/or Bluetooth.
I can't imagine
On Mon, Jan 28, 2019 at 12:58 PM Daniel Kulp wrote:
>
>
> I tried to update our app image from the 4.14 bone kernel to the 4.19 bone
> kernel and ran into a big problem: uio_pruss is not configured in as it is
> with 4.14. Is this an oversight? Is there anyone I need to contact to try
> and
To add a little bit of background to this;
There are several posts on TI's e2e forum stating that ad-hoc mode is no
longer supported. In TI's use cases ad-hoc was replaced by Wi-Fi Direct.
http://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/367550
TI supported 802.11s meshing
On Monday, January 28, 2019 at 4:20:33 PM UTC-5, Jason Kridner wrote:
>
> On Monday, January 28, 2019 at 1:57:56 PM UTC-5, Daniel Kulp wrote:
>>
>>
>> I tried to update our app image from the 4.14 bone kernel to the 4.19
>> bone kernel and ran into a big problem: uio_pruss is not configured in
Got it working. Thanks!
On Monday, January 28, 2019, 2:04:17 PM CST, Robert Nelson
wrote:
On Wed, Jan 23, 2019 at 7:09 AM david rediger wrote:
>
> I found a Beagebone for Dummies post and figured out why I could not write to
> protected files. I had to log in as a Superuser. Once I
Read the BeagleBone System Requirements Manual.
Section 8.3 and 8.3.1
It tells you several times about the requirement to protect the boot pins,
which are common with the LCD pins.
During boot, long before the device tree has any effect, the processor must
read the 100K pull up and pull down
The snippet below is in the common dtsi for all am335x boards.
What I am asking is if that snippet is meaningless, or if it has the actual
effect of switching standard out at some point to uart0 ?
Also what is the simplest way to rebuild the am335x-bone-uboot-univ.dtb ?
I am not familiar with
Serial capture files attached.
I used vim to change the timestamps to to allow ignoring timestamp
differences when comparing the files.
mts.txt is the boot on the target board.
bbb.txt is the boot on a BBB
If you diff the two files there are very very few differences - none of
which
I have made no changes to the root filesystem EXCEPT using
bb-kernel/build_deb.sh to build a relatively stripped kernel and
installing that when the immage is booted on a BBB before switching to the
target board.
I have not messed with init, inittab, or systemd or getty.
That may be
>
> I am booting my "custom" SD card in a BBB for reference purposes.
My "process" is start u-boot, use editenv to chang the console as
appropriate for the current board - ttyO0 on the bbb and ttyO4 on the
target.
saveenv.
reset the board with serial capture turned on .
Do the above with
I KNOW this is a problem that I can ultimately defeat.
I know I can attach a JTAG or I can add code to LINUX to flash LED's or
something like that to place sentinels and divide and conquer until I find
the offending problem.
But that could be a very long tedious process possibily taking
I am trying to avoid using toggling GPIO's to trace. I know how to do it.
But that could take weeks to find the problem.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To
I am trapping serial output on BOTH the target board and a BBB booting the
SAME SD card, with the only difference being the setting of init_console.
After each has run as far as it will - in the case of the BBB I get a login
prompt.
I vimdiff the serial output captures.
On the BBB I get alot
33 matches
Mail list logo
