[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-30 Thread Dennis Lee Bieber 
On Sun, 30 May 2021 11:51:27 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Karishma Jaiswal
 wrote:


>Can u suggest any way to change my application as currently my application 
>is getting call from .bashrc file and now it's taking around 35 sec to get 
>execute.
>Some how can I call the .bashrc file bit faster?  
>this will really help to reduce the boot time.

Since .bashrc is a SHELL CONFIGURATION file, it gets run when a BASH
shell is opened. So how are you getting to a bash shell? (It is vaguely
possible you have some script being started by systemd, or a @reboot
crontab entry, which specifies that the bash shell is to be used).

Bash shell/command interpreter won't be available until most of the OS
has booted.


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

Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-30 Thread Karishma Jaiswal 
@Robet Nelson

Can u suggest any way to change my application as currently my application 
is getting call from .bashrc file and now it's taking around 35 sec to get 
execute.
Some how can I call the .bashrc file bit faster?  
this will really help to reduce the boot time.

Thanks
Karishma Jaiswal

On Monday, May 24, 2021 at 9:56:44 PM UTC+5:30 robert.sty...@gmail.com 
wrote:

> Can you start these services later?
>
> If you cannot just sleep, or hibinate to save power, and have to cold boot 
> quickly.
> I would hope for something like:
>
> Initially
> load the kernel loader
> load the kernel
> (load root file-system service)
> (load IPC or network service)
> load the turnkey application
>
> Then as Needed
> load device and file-system services
>
>
> For a screen based turnkey app, you can only display a splash screen for a 
> few seconds, before the user thinks it is broken, a bit longer for an 
> animated splash screen. Imagine a car radio, something has happen 
> immediately after power on (speaker click or LED indicator or screen 
> backlight), then less than half a second "Tuning..." before music appears.
>
> On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote:
>
>> On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal 
>>  wrote: 
>> > 
>> > @Dennis L Bieber Really thanks for your detailed explanation about the 
>> each services. 
>> > I also updated ubuntu from 16 to 18 and done some modification in the 
>> services. now my board's logs are as below 
>> > My system should be working as station mode but may be future, we will 
>> add AP mode also. 
>> > I will also remove nginx services. 
>> > 
>> > 
>> > ubuntu@beaglebone:~$ systemd-analyze blame 
>> > 51.048s dev-mmcblk1p1.device 
>> > 28.951s generic-board-startup.service 
>> > 6.550s led-status.service 
>> > 6.133s systemd-hwdb-update.service 
>> > 4.805s grub-common.service 
>> > 4.611s loadcpufreq.service 
>> > 3.244s nginx.service 
>> > 3.053s systemd-udev-trigger.service 
>> > 2.971s avahi-daemon.service 
>> > 2.099s ssh.service 
>> > 1.958s archive_log.service 
>> > 1.839s keyboard-setup.service 
>> > 1.548s rsyslog.service 
>> > 1.512s connman.service 
>> > 1.438s systemd-user-sessions.service 
>> > 1.404s wpa_supplicant.service 
>> > 1.315s ofono.service 
>> > 1.291s systemd-logind.service 
>> > 1.275s cpufrequtils.service 
>> > 1.253s tacread-keymap.service 
>> > 887ms systemd-timesyncd.service 
>> > 786ms us...@0.service 
>> > 685ms systemd-journald.service 
>> > 508ms kmod-static-nodes.service 
>> > 498ms dev-mqueue.mount 
>> > 487ms fake-hwclock.service 
>> > 469ms sys-kernel-config.mount 
>> > 459ms systemd-fsck-root.service 
>> > 422ms systemd-tmpfiles-setup-dev.service 
>> > 406ms systemd-modules-load.service 
>> > 401ms systemd-sysctl.service 
>> > 390ms systemd-tmpfiles-setup.service 
>> > 387ms setvtrgb.service 
>> > 350ms nvda.service 
>> > 341ms sys-fs-fuse-connections.mount 
>> > 
>> > 
>> > Also want to know that in ubuntu 18, why below two task taking so much 
>> time and how we can reduce it further to achieve the over all boot time as 
>> 30 sec. Any suggestion will help me. 
>> > 
>> > 51.048s dev-mmcblk1p1.device 
>> > 28.951s generic-board-startup.service 
>>
>> as long as you don't use usb-serial, usb-flash, or usb-networking on 
>> the "OTG" USB port, you can nuke generic-board-startup.service 
>>
>> 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/33fc689f-5f9e-403a-83b1-428fa27f90d0n%40googlegroups.com.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-27 Thread Karishma Jaiswal 
*Hi*
*Now my boot time, [from the power up to console message display] is around 
40 sec.*
*I want to reduce it further till 25 sec. below are the existing dmesg log 
of my beaglebone board.*

ubuntu@beaglebone:~$ dmesg 
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.19.94-ti-r36 (voodoo@w1-imx6q-wandboard-2gb) 
(gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #1bionic SMP 
PREEMPT Mon Mar 2 15:55:39 UTC 2020
[0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), 
cr=10c5387d
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache
[0.00] OF: fdt: Machine model: TI AM335x BeagleBone Green Wireless
[0.00] Memory policy: Data cache writeback
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 48 MiB at 0x9c80
[0.00] On node 0 totalpages: 130560
[0.00]   Normal zone: 1148 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 130560 pages, LIFO batch:31
[0.00] CPU: All CPU(s) started in SVC mode.
[0.00] AM335X ES2.1 (sgx neon)
[0.00] random: get_random_bytes called from start_kernel+0xa0/0x508 
with crng_init=0
[0.00] percpu: Embedded 17 pages/cpu s39628 r8192 d21812 u69632
[0.00] pcpu-alloc: s39628 r8192 d21812 u69632 alloc=17*4096
[0.00] pcpu-alloc: [0] 0 
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 129412
[0.00] Kernel command line: console=ttyO0,115200n8 
bone_capemgr.enable_partno=BB-UART2 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0 rng_core.default_quality=100 quiet
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 
bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 
bytes)
[0.00] Memory: 445240K/522240K available (13312K kernel code, 1156K 
rwdata, K rodata, 1024K init, 355K bss, 27848K reserved, 49152K 
cma-reserved, 0K highmem)
[0.00] Virtual kernel memory layout:
   vector  : 0x - 0x1000   (   4 kB)
   fixmap  : 0xffc0 - 0xfff0   (3072 kB)
   vmalloc : 0xe000 - 0xff80   ( 504 MB)
   lowmem  : 0xc000 - 0xdfe0   ( 510 MB)
   pkmap   : 0xbfe0 - 0xc000   (   2 MB)
   modules : 0xbf00 - 0xbfe0   (  14 MB)
 .text : 0x(ptrval) - 0x(ptrval)   (14304 kB)
 .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
 .data : 0x(ptrval) - 0x(ptrval)   (1157 kB)
  .bss : 0x(ptrval) - 0x(ptrval)   ( 356 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] ftrace: allocating 42638 entries in 126 pages
[0.00] rcu: Preemptible hierarchical RCU implementation.
[0.00] rcu: RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
[0.00] Tasks RCU enabled.
[0.00] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[0.00] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[0.00] IRQ: Found an INTC at 0x(ptrval) (revision 5.0) with 128 
interrupts
[0.00] OMAP clockevent source: timer2 at 2400 Hz
[0.15] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 
89478484971ns
[0.32] clocksource: timer1: mask: 0x max_cycles: 
0x, max_idle_ns: 79635851949 ns
[0.41] OMAP clocksource: timer1 at 2400 Hz
[0.000776] timer_probe: no matching timers found
[0.001015] Console: colour dummy device 80x30
[0.001045] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[0.001049] This ensures that you still see kernel messages. Please
[0.001053] update your kernel commandline.
[0.001113] Calibrating delay loop... 995.32 BogoMIPS (lpj=1990656)
[0.046823] pid_max: default: 32768 minimum: 301
[0.047115] Security Framework initialized
[0.047128] Yama: becoming mindful.
[0.047277] AppArmor: AppArmor initialized
[0.047390] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.047401] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 
bytes)
[0.048512] CPU: Testing write buffer coherency: ok
[0.048574] CPU0: Spectre v2: using BPIALL workaround
[0.049060] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[0.070931] Setting up static identity map for 0x8010 - 0x80100060
[0.078845] rcu: Hierarchical SRCU implementation.
[0.090150] EFI services will not be available.
[0.094854] smp: Bringing up secondary CPUs ...
[0.094868] smp: Brought up 1 node, 1 CPU
[0.094878] SMP: Total of 1 processors activated (995.32 BogoMIPS).
[0.094885] CPU: All CPU(s) started in SVC mode.
[0.096625] devtmpfs: initialized
[0.111301] VFP support v0.3:

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-25 Thread Dennis Lee Bieber 
On Mon, 24 May 2021 20:47:42 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Karishma Jaiswal
 wrote:


> not getting the exact reason why * 51.048s dev-mmcblk1p1.device *this is 
>taking too much time and is there any way that we can reduce it?
>

Part of that may be tied to the flash memory device itself. Booting
from eMMC, my BBB came up with:

debian@beaglebone:~$ systemd-analyze blame
 48.972s generic-board-startup.service
 48.587s dev-mmcblk1p1.device
  3.739s nginx.service

But booting from a uSD card (my normal mode to avoid "wearout" of the eMMC)
showed:

debian@beaglebone:~$ systemd-analyze blame
 49.889s generic-board-startup.service
 39.657s dev-mmcblk0p1.device
  4.126s nginx.service

... The uSD was 10 seconds faster, even though that is an 8GB uSD card vs
the 4GB eMMC.

I couldn't find anything confirming if there is some sort of boot time
fsck being run.

debian@beaglebone:~$ sudo tune2fs -l /dev/mmcblk0p1
tune2fs 1.44.5 (15-Dec-2018)
Filesystem volume name:   rootfs
Last mounted on:  /

Last mount time:  Tue May 25 12:34:35 2021
Last write time:  Tue May 25 12:34:31 2021
Mount count:  132
Maximum mount count:  -1
Last checked: Wed Aug 19 21:34:49 2020
Check interval:   0 ()

debian@beaglebone:~$

Those seem to imply that no fsck is run at boot time.



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

RE: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-25 Thread John Dammeyer 
Let's do the math.  One million users running WIN-10 software waiting say 2 
minutes for usable desktop ready to perform.  That's 2 million minutes.  Or 
33,333..333  hours or 4,166.666 days or 11.4 man-years of wasted time.

Do you think we can send an invoice to Bill Gates?
John


> -Original Message-
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
> Behalf Of Dennis Lee Bieber
> Sent: May-25-21 9:05 AM
> To: Beagleboard
> Subject: [beagleboard] Re: Reducing Boottime in Beaglebone Black
> 
> On Mon, 24 May 2021 15:36:54 -0700, in gmane.comp.hardware.beagleboard.user
> "John Dammeyer"  wrote:
> 
> 
> >I will state that waiting over two minutes for a Beagle to boot into Linux 
> >desktop mouse/keyboard/screen is unacceptable.  Windows
> with a 640K 8088 or a Pentium-33MHz  could create a graphical desktop way 
> faster than a 1GHz Beagle with super fast SD card and
> 512MB of ram.  From an end user perspective anything longer than 10 to 15 
> seconds just means it's not done right.
> 
>   WfW barely qualified as a desktop. It was more of an application
> manager running on top of MS-DOS.
> 
>   My current desktop machine: 3.4GHz Intel i7-3770 with 12GB of RAM and
> Windows 10, from a shutdown state took:
> 
> 1:15 to reach the blue four-windows logo
> 2:00 to reach the Windows boot chime
> 2:25 to get to the login screen (and since my default user doesn't have a
> password...)
> 2:55 to get to user desktop -- it was still loading various services for a
> few more minutes after that
> 
> >
> >So I'd like to pose the question back to the original poster of this thread 
> >karry.jaiswal-Re5JQEeQqe9fmgfxC/sS/w...@public.gmane.org
> Why are you using a Beagle if you need fast boot times?  What is it that the 
> Beagle Green has that you need compared to something
> with an RTOS (Free RTOS for example).  Why Linux?
> >
> >
> >And with respect to University days I'll deny I ever took Fortran or Cobal 
> >courses.
> >
>   It shows... 
> 
>   COBOL COmmon Business Oriented Language
>   COBAL Generic Name: cyanocobalamin (vitamin b-12)
> 
> 
> --
> 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/jh7qagtbnnusf9aet6khtpo7aqarjqug94%404ax.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/01bc01d75186%241e46e870%245ad4b950%24%40autoartisans.com.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-25 Thread Dennis Lee Bieber 
On Mon, 24 May 2021 15:36:54 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer"  wrote:


>I will state that waiting over two minutes for a Beagle to boot into Linux 
>desktop mouse/keyboard/screen is unacceptable.  Windows with a 640K 8088 or a 
>Pentium-33MHz  could create a graphical desktop way faster than a 1GHz Beagle 
>with super fast SD card and 512MB of ram.  From an end user perspective 
>anything longer than 10 to 15 seconds just means it's not done right.

WfW barely qualified as a desktop. It was more of an application
manager running on top of MS-DOS.

My current desktop machine: 3.4GHz Intel i7-3770 with 12GB of RAM and
Windows 10, from a shutdown state took:

1:15 to reach the blue four-windows logo
2:00 to reach the Windows boot chime
2:25 to get to the login screen (and since my default user doesn't have a
password...)
2:55 to get to user desktop -- it was still loading various services for a
few more minutes after that

>
>So I'd like to pose the question back to the original poster of this thread 
>karry.jaiswal-Re5JQEeQqe9fmgfxC/sS/w...@public.gmane.org  Why are you using a 
>Beagle if you need fast boot times?  What is it that the Beagle Green has that 
>you need compared to something with an RTOS (Free RTOS for example).  Why 
>Linux?
>
>
>And with respect to University days I'll deny I ever took Fortran or Cobal 
>courses.
>
It shows... 

COBOL COmmon Business Oriented Language
COBAL Generic Name: cyanocobalamin (vitamin b-12)


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

Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread Karishma Jaiswal 
Thanks Robert, 
As suggested in link https://github.com/RobertCNelson/boot-scripts/issues/10 , 
I already applied the many changes.
In very initial, my system was taking total 90 sec as boot time which got 
reduced and now it's 54 sec approx. 

I also check to nuke generic-board-startup.service but not able to reduce 
further. can u suggest few example for which I need to reduce?
I removed the USB flash related things.
 not getting the exact reason why * 51.048s dev-mmcblk1p1.device *this is 
taking too much time and is there any way that we can reduce it?

Thanks
Karishma Jaiswal

On Monday, May 24, 2021 at 9:12:08 PM UTC+5:30 RobertCNelson wrote:

> On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal
>  wrote:
> >
> > @Dennis L Bieber Really thanks for your detailed explanation about the 
> each services.
> > I also updated ubuntu from 16 to 18 and done some modification in the 
> services. now my board's logs are as below
> > My system should be working as station mode but may be future, we will 
> add AP mode also.
> > I will also remove nginx services.
> >
> >
> > ubuntu@beaglebone:~$ systemd-analyze blame
> > 51.048s dev-mmcblk1p1.device
> > 28.951s generic-board-startup.service
> > 6.550s led-status.service
> > 6.133s systemd-hwdb-update.service
> > 4.805s grub-common.service
> > 4.611s loadcpufreq.service
> > 3.244s nginx.service
> > 3.053s systemd-udev-trigger.service
> > 2.971s avahi-daemon.service
> > 2.099s ssh.service
> > 1.958s archive_log.service
> > 1.839s keyboard-setup.service
> > 1.548s rsyslog.service
> > 1.512s connman.service
> > 1.438s systemd-user-sessions.service
> > 1.404s wpa_supplicant.service
> > 1.315s ofono.service
> > 1.291s systemd-logind.service
> > 1.275s cpufrequtils.service
> > 1.253s tacread-keymap.service
> > 887ms systemd-timesyncd.service
> > 786ms us...@0.service
> > 685ms systemd-journald.service
> > 508ms kmod-static-nodes.service
> > 498ms dev-mqueue.mount
> > 487ms fake-hwclock.service
> > 469ms sys-kernel-config.mount
> > 459ms systemd-fsck-root.service
> > 422ms systemd-tmpfiles-setup-dev.service
> > 406ms systemd-modules-load.service
> > 401ms systemd-sysctl.service
> > 390ms systemd-tmpfiles-setup.service
> > 387ms setvtrgb.service
> > 350ms nvda.service
> > 341ms sys-fs-fuse-connections.mount
> >
> >
> > Also want to know that in ubuntu 18, why below two task taking so much 
> time and how we can reduce it further to achieve the over all boot time as 
> 30 sec. Any suggestion will help me.
> >
> > 51.048s dev-mmcblk1p1.device
> > 28.951s generic-board-startup.service
>
> as long as you don't use usb-serial, usb-flash, or usb-networking on
> the "OTG" USB port, you can nuke generic-board-startup.service
>
> 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/eaa6cccf-dbc1-40fc-b520-8ee082e3db33n%40googlegroups.com.

Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread Karishma Jaiswal 

Hi
>>>So I'd like to pose the question back to the original poster of this 
thread karry@gmail.com . Why are you using 
a Beagle if you need fast boot times? 
it's an older product and we have to migrate it with enhanced peripheral. 
in the existing product, beagle bone board was used so as of now we can not 
change the board.
Recently we upgraded from ubuntu 16 to ubuntu 18. in ubuntu 16 total boot 
time was 30 sec only. But after ubuntu 18, boot time is taking too much 
time. 
Also we already showing "in progress" kind of message in our product, as 
"Tuning... " kind of message suggested. 

Thanks
Karishma Jaiswal
  
On Tuesday, May 25, 2021 at 4:07:14 AM UTC+5:30 jo...@autoartisans.com 
wrote:

> > From: beagl...@googlegroups.com [mailto:beagl...@googlegroups.com] On 
> Behalf Of Dennis Lee Bieber 
> >  wrote: 
> > 
> > > 
> > >For a screen based turnkey app, you can only display a splash screen 
> for a 
> > >few seconds, before the user thinks it is broken, a bit longer for an 
> > >animated splash screen. Imagine a car radio, something has happen 
> > >immediately after power on (speaker click or LED indicator or screen 
> > >backlight), then less than half a second "Tuning..." before music 
> appears. 
> > > 
> > Probably not the best example. At best the "car radio" is running a 
> > microcontroller -- not a microcomputer -- with maybe an RTOS at best. 
> The 
> > "radio application" is burned into the microcontroller flash memory, AND 
> > RUNS out of that flash memory. There is no setting up RAM (virtual 
> memory 
> > mapping) as "RAM" in most microcontrollers is the general purpose 
> register 
> > bank. There may be secondary flash or EEPROM used to store user settings 
> > (current volume/tone encoder position, stored station listing). A bigger 
> > unit may include a spinning disk or "user flash" for storing MP3s, but 
> the 
> > core system doesn't have real "boot" phase. 
>
> I think the requirements concept is the issue. Too many times in the past 
> I've run into projects where the client makes a choice on the architecture 
> and then we have to make the project fit. Instead of a layout of the 
> requirements and current/future capabilities as a design specification 
> first. Then look around at what is available to fill that. 
>
> Now if boot time is an issue then what amount of time is acceptable. If it 
> needs to be running in under 1 second then it doesn't matter how embedded 
> the controller might be, a beagle or a pi running Linux is just not the 
> tool for it. Sort of... 
>
> Volume of systems sold is another criteria as well as development time and 
> longevity. The design decisions made if the device goes into a hard to 
> access location will impact how it's designed and what's done with it. Etc. 
>
> I will state that waiting over two minutes for a Beagle to boot into Linux 
> desktop mouse/keyboard/screen is unacceptable. Windows with a 640K 8088 or 
> a Pentium-33MHz could create a graphical desktop way faster than a 1GHz 
> Beagle with super fast SD card and 512MB of ram. From an end user 
> perspective anything longer than 10 to 15 seconds just means it's not done 
> right. 
>
> So I'd like to pose the question back to the original poster of this 
> thread karry@gmail.com. Why are you using a Beagle if you need fast 
> boot times? What is it that the Beagle Green has that you need compared to 
> something with an RTOS (Free RTOS for example). Why Linux? 
>
> I've been on both sides of the fence. I might have already posted the 
> attached photo that shows a PiZeroW mounted onto a board that holds a 
> PIC32, SuperCaps, RTC along with GPS module and SMS module. Two antennas: 
> one for GPS, one for SMS messaging. And the connector to power and the 
> vehicle CAN bus which requires instant on logging while the PiZero provides 
> the file/networking infrastructure. The Pi is the SPI master, the PIC32 is 
> the SPI slave. As long as the PIC has the RAM storage for all the CAN 
> messages during the 18 second PiZeroW boot time all is good. It wasn’t 
> worth the time to port Microchip SD card file system support or all the 
> network stuff needed for cell net access. We only built 20. 
>
> And with respect to University days I'll deny I ever took Fortran or Cobal 
> courses. 
>
> John 
>
>
>
>
>

-- 
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/3a1ceabc-55d5-4646-91e5-df43ba9a3b38n%40googlegroups.com.

RE: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread John Dammeyer 
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
> Behalf Of Dennis Lee Bieber
>  wrote:
> 
> >
> >For a screen based turnkey app, you can only display a splash screen for a
> >few seconds, before the user thinks it is broken, a bit longer for an
> >animated splash screen. Imagine a car radio, something has happen
> >immediately after power on (speaker click or LED indicator or screen
> >backlight), then less than half a second "Tuning..." before music appears.
> >
>   Probably not the best example. At best the "car radio" is running a
> microcontroller -- not a microcomputer -- with maybe an RTOS at best. The
> "radio application" is burned into the microcontroller flash memory, AND
> RUNS out of that flash memory. There is no setting up RAM (virtual memory
> mapping) as "RAM" in most microcontrollers is the general purpose register
> bank. There may be secondary flash or EEPROM used to store user settings
> (current volume/tone encoder position, stored station listing). A bigger
> unit may include a spinning disk or "user flash" for storing MP3s, but the
> core system doesn't have real "boot" phase.

I think the requirements concept is the issue.  Too many times in the past I've 
run into projects where the client makes a choice on the architecture and then 
we have to make the project fit.  Instead of a layout of the requirements and 
current/future capabilities as a design specification first.  Then look around 
at what is available to fill that.

Now if boot time is an issue then what amount of time is acceptable.  If it 
needs to be running in under 1 second then it doesn't matter how embedded the 
controller might be, a beagle or a pi running Linux is just not the tool for 
it.  Sort of...

Volume of systems sold is another criteria as well as development time and 
longevity.  The design decisions made if the device goes into a hard to access 
location will impact how it's designed and what's done with it. Etc.

I will state that waiting over two minutes for a Beagle to boot into Linux 
desktop mouse/keyboard/screen is unacceptable.  Windows with a 640K 8088 or a 
Pentium-33MHz  could create a graphical desktop way faster than a 1GHz Beagle 
with super fast SD card and 512MB of ram.  From an end user perspective 
anything longer than 10 to 15 seconds just means it's not done right.

So I'd like to pose the question back to the original poster of this thread 
karry.jais...@gmail.com.  Why are you using a Beagle if you need fast boot 
times?  What is it that the Beagle Green has that you need compared to 
something with an RTOS (Free RTOS for example).  Why Linux?

I've been on both sides of the fence.  I might have already posted the attached 
photo that shows a PiZeroW mounted onto a board that holds a PIC32, SuperCaps, 
RTC along with GPS module and SMS module.  Two antennas: one for GPS, one for 
SMS messaging.  And the connector to power and the vehicle CAN bus which 
requires instant on logging while the PiZero provides the file/networking 
infrastructure.  The Pi is the SPI master, the PIC32 is the SPI slave.  As long 
as the PIC has the RAM storage for all the CAN messages during the 18 second 
PiZeroW boot time all is good.  It wasn’t worth the time to port Microchip SD 
card file system support or all the network stuff needed for cell net access.  
We only built 20.

And with respect to University days I'll deny I ever took Fortran or Cobal 
courses.

John




-- 
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/00f601d750ed%244cafa650%24e60ef2f0%24%40autoartisans.com.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread Dennis Lee Bieber 
On Mon, 24 May 2021 09:26:44 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user
"robert.sty...-re5jqeeqqe8avxtiumw...@public.gmane.org"
 wrote:

>
>For a screen based turnkey app, you can only display a splash screen for a 
>few seconds, before the user thinks it is broken, a bit longer for an 
>animated splash screen. Imagine a car radio, something has happen 
>immediately after power on (speaker click or LED indicator or screen 
>backlight), then less than half a second "Tuning..." before music appears.
>
Probably not the best example. At best the "car radio" is running a
microcontroller -- not a microcomputer -- with maybe an RTOS at best. The
"radio application" is burned into the microcontroller flash memory, AND
RUNS out of that flash memory. There is no setting up RAM (virtual memory
mapping) as "RAM" in most microcontrollers is the general purpose register
bank. There may be secondary flash or EEPROM used to store user settings
(current volume/tone encoder position, stored station listing). A bigger
unit may include a spinning disk or "user flash" for storing MP3s, but the
core system doesn't have real "boot" phase.

Think Arduino Due, TIVA TM4C123 or TM4C1294, STM chips. ARM "M" cores,
not "A" cores.

On power-on, they start running the code burnt into the on-board flash
(and the first thing said code likely does is read the saved configuration
and command displays/output encoders to those values).

{Heck, most of the car is running off of microcontrollers with the single
application for each burned into flash. Can you imagine having to wait 60+
seconds for a Linux type OS to boot before you can turn the switch from ON
to START?}



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

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread Dennis Lee Bieber 
On Mon, 24 May 2021 11:34:41 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer"  wrote:


>But the side effect is that 16 to 18 seconds appears to be the fastest it can 
>wake up which means it's not always the best solution for a product.  But in 
>this world of Python and web based programming, embedded systems have taken a 
>back seat.
>

https://www.adafruit.com/product/4064
Native system runs the CircuitPython interpreter in chip, with Python
application code files on the external flash (if you want base Arduino
behavior, you replace the in-chip CircuitPython with your Arduino sketch,
and use the external flash for data storage).

There are smaller Metro M4 Express (out of stock) and Metro M4 Express
AirLift (with on-board WiFi)

>If you were a new grad from what now tends to be called "Computer Engineering" 
>would you take a job that offered $100K per year as a web designer or $60K 
>developing embedded systems that required assembler knowledge?

Considering my ancient degree was "Computer Science" with an emphasis
on "systems" software rather than "business" software*... I'd probably have
qualified for the latter (at the time, as a new-hire at Lockheed Sunnyvale,
I got only $21K -- which had grown to $125K after 30 years) {And had a
defined benefit retirement plan, vs defined contribution... After layoff
moved to MI and manage a few years at GE Aviation -- my ("early
retirement") from Lockheed was nearly as much as GE paid!}




*   "systems software" covered OS principles along with
compilers/linkers/etc, and language design. "business" had two terms of
statistics using SPSS (I'm sure these days they'd be using R [optimal],
Octave [as a backup -- Octave being a number cruncher/display tool, where R
includes more statistics testing built-in]), or maybe Python with SciPy and
or pandas extensions.
.


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

RE: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread John Dammeyer 
I agree.  
RantMode := TRUE;
It's not Linux per say which is an amazing environment that has brought so 
much. Not to mention the tremendous support from people like Robert. 
 
But the side effect is that 16 to 18 seconds appears to be the fastest it can 
wake up which means it's not always the best solution for a product.  But in 
this world of Python and web based programming, embedded systems have taken a 
back seat.
 
If you were a new grad from what now tends to be called "Computer Engineering" 
would you take a job that offered $100K per year as a web designer or $60K 
developing embedded systems that required assembler knowledge?
 
So if your school used Linux and Raspberry Pi or Beagles as the learning 
environment and you were hired to develop a BluRay Player by Panasonic, would 
you pull out Microchip's MPLAB-X which you had never used along with a PIC32 or 
shoehorn in an ARM processor running Linux with all the support for online 
firmware upgrades and pre-written video decoding?  And if it takes 20 seconds 
to open the drawer just say so "who cares?".
 
When this BD30 player fails the first thing I will test on new hardware is how 
fast the drawer opens.  But I might also not have a choice…
RantMode := FALSE;
 
John
 
From: 'Mark Lazarewicz' via BeagleBoard [mailto:beagleboard@googlegroups.com] 
Sent: May-24-21 10:58 AM
To: beagleboard@googlegroups.com
Subject: RE: [beagleboard] Re: Reducing Boottime in Beaglebone Black
 
John 
 
Ohh boy you got me started now. My Verizon hotspot jetpack  (my 3rd purchase) 
resets very frequently sometimes 4 time's rebooting during important updates to 
my online database of vinyl. It also Freeze's up after 2 years intermittently 
for days. Linux and poor design. I suspect it's the wifi radio and software 
interface to Linux GUI. Has to be a serious bug to reset Chip. No watchdog to 
reset radio just goodbye reboot hello repeatedly.
 
Cheap design by some low payed QT PC programmer who's never seen an 
oscilloscope in his life is my guess.
 
I read them the riot act at Verizon. The Verizon manager was a computer science 
graduate who could not find a job 6 years ago.
 
Yes as consumer's we have to demand better and boycott bad engineering with our 
wallets.
 
Rant over
 
Mark
 
 
Sent from Yahoo Mail on Android 
<https://go.onelink.me/107872968?pid=InProduct=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers_wl=ym_sub1=Internal_sub2=Global_YGrowth_sub3=EmailSignature>
 
 
On Mon, May 24, 2021 at 12:32 PM, John Dammeyer
 wrote:
Just a totally irrelevant side note here.  
 
I finally found out why my Panasonic DMP-BD30 is so incredibly annoying on 
power up.  I can press the power button and the display lights up and a 'HELLO' 
message shows up instantly.  Then noises come from inside.  The 'HELLO' 
brightens and then changes to 'READING'.  About 20 seconds later the button to 
open the disk drawer finally works.
 
When went searching to see if there was a firmware upgrade I found out it was 
running Linux. 
 
The inability of the disk drawer to be opened immediately is bad human factors 
engineering IMHO.  When a user turns on power they expect and should be 
rewarded with the drawer opening immediately if the eject button is pressed.  
If it weren't running Linux but an RTOS or even just co-operative 
multi-threading the drawer operation wouldn't be delayed.  But that just isn't 
possible in a stock Linux system unless a special task is written that is 
loaded early and handles the tray.  Which would be very complicated I suspect 
and beyond the ability of the normal software engineer.
 
What is sad is we are seeing acceptance of this sort of poor behavior as 
perfectly alright.  Again IMHO.
 
John
 
 
 
 
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of robert.sty...@gmail.com
Sent: May-24-21 9:27 AM
To: BeagleBoard
Subject: Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black
 
Can you start these services later?
 
If you cannot just sleep, or hibinate to save power, and have to cold boot 
quickly.
I would hope for something like:
 
Initially
load the kernel loader
load the kernel
(load root file-system service)
(load IPC or network service)
load the turnkey application
 
Then as Needed
load device and file-system services
 
 
For a screen based turnkey app, you can only display a splash screen for a few 
seconds, before the user thinks it is broken, a bit longer for an animated 
splash screen. Imagine a car radio, something has happen immediately after 
power on (speaker click or LED indicator or screen backlight), then less than 
half a second "Tuning..." before music appears.
 
On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote:
On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal 
 wrote: 
> 
> @Dennis L Bieber Really thanks for your detailed explanation about the each 
> services. 
> I also updated ubuntu from 16 to 18 and done some modification in t

RE: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread 'Mark Lazarewicz' via BeagleBoard 
John 
Ohh boy you got me started now. My Verizon hotspot jetpack  (my 3rd purchase) 
resets very frequently sometimes 4 time's rebooting during important updates to 
my online database of vinyl. It also Freeze's up after 2 years intermittently 
for days. Linux and poor design. I suspect it's the wifi radio and software 
interface to Linux GUI. Has to be a serious bug to reset Chip. No watchdog to 
reset radio just goodbye reboot hello repeatedly.
Cheap design by some low payed QT PC programmer who's never seen an 
oscilloscope in his life is my guess.
I read them the riot act at Verizon. The Verizon manager was a computer science 
graduate who could not find a job 6 years ago.
Yes as consumer's we have to demand better and boycott bad engineering with our 
wallets.
Rant over
Mark


Sent from Yahoo Mail on Android 
 
  On Mon, May 24, 2021 at 12:32 PM, John Dammeyer 
wrote:   #yiv3954327767 #yiv3954327767 -- _filtered {} _filtered {} _filtered 
{}#yiv3954327767 #yiv3954327767 p.yiv3954327767MsoNormal, #yiv3954327767 
li.yiv3954327767MsoNormal, #yiv3954327767 div.yiv3954327767MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New;}#yiv3954327767
 a:link, #yiv3954327767 span.yiv3954327767MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv3954327767 a:visited, #yiv3954327767 
span.yiv3954327767MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv3954327767 p 
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:New;}#yiv3954327767
 p.yiv3954327767Code, #yiv3954327767 li.yiv3954327767Code, #yiv3954327767 
div.yiv3954327767Code 
{margin:0cm;margin-bottom:.0001pt;font-size:8.0pt;}#yiv3954327767 
span.yiv3954327767EmailStyle19 {font-family:New;color:#1F497D;}#yiv3954327767 
.yiv3954327767MsoChpDefault {font-size:10.0pt;} _filtered {}#yiv3954327767 
div.yiv3954327767WordSection1 {}#yiv3954327767 
Just a totally irrelevant side note here.  

  

I finally found out why my Panasonic DMP-BD30 is so incredibly annoying on 
power up.  I can press the power button and the display lights up and a 'HELLO' 
message shows up instantly.  Then noises come from inside.  The 'HELLO' 
brightens and then changes to 'READING'.  About 20 seconds later the button to 
open the disk drawer finally works.

  

When went searching to see if there was a firmware upgrade I found out it was 
running Linux. 

  

The inability of the disk drawer to be opened immediately is bad human factors 
engineering IMHO.  When a user turns on power they expect and should be 
rewarded with the drawer opening immediately if the eject button is pressed.  
If it weren't running Linux but an RTOS or even just co-operative 
multi-threading the drawer operation wouldn't be delayed.  But that just isn't 
possible in a stock Linux system unless a special task is written that is 
loaded early and handles the tray.  Which would be very complicated I suspect 
and beyond the ability of the normal software engineer.

  

What is sad is we are seeing acceptance of this sort of poor behavior as 
perfectly alright.  Again IMHO.

  

John

  

  

  

  

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of robert.sty...@gmail.com
Sent: May-24-21 9:27 AM
To: BeagleBoard
Subject: Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

  

Can you start these services later?

  

If you cannot just sleep, or hibinate to save power, and have to cold boot 
quickly.

I would hope for something like:

  

Initially

load the kernel loader

load the kernel

(load root file-system service)

(load IPC or network service)

load the turnkey application

  

Then as Needed

load device and file-system services

  

  

For a screen based turnkey app, you can only display a splash screen for a few 
seconds, before the user thinks it is broken, a bit longer for an animated 
splash screen. Imagine a car radio, something has happen immediately after 
power on (speaker click or LED indicator or screen backlight), then less than 
half a second "Tuning..." before music appears.

  

On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote:


On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal 
 wrote: 
> 
> @Dennis L Bieber Really thanks for your detailed explanation about the each 
> services. 
> I also updated ubuntu from 16 to 18 and done some modification in the 
> services. now my board's logs are as below 
> My system should be working as station mode but may be future, we will add AP 
> mode also. 
> I will also remove nginx services. 
> 
> 
> ubuntu@beaglebone:~$ systemd-analyze blame 
> 51.048s dev-mmcblk1p1.device 
> 28.951s generic-board-startup.service 
> 6.550s led-status.service 
> 6.133s systemd-hwdb-update.service 
> 4.805s grub-common.service 
> 4.611s loadcpufreq.service 
> 3.244s nginx.service 
> 3.053s systemd-udev-trigger.service 
> 2.971s avahi-daemon.service 
> 2.099s ssh.service 
> 1.958s ar

RE: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread John Dammeyer 
Just a totally irrelevant side note here.  
 
I finally found out why my Panasonic DMP-BD30 is so incredibly annoying on 
power up.  I can press the power button and the display lights up and a 'HELLO' 
message shows up instantly.  Then noises come from inside.  The 'HELLO' 
brightens and then changes to 'READING'.  About 20 seconds later the button to 
open the disk drawer finally works.
 
When went searching to see if there was a firmware upgrade I found out it was 
running Linux. 
 
The inability of the disk drawer to be opened immediately is bad human factors 
engineering IMHO.  When a user turns on power they expect and should be 
rewarded with the drawer opening immediately if the eject button is pressed.  
If it weren't running Linux but an RTOS or even just co-operative 
multi-threading the drawer operation wouldn't be delayed.  But that just isn't 
possible in a stock Linux system unless a special task is written that is 
loaded early and handles the tray.  Which would be very complicated I suspect 
and beyond the ability of the normal software engineer.
 
What is sad is we are seeing acceptance of this sort of poor behavior as 
perfectly alright.  Again IMHO.
 
John
 
 
 
 
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of robert.sty...@gmail.com
Sent: May-24-21 9:27 AM
To: BeagleBoard
Subject: Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black
 
Can you start these services later?
 
If you cannot just sleep, or hibinate to save power, and have to cold boot 
quickly.
I would hope for something like:
 
Initially
load the kernel loader
load the kernel
(load root file-system service)
(load IPC or network service)
load the turnkey application
 
Then as Needed
load device and file-system services
 
 
For a screen based turnkey app, you can only display a splash screen for a few 
seconds, before the user thinks it is broken, a bit longer for an animated 
splash screen. Imagine a car radio, something has happen immediately after 
power on (speaker click or LED indicator or screen backlight), then less than 
half a second "Tuning..." before music appears.
 
On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote:
On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal 
 wrote: 
> 
> @Dennis L Bieber Really thanks for your detailed explanation about the each 
> services. 
> I also updated ubuntu from 16 to 18 and done some modification in the 
> services. now my board's logs are as below 
> My system should be working as station mode but may be future, we will add AP 
> mode also. 
> I will also remove nginx services. 
> 
> 
> ubuntu@beaglebone:~$ systemd-analyze blame 
> 51.048s dev-mmcblk1p1.device 
> 28.951s generic-board-startup.service 
> 6.550s led-status.service 
> 6.133s systemd-hwdb-update.service 
> 4.805s grub-common.service 
> 4.611s loadcpufreq.service 
> 3.244s nginx.service 
> 3.053s systemd-udev-trigger.service 
> 2.971s avahi-daemon.service 
> 2.099s ssh.service 
> 1.958s archive_log.service 
> 1.839s keyboard-setup.service 
> 1.548s rsyslog.service 
> 1.512s connman.service 
> 1.438s systemd-user-sessions.service 
> 1.404s wpa_supplicant.service 
> 1.315s ofono.service 
> 1.291s systemd-logind.service 
> 1.275s cpufrequtils.service 
> 1.253s tacread-keymap.service 
> 887ms systemd-timesyncd.service 
> 786ms us...@0.service 
> 685ms systemd-journald.service 
> 508ms kmod-static-nodes.service 
> 498ms dev-mqueue.mount 
> 487ms fake-hwclock.service 
> 469ms sys-kernel-config.mount 
> 459ms systemd-fsck-root.service 
> 422ms systemd-tmpfiles-setup-dev.service 
> 406ms systemd-modules-load.service 
> 401ms systemd-sysctl.service 
> 390ms systemd-tmpfiles-setup.service 
> 387ms setvtrgb.service 
> 350ms nvda.service 
> 341ms sys-fs-fuse-connections.mount 
> 
> 
> Also want to know that in ubuntu 18, why below two task taking so much time 
> and how we can reduce it further to achieve the over all boot time as 30 sec. 
> Any suggestion will help me. 
> 
> 51.048s dev-mmcblk1p1.device 
> 28.951s generic-board-startup.service 

as long as you don't use usb-serial, usb-flash, or usb-networking on 
the "OTG" USB port, you can nuke generic-board-startup.service 

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/f25766a9-4032-4466-a3b5-e42a5df485d5n%40googlegroups.com
 
<https://groups.google.com/d/msgid/beagleboard/f25766a9-4032-4466-a3b5-e42a5df485d5n%40googlegroups.com?utm_medium=email_sou

Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread robert.sty...@gmail.com 
Can you start these services later?

If you cannot just sleep, or hibinate to save power, and have to cold boot 
quickly.
I would hope for something like:

Initially
load the kernel loader
load the kernel
(load root file-system service)
(load IPC or network service)
load the turnkey application

Then as Needed
load device and file-system services


For a screen based turnkey app, you can only display a splash screen for a 
few seconds, before the user thinks it is broken, a bit longer for an 
animated splash screen. Imagine a car radio, something has happen 
immediately after power on (speaker click or LED indicator or screen 
backlight), then less than half a second "Tuning..." before music appears.

On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote:

> On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal
>  wrote:
> >
> > @Dennis L Bieber Really thanks for your detailed explanation about the 
> each services.
> > I also updated ubuntu from 16 to 18 and done some modification in the 
> services. now my board's logs are as below
> > My system should be working as station mode but may be future, we will 
> add AP mode also.
> > I will also remove nginx services.
> >
> >
> > ubuntu@beaglebone:~$ systemd-analyze blame
> > 51.048s dev-mmcblk1p1.device
> > 28.951s generic-board-startup.service
> > 6.550s led-status.service
> > 6.133s systemd-hwdb-update.service
> > 4.805s grub-common.service
> > 4.611s loadcpufreq.service
> > 3.244s nginx.service
> > 3.053s systemd-udev-trigger.service
> > 2.971s avahi-daemon.service
> > 2.099s ssh.service
> > 1.958s archive_log.service
> > 1.839s keyboard-setup.service
> > 1.548s rsyslog.service
> > 1.512s connman.service
> > 1.438s systemd-user-sessions.service
> > 1.404s wpa_supplicant.service
> > 1.315s ofono.service
> > 1.291s systemd-logind.service
> > 1.275s cpufrequtils.service
> > 1.253s tacread-keymap.service
> > 887ms systemd-timesyncd.service
> > 786ms us...@0.service
> > 685ms systemd-journald.service
> > 508ms kmod-static-nodes.service
> > 498ms dev-mqueue.mount
> > 487ms fake-hwclock.service
> > 469ms sys-kernel-config.mount
> > 459ms systemd-fsck-root.service
> > 422ms systemd-tmpfiles-setup-dev.service
> > 406ms systemd-modules-load.service
> > 401ms systemd-sysctl.service
> > 390ms systemd-tmpfiles-setup.service
> > 387ms setvtrgb.service
> > 350ms nvda.service
> > 341ms sys-fs-fuse-connections.mount
> >
> >
> > Also want to know that in ubuntu 18, why below two task taking so much 
> time and how we can reduce it further to achieve the over all boot time as 
> 30 sec. Any suggestion will help me.
> >
> > 51.048s dev-mmcblk1p1.device
> > 28.951s generic-board-startup.service
>
> as long as you don't use usb-serial, usb-flash, or usb-networking on
> the "OTG" USB port, you can nuke generic-board-startup.service
>
> 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/f25766a9-4032-4466-a3b5-e42a5df485d5n%40googlegroups.com.

Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-24 Thread Robert Nelson 
On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal
 wrote:
>
> @Dennis L Bieber Really thanks for your detailed explanation about the each 
> services.
> I also updated ubuntu from 16 to 18 and done some modification in the 
> services. now my board's logs are as below
> My system should be working as station mode but may be future, we will add AP 
> mode also.
> I will also remove nginx services.
>
>
> ubuntu@beaglebone:~$ systemd-analyze blame
>  51.048s dev-mmcblk1p1.device
>  28.951s generic-board-startup.service
>   6.550s led-status.service
>   6.133s systemd-hwdb-update.service
>   4.805s grub-common.service
>   4.611s loadcpufreq.service
>   3.244s nginx.service
>   3.053s systemd-udev-trigger.service
>   2.971s avahi-daemon.service
>   2.099s ssh.service
>   1.958s archive_log.service
>   1.839s keyboard-setup.service
>   1.548s rsyslog.service
>   1.512s connman.service
>   1.438s systemd-user-sessions.service
>   1.404s wpa_supplicant.service
>   1.315s ofono.service
>   1.291s systemd-logind.service
>   1.275s cpufrequtils.service
>   1.253s tacread-keymap.service
>887ms systemd-timesyncd.service
>786ms user@0.service
>685ms systemd-journald.service
>508ms kmod-static-nodes.service
>498ms dev-mqueue.mount
>487ms fake-hwclock.service
>469ms sys-kernel-config.mount
>459ms systemd-fsck-root.service
>422ms systemd-tmpfiles-setup-dev.service
>406ms systemd-modules-load.service
>401ms systemd-sysctl.service
>390ms systemd-tmpfiles-setup.service
>387ms setvtrgb.service
>350ms nvda.service
>341ms sys-fs-fuse-connections.mount
>
>
> Also want to know that in ubuntu 18, why below two task taking so much time 
> and how we can reduce it further to achieve the over all boot time as 30 sec. 
> Any suggestion will help me.
>
>  51.048s dev-mmcblk1p1.device
>  28.951s generic-board-startup.service

as long as you don't use usb-serial, usb-flash, or usb-networking on
the "OTG" USB port, you can nuke generic-board-startup.service

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/CAOCHtYgLWHEPsyhJE-CuqE%2BWnSBHQkdzPDrdjqM0JSWcU%3D_Q0A%40mail.gmail.com.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-23 Thread Karishma Jaiswal 
@Dennis L Bieber Really thanks for your detailed explanation about the each 
services.
I also updated ubuntu from 16 to 18 and done some modification in the 
services. now my board's logs are as below   
My system should be working as station mode but may be future, we will add 
AP mode also.
I will also remove nginx services.  


ubuntu@beaglebone:~$ systemd-analyze blame
* 51.048s dev-mmcblk1p1.device*
 *28.951s generic-board-startup.service*
  6.550s led-status.service
  6.133s systemd-hwdb-update.service
  4.805s grub-common.service
  4.611s loadcpufreq.service
  3.244s nginx.service
  3.053s systemd-udev-trigger.service
  2.971s avahi-daemon.service
  2.099s ssh.service
  1.958s archive_log.service
  1.839s keyboard-setup.service
  1.548s rsyslog.service
  1.512s connman.service
  1.438s systemd-user-sessions.service
  1.404s wpa_supplicant.service
  1.315s ofono.service
  1.291s systemd-logind.service
  1.275s cpufrequtils.service
  1.253s tacread-keymap.service
   887ms systemd-timesyncd.service
   786ms user@0.service
   685ms systemd-journald.service
   508ms kmod-static-nodes.service
   498ms dev-mqueue.mount
   487ms fake-hwclock.service
   469ms sys-kernel-config.mount
   459ms systemd-fsck-root.service
   422ms systemd-tmpfiles-setup-dev.service
   406ms systemd-modules-load.service
   401ms systemd-sysctl.service
   390ms systemd-tmpfiles-setup.service
   387ms setvtrgb.service
   350ms nvda.service
   341ms sys-fs-fuse-connections.mount


Also want to know that in ubuntu 18, why below two task taking so much time 
and how we can reduce it further to achieve the over all boot time as 30 
sec. Any suggestion will help me. 

 *51.048s dev-mmcblk1p1.device*
 *28.951s generic-board-startup.service*


Thanks
Karishma Jaiswal
On Sunday, May 23, 2021 at 9:19:48 AM UTC+5:30 Dennis Bieber wrote:

> On Sat, 22 May 2021 12:00:54 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user Karishma Jaiswal
>  wrote:
>
> > 15.945s postfix.service
>
> Do you need a mail delivery service? http://www.postfix.org/ You have
> scripts sending emails?
>
> > 12.165s generic-board-startup.service
> > 8.654s apache2.service
>
> Do you need a web-server -- and if you do, does it have to be Apache?
> Consider that nginx is installed as part of the normal Debian images.
>
> > 7.635s systemd-logind.service
> > 6.160s avahi-daemon.service
>
> https://www.linux.com/topic/desktop/cleaning-your-linux-startup-process/
> """
> avahi-daemon.service is supposed to provide zero-configuration network
> discovery, and make it super-easy to find printers and other hosts on your
> network. I always disable it and don’t miss it.
> """
>
>
> > 5.594s systemd-hwdb-update.service
> > 5.568s ondemand.service
> > 5.432s loadcpufreq.service
> > 4.968s bb-wl18xx-bluetooth.service
> > 4.578s led-status.service
> > 3.547s networking.service
> > 2.981s capemgr.service
> > 2.412s hostapd.service
>
> Do you need to have the unit operate as a WiFi hotspot (Access Point)?
> Note: not sure if the authentication feature is used for regular connection
> /to/ an access point (WiFi Router). https://man.openbsd.org/hostapd.8
>
> > 2.389s rsyslog.service
> > 2.073s cpufrequtils.service
> > 1.535s ssh.service
> > 1.477s systemd-user-sessions.service
> > 1.389s pppd-dns.service
>
> Same web site:
> """
> pppd-dns.service is a relic of the dim past. If you use dial-up Internet,
> keep it. Otherwise, you don’t need it.
>
> """
> > 1.151s systemd-udev-trigger.service
> > 1.040s archive_log.service
> > 1.011s systemd-journal-flush.service
> > 979ms rc-local.service
> > 860ms brltty.service
> Ditto:
> """
> brltty.service provides Braille device support, for example, Braille
> displays.
> """
>
> > 653ms keyboard-setup.service
> > 629ms systemd-journald.service
> > 609ms tacread-keymap.service
>
> Can't find any information on "tacread" via Google... Nor via apt
> search in Buster IoT release.
>
> > 499ms rename-bluetooth-hardware.service
> > 494ms systemd-update-utmp.service
> > 462ms systemd-udevd.service
> > 451ms resolvconf.service
> > 437ms dev-mqueue.mount
> > 437ms sys-kernel-debug.mount
>
>
> -- 
> 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/e1da2842-d3f2-4e63-a4e6-3fa1daa9b33an%40googlegroups.com.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-22 Thread Dennis Lee Bieber 
On Sat, 22 May 2021 12:00:54 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Karishma Jaiswal
 wrote:

> 15.945s postfix.service

Do you need a mail delivery service? http://www.postfix.org/ You have
scripts sending emails?

> 12.165s generic-board-startup.service
>  8.654s apache2.service

Do you need a web-server -- and if you do, does it have to be Apache?
Consider that nginx is installed as part of the normal Debian images.

>  7.635s systemd-logind.service
>  6.160s avahi-daemon.service

https://www.linux.com/topic/desktop/cleaning-your-linux-startup-process/
"""
avahi-daemon.service is supposed to provide zero-configuration network
discovery, and make it super-easy to find printers and other hosts on your
network. I always disable it and don’t miss it.
"""


>  5.594s systemd-hwdb-update.service
>  5.568s ondemand.service
>  5.432s loadcpufreq.service
>  4.968s bb-wl18xx-bluetooth.service
>  4.578s led-status.service
>  3.547s networking.service
>  2.981s capemgr.service
>  2.412s hostapd.service

Do you need to have the unit operate as a WiFi hotspot (Access Point)?
Note: not sure if the authentication feature is used for regular connection
/to/ an access point (WiFi Router). https://man.openbsd.org/hostapd.8

>  2.389s rsyslog.service
>  2.073s cpufrequtils.service
>  1.535s ssh.service
>  1.477s systemd-user-sessions.service
>  1.389s pppd-dns.service

Same web site:
"""
pppd-dns.service is a relic of the dim past. If you use dial-up Internet,
keep it. Otherwise, you don’t need it.

"""
>  1.151s systemd-udev-trigger.service
>  1.040s archive_log.service
>  1.011s systemd-journal-flush.service
>   979ms rc-local.service
>   860ms brltty.service
Ditto:
"""
brltty.service provides Braille device support, for example, Braille
displays.
"""

>   653ms keyboard-setup.service
>   629ms systemd-journald.service
>   609ms tacread-keymap.service

Can't find any information on "tacread" via Google... Nor via apt
search in Buster IoT release.

>   499ms rename-bluetooth-hardware.service
>   494ms systemd-update-utmp.service
>   462ms systemd-udevd.service
>   451ms resolvconf.service
>   437ms dev-mqueue.mount
>   437ms sys-kernel-debug.mount


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

[beagleboard] Re: Reducing Boottime in Beaglebone Black

2021-05-19 Thread Dennis Lee Bieber 
On Wed, 19 May 2021 09:37:32 -0700, in gmane.comp.hardware.beagleboard.user
"John Dammeyer"  wrote:

>Hi Amit,
>Interesting.  4.19.94 is a only a little bit faster than 4.14.108.  Is there a 
>document somewhere that explains what to do to even just speed up both start 
>up and shut down?
>What did you do to get it to 50 seconds?
> 
>John
> 
> 
>debian@ebb:~$ uname -a
>Linux ebb 4.14.108-ti-r136 #1stretch SMP PREEMPT Mon Jun 8 15:38:30 UTC 2020 
>armv7l GNU/Linux
> 
>debian@ebb:~$ systemd-analyze
>Startup finished in 40.059s (kernel) + 1min 27.889s (userspace) = 2min 7.948s
> 
>debian@ebb:~$ systemd-analyze blame
>1min 47.177s dev-mmcblk0p1.device
>1min 13.819s generic-board-startup.service
> 
>debian@beaglebone:~$ uname -a
>Linux beaglebone 4.19.94-ti-r63 #1buster SMP PREEMPT Fri May 14 16:42:32 UTC 
>2021 armv7l GNU/Linux
> 
>debian@beaglebone:~$ systemd-analyze
>Startup finished in 26.608s (kernel) + 1min 32.506s (userspace) = 1min 59.114s
>graphical.target reached after 1min 32.205s in userspace
> 
>debian@beaglebone:~$ systemd-analyze blame
>1min 20.997s generic-board-startup.service
> 1min 4.519s dev-mmcblk0p1.device
> 11.344s udisks2.service
> 

Just to add a data point: Buster IoT image on uSD card...

debian@beaglebone:~$ uname -a
Linux beaglebone 4.19.94-ti-r48 #1buster SMP PREEMPT Wed Aug 19 17:38:55
UTC 2020 armv7l GNU/Linux

debian@beaglebone:~$ systemd-analyze
Startup finished in 10.915s (kernel) + 1min 961ms (userspace) = 1min
11.877s
graphical.target reached after 1min 668ms in userspace

That's odd -- Did I leave the LXQT image in the board (I have uSD for
both IoT and LXQT)

debian@beaglebone:~$ systemd-analyze blame
 51.745s generic-board-startup.service
 40.798s dev-mmcblk0p1.device
  4.064s nginx.service
  3.587s systemd-udev-trigger.service

From DMESG one finds such ...

[1.668861] ALSA device list:
[1.668877]   #0: TI BeagleBone Black
[1.675450] Freeing unused kernel memory: 1024K
[1.676178] Run /init as init process
[2.664089] [drm] Cannot find any crtc or sizes
[   10.155042] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data
mode. Opts: (null)
[   10.955497] systemd[1]: System time before build time, advancing clock.

EIGHT seconds mounting file system

[   13.203659] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro
[   14.816264] systemd-journald[893]: Received request to flush runtime
journal from PID 1
[   21.928916] net eth0: initializing cpsw version 1.12 (0)
[   22.000769] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver
[SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)

SEVEN seconds initializing eth0

[   27.071692] configfs-gadget gadget: high-speed config #1: c
[   27.072147] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   27.277845] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[   69.566416] remoteproc remoteproc0: wkup_m3 is available
[   69.658941] remoteproc remoteproc0: powering up wkup_m3
[   69.658973] remoteproc remoteproc0: Booting fw image
am335x-pm-firmware.elf, size 217168

FORTY seconds preparing the PRUs with remoteproc

Let me switch uSD card...

debian@beaglebone:~$ uname -a
Linux beaglebone 4.19.94-ti-r48 #1buster SMP PREEMPT Wed Aug 19 17:38:55
UTC 2020 armv7l GNU/Linux

debian@beaglebone:~$ systemd-analyze
Bootup is not yet finished
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
debian@beaglebone:~$ systemctl list-jobs
JOB UNIT TYPE  STATE
 89 getty.target start waiting
 69 generic-board-startup.servicestart running
 97 serial-getty@ttyGS0.service  start waiting
  2 multi-user.targetstart waiting
  1 graphical.target start waiting
 81 systemd-update-utmp-runlevel.service start waiting
 98 dev-ttyGS0.devicestart running

7 jobs listed.

Hmmm, looks like I need to attach an HDMI cable and monitor to
determine which has the LXQT image...

debian@beaglebone:~$ systemctl list-jobs
No jobs running.

debian@beaglebone:~$ systemd-analyze
Startup finished in 11.355s (kernel) + 1min 24.913s (userspace) = 1min
36.268s
graphical.target reached after 1min 24.632s in userspace
debian@beaglebone:~$ systemd-analyze blame
1min 15.551s generic-board-startup.service
 1min 1.691s dev-mmcblk0p1.device
  9.380s udisks2.service

DMESG output snippets

[1.928371] Run /init as init process
[2.920215] [drm] Cannot find any crtc or sizes
[   10.473694] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data
mode. Opts: (null)
[   11.394359] systemd[1]: System time before build time, advancing clock.

SEVEN and a half seconds mounting filesystem

[   14.116062] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro
[