Re: [beagleboard] setting up build machine

[Marius]

I use this for all my work:

http://www.jumpnowtek.com/beaglebone/BeagleBone-Systems-with-Yocto.html

Scott is also very helpful if you have problems. All his tutorials 
worked first go for me.




-- Original Message --
From: k.nak...@gmail.com
To: "BeagleBoard" 
Sent: 2016-02-02 16:22:48
Subject: [beagleboard] setting up build machine


hi team


i have a beagle bone black

I need to setup a build machine so that i can write some kernel code 
compile and flash it back to board

can any one help me with the system requirements and also steps to
1) download android and debian packages on remote system.
2) steps to compile.
3) steps to flash on eMMC drive

Regards


--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google 
Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to beagleboard+unsubscr...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SPI Overlay not changing states BBB 4.1.15-ti-r43 Debian Image 2015-11-12

[Bit Pusher]

I've been using spi2  quite extensively in python:
from spidev import SpiDev as SPI
and it works fine for me.
> ls /dev/spi*
/dev/spidev1.0  /dev/spidev1.1
> 
> sudo cat $SLOTS
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-BONE-PRU
 5: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-ADC
 6: P-O-L-   2 Override Board Name,00A0,Override Manuf,ADAFRUIT-SPI1
> uname -a
Linux BBB4 4.1.15-bone17 #1 Wed Dec 16 17:39:16 UTC 2015 armv7l GNU/Linux
> 
> lsb_release -d
Description: Debian GNU/Linux 8.3 (jessie)
> 
I could post my tbo file if you think it would help, but I don't think I 
changed it much besides playing with the clock rate
and making sure d1 and d0 change on negative edges of the clock (i.e. 
commenting out spi-cpha;)
Have you checked your pins carefully; for example, the clock should be an 
input not an output; I've never figured this one out.

I load the overlays using a service that simply calls a shell script in my 
bin directory:
#!/bin/sh
cd /lib/firmware
echo BB-BONE-PRU > /sys/devices/platform/bone_capemgr/slots
echo BB-ADC > /sys/devices/platform/bone_capemgr/slots
echo ADAFRUIT-SPI1 > /sys/devices/platform/bone_capemgr/slots
> 
I could also post the service, but it is very straightforward and simple.

My pins are defined as:
pinctrl_spi1_pins {
pinctrl-single,pins = <0x190 0x33 0x194 0x33 0x198 0x13 
0x19c 0x13>;
linux,phandle = <0x1>;
phandle = <0x1>;
};
When I do >sudo cat $PINS, their values are verified:
pin 100 (44e10990.0) 0033 pinctrl-single 
pin 101 (44e10994.0) 0033 pinctrl-single 
pin 102 (44e10998.0) 0013 pinctrl-single 
pin 103 (44e1099c.0) 0013 pinctrl-single 

I hope this helps a bit.

>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB HDMI initialization (bare metal)

[Viktor From RU]

 
I was able to beat her! :-)

-- 
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 3D Printers: How to connect a BBB to a Melzi printer controller board

[canis]

Hello Forum,

This is a follow up to a question regarding copying the contents of one BBB 
to another.

I have a BBB that I am trying to connect to the Melzi board in order to 
operate a 3D printer.
Repetier server has been downloaded onto the Melzi, but the BBB is not able 
to communicate with the Melzi.  

Seeking help with this connection- any suggestions would be greatly 
appreciated.

Many thanks,
canis

-- 
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: IVerilog: just for info

[Bit Pusher]

Followup, a suite of tests can also be downloaded from
git clone git://github.com/steveicarus/ivtest.git
Running the tests on the BBB resulted in:

Test results:
  Total=2177, Passed=2165, Failed=12, Not Implemented=0, Expected Fail=0
> 
Not bad. Kind of what I was thinking of is to use the GPIO's as inputs and 
outputs and iverilog as sort of a hardware machine. I wouldn't expect it to 
be very fast, but the ability to adapt based on a particular application 
and maybe the applications inputs and outputs might be interesting.

On Sunday, January 31, 2016 at 8:49:36 PM UTC-5, Bit Pusher wrote:
>
> I've been meaning to check out iverilog written by Stephen Williams for 
> quite some time. I finally got around to it and thought why not
> install to the BBB in anticipation of the X15 that should be available 
> soon. I did a git install from
> git clone git://github.com/steveicarus/ivtest.git
> The only dependency missing was gperf; after installing this the 
> compilation proceeded seamlessly (but took awhile). I haven't had a chance 
> to
> exercise it yet, but the idea of a whole bunch of BBB's each running 
> verilog and talking to each other strikes me as a bit of fun. Even more
> fun might be if we could get it to run on C66x's in the imminent X15s (and 
> I pretend to hate acronyms?). Anyone else find this potentially
> interesting?
>
> For info:
> > ver
> No LSB modules are available.
> Distributor ID: Debian
> Description: Debian GNU/Linux 8.2 (jessie)
> Release: 8.2
> Codename: jessie
> > uname -a
> Linux BBB6 4.1.15-bone17 #1 Wed Dec 16 17:39:16 UTC 2015 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Failure to recognize SD card inserted at runtime

[Hilmar Lapp]

Thanks, good ideas. I checked the UUIDs as you suggested and they are 
different. I then went ahead and hot-plugged another card I had with only a 
single partition. Lo and behold, this time it worked (mostly, see below).

I now also noticed on the board running Debian that the card with the two ext4 
partitions on it lacked a label for the second partition (it got auto-mounted 
under /media but using its UUID, not label). So I used e2label to give that 
partition a label, too. Then hot-plugged it into the board running the 
4.1.15-ti-r40 kernel under Ubuntu, which before would give the error with this 
card, and lo and behold it now worked (mostly, see below).

I wish I had re-tested the card just before doing this so it was clearer that 
all partitions having labels was really the only change. It’s a bit hard to 
believe that this would make the difference between the kernel succeeding or 
failing to initialize the card device. But other than a week of time having 
passed, I don’t know what else could have possibly changed. I also don’t have 
time right now to go back and recreate a card with 2 partitions one of which 
unlabeled (or is there a way to erase a label from a partition? tune2fs and 
e2label only talk about setting the label.).

By “worked mostly” I mean that the kernel properly recognizes the card and 
creates the block devices for both the card and the partitions on the card. 
Also, the symlinks under /dev/disk/by-id/ and /dev/disk/by-label are created 
(by udev rules, I believe?). What doesn’t happen on the Ubuntu/4.1.15-ti-r40 
board but does on the Debian/3.8.13-bone79 board is that the partitions get 
auto mounted under /media/. But I can now see and figure out 
what’s missing on the Ubuntu-running board, and at least right now for me that 
part isn’t so important.

  -hilmar

> On Feb 2, 2016, at 6:11 PM, Wally Bkg  wrote:
> 
> If you don't have another SD card to try and can lose these contents, its 
> worth trying a reformat to a single partition, although Ubuntu generally 
> seems very good at handling multi-partition SD cards.
> 
> I have hot plugged an SD card into Debian 7.9 (image 2015-11-12) same as you 
> have done, (the card I used to flash with) and it worked, although it didn't 
> automount.   I see in your first post you said your card worked on a Debian 
> 3.8 kernel, so  I'd suspect it may be a kernel version issue or something 
> wrong with the udev rules for your Ubuntu (sorry, I'm no help with these).
> 
> Just as I about to hit "POST" it occurred to me the flasher may have cloned 
> the image to the eMMC so the card may have the same UUID as the eMMC which 
> might mess up the udev rules.  Try blkid on your BBB to get the UUID of the 
> eMMC and do it with the SD card in another system to see if they are the same.
> 
> 
> On Monday, February 1, 2016 at 9:59:53 AM UTC-6, Hilmar Lapp wrote:
> Any chance someone has an idea what might be going wrong here? I’d be happy 
> to reformat the card or take other destructive measures, but right now the 
> device for the card is not even showing up under /dev when the card is 
> inserted.
> 
> Is it that the 4.1.15-ti-r40 kernel doesn’t support hot-plugging of uSD 
> cards? If so, anything I can do to change that? And I’m not sure how to boot 
> into the eMMC when the card is inserted in at boot. (The system will boot 
> into the SD card if inserted.)
> 
>   -hilmar
> 
>> On Jan 25, 2016, at 11:28 AM, Hilmar Lapp > 
>> wrote:
>> 
>> I am running the Ubuntu 14.04.3 image from Dec 11, 2015, on a Beaglebone 
>> Black, with updated packages and updated kernel. System details below. When 
>> I insert an SD card with 2 Linux partitions (and formatted ext4 filesystems) 
>> on it after boot, it fails to be recognized.  The following message appears 
>> in syslog:
>> 
>> Jan 25 11:01:52 hostname kernel: [47672.809891] mmc0: card never left busy 
>> state
>> Jan 25 11:01:52 hostname kernel: [47672.814264] mmc0: error -110 whilst 
>> initialising SD card
>> 
>> The odd thing is that first this is the same card onto which I wrote and 
>> then booted the downloaded image. I later flashed the card to the eMMC. So I 
>> can boot from the card successfully (which presumably means the kernel 
>> supports it), but when booting into the same kernel and rootfs from the 
>> eMMC, it's reported as failing to initialize. Also, I *can* insert the card 
>> perfectly fine into a BBB running Debian Wheezy with kernel 3.8.13-bone79 
>> booted from the eMMC - the kernel recognizes it, udisks-daemon fires, 
>> partitions get mounted etc, all without any errors. So I'm rather confident 
>> that the card is fine.
>> 
>> Anyone got any ideas what I might be missing?
>> 
>>   -hilmar
>> 
>> System details: starting image 
>> bone-ubuntu-14.04.3-console-armhf-2015-12-11-2gb.img
>> 
>> ubuntu@hostname:~$ lsb_release -a
>> No LSB modules are available.
>> Distributor ID:  Ubuntu
>> Description: Ubuntu 14.04.3 LTS
>> Release: 14.04
>> Codename:trusty
>> u

Re: [beagleboard] debian testing: 2016-01-31 (Node-RED)

[William Hermans]

Wally, what was the original purpose of this post ? E.G. what was it your
buddy wanted to accomplish ? If it's just twiddle a couple of GPIO's and
read an ADC or two. That can be done fairly easily in Nodejs, without even
any plugins. So not need for Node-RED, or C/C++ if not wanted.

On Tue, Feb 2, 2016 at 4:26 PM, Wally Bkg  wrote:

> Thanks, I will definitely look into this if I find nodejs or node-red
> useful to my projects, but I'm setting up a system to get a non-programmer
> started with an automation project using a BBG as an alternative to wiring
> up a bunch of relays and timers.  I'm going to give it to him tomorrow and
> show him some simple demos I've set up.  He's ~80 miles away, being
> "off-grid" with only limited Internet access via cell phone tethering so
> there are some serious obstacles for a programming newbie.
>
>
>
> On Tuesday, February 2, 2016 at 3:56:41 PM UTC-6, john3909 wrote:
>>
>> Why don’t you use C/C++ addons for Nodejs?
>>
>> https://nodejs.org/dist/latest-v5.x/docs/api/addons.html
>>
>> With Nodejs C/C++ addons, you can interface to any I/O on the BBB.
>>
>> Regards,
>> John
>>
>>
>>
>>
>> On Feb 2, 2016, at 1:39 PM, Wally Bkg  wrote:
>>
>> I think its pretty sweet to have node-red running "out of the box" but
>> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript
>> PWM is still broken) its nowhere near as neat as it could be!
>>
>> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript
>> working beyond installing the Beaglebone nodes with npm?
>>
>>
>> I'm having issues with this image getting the "gadget" to connect -- it
>> seems to only work from a cold start -- when I first plug it in the FAT
>> partition mount but the gadget hangs "waiting for IP address"  If I press
>> reset it may or may not start after the reboot.  So far its always started
>> if I hold the powerbutton down until it shuts off, and then press it again
>> to do a cold boot.
>>
>> Some of it may be that I'm using Ubuntu-Mate 15.10,  I try it later on my
>> main Ubuntu 10.04 which has been mostly reliable mounting the gadget
>> Ethernet.
>>
>>
>> On Tuesday, February 2, 2016 at 10:41:29 AM UTC-6, RobertCNelson wrote:
>>>
>>> On Mon, Feb 1, 2016 at 9:49 AM, Robert Nelson 
>>> wrote:
>>> > Howdy!
>>> >
>>> > So there's a little something new in this week's snapshot (lxqt not
>>> console):
>>> >
>>> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31
>>> >
>>> > http://beaglebone.local:1880/
>>> >
>>> > nodered.org v0.13.1
>>>
>>> On earlier jessie/stretch rootfs, then can now be installed via:
>>>
>>> sudo apt-get update
>>> sudo apt-get install bb-node-red-installer
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: debian testing: 2016-01-31 (Node-RED)

[William Hermans]

I will say, that all the talking you've done about Bonescript not working
right for you. That time instead invested into learning about the various
aspects of GPIO, Nodejs, etc in Linux, and you might be done by now. Me . .
. I dove in pretty much knowing nothing about those given subjects, and had
something working in a week piddling around with it.

On Tue, Feb 2, 2016 at 4:23 PM, William Hermans  wrote:

> *think its pretty sweet to have node-red running "out of the box" but
>> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript
>> PWM is still broken) its nowhere near as neat as it could be!*
>>
>
> So, why don't you learn how to do this without using Bonescript ? It's not
> that hard, but is not exactly something that is easily relate-able via
> email either. But I'll try . . .
>
> What I did was . . .
>
>
>- start from a fresh bare image, but for simplicity a console image
>would work fine too.
>- downloaded, and installed development prerequisites. Including git.
>- downloaded Nodejs code via git, compiled, and installed once
>finished compiling.
>- Learned a bit of how to access files from Nodejs . . . and all set .
>. .done.
>
>
>
> On Tue, Feb 2, 2016 at 3:16 PM, Robert Nelson 
> wrote:
>
>> On Tue, Feb 2, 2016 at 3:57 PM, Robert Nelson 
>> wrote:
>> > On Tue, Feb 2, 2016 at 3:39 PM, Wally Bkg 
>> wrote:
>> >> I think its pretty sweet to have node-red running "out of the box" but
>> >> without the BoneScript access to the GPIO and A/D pins (I assume
>> BoneScript
>> >> PWM is still broken) its nowhere near as neat as it could be!
>> >
>> > GPIO & A/D can be accessed via config-pin
>> >
>> > root@beaglebone:~# config-pin -l P9.18
>> > default gpio gpio_pu gpio_pd spi i2c pwm
>> >
>> >
>> >>
>> >> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript
>> >> working beyond installing the Beaglebone nodes with npm?
>> >
>> > sudo apt-get install linux-image-3.8.13-bone79
>> > sudo reboot
>> >
>> > Bonescript is installed..
>> >
>> >> I'm having issues with this image getting the "gadget" to connect -- it
>> >> seems to only work from a cold start -- when I first plug it in the FAT
>> >> partition mount but the gadget hangs "waiting for IP address"  If I
>> press
>> >> reset it may or may not start after the reboot.  So far its always
>> started
>> >> if I hold the powerbutton down until it shuts off, and then press it
>> again
>> >> to do a cold boot.
>> >
>> > Okay, that's different..  Starts flashing the clean image to do reset
>> > button testing. ;)
>> >
>> > journalctl -f | grep kernel
>> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: Attached scsi generic sg1
>> type 0
>> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] 81920 512-byte
>> > logical blocks: (41.9 MB/40.0 MiB)
>> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write Protect is off
>> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Mode Sense: 0f 00 00 00
>> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write cache: enabled,
>> > read cache: enabled, doesn't support DPO or FUA
>> > Feb 02 15:52:54 hades kernel:  sdb: sdb1
>> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Attached SCSI
>> removable disk
>> > push reboot...
>> > Feb 02 15:53:53 hades kernel: usb 5-1.4: USB disconnect, device number 8
>> > Feb 02 15:53:53 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
>> > unregister 'rndis_host' usb-:00:10.1-1.4, RNDIS device
>> > Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronizing SCSI
>> cache
>> > Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronize Cache(10)
>> > failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
>> > Feb 02 15:54:18 hades kernel: usb 5-1.4: new high-speed USB device
>> > number 9 using xhci_hcd
>> > Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device found,
>> > idVendor=1d6b, idProduct=0104
>> > Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device strings:
>> > Mfr=3, Product=4, SerialNumber=5
>> > Feb 02 15:54:18 hades kernel: usb 5-1.4: Product: BeagleBoneBlack
>> > Feb 02 15:54:18 hades kernel: usb 5-1.4: Manufacturer: Circuitco
>> > Feb 02 15:54:18 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103
>> > Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 eth0: register
>> > 'rndis_host' at usb-:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92
>> > Feb 02 15:54:18 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device
>> > Feb 02 15:54:18 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage
>> > device detected
>> > Feb 02 15:54:18 hades kernel: scsi host16: usb-storage 5-1.4:1.4
>> > Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
>> > renamed from eth0
>> > Feb 02 15:54:18 hades kernel: IPv6: ADDRCONF(NETDEV_UP):
>> > enx7c669d4bac92: link is not ready
>> > Feb 02 15:54:19 hades kernel: scsi 16:0:0:0: Direct-Access Linux
>> >  File-Stor Gadget 0401 PQ: 0 ANSI: 2
>> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: Attached scsi generic sg1
>> type 0
>> > 

Re: [beagleboard] debian testing: 2016-01-31 (Node-RED)

[Wally Bkg]

Thanks, I will definitely look into this if I find nodejs or node-red 
useful to my projects, but I'm setting up a system to get a non-programmer 
started with an automation project using a BBG as an alternative to wiring 
up a bunch of relays and timers.  I'm going to give it to him tomorrow and 
show him some simple demos I've set up.  He's ~80 miles away, being 
"off-grid" with only limited Internet access via cell phone tethering so 
there are some serious obstacles for a programming newbie.



On Tuesday, February 2, 2016 at 3:56:41 PM UTC-6, john3909 wrote:
>
> Why don’t you use C/C++ addons for Nodejs?
>
> https://nodejs.org/dist/latest-v5.x/docs/api/addons.html
>
> With Nodejs C/C++ addons, you can interface to any I/O on the BBB.
>
> Regards,
> John
>
>
>
>
> On Feb 2, 2016, at 1:39 PM, Wally Bkg > 
> wrote:
>
> I think its pretty sweet to have node-red running "out of the box" but 
> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript 
> PWM is still broken) its nowhere near as neat as it could be!
>
> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript 
> working beyond installing the Beaglebone nodes with npm?
>
>
> I'm having issues with this image getting the "gadget" to connect -- it 
> seems to only work from a cold start -- when I first plug it in the FAT 
> partition mount but the gadget hangs "waiting for IP address"  If I press 
> reset it may or may not start after the reboot.  So far its always started 
> if I hold the powerbutton down until it shuts off, and then press it again 
> to do a cold boot.
>
> Some of it may be that I'm using Ubuntu-Mate 15.10,  I try it later on my 
> main Ubuntu 10.04 which has been mostly reliable mounting the gadget 
> Ethernet.
>
>
> On Tuesday, February 2, 2016 at 10:41:29 AM UTC-6, RobertCNelson wrote:
>>
>> On Mon, Feb 1, 2016 at 9:49 AM, Robert Nelson  
>> wrote: 
>> > Howdy! 
>> > 
>> > So there's a little something new in this week's snapshot (lxqt not 
>> console): 
>> > 
>> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31 
>> > 
>> > http://beaglebone.local:1880/ 
>> > 
>> > nodered.org v0.13.1 
>>
>> On earlier jessie/stretch rootfs, then can now be installed via: 
>>
>> sudo apt-get update 
>> sudo apt-get install bb-node-red-installer 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: debian testing: 2016-01-31 (Node-RED)

[William Hermans]

>
> *think its pretty sweet to have node-red running "out of the box" but
> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript
> PWM is still broken) its nowhere near as neat as it could be!*
>

So, why don't you learn how to do this without using Bonescript ? It's not
that hard, but is not exactly something that is easily relate-able via
email either. But I'll try . . .

What I did was . . .


   - start from a fresh bare image, but for simplicity a console image
   would work fine too.
   - downloaded, and installed development prerequisites. Including git.
   - downloaded Nodejs code via git, compiled, and installed once finished
   compiling.
   - Learned a bit of how to access files from Nodejs . . . and all set . .
   .done.



On Tue, Feb 2, 2016 at 3:16 PM, Robert Nelson 
wrote:

> On Tue, Feb 2, 2016 at 3:57 PM, Robert Nelson 
> wrote:
> > On Tue, Feb 2, 2016 at 3:39 PM, Wally Bkg  wrote:
> >> I think its pretty sweet to have node-red running "out of the box" but
> >> without the BoneScript access to the GPIO and A/D pins (I assume
> BoneScript
> >> PWM is still broken) its nowhere near as neat as it could be!
> >
> > GPIO & A/D can be accessed via config-pin
> >
> > root@beaglebone:~# config-pin -l P9.18
> > default gpio gpio_pu gpio_pd spi i2c pwm
> >
> >
> >>
> >> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript
> >> working beyond installing the Beaglebone nodes with npm?
> >
> > sudo apt-get install linux-image-3.8.13-bone79
> > sudo reboot
> >
> > Bonescript is installed..
> >
> >> I'm having issues with this image getting the "gadget" to connect -- it
> >> seems to only work from a cold start -- when I first plug it in the FAT
> >> partition mount but the gadget hangs "waiting for IP address"  If I
> press
> >> reset it may or may not start after the reboot.  So far its always
> started
> >> if I hold the powerbutton down until it shuts off, and then press it
> again
> >> to do a cold boot.
> >
> > Okay, that's different..  Starts flashing the clean image to do reset
> > button testing. ;)
> >
> > journalctl -f | grep kernel
> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: Attached scsi generic sg1
> type 0
> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] 81920 512-byte
> > logical blocks: (41.9 MB/40.0 MiB)
> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write Protect is off
> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write cache: enabled,
> > read cache: enabled, doesn't support DPO or FUA
> > Feb 02 15:52:54 hades kernel:  sdb: sdb1
> > Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Attached SCSI removable
> disk
> > push reboot...
> > Feb 02 15:53:53 hades kernel: usb 5-1.4: USB disconnect, device number 8
> > Feb 02 15:53:53 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
> > unregister 'rndis_host' usb-:00:10.1-1.4, RNDIS device
> > Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronizing SCSI cache
> > Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronize Cache(10)
> > failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> > Feb 02 15:54:18 hades kernel: usb 5-1.4: new high-speed USB device
> > number 9 using xhci_hcd
> > Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device found,
> > idVendor=1d6b, idProduct=0104
> > Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device strings:
> > Mfr=3, Product=4, SerialNumber=5
> > Feb 02 15:54:18 hades kernel: usb 5-1.4: Product: BeagleBoneBlack
> > Feb 02 15:54:18 hades kernel: usb 5-1.4: Manufacturer: Circuitco
> > Feb 02 15:54:18 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103
> > Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 eth0: register
> > 'rndis_host' at usb-:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92
> > Feb 02 15:54:18 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device
> > Feb 02 15:54:18 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage
> > device detected
> > Feb 02 15:54:18 hades kernel: scsi host16: usb-storage 5-1.4:1.4
> > Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
> > renamed from eth0
> > Feb 02 15:54:18 hades kernel: IPv6: ADDRCONF(NETDEV_UP):
> > enx7c669d4bac92: link is not ready
> > Feb 02 15:54:19 hades kernel: scsi 16:0:0:0: Direct-Access Linux
> >  File-Stor Gadget 0401 PQ: 0 ANSI: 2
> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: Attached scsi generic sg1
> type 0
> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] 81920 512-byte
> > logical blocks: (41.9 MB/40.0 MiB)
> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write Protect is off
> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write cache: enabled,
> > read cache: enabled, doesn't support DPO or FUA
> > Feb 02 15:54:19 hades kernel:  sdb: sdb1
> > Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Attached SCSI removable
> disk
> > yank power
> 

Re: [beagleboard] Failure to recognize SD card inserted at runtime

[Wally Bkg]

If you don't have another SD card to try and can lose these contents, its 
worth trying a reformat to a single partition, although Ubuntu generally 
seems very good at handling multi-partition SD cards.

I have hot plugged an SD card into Debian 7.9 (image 2015-11-12) same as 
you have done, (the card I used to flash with) and it worked, although it 
didn't automount.   I see in your first post you said your card worked on a 
Debian 3.8 kernel, so  I'd suspect it may be a kernel version issue or 
something wrong with the udev rules for your Ubuntu (sorry, I'm no help 
with these).

Just as I about to hit "POST" it occurred to me the flasher may have cloned 
the image to the eMMC so the card may have the same UUID as the eMMC which 
might mess up the udev rules.  Try blkid on your BBB to get the UUID of the 
eMMC and do it with the SD card in another system to see if they are the 
same.


On Monday, February 1, 2016 at 9:59:53 AM UTC-6, Hilmar Lapp wrote:
>
> Any chance someone has an idea what might be going wrong here? I’d be 
> happy to reformat the card or take other destructive measures, but right 
> now the device for the card is not even showing up under /dev when the card 
> is inserted.
>
> Is it that the 4.1.15-ti-r40 kernel doesn’t support hot-plugging of uSD 
> cards? If so, anything I can do to change that? And I’m not sure how to 
> boot into the eMMC when the card is inserted in at boot. (The system will 
> boot into the SD card if inserted.)
>
>   -hilmar
>
> On Jan 25, 2016, at 11:28 AM, Hilmar Lapp > 
> wrote:
>
> I am running the Ubuntu 14.04.3 image from Dec 11, 2015, on a Beaglebone 
> Black, with updated packages and updated kernel. System details below. When 
> I insert an SD card with 2 Linux partitions (and formatted ext4 
> filesystems) on it after boot, it fails to be recognized.  The following 
> message appears in syslog:
>
> Jan 25 11:01:52 hostname kernel: [47672.809891] mmc0: card never left busy 
> state
> Jan 25 11:01:52 hostname kernel: [47672.814264] mmc0: error -110 whilst 
> initialising SD card
>
> The odd thing is that first this is the same card onto which I wrote and 
> then booted the downloaded image. I later flashed the card to the eMMC. So 
> I can boot from the card successfully (which presumably means the kernel 
> supports it), but when booting into the same kernel and rootfs from the 
> eMMC, it's reported as failing to initialize. Also, I *can* insert the card 
> perfectly fine into a BBB running Debian Wheezy with kernel 3.8.13-bone79 
> booted from the eMMC - the kernel recognizes it, udisks-daemon fires, 
> partitions get mounted etc, all without any errors. So I'm rather confident 
> that the card is fine.
>
> Anyone got any ideas what I might be missing?
>
>   -hilmar
>
> System details: starting image 
> bone-ubuntu-14.04.3-console-armhf-2015-12-11-2gb.img
>
> ubuntu@hostname:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 14.04.3 LTS
> Release: 14.04
> Codename: trusty
> ubuntu@hostname:~$ uname -a
> Linux hostname 4.1.15-ti-r40 #1 SMP PREEMPT Fri Jan 8 09:45:11 UTC 2016 
> armv7l armv7l armv7l GNU/Linux
>
>
>
> -- 
> 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/IeLSZ19NbMU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Hilmar Lapp -:- lappland.io
>
>
>
>

-- 
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: Make a backup of contents of one beaglebone black and install said contents on a second BBB

[Wally Bkg]

I'll try to walk you through this, step by step but it may take awhile.  
I'll try to check this thread everyday.

Since you are using the eMMC the easiest backup will be if you can "hot 
plug" a micro SD card.  Get an 8GB Class 10 card.  After you boot your 
Beaglebone open a terminal window (the root console tab in Cloud9 will 
work, although putty or ssh will be better) and do the command:  ls 
/dev/mmc*
you should see something like:
/dev/mmcblk0  /dev/mmcblk0p1  /dev/mmcblk1boot0

Next plug in the SD card and repeat the ls /dev/mmc* command, you should 
then see something like:
/dev/mmcblk0/dev/mmcblk1   /dev/mmcblk1boot1  /dev/mmcblk1p2
/dev/mmcblk0p1  /dev/mmcblk1boot0  /dev/mmcblk1p1

If these appear you should be able to use dd to clone your eMMC to the SD 
card.  Try this and let me know what you find.  Use a card larger than the 
eMMC so the command won't fail if your SD card is a bit smaller than the 
eMMC, that is why I suggest an 8GB card.

Hope this helps, If your card doesn't "hot plug"  post the links to what 
procedures you've found and I can try to help you follow the one I think 
should work with the least hassle.



On Monday, February 1, 2016 at 3:19:24 PM UTC-6, canis wrote:
>
> Hi Wally
>
> Many thanks.  I'll apologize in advance- there are terms I'm not familiar 
> with; I fear I'll have to take small steps
>
> First question, is your system running from an SD card or the eMMC?
>
> Running the eMMC
>
> If running from an SD card, just "clone" or duplicate the card using 
> Windows or Linux tools.  If its running from the eMMC (on-board storage).  
> It'll require knowing some Linux commands.   For a beginner, I'd suggest 
> downloading an image as close to what is in your eMMC as you can, write 
> it to an SD and then mounting the SD card using a USB to SD card adapter 
> (this gets you the correct partition layout) on the BBB and using rsync or 
> dd to clone (copy) the / (root) and /boot partitions from your eMMC to the 
> SD card.
>
> Is the image the list of files & folders visible upon opening BBB on my 
> laptop OR the list of folders and files within Cloud 9 OR something else?
>
> Thanks again,
> canis
>
>
>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: debian testing: 2016-01-31 (Node-RED)

[Robert Nelson]

On Tue, Feb 2, 2016 at 3:57 PM, Robert Nelson  wrote:
> On Tue, Feb 2, 2016 at 3:39 PM, Wally Bkg  wrote:
>> I think its pretty sweet to have node-red running "out of the box" but
>> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript
>> PWM is still broken) its nowhere near as neat as it could be!
>
> GPIO & A/D can be accessed via config-pin
>
> root@beaglebone:~# config-pin -l P9.18
> default gpio gpio_pu gpio_pd spi i2c pwm
>
>
>>
>> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript
>> working beyond installing the Beaglebone nodes with npm?
>
> sudo apt-get install linux-image-3.8.13-bone79
> sudo reboot
>
> Bonescript is installed..
>
>> I'm having issues with this image getting the "gadget" to connect -- it
>> seems to only work from a cold start -- when I first plug it in the FAT
>> partition mount but the gadget hangs "waiting for IP address"  If I press
>> reset it may or may not start after the reboot.  So far its always started
>> if I hold the powerbutton down until it shuts off, and then press it again
>> to do a cold boot.
>
> Okay, that's different..  Starts flashing the clean image to do reset
> button testing. ;)
>
> journalctl -f | grep kernel
> Feb 02 15:52:54 hades kernel: sd 15:0:0:0: Attached scsi generic sg1 type 0
> Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] 81920 512-byte
> logical blocks: (41.9 MB/40.0 MiB)
> Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write Protect is off
> Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write cache: enabled,
> read cache: enabled, doesn't support DPO or FUA
> Feb 02 15:52:54 hades kernel:  sdb: sdb1
> Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Attached SCSI removable disk
> push reboot...
> Feb 02 15:53:53 hades kernel: usb 5-1.4: USB disconnect, device number 8
> Feb 02 15:53:53 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
> unregister 'rndis_host' usb-:00:10.1-1.4, RNDIS device
> Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronizing SCSI cache
> Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronize Cache(10)
> failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Feb 02 15:54:18 hades kernel: usb 5-1.4: new high-speed USB device
> number 9 using xhci_hcd
> Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device found,
> idVendor=1d6b, idProduct=0104
> Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device strings:
> Mfr=3, Product=4, SerialNumber=5
> Feb 02 15:54:18 hades kernel: usb 5-1.4: Product: BeagleBoneBlack
> Feb 02 15:54:18 hades kernel: usb 5-1.4: Manufacturer: Circuitco
> Feb 02 15:54:18 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103
> Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 eth0: register
> 'rndis_host' at usb-:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92
> Feb 02 15:54:18 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device
> Feb 02 15:54:18 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage
> device detected
> Feb 02 15:54:18 hades kernel: scsi host16: usb-storage 5-1.4:1.4
> Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
> renamed from eth0
> Feb 02 15:54:18 hades kernel: IPv6: ADDRCONF(NETDEV_UP):
> enx7c669d4bac92: link is not ready
> Feb 02 15:54:19 hades kernel: scsi 16:0:0:0: Direct-Access Linux
>  File-Stor Gadget 0401 PQ: 0 ANSI: 2
> Feb 02 15:54:19 hades kernel: sd 16:0:0:0: Attached scsi generic sg1 type 0
> Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] 81920 512-byte
> logical blocks: (41.9 MB/40.0 MiB)
> Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write Protect is off
> Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Mode Sense: 0f 00 00 00
> Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write cache: enabled,
> read cache: enabled, doesn't support DPO or FUA
> Feb 02 15:54:19 hades kernel:  sdb: sdb1
> Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Attached SCSI removable disk
> yank power
> Feb 02 15:54:39 hades kernel: usb 5-1.4: USB disconnect, device number 9
> Feb 02 15:54:39 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
> unregister 'rndis_host' usb-:00:10.1-1.4, RNDIS device
> Feb 02 15:54:39 hades kernel: sd 16:0:0:0: [sdb] Synchronizing SCSI cache
> Feb 02 15:54:39 hades kernel: sd 16:0:0:0: [sdb] Synchronize Cache(10)
> failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
> Feb 02 15:55:07 hades kernel: usb 5-1.4: new high-speed USB device
> number 10 using xhci_hcd
> Feb 02 15:55:07 hades kernel: usb 5-1.4: New USB device found,
> idVendor=1d6b, idProduct=0104
> Feb 02 15:55:07 hades kernel: usb 5-1.4: New USB device strings:
> Mfr=3, Product=4, SerialNumber=5
> Feb 02 15:55:07 hades kernel: usb 5-1.4: Product: BeagleBoneBlack
> Feb 02 15:55:07 hades kernel: usb 5-1.4: Manufacturer: Circuitco
> Feb 02 15:55:07 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103
> Feb 02 15:55:07 hades kernel: rndis_host 5-1.4:1.0 eth0: register
> 'rndis_host

Re: [beagleboard] Re: debian testing: 2016-01-31 (Node-RED)

[Robert Nelson]

On Tue, Feb 2, 2016 at 3:39 PM, Wally Bkg  wrote:
> I think its pretty sweet to have node-red running "out of the box" but
> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript
> PWM is still broken) its nowhere near as neat as it could be!

GPIO & A/D can be accessed via config-pin

root@beaglebone:~# config-pin -l P9.18
default gpio gpio_pu gpio_pd spi i2c pwm


>
> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript
> working beyond installing the Beaglebone nodes with npm?

sudo apt-get install linux-image-3.8.13-bone79
sudo reboot

Bonescript is installed..

> I'm having issues with this image getting the "gadget" to connect -- it
> seems to only work from a cold start -- when I first plug it in the FAT
> partition mount but the gadget hangs "waiting for IP address"  If I press
> reset it may or may not start after the reboot.  So far its always started
> if I hold the powerbutton down until it shuts off, and then press it again
> to do a cold boot.

Okay, that's different..  Starts flashing the clean image to do reset
button testing. ;)

journalctl -f | grep kernel
Feb 02 15:52:54 hades kernel: sd 15:0:0:0: Attached scsi generic sg1 type 0
Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] 81920 512-byte
logical blocks: (41.9 MB/40.0 MiB)
Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write Protect is off
Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Mode Sense: 0f 00 00 00
Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Write cache: enabled,
read cache: enabled, doesn't support DPO or FUA
Feb 02 15:52:54 hades kernel:  sdb: sdb1
Feb 02 15:52:54 hades kernel: sd 15:0:0:0: [sdb] Attached SCSI removable disk
push reboot...
Feb 02 15:53:53 hades kernel: usb 5-1.4: USB disconnect, device number 8
Feb 02 15:53:53 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
unregister 'rndis_host' usb-:00:10.1-1.4, RNDIS device
Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronizing SCSI cache
Feb 02 15:53:53 hades kernel: sd 15:0:0:0: [sdb] Synchronize Cache(10)
failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 02 15:54:18 hades kernel: usb 5-1.4: new high-speed USB device
number 9 using xhci_hcd
Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device found,
idVendor=1d6b, idProduct=0104
Feb 02 15:54:18 hades kernel: usb 5-1.4: New USB device strings:
Mfr=3, Product=4, SerialNumber=5
Feb 02 15:54:18 hades kernel: usb 5-1.4: Product: BeagleBoneBlack
Feb 02 15:54:18 hades kernel: usb 5-1.4: Manufacturer: Circuitco
Feb 02 15:54:18 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103
Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 eth0: register
'rndis_host' at usb-:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92
Feb 02 15:54:18 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device
Feb 02 15:54:18 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage
device detected
Feb 02 15:54:18 hades kernel: scsi host16: usb-storage 5-1.4:1.4
Feb 02 15:54:18 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
renamed from eth0
Feb 02 15:54:18 hades kernel: IPv6: ADDRCONF(NETDEV_UP):
enx7c669d4bac92: link is not ready
Feb 02 15:54:19 hades kernel: scsi 16:0:0:0: Direct-Access Linux
 File-Stor Gadget 0401 PQ: 0 ANSI: 2
Feb 02 15:54:19 hades kernel: sd 16:0:0:0: Attached scsi generic sg1 type 0
Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] 81920 512-byte
logical blocks: (41.9 MB/40.0 MiB)
Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write Protect is off
Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Mode Sense: 0f 00 00 00
Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Write cache: enabled,
read cache: enabled, doesn't support DPO or FUA
Feb 02 15:54:19 hades kernel:  sdb: sdb1
Feb 02 15:54:19 hades kernel: sd 16:0:0:0: [sdb] Attached SCSI removable disk
yank power
Feb 02 15:54:39 hades kernel: usb 5-1.4: USB disconnect, device number 9
Feb 02 15:54:39 hades kernel: rndis_host 5-1.4:1.0 enx7c669d4bac92:
unregister 'rndis_host' usb-:00:10.1-1.4, RNDIS device
Feb 02 15:54:39 hades kernel: sd 16:0:0:0: [sdb] Synchronizing SCSI cache
Feb 02 15:54:39 hades kernel: sd 16:0:0:0: [sdb] Synchronize Cache(10)
failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Feb 02 15:55:07 hades kernel: usb 5-1.4: new high-speed USB device
number 10 using xhci_hcd
Feb 02 15:55:07 hades kernel: usb 5-1.4: New USB device found,
idVendor=1d6b, idProduct=0104
Feb 02 15:55:07 hades kernel: usb 5-1.4: New USB device strings:
Mfr=3, Product=4, SerialNumber=5
Feb 02 15:55:07 hades kernel: usb 5-1.4: Product: BeagleBoneBlack
Feb 02 15:55:07 hades kernel: usb 5-1.4: Manufacturer: Circuitco
Feb 02 15:55:07 hades kernel: usb 5-1.4: SerialNumber: 0C-2414BBBK0103
Feb 02 15:55:07 hades kernel: rndis_host 5-1.4:1.0 eth0: register
'rndis_host' at usb-:00:10.1-1.4, RNDIS device, 7c:66:9d:4b:ac:92
Feb 02 15:55:07 hades kernel: cdc_acm 5-1.4:1.2: ttyACM0: USB ACM device
Feb 02 15:55:07 hades kernel: usb-storage 5-1.4:1.4: USB Mass Storage
device detected
Feb 0

Re: [beagleboard] debian testing: 2016-01-31 (Node-RED)

[John Syne]

Why don’t you use C/C++ addons for Nodejs?

https://nodejs.org/dist/latest-v5.x/docs/api/addons.html 


With Nodejs C/C++ addons, you can interface to any I/O on the BBB.

Regards,
John




> On Feb 2, 2016, at 1:39 PM, Wally Bkg  wrote:
> 
> I think its pretty sweet to have node-red running "out of the box" but 
> without the BoneScript access to the GPIO and A/D pins (I assume BoneScript 
> PWM is still broken) its nowhere near as neat as it could be!
> 
> If I "downgrade" to 3.8 kernel, what else is required to get BoneScript 
> working beyond installing the Beaglebone nodes with npm?
> 
> 
> I'm having issues with this image getting the "gadget" to connect -- it seems 
> to only work from a cold start -- when I first plug it in the FAT partition 
> mount but the gadget hangs "waiting for IP address"  If I press reset it may 
> or may not start after the reboot.  So far its always started if I hold the 
> powerbutton down until it shuts off, and then press it again to do a cold 
> boot.
> 
> Some of it may be that I'm using Ubuntu-Mate 15.10,  I try it later on my 
> main Ubuntu 10.04 which has been mostly reliable mounting the gadget Ethernet.
> 
> 
> On Tuesday, February 2, 2016 at 10:41:29 AM UTC-6, RobertCNelson wrote:
> On Mon, Feb 1, 2016 at 9:49 AM, Robert Nelson  > wrote: 
> > Howdy! 
> > 
> > So there's a little something new in this week's snapshot (lxqt not 
> > console): 
> > 
> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31 
> >  
> > 
> > http://beaglebone.local:1880/  
> > 
> > nodered.org  v0.13.1 
> 
> On earlier jessie/stretch rootfs, then can now be installed via: 
> 
> sudo apt-get update 
> sudo apt-get install bb-node-red-installer 
> 
> 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] Re: debian testing: 2016-01-31 (Node-RED)

[Wally Bkg]

I think its pretty sweet to have node-red running "out of the box" but 
without the BoneScript access to the GPIO and A/D pins (I assume BoneScript 
PWM is still broken) its nowhere near as neat as it could be!

If I "downgrade" to 3.8 kernel, what else is required to get BoneScript 
working beyond installing the Beaglebone nodes with npm?


I'm having issues with this image getting the "gadget" to connect -- it 
seems to only work from a cold start -- when I first plug it in the FAT 
partition mount but the gadget hangs "waiting for IP address"  If I press 
reset it may or may not start after the reboot.  So far its always started 
if I hold the powerbutton down until it shuts off, and then press it again 
to do a cold boot.

Some of it may be that I'm using Ubuntu-Mate 15.10,  I try it later on my 
main Ubuntu 10.04 which has been mostly reliable mounting the gadget 
Ethernet.


On Tuesday, February 2, 2016 at 10:41:29 AM UTC-6, RobertCNelson wrote:
>
> On Mon, Feb 1, 2016 at 9:49 AM, Robert Nelson  > wrote: 
> > Howdy! 
> > 
> > So there's a little something new in this week's snapshot (lxqt not 
> console): 
> > 
> > http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31 
> > 
> > http://beaglebone.local:1880/ 
> > 
> > nodered.org v0.13.1 
>
> On earlier jessie/stretch rootfs, then can now be installed via: 
>
> sudo apt-get update 
> sudo apt-get install bb-node-red-installer 
>
> 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.

[beagleboard] Re: add i2c expander PCA9535 using device tree

[Graham]

You didn't say which version of OS you were running.
The I2C busses were renumbered in later OS.
Since you mentioned kernel 4.1.15, I will assume that you are running 
Debian 8

In Debian 8, I2C2 is pinned out to P9-19 and P9-20 by default. (No device 
tree changes necessary.)
Hook your expander there and see if you can see it with i2cdetect.

--- Graham

==

On Tuesday, February 2, 2016 at 4:54:55 AM UTC-6, malkowki_belgium wrote:
>
> Hello all,
>
> I am trying to add the PCA 9535 expander on the i2c2 bus on P9. 23 and 
> P9.24 using the device tree but I cannot detect it when booting the board 
> with the kernel 4.1.15.
> below the way I declare the device on the DTS.
>
> Do you know what I am doing wrong?
>
> &omap3_pmx_core {
> pinctrl-names = "default";
> pinctrl-0 = <
> &hsusb2_pins
> >;
>  i2c2_pins: pinmux_i2c_pins {
> pinctrl-single,pins = <
> 0x18E (PIN_INPUT_PULLUP | MUX_MODE0) /* 
> i2c2_scl.gpio_168 */
> 0x190 (PIN_INPUT_PULLUP | MUX_MODE0) /* 
> i2c2_sda.gpio_136 */
> 
>>; 
> };
>
> &i2c2 {
> 
> clock-frequency = <40>;
> 
> pca9535: gpio@20 {
> compatible = "nxp, pca9535";
> gpio-controller;
> #gpio-cell = <2>;
> reg = <0x20>;
> status = "okay";
> 
> };
>
>gpio@21 {
> compatible = "nxp, pca9535";
> gpio-controller;
> #gpio-cell = <2>;
> reg = <0x21>;
> status = "okay";
> 
>  };
>  gpio@22 {
> compatible = "nxp, pca9535";
> gpio-controller;
> status = "okay";
> #gpio-cell = <2>;
> reg = <0x22>;
> 
>  };
>  gpio@24 {
> compatible = "nxp, pca9535";
> gpio-controller;
> status = "okay";
> #gpio-cell = <2>;
> reg = <0x24>;
> 
>  };
> };
>
> &gpio5 {
> pinctrl-names = "defaults";
> pinctrl-0 = <
> &gpio_pins
> &i2c2_pins
> 
> >;
> };
>
>
>

-- 
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: Will the webcast "Taking the BeagleBone Cookbook recipes beyond BeagleBone Black" be available?

[Jason Kridner]

On Tuesday, February 2, 2016 at 10:04:58 AM UTC-5, Soapy Smith wrote:
>
> There is a 2-layer sign-in process, first you need an O'Reilly account, 
> then you have to register for the webcast.
>
> It's essentially a 1.5 hour long info-mercial for both Beagleboard.org and 
> "Beaglebone Cookbook" with the two authors of the book discussing numerous 
> Beagleboard topics.
>
> It's really good.  What I got out of it is a better understanding of the 
> history and motivation for Beagleboard.org.
> It's really starting to branch out and you will see where they are headed 
> with this technology.
>
> Starting about 80 minutes in there is a discussion of the Device Tree and 
> how it relates to "mainline Linux".  Worth a listen!
>
> I watched using Firefox in Ubuntu 14.04.  O'Reilly's media player is one 
> of the best I have seen.  There is a row of icons at the bottom you can use 
> to control the session.
> Very informative presentation by authors Mark Yoder and Jason Kridner!
>

Thanks! I'll ping O'Reilly to see if they will post without requiring so 
many login steps. 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cape manager on linux 4.1: can't load bone_eqep2b cape

[Robert Nelson]

On Tue, Feb 2, 2016 at 12:55 PM, Maksim Surov  wrote:
> I tried to run another devices, and I found that all the encoders conflict
> with somewhat. So, I add encoder 1:
>
> root@arm: # echo bone_eqep1 > /sys/devices/platform/bone_capemgr/slots
> root@arm: # cat /sys/devices/platform/bone_capemgr/slots
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,bone_eqep1
>
>
> There is no error, but actually eqep1 doesn't work. I looked at syslog:
>
> root@arm: # dmesg
> [   73.259486] bone_capemgr bone_capemgr: part_number 'bone_eqep1', version
> 'N/A'
> [   73.259580] bone_capemgr bone_capemgr: slot #4: override
> [   73.259632] bone_capemgr bone_capemgr: Using override eeprom data at slot
> 4
> [   73.259687] bone_capemgr bone_capemgr: slot #4: 'Override Board
> Name,00A0,Override Manuf,bone_eqep1'
> [   73.283359] bone_capemgr bone_capemgr: slot #4: dtbo
> 'bone_eqep1-00A0.dtbo' loaded; overlay id #0
> [   73.340888] pinctrl-single 44e10800.pinmux: pin 44e108d0.0 already
> requested by 0-0070; cannot claim for 48302180.eqep
> [   73.359630] pinctrl-single 44e10800.pinmux: pin-52 (48302180.eqep) status
> -22
> [   73.378359] pinctrl-single 44e10800.pinmux: could not request pin 52
> (44e108d0.0) from group pinctrl_eqep1_pins  on device pinctrl-single
> [   73.392369] eqep 48302180.eqep: Error applying setting, reverse things
> back
> [   73.400930] eqep 48302180.eqep: ver. 1.0
> [   73.401220] pinctrl-single 44e10800.pinmux: pin 44e108d0.0 already
> requested by 0-0070; cannot claim for 48302180.eqep
> [   73.416060] pinctrl-single 44e10800.pinmux: pin-52 (48302180.eqep) status
> -22
> [   73.424119] pinctrl-single 44e10800.pinmux: could not request pin 52
> (44e108d0.0) from group pinctrl_eqep1_pins  on device pinctrl-single
> [   73.437039] eqep 48302180.eqep: Error applying setting, reverse things
> back
> [   73.444534] eqep 48302180.eqep: unable to select pin group
>
> The same happens with eqep2.

That would be expected...

It shares pins are already muxed with the hdmi output..

So use one of the dtb= overrides in /boot/uEnv.txt

dtb=am335x-boneblack-emmc-overlay.dtb

or

dtb=am335x-boneblack-overlay.dtb


BBB compatibility issues:

https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md

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.

Re: [beagleboard] usb data filtering

[Chris Morgan]

On Tue, Feb 2, 2016 at 1:41 PM,  wrote:

> Hi,
> I need a device which makes usb disks read only. It will be a bridge
> between PC and USB disk (hard disk, stick, etc). PC will be able to read
> everything in usb disk but not able write. If there is no usb disk
> connected to the device it will not allow PC to detect itself.
> If you think that it is possible to do it with beaglebone with or without
> linux, please guide me.
>
> Thanks in advance,
> Serdar
>
> --
> 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.
>


Hello.

The bbb supports the usb gadget driver that will provide access to the
local filesystems (emmc etc) via the mini-usb-b port. I'd imagine you could
modify this configuration to mount, as read-only, your eventual target
disk, which is plugged into the host-a usb port.

So it seems like this could be doable. I'd wonder what kind of performance
you might get.

Chris

-- 
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] usb data filtering

[icegray]

Hi,
I need a device which makes usb disks read only. It will be a bridge 
between PC and USB disk (hard disk, stick, etc). PC will be able to read 
everything in usb disk but not able write. If there is no usb disk 
connected to the device it will not allow PC to detect itself.
If you think that it is possible to do it with beaglebone with or without 
linux, please guide me.

Thanks in advance,
Serdar

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cape manager on linux 4.1: can't load bone_eqep2b cape

[Maksim Surov]

I tried to run another devices, and I found that all the encoders conflict 
with somewhat. So, I add encoder 1:

root@arm: # echo bone_eqep1 > /sys/devices/platform/bone_capemgr/slots
root@arm: # cat /sys/devices/platform/bone_capemgr/slots
 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,bone_eqep1


There is no error, but actually eqep1 doesn't work. I looked at syslog:

root@arm: # dmesg
[   73.259486] bone_capemgr bone_capemgr: part_number 'bone_eqep1', version 
'N/A'
[   73.259580] bone_capemgr bone_capemgr: slot #4: override
[   73.259632] bone_capemgr bone_capemgr: Using override eeprom data at 
slot 4
[   73.259687] bone_capemgr bone_capemgr: slot #4: 'Override Board 
Name,00A0,Override Manuf,bone_eqep1'
[   73.283359] bone_capemgr bone_capemgr: slot #4: dtbo 
'bone_eqep1-00A0.dtbo' loaded; overlay id #0
[   73.340888] pinctrl-single 44e10800.pinmux: pin 44e108d0.0 already 
requested by 0-0070; cannot claim for 48302180.eqep
[   73.359630] pinctrl-single 44e10800.pinmux: pin-52 (48302180.eqep) 
status -22
[   73.378359] pinctrl-single 44e10800.pinmux: could not request pin 52 (
44e108d0.0) from group pinctrl_eqep1_pins  on device pinctrl-single
[   73.392369] eqep 48302180.eqep: Error applying setting, reverse things 
back
[   73.400930] eqep 48302180.eqep: ver. 1.0
[   73.401220] pinctrl-single 44e10800.pinmux: pin 44e108d0.0 already 
requested by 0-0070; cannot claim for 48302180.eqep
[   73.416060] pinctrl-single 44e10800.pinmux: pin-52 (48302180.eqep) 
status -22
[   73.424119] pinctrl-single 44e10800.pinmux: could not request pin 52 (
44e108d0.0) from group pinctrl_eqep1_pins  on device pinctrl-single
[   73.437039] eqep 48302180.eqep: Error applying setting, reverse things 
back
[   73.444534] eqep 48302180.eqep: unable to select pin group

The same happens with eqep2.



понедельник, 1 февраля 2016 г., 21:57:29 UTC+3 пользователь RobertCNelson 
написал:
>
> On Mon, Feb 1, 2016 at 12:37 PM, Soapy Smith  > wrote: 
> > # grep part-number bone_eqep2-00A0.dts 
> > part-number = "bone_eqep2"; 
> > # grep part-number bone_eqep2b.dts 
> > part-number = "bone_eqep2"; 
> > 
> > The source files for eqep2 and eqep2b both have the same part number? 
> > The dts files are in 
> > 
> > /opt/source/bb.org-overlays/src/arm 
>
> Good point, we can't do that: 
>
>
> https://github.com/beagleboard/bb.org-overlays/commit/cc5c45529402f5e8cea86b703c6e148cf10c0ffc
>  
>
> use "bone_eqep2b" for the one that doesn't conflict with hdmi.. 
>
> 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.

[beagleboard] Re: strange error when running simple *.js file setting a pin to output using beaglebone black Rev C.

[vlupinek]

Hi.

I use beaglebone-green and i try enable P8_15.

In folder /lib/firmware i found files bspm_P8_15_27-00A0.dts and 
bspm_P8_15_27-00A0.dtbo

I try enable PIN with command
echo bspm_P8_15_27 > /sys/devices/bone_capemgr.9/slots
but result was with error

Then I edit file bspm_P8_15_27-00A0.dts
change line
compatible = "ti,beaglebone", "ti,beaglebone-black";
to
compatible = "ti,beaglebone", "ti,beaglebone-black", "ti,beaglebone-green";

Rebuilt file with command
dtc -@ -I dts -O dtb -o bspm_P8_15_27-00A0.dtbo bspm_P8_15_27-00A0.dts

Then I try command
echo bspm_P8_15_27 > /sys/devices/bone_capemgr.9/slots

and result is OK.

Content /sys/devices/bone_capemgr.9/slots is
0: 54:P---L 4D 7.0 LCD CAPE- 4DCAPE-70T ,00A3,4D SYSTEMS  
,BB-BONE-LCD7-01
 1: 55:PF--- 
 2: 56:PF--- 
 3: 57:PF--- 
 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
 6: ff:P-O-L Override Board Name,00A0,Override Manuf,bspm_P8_15_27
 

Now i can use PIN P8_15.

Sorry for my english.

I wish help you.

Dne středa 20. srpna 2014 11:06:04 UTC+2 fung...@auckland.ac.nz napsal(a):
>
>
> Hello! How's everything?
>
> I encountered strange error when running simple *.js file 
> setting a pin to output using beaglebone black Rev C which I received this 
> August.
>
> I even reinstalled bonescript using 
> "npm install -g bonescript"
> but still encounter the same error message.
>
> led = "P9_11", "9_12" worked
> led = "P8_39", "P8_40", "P8_41", and many other pins
> do not work with error message listed below
> following "simpleDigitalOut.js":
>
> //
> //simpleDigitalOut.js
>
> var b = require('/usr/local/lib/node_modules/bonescript');
>
> var led = "P8_41";
> b.pinMode(led, b.OUTPUT);
>
> console.log("end of program");
>
> //=
> ro...@beaglebone:/var/lib/cloud9/myProg # node 
> simpleDigitalOut.js
>
> /usr/local/lib/node_modules/bonescript/my.js:57
> if(slot[0]) {
>^
> TypeError: Cannot read property '0' of null
> at Object.exports.load_dt 
> (/usr/local/lib/node_modules/bonescript/my.js:57:20)
> at Object.exports.create_dt 
> (/usr/local/lib/node_modules/bonescript/my.js:123:33)
> at Object.exports.setPinMode 
> (/usr/local/lib/node_modules/bonescript/hw_capemgr.js:83:12)
> at Object.f.pinMode 
> (/usr/local/lib/node_modules/bonescript/index.js:160:15)
> at Object. (/var/lib/cloud9/myProg/simpleDigitalOut.js:4:3)
> at Module._compile (module.js:456:26)
> at Object.Module._extensions..js (module.js:474:10)
> at Module.load (module.js:356:32)
> at Function.Module._load (module.js:312:12)
> at Function.Module.runMain (module.js:497:10)
> ro...@beaglebone:/var/lib/cloud9/myProg #
> //=
>
> I googled but cannot find a solution to this problem.
>
> It would be a great help if you can guide me through it.
> your advice is very much appreciated.
>
> Many thanks,
> Fung Yang
>

-- 
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: debian testing: 2016-01-31 (Node-RED)

[Wally Bkg]

Thanks!  I'm downloading it now.  I'll post if I have any issues on a BBG,  
I plan on using an 8GB SD card.


On Monday, February 1, 2016 at 9:50:02 AM UTC-6, RobertCNelson wrote:
>
> Howdy! 
>
> So there's a little something new in this week's snapshot (lxqt not 
> console): 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31 
>
> http://beaglebone.local:1880/ 
>
> nodered.org v0.13.1 
>
> 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.

Re: [beagleboard] Does apt-get upgrade not update BoneScript?

[Robert Nelson]

On Tue, Feb 2, 2016 at 11:30 AM, Wally Bkg  wrote:
>
> On Sunday, January 31, 2016 at 3:26:37 PM UTC-6, RobertCNelson wrote:
>>
>> On Sun, Jan 31, 2016 at 10:42 AM, Wally Bkg  wrote:
>> > So you are saying I will still need to stay with the 7.9 image series
>> > for
>> > BoneScript for the foreseeable future?
>>
>> or install the 3.8.x based kernel on jessie.
>
>
> Other than the  Bonescript PWM analogWrite() not working and the other
> "harmless" error messages thrown, its hard to see how either would make a
> difference to my friend.  He is not in a position to do a lot of image
> downloading or apt-get updating for lack of adequate Internet bandwidth at
> his rural location (he's actually "off-grid" running on solar power).
>
> The fact remains I could not explain why anyone should use Jessie over
> Wheezy, or vice-versa, other than "Jessie is newer and is the future".  But
> if the 3.8.x kernel on Jessie fixed the PWM and error message nags I'd
> quickly install it before I give him the BBG and proto-plate setup I've made
> to get him started.
>
>
>>
>>
>> > Can I get to 8.3 2016-01-24 from 8.2 2015-12-06 with apt-get updates and
>> > installs? or should I download the new image and start over?
>>
>> Yes/No
>>
>> Yes, you will get the same packages..
>>
>> No, you will not get the "extra" packages/things i added to
>> "2016-01-24"...
>
>
> If the extra stuff is all apt-get installable, a simple list of packages

It's in the commit log: "bb.org: jessie:"

https://github.com/beagleboard/image-builder/commits/master

> removed or added for the updated images would seem to save a lot of
> elinux.org download bandwidth. I assume that is also the reason for the
> *.bmap versions.

bandwidth is cheap, only pushed out 1.5TB last month...

>
>> > I think the "top level" beaglebone.localhost web page needs some serious
>> > updating as the link:
>> > http://192.168.7.2/bone101/Support/BoneScript/updates/
>> > is still talking about Angstrom.
>>
>> That repo is right here:
>>
>> https://github.com/beagleboard/beaglebone-getting-started
>>
>> go ahead fork it and submit pull requests.
>
>
> I would if I actually knew what the answers and changes were.  But it'd be
> ugly as I've never authored a webpage nor have I any experience with web
> authoring tools of any kind.  Authoring a webpage is just not on my bucket
> list.  Although writing some PRU code is :)
>
> I've had Beaglebones since the White, but this is the first time I've
> actually tried to do anything with Cloud9 and Bonescript.  Pointing out the
> problems I've found was in the hope that someone in position to fix it would
> be made aware.  I'm perfectly willing to accept that Beagleboard.org has
> given up on "beginners" instead focusing on near experts that want the PRU
> or DSP of the X-15.  Other than not having on-board A/D and a much lesser
> number of GPIO pins my friend would otherwise likely be better served with a
> Raspberry Pi2.
>
> Node-red is great, it'll be awesome if a few issues get fixed, having it
> work in a downloaded image is a very good thing IMHO, although the
> installation instructions on the node-red website are very good.

nah i have better ones today: (jessie/stretch rootfs)

sudo apt-get update
sudo apt-get install bb-node-red-installer


>> Angstrom is dead, it's maintainer left for a job at linaro, NO ONE has
>> stepped up since the fall of 2013 to pick up maintenance.
>>
>  Re forking the above, I'm in no position to declare "Angstrom Dead" on a
> website or a forum post, although I've suspected it, given the lack of
> updates since about 2013.  Although in my limited use of it and some of the
> recent Debian images with my A5A BBB HDMI it seemed Angstrom GUI was more
> responsive, although a lot more limited.
>
> I've given up on BBB HDMI, as I'm finding the GUI apps I want to use mostly
> work better with ssh -X anyway,  which is pretty neat when I run them on the
> BBG :)   Although it doesn't take a lot of GUI app installations to overflow
> the 4GB eMMC.
>
> I'm not sure that no one stepping up for Angstrom is such a bad thing,
> Debian is much better documented (probably the most complete of all distros)
> and all the really "minimal" Linux systems seem to be moving to Yacto
> project.  I've always though there has been too much duplicated effort in
> Linux.

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.

Re: [beagleboard] Does apt-get upgrade not update BoneScript?

[Wally Bkg]

On Sunday, January 31, 2016 at 3:26:37 PM UTC-6, RobertCNelson wrote:
>
> On Sun, Jan 31, 2016 at 10:42 AM, Wally Bkg  > wrote: 
> > So you are saying I will still need to stay with the 7.9 image series 
> for 
> > BoneScript for the foreseeable future? 
>
> or install the 3.8.x based kernel on jessie. 
>
 
Other than the  Bonescript PWM analogWrite() not working and the other 
"harmless" error messages thrown, its hard to see how either would make a 
difference to my friend.  He is not in a position to do a lot of image 
downloading or apt-get updating for lack of adequate Internet bandwidth at 
his rural location (he's actually "off-grid" running on solar power).

The fact remains I could not explain why anyone should use Jessie over 
Wheezy, or vice-versa, other than "Jessie is newer and is the future".  But 
if the 3.8.x kernel on Jessie fixed the PWM and error message nags I'd 
quickly install it before I give him the BBG and proto-plate setup I've 
made to get him started.

 

>
> > Can I get to 8.3 2016-01-24 from 8.2 2015-12-06 with apt-get updates and 
> > installs? or should I download the new image and start over? 
>
> Yes/No 
>
> Yes, you will get the same packages.. 
>
> No, you will not get the "extra" packages/things i added to 
> "2016-01-24"... 
>

If the extra stuff is all apt-get installable, a simple list of packages 
removed or added for the updated images would seem to save a lot of 
elinux.org download bandwidth. I assume that is also the reason for the 
*.bmap versions.


> I think the "top level" beaglebone.localhost web page needs some serious 
> > updating as the link: 
> > http://192.168.7.2/bone101/Support/BoneScript/updates/ 
> > is still talking about Angstrom. 
>
> That repo is right here: 
>
> https://github.com/beagleboard/beaglebone-getting-started 
>
> go ahead fork it and submit pull requests. 
>

I would if I actually knew what the answers and changes were.  But it'd be 
ugly as I've never authored a webpage nor have I any experience with web 
authoring tools of any kind.  Authoring a webpage is just not on my bucket 
list.  Although writing some PRU code is :)

I've had Beaglebones since the White, but this is the first time I've 
actually tried to do anything with Cloud9 and Bonescript.  Pointing out the 
problems I've found was in the hope that someone in position to fix it 
would be made aware.  I'm perfectly willing to accept that Beagleboard.org 
has given up on "beginners" instead focusing on near experts that want the 
PRU or DSP of the X-15.  Other than not having on-board A/D and a much 
lesser number of GPIO pins my friend would otherwise likely be better 
served with a Raspberry Pi2.

Node-red is great, it'll be awesome if a few issues get fixed, having it 
work in a downloaded image is a very good thing IMHO, although the 
installation instructions on the node-red website are very good.


Angstrom is dead, it's maintainer left for a job at linaro, NO ONE has 
> stepped up since the fall of 2013 to pick up maintenance. 
>
>  Re forking the above, I'm in no position to declare "Angstrom Dead" on a 
website or a forum post, although I've suspected it, given the lack of 
updates since about 2013.  Although in my limited use of it and some of the 
recent Debian images with my A5A BBB HDMI it seemed Angstrom GUI was more 
responsive, although a lot more limited.

I've given up on BBB HDMI, as I'm finding the GUI apps I want to use mostly 
work better with ssh -X anyway,  which is pretty neat when I run them on 
the BBG :)   Although it doesn't take a lot of GUI app installations to 
overflow the 4GB eMMC.

I'm not sure that no one stepping up for Angstrom is such a bad thing, 
Debian is much better documented (probably the most complete of all 
distros) and all the really "minimal" Linux systems seem to be moving to 
Yacto project.  I've always though there has been too much duplicated 
effort in 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: debian testing: 2016-01-31 (Node-RED)

[Robert Nelson]

On Mon, Feb 1, 2016 at 9:49 AM, Robert Nelson  wrote:
> Howdy!
>
> So there's a little something new in this week's snapshot (lxqt not console):
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2016-01-31
>
> http://beaglebone.local:1880/
>
> nodered.org v0.13.1

On earlier jessie/stretch rootfs, then can now be installed via:

sudo apt-get update
sudo apt-get install bb-node-red-installer

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.

[beagleboard] Re: Will the webcast "Taking the BeagleBone Cookbook recipes beyond BeagleBone Black" be available?

[Soapy Smith]

There is a 2-layer sign-in process, first you need an O'Reilly account, 
then you have to register for the webcast.

It's essentially a 1.5 hour long info-mercial for both Beagleboard.org and 
"Beaglebone Cookbook" with the two authors of the book discussing numerous 
Beagleboard topics.

It's really good.  What I got out of it is a better understanding of the 
history and motivation for Beagleboard.org.
It's really starting to branch out and you will see where they are headed 
with this technology.

Starting about 80 minutes in there is a discussion of the Device Tree and 
how it relates to "mainline Linux".  Worth a listen!

I watched using Firefox in Ubuntu 14.04.  O'Reilly's media player is one of 
the best I have seen.  There is a row of icons at the bottom you can use to 
control the session.
Very informative presentation by authors Mark Yoder and Jason Kridner!

-- 
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 build machine

[k . nakul1]

hi team


i have a beagle bone black

I need to setup a build machine so that i can write some kernel code 
compile and flash it back to board
can any one help me with the system requirements and also steps to 
1) download android and debian packages on remote system.
2) steps to compile.
3) steps to flash on eMMC drive

Regards

-- 
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] add i2c expander PCA9535 using device tree

[malkowki_belgium]

Hello all,

I am trying to add the PCA 9535 expander on the i2c2 bus on P9. 23 and 
P9.24 using the device tree but I cannot detect it when booting the board 
with the kernel 4.1.15.
below the way I declare the device on the DTS.

Do you know what I am doing wrong?

&omap3_pmx_core {
pinctrl-names = "default";
pinctrl-0 = <
&hsusb2_pins
>;
 i2c2_pins: pinmux_i2c_pins {
pinctrl-single,pins = <
0x18E (PIN_INPUT_PULLUP | MUX_MODE0) /* 
i2c2_scl.gpio_168 */
0x190 (PIN_INPUT_PULLUP | MUX_MODE0) /* 
i2c2_sda.gpio_136 */

   >; 
};

&i2c2 {

clock-frequency = <40>;

pca9535: gpio@20 {
compatible = "nxp, pca9535";
gpio-controller;
#gpio-cell = <2>;
reg = <0x20>;
status = "okay";

};

   gpio@21 {
compatible = "nxp, pca9535";
gpio-controller;
#gpio-cell = <2>;
reg = <0x21>;
status = "okay";

 };
 gpio@22 {
compatible = "nxp, pca9535";
gpio-controller;
status = "okay";
#gpio-cell = <2>;
reg = <0x22>;

 };
 gpio@24 {
compatible = "nxp, pca9535";
gpio-controller;
status = "okay";
#gpio-cell = <2>;
reg = <0x24>;

 };
};

&gpio5 {
pinctrl-names = "defaults";
pinctrl-0 = <
&gpio_pins
&i2c2_pins

>;
};


-- 
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] PTP TEST( ethtool -T information)

[Juan Jonathan]

I am trying PTP and PPS function with LINUXPTP from sourceforge and testptp 
from kernel 4.1 document. We use "ethtool -T" to get the following. Is the 
"PTP Hardware Clock:0" is the correct value.
===

Time stamping parameters for eth0:

Capabilities:

hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)

software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)

hardware-receive  (SOF_TIMESTAMPING_RX_HARDWARE)

software-receive  (SOF_TIMESTAMPING_RX_SOFTWARE)

software-system-clock (SOF_TIMESTAMPING_SOFTWARE)

hardware-raw-clock(SOF_TIMESTAMPING_RAW_HARDWARE)

PTP Hardware Clock: 0

Hardware Transmit Timestamp Modes:

off   (HWTSTAMP_TX_OFF)

on(HWTSTAMP_TX_ON)

Hardware Receive Filter Modes:

none  (HWTSTAMP_FILTER_NONE)

ptpv2-event   (HWTSTAMP_FILTER_PTP_V2_EVENT)

==


We use testptp to get the clock capabilities. it show the following message.

We want to design a pulse output function. Can  the hardware config do this 
function?

===


beaglebone:~/TESTPTP# ./a.out -c

capabilities:

  100 maximum frequency adjustment (ppb)

  0 programmable alarms

  0 external time stamp channels

  0 programmable periodic signals

  0 pulse per second

==


Thanks for your help

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.