Re: [beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

2017-10-17 Thread CJA 
Okay, Thanks for letting me know..Please let me know if a spot opens up for 
-Rapid Prototyping & Linux Kernel Development with the PocketBeagle 
Platform ,and I will register for the workshop.. - Carmelito

On Monday, October 16, 2017 at 8:41:01 PM UTC-7, William Hermans wrote:
>
> Just a note, all workshops already sold out.
>
> On Mon, Oct 16, 2017 at 2:47 PM, Robert Nelson  > wrote:
>
>> On Mon, Oct 16, 2017 at 4:30 PM, CJA  
>> wrote:
>> > Hi Drew,
>> > Awesome, I just received my PocketBeagle today from arrow.com.  Is this
>> > going to be a full day workshop ? And are there any prerequisites, in 
>> terms
>> > of getting acquainted to certain topic's before attending the workshop..
>> > Thanks for the help - Carmelito
>>
>> What would you like us to talk about? ;)
>>
>> aka, i'm still writing everything up..  Definitely be going over
>> u-boot, kernel, u-boot overlays, config-pin, adafruit-io... ;)
>>
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYh9XY%2B5WPhyhjAHquzjqs8N200v%2BR30ORNe3QzCBdGtng%40mail.gmail.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/cf83f20f-079b-45a3-b4bf-dc2735b0f033%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

2017-10-17 Thread CJA 
Okay Thanks for letting me know.. - Carmelito

On Monday, October 16, 2017 at 8:41:01 PM UTC-7, William Hermans wrote:
>
> Just a note, all workshops already sold out.
>
> On Mon, Oct 16, 2017 at 2:47 PM, Robert Nelson  > wrote:
>
>> On Mon, Oct 16, 2017 at 4:30 PM, CJA  
>> wrote:
>> > Hi Drew,
>> > Awesome, I just received my PocketBeagle today from arrow.com.  Is this
>> > going to be a full day workshop ? And are there any prerequisites, in 
>> terms
>> > of getting acquainted to certain topic's before attending the workshop..
>> > Thanks for the help - Carmelito
>>
>> What would you like us to talk about? ;)
>>
>> aka, i'm still writing everything up..  Definitely be going over
>> u-boot, kernel, u-boot overlays, config-pin, adafruit-io... ;)
>>
>> 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 .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYh9XY%2B5WPhyhjAHquzjqs8N200v%2BR30ORNe3QzCBdGtng%40mail.gmail.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/02df0ab4-740f-486d-82d8-d6f5a0bb2b29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Activating I2C1 in BBB Rev C

2017-10-17 Thread Mala Dies 
Hello,

Look here if you are wanting it to last past 
boot: 
https://github.com/adafruit/adafruit-beaglebone-io-python/blob/master/doc/run_config-pin_during_startup.md.

Enjoy,

Seth

P.S. This helped me keep my configuration after boot, i.e. after reboot or 
starting the machine. 

On Saturday, October 14, 2017 at 6:01:11 AM UTC-5, sajeevan k wrote:
>
> Hi Jose Valenzuela San Juan,
>
> Thank You very much for the information.
>
> Based on Your mail, I tested again with
>
> config-pin P9.17 i2c
>
> config-pin P9.18 i2c
>
>
> Now it is working.  
>
>
> I might not have tested it properly.
>
>
>
> or I might have tested it, before doing modification in .dts file.
>
>
>
> Thank You very much for giving me plenty of information.
>
>
> Thanks & Regards,
> Sajeevan.K
>
>
> Thank 
>
> On Friday, October 13, 2017 at 11:09:01 PM UTC+5:30, Jose Valenzuela San 
> Juan wrote:
>>
>> Config-pin works fine though
>>
>> On Friday, October 13, 2017 at 2:36:09 PM UTC-3, Jose Valenzuela San Juan 
>> wrote:
>>>
>>> I forgot to mention
>>> I had the image version that you are using and after an apt-upgrade 
>>> (from debian image - bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img and 
>>> BBB Rev C. in july) config-pin stopped working.
>>>
>>> 
>>> https://groups.google.com/d/msg/beagleboard/AvRrv9aaFbw/Gfl-384BCAAJ
>>>
>>> Flashing the latest images solved the problem.
>>>
>>> One more thing. If you update to newer images, the way the overlays are 
>>> loaded changed, so that video is now outdated.
>>>
>>> https://forum.digikey.com/t/all-beaglebone-varients-u-boot-overlays/26
>>> https://groups.google.com/d/msg/beagleboard/W0QPDee5u2s/Fl_LeVnmEgAJ
>>>  
>>> Regards,
>>> On Friday, October 13, 2017 at 2:23:04 PM UTC-3, Jose Valenzuela San 
>>> Juan wrote:

 Good to know that the info was helpful.

 That's weird, the script is made so that its friendly with how you 
 input the pin name: 917, p917, 9.17, 9-17, p9.17, P9-17 and so on, all 
 work 
 fine..

 The documentation is in the github page of the universal device tree 
 overlay and supporting scripts:
 https://github.com/cdsteinkuehler/beaglebone-universal-io

 regards,



 On Friday, October 13, 2017 at 5:09:21 AM UTC-3, sajeevan k wrote:
>
>
> Hi Jose Valenzuela San Juan,
>
> Thank You very much.
> Your suggestion solved my issue.
>
> Earlier I tried something like this as per the following video for pwm 
> enabling - https://www.youtube.com/watch?v=MT3wjlzQhNQ.
>
> I tried 
>
> config-pin P9.17 i2c
>
> config-pin P9.18 i2c
>
>
>
> But that was not successful. 
>
>
> Now I got the correct solution
>
>
> config-pin p9-17 i2c
> config-pin p9-18 i2c
>
> from You. Thank You.
> If You provide some documents which describes this, that would be more 
> appreciated.
>
> Thanks & Regards,
> Sajeevan.K
>
>
>
>
>
>
> On Thursday, October 12, 2017 at 7:00:59 PM UTC+5:30, Jose Valenzuela 
> San Juan wrote:
>>
>> What I do is enable them using config-pin like so (pins p9-17 & p9-18 
>> in the example):
>> sudo config-pin p9-17 i2c
>> sudo config-pin p9-18 i2c
>> by default those are configured as gpio. This settings are lost when 
>> you restart, but you can autoexecute those commands every boot.
>>
>> You can see how are configured (or check if the previos command 
>> worked) with the -q option:
>> config-pin -q p9-17
>>
>>
>> list available modes with -l:
>> config-pin -l p9-17
>>
>>
>> or get detailed info with -i:
>> config-pin -i p9-17
>>
>>
>> That's what i am using for the moment, but I like to also know for a 
>> more 
>> correct/goodpractice/efficient/permanent/lowlevel/before-boot/devicetree/uboot
>>  
>> way of setting those parameters.
>>
>> Other thing: the latest images were updated check 
>> https://beagleboard.org/latest-images.
>> Also there are monthly and weekly releases: https://rcn-ee.net
>> You most probably need to update u-boot to go from 
>> bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img to the latest.
>>
>> Regards,
>>
>> On Thursday, October 12, 2017 at 9:07:06 AM UTC-3, sajeevan k wrote:
>>>
>>> Hi all,
>>>
>>> I would like to use both I2C1 and I2C2 which are available in 
>>> Beaglebone Black P9 connector. I could make I2C2 working. But so far I 
>>> couldn't make I2C1 working. 
>>>
>>> In /boot/uEnv.txt, I have not commented the line
>>> cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
>>>
>>> That means Universal cap is active.
>>>
>>> So I cannot use the command 
>>>
>>> echo BB-I2C1 > /sys/devices/platform/bone_capemgr/slots
>>>
>>>
>>> for enabling I2C1.
>>>

[beagleboard] Re: cannot SSH to BBB via LINUX terminal

2017-10-17 Thread Mala Dies 
Hello,

I usually just use ssh @192.168.7.2. For instance, while in root, 
type ssh debian@192.168.7.2 if your name is debian and if you are using the 
Debian Distro. This may work.

Seth

P.S. If it does not work, let me know. We can make sure you have 
sudo installed.

On Tuesday, October 17, 2017 at 5:42:47 AM UTC-5, Simas Paulius wrote:
>
> I'm trying to SSH to my BBB board via LINUX (UBUNTU 17.04 distro) terminal 
> using a command *ssh -v 192.168.7.2 *with no luck.
> I always get the same error:
>
>
> OpenSSH_7.4p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug1: Connecting to 192.168.7.2 [192.168.7.2] port 22.
> debug1: Connection established.
> debug1: identity file /home/simon/.ssh/id_rsa type 1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_rsa-cert type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_dsa type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_dsa-cert type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_ecdsa type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_ecdsa-cert type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_ed25519 type -1
> debug1: key_load_public: No such file or directory
> debug1: identity file /home/simon/.ssh/id_ed25519-cert type -1
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_7.4p1 Ubuntu-10
> ssh_exchange_identification: read: Connection reset by peer
>
> please give me some advice on this issue.
> Thank you in advance! :)
>

-- 
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/f5611f40-7e0b-40cc-9bb7-9241716e8925%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Failed to enable UART1, Ubuntu 16.04

2017-10-17 Thread Jeff Andich 
Glad I saw this post!  I was able to enable UART1 and confirm that the BBB 
talks to the UART on my host PC using config-pin 924/926 uart.  


However, I'm still having an issue with enabling UART1 or UART3 via u-boot 
overlays in uEnv.txt on the BBB.  I'm new to u-boot overlays.

When the following line(s) are added to uEnv.txt, and I reboot, the systemd 
gods get angry and won't grant me a Debian login prompt.
Note: I only have tried one UART overlay at a time.


uboot_overlay_addr3=/lib/firmware/BB-UART1-00A0.dtbo

OR

uboot_overlay_addr3=/lib/firmware/BB-UART3-00A0.dtbo



.
.
.
[   29.881903] random: nonblocking pool is initialized
[  *** ] A start job is running for LSB: con...ial ports (14min 37s / no 
limit)

It looks like UART1,2,4 are already enabled in the Debian 8.9, BBB console 
image I have (details about the version of u-boot, SPL, kernel, and debian 
at the end).


debian@beaglebone:~$ setserial -g /dev/ttyS[0-5]
/dev/ttyS0, UART: 8250, Port: 0x, IRQ: 158
/dev/ttyS1, UART: 8250, Port: 0x, IRQ: 159
/dev/ttyS2, UART: 8250, Port: 0x, IRQ: 160
/dev/ttyS3, UART: unknown, Port: 0x, IRQ: 0
/dev/ttyS4, UART: 8250, Port: 0x, IRQ: 161
/dev/ttyS5, UART: unknown, Port: 0x, IRQ: 0



I'm not sure why the serial systemd startup is getting stuck, and I tried 
doing a cursory look at journalctl on the next bootup (after commenting the 
UART overlay lines in uEnv.txt) to see if the systemd history persisted 
what may have happened, but I didn't see that.

Right now, I have some guesses at what may be going on: 

1)Since UART1 is already enabled, there was a resource contention when the 
UART1 u-boot overlay was loaded.
2)When u-boot attempted to load the UART3 overlay, there may have been a 
resource contention between something existing in the active device tree 
and the DTBO for UART3.

??Do you get the same kind of error messages with u-boot overlays when 
there's a device tree resource contention that you get with the cape 
manager and kernel overlays?? 


I also tried commenting these back in,  in uEnv.txt, but this didn't make 
systemd happy.


disable_uboot_overlay_emmc=1
#disable_uboot_overlay_video=1
#disable_uboot_overlay_audio=1
#disable_uboot_overlay_wireless=1
#disable_uboot_overlay_adc=1


I also tried renaming /boot/initrd.img-4.x to back.initrd.img-4.x per the 
thread which was posted today, but apparently that wasn't the issue..

***
image Version information
***

This is the debian 8.9 console image which downloaded a couple of weeks ago.

U-Boot SPL 2017.09-3-g11d92ba68a (Sep 21 2017 - 10:40:17)
Trying to boot from MMC2


U-Boot 2017.09-3-g11d92ba68a (Sep 21 2017 - 10:40:17 -0500), Build: 
jenkins-github_Bootloader-Builder-602

CPU  : AM335X-GP rev 2.1


debian@beaglebone:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2017-10-02

debian@beaglebone:~$ uname -r
4.4.89-ti-r130




Thanks a lot for wading through all of this

Regards,

Jeff



On Wednesday, September 6, 2017 at 12:11:03 PM UTC-5, 
daniel.di...@gmail.com wrote:
>
> Thanks Robert, you saved my day.
> I lost a couple of days with UART not working after upgrading to Debian 9.
> Finally after having a look at the posts in the mailing list I found this 
> and figured out 'cape_enable=bone_capemgr.enable_partno=BB-UART1' is not 
> enough anymore.
> It is perhaps worthed to include an entry in the wiki 
>  
> with specific information on this change and how to enable the UART, as not 
> all of us who work with overlays have a full understanding on how they work 
> and interact with uboot.
>
> Thanks a log again! :)
>
> El dilluns, 17 juliol de 2017 20:01:24 UTC+2, RobertCNelson va escriure:
>>
>> On Mon, Jul 17, 2017 at 12:18 PM, Hồng Quân Nguyễn 
>>  wrote: 
>> > I installed Ubuntu 16.04 to my BeagleBone Black and tried to enable 
>> UART1, 
>> > but it seems to not works. 
>> > 
>> > Content of /etc/default/capemgr: 
>> > 
>> > # Default settings for capemgr. This file is sourced by /bin/sh from 
>> > # /etc/init.d/capemgr.sh 
>> > 
>> > # Options to pass to capemgr 
>> > CAPE=BB-UART1,BB-PWM1 
>> > 
>> > 
>> > 
>> > Content of /sys/devices/platform/bone_capemgr/slots: 
>> > 
>> >  0: ---l--  -1 
>> >  1: --  -1 
>> >  2: ---l--  -1 
>> >  3: ---l--  -1 
>> >  4: --O---  -1 
>> > 
>> > 
>> > 
>> > Log related to BB-UART1 cape: 
>> > 
>> > $ journalctl 
>> > Jul 17 16:15:00 beaglebone-glass sh[612]: generic-board-startup: 
>> > [model=TI_AM335x_BeagleBone_Black] 
>> > Jul 17 16:15:00 beaglebone-glass sh[612]: generic-board-startup: 
>> [startup 
>> > script=/opt/scripts/boot/am335x_evm.sh] 
>> > Jul 17 16:15:00 beaglebone-glass kernel: bone_capemgr bone_capemgr: 
>> > part_number 'BB-UART1', version 'N/A' 
>> > Jul 17 16:15:00 beaglebone-glass kernel: bone_capemgr bone_capemgr: 
>> slot #4: 
>> > override 
>> > Jul 17 16:15:00 beaglebone-glass

Re: [beagleboard] Newer BBB fails to enable eMMC with legacy 3.8 SD image

2017-10-17 Thread Gary Simmons 
Thank you! Patched our custom kernel successfully with those patches. For
some reason I could not for the life of me track down what had changed.

On Fri, Oct 13, 2017 at 8:32 PM, Robert Nelson 
wrote:

> On Fri, Oct 13, 2017 at 3:00 PM,   wrote:
> > I have an older BBB that is flashing just fine from my SD (3.8 kernel
> img).
> > When I put this same SD into a newer BBB it fails to flash because
> mmcblk1
> > doesn't exist. So I disabled the emmc flash script at the end of
> uEnv.txt,
> > and did an lsblk. Sure enough there is no emmc enabled, or at least
> mmcblk1
> > is not seen/mounted.
> >
> > The SD card is unchanged from one device to another, and the only thing I
> > can see that's different is the newer one seems to be running U-Boot
> > 2016.11-rc3-2-g73df7f7, as apposed to the older one running U-Boot
> > 2015.01.
> >
> > If I grab a newer image (4.4) and put it on the SD, it works fine. The
> issue
> > is, I need to keep 3.8 for the time being, and I need it to properly
> enable
> > the emmc.
> >
> > Anyone run into this type of issue? Any advice would be amazing! Thank
> you.
>
> This was fixed in 3.8.13-bone80, which is the "first" 3.8.13 kernel to
> support eMMC5.1..
>
> It's not any issue in any other kernel branches.
>
> If you "MUST" have a specific 3.8.13 version follow these directions:
>
> https://gist.github.com/RobertCNelson/39faf80ddc9fcefae74dce2c6ca2eb45
>
> and rebuild it yourself.. ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>



-- 
*Sincerely,*
*Gary Simmons*

-- 
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/CAG5gR-KYTVPwD-mNuNq82s%2BmrKbYg4%2BPcH2oLGNFkruejyPS9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: ENC28J60 Click on PocketBeagle

2017-10-17 Thread Steven Keller 
I have been running my PocketBeagle with the ENC28 for over a week with no 
apparent issues.  I have it sending/receiving data to a cloud-based MQTT 
server using node red.  It sends a packet of data every 250ms and measures 
the time to get the data back.  Average response time is about 30ms.

The device is just sitting on my desk and connecting through my home 
network to my Comcast cable internet.  I have not tested any recovery from 
dropped connections, power fails, etc.



On Friday, October 6, 2017 at 1:36:14 AM UTC-5, Steven Keller wrote:
>
> I got the ENC28J60 Click module functioning fairly quickly but I wanted to 
> share what I needed to do.  Hopefully, it will help the next person who 
> goes down this road.
>
> I used these headers from Digi-Key: SAM1204-18-ND (
> https://www.digikey.com/product-detail/en/samtec-inc/SSQ-118-03-T-D/SAM1204-18-ND/842
> )
>
> Ethernet Click Module: 
> https://www.digikey.com/product-detail/en/mikroelektronika/MIKROE-971/1471-1320-ND/4495684
>  
> 
> https://shop.mikroe.com/eth-click
>
>
> I am using Debian 9.1 2017-09-21
>
> I had to update the bb-cape-overlays by using the following command.  (In 
> order for this to work you need to have an internet connection through the 
> USB port.  Go here for more info:
>  
> http://ofitselfso.com/BeagleNotes/HowToConnectBeagleboneBlackToTheInternetViaUSB.php
>  
> 
>   
> )
>
> sudo apt update ; sudo apt install bb-cape-overlays
>
> More info on mikroBus Click boards support can be found here: 
> https://github.com/beagleboard/pocketbeagle/wiki/mikroBus%E2%84%A2-Click-Boards
>
> I edited /boot/uEnv.txt to the following:
>
>
> ###Overide capes with eeprom
> uboot_overlay_addr0=/lib/firmware/PB-SPI0-ETH-CLICK.dtbo
> #uboot_overlay_addr1=/lib/firmware/.dtbo
> #uboot_overlay_addr2=/lib/firmware/.dtbo
> #uboot_overlay_addr3=/lib/firmware/.dtbo
>
> After reboot, it "just worked"!
>
> My Download and Upload speeds from speedtest.net were about 2.7Mbit/sec.  
>  Not a speed demon but fast enough for IoT work.
>
>
> Next step is to get a NimbeLink cellular modem working.
>
>
>
> 
>
>
> 
>
>
> 
>
>
>

-- 
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/db383a03-b14b-4ebc-8be6-30ae56db2f3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Boot is extremely slow/hangs

2017-10-17 Thread Robert Nelson 
On Tue, Oct 17, 2017 at 9:45 AM, Robert Nelson  wrote:
> On Tue, Oct 17, 2017 at 9:11 AM, Robert Nelson  
> wrote:
>> Hi Alexander,
>>
>> On Tue, Oct 17, 2017 at 7:53 AM, Alexander Rössler
>>  wrote:
>>> I found a workaround for the problem.
>>>
>>> The problems seems to be related to the images I built with the
>>> setup_sdcard script. I used the Debian Stretch console image builder 9.2
>>> with the following command:
>>>
 ./setup_sdcard.sh --dtb beaglebone --enable-cape-universal
 --enable-uboot-cape-overlays --boot_label SandyBox --enable-systemd
 --hostname sandybox --img-4gb test.img
>>>
>>>
>>> With the prebuilt image, everything works as expected. For me this
>>> solution is okay.
>>>
>>> My best guess is that it has to do with the boot_label, but I have no clue
>>> why it should only cause trouble with the RT kernels.
>>
>> It also could be the "--enable-systemd" that was only for the old
>> "wheezy", since jessie systemd has been the default and the flag my
>> change something else..
>>
>> if [ "x${enable_systemd}" = "xenabled" ] ; then
>>cmdline="${cmdline} init=/lib/systemd/systemd"
>> fi
>
> Nope, that didn't make a difference:
>
> debian@sandybox:~$ uname -r
> 4.9.56-bone-rt-r7
>
> debian@sandybox:~$ cat /proc/cmdline
> console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
> net.ifnames=0 quiet init=/lib/systemd/systemd cape_universal=enable
>
>
> [4.573940] ALSA device list:
> [4.573948]   #0: TI BeagleBone Black
> [4.575942] Freeing unused kernel memory: 1024K
> [   37.414498] EXT4-fs (mmcblk0p1): mounted filesystem with ordered
> data mode. Opts: (null)
> [   37.991016] ip_tables: (C) 2000-2006 Netfilter Core Team
>
> debian@sandybox:~$ cat /proc/cmdline
> console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
> root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
> net.ifnames=0 quiet cape_universal=enable
>
> [4.573685] ALSA device list:
> [4.573870]   #0: TI BeagleBone Black
> [4.575851] Freeing unused kernel memory: 1024K
> [   34.504317] EXT4-fs (mmcblk0p1): mounted filesystem with ordered
> data mode. Opts: (null)
> [   35.085202] ip_tables: (C) 2000-2006 Netfilter Core Team

Bingo, it's the initrd.img..  This is only really needed for 3.8.13,
"kernel overlays" (which are now, not recommended)..

[4.133706] PM: Hibernation image not present or could not be loaded.
[4.133987] ALSA device list:
[4.133997]   #0: TI BeagleBone Black
[4.147398] EXT4-fs (mmcblk0p1): mounted filesystem with ordered
data mode. Opts: (null)
[4.147467] VFS: Mounted root (ext4 filesystem) readonly on device 179:1.

So double check:

cat /proc/cmdline

that's using, root=/dev/mmcblk*

and that /etc/fstab

has "/dev/mmcblk*"

(aka no UUID)

Then your safe to do:

sudo rm /boot/initrd.img-4.*

I'll keep testing, as something in the initrd is blocking the RT kernel..

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/CAOCHtYgycLgTowo6cD3FnDAnwtKLGOVpBGZGv%2BN-2%2BcM818OqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Boot is extremely slow/hangs

2017-10-17 Thread Robert Nelson 
On Tue, Oct 17, 2017 at 9:11 AM, Robert Nelson  wrote:
> Hi Alexander,
>
> On Tue, Oct 17, 2017 at 7:53 AM, Alexander Rössler
>  wrote:
>> I found a workaround for the problem.
>>
>> The problems seems to be related to the images I built with the
>> setup_sdcard script. I used the Debian Stretch console image builder 9.2
>> with the following command:
>>
>>> ./setup_sdcard.sh --dtb beaglebone --enable-cape-universal
>>> --enable-uboot-cape-overlays --boot_label SandyBox --enable-systemd
>>> --hostname sandybox --img-4gb test.img
>>
>>
>> With the prebuilt image, everything works as expected. For me this
>> solution is okay.
>>
>> My best guess is that it has to do with the boot_label, but I have no clue
>> why it should only cause trouble with the RT kernels.
>
> It also could be the "--enable-systemd" that was only for the old
> "wheezy", since jessie systemd has been the default and the flag my
> change something else..
>
> if [ "x${enable_systemd}" = "xenabled" ] ; then
>cmdline="${cmdline} init=/lib/systemd/systemd"
> fi

Nope, that didn't make a difference:

debian@sandybox:~$ uname -r
4.9.56-bone-rt-r7

debian@sandybox:~$ cat /proc/cmdline
console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet init=/lib/systemd/systemd cape_universal=enable


[4.573940] ALSA device list:
[4.573948]   #0: TI BeagleBone Black
[4.575942] Freeing unused kernel memory: 1024K
[   37.414498] EXT4-fs (mmcblk0p1): mounted filesystem with ordered
data mode. Opts: (null)
[   37.991016] ip_tables: (C) 2000-2006 Netfilter Core Team

debian@sandybox:~$ cat /proc/cmdline
console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet cape_universal=enable

[4.573685] ALSA device list:
[4.573870]   #0: TI BeagleBone Black
[4.575851] Freeing unused kernel memory: 1024K
[   34.504317] EXT4-fs (mmcblk0p1): mounted filesystem with ordered
data mode. Opts: (null)
[   35.085202] ip_tables: (C) 2000-2006 Netfilter Core Team

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/CAOCHtYhgoRHZaMnybSPkurCx86w6d375NNiZc%3DDQqPXRJCLxeA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Boot is extremely slow/hangs

2017-10-17 Thread Robert Nelson 
Hi Alexander,

On Tue, Oct 17, 2017 at 7:53 AM, Alexander Rössler
 wrote:
> I found a workaround for the problem.
>
> The problems seems to be related to the images I built with the
> setup_sdcard script. I used the Debian Stretch console image builder 9.2
> with the following command:
>
>> ./setup_sdcard.sh --dtb beaglebone --enable-cape-universal
>> --enable-uboot-cape-overlays --boot_label SandyBox --enable-systemd
>> --hostname sandybox --img-4gb test.img
>
>
> With the prebuilt image, everything works as expected. For me this
> solution is okay.
>
> My best guess is that it has to do with the boot_label, but I have no clue
> why it should only cause trouble with the RT kernels.

It also could be the "--enable-systemd" that was only for the old
"wheezy", since jessie systemd has been the default and the flag my
change something else..

if [ "x${enable_systemd}" = "xenabled" ] ; then
   cmdline="${cmdline} init=/lib/systemd/systemd"
fi

i'll test that locally too...

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/CAOCHtYg8opuHcwBu3r_WGQMebQ%3DwaXOLPS3qE9LSL%2Bx35y19jg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Boot is extremely slow/hangs

2017-10-17 Thread Alexander Rössler 
I found a workaround for the problem.

The problems seems to be related to the images I built with the
setup_sdcard script. I used the Debian Stretch console image builder 9.2
with the following command:

./setup_sdcard.sh --dtb beaglebone --enable-cape-universal
> --enable-uboot-cape-overlays --boot_label SandyBox --enable-systemd
> --hostname sandybox --img-4gb test.img


With the prebuilt image, everything works as expected. For me this
solution is okay.

My best guess is that it has to do with the boot_label, but I have no clue 
why it should only cause trouble with the RT kernels.

Am Mittwoch, 13. September 2017 11:52:21 UTC+2 schrieb Alexander Rössler:
>
> After disabling the video, audio and wireless overlays in my uEnv.txt the 
> boot starts to get extremely slow.
>
> The serial console output looks as follows:
>
> [11:41:14:515] ␍␊
>
> [11:41:14:519] U-Boot SPL 2017.07-2-g61c3ee0fb5 (Jul 19 2017 - 17:02:
> 08)␍␊
>
> [11:41:14:576] Trying to boot from MMC2␍␊
>
> [11:41:14:678] ␍␊
>
> [11:41:14:681] ␍␊
>
> [11:41:14:681] U-Boot 2017.07-2-g61c3ee0fb5 (Jul 19 2017 - 17:02:08 -
> 0500), Build: jenkins-github_Bootloader-Builder-591␍␊
>
> [11:41:14:690] ␍␊
>
> [11:41:14:690] CPU  : AM335X-GP rev 2.1␍␊
>
> [11:41:14:692] I2C:   ready␍␊
>
> [11:41:14:744] DRAM:  512 MiB␍␊
>
> [11:41:14:793] No match for driver 'omap_hsmmc'␍␊
>
> [11:41:14:798] No match for driver 'omap_hsmmc'␍␊
>
> [11:41:14:801] Some drivers were not found␍␊
>
> [11:41:14:803] Reset Source: Power-on reset has occurred.␍␊
>
> [11:41:14:808] MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1␍␊
>
> [11:41:14:812] Using default environment␍␊
>
> [11:41:14:812] ␍␊
>
> [11:41:14:874] Board: BeagleBone Black␍␊
>
> [11:41:14:878]  not set. Validating first E-fuse MAC␍␊
>
> [11:41:14:934] BeagleBone Black:␍␊
>
> [11:41:14:938] BeagleBone: cape eeprom: i2c_probe: 0x54:␍␊
>
> [11:41:14:943] BeagleBone: cape eeprom: i2c_probe: 0x55:␍␊
>
> [11:41:14:947] BeagleBone: cape eeprom: i2c_probe: 0x56:␍␊
>
> [11:41:14:952] BeagleBone: cape eeprom: i2c_probe: 0x57:␍␊
>
> [11:41:14:955] Net:   eth0: MII MODE␍␊
>
> [11:41:14:961] cpsw␍␊
>
> [11:41:14:964] Press SPACE to abort autoboot in 2 seconds␍␊
>
> [11:41:16:964] board_name=[A335BNLT] ...␍␊
>
> [11:41:16:970] board_rev=[00C0] ...␍␊
>
> [11:41:17:309] switch to partitions #0, OK␍␊
>
> [11:41:17:309] mmc0 is current device␍␊
>
> [11:41:17:385] SD/MMC found on device 0␍␊
>
> [11:41:17:385] ** Bad device 0:2 0x8200 **␍␊
>
> [11:41:17:385] ** Bad device 0:2 0x8200 **␍␊
>
> [11:41:17:454] switch to partitions #0, OK␍␊
>
> [11:41:17:457] mmc0 is current device␍␊
>
> [11:41:17:548] Scanning mmc 0:1...␍␊
>
> [11:41:17:960] gpio: pin 56 (gpio 56) value is 0␍␊
>
> [11:41:17:965] gpio: pin 55 (gpio 55) value is 0␍␊
>
> [11:41:17:966] gpio: pin 54 (gpio 54) value is 0␍␊
>
> [11:41:17:971] gpio: pin 53 (gpio 53) value is 1␍␊
>
> [11:41:18:042] switch to partitions #0, OK␍␊
>
> [11:41:18:046] mmc0 is current device␍␊
>
> [11:41:18:115] gpio: pin 54 (gpio 54) value is 1␍␊
>
> [11:41:18:333] Checking for: /uEnv.txt ...␍␊
>
> [11:41:18:369] Checking for: /boot.scr ...␍␊
>
> [11:41:18:404] Checking for: /boot/boot.scr ...␍␊
>
> [11:41:18:464] Checking for: /boot/uEnv.txt ...␍␊
>
> [11:41:18:520] gpio: pin 55 (gpio 55) value is 1␍␊
>
> [11:41:18:576] 2141 bytes read in 49 ms (42 KiB/s)␍␊
>
> [11:41:18:581] Loaded environment from /boot/uEnv.txt␍␊
>
> [11:41:18:586] Checking if uname_r is set in /boot/uEnv.txt...␍␊
>
> [11:41:18:590] gpio: pin 56 (gpio 56) value is 1␍␊
>
> [11:41:18:594] Running uname_boot ...␍␊
>
> [11:41:18:653] loading /boot/vmlinuz-4.4.87-ti-rt-r121 ...␍␊
>
> [11:41:19:263] 8725520 bytes read in 602 ms (13.8 MiB/s)␍␊
>
> [11:41:19:269] uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] 
> ...␍␊
>
> [11:41:19:360] uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb 
> ...␍␊
>
> [11:41:19:451] loading /boot/dtbs/4.4.87-ti-rt-r121/am335x-boneblack-uboot
> .dtb ...␍␊
>
> [11:41:19:547] 53128 bytes read in 86 ms (602.5 KiB/s)␍␊
>
> [11:41:19:553] uboot_overlays: [fdt_buffer=0x6] ...␍␊
>
> [11:41:19:800] uboot_overlays: loading /lib/firmware/AM335X-20-00A0.dtbo 
> ...␍␊
>
> [11:41:20:048] 378 bytes read in 238 ms (1000 Bytes/s)␍␊
>
> [11:41:20:289] uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-
> 00A0.dtbo ...␍␊
>
> [11:41:20:525] 1105 bytes read in 226 ms (3.9 KiB/s)␍␊
>
> [11:41:20:536] uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-
> TDA998x-00A0.dtbo] disabled by /boot/uEnv.txt [disable_uboot_overlay_video
> =1]...␍␊
>
> [11:41:20:611] uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo 
> ...␍␊
>
> [11:41:20:679] 695 bytes read in 58 ms (10.7 KiB/s)␍␊
>
> [11:41:20:962] uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-
> 00A0.dtbo ...␍␊
>
> [11:41:21:241] 853 bytes read in 269 ms (2.9 KiB/s)␍␊
>
> [11:41:21:294] uboot_overlays: loading /lib/firmware/univ-bbb-Exx-
> 00A0.dtbo ...␍␊
>
> [11:41:21:347] 92817 bytes read in 43 ms (2.1 MiB/s)␍␊
>
>

[beagleboard] cannot SSH to BBB via LINUX terminal

2017-10-17 Thread Simas Paulius 
I'm trying to SSH to my BBB board via LINUX (UBUNTU 17.04 distro) terminal 
using a command *ssh -v 192.168.7.2 *with no luck.
I always get the same error:


OpenSSH_7.4p1 Ubuntu-10, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to 192.168.7.2 [192.168.7.2] port 22.
debug1: Connection established.
debug1: identity file /home/simon/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/simon/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4p1 Ubuntu-10
ssh_exchange_identification: read: Connection reset by peer

please give me some advice on this issue.
Thank you in advance! :)

-- 
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/1a9ed1f2-817b-49c7-ae46-0e022d2c647d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.