[beagleboard] When was connmanctl introduced?

[bryan . miller]

Can someone please point me to the history of connmanctl and when it was 
introduced for Debian on BBB?   All of the legacy documentation circa 2015 
shows a simple entry in /etc/network/interfaces but clearly connmanctl is 
the way to go now.

Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/02d4f55a-544b-44c7-aab6-9a4e9fdce21e%40googlegroups.com.

Re: [beagleboard] When was connmanctl introduced?

[Robert Nelson]

On Thu, Apr 23, 2020 at 10:21 PM  wrote:
>
> Can someone please point me to the history of connmanctl and when it was 
> introduced for Debian on BBB?   All of the legacy documentation circa 2015 
> shows a simple entry in /etc/network/interfaces but clearly connmanctl is the 
> way to go now.
>
> Thanks!

The original BeagleBoard.org Debian Wheezy release around 2014 used
wicd for wifi configuration, shortly there after around 2015 we
started transitioning to connman.

I believe wicd-gtk was no longer maintained at that time and we needed
to find a new solution..

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/CAOCHtYjh6_3nRc%2B%2BLxZJorqq4ZjMigrEJLK3gwt%3DWFKvpmzS8g%40mail.gmail.com.

Re: [beagleboard] Network setup taken over by something

[maxmike]

Using BeagleBoard.org Debian Buster IoT Image 2020-04-06

On Thursday, April 23, 2020 at 4:26:03 PM UTC-7, maxmike wrote:
>
> Wow - it looks like the entire cape-universal software is now broken:
>
>
> One used to be able to do :  config-pin p8.12 out
> and then test it by issuing config-pin p8.12 hi or lo
>
> This is no longer possible, now the pin can only be set as pruout and 
> hi/lo don't work anymore. 
>

-- 
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/df463059-f2b0-403f-b542-ff60c6ae3bb4%40googlegroups.com.

[beagleboard] Converting GPIO pins to MMC mode (BeagleBone Black)

[GJ]

I'm using a BeagleBone Black (kernel 4.14.108-ti-r131), and I was able to 
successfully configure the MMC0 Dat0 and Dat1 pins to GPIO mode.

In am335x-bone-common.dtsi, I just modified the 2 entries related 
to pinmux_mmc1_pins and changed them to MUX_MODE_7:

AM33XX_PADCONF(AM335X_PIN_MMC0_DAT0, PIN_OUTPUT_PULLUP, MUX_MODE7)
AM33XX_PADCONF(AM335X_PIN_MMC0_DAT1, PIN_OUTPUT_PULLUP, MUX_MODE7)

I then recompiled the .dtb files, installed them, rebooted my BeagleBone, 
and I was able to toggle those 2 pins as GPIO through sysfs.

Now i want to change those 2 pins back to MMC0 mode.  I wanted to be able 
to do that on the fly, but I was told that I wouldn't be able to do that 
and that I'd have to modify the device tree.  Basically the note was that 
I'd have to go back to the .dtsi file and change those pins back to 
MUX_MODE0 (which makes the mmc0).  

Is there a way I can do that and modify the device tree without having to 
reboot the BeagleBone?  Could I just modify the .dtsi file, compile the 
appropriate .dtb file, and if possible, issue some command that would load 
the updated device tree without rebooting?

Thanks!

-- 


*Your privacy is important to us. That is why we have taken appropriate 
measures to ensure the data you provide to us is kept secure. To learn more 
about how we process your personal information, how we comply with 
applicable data protection laws, and care for the security and privacy of 
your personal data, please review our Privacy Policy. If you have any 
questions related to data protection and compliance with applicable laws, 
please contact us at our Security Operations Center at 1-800-674-4357.*

-- 
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/023451c4-04a7-40eb-83eb-c0b367dd95b0%40googlegroups.com.

Re: [beagleboard] Network setup taken over by something

[Robert Nelson]

On Thu, Apr 23, 2020 at 6:26 PM maxmike  wrote:
>>
>> Wow - it looks like the entire cape-universal software is now broken:
>
>
> One used to be able to do :  config-pin p8.12 out
> and then test it by issuing config-pin p8.12 hi or lo
>
> This is no longer possible, now the pin can only be set as pruout and hi/lo 
> don't work anymore.

I had no idea config-pin had a sub-option to also set the value and direction..

https://github.com/beagleboard/bb.org-overlays/blob/master/tools/beaglebone-universal-io/config-pin#L1077-L1109

https://github.com/beagleboard/bb.org-overlays/blob/master/tools/beaglebone-universal-io/config-pin#L1279-L1289

https://github.com/beagleboard/bb.org-overlays/blob/master/tools/beaglebone-universal-io/config-pin#L1396-L1413

Anywho, the current shipping config-pin would require:

config-pin P8.12 gpio
echo 1 > /sys/class/gpio/gpio44/value

But you probably don't want to do that..

sudo rm /usr/bin/config-pin
sudo cp -v /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin
/usr/bin/

So there, all fixed..

For comparison, the old script:

https://github.com/beagleboard/bb.org-overlays/blob/master/tools/beaglebone-universal-io/config-pin

It's replacment..

https://github.com/beagleboard/bb.org-overlays/blob/master/tools/pmunts_muntsos/config-pin.c

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiQtGKgOsei0a93Z%3DHVgZOD_J0QUSk9mA0XcaMsXskAfw%40mail.gmail.com.

Re: [beagleboard] Network setup taken over by something

[maxmike]

>
> Wow - it looks like the entire cape-universal software is now broken:


One used to be able to do :  config-pin p8.12 out
and then test it by issuing config-pin p8.12 hi or lo

This is no longer possible, now the pin can only be set as pruout and hi/lo 
don't work anymore. 

-- 
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/105f0d48-92a6-4bde-9839-2d2967755e4e%40googlegroups.com.

Re: [beagleboard] When was connmanctl introduced?

[Robert Nelson]

> Thank you Robert!  That is very helpful.   For my wired NIC connections 
> interfaces is dead simple.  I can see the advantage of connman for wifi.

Yeah, today for a wired connection, not using "connman" works fine.

But there was a time about 2-3 years ago..  That Debian/Ubuntu had a
really crappy ifupdown network setting, that forced you into a 2
minute wait (timeout) on bootup before the login prompt would become
available... Unless your ethernet port was connected, then login
appeared instantly..

Swapping from "auto eth0" to "allow-hotplug eth0" made zero difference
at the time.  I remember supporting 2 boards with one image back
then.. The original BeagleBoard (with no default ethernet) and the xM
with a usb-ethernet adapter..  It really sucked trying to support that
configuration, as we had to have "eth0" defined in
/etc/network/interfaces so the xM would have working ethernet.  Yet at
the same time hack up teh ifup scripts to remove the 2 minute timeout
so the non ethernet BeagleBoard, would still bootup quiclly to a login
prompt.

Once we swapped to connman, connman took care of those two cases pretty easily..

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/CAOCHtYgfXJqSxVx_SJviFTpEQUptKGnvrM1KbpEdzd7VsDWPfw%40mail.gmail.com.

RE: [beagleboard] When was connmanctl introduced?

[Bryan Miller]

-Original Message-
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Robert Nelson
Sent: Thursday, April 23, 2020 9:31 PM
To: Beagle Board
Subject: Re: [beagleboard] When was connmanctl introduced?

>On Thu, Apr 23, 2020 at 10:21 PM  wrote:
>>
>> Can someone please point me to the history of connmanctl and when it was 
>> introduced for Debian on BBB?   All of the legacy documentation circa 2015 
>> shows a simple entry in /etc/network/interfaces but clearly connmanctl is 
>> the way to go now.
>>
>> Thanks!
>
> The original BeagleBoard.org Debian Wheezy release around 2014 used
> wicd for wifi configuration, shortly there after around 2015 we
> started transitioning to connman.
>
> I believe wicd-gtk was no longer maintained at that time and we needed to 
> find a new solution..

Thank you Robert!  That is very helpful.   For my wired NIC connections 
interfaces is dead simple.  I can see the advantage of connman for wifi.

-Bryan

-- 
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/5ea26271.1c69fb81.36b1d.62f8%40mx.google.com.

Re: [beagleboard] Re: PocketBeagle Boot Time

[Paul Beam]

Robert,

I have been working with the LTS 4.14 ti branch.  Is 4.19 better?  To be 
honest, I don't remember the image I started with, but I started 6+ months 
ago.  I'm in a position where I can basically start fresh if there are 
advantages.  


On Thursday, April 23, 2020 at 11:37:10 AM UTC-4, RobertCNelson wrote:
>
> >   2.649s loadcpufreq.service 
> >707ms cpufrequtils.service 
>
> It's safe to disable cpufrequtils, by default it's already running at 
> 1Ghz out of u-boot and with Performance enabled 
> with the default kernel.. 
>
> It's more for legacy.. 
>
> debian@beaglebone:~$ systemd-analyze 
> Startup finished in 1.357s (kernel) + 27.030s (userspace) = 28.387s 
> graphical.target reached after 26.727s in userspace 
>
>
> 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/ce0b4dac-64ec-4aac-a405-f53f8867320a%40googlegroups.com.

[beagleboard] Re: requesting information on pcb files for beaglebone black and beaglebone ai

[Jason Kridner]

On Wed, Apr 22, 2020 at 10:35 AM Ramakrishna Bachimanchi 
wrote:

> Hello,
> my name is Rama Bachimanchi and I am an electrical engineer working at
> Jefferson Lab (non-profit research organization). I have come across the
> amazing work you guys are doing and was looking into possibly modifying one
> of your designs to replace an obsolete ioc we are using (it's a kontron
> pc/104 no longer in production). I was able to import the schematic into
> Altium, but not the pcb design files. I am getting an error when tried to
> view the files using the free allegro pcb viewer. Would it be possible to
> update the files and also upload the ascii file, so that we can import this
> into altium. We are planning to replace the expansion connectors with
> pc/104 connector. If we get to work and finish the design, we will most
> likely share it with you(not sure, if this is useful for the community).
> Please let me know
>


I'm not sure what ASCII file is needed. If I knew, I'd be happy to export
it.

For conversion to KiCAD, I created a cds2f text file:
https://github.com/beagleboard/beaglebone-ai/blob/master/HW/cds2f_BeagleBone-AI.txt

When the KiCAD version is available, you might find it easier to import
that into Altium:
https://www.altium.com/solution/kicad-pcb-design-software-free-download



>
> Thanks,
> Rama Bachimanchi
>
>

-- 
https://beagleboard.org/about - a 501c3 non-profit educating around open
hardware computing

-- 
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/CA%2BT6QP%3DCryDTk7QT1keBQ6-3HuJ5%3DW35nSacRYepa3MR6Ac9sg%40mail.gmail.com.

Re: [beagleboard] Re: PocketBeagle Boot Time

[Robert Nelson]

On Thu, Apr 23, 2020 at 11:32 AM Paul Beam  wrote:
>
> Robert,
>
> I have been working with the LTS 4.14 ti branch.  Is 4.19 better?  To be 
> honest, I don't remember the image I started with, but I started 6+ months 
> ago.  I'm in a position where I can basically start fresh if there are 
> advantages.

Doesn't really matter, for me 4.14.x-ti = stretch, v4.14.x+ is buster,
so if we grab this stretch console image:

https://elinux.org/Beagleboard:Latest-images-testing#Debian_9_.28Stretch.29_Console

Then on the PocketBeagle...

BeagleBoard.org Debian Stretch Console Image 2020-04-06

1st boot...

debian@beaglebone:~$ uname -r
4.14.108-ti-r131

debian@beaglebone:~$ systemd-analyze
Startup finished in 9.701s (kernel) + 44.498s (userspace) = 54.200s

2nd boot...

debian@beaglebone:~$ systemd-analyze
Startup finished in 9.691s (kernel) + 29.165s (userspace) = 38.856s

sudo systemctl disable systembb-wl18xx-bluetooth.service
sudo systemctl disable bb-wl18xx-wlan0.service
sudo systemctl disable wpa_supplicant.service

sudo apt remove cpufrequtils libcpufreq0 hostapd --purge

3rd boot...

debian@beaglebone:~$ systemd-analyze
Startup finished in 9.637s (kernel) + 28.614s (userspace) = 38.252s

sudo rm /boot/initrd.img-4.14.108-ti-r131

4th boot...

debian@beaglebone:~$ systemd-analyze
Startup finished in 1.117s (kernel) + 27.318s (userspace) = 28.436s

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/CAOCHtYjm7DcFZQ48eLEWqQNsS-eR%3DYJwTAR5Kg3_wfBch7od5A%40mail.gmail.com.

Re: [beagleboard] Re: Beaglebone AI UART access

[Jason Kridner]

Thanks for all your shared work.

The plan for the Fall release (based on GSoC work on-going this summer, if
approved, or this might be delayed) is to modify the base device trees and
set of overlays to provide at common set of overlays to load for Black/AI.
Then, symlinks would be provided that map to UARTs on specific header pins.

See https://elinux.org/Beagleboard:BeagleBone_cape_interface_spec for
work-in-progress.

On Wed, Apr 22, 2020 at 10:22 PM  wrote:

>
> I hope it is helpful for uart3  /dev/ttyS2 device tree implementation.
>
> Uart3 RX starts working after the mode update to
>
> PIN_INPUT_PULLUP | MUX_MODE1 // P9.22b uart3_rxd
>
> Mode is confirmed as the following:
>
>
> P9.22b   240 fast rx  up   1 uart 2 rxd   serial@4802 (uart3)
>
> pin 240 (PIN240) 4a0037c0 00060001 pinctrl-single ( instead of 0001)
>
>
>
> UART3 TX was working without any pull up or pull down.
>
> P9_21, MUX_MODE1 ) // P9.21 uart3_txd
>
> pin 241 (PIN241) 4a0037c4 0001 pinctrl-single
>
>
>
> To activate uart3, please add the following code into *.dts file and
> compile to *.dtb.
>
> Also please modify the am572*ai.dts file by deactivating the shared pins.
>
>
>  {
>
>  status = "okay";
>
>  pinctrl-names = "default";
>
>  pinctrl-0 = <_pins>;
>
> };
>
> _pmx_core {
>
>  uart3_pins: uart3 {
>
>   pinctrl-single,pins = <
>
>DRA7XX_CORE_IOPAD( P9_21, MUX_MODE1 ) // P9.21 uart3_txd
>
>DRA7XX_CORE_IOPAD( P9_22b, PIN_INPUT_PULLUP | MUX_MODE1) // P9.22b
> uart3_rxd
>
>DRA7XX_CORE_IOPAD( P9_22a, MUX_MODE15) // P9.22a driver_off //shared-pin
>
>   >;
>
>  };
>
>
>
> };
>
>
> --
> 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/c77fd7a6-4177-4a4c-9f20-cca67e254fb5%40googlegroups.com
> 
> .
>


-- 
https://beagleboard.org/about - a 501c3 non-profit educating around open
hardware computing

-- 
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/CA%2BT6QPm5OdC%3Dth0ByQ3DJ-Rq9ynfarN9MkhiDdd3eOh0_RrW0g%40mail.gmail.com.

Re: [beagleboard] BBB (Element14/Industrial) Fails to Boot off EMMC After Flash

[Robert Nelson]

On Thu, Apr 23, 2020 at 11:50 AM biggi_  wrote:
>
> Sorry for the book in advance, just want to make sure I outline all the steps 
> I did to try to get to the bottom of this. I picked up an Element14 
> Industrial Version of the BBB.  Trying to get Python 3.6 installed to find 
> out that it's not supported on the Debian 8.11 that was running.  Went to 
> Beaglebone images and downloaded "AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT 
> Flasher" and used Win32DiskImager to flash it to a microSD card.  I also 
> uncommented the 
> "#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh" at the bottom 
> of the uEnv.txt file.  Flash seemed to go fine, the LEDs went back and forth 
> then on one attempt, the LEDs were all flashing on and off at the same time.

ALL on and ALL off is an error condition, do you have usb serial
adapter to plug into J1?

https://elinux.org/Beagleboard:BeagleBone_Black_Serial

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/CAOCHtYhyauCJpsfT0BmtUcvKAco_JnbVAodnv4EkF_WcHD1gkw%40mail.gmail.com.

Re: [beagleboard] Re: PocketBeagle Boot Time

[Robert Nelson]

On Thu, Apr 23, 2020 at 10:29 AM Robert Nelson  wrote:
>
> On Thu, Apr 23, 2020 at 7:42 AM  wrote:
> >
> > I have done that, but I am perplexed with the results I posted – I think 
> > that was from a different unit as I have several in various states of 
> > development.  From what I have read, the usb gadget takes most of the 
> > userspace time.  On the one hand, I find it amazing that the startup 
> > scripts work for so many boards, but on the other hand I find their size 
> > and complexity daunting to tramps through and figure out.
>
> Hi Paul,
>
> What kernel are you using?
>
> Before our Spring 2020 release time, i had spent some time cleaning up
> the boot script (and the kernel..)
>
> Have you tried the newer Spring 2020 "console" image?
>
> https://elinux.org/Beagleboard:Latest-images-testing#Debian_10_.28Buster.29_Console
>
> Out of the box, (2nd boot, as the 1st boot generates the ssh keys..)
>
> debian@beaglebone:~$ uname -r
> 4.19.94-ti-r42
>
>
> debian@beaglebone:~$ systemd-analyze
> Startup finished in 7.686s (kernel) + 29.068s (userspace) = 36.755s
> graphical.target reached after 28.776s in userspace
>
> debian@beaglebone:~$ systemd-analyze blame
>  21.211s generic-board-startup.service
>  19.429s dev-mmcblk0p1.device
>   3.214s systemd-udev-trigger.service
>   2.649s loadcpufreq.service
>   1.970s networking.service
>   1.466s ssh.service
>   1.387s systemd-logind.service
>   1.318s systemd-journald.service
>   1.261s systemd-timesyncd.service
>   1.135s connman.service
>   1.077s bb-wl18xx-wlan0.service
>835ms dnsmasq.service
>707ms cpufrequtils.service
>695ms wpa_supplicant.service
>644ms kmod-static-nodes.service
>642ms systemd-fsck-root.service
>626ms systemd-user-sessions.service
>611ms sys-kernel-debug.mount
>604ms systemd-update-utmp.service
>541ms systemd-remount-fs.service
>518ms user@1000.service
>478ms systemd-tmpfiles-setup.service
>457ms systemd-sysctl.service
>448ms rsyslog.service
>447ms systemd-modules-load.service
>411ms systemd-journal-flush.service
>389ms dev-mqueue.mount
>387ms systemd-sysusers.service
>381ms sys-fs-fuse-connections.mount
>361ms systemd-udevd.service
>337ms systemd-random-seed.service
>273ms sys-kernel-config.mount
>234ms systemd-tmpfiles-setup-dev.service
>223ms systemd-update-utmp-runlevel.service
>151ms ifupdown-pre.service
>125ms user-runtime-dir@1000.service
> 94ms bb-wl18xx-bluetooth.service
>
> Looks like i forgot to disable*  wl18xx on boot-up on the PocketBeagle..
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L892-L911
>
> debian@beaglebone:~$ sudo systemctl disable bb-wl18xx-bluetooth.service
> debian@beaglebone:~$ sudo systemctl disable bb-wl18xx-wlan0.service
>
> debian@beaglebone:~$ systemd-analyze
> Startup finished in 7.669s (kernel) + 28.640s (userspace) = 36.310s
> graphical.target reached after 28.363s in userspace
>
> debian@beaglebone:~$ sudo rm /boot/initrd.img-4.19.94-ti-r42
>
> debian@beaglebone:~$ systemd-analyze
> Startup finished in 1.355s (kernel) + 27.831s (userspace) = 29.187s
> graphical.target reached after 27.564s in userspace
>
> debian@beaglebone:~$ systemd-analyze blame
>  19.893s generic-board-startup.service
>  19.072s dev-mmcblk0p1.device
>   3.193s systemd-udev-trigger.service
>   2.905s loadcpufreq.service
>   1.898s networking.service
>   1.427s ssh.service
>   1.314s systemd-timesyncd.service
>   1.159s systemd-journald.service
>   1.043s systemd-logind.service
>929ms connman.service
>878ms cpufrequtils.service
>864ms dnsmasq.service
>830ms systemd-fsck-root.service
>699ms rsyslog.service
>608ms wpa_supplicant.service
>578ms systemd-user-sessions.service
>557ms sys-kernel-debug.mount
>506ms systemd-modules-load.service
>506ms user@1000.service
>467ms systemd-tmpfiles-setup.service
>465ms systemd-update-utmp.service
>452ms kmod-static-nodes.service
>399ms systemd-sysusers.service
>393ms systemd-journal-flush.service
>386ms systemd-sysctl.service
>345ms systemd-udevd.service
>341ms sys-kernel-config.mount
>322ms systemd-random-seed.service
>296ms dev-mqueue.mount
>284ms sys-fs-fuse-connections.mount
>258ms systemd-remount-fs.service
>203ms systemd-tmpfiles-setup-dev.service
>194ms systemd-update-utmp-runlevel.service
>

Re: [beagleboard] Re: PocketBeagle Boot Time

[Robert Nelson]

On Thu, Apr 23, 2020 at 7:42 AM  wrote:
>
> I have done that, but I am perplexed with the results I posted – I think that 
> was from a different unit as I have several in various states of development. 
>  From what I have read, the usb gadget takes most of the userspace time.  On 
> the one hand, I find it amazing that the startup scripts work for so many 
> boards, but on the other hand I find their size and complexity daunting to 
> tramps through and figure out.

Hi Paul,

What kernel are you using?

Before our Spring 2020 release time, i had spent some time cleaning up
the boot script (and the kernel..)

Have you tried the newer Spring 2020 "console" image?

https://elinux.org/Beagleboard:Latest-images-testing#Debian_10_.28Buster.29_Console

Out of the box, (2nd boot, as the 1st boot generates the ssh keys..)

debian@beaglebone:~$ uname -r
4.19.94-ti-r42


debian@beaglebone:~$ systemd-analyze
Startup finished in 7.686s (kernel) + 29.068s (userspace) = 36.755s
graphical.target reached after 28.776s in userspace

debian@beaglebone:~$ systemd-analyze blame
 21.211s generic-board-startup.service
 19.429s dev-mmcblk0p1.device
  3.214s systemd-udev-trigger.service
  2.649s loadcpufreq.service
  1.970s networking.service
  1.466s ssh.service
  1.387s systemd-logind.service
  1.318s systemd-journald.service
  1.261s systemd-timesyncd.service
  1.135s connman.service
  1.077s bb-wl18xx-wlan0.service
   835ms dnsmasq.service
   707ms cpufrequtils.service
   695ms wpa_supplicant.service
   644ms kmod-static-nodes.service
   642ms systemd-fsck-root.service
   626ms systemd-user-sessions.service
   611ms sys-kernel-debug.mount
   604ms systemd-update-utmp.service
   541ms systemd-remount-fs.service
   518ms user@1000.service
   478ms systemd-tmpfiles-setup.service
   457ms systemd-sysctl.service
   448ms rsyslog.service
   447ms systemd-modules-load.service
   411ms systemd-journal-flush.service
   389ms dev-mqueue.mount
   387ms systemd-sysusers.service
   381ms sys-fs-fuse-connections.mount
   361ms systemd-udevd.service
   337ms systemd-random-seed.service
   273ms sys-kernel-config.mount
   234ms systemd-tmpfiles-setup-dev.service
   223ms systemd-update-utmp-runlevel.service
   151ms ifupdown-pre.service
   125ms user-runtime-dir@1000.service
94ms bb-wl18xx-bluetooth.service

Looks like i forgot to disable*  wl18xx on boot-up on the PocketBeagle..

https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L892-L911

debian@beaglebone:~$ sudo systemctl disable bb-wl18xx-bluetooth.service
debian@beaglebone:~$ sudo systemctl disable bb-wl18xx-wlan0.service

debian@beaglebone:~$ systemd-analyze
Startup finished in 7.669s (kernel) + 28.640s (userspace) = 36.310s
graphical.target reached after 28.363s in userspace

debian@beaglebone:~$ sudo rm /boot/initrd.img-4.19.94-ti-r42

debian@beaglebone:~$ systemd-analyze
Startup finished in 1.355s (kernel) + 27.831s (userspace) = 29.187s
graphical.target reached after 27.564s in userspace

debian@beaglebone:~$ systemd-analyze blame
 19.893s generic-board-startup.service
 19.072s dev-mmcblk0p1.device
  3.193s systemd-udev-trigger.service
  2.905s loadcpufreq.service
  1.898s networking.service
  1.427s ssh.service
  1.314s systemd-timesyncd.service
  1.159s systemd-journald.service
  1.043s systemd-logind.service
   929ms connman.service
   878ms cpufrequtils.service
   864ms dnsmasq.service
   830ms systemd-fsck-root.service
   699ms rsyslog.service
   608ms wpa_supplicant.service
   578ms systemd-user-sessions.service
   557ms sys-kernel-debug.mount
   506ms systemd-modules-load.service
   506ms user@1000.service
   467ms systemd-tmpfiles-setup.service
   465ms systemd-update-utmp.service
   452ms kmod-static-nodes.service
   399ms systemd-sysusers.service
   393ms systemd-journal-flush.service
   386ms systemd-sysctl.service
   345ms systemd-udevd.service
   341ms sys-kernel-config.mount
   322ms systemd-random-seed.service
   296ms dev-mqueue.mount
   284ms sys-fs-fuse-connections.mount
   258ms systemd-remount-fs.service
   203ms systemd-tmpfiles-setup-dev.service
   194ms systemd-update-utmp-runlevel.service
   152ms user-runtime-dir@1000.service
   113ms ifupdown-pre.service


There under 30 seconds, with more room to disable things. ;)

If you kill "generic-board-startup.service" make sure you have a
usb-serial adapter plugged into the usart on the PocketBeagle's uart
pins, as 

Re: [beagleboard] Re: PocketBeagle Boot Time

[Robert Nelson]

>   2.649s loadcpufreq.service
>707ms cpufrequtils.service

It's safe to disable cpufrequtils, by default it's already running at
1Ghz out of u-boot and with Performance enabled
with the default kernel..

It's more for legacy..

debian@beaglebone:~$ systemd-analyze
Startup finished in 1.357s (kernel) + 27.030s (userspace) = 28.387s
graphical.target reached after 26.727s in userspace


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/CAOCHtYjdcZHxY%3D_0kOg%2BnnX-oux_wHQVqDaf0cciFmfzEruZiA%40mail.gmail.com.

[beagleboard] BBB (Element14/Industrial) Fails to Boot off EMMC After Flash

[biggi_]

Sorry for the book in advance, just want to make sure I outline all the 
steps I did to try to get to the bottom of this. I picked up an Element14 
Industrial Version of the BBB.  Trying to get Python 3.6 installed to find 
out that it's not supported on the Debian 8.11 that was running.  Went to 
Beaglebone images and downloaded "AM3358 Debian 10.3 2020-04-06 4GB eMMC 
IoT Flasher" and used Win32DiskImager to flash it to a microSD card.  I 
also uncommented the 
"#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh" at the 
bottom of the uEnv.txt file.  Flash seemed to go fine, the LEDs went back 
and forth then on one attempt, the LEDs were all flashing on and off at the 
same time.  I unplugged here thinking it was done, but apparently it 
wasn't.  Went back and managed to flash again (saw lights going up and down 
in order/etc) then waited for it to totally turn off.  After all LEDs were 
off I unplugged the BBB and now the heartbeat flashes a few times then all 
goes dark.  No lights or anything.  The only weird part is if I put the 
flasher microsd card in that I made (can confirm I used the flasher image) 
then it will boot and it's still running Debian 8.11.  Anyone have any 
ideas as to what in the world might be going on?  Thanks 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/86cfa146-62ef-41d5-9247-0870d25a14a1%40googlegroups.com.

[beagleboard] RAM Upgrade possible?

[andrew . chilcott]

If I was making a new board using the BBAI as the starting point, would it 
be easy to simply upgrade the existing RAM to allow for 4GB rather than the 
current 1GB?  Would there need to be any OS changes (maybe just a device 
tree change?).

Or, assuming infinite skill with reworking BGA's, is it possible to 
"simply" pop off the existing RAM chips and solder on some new ones?

I know the processor is capable of supporting 4GB, but am not sure on 
whether the existing BBAI and OS images support it out of the box.


Thanks

Andrew

-- 
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/6e8dff92-65d7-4865-ad1e-3542b3159a3f%40googlegroups.com.

[beagleboard] Re: BBB (Element14/Industrial) Fails to Boot off EMMC After Flash

[Dennis Lee Bieber]

On Wed, 22 Apr 2020 19:07:33 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user biggi_
 wrote:


>IoT Flasher" and used Win32DiskImager to flash it to a microSD card.  I 
>also uncommented the 
>"#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh" at the 

Apologies that I don't have anything for the current situation, but
just some advise for the future.

1)  Win32 Disk Imager has been somewhat deprecated (it is still useful if
one is going in the other direction: SD card to disk file).  Balena Etcher
seems to be the currently recommended tool for writing image files to SD
card (it tends to handle most compression formats too, so no need to first
unpack the image file)

2)  Suggest that one should ensure the image runs from SD card (maybe doing
any customizations too) BEFORE converting it to a flasher image.


-- 
Dennis L Bieber

-- 
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/p3i3af9n8nkf70qqcnpccbigpu5arbts1c%404ax.com.

RE: [beagleboard] Re: PocketBeagle Boot Time

[rpaulbeam]

I have done that, but I am perplexed with the results I posted – I think that 
was from a different unit as I have several in various states of development.  
From what I have read, the usb gadget takes most of the userspace time.  On the 
one hand, I find it amazing that the startup scripts work for so many boards, 
but on the other hand I find their size and complexity daunting to tramps 
through and figure out.
 
From: beagleboard@googlegroups.com  On Behalf Of 
Daniel Kulp
Sent: Wednesday, April 22, 2020 3:43 PM
To: BeagleBoard 
Subject: Re: [beagleboard] Re: PocketBeagle Boot Time
 
 
The first step would be to delete any initrd images in /boot.   That will 
likely chop about 10 seconds off the "kernel" time.   I'm not sure why we're 
creating the initrd things.  
 


On Sunday, April 19, 2020 at 3:38:00 PM UTC-4, rpau...@gmail.com 
  wrote:
Thanks.  I will look at that thread.  My recent efforts have resulted in 
negative process.  
Startup finished in 17.476s (kernel) + 41.899s (userspace) = 59.376s
 
From: beagl...@googlegroups.com> On Behalf Of TJF
Sent: Saturday, April 18, 2020 2:04 PM
To: BeagleBoard  >
Subject: [beagleboard] Re: PocketBeagle Boot Time
 
On BBB:
 
$ systemd-analyze 
Startup finished in 1.067s (kernel) + 15.828s (userspace) = 16.896s
 
Booting with USB WiFi stick including connection with static IP adress. Should 
be possible with PocketBeagle as well. Find details at
 
https://groups.google.com/d/msg/beagleboard/CN5qKSmPIbc/9yNlI-w1AQAJ
 
 
-- 
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 beagl...@googlegroups.com  .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2a75d9fa-0cfa-4c4c-b29a-98c7a424caeb%40googlegroups.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/9de2a436-e717-4cc0-8571-8803f46bfb4d%40googlegroups.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/0c3901d6196c%24931ea5f0%24b95bf1d0%24%40gmail.com.

Re: [beagleboard] BBAI Flasher Image with Desktop

[Jason Kridner]

On Wed, Apr 22, 2020 at 9:51 PM Robert Nelson 
wrote:

> On Wed, Apr 22, 2020 at 8:49 PM  wrote:
> >
> > Does anyone know if there is an image for the bealgebone ai that will
> flash to the eMMC and includes the graphical desktop?
> > None of the images at http://beagleboard.org/latest-images have a
> graphical desktop and will flash to eMMC that I can see.
> > An older Debian version is okay.
> >
> > I had to re-flash the eMMC on my board due to a network connectivity
> problem but have lost the desktop that I was using to display using opencv.
> > I also don't want to boot off of an sd card because it has been a pain
> getting opencv and tensorflow installed locally.
>
> Grab this version, it's updated once a month:
>
>
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Stretch_LXQt_TIDL_Snapshot


Robert, Is there a simple process for installing the extra LXQt bits via
apt?



>
>
> 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/CAOCHtYhGfXK6PMPc20mm2oDMKXWk5O%3Dz%2BGUf7wZBHb35TBKVnA%40mail.gmail.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/CA%2BT6QPk94NcewYOKceOfdN04xSCQO70gmEpCxvJg%2BZoLxjHQVg%40mail.gmail.com.

Re: [beagleboard] Jumps right to cloud9 ide, connecting with board right?

[Jason Kridner]

On Wed, Apr 22, 2020 at 10:05 AM Robert Nelson 
wrote:

> On Wed, Apr 22, 2020 at 9:01 AM  wrote:
> >
> > Hello everyone,
> >
> > I have a BBB, Rev C and I was just trying to follow the Start menu and
> update the software, now, after I have tried to set it up, when I 'connect'
> to it it goes right to cloud9 IDE without the prior start up page, what
> happened?  I was wanting to play with the scripts on that start page. How
> do I get back to it, I try going to connect board by putting in address,
> and it does not connect.  How can I get my board back to original factory
> settings on the eMMC?  It is an Element 14 board.
>
> It was decided to drop the whole "bone" webpage on startup and just
> move users to Cloud9, and provide all the examples/doc's in the left
> hand plane of the ide.
>
> https://github.com/beagleboard/cloud9-examples


That said, we haven't *fully* killed it (at least not last I checked).

Look at http://:8000/Support/bone101

But, it is likely to be not installed in future images. I do see this stuff
gets some usage, but not enough interest to really continue driving updates
to the tutorials, which is why we've shifted to this model of tutorials
that people seem to understand what is going on quicker. The whole RPC
server confuses a lot of people, despite being a powerful tutorial feature.


If you want to run an older image, scroll down on
https://beagleboard.org/latest-images and find the date you want to move
back to. The flashing process is covered at
https://beagleboard.org/getting-started#update.


>
>
> 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/CAOCHtYge1M-caKj%3DKGmLmYiyc_y6ndqg41aSWw9_-_1NtZpCDw%40mail.gmail.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/CA%2BT6QPkrQ_6jLYPyCpvhQc%2B4QyYXL7uLx6mg2%3DJO%3D6ESzzOHdw%40mail.gmail.com.

[beagleboard] BeagleBoneBlack-Ind-4g Bill of Material

[jbossert nssengr . com]

As a follow up to my last email, one of the components in the BeagleBone Black 
Industrial Bill of Materials has a temperature range of -20C to 85C.  -20C is a 
higher temperature than what is specified for the BBBI-4G on element14's 
website (-40C to 85C).  The component in question is part number 
TDA19988BHN/C1,551 Reference Designator U11.  It is the HDMI transmitter.

My question is how will the BBBI operate below -20C?  If we are not using 
video, will the BBBI function normally below -20C?  Will the video start 
working normally again once the temperature goes above -20C?

Thanks!
Jeff Bossert
North Star Systems, Inc.

-- 
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/BN8PR12MB3412BA9B271799E98BEB131FC1D30%40BN8PR12MB3412.namprd12.prod.outlook.com.

Re: [beagleboard] Network setup taken over by something

[maxmike]

> OK - but here we go again with cape-universal:

 
 root@beaglebone:~# config-pin -q p9.26

Current mode for P9_26 is: default

root@beaglebone:~# config-pin p9.26 in+
ERROR: write() to /sys/devices/platform/ocp/ocp:P9_26_pinmux/state failed, 
No such device

-- 
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/6b35b548-5af5-47b4-8b77-fce218fb8b87%40googlegroups.com.

Re: [beagleboard] Network setup taken over by something

[Robert Nelson]

On Thu, Apr 23, 2020 at 4:32 PM maxmike  wrote:
>
>
>> OK - but here we go again with cape-universal:
>
>
>  root@beaglebone:~# config-pin -q p9.26
>
> Current mode for P9_26 is: default
>
> root@beaglebone:~# config-pin p9.26 in+
> ERROR: write() to /sys/devices/platform/ocp/ocp:P9_26_pinmux/state failed, No 
> such device

Yeah, in+ is no longer valid..

debian@bbb-pwr02-ser10:~$ config-pin -q P9.26

Current mode for P9_26 is: default

debian@bbb-pwr02-ser10:~$ config-pin -l P9.26

Available modes for P9_26 are: default gpio gpio_pu gpio_pd gpio_input
uart can i2c pru_uart pruin

in+ may have been supported by the original version of config-pin, but
that shell script is un-maintainable as we added more boards..

The new version of config-pin, parses the actual modes available.


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/CAOCHtYhNPsCKefa3tvx3xNUAReVokqU6DBhHD%3DKq76AfEb_Yiw%40mail.gmail.com.