Assuming he's using one of the newer images,
Any reason it can't be done with config-pin instead of an overlay?
On Wednesday, May 11, 2016 at 1:55:08 PM UTC-5, RobertCNelson wrote:
>
>
>
> On Wed, May 11, 2016 at 1:48 PM, Michael Williams > wrote:
>
>> Thank you, Robert, for the tips and files.
If one did this, would config-pin still work to enable a UART etc?
On Tuesday, May 10, 2016 at 11:00:37 AM UTC-5, RobertCNelson wrote:
>
>
>
> On Tue, May 10, 2016 at 9:26 AM, > wrote:
>
>> Hi all,
>>
>> I'm just trying to improve the boot time on my beaglebone black using
>> Jessie and I'm down
Hello,
I just wanted to say that the problem iwas solved with the kernel 4.5.x
using the gpib-linux 4.0.3..
Thanks!
Le vendredi 29 avril 2016 17:25:26 UTC+2, malkowki_belgium a écrit :
>
> Thanks William,
> But this didn't help me a lot.
>
> I have notice that the gcc --version on the board wa
What image do I need to be using, in order to use the uart3_txd? I am
currently using Debian, version 3.8.13-bone79.
On Thursday, May 12, 2016 at 8:26:59 AM UTC-4, Wally Bkg wrote:
>
> Assuming he's using one of the newer images,
> Any reason it can't be done with config-pin instead of an overla
Hello,
I read some sites with BBB and RS485, but not sure if I unterstand it
correctly.
I want to enable UART4 to RS485 and communicate with ser2net.
I already setup the UART1 as RS232 with ser2net and running fine.
But what I have to do, to enable UART4 to RS485. Here it is an example ...
bu
Hello Gregor,
I'm actually working on a project incolving a SPI connection between a
BeagleBone black and an AD7606 (ADC). I have a couple of problems to enable
properly the SPI connection, could you give me more details about how you
have done it ? (if it worked).
I'm programming the BB_blac
Superb, I'll give that a go.
Thank you!
On Tue, May 10, 2016 at 4:59 PM, Robert Nelson
wrote:
>
>
> On Tue, May 10, 2016 at 9:26 AM, wrote:
>
>> Hi all,
>>
>> I'm just trying to improve the boot time on my beaglebone black using
>> Jessie and I'm down to about 16 seconds, of which about 8 are
Hi ,
I am running the following Kernel on my board:
Linux version 4.5.2-armv7-x2 gcc version 5.3.1 20160113 (Linaro GCC 5.3-
2016.02) ) #1 SMP Wed May 11 12:23:19 CEST 2016
I am getting the following error while compiling the kernel version from
Robert Nelson for the module PCA9535 as buil-in:
d
Problem solved with new Kernel from 4.1.x
Le vendredi 19 février 2016 11:17:54 UTC+1, malkowki_belgium a écrit :
>
> Hi all,
>
> I am working on the beagleboard xM using the Debian release 7.3 Wheezy ,
> and still using the old non DT Kernel Version 3.9.11-x5.
> I have instantiated the PCA9535 in
I apologize for bothering you again. I seem to be having a problem
compiling the BB-UART3-00A0.dts file that you sent me a link to. Here is
the command I issue to compile it. "dtc -O dtb -o BB-UART3-00A0.dtbo -b 0
-@ BB-UART3-00A0.dts" I have tried several times and have received the
follow
On Thu, May 12, 2016 at 8:59 AM, Michael Williams
wrote:
> I apologize for bothering you again. I seem to be having a problem
> compiling the BB-UART3-00A0.dts file that you sent me a link to. Here is
> the command I issue to compile it. "dtc -O dtb -o BB-UART3-00A0.dtbo -b 0
> -@ BB-UART3-00A
dont you love the error when compiling ?
no line number or more infos to help you troubleshoot.
have you modified it in any way ?
i had issues manually compiling so i just used the makefile
make clean then make and if all went well a sudo make install
On 5/12/2016 6:59 AM, Michael Williams wr
Bare Metal is not Debian? If you use bare metal you need to set up all pin mux
and initialize memory controller typically with a gel file in CCS. Briefly
looking at your code assuming nothing is interference with mux I'd make sure
your SPI chipselect is properly timed with a scope if you're tr
On Thu, May 12, 2016 at 9:09 AM, evilwulfie wrote:
> dont you love the error when compiling ?
> no line number or more infos to help you troubleshoot.
>
The issue, he didn't run gcc pre-proccessor on it. ;)
Easier to just run make in the included makefiel..
>
> have you modified it in any way
Why don't you adapt the 1-wire overlay? It should be easy to use a pin not
connected to any PWMSS. Ie. use P9_11 or P8_07.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe
Because the universal overlay causes my one wire overlay to be rejected.
The error is File Exists and dmesg points to the conflict with the slots
entry that has the conflict. I am probably doing something wrons, even
when I delete the P9_22 from the universal overlay and reapply it, it
reject
>
> *Because the universal overlay causes my one wire overlay to be rejected.
> The error is File Exists and dmesg points to the conflict with the slots
> entry that has the conflict. I am probably doing something wrons, even
> when I delete the P9_22 from the universal overlay and reapply it, it
That's correct, every pin is configured. And the load the driver for PWM,
or SPI, or ... but it is not configured to load the OneWire driver for the
pin. All of the config-pin options are for standard drivers. The point
is, if you want to use the pin to another device that is not a built in
>
> *That's correct, every pin is configured. And the load the driver for
> PWM, or SPI, or ... but it is not configured to load the OneWire driver for
> the pin. All of the config-pin options are for standard drivers. The
> point is, if you want to use the pin to another device that is not a bu
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-W1";
version = "00A0";
exclusive-use =
"P9.22",
"gpio0_2";
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
Ok. I have made a bit of progress, this afternoon.
I finally was able to get the file you sent me to compile with the dtc
version that I have. The only problem, is it is not assigning BB-UART3 to
/dev/ttyO3 for use. Attached is my updated ".dts" file.
Thanks again for your help.
Regards
On Thu, May 12, 2016 at 2:10 PM, Michael Williams
wrote:
> Ok. I have made a bit of progress, this afternoon.
>
> I finally was able to get the file you sent me to compile with the dtc
> version that I have. The only problem, is it is not assigning BB-UART3 to
> /dev/ttyO3 for use. Attached is
I mounted the Adafruit DS3231 RTC module on a breadboard and using the
Adafruit instructions got it to work. It works fine but it takes one minute
after booting the BBB before it reads the clock date and time and updates
to Debian. I would like it to update right away when the BBB boots up. I
s
Hi all! I am trying to use the eQEP device driver, found here:
https://github.com/Teknoman117/beaglebot
So, I could get the module loaded by echoing the device tree to cape
manager. After disabling eMMC and HDMI, all 0-2 modules loaded OK.
I hooked up my encoder, which uses open NPN to the board,
I do this for them pins in my dts file makes it easier to read
BONE_P8_31 (PIN_INPUT | MUX_MODE6) /* (V4)
lcd_data14.uart5_ctsn */
BONE_P8_32 (PIN_OUTPUT | MUX_MODE6) /* (T5)
lcd_data15.uart5_rtsn */
BONE_P8_33 (PIN_OUT
So, turns out that the DTBO being compiled was, for some unknown reason,
wrong. I copied the files from /beaglebot/tree/master/encoders/dts into
/beagleboard/bb.org-overlays/src/arm/ and ran make clean | make | make
install. This generated a file with the -00A0 sufix and another without.
The o
we are using beaglebone black based custom board,
We have programming station[desktop PC just naming it] where we have
configured tftpboot and nfsroot(network rfs).
And Last init script( programming init script in /etc/init.d/ folder)
flashes freshly manufactured board.
Programming script d
27 matches
Mail list logo
