Re: [beagleboard] Trouble creating a BeagleBone Static IP

[Davide Picchi]

Lidia,
I think you got a corrupted file.

Install your SO again and follow what Robert says

Here the syntax:
*sudo connmanctl config  --ipv4 manual  
 --nameservers *

run:

debian@beaglebone:~$ connmanctl services
*AO Wiredethernet_74daea0a4b52_cable

sudo connmanctl config ethernet_74daea0a4b52_cable --ipv4
manual 30.0.0.39 255.0.0.0 30.0.0.1 --nameservers 8.8.8.8

You don't need to edit the file /etc/network/interfaces
Just run connmanctl as above.


2016-08-01 20:00 GMT+02:00 evilwulfie :

> Flash Debian on it, I don't think anybody is supporting angstrom on the
> BBB ANYMORE
>
>
>
> On 8/1/2016 10:55 AM, Lidia Toscano wrote:
>
> I am totally a nenwbie to BBB -  I am having trouble connecting it to my
> pc through ethernet.  I am using Angstrom.  I've tried following the
> instructions here: http://derekmolloy.ie/set-ip-address-to-be-static-
> on-the-beaglebone-black/but then I run into lots of errors:
>
>
> login as: root
> root@beaglebone.local's password:
> root@beaglebone:~# ls -al
> total 64
> drwxr-xr-x 10 root root 4096 Jan  1 00:00 .
> drwxr-sr-x  4 root root 4096 Mar 18  2013 ..
> -rw---  1 root root 1320 Jan  1 00:00 .ICEauthority
> -rw---  1 root root  190 Jan  1  2000 .bash_history
> drwxr-xr-x  4 root root 4096 Jan  1 00:01 .config
> -rw-r--r--  1 root root   31 Jan  1 00:00 .dmrc
> drwx--  4 root root 4096 Jan  1 00:00 .gconf
> drwx--  5 root root 4096 Jan  1 00:01 .gnome2
> dr-x--  2 root root0 Jan  1 00:00 .gvfs
> drwxr-xr-x  3 root root 4096 Jan  1 00:00 .local
> drwxr-xr-x  2 root root 4096 Jan  1 00:01 .nautilus
> drwx--  2 root root 4096 Jan  1 00:00 .pulse
> -rw---  1 root root  256 Jan  1 00:00 .pulse-cookie
> -rw---  1 root root7 Jan  1 00:16 .python-history
> -rw---  1 root root 1501 Jan  1 00:00 .xsession-errors
> -rw---  1 root root 1501 Jan  1 00:00 .xsession-errors.old
> drwxr-xr-x  2 root root 4096 Jan  1 00:01 Desktop
> root@beaglebone:~# route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 192.168.7.0 0.0.0.0 255.255.255.252 U 0  00
> usb0
> root@beaglebone:~# cat /etc/network/interfaces
> cat: /etc/network/interfaces: No such file or directory
> root@beaglebone:~# iface eth0 inet dhcp
> -sh: iface: command not found
> root@beaglebone:~# /etc/network/interfaces
> -sh: /etc/network/interfaces: No such file or directory
> root@beaglebone:~#
>
> I cannot find the ethernet_c8a030ab323a_cable# Derek speaks about, I
> cannot fint the /etc/network/interfaces to try to edit the file indicated
> by Derek.
>
> Any idea why I am getting those errors?  You help will be greatly
> appreciated.
>
> Thanks in advance!
>
> Lidia
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/5404eb31-a8c8-43a3-9036-c4ca17f66a04%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/2a5bf207-bdd6-ac79-f1e5-3c16b02f5ebb%40gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAMktrusPNmhjOOviF6ifFy1nSaVHKXjzfE41k5rq8GDXCrGHvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Bug or error in the documentation of libpruio

[Davide Picchi]

One thing more:

I looked into the dtc-overlay: libpruio-00A0.dts and the overlay seems to
be only for *beaglebone* and *beaglebone-black* compatible.
I think you should add *beaglebone-green* as well.

2016-02-13 17:58 GMT+01:00 TJF :

> Hi Davide!
>
> You're right, thanks for reporting that bug. It'll be fixed in next
> release. It's a copy / paste, you can find it in all C examples. The effect
> is that the ADC runs faster than expected (no delay).
>
> BR
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Bug or error in the documentation of libpruio

[Davide Picchi]

I was reading carefully the following example taken from here 
:

file: button.c

define _GNU_SOURCE 1 
 #include "stdio.h" 
 #include  
 #include  
#include  
 #include  
#include  
 #include "../c_wrapper/pruio.h" 
 #include "../c_wrapper/pruio_pins.h" 
  
 #define PIN P8_07 
 
 int 
 isleep(unsigned int mseconds) 
 { 
 fd_set set; 
  struct timeval timeout; 
  
 /* Initialize the file descriptor set. */ 
  FD_ZERO(); 
  FD_SET(STDIN_FILENO, ); 
  
  /* Initialize the timeout data structure. */ 
 timeout.tv_sec = 0; 
  timeout.tv_usec = mseconds * 1000; 
  
 return TEMP_FAILURE_RETRY(select(FD_SETSIZE, 
 , NULL, NULL, 
 )); 
 } 
  
 int main(int argc, char **argv) 
 { 
 pruIo *io = pruio_new(PRUIO_DEF_ACTIVE, 0x98, 0, 1); // <= LOOK HERE
 
  do { 
  if (io->Errr) { 
  printf("initialisation failed (%s)\n", io->Errr); break;} 
  
  if (pruio_config(io, 1, 0x1FE, 0, 4)) { 
printf("config failed (%s)\n", io->Errr); break;} 
  
 struct termios oldt, newt; // make terminal non-blocking 
 tcgetattr( STDIN_FILENO,  ); 
 newt = oldt; 
 newt.c_lflag &= ~( ICANON | ECHO ); 
 newt.c_cc[VMIN] = 0; 
 newt.c_cc[VTIME] = 0; 
 tcsetattr(STDIN_FILENO, TCSANOW, ); 
  
 while(!isleep(1)) { // run loop until keystroke 
 printf("\r%1X", pruio_gpio_Value(io, PIN)); 
 fflush(STDIN_FILENO); 
 } 
 tcsetattr(STDIN_FILENO, TCSANOW, ); // reset terminal 
  
  printf("\n"); 
 } while (0); 
  
 pruio_destroy(io); /* destroy driver structure */ 
 return 0; 
 }


In the following line of code you can read that the value 0x98 is the 
*second* argument passed to the function.
*BUT* In the documentation I found that:

pruIo* pruio_new ( uint16  *Act*, 


uint8  *Av*, 


uint32  *OpD*, 


uint8  *SaD*  

) 

Wrapper function for the constructor PruIo::PruIo(). 
Parameters 
Act mask for active subsystems and PRU number 
Av avaraging for default steps (0 to 16, defaults to 0) 
OpD open delay for default steps (0 to 0x3, defaults to 0x98) 
SaD sample delay for default steps (0 to 255, defaults to 0) 
the second argument of that function should be the parameter Av, which 
ranges [0-16].
the OpD is passed lately to the function.

Is there a problem in the documentation or somewhere else??


-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Bug or error in the documentation of libpruio

[Davide Picchi]

In the following line of code you can read that the value 0x98 is the 
*second* argument passed to the function:
 pruIo *io = pruio_new(PRUIO_DEF_ACTIVE, 0x98, 0, 1);

I forgot to point to the function in the text.



Am Samstag, 13. Februar 2016 13:01:04 UTC+1 schrieb Davide Picchi:
>
> I was reading carefully the following example taken from here:
>
> file: button.c
>
> define _GNU_SOURCE 1 
>  #include "stdio.h" 
>  #include  
>  #include  
> #include  
>  #include  
> #include  
>  #include "../c_wrapper/pruio.h" 
>  #include "../c_wrapper/pruio_pins.h" 
>   
>  #define PIN P8_07 
>  
>  int 
>  isleep(unsigned int mseconds) 
>  { 
>  fd_set set; 
>   struct timeval timeout; 
>   
>  /* Initialize the file descriptor set. */ 
>   FD_ZERO(); 
>   FD_SET(STDIN_FILENO, ); 
>   
>   /* Initialize the timeout data structure. */ 
>  timeout.tv_sec = 0; 
>   timeout.tv_usec = mseconds * 1000; 
>   
>  return TEMP_FAILURE_RETRY(select(FD_SETSIZE, 
>  , NULL, NULL, 
>  )); 
>  } 
>   
>  int main(int argc, char **argv) 
>  { 
>  pruIo *io = pruio_new(PRUIO_DEF_ACTIVE, 0x98, 0, 1); // <= LOOK HERE
>  
>   do { 
>   if (io->Errr) { 
>   printf("initialisation failed (%s)\n", io->Errr); break;} 
>   
>   if (pruio_config(io, 1, 0x1FE, 0, 4)) { 
> printf("config failed (%s)\n", io->Errr); break;} 
>   
>  struct termios oldt, newt; // make terminal non-blocking 
>  tcgetattr( STDIN_FILENO,  ); 
>  newt = oldt; 
>  newt.c_lflag &= ~( ICANON | ECHO ); 
>  newt.c_cc[VMIN] = 0; 
>  newt.c_cc[VTIME] = 0; 
>  tcsetattr(STDIN_FILENO, TCSANOW, ); 
>   
>  while(!isleep(1)) { // run loop until keystroke 
>  printf("\r%1X", pruio_gpio_Value(io, PIN)); 
>  fflush(STDIN_FILENO); 
>  } 
>  tcsetattr(STDIN_FILENO, TCSANOW, ); // reset terminal 
>   
>   printf("\n"); 
>  } while (0); 
>   
>  pruio_destroy(io); /* destroy driver structure */ 
>  return 0; 
>  }
>
>
> In the following line of code you can read that the value 0x98 is the 
> *second* argument passed to the function.
> *BUT* In the documentation I found that:
>
> pruIo* pruio_new ( uint16  *Act*, 
>
>
> uint8  *Av*, 
>
>
> uint32  *OpD*, 
>
>
> uint8  *SaD*  
>
> ) 
>
> Wrapper function for the constructor PruIo::PruIo(). 
> Parameters 
> Act mask for active subsystems and PRU number 
> Av avaraging for default steps (0 to 16, defaults to 0) 
> OpD open delay for default steps (0 to 0x3, defaults to 0x98) 
> SaD sample delay for default steps (0 to 255, defaults to 0) 
> the second argument of that function should be the parameter Av, which 
> ranges [0-16].
> the OpD is passed lately to the function.
>
> Is there a problem in the documentation or somewhere else??
>
>
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Question regarding UART

[Davide Picchi]

Which programming language would be the best to write uart applications in
C++, Python, or Java?

This question doesn't make any sense. There is not a better programming
language than another.Not absolutely. From your question I can understand
that you are pretty new in the world of programming. Specially for embedded
devices. Maybe you want to use the BBB and not be one day an expert in
informatics. In this case you can start which any language you want, but
most probably you'll find confortable with Python.
In this case you have tons of tutorial about using USART. But...if you
don't have any experience in programming language it will be very hard for
you to adapt tutorials to your needs.

Is it possible to send data between the uarts without them being physically
connected?

Do you mean through a wireless connections? Of course...take a look at Xbee
Module or eNIC Nitro. The latter is a modified version of an Arduino. Both
are really easy to configure and to use.

2016-01-19 19:04 GMT+01:00 Michael Williams :

> I have a few questions regarding the UARTs on the Beaglebone Black & Green.
>
> What is a good resource for writing programs for the uarts? Which
> programming language would be the best to write uart applications in C++,
> Python, or Java?
>
> Is it possible to send data between the uarts without them being
> physically connected?
>
> Thank you in advance for your help.
>
> Mike
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Device tree overlay does not affect GPIO pin's state

[Davide Picchi]

1) Reboot the board
2) check whether the cape has been rightly loaded
3) if yes, check the pinmux again.

Your device tree seems ok to me

2016-01-09 9:29 GMT+01:00 :

> Hi all,
>
> I started using Beaglebone Black with Debian 7.9 for my project and I'm
> trying to load my own device-tree overlay in order to get more GPIO pins
> available. I need to use P8.46 pin as GPIO (Mode7) pin. I've disabled HDMI
> cape and then built custom dts to configure P8.46 pin as GPIO pin (mode7,
> output, pull-down):
>
> /dts-v1/;
> /plugin/;
>
>
> /{
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part_number = "BS_PINMODE_P8_46_0x7";
>
>
> exclusive-use =
> "P8.46",
> "gpio2_7";
>
>
> fragment@0 {
> target = <_pinmux>;
> __overlay__ {
> bs_pinmode_P8_46_0x7: pinmux_bs_pinmode_P8_46_0x7 {
> pinctrl-single,pins = <0x0a4 0x7>;
> };
> };
> };
>
>
> fragment@1 {
> target = <>;
> __overlay__ {
> bs_pinmode_P8_46_0x7_pinmux {
> compatible = "bone-pinmux-helper";
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <_pinmode_P8_46_0x7>;
> };
> };
> };
> };
>
> Then I've compiled dts and put dtbo in /lib/firmware. I can load the
> overlay manually:
>
> root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,bspm_P8_46_7
>
> But when I tried to check pin config I got the next output:
> root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
> grep "pin 71"
> pin 71 (44e1091c)  pinctrl-single
>
> What's wrong with my dts why I can't change muxing for the pin? What am I
> missing?
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: bbb startup fails with cape

[Davide Picchi]

Read BBB-SRM paragraph: 6.7 and 8.3
I drive some pins needed for the boot process

Am Freitag, 12. Juni 2015 03:06:10 UTC+2 schrieb luc.d...@gmail.com:
>
> hello all,
> I design a cape for BBB.
> this cape use a lot of of bbb gpio (28 as input - opto isolated, 24 as 
> output - relay).
> I launch some bonescript to work with.
> all works when I plug the cape after bbb has started.
> but if I plug the cape before the bbb start, it does not boot : only the 
> power led swith on. other leds keep off. the bbb won't start.
> I think it is a problem with the bonescript GPIO device tree not loaded at 
> boot time.
> can someone confirm that ?
> do I need an eeprom on my cape to configure device tree on start up ?
> or I will have a chance to do that only programmatically ?
> thank's
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] ubuntu doesnt go to desktop

[Davide Picchi]

Did you typed:

$startx

???


But I think you should install a VNC-Server anyway

2016-01-09 16:22 GMT+01:00 :

> hi guys
>
> I want to get ubuntu on my beaglebone black. I write image on micro sd and
> after plugging beaglebone black to power its start booting.
>
> Afterwards i had to type in login and password. Yeah i was logged in.
>
> The problem is i am not getting to desktop
>
> always coming
>
> ubuntu@arm:
>
> So which command i have to type in to start ubuntu?
>
> Pls help
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Device tree overlay does not affect GPIO pin's state

[Davide Picchi]

Sorry I forgot:

you should check with the following command:

root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
grep "8a4"

because you have 0x0a4 that is the offset. Ok, now you should add 44e10800
=> 44e108a4
Looking for "8a4" is enough and you ll find the right pin.

Pin 71 is not the right one.

2016-01-18 21:04 GMT+01:00 Davide Picchi <pave...@gmail.com>:

> 1) Reboot the board
> 2) check whether the cape has been rightly loaded
> 3) if yes, check the pinmux again.
>
> Your device tree seems ok to me
>
> 2016-01-09 9:29 GMT+01:00 <taras.pit...@gmail.com>:
>
>> Hi all,
>>
>> I started using Beaglebone Black with Debian 7.9 for my project and I'm
>> trying to load my own device-tree overlay in order to get more GPIO pins
>> available. I need to use P8.46 pin as GPIO (Mode7) pin. I've disabled HDMI
>> cape and then built custom dts to configure P8.46 pin as GPIO pin (mode7,
>> output, pull-down):
>>
>> /dts-v1/;
>> /plugin/;
>>
>>
>> /{
>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>> part_number = "BS_PINMODE_P8_46_0x7";
>>
>>
>> exclusive-use =
>> "P8.46",
>> "gpio2_7";
>>
>>
>> fragment@0 {
>> target = <_pinmux>;
>> __overlay__ {
>> bs_pinmode_P8_46_0x7: pinmux_bs_pinmode_P8_46_0x7 {
>> pinctrl-single,pins = <0x0a4 0x7>;
>> };
>> };
>> };
>>
>>
>> fragment@1 {
>> target = <>;
>> __overlay__ {
>> bs_pinmode_P8_46_0x7_pinmux {
>> compatible = "bone-pinmux-helper";
>> status = "okay";
>> pinctrl-names = "default";
>> pinctrl-0 = <_pinmode_P8_46_0x7>;
>> };
>> };
>> };
>> };
>>
>> Then I've compiled dts and put dtbo in /lib/firmware. I can load the
>> overlay manually:
>>
>> root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots
>>  0: 54:PF---
>>  1: 55:PF---
>>  2: 56:PF---
>>  3: 57:PF---
>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,bspm_P8_46_7
>>
>> But when I tried to check pin config I got the next output:
>> root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
>> grep "pin 71"
>> pin 71 (44e1091c)  pinctrl-single
>>
>> What's wrong with my dts why I can't change muxing for the pin? What am I
>> missing?
>>
>> --
>> 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 this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Can't connect to Beaglebone after doing a "reboot"

[Davide Picchi]

Yes.
It does it something (more oft than wanted). The reason is that your BBB
gets rebooted but in the process doesn't initialize the eth0. Check in your
router and you'll see the BBB that is not able to get connected with the
internet.

I fixed in the following way:
create a crontab with the following line:

@reboot /etc/init.d/networking restart

There is an old post about this problem. If I find it, I post it here.

Regards

2016-01-16 2:54 GMT+01:00 Markus Huber :

> I am using a Beaglebone for 4 months now and never had this problem. I
> flushed it and installed the new OS (the latest one debian 7.9), then I
> connect to it with
>
> ssh root@192.168.7.2
>
> that works the first time, when I do
>
> shutdown -h now unplug it and replug it again it works.
>
> But when I do
>
> reboot
>
> it reboots but I can't connect or ping it anymore. Once I unplug and
> replug it in, it works again.
>
> Any ideas?
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: disabling power on gpio pins during boot

[Davide Picchi]

Did you fix this problem?
Because I m facing the same undesired behavior.

Thanks

Am Sonntag, 28. Juni 2015 22:04:07 UTC+2 schrieb andrew otis:
>
> Hey Everyone,
>
> I'm a n00b so please excuse me, but I have been trying to get my BBB to 
> boot with no power on P9-pin 11.
>
> Controlling them through /sys/class/export works fine but even if I write 
> a bash script to disable power, it still stays on for about 5 seconds 
> before my script runs to cut power.
>
> So, obviously I learned bash scripts are not the way to go here.
>
> Next, I tried exploring making the config changes in the boot loader. I've 
> modified beagle.c in u-boot source and commented out this entire section:
>
>/* Set GPIO states before they are made outputs
> writel(GPIO23 | GPIO10 | GPIO8 | GPIO2 | GPIO1,
> _base->setdataout);
> writel(GPIO31 | GPIO29 | GPIO28 | GPIO22 | GPIO21 |
> GPIO15 | GPIO14 | GPIO13 | GPIO12, 
> _base->setdataout); */
>
> /* Configure GPIOs to output
> writel(~(GPIO23 | GPIO10 | GPIO8 | GPIO2 | GPIO1), 
> _base->oe);
> writel(~(GPIO31 | GPIO29 | GPIO28 | GPIO22 | GPIO21 |
> GPIO15 | GPIO14 | GPIO13 | GPIO12), _base->oe); */
>
> Recompiled, put MLO and u-boot.img in my /boot/uboot path but it still 
> doesn't seem to work.
>
> Again, I apologize for the n00bness, but would someone that has experience 
> doing this kind of thing be able to at least point me in the right 
> direction? 
>
> are there other methods I can use in this $gpio5_base? 
>
> End goal is to be able to hook up my multimeter to pin 11 on P9, boot the 
> device and never see voltage, until I want it (I got that part down)
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot boot from expanded microSD and I don't know where to look for logs

[Davide Picchi]

Logs are under:

1.) logs are at /var/*log*/  /* without s */
>



2015-12-31 4:01 GMT+01:00 Graham :

> 1.) logs are at /var/logs/
> 2.) look in the file named syslog for the latest boot information.  Other
> log files may have specialized information.
> 3.) I usually take a card that has had the 4G image installed, that has
> been tested for proper booting, then expand the partition by plugging the
> card into another LINUX computer, and using gparted to expand the partition
> to the desired size, including the maximum for the card.
> 4.) Expanding to 30GB on a 32 GB card should not be a problem.
> 5.) Cheap cards can cause problems. Use a quality card.
>
> --- Graham
>
> ==
>
>
> On Wednesday, December 30, 2015 at 3:24:50 PM UTC-6, gor...@gmail.com
> wrote:
>>
>> Hello,
>> I just got my bbb and I started playing with it. So I have written newest
>> stable debian on microSD and I was able to boot it from the card but then I
>> used grow partition script to expand partition and now it has 30GB
>> partition however I am not able to boot from it. When I try USR LEDs blink
>> for a fraction of a second and USR2 was left turned on. The funny thing is,
>> it has same behavior even if I don't hold USER/BOOT button so it won't boot
>> even if the card is present.
>>
>> So where are there any logs for unsuccessful boot? If so, where can I
>> find them?
>> Am I unable to use 30GB as a root partition or something?
>>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cannot set pins by overlay

[Davide Picchi]

@bremenpl

try removing the follwing part in your code:

test_input1 { 
gpio-name = "test_input1"; 
gpio = < 23 0x00>;/* 
gpio4 is gpio3 */ 
input; 
count-rising-edge; 
count-falling-edge; 
}; 
  
test_input2 { 
gpio-name = "test_input2"; 
gpio = < 10 0x00>;/* 
gpio4 is gpio3 */ 
input; 
count-rising-edge; 
count-falling-edge; 
};



and just leave the following part as it is:



   fragment@1 { 
target = <>; 
__overlay__ { 
gpio_helper { 
compatible = "gpio-of-helper"; 
status = "okay"; 
pinctrl-names = "default"; 
pinctrl-0 = <_example>;
 
}; 
}; };

...





Am Samstag, 12. September 2015 12:57:49 UTC+2 schrieb bremenpl:
>
> I also dont think that there is a device tree with this name. I will 
> however try you tips at mo day in the morning and let know here. Thank you 
> for help. 
>
>
> On September 11, 2015 3:41:52 PM Charles Steinkuehler 
>  wrote: 
>
> > On 9/11/2015 3:41 AM, Bremenpl wrote: 
> >> 
> >> Am I still doing something wrong? 
> > 
> > Two things to check: 
> > 
> > 1) The kernel will load any compiled in overlays in preference to 
> > files in /lib/firmware.  I don't think there's a BB_AVRDUDE overlay 
> > compiled into the kernel, but you can test by changing the name of 
> > your *.dtbo file to something guaranteed to be unique (or give it a 
> > custom version number) and try to load that instead.  That will force 
> > the kernel to look for the file in /lib/firmware. 
> > 
> > 2) You can crawl through the live device tree (/proc/device-tree/*) 
> > and make sure it's what you're expecting.  It's easy to have one typo 
> > or similar that will mess up everything you're trying to do.  :) 
> > 
> > -- 
> > Charles Steinkuehler 
> > cha...@steinkuehler.net  
> > 
> > -- 
> > For more options, visit http://beagleboard.org/discuss 
> > --- 
> > You received this message because you are subscribed to a topic in the 
> > Google Groups "BeagleBoard" group. 
> > To unsubscribe from this topic, visit 
> > https://groups.google.com/d/topic/beagleboard/kL9YPe8NuPg/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> > beagleboard...@googlegroups.com . 
> > For more options, visit https://groups.google.com/d/optout. 
>
>
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cannot set pins by overlay

[Davide Picchi]

And if you need some help I can suggest you to try the code generated in 
this page 

.

At least you have the chance to check, whether your code is right or not. 
You can simplify debugging of your code.

Regards

Am Mittwoch, 9. September 2015 18:41:21 UTC+2 schrieb bremenpl:
>
> Hello there,
> I just got back to my BeagleBone Black and i have no idea why but I just 
> cannot change a pin configuration using overlay nor through export. This is 
> what I am trying to do:
>
> I want to set P8_29 and P8_31 Pins to inputs with a pullup (0x37). here is 
> my overlay:
>
> /dts-v1/;
> /plugin/;
>
> /{
>compatible = "ti,beaglebone", "ti,beaglebone-black";
>part-number = "BB-AVRDUDE";
>version = "00A0";
>
>fragment@0 {
>  target = <_pinmux>;
> 
>  __overlay__ {
>   ebb_example: BB-AVRDUDE {
> pinctrl-single,pins = <
> 0x0E4 0x37  // P8_29, AVR #RST pin, Input Mode7 pullup
> 0x0D8 0x37  // P8_31, AVR #HWB pin, Input Mode7 pullup
>   
>/* INPUT   GPIO(mode7) 0x27 pulldown, 0x37 pullup, 
> 0x?f no pullup/down */
> >;
>   };
>  };
>};
>
>fragment@1 {
> target = <>;
> __overlay__ {
> gpio_helper {
> compatible = "gpio-of-helper";
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <_example>;
> };
> };
> };
> };
>
> Then I load the DTS and see in the list (last). HDMI is disabled:
>
>  0: 54:PF--- 
>  1: 55:PF--- 
>  2: 56:PF--- 
>  3: 57:PF--- 
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,NEOSEC-TINYLCD22
>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-KEYS
>  9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-SPI1-2CS
> 10: ff:P-O-L Override Board Name,00A0,Override Manuf,am33xx_pwm
> 11: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-COOLER
> 12: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART5
> 13: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BUZZER
> 14: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-W1
> *15: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-AVRDUDE*
>
>
> Dmesg says it was OK:
>
> root@beaglebone:~# dmesg | grep BB-AVRDUDE
> [  151.732517] bone-capemgr bone_capemgr.9: part_number 'BB-AVRDUDE', 
> version 'N/A'
> [  151.732633] bone-capemgr bone_capemgr.9: slot #15: 'Override Board 
> Name,00A0,Override Manuf,BB-AVRDUDE'
> [  151.732729] bone-capemgr bone_capemgr.9: slot #15: Requesting part 
> number/version based 'BB-AVRDUDE-00A0.dtbo
> [  151.732744] bone-capemgr bone_capemgr.9: slot #15: Requesting firmware 
> 'BB-AVRDUDE-00A0.dtbo' for board-name 'Override Board Name', version '00A0'
> [  151.736445] bone-capemgr bone_capemgr.9: slot #15: dtbo 
> 'BB-AVRDUDE-00A0.dtbo' loaded; converting to live tree
>
>
> Then I check the pins and they remain as they were in default:
>
> root@beaglebone:~# cat $PINS | grep "pin 57"
> pin 57 (44e108e4) 0027 pinctrl-single 
> root@beaglebone:~# cat $PINS | grep "pin 54"
> pin 54 (44e108d8) 002f pinctrl-single 
>
>
> Did I forget something? I really cant think of anything. I would really 
> apreciate all help here!
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot set pins by overlay

[Davide Picchi]

I discovered that (at least in my ubuntu Linux arm 4.1.13-ti-r36) trying to
load and unload overlays on the fly doesn't work.
I did it many times, in the right way. But you should reboot your system at
first and THEN try to load your overlay.
Your changes at the pinmux should be visible now.

I don't know why one should reboot the system everytime.

2015-12-31 11:39 GMT+01:00 Bremenpl <breme...@gmail.com>:

> Didnt know about this page, thabk you a lot :).
>
> On December 31, 2015 11:30:53 AM Davide Picchi <pave...@gmail.com> wrote:
>
>> And if you need some help I can suggest you to try the code generated in
>> this page
>> <http://kilobaser.com/blog/2014-07-28-beaglebone-black-devicetreeoverlay-generator#1gpiodto>
>> .
>>
>> At least you have the chance to check, whether your code is right or not.
>> You can simplify debugging of your code.
>>
>> Regards
>>
>> Am Mittwoch, 9. September 2015 18:41:21 UTC+2 schrieb bremenpl:
>>>
>>> Hello there,
>>> I just got back to my BeagleBone Black and i have no idea why but I just
>>> cannot change a pin configuration using overlay nor through export. This is
>>> what I am trying to do:
>>>
>>> I want to set P8_29 and P8_31 Pins to inputs with a pullup (0x37). here
>>> is my overlay:
>>>
>>> /dts-v1/;
>>> /plugin/;
>>>
>>> /{
>>>compatible = "ti,beaglebone", "ti,beaglebone-black";
>>>part-number = "BB-AVRDUDE";
>>>version = "00A0";
>>>
>>>fragment@0 {
>>>  target = <_pinmux>;
>>>
>>>  __overlay__ {
>>>   ebb_example: BB-AVRDUDE {
>>> pinctrl-single,pins = <
>>> 0x0E4 0x37  // P8_29, AVR #RST pin, Input Mode7 pullup
>>> 0x0D8 0x37  // P8_31, AVR #HWB pin, Input Mode7 pullup
>>>
>>>/* INPUT   GPIO(mode7) 0x27 pulldown, 0x37 pullup,
>>> 0x?f no pullup/down */
>>> >;
>>>   };
>>>  };
>>>};
>>>
>>>fragment@1 {
>>> target = <>;
>>> __overlay__ {
>>> gpio_helper {
>>> compatible = "gpio-of-helper";
>>> status = "okay";
>>> pinctrl-names = "default";
>>> pinctrl-0 = <_example>;
>>> };
>>> };
>>> };
>>> };
>>>
>>> Then I load the DTS and see in the list (last). HDMI is disabled:
>>>
>>>  0: 54:PF---
>>>  1: 55:PF---
>>>  2: 56:PF---
>>>  3: 57:PF---
>>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>>>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,NEOSEC-TINYLCD22
>>>  8: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-KEYS
>>>  9: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BONE-SPI1-2CS
>>> 10: ff:P-O-L Override Board Name,00A0,Override Manuf,am33xx_pwm
>>> 11: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-COOLER
>>> 12: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-UART5
>>> 13: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-BUZZER
>>> 14: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-W1
>>> *15: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-AVRDUDE*
>>>
>>>
>>> Dmesg says it was OK:
>>>
>>> root@beaglebone:~# dmesg | grep BB-AVRDUDE
>>> [  151.732517] bone-capemgr bone_capemgr.9: part_number 'BB-AVRDUDE',
>>> version 'N/A'
>>> [  151.732633] bone-capemgr bone_capemgr.9: slot #15: 'Override Board
>>> Name,00A0,Override Manuf,BB-AVRDUDE'
>>> [  151.732729] bone-capemgr bone_capemgr.9: slot #15: Requesting part
>>> number/version based 'BB-AVRDUDE-00A0.dtbo
>>> [  151.732744] bone-capemgr bone_capemgr.9: slot #15: Requesting
>>> firmware 'BB-AVRDUDE-00A0.dtbo' for board-name 'Override Board Name',
>>> version '00A0'
>>> [  151.736445] bone-capemgr bone_capemgr.9: slot #15: dtbo
>>> 'BB-AVRDUDE-00A0.dtbo' loaded; converting to live tree
>>>
>>>
>>> Then I check the pins and they remain as they were in default:
>>>
>>> root@beagle

Re: [beagleboard] BBB External Powering Issue

[Davide Picchi]

Riley,
try powering the board through an USB cable, to make sure that it is
nothing related to the hw or sw on the board.
If positive then try with a power supply that match the minimal
requirements.


2015-12-05 9:28 GMT+01:00 William Hermans :

> Voltage has to be too high, or not high enough. I'd assume too high as
> you've already stated the power supply is 5.25v. The reason why I say it
> has to be this, is that the power LED goes out nearly instantly.
>
> On Fri, Dec 4, 2015 at 9:45 PM, Gerald Coley 
> wrote:
>
>> 5.25V is a little high and in reality it may be even higher on power up.
>> The spec is 5V. I suggest you try and meet the specification and get a good
>> power supply.
>>
>> Another possibility is that while the supply is rated at 3A, it may have
>> a surge limiting function based on the product it was designed for. It
>> could be that as the board powers up and the current increases, it
>> increases to fast causing the power supply to shut down. I cannot say that
>> is the case or not based on a video.
>>
>> Also, based on the video you need t plug in the power jack., not wiggle
>> it in. Just plug in in firmly.
>>
>> Gerald
>>
>>
>> On Fri, Dec 4, 2015 at 10:35 PM, ril3y  wrote:
>>
>>> Hey Everyone.
>>>
>>>
>>> I need to use the 5v rails for about 300-400 miliamps so after doing a
>>> bunch of reading I found out that I could pull this from the 5v rail IF I
>>> used an external power adapter.
>>>
>>> I found one on amazon and got it here today.  Its 5v @3 amps.  I check
>>> it out and it looks to be about at 5.25V.  Here is a video of what is
>>> happening.
>>> https://goo.gl/photos/4fnzHVykRxVvgosB7
>>>
>>> It looks like it turns on.. the user leds light up then everything just
>>> fails.  I am not sure what the issue is.  I have tried 2 different BBB's
>>> and both exhibit the exact same behavior.
>>>
>>> Thanks everyone.
>>>
>>> Riley
>>>
>>> --
>>> 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 this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>>
>> --
>> 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 this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Configure Beaglebone to access usb0 from host PC. (Cannot ssh to beaglebone through USB)

[Davide Picchi]

I have the same issue too.
Did you fix that problem?

Am Freitag, 30. Oktober 2015 18:13:55 UTC+1 schrieb Alex:
>
> Hi,
>
> I am using ubuntu 14.04 (from Robert Nelson ) with a 
> custom 3.15.10-bone8 kernel on Beaglebone Black. HDMI is disabled. 
> When I plug the board to a PC, Beaglebone powers up but the PC does not 
> recognize that a USB device is connected to it. I have installed the 
> drivers for network-over-USB which is recommended on 
> Beagleboard.org/getting-started too. Moreover, I cannot ssh into it using 
> 192.168.7.2 eventhough I have set up my /etc/network/interfaces. 
> ubuntu@arm $ ifconfig usb0
> usb0  Link encap:Ethernet  HWaddr d2:56:2f:23:1d:e2
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
> Is there some modules that I need to run or compile to Kernel to bring the 
> client USB up? How should I configure the linux to be seen by PC when 
> connected from mini USB?
> Thanks for any help. 
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: How to enable UART1 using dtb-rebuilder?

[Davide Picchi]

Thank both of you.

Your explanations did work very well and I can load capes without a problem.

The only problem is that no capes are loaded at boot startup process. So I 
need to load the cape everytime.
The following answer 
<https://groups.google.com/forum/?hl=de#!topicsearchin/beagleboard/overlay/beagleboard/hr8L9U7HLMk>
 
didn't help further. I have that flag as default in my beagle.

The only working way seems to be:

/boot/uEnv.txt  // open that file and write the following:
 
cape_enable=bone_capemgr.enable_partno=BB-UART1

But I thought that this is just an alternative, not the first choice.

Any idea?
 



Am Montag, 9. November 2015 21:16:10 UTC+1 schrieb William Hermans:
>
>
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/
>
> On Mon, Nov 9, 2015 at 11:48 AM, Robert Nelson <robert...@gmail.com 
> > wrote:
>
>> On Mon, Nov 9, 2015 at 12:45 PM, Davide Picchi <pav...@gmail.com 
>> > wrote:
>> >> 4.1-ti supports overlays, so you can either do it like "3.8".
>> >>
>> >>
>> >> 
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts
>> >>
>> >> or create a custom *.dtb
>> >
>> >
>> > That's nice,
>> > but I cannot find any guide that helps me to install the new cape like 
>> in
>> > the first tutorial I posted above.
>> >
>> > How do I use such overlays?
>> > 
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts
>> >
>> > Should I copy them somewhere?
>>
>> Follow steps 1 -> 3:
>>
>> https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md
>>
>> Then either:
>>
>> sudo sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots"
>>
>> or:
>>
>> /boot/uEnv.txt
>>
>> cape_enable=bone_capemgr.enable_partno=BB-UART1
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> 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 this group and stop receiving emails from it, send an 
>> email to beagleboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to enable UART1 using dtb-rebuilder?

[Davide Picchi]

>
> 4.1-ti supports overlays, so you can either do it like "3.8". 
>
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts
>  
>
> or create a custom *.dtb 
>

That's nice,
but I cannot find any guide that helps me to install the new cape like in 
the first tutorial I posted above.

How do I use such overlays?
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts

Should I copy them somewhere?



Am Montag, 9. November 2015 16:44:03 UTC+1 schrieb Davide Picchi:
>
> I was able to enable all the UART serial connections on my BBB before I 
> switched to the last kernel.
> In the following tutorial 
> <https://github.com/khancyr/dtb-rebuilder/wiki/Example>it was explained 
> very well, how to change the cape-fuctions accordingly and everything 
> worked fine.
>
> Now I have the latest Ubuntu distro on my board. I ve downloaded the last 
> dtb-rebuilder 
> for 4.1-ti <https://github.com/RobertCNelson/dtb-rebuilder> and try to 
> enable again my old uart ports.
> It seems that everything is changed since 3.8. I open my 
> am335x-boneblack-dts, but I can find any 
> #include
>
> directive which helps to activate/deactivate peripherals.
>
> The readme in the repository says nothing about that.
>
> What should I do? 
> How can I compile my dtb-file for my board?
>
>
>
>

-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to enable UART1 using dtb-rebuilder?

[Davide Picchi]

I was able to enable all the UART serial connections on my BBB before I 
switched to the last kernel.
In the following tutorial 
it was explained 
very well, how to change the cape-fuctions accordingly and everything 
worked fine.

Now I have the latest Ubuntu distro on my board. I ve downloaded the last 
dtb-rebuilder 
for 4.1-ti  and try to 
enable again my old uart ports.
It seems that everything is changed since 3.8. I open my 
am335x-boneblack-dts, but I can find any 
#include

directive which helps to activate/deactivate peripherals.

The readme in the repository says nothing about that.

What should I do? 
How can I compile my dtb-file for my board?



-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] UART communication in Beaglebone Black

[Davide Picchi]

Are you sure, that you selected the right UART port???

It should be 
 /dev/ttyO0

 or 
 /dev/ttyO1

 and so on...but not 
 /dev/ttySx



On Tuesday, April 28, 2015 at 9:19:31 PM UTC+2, Peter Hurley wrote:

 On 04/27/2015 06:41 AM, JAY KOTHARI wrote: 
  Hi, 
  I am unable to do simple uart communication in BBB. I have set 
 device tree 
  
  uart2_pins: uart2_pins { 
  pinctrl-single,pins =  
  0x154 0x01 
  0x150 0x31 
 ; 
  }; 
  
  uart2 { 
  status = okay; 
  pinctrl-names = default; 
  pinctrl-0 = uart2_pins; 
  }; 
  
  then I configure the UART Port 
  
  stty -F /dev/ttys0 cstopb -evenp ispeed 115200 
^ 
 stty: /dev/ttys0: No such file or directory 

 uart2 is not /dev/ttyS0. 

 uart0 = /dev/ttyS0 
 uart1 = /dev/ttyS1 
 uart2 = /dev/ttyS2 

 Regards, 
 Peter Hurley 


  Then I made a user space application for reading and writing data to 
  device file. I have attached the application program 
  
  I connected Tx and Rx pin in same BBB.(Loop back mode) 
  
  But  I am not able to do simple UART communication in loop back 
  mode. Do am I missing something? Please help me 



-- 
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 this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.