Re: [beagleboard] Re: Disable Power Button IRQ from TPS65217 on BBBW?

[Joe Glandorf]

Thanks, Robert.  Unfortunately, commenting out either line in uEnv.txt, 
`#enable_uboot_overlays=1` or 
`#enable_uboot_cape_universal=1`
the TPS65217 IRQ still exists:  
$ cat /proc/interrupts | grep 65217
 60:  0  INTC   7 Level tps65217-irq
 62:  0  tps65217   0 Edge  vbus
 63:  0  tps65217   2 Edge  tps65217_pwr_but
And, PWM no longer works using the Python scripts, even after restoring the 
original dtb files.

Is this the appropriate information source for building the kernel?  
- 
https://www.digikey.com/eewiki/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel
  
We're currently using this lxqt image for the BBBW:  
- 
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Buster_LXQt_Snapshot
  

Joe

On Wednesday, October 28, 2020 at 1:44:11 PM UTC-4 RobertCNelson wrote:

> You can disable teh cape universal redirect with disabling this line
> in /boot/uEnv.txt
>
> enable_uboot_overlays=1
>
> You can also just not build with the tps65218-pwrbutton driver:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/input/misc/tps65218-pwrbutton.c
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2b95f0ea-c707-4298-82dc-c833f3e0ec9en%40googlegroups.com.

[beagleboard] Re: Disable Power Button IRQ from TPS65217 on BBBW?

[Joe Glandorf]

Added another test, below (without success), and also posted this 
to 
https://forum.digikey.com/t/disable-power-button-irq-from-tps65217-on-bbbw/9803 
 

  - based on boot-up messages from serial port 
```  
...
debug: [enable_uboot_cape_universal=1] ...
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ...
loading /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-uboot-univ.dtb ...
...
```
I copied `am335x-boneblack-uboot-univ.dtb` instead of 
`am335x-boneblack-wireless.dtb` (already built, above)  
   - `pushd ~/BeagleBoard-DeviceTrees`  
   - `sudo mv /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-uboot-univ.dtb 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-uboot-univ.bak.dtb`  
   - `sudo cp ./src/arm/am335x-boneblack-uboot-univ.dtb 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-uboot-univ`  
   - `dtdiff /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-uboot-univ.bak.dtb 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-uboot-univ.dtb`  
   - verify no occurrences of `pwr` in the decompiled tree:  
- `dtc -I dtb -O dts -o ./src.txt  
./src/arm/am335x-boneblack-uboot-univ.dtb`  
- `nano src.txt`  
   - _the `tps65217_pwr_but` IRQ is still present_  
 - check irq's:  
$ cat /proc/interrupts | grep 65217
```  
142:  0  INTC   7 Level tps65217-irq
144:  0  tps65217   0 Edge  vbus
145:  0  tps65217   2 Edge  tps65217_pwr_but
```   


On Wednesday, October 28, 2020 at 7:46:13 AM UTC-4 Joe Glandorf wrote:

> If I just tap the power button on the BBBW, it immediately begins the 
> shutdown sequence.  We need to avoid that behavior; it seems the way to do 
> so is to disable the PB-state change IRQ (from the TPS65217 datasheet):  
>   8.6.4 Interrupt Register (INT) (Address = 0x02) [reset = 0x80]
>   Bit 6:  PBM  R/W  0b = Interrupt is issued when PB status changes.
>   Bit 6:  PBM  R/W 1b = No interrupt is issued when PB status changes.
> The bit is cleared:
>   `i2cget -f -y 0 0x24 0x2`  
>   ` 0x20`
> A similar post from 2017 didn't really seem to have a resolution:  
> "Disabling PowerOff and Reset button" 
> https://groups.google.com/g/beagleboard/c/4qv0osguaDI/m/0ITntryPAQAJ  
> I've followed a similar path, outlined in more detail below, without being 
> able to disable the PB IRQ, either.  
> Thanks for any assistance.
>
> The hardware is a BBBW with a 4D Systems gen4 cape and LCD.  
> `$ uname -a`  
> `Linux beaglebone 4.19.94-ti-r43 #1buster SMP PREEMPT Wed Apr 22 
> 06:11:16 UTC 2020 armv7l GNU/Linux`  
> The image is from 
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Buster_LXQt_Snapshot
>  
> , as it works with the LCD out-of-the-box.  
>
>   - start with RCN's DT repo:  
>   - `git clone https://github.com/beagleboard/BeagleBoard-DeviceTrees` 
> <https://github.com/beagleboard/BeagleBoard-DeviceTrees>  
>   - `pushd ~/BeagleBoard-DeviceTrees`  
>   - `fgrep -rni . -e 'tps65217-pwrbutton'`  
> `./src/arm/tps65217.dtsi:27: compatible = 
> "ti,tps65217-pwrbutton";`  
>   - `nano ./src/arm/tps65217.dtsi`  
> comment out the `pwrbutton` node  
> ```  
> /*
> pwrbutton {
> compatible = "ti,tps65217-pwrbutton";
> interrupts = <2>;
> status = "disabled";
> };
>
> */
> ``` 
>  - Note that it doesn't matter if the above file is modified, or the one 
> below, or both.  In no case is the PB IRQ disabled.
>
>   - edit the common BB file, `am335x-bone-common.dtsi`, to disable the 
> `pwrbutton` 
>   - `pushd ~/BeagleBoard-DeviceTrees`  
>   - `nano -l ./src/arm/am335x-bone-common.dtsi`  
>- the line to edit is ~365  
>- change status from `okay` to `disabled`:  
>   ```  
> pwrbutton {
> status = "disabled";
> };  
>   ```  
>   - build the dtb files:  `make`  
>   - back up the current dtb file, then copy the new dtb file 
> ```  
> debian@beaglebone:~/BeagleBoard-DeviceTrees$ sudo mv 
> /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.dtb 
> /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.bak.dtb
> debian@beaglebone:~/BeagleBoard-DeviceTrees$ sudo cp 
> ./src/arm/am335x-boneblack-wireless.dtb 
> /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.dtb   
> ```  
>
>   - Compare the resulting dtb file with the original:  
>- the entire `pwrbutton` section commented out in `tps65217.dtsi`  
>- `pwrbutton` set to `disabled` in `am335x-bone-common.dtsi`  
> ```  
> $ dtdi

[beagleboard] Disable Power Button IRQ from TPS65217 on BBBW?

[Joe Glandorf]

If I just tap the power button on the BBBW, it immediately begins the 
shutdown sequence.  We need to avoid that behavior; it seems the way to do 
so is to disable the PB-state change IRQ (from the TPS65217 datasheet):  
  8.6.4 Interrupt Register (INT) (Address = 0x02) [reset = 0x80]
  Bit 6:  PBM  R/W  0b = Interrupt is issued when PB status changes.
  Bit 6:  PBM  R/W 1b = No interrupt is issued when PB status changes.
The bit is cleared:
  `i2cget -f -y 0 0x24 0x2`  
  ` 0x20`
A similar post from 2017 didn't really seem to have a resolution:  
"Disabling PowerOff and Reset button" 
https://groups.google.com/g/beagleboard/c/4qv0osguaDI/m/0ITntryPAQAJ  
I've followed a similar path, outlined in more detail below, without being 
able to disable the PB IRQ, either.  
Thanks for any assistance.

The hardware is a BBBW with a 4D Systems gen4 cape and LCD.  
`$ uname -a`  
`Linux beaglebone 4.19.94-ti-r43 #1buster SMP PREEMPT Wed Apr 22 
06:11:16 UTC 2020 armv7l GNU/Linux`  
The image is 
from 
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Buster_LXQt_Snapshot
 
, as it works with the LCD out-of-the-box.  

  - start with RCN's DT repo:  
  - `git clone https://github.com/beagleboard/BeagleBoard-DeviceTrees`  
  - `pushd ~/BeagleBoard-DeviceTrees`  
  - `fgrep -rni . -e 'tps65217-pwrbutton'`  
`./src/arm/tps65217.dtsi:27: compatible = 
"ti,tps65217-pwrbutton";`  
  - `nano ./src/arm/tps65217.dtsi`  
comment out the `pwrbutton` node  
```  
/*
pwrbutton {
compatible = "ti,tps65217-pwrbutton";
interrupts = <2>;
status = "disabled";
};

*/
``` 
 - Note that it doesn't matter if the above file is modified, or the one 
below, or both.  In no case is the PB IRQ disabled.

  - edit the common BB file, `am335x-bone-common.dtsi`, to disable the 
`pwrbutton` 
  - `pushd ~/BeagleBoard-DeviceTrees`  
  - `nano -l ./src/arm/am335x-bone-common.dtsi`  
   - the line to edit is ~365  
   - change status from `okay` to `disabled`:  
  ```  
pwrbutton {
status = "disabled";
};  
  ```  
  - build the dtb files:  `make`  
  - back up the current dtb file, then copy the new dtb file 
```  
debian@beaglebone:~/BeagleBoard-DeviceTrees$ sudo mv 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.dtb 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.bak.dtb
debian@beaglebone:~/BeagleBoard-DeviceTrees$ sudo cp 
./src/arm/am335x-boneblack-wireless.dtb 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.dtb   
```  

  - Compare the resulting dtb file with the original:  
   - the entire `pwrbutton` section commented out in `tps65217.dtsi`  
   - `pwrbutton` set to `disabled` in `am335x-bone-common.dtsi`  
```  
$ dtdiff /boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.bak.dtb 
/boot/dtbs/4.19.94-ti-r43/am335x-boneblack-wireless.dtb
--- /dev/fd/63  2020-10-28 02:56:38.720410323 +
+++ /dev/fd/62  2020-10-28 02:56:38.720410323 +
@@ -280,7 +280,7 @@

chosen {
base_dtb = "am335x-boneblack-wireless.dts";
-   base_dtb_timestamp = "Wed Apr 22 06:09:34 2020";
+   base_dtb_timestamp = "Tue Oct 27 19:48:20 2020";
stdout-path = "/ocp/serial@44e09000";
};

@@ -851,9 +851,7 @@
};

pwrbutton {
-   compatible = 
"ti,tps65217-pwrbutton";
-   interrupts = < 0x02 >;
-   status = "okay";
+   status = "disabled";
};

regulators {
```  

 - check IRQ's:  
$ cat /proc/interrupts | grep 65217
```  
142:  0  INTC   7 Level tps65217-irq
144:  0  tps65217   0 Edge  vbus
145:  0  tps65217   2 Edge  tps65217_pwr_but
```   

-- 
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/8593581f-3981-4e3d-ad88-d7c4a6cbc39bn%40googlegroups.com.

Re: [beagleboard] Does anyone have experience installing a RedHat 7 operating system on this board?

[joe dynon]

Thanks for the info my friend.  I appreciate it.  I think we are working
with a custom image and wouldn't be able to get one from CentOS.

On Wed, Jul 17, 2019 at 1:12 PM Robert Heller  wrote:

> *RedHat* does not support the ARM processor, but *CentOS* does.  I don't
> know
> if there is an image for the *beagles*, but there are images for the
> Raspberry
> Pi.  (Actually, the Raspberry Pi is a faster machine and is generally
> cheaper
> than a Beagle Bone Black.)
>
> At Wed, 17 Jul 2019 07:25:14 -0700 (PDT) beagleboard@googlegroups.com
> wrote:
>
> >
> >
> >
> > We are thinking about buying one of these but aren't sure if we can put
> a
> > RedHat OS on it.  We specifically need to use RedHat 7.6.  If anyone has
> > done this or knows if it's even possible, please respond.  Thanks for
> your
> > time.
> >
>
> --
> Robert Heller -- 978-544-6933
> Deepwoods Software-- Custom Software Services
> http://www.deepsoft.com/  -- Linux Administration Services
> hel...@deepsoft.com   -- Webhosting Services
>
>
> --
> 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/Ekg5iLu_J2g/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/20190717171203.E216426C0168%40sharky3.deepsoft.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/CAPNMJ1pKZcOFKa-xq-ZCkW8auWzWNYN%2Bmgm9WaGZMXMk4jVNaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB pps0 assigned to serial4

[Joe Smith]

I have discovered that gpsd was causing the PPS device to get created for 
/dev/ttyS4. I had to recompile gpsd to turn off PPS support and that solved 
that particular part of the problem.

The issue I'm running into now is that when systemd goes to start chronyd, 
the kernel has not yet created the PPS source /dev/pps0 corresponding the 
the NF3H-PPS-00A0.dtbo overlay. Does anybody know how I can prevent chronyd 
from starting before /dev/pps0 is created by the kernel?

On Monday, November 27, 2017 at 3:21:37 PM UTC-5, Joe Smith wrote:
>
> I have a BeagleBone Black configured with U-Boot overlays for PPS input on 
> header pin 9.12 and UART4 on 9.11 and 9.13. This is being fed from an 
> AdaFruit Ultimate GPS breakout board.
>
> Excerpt from /boot/uEnv.txt
>
> uboot_overlay_addr0=/lib/firmware/NF3H-PPS-00A0.dtbo
> uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo
>
> No other mods were made to uEnv.txt. Initially when I set it up, all 
> appeared good, with the PPS input getting assigned to /dev/pps0  Then all 
> of a sudden on my last reboot the PPS input started getting assigned to 
> /dev/pps1 and serial4 getting assigned to /dev/pps0  I noticed something 
> like this before I installed the latest BBB debian image but dismissed it. 
> Now that I see it again I have questions as to what is causing it. I need 
> to be able to reliably predict what PPS device is getting assigned, as this 
> BBB is being set up as a GPS NTP server using GPSD and Chrony. See dmesg 
> output below.
>
> [   17.330602] pps_ldisc: PPS line discipline registered
> [   17.332357] pps pps0: new PPS source serial4
> [   17.332431] pps pps0: source "/dev/ttyS4" added
>
> Then later in dmesg output...
>
> [   26.246745] pps pps1: new PPS source ocp:bs_pinmode_P9_12_0x27_pinm
> [   26.246871] pps pps1: Registered IRQ 88 as PPS source
>
> Does anybody have any ideas as to what is causing this? The uEnv.txt mods 
> above are the only system changes made other than doing apt-gets to install 
> the necessary debian packages for ppstools, gpsd, man-db, and chrony. I 
> also had to build and "make install" chrony from source in order to get PPS 
> support built in. If the answer is that it'll always be /dev/pps1 I'm OK 
> with that. It's just that it has flopped around on me a couple of times now 
> for reasons I don't understand. Now when I power-cycle or reboot the BBB, 
> the chrony service will not start because it fails to open /dev/pps1 yet 
> when I do a ppstest /dev/pps1 I see the PPS input coming in. Almost as if 
> during startup the chrony service is trying to access /dev/pps1 before it 
> is ready. If I then start chrony manually with systemctl start chrony, it 
> starts up successfully.
>
> debian@beaglebone:~$ uname -a
> Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
> GNU/Linux
>

-- 
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/675e326c-ca77-446f-9f3a-ada62e88cb7a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB pps0 assigned to serial4

[Joe Smith]

I have a BeagleBone Black configured with U-Boot overlays for PPS input on 
header pin 9.12 and UART4 on 9.11 and 9.13. This is being fed from an 
AdaFruit Ultimate GPS breakout board.

Excerpt from /boot/uEnv.txt

uboot_overlay_addr0=/lib/firmware/NF3H-PPS-00A0.dtbo
uboot_overlay_addr1=/lib/firmware/BB-UART4-00A0.dtbo

No other mods were made to uEnv.txt. Initially when I set it up, all 
appeared good, with the PPS input getting assigned to /dev/pps0  Then all 
of a sudden on my last reboot the PPS input started getting assigned to 
/dev/pps1 and serial4 getting assigned to /dev/pps0  I noticed something 
like this before I installed the latest BBB debian image but dismissed it. 
Now that I see it again I have questions as to what is causing it. I need 
to be able to reliably predict what PPS device is getting assigned, as this 
BBB is being set up as a GPS NTP server using GPSD and Chrony. See dmesg 
output below.

[   17.330602] pps_ldisc: PPS line discipline registered
[   17.332357] pps pps0: new PPS source serial4
[   17.332431] pps pps0: source "/dev/ttyS4" added

Then later in dmesg output...

[   26.246745] pps pps1: new PPS source ocp:bs_pinmode_P9_12_0x27_pinm
[   26.246871] pps pps1: Registered IRQ 88 as PPS source

Does anybody have any ideas as to what is causing this? The uEnv.txt mods 
above are the only system changes made other than doing apt-gets to install 
the necessary debian packages for ppstools, gpsd, man-db, and chrony. I 
also had to build and "make install" chrony from source in order to get PPS 
support built in. If the answer is that it'll always be /dev/pps1 I'm OK 
with that. It's just that it has flopped around on me a couple of times now 
for reasons I don't understand. Now when I power-cycle or reboot the BBB, 
the chrony service will not start because it fails to open /dev/pps1 yet 
when I do a ppstest /dev/pps1 I see the PPS input coming in. Almost as if 
during startup the chrony service is trying to access /dev/pps1 before it 
is ready. If I then start chrony manually with systemctl start chrony, it 
starts up successfully.

debian@beaglebone:~$ uname -a
Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l 
GNU/Linux

-- 
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/c33a66f2-6138-47e4-9f54-f6188a268ee8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] EEPROM Serial Number for cape

[Joe Vanderstelt]

The SRM states (in 8.2.4)  State the serial number should be WWYY 
is that a requirement or can I use my own serial number?

I am asking because I want to get my cape approved 
https://beagleboard.org/approved

-- 
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/aa8218a0-15cd-402a-ab68-ae15e7c7e91d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Booting BeagleBone Black without a Power Button

[Joe Kleespies]

Hey All,

I'm in the process of designing a custom version of the BeagleBone Black. 
In my application, I don't want a power button. I'd like the board to boot 
as soon as the AC or USB signal is energized on the PMIC. I know that, by 
default, the BeagleBone Black looks for the PB INT bit in the PMIC INT 
register before asserting the PMIC_PWR_EN. In my application, I assume I'd 
need to modify boot code to look for the AC or USB INT bits in the PMIC INT 
register. My question is whether or not this requires a modification of the 
SPL or if the processor handles this in the primary boot code in ROM.

Any advice is much appreciated.

-- 
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/7f249028-9b5e-4db7-b7fe-cd30b1e243e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Modifying BeagleBone Black Boot Code to Eliminate Power Button

[Joe Kleespies]

Hey All,

We're in the process of making a custom version of the BeagleBone Black. 
Because this is a custom board, I assume that some sort of boot code needs 
to be flashed to the processor ROM, which handles initial booting of the 
processor before passing control to an image in eMMC or SD. Does anyone 
know where this primary boot code for the BeagleBone Black can be found and 
how it is flashed to the processor?

Also, in our application, we don't want a power button. We'd like the board 
to begin booting as soon as power is applied on either the AC or USB inputs 
of the PMIC. I assume that, by default, the BeagleBone Black boot code 
reads the INT register on the PMIC and asserts the PMIC_PWR_EN line only 
when it reads a set PB INT bit. We'd like to modify this code such that the 
processor asserts PMIC_PWR_EN when it reads the AC or USB INT bits.

Does anyone know where the boot code can be found and where it should be 
modified to suit this application?

Thanks in advance,

Joe

-- 
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/c42a0da2-6d77-44c8-96a0-a49e103d5ec3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Is there a GPIO status register somewhere?

[Joe Hupcey III]

Thanks, Dennis, for the detailed response!

[headsmack] to myself for missing the "GPIO_DATAIN Register" section
in the Sitara docs.

This is what has been concerning me about the file reading approach:
>  it may also be that for the duration the "file" is open, others may be 
> blocked

But then again for my application I only need to poll the files'
status every 2-3 seconds or so -- nothing high bandwidth at all.


> Are A/B/C and M (master) truly independent?

Yes -- they are all separate programs kicked off at boot time by their
own crontabs -- M is the only program that has to see all the pins --
A, B, and C don't need to know or care about each other.

Regarding the master program M, I still want to keep A, B, and C
independent and ignorant of each other, but I really like your idea of
a "status queue" + monitoring and ack mechanism for A, B, and C
themselves.

Great food for thought, and thanks again for the detailed post and
suggestions!!!

Joe



On Sat, Jun 3, 2017 at 5:58 AM, Dennis Lee Bieber  wrote:
> On Thu, 1 Jun 2017 20:46:43 -0700 (PDT),
> jhup...@gmail.com declaimed the following:
>
>>Hello!
>>
>>On a Beagle Bone Black Rev C is there a digital GPIO status register where
>>I can simply read the [digital] status of all the GPIOs?
>>
>
> There is a register for each GPIO bank (actually, a slew of registers
> for each bank), but "simply read" may not be the case. {Further info below}
>
>>
>>Is there a way for two or more separate programs to read-only monitor the
>>same digital GPIO pin at the exact same time?
>>
>
> The sys filesystem approach is to open/(read|write)/close the "file"
> associated with each individual GPIO pin. I haven't experimented to see if
> one can hold the "file" open and rewind (seek 0)/reread to get updates, or
> must do the close/open stuff for each read. For a polling loop, that may be
> a lot of OS overhead -- it may also be that for the duration the "file" is
> open, others may be blocked (unless it can be opened in a shared read-only
> mode without blocking the OS from updating the status).
>
> Last time I looked, this is the method used by the BBIO Python
> libraries.
>
>>
>>I've looked through the PDF on the Sitara processor, every doc & book on
>>the BBB I could find, and through this board, and I have had no luck
>>finding reference to such an animal. I'm posting here since someone may
>>have discovered an "undocumented feature" like this.
>>
>
> Unless I have the wrong document (AM335x and AMIC110 Sitara™ 
> Processors
> Technical Reference Manual; Literature Number: SPRUH73P October
> 2011–Revised March 2017) what you are asking for is in Chapter 25. The
> registers are listed in table 25.5 (as offsets -- I haven't found where the
> banks are located yet). You probably want GPIO_DATAIN.
>
> """
> 25.4.1.17 GPIO_DATAIN Register (offset = 138h) [reset = 0h]
>
> GPIO_DATAIN is shown in Figure 25-24 and described in Table 25-22.
>
> The GPIO_DATAIN register is used to register the data that is read from the
> GPIO pins. The GPIO_DATAIN register is a read-only register. The input data
> is sampled synchronously with the interface clock and then captured in the
> GPIO_DATAIN register synchronously with the interface clock. So, after
> changing, GPIO pin levels are captured into this register after two
> interface clock cycles (the required cycles to synchronize and to write the
> data). When the AUTOIDLE bit in the system configuration register
> (GPIO_SYSCONFIG) is set, the GPIO_DATAIN read command has a 3 OCP cycle
> latency due to the data in sample gating mechanism. When the AUTOIDLE bit
> is not set, the GPIO_DATAIN read command has a 2 OCP cycle latency.
> """
>
> Ah... Chapter 2 "Memory Map", with some digging, gives the base
> addresses for the GPIO banks (GPIO0 is in a different table from the other
> three -- as it is "wake-up" event capable).
>
> Getting access to the banks likely involves mmap operations, and that
> may require running as root (granted, without doing some games to give user
> accounts privileges in the sys filesystem, even the simple open/read/close
> stuff requires root -- I believe work is being done to make GPIO, if not
> the rest of the peripherals, accessible to user accounts).
>
> Of course, mapping bank/register/bit to each external GPIO is left as
> an exercise...
>
>>
>>Back story:
> 
>>More specifically, my use case example is: independent programs A, B, and C
>>each monitor a own GPIO and perform different

Re: [beagleboard] Re: config-pin does not work for all pins on BBBW

[Joe Vanderstelt]

This solved my problem

https://github.com/RobertCNelson/linux-stable-rcn-ee/issues/1

On Sat, Apr 22, 2017, 9:47 AM Charles Steinkuehler 
wrote:

> On 4/20/2017 8:51 PM, thisboyiscr...@gmail.com wrote:
> > I am having  the same problem with P9_31.
> >
> > I think it is because you need to disable the audio but I can not figure
> out how
> > to do that.
>
> Disable the HDMI virtual cape in your uEnv.txt file.  This leaves the
> HDMIn (HDMI with no audio) enabled, so you will still have a display.
>
> In uEnv.txt:
> optargs=capemgr.disable_partno=BB-BONELT-HDMI
>
> --
> Charles Steinkuehler
> char...@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/g5pVlvhj-q4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/daf701de-1591-02cd-d0e6-a60a6ad93e3b%40steinkuehler.net
> .
> 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/CAAb3x5aruaNKwdTJwJ6JTptXyupXt_hwXbPu72Ze3uZU_qia%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBGW SPI0 data corrupt

[Joe Phaneuf]

Pretty confident it's not kernel version. Actually explored that line of 
thinking a little, but there's a u-boot spi tool you can use to test before 
the kernel even loads, and you can replicate this issue with that.

FYI response from Seeed regarding the existence of the caps is that they're 
for EMC related to the UART on the Grove connector.

This is the location of the spi0 capacitors (Should only need to remove the 
one on clock, but I removed both, forget which one is which).  Near the sd 
card slot, underneath the grove connectors:

<https://lh3.googleusercontent.com/-uE8y1zCNuvY/WEGpUUGI9_I/Ahs/UtQrknyZH3ExCItVhhWf_-_sveyWlE1fACLcB/s1600/BBGW.jpg>


On Thursday, December 1, 2016 at 10:16:14 PM UTC-8, Buming Chen wrote:
>
> Thanks! Could you tell me where is the cap on the board? Already read the 
> BBGW's SCH, but still couldn't figure it out
> And do you think this is the problem caused by specific kernel versions 
> (I'm using ubuntu 16.04, 4.4.12-ti-r30)? I assume using SPI0 for 
> communication is really common among BBGW users, but after I searched the 
> whole forum, just you and me encountered this CLK hardware design issue??   
>
> On Friday, December 2, 2016 at 12:43:24 AM UTC+8, Joe Phaneuf wrote:
>>
>> Howdy, correct, had to completely remove the cap on the spi0 clock. Hope 
>> that helps!
>>
>

-- 
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/82c331b9-3507-4acb-b61c-bdf54857d264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBGW SPI0 data corrupt

[Joe Phaneuf]

Howdy, correct, had to completely remove the cap on the spi0 clock. Hope that 
helps!

-- 
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/fccba153-c249-4df7-bdc4-e5c419151916%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBGW SPI0 data corrupt

[Joe Phaneuf]

resolved, 100pF cap on SPI0 clock near the grove connector causing 
reflections, resulting in double-clocking data. sigh.

-- 
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/56125c13-19aa-4cfa-83a8-edeb87a2731d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBGW SPI0 data corrupt

[Joe Phaneuf]

Hey, cross posting from seeed studio forums.


tldr: clocking in data on spi0 looks cattywompus, spi1 ok

Was noticing an issue with some custom hardware/software that utilizes both 
spi channels, was working on beaglebone black prior.  Wanted to make it 
easily reproducible so flashed a bbgw and used adafruit bbio library as an 
example. 

steps:

1.) flash BBGW with latest production image 4.4.15-ti-r37 (other kernel 
versions and imaged used as well) 

2.) prevent sound drivers from loading, as they conflict with spi1:

  cd /lib/modules/4.4.15-ti-r37/kernel/sound/core

  mv snd.ko snd.ko.bkp

3.) install adafruit library from source (need latest greatest, pip upgrade 
didn't work)

  cd ~
  git clone 
https://github.com/adafruit/adafruit-beaglebone-io-python.git
  cd adafruit-beaglebone-io-python
  python setup.py install
  cd ..

4.) reboot 

5.) use wires to loopback MOSI to MISO, both channels

  short P9.18 and P9.21 with a piece of wire (SPI0)

  short P9.29 and P9.30 with a piece of wire (SPI1)

6.) put the following into a file and run it

from Adafruit_BBIO.SPI import SPI
def run(x,y):

  print 'running spi {} {}'.format(x,y)
  spi = SPI(x,y)
  spi.mode=2
  spi.msh=400
  bytes2send = range(20)
  print 'sending {}'.format(bytes2send)
  print spi.xfer2(bytes2send)
  spi.close()

run(0,0)
run(1,0)

result:
sending [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 
19]
[128, 7, 28, 31, 112, 231, 124, 127, 192, 135, 156, 159, 240, 231, 252, 
255, 0, 7, 28, 31]
running spi 1 0
sending [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 
19]
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19]

so, spi1 works in loopback.  spi0...wtf? there are places where it looks 
like it's double clocking MISO (like a 0x0001 becomes a 0x0011), 
some of it just looks random. Works fine on beaglebone black.

Thoughts?
If anyone has spi0 working on a bbgw would love to hear about the setup.
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 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/83280ea1-4688-4f88-a1eb-f82e512a71c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] SPI0 data in corrupt

[Joe Phaneuf]

Cross posting from seeed forums, no responses there.

If anyone has had any success whatsoever using spi0 on a beagle bone green 
wireless, would love to hear about it.


tldr: clocking in data on spi0 looks cattywompus, spi1 ok


Was noticing an issue with some custom hardware/software that utilizes both 
spi channels, was working on beaglebone black prior.  Wanted to make it 
easily reproducible so flashed a bbgw and used adafruit bbio library as an 
example. 

steps:

1.) flash BBGW with latest production image 4.4.15-ti-r37 (tested on 4.1 
kernel, and some other images that I forgot to document as well)

2.) prevent sound drivers from loading, as they conflict with spi1:

  cd /lib/modules/4.4.15-ti-r37/kernel/sound/core
  mv snd.ko snd.ko.bkp

3.) install adafruit library from source (need latest greatest, pip upgrade 
didn't work)

  cd ~
  git clone 
https://github.com/adafruit/adafruit-beaglebone-io-python.git
  cd adafruit-beaglebone-io-python
  python setup.py install
  cd ..

4.) use wires to loopback MOSI to MISO, both channels

  short P9.18 and P9.21 with a piece of wire (SPI0)

  short P9.29 and P9.30 with a piece of wire (SPI1)

5.) put the following into a file and run it

from Adafruit_BBIO.SPI import SPI
def run(x,y):

  print 'running spi {} {}'.format(x,y)
  spi = SPI(x,y)
  spi.mode=2
  spi.msh=400
  bytes2send = range(20)
  print 'sending {}'.format(bytes2send)
  print spi.xfer2(bytes2send)
  spi.close()

run(0,0)
run(1,0)

result:
sending [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 
19]
[128, 7, 28, 31, 112, 231, 124, 127, 192, 135, 156, 159, 240, 231, 252, 
255, 0, 7, 28, 31]
running spi 1 0
sending [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 
19]
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19]

so, spi1 works in loopback.  spi0...wtf? there are places where it looks 
like it's double clocking MISO (like a 0x0001 becomes a 0x0011), 
some of it just looks random. Works fine on beaglebone black.

Thoughts?

-- 
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/c34759e0-e2c3-4c99-a3c3-8160b89a4ff9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB boot from SPI flash

[Joe Desbonnet]

I just tried the latest u-boot 2016.05 and it worked this time without any 
difficulty.  I just had to edit configs/am335x_boneblack_defconfig and 
replace option CONFIG_SYS_EXTRA_OPTIONS with 
CONFIG_SYS_EXTRA_OPTIONS="SPI_BOOT" and add line CONFIG_SPI_FLASH_STMICRO=y 
 (because my SPI flash chip is a ST Microelectronics M25P16).

I was able to program the flash from another build of u-boot with the SPI 
bus enabled by entering the following commands from the u-boot command 
prompt:

sf probe 0
sf erase 0 +20
mmc rescan
fatload mmc 0 ${loadaddr} MLO.byteswap
sf write ${loadaddr} 0 ${filesize}
fatload mmc 0 ${loadaddr} u-boot.img
sf write ${loadaddr} 0x2 ${filesize}

To test, hold down the Beaglebone Black S2 button while applying power. 
That kicks in an alternative boot order which puts boot over SPI0 bus at 
the top of the list.

Joe.


On Wednesday, 15 June 2016 12:13:08 UTC+1, Joe Desbonnet wrote:
>
> I'm attempting to implement boot to Linux from SPI flash on the Beaglebone 
> Black. The motivation is to implement secure boot using u-boot vboot from 
> write protected SPI flash. 
>
> I've been working with 2016.01 u-boot release. 
>
> My progress to date is that I can boot the u-boot SPL (MLO) from SPI and 
> that runs, but it didn't find any SPI device to boot from. So patched the 
> code to enable pin mux for SPI0 and forced SPI boot in common/spl/spl.c. 
>
> Now I can see it loading u-boot.img from 0x2 over the SPI bus. But it 
> hangs when attempting to jump to the loaded u-boot.
>
> Wondering has anyone got a howto on this? 
>
> Thanks,
> Joe.
>
>

-- 
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/2dd48a31-98ed-4666-af7a-0678bb15d7fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB boot from SPI flash

[Joe Desbonnet]

I'm attempting to implement boot to Linux from SPI flash on the Beaglebone 
Black. The motivation is to implement secure boot using u-boot vboot from 
write protected SPI flash. 

I've been working with 2016.01 u-boot release. 

My progress to date is that I can boot the u-boot SPL (MLO) from SPI and 
that runs, but it didn't find any SPI device to boot from. So patched the 
code to enable pin mux for SPI0 and forced SPI boot in common/spl/spl.c. 

Now I can see it loading u-boot.img from 0x2 over the SPI bus. But it 
hangs when attempting to jump to the loaded u-boot.

Wondering has anyone got a howto on this? 

Thanks,
Joe.

-- 
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/cad4c085-ab62-4972-9d95-de24b8bd6836%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

[Joe Julian]

As far as I can tell, based 
on 
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/PKGBUILD,
 
the Arch Linux kernel I'm using *should* have all the necessary patches to 
make this work with 4.5.2. Unfortunately it's not. aplay -l still shows no 
drivers.

@RobertCNelson do you see anything wrong with that patch set that might be 
a problem? I'd really prefer to use Arch since the package versions are new 
enough to support some of the features I'm trying to implement.

I do, of course, have the correct resolution and I confirmed the edid does 
have the audio block.

-- 
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/d657b060-4d2a-442f-9f8a-caf5b95f0b07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Play audio throuhg HDMI on BeagleBone Black

[Joe Julian]

On Tuesday, March 22, 2016 at 9:35:54 AM UTC-7, RobertCNelson wrote:
>
> On Tue, Mar 22, 2016 at 11:31 AM,  > 
> wrote: 
>
> HDMI audio is in patch hell on mainline, if you want to use "4.1.x" 
> with hdmi audio you need to use the ti branch: 
>
>
>
Do you  have a reference?

-- 
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/6a5d7e32-2886-421e-b611-67a3468c4652%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Working kexec example for BBB?

[Joe Desbonnet]

Has any one got kexec to work on the Beagle Bone Black? 

I'm using Debian 7.9 and 8.3, but I'd be delighted to get a working recipe 
for any BBB distribution. 

I'm currently trying something like this:

KERNEL=/boot/vmlinuz-3.8.13-bone79 
INITRD=/boot/initrd.img-3.8.13-bone79
CMDLINE="console=tty0 console=ttyO0,115200n8 root=/dev/mmcblk0p2 
rootfstype=ext4 rootwait coherent_pool=1M quiet init=/lib/systemd/systemd 
cape_universal=enable"
kexec --load "${KERNEL}" --append="${CMDLINE}" --initrd="${INITRD}"

I get this warning:
Cannot open /proc/atags: No such file or directory

Then:
kexec -e

after which I get:

(NULL device *): gadget not registered
Starting new kernel

and that's it... hangs indefinitely. Any tips greatly appreciated.
Joe.

-- 
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: GPIO 1 28 on Debian

[Joe]

It sounds like the line is configured to be a clock signal, perhaps it is 
in MODE 6 (mcasp0_aclkr_mux3)?

What dtb/overlays are you using when booting?

On Tuesday, December 1, 2015 at 1:30:56 PM UTC-6, rshiel...@gmail.com wrote:
>
> After booting Debian for Beaglebone Black I looked at P9 pin 12 (GPIO 1 
> 28) on an oscilloscope, their is a positive 65ms wide positive pulse that 
> repeats approximately every second. 
>
> Is this pin not set up as a GPIO pin? 
>
> I tried 
>
> echo 60 > /sys/class/gpio/export
>
>
> However when I tried 
>
> ls -al /sys/class/gpio
>
>
> after this gpio60 did not show up. 
>

-- 
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: Using gpio2[4] as chip select 2 for SPI1

[Joe]

It turns that the spi-omap2 driver in Linux 4.1 does not support GPIO chip 
selects.  However, Linux 4.3 rc7 supports it with a patch.  I wrote up 
details on using the mikroBUS Cape with 4 SPI devices here: 
 
http://dev.iachieved.it/iachievedit/adventures-in-beaglebone-black-device-overlays-and-spi/

and explain the patch to the spi-omap2 driver here: 
 http://dev.iachieved.it/iachievedit/gpio-chip-selects-with-the-beaglebone/

Hopefully it's useful to someone wrestling with multiple SPI devices on the 
BeagleBone.

Joe


On Sunday, November 15, 2015 at 10:45:06 PM UTC-6, Joe wrote:
>
>
> Howdy.
>
> I came into possession of a mikroBUS Cape (
> http://beagleboard.org/project/mikrobus) and have been using it to learn 
> how to write a .dts overlay.  Since there are 4 slots for clickboards on 
> the cape and I have 4 SPI boards (4-20mA T Click), I figured I'd try to 
> create a single .dts that exposed all 4 as SPI devices.
>
> Ignoring SPI0 (routed to "Host 3" on the mikroBUS Cape) for now, I have 
> Host 1 and Host 2 working.  These map directly to SPI1.0 and SPI1.1, but I 
> cannot get a "SPI1.2" enabled (Host4).  The mikroBUS Cape schematic shows 
> that chipselect for Host 4 is routed to P8.10, so I thought I could add 
> that pin (gpio2_4) as OUTPUT_PULLUP | MODE 7, and then simply add a third 
> fragment for the third chipselect.
>
>   spi1@2 {
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "spidev";
> reg = <2>;
> spi-max-frequency = <1600>;
> spi-cpol;
> spi-cpha;
>   };
>
> Unfortunately this fails with a "cs2 >= max2" error when I load the 
> overlay.
>
> Reading around I'm trying to figure out, okay, how do I increase the 
> number of SPI devices on the SPI1 bus.  I've read about:
>
> num-cs
> num-chipselects
> cs-gpios
>
> When using cs-gpios like this:
>
>   cs-gpios = <0>, <1>, <&gpio3 4 0>;
>
> I get 
>
> [  171.494015] /ocp/spi@481a: could not get #gpio-cells for 
> /ocp/interrupt-controller@4820
>
> My complete dts is at http://pastebin.com/BvxZ3fa2
>
> TL;DR:  How can I enable a 3rd chipselect for SPI1 where the CS is mapped 
> to P8.11 (gpio2[4])?
>

-- 
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] X15 as a Build Machine

[Joe]

Oh, that is without a doubt.  My experience with QEMU has been 
disappointing as best.  The final straw was trying to build images that 
included NodeJS modules in the base image 
- https://github.com/nodejs/node-v0.x-archive/issues/8616 - a number of 
folks reported the near impossibility of getting that to work reliably.

At any rate, I've run a couple of kernel compiles on the X15 and it still 
takes quite a bit of time, but I'm thinking I'm IO bound at the moment 
(can't get the USB3 ports working with USB3 devices).

On Wednesday, November 25, 2015 at 3:49:22 PM UTC-6, john3909 wrote:
>
> Running omap-image-builder on the BeagleBoard-x15 is way faster and more 
> reliable than using QEMU on quad core x86 machine.
>
> Regards,
> John
>
>
>
>
> On Nov 25, 2015, at 1:13 PM, Joe > wrote:
>
> Howdy,
>
> I've come into a possession of an X15 and would like to help provide 
> feedback to the community in any way possible.  My area of expertise lies 
> on the software development side, though I occasionally dabble in working 
> with hardware, capes, device trees, etc.
>
> My first task is to use the X15 as a hard-core build system - I bought a 
> WandBoard a few months back to build Linux kernel images and filesystems, 
> and was underwhelmed with its USB2.0 and 10/100 Ethernet.  I also grow 
> weary of trying to using cross-compiler tools/QEMU, its always a pain.  I 
> see the X15 as a great platform to compile kernels, large applications, 
> build filesystems, create Debian packages, do Android development on 
> perhaps (though I don't do much Android development myself).  Is there 
> anything else others would like to see benchmarked, reviewed, etc?  I'd 
> love to help.
>
> Thanks,
> Joe
>
>
> -- 
> 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] X15 as a Build Machine

[Joe]

Howdy,

I've come into a possession of an X15 and would like to help provide 
feedback to the community in any way possible.  My area of expertise lies 
on the software development side, though I occasionally dabble in working 
with hardware, capes, device trees, etc.

My first task is to use the X15 as a hard-core build system - I bought a 
WandBoard a few months back to build Linux kernel images and filesystems, 
and was underwhelmed with its USB2.0 and 10/100 Ethernet.  I also grow 
weary of trying to using cross-compiler tools/QEMU, its always a pain.  I 
see the X15 as a great platform to compile kernels, large applications, 
build filesystems, create Debian packages, do Android development on 
perhaps (though I don't do much Android development myself).  Is there 
anything else others would like to see benchmarked, reviewed, etc?  I'd 
love to help.

Thanks,
Joe

-- 
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] miniPCIe+SIM cape

[Joe]

Howdy -

I'm looking for a BBB cape that has a miniPCIe slot and SIM card holder 
(2FF).  I'm pretty sure this one http://elinux.org/IOTYS:IOTCape fits my 
requirements but was wondering if there are other options out there (don't 
want to hitch my wagon before looking at other horses).  I'm actually 
surprised after quite a bit of Googling there aren't more cape options for 
this.

Joe

-- 
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: Setting up cross compiler under OS X 10.11 / El Capitan

[Joe Ciarcia]

I gave up on using OS X El Cap and Xcode for development on the Beaglebone. 
I posted to the crosstool-ng list to see if anyone could help with the 
errors I was seeing and I didn't get any responses (even though it's a 
pretty active list, I just suspect very few people are trying to do cross 
platform development for the arm on a Mac). I ended up installing Debian 
Jessie on an old Macbook (the original one actually, version 1,1) and 
everything just works great with it. After playing around a bit on the Mac 
I decided to buy a new Dell XPS 13 for development (warning there... you'll 
need to run Debian unstable with the 4.3 experimental kernel in order to 
support the new Skylake architecture but figuring all that out was MUCH 
easier than trying to build a cross compiler toolchain for Xcode). As for 
getting get the USB working... I never did but it looks like there's been 
some progress in the past few weeks. Check out Robert's post. 

As for connecting to it via ethernet (which is pretty easy)... you can 
either connect it directly to the ethernet port on your Mac, or you can 
connect it to your router. To log in all you have to do is open a terminal 
and ssh in...

ssh root@beaglebone.local

You don't have to fool around with IP addresses etc. as most of the 
tutorials indicate. Much easier that way. Once you're in though, create a 
new user so that you're not using root all the time.

If you want to go the Debian route, I highly recommend this video from 
Derek Molloy to get things started. It will show you how to get the Eclipse 
IDE up and running which will allow you to do cross compilation, remote 
deployment of your binaries, and remote debugging. It's pretty slick!

https://www.youtube.com/watch?v=T9yFyWsyyGk

Cheers, Joe

On Tuesday, November 17, 2015 at 2:11:30 PM UTC-5, theobo...@gmail.com 
wrote:
>
> Dear Joe,
>
> I see you are running os 10.11, me too.
> I'm not getting the BBB to be recognized by my mac.
> And when i'm trying to install the Serial driver, i get an error
> Can you help me?
>
> Op zaterdag 24 oktober 2015 16:27:43 UTC+2 schreef Joe Ciarcia:
>>
>> I've found some great resources out there that help us Mac folk out with 
>> building an arm toolchain on the OS X platform. Here they are if any others 
>> stumble across this thread looking for the same:
>>
>> http://www.benmont.com/tech/crosscompiler.html
>> http://will-tm.com/cross-compiling-mac-os-x-mavericks/
>> http://hansbot.blogspot.com/p/beaglebone-black-mac-os-x-toolchain.html 
>>  (this one is the most detailed)
>>
>>
>> I've gotten through a few of the stumbling blocks but I'm currently 
>> stuck. I get this far:
>>
>> [INFO ]  Performing some trivial sanity checks
>>
>> [INFO ]  Build started 20151023.200552
>>
>> [INFO ]  Building environment variables
>>
>> [00:03] /
>>
>>
>> So, after that, if I look at the activity monitor, bash is around 100% 
>> processor utilization on one of the cores. I figure "great, it's doing 
>> something". I left it to do its thing and after an hour, I killed the 
>> process. I changed a few settings... ran it again... same thing. Okay... 
>> maybe it just takes a really long time. I left it overnight. This morning 
>> it was still near 100% processor utilization and nothing had changed in the 
>> build.log file. Here's the last few lines from the build log:
>>
>>
>> [DEBUG]  =
>>
>> [DEBUG]  Checking that we can run gcc -v
>>
>> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-v' 
>>
>> [DEBUG]Configured with: 
>> --prefix=/Applications/Xcode.app/Contents/Developer/usr 
>> --with-gxx-include-dir=/usr/include/c++/4.2.1
>>
>> [DEBUG]Apple LLVM version 7.0.0 (clang-700.1.76)
>>
>> [DEBUG]Target: x86_64-apple-darwin15.0.0
>>
>> [DEBUG]Thread model: posix
>>
>> [DEBUG]  Checking that we can run gcc -v: done in 0.00s (at 00:03)
>>
>> [DEBUG]  =
>>
>> [DEBUG]  Checking that gcc can compile a trivial program
>>
>> [DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-O2' 
>> '-g' '-pipe' 
>> '/Volumes/CaSe/.build/arm-JoesBeaglebone-linux-gnueabi/build/test.c' '-o' 
>> '/Volumes/CaSe/.build/arm-unknown-linux-gnueabi/build/.gccout' 
>>
>> [DEBUG]  Checking that gcc can compile a trivial program: done in 0.00s 
>> (at 00:03)
>>
>> [EXTRA]

[beagleboard] Re: Detect active connection: ethernet and/or wifi?

[Joe]

Take a look at Network Manager/DBus 
- 
http://dev.iachieved.it/iachievedit/gauging-wireless-ap-stability-with-a-beaglebone-black/

Disclaimer:  I'm the author of above post, but it shows how I detect 
Ethernet/Wifi.

On Saturday, November 14, 2015 at 3:06:00 PM UTC-6, dlchambers wrote:
>
> How can I detect:
> a) If Cat5 ethernet has a live connection (to, say, a switch/router, 
> though perhaps not to the internet)
> b) If wifi has a live connection to
>   i) AP
>   ii) internet
> c) If both ethernet and wifi are present, which adapter is the one I'm 
> currently using?
>
> Many thanks,
> -Dave
>

-- 
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: Detect active connection: ethernet and/or wifi?

[Joe]

Eek - its this one, but I'm using a Pi:

http://dev.iachieved.it/iachievedit/exploring-networkmanager-d-bus-systemd-and-raspberry-pi/

On Monday, November 16, 2015 at 9:16:30 AM UTC-6, Joe wrote:
>
> Take a look at Network Manager/DBus - 
> http://dev.iachieved.it/iachievedit/gauging-wireless-ap-stability-with-a-beaglebone-black/
>
> Disclaimer:  I'm the author of above post, but it shows how I detect 
> Ethernet/Wifi.
>
> On Saturday, November 14, 2015 at 3:06:00 PM UTC-6, dlchambers wrote:
>>
>> How can I detect:
>> a) If Cat5 ethernet has a live connection (to, say, a switch/router, 
>> though perhaps not to the internet)
>> b) If wifi has a live connection to
>>   i) AP
>>   ii) internet
>> c) If both ethernet and wifi are present, which adapter is the one I'm 
>> currently using?
>>
>> Many thanks,
>> -Dave
>>
>

-- 
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: shrink emmc for backup

[Joe]

Can you clarify?  Do you want to decrease the size of the partition that is 
created by the flasher script or do you want to shrink the size of the 
partition of a running eMMC.  Also, can you clarify that you mean the 
onboard chip or a miniSD card?

On Sunday, November 15, 2015 at 11:57:12 PM UTC-6, Fohnbit wrote:
>
> Hello!
>
> Based on different eMMC chips I have the problem that dd backup can´t 
> restore on new BBB.
>
> Is it possible to shrink the partition on the eMMC? Maybe for 50MB?
>
> After this, dd Backup and restore?
>
> If yes, has maybe someone can help how I have to do this?
>
> Thank you!
>

-- 
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: Using gpio2[4] as chip select 2 for SPI1

[Joe]

Edit:  P8.10 (gpio2[4]) is the chipselect line I'm trying to create

On Sunday, November 15, 2015 at 10:45:06 PM UTC-6, Joe wrote:
>
>
> Howdy.
>
> I came into possession of a mikroBUS Cape (
> http://beagleboard.org/project/mikrobus) and have been using it to learn 
> how to write a .dts overlay.  Since there are 4 slots for clickboards on 
> the cape and I have 4 SPI boards (4-20mA T Click), I figured I'd try to 
> create a single .dts that exposed all 4 as SPI devices.
>
> Ignoring SPI0 (routed to "Host 3" on the mikroBUS Cape) for now, I have 
> Host 1 and Host 2 working.  These map directly to SPI1.0 and SPI1.1, but I 
> cannot get a "SPI1.2" enabled (Host4).  The mikroBUS Cape schematic shows 
> that chipselect for Host 4 is routed to P8.10, so I thought I could add 
> that pin (gpio2_4) as OUTPUT_PULLUP | MODE 7, and then simply add a third 
> fragment for the third chipselect.
>
>   spi1@2 {
> #address-cells = <1>;
> #size-cells = <0>;
> compatible = "spidev";
> reg = <2>;
> spi-max-frequency = <1600>;
> spi-cpol;
> spi-cpha;
>   };
>
> Unfortunately this fails with a "cs2 >= max2" error when I load the 
> overlay.
>
> Reading around I'm trying to figure out, okay, how do I increase the 
> number of SPI devices on the SPI1 bus.  I've read about:
>
> num-cs
> num-chipselects
> cs-gpios
>
> When using cs-gpios like this:
>
>   cs-gpios = <0>, <1>, <&gpio3 4 0>;
>
> I get 
>
> [  171.494015] /ocp/spi@481a: could not get #gpio-cells for 
> /ocp/interrupt-controller@4820
>
> My complete dts is at http://pastebin.com/BvxZ3fa2
>
> TL;DR:  How can I enable a 3rd chipselect for SPI1 where the CS is mapped 
> to P8.11 (gpio2[4])?
>

-- 
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] Using gpio2[4] as chip select 2 for SPI1

[Joe]

Howdy.

I came into possession of a mikroBUS Cape 
(http://beagleboard.org/project/mikrobus) and have been using it to learn 
how to write a .dts overlay.  Since there are 4 slots for clickboards on 
the cape and I have 4 SPI boards (4-20mA T Click), I figured I'd try to 
create a single .dts that exposed all 4 as SPI devices.

Ignoring SPI0 (routed to "Host 3" on the mikroBUS Cape) for now, I have 
Host 1 and Host 2 working.  These map directly to SPI1.0 and SPI1.1, but I 
cannot get a "SPI1.2" enabled (Host4).  The mikroBUS Cape schematic shows 
that chipselect for Host 4 is routed to P8.10, so I thought I could add 
that pin (gpio2_4) as OUTPUT_PULLUP | MODE 7, and then simply add a third 
fragment for the third chipselect.

  spi1@2 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "spidev";
reg = <2>;
spi-max-frequency = <1600>;
spi-cpol;
spi-cpha;
  };

Unfortunately this fails with a "cs2 >= max2" error when I load the overlay.

Reading around I'm trying to figure out, okay, how do I increase the number 
of SPI devices on the SPI1 bus.  I've read about:

num-cs
num-chipselects
cs-gpios

When using cs-gpios like this:

  cs-gpios = <0>, <1>, <&gpio3 4 0>;

I get 

[  171.494015] /ocp/spi@481a: could not get #gpio-cells for 
/ocp/interrupt-controller@4820

My complete dts is at http://pastebin.com/BvxZ3fa2

TL;DR:  How can I enable a 3rd chipselect for SPI1 where the CS is mapped 
to P8.11 (gpio2[4])?

-- 
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] Setting up cross compiler under OS X 10.11 / El Capitan

[Joe Ciarcia]

I've found some great resources out there that help us Mac folk out with 
building an arm toolchain on the OS X platform. Here they are if any others 
stumble across this thread looking for the same:

http://www.benmont.com/tech/crosscompiler.html
http://will-tm.com/cross-compiling-mac-os-x-mavericks/
http://hansbot.blogspot.com/p/beaglebone-black-mac-os-x-toolchain.html 
 (this one is the most detailed)


I've gotten through a few of the stumbling blocks but I'm currently stuck. 
I get this far:

[INFO ]  Performing some trivial sanity checks

[INFO ]  Build started 20151023.200552

[INFO ]  Building environment variables

[00:03] /


So, after that, if I look at the activity monitor, bash is around 100% 
processor utilization on one of the cores. I figure "great, it's doing 
something". I left it to do its thing and after an hour, I killed the 
process. I changed a few settings... ran it again... same thing. Okay... 
maybe it just takes a really long time. I left it overnight. This morning 
it was still near 100% processor utilization and nothing had changed in the 
build.log file. Here's the last few lines from the build log:


[DEBUG]  =

[DEBUG]  Checking that we can run gcc -v

[DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-v' 

[DEBUG]Configured with: 
--prefix=/Applications/Xcode.app/Contents/Developer/usr 
--with-gxx-include-dir=/usr/include/c++/4.2.1

[DEBUG]Apple LLVM version 7.0.0 (clang-700.1.76)

[DEBUG]Target: x86_64-apple-darwin15.0.0

[DEBUG]Thread model: posix

[DEBUG]  Checking that we can run gcc -v: done in 0.00s (at 00:03)

[DEBUG]  =

[DEBUG]  Checking that gcc can compile a trivial program

[DEBUG]==> Executing: 'x86_64-build_apple-darwin15.0.0-gcc' '-O2' '-g' 
'-pipe' 
'/Volumes/CaSe/.build/arm-JoesBeaglebone-linux-gnueabi/build/test.c' '-o' 
'/Volumes/CaSe/.build/arm-unknown-linux-gnueabi/build/.gccout' 

[DEBUG]  Checking that gcc can compile a trivial program: done in 0.00s (at 
00:03)

[EXTRA]  Installing user-supplied crosstool-NG configuration

[DEBUG]  ==> Executing: 'mkdir' '-p' '/Volumes/CaSe/prefix/bin' 

[DEBUG]  ==> Executing: 'install' '-m' '0755' 
'/usr/local/Cellar/crosstool-ng/1.21.0/lib/ct-ng.1.21.0/scripts/toolchain-config.in'
 
'/Volumes/CaSe/prefix/bin/arm-unknown-linux-gnueabi-ct-ng.config' 

[ERROR]  

[ERROR]  >>

[ERROR]  >>  Build failed in step '(top-level)'

[ERROR]  >>

[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@216]

[ERROR]  >>called from: main[scripts/crosstool-NG.sh@564]

[ERROR]  

[ERROR]  (elapsed: 756:57.00)


Any suggestions on how to debug this? Obviously it's attempting to do 
something given the processor utilization but... what the heck is it hung 
up on?


One thing worth noting... early in the process the build log had an error 
with regards to not being able to find the ginstall tool. Since this was at 
the beginning of the test process I figured it hadn't gotten to building 
anything yet and as such, ct-ng clean was not needed (maybe I'm wrong). As 
part of running ct-ng build it creates a directory structure (running clean 
deletes this structure and all the tools included) at 
/YourCaseSensitiveDirectory/.build/tools/bin. My solution was to just cp 
install ginstall, and that got me past that error. Not sure if that's 
contributing to anything but I thought it worth mentioning. Is there 
another way around the missing ginstall problem?


Cheers, Joe


-- 
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] Talking to BBB with OS X 10.11 (El Capitan)

[Joe Ciarcia]

On Sunday, October 18, 2015 at 10:18:02 PM UTC-4, RobertCNelson wrote:

> Yes, I know it's hard to believe the original "2014-05-14" image, is 
> that far out of date! What were we thinking not to "support" 10.11 2 
> springs ago!!! 
>
> Please read the first paragraph of the author's website on horndis for 
> 10.11 updates: 
>
> http://www.joshuawise.com/horndis 
>

Thanks Robert, as I mentioned, it was impossible to read that as the 
website wasn't up. I figured it was just one of many other dead links I've 
come across. Just bad timing, it was back the next day. I certainly don't 
expect engineers who are volunteering their time to have any obligation to 
update anything at all. It was merely a question as it appeared that 
support for that particular tool had been dropped based on the links 
provided on the getting started page (and in Googling around, the only 
other references I found for FTDI and HORNDIS were a few years old).

Now that it's back up, I can see that it looks like a few people have come 
up with some workarounds in the interim. 

I actually managed to get up and running without any of that by connecting 
to root@beaglebone.local via ssh and then grabbing the IP through ifconfig 
so I could launch the Cloud9 IDE.

Cheers, Joe

-- 
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: OSX el Capitan breaks HoRNDIS?

[Joe Ciarcia]

If you're just getting started and are new to using the BeagleBone Black 
(as I am) you've no doubt read and watched countless videos that insist you 
must get this ethernet over USB working in order to change the BBB to a 
static IP before you can move forward. I've not found this to be true. You 
can connect directly via ethernet. Just connect one end of an ethernet 
cable into your BBB, and the other directly into your Mac, or connect the 
BBB directly to your router (many of these tutorials say you need a 
crossover cable for a direct connection to your computer... it's 2015, you 
do not need a crossover cable to connect directly to your computer (well, 
unless you're using a relic). 

I suspect you may know some of the following, I'm just going to explain it 
down to the basics just in case there are others who are new to the *NIX 
command line.

The default config of the BBB is for a DHCP connection... this will work 
great (all of these tutorials seem to suggest you need a static IP, you do 
not). The Mac's default config on the Ethernet port will of course also be 
DHCP.

Open a terminal window and type:

ssh root@beaglebone.local

If it asks for a password, just hit return (there is none). You should now 
be connected to the BBB. If you want to find the IP so you can use Cloud9 
just type:

ifconfig

It will respond with something like this:

eth0  Link encap:Ethernet  HWaddr 6c:ec:eb:b0:0e:a0  

  inet addr:192.168.2.2  Bcast:192.168.2.255  Mask:255.255.255.0

  inet6 addr: fe80::6eec:ebff:feb0:ea0/64 Scope:Link

  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

  RX packets:10051 errors:0 dropped:0 overruns:0 frame:0

  TX packets:866 errors:0 dropped:0 overruns:0 carrier:0

  collisions:0 txqueuelen:1000 

  RX bytes:808671 (789.7 KiB)  TX bytes:114797 (112.1 KiB)

  Interrupt:40 


loLink encap:Local Loopback  

  inet addr:127.0.0.1  Mask:255.0.0.0

  inet6 addr: ::1/128 Scope:Host

  UP LOOPBACK RUNNING  MTU:65536  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:0 

  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


usb0  Link encap:Ethernet  HWaddr 6c:ec:eb:b0:0e:a1  

  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)


Your IP is under eth0, in this case my board has an address of 192.168.2.2


If you want to launch Cloud9, open up a browser and enter 192.168.2.2:3000 
for the URL and hit return. Cloud9 will take a few seconds to start up, and 
then you're good to go. 


If your want your BBB to be able to access the net from your Mac, open up 
your system preferences, click on sharing, and then make sure the internet 
sharing box is checked, and the appropriate ethernet port is selected. You 
can test to see if it's working by pinging Google from the terminal (either 
in Cloud9, or from the terminal window you opened for SSH)


ping www.google.com


Now... if you DO want to configure a static IP, you can do that now by 
typing:


nano /etc/network/interfaces


There are plenty of tutorials that can show you how to modify this file... 
just make sure you know exactly what you want to do as modifications to 
this file may prevent you from connecting via ethernet the next time around.


Cheers, Joe

-- 
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: Starting VNC at boot in debian

[Joe Spanier]

Still having issues. I followed some guides specific to LDXE this weekend 
but still no luck. Anyone?

On Friday, June 26, 2015 at 1:12:29 PM UTC-5, Joe Spanier wrote:
>
> Im working with the 6-17 machinekit image on elinux.org on my BBB running 
> the xenomai kernel and I am having a hell of a time getting things to 
> autostart, specifically x11vnc. 
>
> Ive been able to get this to work with raspberry pi and in ubuntu, but no 
> matter what I have tried or what tutuorial I follow I cant seem to get 
> anything to autostart on the BBB. 
>
> Is anyone using a VNC server that they can give me the script and setup 
> process they are using? The directions I followed most recently are these 
> and still no luck:
>
> There are several ways of doing this, but here is my preferred way (as 
> root):
>
> -create a password file using “x11vnc -storepasswd ” and 
> provide your password, then chmod 600  to avoid anyone 
> reading it but root,
>
> -create the following in /etc/init/x11vnc.conf (make sure you replace the 
> "<...>", from the script details below, with the correct information):
>
> start on login-session-start
> script
> x11vnc -xkb -noxrecord -noxfixes -noxdamage -repeat -display :0 -auth/var/
> run/lightdm/root/:0 -forever -shared -bg -o /var/log/x11vnc.log -rfbauth
>  -rfbport 5900 -allow 
> end script
>
> Now let’s see some of the options used above (and it has a lot of them 
> <http://www.karlrunge.com/x11vnc/x11vnc_opts.html>):
>
> -xkb will allow better clipboard interactions in my experience,
>
> -repeat is allowing keyboard repeating keys (most annoying thing when it 
> doesn’t work),
>
> -forever means even if you disconnect from your session, x11vnc will still 
> be alive,
>
> -shared means several users may be connected at the same time (use this 
> only if you plan to connect multiple users simultaneously to it),
>
> -allow enables to restrict the machines that will be able to connect to 
> vnc, remember, vnc is an open door to your machine (I removed this for my 
> linux PC).
>
> Reboot. You should be able to connect on the default port 5900 after that.
>

-- 
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] Starting VNC at boot in debian

[Joe Spanier]

Im working with the 6-17 machinekit image on elinux.org on my BBB running 
the xenomai kernel and I am having a hell of a time getting things to 
autostart, specifically x11vnc. 

Ive been able to get this to work with raspberry pi and in ubuntu, but no 
matter what I have tried or what tutuorial I follow I cant seem to get 
anything to autostart on the BBB. 

Is anyone using a VNC server that they can give me the script and setup 
process they are using? The directions I followed most recently are these 
and still no luck:

There are several ways of doing this, but here is my preferred way (as 
root):

-create a password file using “x11vnc -storepasswd ” and 
provide your password, then chmod 600  to avoid anyone 
reading it but root,

-create the following in /etc/init/x11vnc.conf (make sure you replace the 
"<...>", from the script details below, with the correct information):

start on login-session-start
script
x11vnc -xkb -noxrecord -noxfixes -noxdamage -repeat -display :0 -auth/var/
run/lightdm/root/:0 -forever -shared -bg -o /var/log/x11vnc.log -rfbauth
 -rfbport 5900 -allow 
end script

Now let’s see some of the options used above (and it has a lot of them 
):

-xkb will allow better clipboard interactions in my experience,

-repeat is allowing keyboard repeating keys (most annoying thing when it 
doesn’t work),

-forever means even if you disconnect from your session, x11vnc will still 
be alive,

-shared means several users may be connected at the same time (use this 
only if you plan to connect multiple users simultaneously to it),

-allow enables to restrict the machines that will be able to connect to 
vnc, remember, vnc is an open door to your machine (I removed this for my 
linux PC).

Reboot. You should be able to connect on the default port 5900 after that.

-- 
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] U-Boot Location

['Joe Mama' via BeagleBoard]

Thanks Robert.  

1.  You mention the internal "boot rom"  Is this the masked ROM that is part of 
the chip?  

  



  From: Robert Nelson 
 To: Beagle Board  
 Sent: Monday, June 15, 2015 7:30 AM
 Subject: Re: [beagleboard] U-Boot Location
   
On Sat, Jun 13, 2015 at 1:11 PM,  <4andy2...@gmail.com> wrote:
> Hello,
>
> Delving deeper into the Black.  Could someone please respond to my
> questions/assumptions below?
>
> 1.  I assume U-Boot is located in the eMMC and that at boot depending on
> position of boot switch, it will load the kernel either from eMMC or the SD
> card?

Actually the "boot" switch lets the internal "boot rom" know what
device to search first.  The boot rom then attempts to load u-boot
from the appropriate device.

> 2.  Where are pre-built images for U-Boot for the Black located and where is
> source code located?

They are currently dd'ed to the mbr. You can find a patch under /opt/source/

Otherwise:
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot

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+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] Issues with autostarting services in Debian

[Joe Spanier]

I am using my beaglebone black to run Octoprint for my printer. Its a new 
RevC with the MachineKit Image from elinux.org and I followed the basic 
raspbian install instructions for getting OctoPrint installed which worked 
fine. I also installed X11vnc and mjpg-streamer. All of these work fine 
with started manually over ssh. The issue cosmes when I try to get any of 
these services to autostart on boot. 

for Octoprint  followed these instructions:
Automatic start up

Copy the script files to their respective folders and make the init script 
executable:

sudo cp scripts/octoprint.init /etc/init.d/octoprint
sudo chmod +x /etc/init.d/octoprint
sudo cp scripts/octoprint.default /etc/default/octoprint

Then add the script to autostart using sudo update-rc.d octoprint defaults.

I also tried running this:

# create run-octoprint

cat > ~/run-octoprint 

[beagleboard] I'm a newbie and just tried git clone and got - Error: couldn't resolve host

[joe . hub . 7816]

I'm a newbie and just tried git clone and got - Error: couldn't resolve host

-- 
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: PID capability

[Joe]

Depends on how much jitter your control can tolerate. Beaglebone most likely 
can hit the 200Hz rate. There is the PRUSS that run independent of the main OS 
so it will have much better jitter.

-- 
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] Kernel Panic with eMMC flasher

[Joe Spanier]

So I have to thank everyone for the patience on this one. I did the mks.ext4 
and that seemed to help but did not fix it. I bought a new sd card last night 
as that was the only variable I didnt chage other then the BBB. 

Damn thing flashed first try.  Thanks again. From now on new SD cards will be 
the first thing I try in errors like this. 

-- 
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] Kernel Panic with eMMC flasher

[Joe Spanier]

Well that escalated quickly. 

I did the windows thing as an experiment. Basically nothing in Linux was 
working so I figured may as well. 

-- 
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] Kernel Panic with eMMC flasher

[Joe Spanier]

<https://lh6.googleusercontent.com/-STFf5nrtDoQ/VGv5lWo1raI/UeE/afhkJDLP07s/s1600/IMG_20141118_191451.jpg>


On Tuesday, November 18, 2014 7:24:11 PM UTC-6, Joe Spanier wrote:
>
> Latest failure. This time I flashed from windows 7 just to try something 
> new, different PC and card reader, and used a wallwart. No dice. Slightly 
> different t error message with the panic though. Progress??

-- 
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] Kernel Panic with eMMC flasher

[Joe Spanier]

Latest failure. This time I flashed from windows 7 just to try something new, 
different PC and card reader, and used a wallwart. No dice. Slightly different 
t error message with the panic though. Progress??

-- 
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] Kernel Panic with eMMC flasher

[Joe Spanier]

https://rcn-ee.net/deb/testing/2014-11-11/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-11-11-4gb.img.xz
 
is the image. Im powering through USB plugged into a wall outlet. No Capes, 
just power, and HDMI. 

I was able to successfully 
flash 
https://rcn-ee.net/deb/testing/2014-11-11/console/BBB-eMMC-flasher-debian-7.7-console-armhf-2014-11-11-2gb.img.xz
 
and pull up the console. There was some concern on the machinekit page that 
I was using an older boot loader but that should have fixed that I would 
think. 

I am for sure using a RevC with the 4g eMMC and I am pushing the boot 
button to boot from the SD.


On Tuesday, November 18, 2014 9:39:39 AM UTC-6, RobertCNelson wrote:
>
> Humm, that's 5 minutes into the flasher..
>
> What was the exact name of the image you flashed?
>
> How are you powering the board? any other capes attached?
>
>
>
> On Tue, Nov 18, 2014 at 9:37 AM, Joe Spanier  > wrote:
>
>>
>>> <https://lh3.googleusercontent.com/-t5YWs6Ft4KM/VGtnph7h5QI/UZY/ffY1GQYl5Y4/s1600/IMG_20141118_073426.jpg>
>>>
>>>
>>> <https://lh3.googleusercontent.com/-t5YWs6Ft4KM/VGtnph7h5QI/UZY/ffY1GQYl5Y4/s1600/IMG_20141118_073426.jpg>
>>>
>>>> Here is a screenshot of the panic 
>>>
>>>  -- 
>> 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.
>>
>
>
>
> -- 
> Robert Nelson
> http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel Panic with eMMC flasher

[Joe Spanier]

There is definitely a text output from the HDMI That is where Im seeing the 
kernel panic. I am trying to flash a new uSD now to try it. If it happens 
again Ill just take a picture of the screen. 

On Monday, November 17, 2014 3:55:22 PM UTC-6, RobertCNelson wrote:
>
> On Mon, Nov 17, 2014 at 3:47 PM, Joe Spanier  > wrote: 
> > I dont have a serial cable. Probably need to pick one up. 
>
> Okay, I'm a little confused.. How then do you know your getting a 
> kernel panic?  While flashing all debug info gets directed over the 
> serial. I still haven't mirrored any of the progress back to hdmi 
> output.. 
>
> > I am properly ejecting the card from my laptop after completing dd. Is 
> that 
> > what you mean by sync? 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel Panic with eMMC flasher

[Joe Spanier]

I dont have a serial cable. Probably need to pick one up. 

I am properly ejecting the card from my laptop after completing dd. Is that 
what you mean by sync?

On Monday, November 17, 2014 1:23:43 PM UTC-6, Jason Lange wrote:
>
> This might not be part of the problem, but I have created much mysterious 
> misery by forgetting to "sync" after "dd"-ing my sd card.  If you forgot to 
> do this and yanked your card out after dd finished you cannot trust that 
> you have an accurate and functional image.  spread the word.
>
>
> On Mon, Nov 17, 2014 at 7:40 AM, Robert Nelson  > wrote:
>
>> On Sun, Nov 16, 2014 at 10:41 PM, Joe Spanier > > wrote:
>> > I am trying to flash my eMMC with the image here:
>> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases I 
>> am
>> > using the 4Gb flasher for the RevC. I can flash the microSD but all of 
>> the
>> > images ive tried cause Kernel Panics when I try to flash the BBB. Im 
>> sure
>> > this is something I am doing but Im not sure.
>> >
>> > Here are the steps Im using:
>> > 1. Wget the image
>> > 2. md5sum check
>> > 3. xzcat BBB-eMMC-Flasher... ...img.xz | sudo dd bs=4096 of=/dev/sdc
>> > 4. load SD and apply power
>> > 5. kernel panic
>>
>> Well 3.8 always panic's (drm) when shutdown at the completion of the
>> flashing procedure.
>>
>> If you have the serial log from the flashing procedure this would confirm 
>> that.
>>
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.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] Kernel Panic with eMMC flasher

[Joe Spanier]

I am trying to flash my eMMC with the image here: 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases I am 
using the 4Gb flasher for the RevC. I can flash the microSD but all of the 
images ive tried cause Kernel Panics when I try to flash the BBB. Im sure 
this is something I am doing but Im not sure.

Here are the steps Im using:
1. Wget the image
2. md5sum check
3. xzcat BBB-eMMC-Flasher... ...img.xz | sudo dd bs=4096 of=/dev/sdc
4. load SD and apply power
5. kernel panic


So what am I missing 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.

[beagleboard] Bittorrent Sync

[Joe Carlin]

Im running Ubuntu 14.04 with LXDE on my BBB.  Ive had great success using 
bittorrent sync and sharing files across multiple platforms.  I see they 
have a version built for arm.  Has anyone had any luck getting it to work?  

-- 
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] GNURADIO build problems

[Joe Carlin]

I'm trying to build gnuradio on the beaglebone black with angstrom. 
 However when I run make I get this error:

libvolk.so.0.0.0: undefined reference to 
`volk_32fc_x2_multiply_32fc_neonasm'
libvolk.so.0.0.0: undefined reference to 
`volk_16i_max_star_horizontal_16i_neonasm'
libvolk.so.0.0.0: undefined reference to 
`volk_32fc_32f_dot_prod_32fc_a_neonasm'
libvolk.so.0.0.0: undefined reference to 
`volk_32f_x2_dot_prod_32f_neonasm_opts'
libvolk.so.0.0.0: undefined reference to 
`volk_32fc_32f_dot_prod_32fc_a_neonpipeline'
libvolk.so.0.0.0: undefined reference to `volk_32f_x2_dot_prod_32f_neonasm'
collect2: error: ld returned 1 exit status
make[2]: *** [volk/lib/test_all] Error 1
make[1]: *** [volk/lib/CMakeFiles/test_all.dir/all] Error 2
make: *** [all] Error 2


Anyone have any ideas how to get this built on the BBB, or anyone been able 
to get gnuradio built.

Thanks

Joe

-- 
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: Beaglebone keeps shutting down when trying to drive a motor

[Uncle Joe]

Well, I've overcome the problem. I was using a GPIO as GND to the ESC. This 
was convenient since those pins are next to each other. Once I used true 
GND, then the problem went away.

But why would using a GPIO as a GND cause a shutdown? I know it will 
restrict the amount of current sinked due to having to flow through an 
extra FET.


On Saturday, May 10, 2014 9:38:55 PM UTC-7, Uncle Joe wrote:
>
> Help, I'm struggling to drive a simple ESC and brushless motor combination 
> with the Beaglebone. I've already spent 1/2 a day figuring out the right 
> arming sequence (caused by a +- 0.01 ms error in timing).
>
> But once I arm the ESC, the Beaglebone shuts off immediately. Most of the 
> time, it shuts off right when it starts spinning up. Sometimes it even 
> shuts off on one of the beeps the motor makes indicating the ESC is arming.
>
> Here's my setup:
> Revolver Stubby motor
> ||
> ||
> 850W PSU  =12V=  ESC   ===3.3V=== BeagleBone
>
> The PSU is an Antec 850 high current gamer. I've disabled over-current, 
> over-voltage, and under-voltage protection on it, so the power draw can be 
> alot (enough to make the lights flicker when the motor starts).
>
>
> The BeagleBone is powered by USB and should be buffered against surges 
> caused by the motor PSU.
> What could be 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 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] Beaglebone keeps shutting down when trying to drive a motor

[Uncle Joe]

Help, I'm struggling to drive a simple ESC and brushless motor combination 
with the Beaglebone. I've already spent 1/2 a day figuring out the right 
arming sequence (caused by a +- 0.01 ms error in timing).

But once I arm the ESC, the Beaglebone shuts off immediately. Most of the 
time, it shuts off right when it starts spinning up. Sometimes it even 
shuts off on one of the beeps the motor makes indicating the ESC is arming.

Here's my setup:
Revolver Stubby motor
||
||
850W PSU  =12V=  ESC   ===3.3V=== BeagleBone

The PSU is an Antec 850 high current gamer. I've disabled over-current, 
over-voltage, and under-voltage protection on it, so the power draw can be 
alot (enough to make the lights flicker when the motor starts).


The BeagleBone is powered by USB and should be buffered against surges 
caused by the motor PSU.
What could be 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 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] Getting the Beaglebone Black to register as an Android Device on PC

[Joe Vee]

I have my BBB loading and running Android just fine.  Anyone have any luck 
getting it to register like a a regular Android device when connected to a 
PC so that apps can run and download from development environments?

-- 
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] How are the production BBB images built?

[Joe Gorse]

Two things. First, I have had success with my bitbaked images. After I 
grabbed my console serial cable from work it seemed my boot was failing to 
find /dtbs/am355x...dtb for the bbb, so I created the folder on the boot 
partition and added the dtb file and it has since worked.

Second, while netboot is cool, it's not quite as cool as fastboot. Here is 
a fan review and tutorial for Android 
BBB<http://wiresareobsolete.com/wordpress/2013/11/fastboot-on-the-beaglebone-black/>
, AM335x eMMC 
booting<http://processors.wiki.ti.com/index.php/AM335x_Android_eMMC_booting#What_is_fastboot.3F>doc
 by TI, and the succinct fastboot 
protocol 
here<https://gitorious.org/rowboat/bootable-bootloader-legacy/source/076ef94d61f349f7cf0fe776e60456d8f232cca5:fastboot_protocol.txt>
.

As it happens, I have just connected to u-boot from linux host using 
fastboot. Next steps are to see if I can boot or flash an Angstrom image 
over USB.

Cheers,
Joe Gorse

On Friday, February 28, 2014 7:51:11 PM UTC-5, john3909 wrote:
>
>
> From: Brandon I >
> Reply-To: >
> Date: Friday, February 28, 2014 at 4:34 PM
> To: >
> Cc: >
> Subject: Re: [beagleboard] How are the production BBB images built?
>
> > Maybe we can become free from SD cards in the near future for BBB 
> development.
>
> Doesn't uboot support network boot already?
>
> Hi Brandon,
>
> I use u-boot on my BBB to tftp zImage from my desktop and then mount 
> rootfs via NFS on my desktop. Is that what you want?
>
> Regards,
> John
>
>
>
> On Thursday, February 27, 2014 11:29:23 PM UTC-8, jhg...@gmail.com wrote:
>>
>> Robert,
>>
>> Have you resolved any of these mysteries in the mean time?
>>
>> I got into this by trying to "bitbake" a simpler image, such as 
>> console-image, since I need no graphics or fancy webserver with node.js 
>> foo. So far I have failed to boot from the SD card with anything which has 
>> been made by the oebb.sh script or bitbake build system. Even Derek's 
>> 2-year-old 
>> instructions<http://derekmolloy.ie/building-angstrom-for-beaglebone-from-source/>seem
>>  not to work for "console-image".
>>
>> After I succeed at booting the BBB with my own custom image, I plan on 
>> updating u-boot to allow "fastboot", an feature more commonly supported by 
>> Android which allows one to boot or flash over USB, ethernet, etc. Maybe we 
>> can become free from SD cards in the near future for BBB development.
>>
>> Cheers,
>> Joe
>>
>> On Friday, July 12, 2013 8:30:29 AM UTC-4, Robert P. J. Day wrote:
>>>
>>> On Fri, 12 Jul 2013, Chris Morgan wrote: 
>>>
>>> > On Friday, July 12, 2013, Koen Kooi wrote: 
>>> > 
>>> >   Op 12 jul. 2013, om 13:46 heeft Robert P. J. Day <
>>> rpj...@crashcourse.ca> het 
>>> >   volgende geschreven: 
>>> > 
>>> >   > On Fri, 12 Jul 2013, Koen Kooi wrote: 
>>> >   > 
>>> >   >> It's all in the SRM, but for people too lazy to read that: 
>>> >   >> 
>>> >   >> ï¿1Ž2 ï¿1Ž2 ï¿1Ž2Read 
>>> http://www.angstrom-distribution.org/building-angstrom and follow the 
>>> >   steps outlined there. 
>>> >   > 
>>> >   > ï¿1Ž2gaah ... i am not interested in the general 
>>> philosophy of how to 
>>> >   > build angstrom, that's *not* the question on the table. the 
>>> question 
>>> >   > is, which *particular* configuration of angstrom is the one 
>>> that 
>>> >   > matches what is currently shipping on the BBB? 
>>> > 
>>> >   The one I linked above. There is only one configuration of 
>>> angstrom per release and 
>>> >   the above matches the release that ships with the bones. 
>>> > 
>>> > 
>>> > Hello. 
>>> > 
>>> > I followed those instructions and, although I had selected the yocto 
>>> > 2013 release, I ended up with the component files in the deploy/ 
>>> > directory but as rootfs and ubi files, not card images. 
>>> > 
>>> > The information yesterday about the emmc-prepare.sh and other 
>>> > scripts has helped informationaly, I think I'll be able to build a 
>>> > sd card image today using those steps, but at this point it seems 
>>> > like a multi step process after following the angstrom build steps. 
>>>
>>>   actually, that's what i would have expected 

[beagleboard] Beagleboard xM - Angstrom cannot 'opkg update' ::: config files for OPKG are wrong

[joe]

Hello All

After a long 'fight' I was able to figure out that the config files for the 
Angstrom package manager are looking into a wrong URL.

The wrong Angstrom images are the Cloud9 ones (and the 'demo' as well as):

Angstrom-Cloud9-IDE-eglibc-ipk-v2011.11-core-beagleboard-2011.11.21.img.gz
Angstrom-Cloud9-IDE-eglibc-ipk-v2011.11-core-beagleboard.rootfs.tar.bz2 

The conf files in '/etc/opkg' are set to: - src/gz base 
http://feeds.angstrom-distribution.org/feeds/*core*/ipk/eglibc/armv7a/base 
- but there is no 'armv7a' under '/core/ipk/eglibc', so it comes with a 404 
error

I have downloaded and compared the conf files in all images and my guess is 
that instead of 'core' it should be 'v2012.05' - I've change all my conf 
files and voila. (conf files in '/etc/opkg').

It would be good if someone from the support team could confirm that that 
is the correct repository for Cloud9-xM, but after comparing all 
possibilities I guessed that to be the one.

So to fix, and start using your Beagleboard-xM using the Cloud9 image you 
need to go to '/etc/opkg' and all the files (except arch.conf) and replace 
'core' with 'v2012.05' - and then 'opkg update' will work, hopefully, and 
you'll be able to upgrade the packages, etc, etc

PS I tried to find a way to feedback the Angstrom team but I was 
unsuccessful, id=f someone knows how to contact them please tell me and 
I'll do it.

Best,

Joe Rosa


-- 
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/groups/opt_out.

[beagleboard] Re: why does reading the DMTIMER clock take so long?

[Uncle Joe]

Wow, I completely forgot about this thread until someone just emailed me 
with a question. Thanks for your interest.

The file I opened is "/dev/mem"

int fd = open("/dev/mem", O_RDWR | O_SYNC); //O_SYNC makes the memory 
uncacheable

The file is a view of the entire 4GB physical memory space. You need to be 
root to open it obviously.

I also have a conjecture about why reading the clock is slow. The DM timer 
isn't part of the ARM architecture, so it has to read it externally. Today 
as processors integrate more and more devices onto the same chip, packet 
switched networks are used more and more instead of dedicated wires since a 
packet interface is general purpose and will have higher utilization.  But 
packet switching will increase latency.

I'd like to know why ARM didn't include a clock as part of the 
architectural state. Sure it can save some power, but it practically all 
embedded devices need a clock and reading an external one will use more 
power. At least one other computer architect agrees:

https://www.youtube.com/watch?v=J9kobkqAicU

At 22:30, Burton laments about the lack of a user readable clock on today's 
processors.

Yale

On Friday, May 24, 2013 12:19:58 AM UTC-7, fis@gmail.com wrote:
>
> Hi, I curentlly have some problem with reading DMTIMER. May I ask how 
> exactly you read the value of this counter? by which file is your 
>
> file descriptor *fd *referred (I mean when you use *mmap()*)?
>
>
> On Saturday, January 28, 2012 6:18:59 AM UTC+1, Uncle Joe wrote:
>>
>> I got a Beaglebone for robotics, where low latency operation is 
>> important (especially, if I want to control 40 pins). I found the 
>> sysfs interface to control GPIO is too slow (~2200 ns), so I resorted 
>> to directly modifying the GPIO registers, which got the time down to 
>> ~200 ns. Then I wanted to read the clock via 
>> clock_gettime(CLOCK_REALTIME), but that's also very slow (1500 ns). 
>> Again I resorted to directly reading the DMTIMER2 counter and got the 
>> time down to about 100ns.  I still think this is a bit high. Can 
>> someone enlighten me why it would take this long to read an on chip 
>> value? 
>>
>>
>>
>> volatile uint32_t *dmtimer2_regs = (uint32_t *)mmap(NULL, 0x1000, 
>> PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0x4804); 
>>
>> while (true) 
>> { 
>>   uint32_t t0 = dmtimer2_regs[0x3c / 4]; 
>>   uint32_t t1 = dmtimer2_regs[0x3c / 4]; 
>>   cout << t1 - t0 << endl;  // typically 5 
>> clock ticks (each clock tick is ~41ns), hence each time stamp read 
>> takes ~100ns 
>> } 
>>
>

-- 
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/groups/opt_out.

[beagleboard] Re: Using LI-VI365 (tvp5146x chip) with Beagleboard xmC

[Joe Pulver]

Sorry to report, I moved on to something new.  I never got the LI-VI365 
working with the Beagleboard-XM.  I did write some capture software using 
the board with a Leopard DM365, but that might not be powerful enough for 
your needs.  

Joe

On Monday, November 25, 2013 3:59:23 PM UTC-5, jeffre...@gmail.com wrote:
>
> Hi Joe,
> I am looking to setup this same configuration.  I noticed that 4 of the 
> wires from the LI-VI365 are either grounded or powered on the beagleboard. 
>  I planned on lifting and terminating these with 1M resistors to open them 
> up.  I haven't looked througouly through the DVP5146 datasheet yet, but I'm 
> assuming that the MSBs can just be hooked up.  The rest of the pins look 
> right.  I would like to see where you have gotten on this, and if perhaps 
> we could share resources to get this working (if you are still working on 
> it.)
> Thanks,
> Jeff
>
>
>
>
> On Thursday, June 9, 2011 12:03:20 PM UTC-4, Joe Pulver wrote:
>>
>> I am trying to use the LI-VI365 board with my beagleboard xmC.  After 
>> several failed attempts, I  have come here hoping for a push in the 
>> right direction. 
>>
>> Attempt 1:  Prebuilt images. 
>>
>> I tried several prebuilt images (angstrom, ubuntu maverick, ubuntu 
>> natty), but none had the TVP514x module built by default. 
>>
>>
>> Attempt 2: Build My Own Kernel 
>>
>> In Angstrom( 
>> http://www.angstrom-distribution.org/building-angstrom<http://www.google.com/url?q=http%3A%2F%2Fwww.angstrom-distribution.org%2Fbuilding-angstrom&sa=D&sntz=1&usg=AFQjCNHXILdToy9tzUiMciaNOzmaYJN8CQ>):
>>  
>>
>> I ran bitbake virtual/kernel -c menuconfig.  Built TVP514x into 
>> kernel.  I believe the v4l2 support is built into the kernel as well. 
>> On boot I see  "Linux video capture interface: v2.00", but no output 
>> from the tvp514x driver.  No /dev/video 
>>
>> Ubuntu build (http://www.elinux.org/BeagleBoard_Ubuntu_ 
>> %26_DSP_From_Sources<http://www.google.com/url?q=http%3A%2F%2Fwww.elinux.org%2FBeagleBoard_Ubuntu_%2526_DSP_From_Sources&sa=D&sntz=1&usg=AFQjCNHYyV1GQz5JGa2_yqKDBkQfo0ZozQ>):
>>  
>>  i built the tvp514x as a module.  V42L is 
>> built as a module by default.  The modprobe command loaded the 
>> v4l2_common and videodev modules.  dmesg reported ("Linux video 
>> capture interface: v2.00".  No /dev/video.  No output from the tvp514x 
>> driver. 
>>
>>
>> Attempt 3: Modifying the kernel source. 
>>
>> Compared to the Ubuntu kernel source, the Angstrom kernel source 
>> appears to have more camera support in the board-omap3beagle.c file. 
>> Angstrom also has a file board-omap3beagle-camera.c that does not 
>> exist in the ubuntu kernel source.  So I started from the angstrom 
>> kernel source (in the work directory), and tried to add support for 
>> the tvp514x driver. 
>>
>> In board-omap3beagle.c, I added some include statements (~ Line 80) 
>>
>> #if defined(CONFIG_VIDEO_TVP514X) || 
>> defined(CONFIG_VIDEO_TVP514X_MODULE) 
>> #include  
>> #include  
>> extern struct tvp514x_platform_data tvp514x_pdata; 
>> #endif 
>>
>> I added a struct (~Line 765): 
>>
>> static struct i2c_board_info __initdata 
>> beagle_tvp514x_i2c2_boardinfo[] = { 
>> #if defined(CONFIG_VIDEO_TVP514X) || 
>> defined(CONFIG_VIDEO_TVP514X_MODULE) 
>> { 
>> I2C_BOARD_INFO("tvp5146", 0x5d), 
>> .platform_data= &tvp514x_pdata, 
>> }, 
>> #endif 
>> }; 
>>
>> And I added an else if clause  to static int __init 
>> omap3_beagle_i2c_init(void) method  : 
>>
>> } else if (!strcmp(cameraboard_name, "tvp514x")) { 
>> printk(KERN_INFO "Beagle cameraboard:" 
>> " registering i2c2 bus for tvp514x\n"); 
>> omap_register_i2c_bus(2, 400,  beagle_tvp514x_i2c2_boardinfo, 
>> ARRAY_SIZE(beagle_tvp514x_i2c2_boardinfo)); 
>> } else { 
>>
>>
>> Then the kernel build failed to link, so I  added this to board- 
>> omap3beagle-camera.c (~ Line 208): 
>>
>> #if defined(CONFIG_VIDEO_TVP514X) || 
>> defined(CONFIG_VIDEO_TVP514X_MODULE) 
>> #include  
>> struct tvp514x_platform_data tvp514x_pdata; 
>> #endif 
>>
>> At this point I could build and run the kernel.  It was last week, so 
>> I hope I didn't forget something. Now, when I boot, in dmesg I see the 
>> "Beagle cameraboard:registering i2c2 b