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

[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

[Karishma Jaiswal]

] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   48.872572] wlcore: loaded
[   49.474429] wlcore: PHY firmware version: Rev 8.2.0.0.240
[   49.518365] wlcore: firmware booted (Rev 8.9.0.0.76)
[   49.534132] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   51.541997] wlan0: authenticate with 50:2b:73:2f:60:81
[   51.548875] wlan0: send auth to 50:2b:73:2f:60:81 (try 1/3)
[   51.586392] wlan0: authenticated
[   51.589980] wlan0: associate with 50:2b:73:2f:60:81 (try 1/3)
[   51.599824] wlan0: RX AssocResp from 50:2b:73:2f:60:81 (capab=0xc11 
status=0 aid=9)
[   51.610042] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   51.615269] wlan0: associated
[   51.697657] cryptd: max_cpu_qlen set to 1000
[   51.773890] wlcore: Association completed.
[   62.719318] using random self ethernet address
[   62.719336] using random host ethernet address
[   63.027125] using random self ethernet address
[   63.027142] using random host ethernet address
[   63.193779] usb0: HOST MAC e4:15:f6:f5:8a:0d
[   63.197119] usb0: MAC e4:15:f6:f5:8a:0c
[   63.207435] usb1: HOST MAC e4:15:f6:f5:8a:0f
[   63.208192] usb1: MAC e4:15:f6:f5:8a:10
[   63.359203] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   63.649893] configfs-gadget gadget: high-speed config #1: c
[   63.651463] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   65.017957] Bluetooth: HCI UART driver ver 2.3
[   65.017977] Bluetooth: HCI UART protocol H4 registered
[   65.019448] Bluetooth: HCI UART protocol LL registered
[   65.019458] Bluetooth: HCI UART protocol ATH3K registered
[   65.019595] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   65.883284] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   65.883300] Bluetooth: BNEP filters: protocol multicast
[   65.884153] Bluetooth: BNEP socket layer initialized
[   66.276579] Bluetooth: RFCOMM TTY layer initialized
[   66.276624] Bluetooth: RFCOMM socket layer initialized
[   66.276682] Bluetooth: RFCOMM ver 1.11
 




Can I further reduce the bootup time with few more second?
At-least console message should get display withing 25 sec.?
Can I change any initialization sequence so that I can get the booting 
message more early ?

Thanks
Karishma Jaiswal  
On Tuesday, May 25, 2021 at 10:30:42 PM UTC+5:30 Dennis Bieber wrote:

> 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/aec503e6-05b8-41ef-bad5-6093c41be5b9n%40googlegroups.com.

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

[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

[Karishma Jaiswal]

Hi
>>>So I'd like to pose the question back to the original poster of this 
thread karry@gmail.com <https://groups.google.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.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

[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.

Re: [beagleboard] Reducing Boottime in Beaglebone Black

[Karishma Jaiswal]

Hi
I am working for the boot time optimization for the beagle bone green 
wireless board 
Now with some above mentioned suggestions, I am able to reduce the boot 
time from 90 sec to 45 sec.
But I want to further reduce it to 30 sec.
Please guide me the further points where I can optimize it.
The current detail of my board is as below 

Startup finished in 4.295s (kernel) + 38.147s (userspace) = 42.442s
ubuntu@arm:~$ systemd-analyze -blaim
systemd-analyze: invalid option -- 'b'
ubuntu@arm:~$ systemd-analyze blame
 25.275s console-setup.service
 17.904s dev-mmcblk1p1.device
 15.945s postfix.service
 12.165s generic-board-startup.service
  8.654s apache2.service
  7.635s systemd-logind.service
  6.160s avahi-daemon.service
  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
  2.389s rsyslog.service
  2.073s cpufrequtils.service
  1.535s ssh.service
  1.477s systemd-user-sessions.service
  1.389s pppd-dns.service
  1.151s systemd-udev-trigger.service
  1.040s archive_log.service
  1.011s systemd-journal-flush.service
   979ms rc-local.service
   860ms brltty.service
   653ms keyboard-setup.service
   629ms systemd-journald.service
   609ms tacread-keymap.service
   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

Thanks 
Karishma Jaiswal 
On Friday, May 21, 2021 at 3:55:32 PM UTC+5:30 Amit Goradia wrote:

> Hi Robert,
> I just realized that I need to use an overlayfs (via overlayroot) to 
> protect the emmc / OS from crashing on sudden power off. 
> Now overlaytroot needs the initrd image to work.
> So I had to enable the /boot/initrd.img-4.19.94-ti-rt-r63 file.
> Re-enablingthe initird file in /boot added about 48 to 50s to the kernel 
> boot time ;-(
> Any ideas on how to mitigate that? how to get the booting time down?
> Thanks & Regards,
> -amit
>
> debian@beaglebone:/$ systemd-analyze
> Startup finished in 58.454s (kernel) + 49.641s (userspace) = 1min 48.096s
> debian@beaglebone:/$ systemd-analyze blame
> 1min 21.167s dev-mmcblk1p1.device
>  10.477s generic-board-startup.service
>   5.278s systemd-udev-trigger.service
>   2.907s networking.service
>   2.684s ssh.service
>   2.328s keyboard-setup.service
>   1.940s dnsmasq.service
>   1.661s systemd-journald.service
>   1.101s systemd-user-sessions.service
>895ms systemd-udevd.service
>845ms us...@1001.service
>785ms systemd-random-seed.service
>766ms systemd-timesyncd.service
>754ms systemd-tmpfiles-setup-dev.service
>725ms systemd-modules-load.service
>670ms systemd-update-utmp.service
>657ms systemd-logind.service
>645ms sys-kernel-config.mount
>641ms sys-kernel-debug.mount
>603ms systemd-tmpfiles-setup.service
>572ms kmod-static-nodes.service
>518ms rsyslog.service
>515ms systemd-sysctl.service
>408ms systemd-remount-fs.service
>358ms slim.service
>351ms console-setup.service
>324ms systemd-journal-flush.service
>280ms sys-fs-fuse-connections.mount
>272ms systemd-tmpfiles-clean.service
>228ms systemd-update-utmp-runlevel.service
>223ms dev-mqueue.mount
>
> On Friday, 21 May, 2021 at 12:32:08 pm UTC+5:30 Amit Goradia wrote:
>
>> On Thursday, 20 May, 2021 at 11:01:42 pm UTC+5:30 RobertCNelson wrote:
>>
>>> > removed wpasupplicant and connman and old kernel 
>>> > 
>>> > sudo apt-get purge linux-image-4.14.108-ti-r134 wpasupplicant connman 
>>> > 
>>> > debian@beaglebone:~$ systemd-analyze 
>>> > 
>>> > Startup finished in 13.502s (kernel) + 36.686s (userspace) = 50.188s 
>>> > 
>>> > I then removed the initrd file in /boot directory (From what I 
>>> understand this kernel does not necessarily need initrd). 
>>> > debian@beaglebone:/boot$ sudo mv initrd.img-4.19.94-ti-rt-r63 
>>> moved-initrd.img-4.19.94-ti-rt-r63 
>>> > 
>>> > Removing the initrd gives the max speedup for kernel. From 10s-13s 
>>> with initrd,

Re: [beagleboard] PocketBeagle SD Card Extra Storage

[Karishma jaiswal]

Hi 
I am trying the same thing with Beagle bone green board. 
Can u help me in this as you mentioned that it worked for you.
Thanks
Karishma

On Thursday, February 22, 2018 at 6:11:02 PM UTC+5:30, jackfh...@gmail.com 
wrote:
>
> I've gotten the sd card overlay working, thank you for the help! Now I'm 
> trying to read and write a file to it in python but am struggling finding 
> the directory that it is in. Any idea on how to locate this path?
>
> On Sunday, February 11, 2018 at 11:49:20 PM UTC-6, Jason Kridner wrote:
>>
>> With Robert’s integration, there’s no longer a need to debug my steps. 
>> Use /opt/scripts/tools/update_kernel.sh to get the latest 4.9 kernel. 
>> Googling for that script name should get sufficient instructions. Once on 
>> that kernel, do the /boot/uEnv.txt edit as indicated. 
>>
>> On Feb 11, 2018, at 7:34 PM, jackg...@tamu.edu wrote:
>>
>> Im having trouble executing this command
>>
>>
>> git fetch origin/4.9 --depth 1
>>
>>
>> Im consistently getting the error
>>
>>
>> fatal: 'origin/4.9' does not appear to be a git repository
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.4
>>
>>
>> How can I get the correct access rights to run the 4.9 kernel?
>>
>>
>> On Saturday, February 3, 2018 at 10:18:57 PM UTC-6, Jason Kridner wrote:
>>>
>>> On Fri, Feb 2, 2018 at 5:00 PM Robert Nelson  
>>> wrote:
>>>
 On Fri, Feb 2, 2018 at 9:15 AM, Jack_H  wrote:
 > Hello all.
 >
 >
 >  I was wondering if there were any resources for adding an additional
 > microSD card to the pocketbeagle for storage. I currently have a 
 microSD
 > click from MikroElektronika but it’s not listed under the pocketbeagle
 > "working" mikrobus.

 Oh, that's easy, prove it can work, and provide a pull request here
 for both spix positions:

 https://github.com/beagleboard/bb.org-overlays/

 Then update the wiki.

 Just because I haven't purchased that click doesn't mean it 'will not' 
 work.. ;)


 > I currently have an ethernet click working with my pocketbealge and
 > beaglebone black using very similar code snippets. I have found 
 resources
 > for using a microSD card for the beaglebone black from
 >
 > here
 >
 > and here
 >
 > and this tutorial
 >
 > Will any of this translate over to the pocketbeagle?

 There's a new driver in v4.14.x? and a device tree node; "mmc-slot"
 CONFIG_MMC_SPI


 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt
>>>
>>>
>>> I found it in the 4.9 driver and made an attempt to build it natively as 
>>> a module and give it a try:
>>>
>>> https://gist.github.com/jadonk/53ae22d550021bf32a299acbd7b546aa 
>>>
>>> I optimized the loading time for the git clone with a shallow checkout. 
>>> The build happens pretty fast. It didn't load for me at first. I was able 
>>> to load it, by doing a depmod and modprobe manually, but it never reports 
>>> anything beyond:
>>>
>>> mmc_spi spi2.1: SD/MMC host mmc3, no WP, no poweroff
>>>
>>> So, got any ideas? How should I specify the interrupts?
>>>
>>> sudo apt-get update
>>> sudo apt-get install linux-headers-`uname -r`
>>> cd
>>> mkdir linux
>>> cd linux/
>>> git init
>>> git config core.sparsecheckout true
>>> git remote add origin https://github.com/beagleboard/linux
>>> echo drivers/mmc/host > .git/info/sparse-checkout   
>>> 
>>> git fetch origin/4.9 --depth 1
>>> git checkout 4.9
>>> cd drivers/mmc/host
>>> CONFIG_MMC_SPI=m make -C /lib/modules/`uname -r`/build M=$PWD
>>> sudo make -C /lib/modules/`uname -r`/build M=$PWD 
>>> INSTALL_MOD_DIR=kernel/drivers/mmc/host modules_install
>>>
>>> cd /lib/modules/`uname -r`
>>> sudo depmod -a
>>>
>>> sudo /opt/scripts/tools/developers/update_initrd.sh
>>> cd /opt/source/bb.org-overlays
>>> echo < src/arm/PB-SPI1-MICROSD-CLICK.dts
>>> /*
>>>  * Copyright (C) 2018 Texas Instruments, Jason Kridner 
>>>  *
>>>  * This program is free software; you can redistribute it and/or modify
>>>  * it under the terms of the GNU General Public License version 2 as
>>>  * published by the Free Software Foundation.
>>>  *
>>>  * https://www.mikroe.com/microsd-click
>>>  * 
>>> https://download.mikroe.com/documents/add-on-boards/click/microsd/microsd-click-schematic.pdf
>>>  */
>>>
>>> /dts-v1/;
>>> /plugin/;
>>>
>>> #include 
>>> #include 
>>> #include 
>>>
>>> / {
>>> /*
>>>  * Free up the pins used by the cape from the pinmux helpers.
>>>  */
>>> fragment@0 {
>>> target = <>;
>>> __overlay__ {
>>> P1_36_pinmux { status = "disabled"; };  /* CD - 
>>> gpio3_14*/
>>> P2_25_pinmux { status = "disabled"; };  /* MOSI - 
>>> gpio1_9 */
>>> P2_27_pinmux { status = 

[beagleboard] Re: BeagleBone Black Wireless and I2S audio output

[Karishma jaiswal]

Please help me for the same problem.
I need to play Audio via i2s in beaglebone board.

Thanks



On Friday, September 22, 2017 at 9:17:33 PM UTC+5:30, adrien.c...@gmail.com 
wrote:
>
> Hello everyone,
>
> I need your help.
>
> I have a BeagleBone Black Wireless, on which I installed the standard 
> Jessie Debian distribution.
> I want to add an audio output with the I2S, and i wish to keep HDMI 
> working.
>
> I also have a DAC (Phat DAC) which is originally made for the Raspberry pi 
> zero.
>
> I'm aware that the HDMI chip is receiving the I2S data that is generated 
> by the processor. (see this [article](
> https://hifiduino.wordpress.com/2014/03/10/beaglebone-black-for-audio/) 
> for details)
>
> I have use the BBBW [shematics](
> https://github.com/beagleboard/beaglebone-black-wireless/blob/master/BeagleBone_Black_Wireless_SCH.pdf)
>  
> and the Ohat DAC pinout (did not find the schematics) to connect the 2 
> boards.
>
> connections:
> - GND (phat pin 6, 39 <-> BBB P9_1 )
> - 5V (phat pin 2 & 4 <-> BBB P9_5 & P9_6)
> - 3.3V (phat pin 1 <-> BBB P9_3)
> - I2S LRCLOCK (phat pin 12 <-> BBB P9_28)
> - I2S SCLK / bitclock (phat pin 35 <-> BBB P9_31)
> - I2S data (phat pin 40 <-> BBB P9_29)
>
> To test my speaker output i run
> `$ speaker-test -F S32_LE -f 48000 -c 2`
>
> I have no sound (i also tried with aplay to read WAV files and mplayer 
> just in case)
>
>
> Does anyone has any idea if:
> - my connections are bad
> - if i must connect the HDMI screen to get the audio output on the I2S bus 
> (because of OS settings) *i tried with and without the screen without 
> success*
> - if i have to change the drivers (I've read about the botic driver but 
> the HDMI should send audio on I2S)
>
> ALso in the future i expect to use GPIO3_21 to add a Master clock (as 
> apparently the BBBW is limited to 48kHz sample rate family)
>
> Thank you in advance for any help
>
> Best
>

-- 
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/ef84c136-cf50-4c48-a341-12b79178e278%40googlegroups.com.

[beagleboard] Re: Yocto boot beaglebone green wifi.

[Karishma jaiswal]

were you able to resolve your issue?

On Wednesday, October 2, 2019 at 4:54:17 PM UTC+5:30, phatnguy...@gmail.com 
wrote:
>
> Hi all,
> I use Yocto to create image and boot beaglebone green wifi. like this 
> introdctuion:
>
> https://embeddedguruji.blogspot.com/2019/04/steps-to-build-and-flash-yocto-image-on.html
> After flash process, board turn down, but it's still old image. Please 
> help thank in advance.
> Step1: Create a folder for Yocto source code:
> *$ mkdir beagblebone_yocto && cd beagblebone_yocto*
>
> Step2: Clone the poky source code:
> *$ git clone -b thud git://git.yoctoproject.org/poky.git 
> *
>
> Step3: Run the environment script to setup the Yocto Environment and 
> create build directory
> *$ source poky/oe-init-build-env build*
>
> Step4: Set the MACHINE variable to 'beaglebone-yocto'
> *$ echo 'MACHINE = "beaglebone-yocto"' > conf/local.conf*
>
> Step5: Build the core-image-minimal image
> *$ bitbake core-image-minimal*
>
> After a few hours, you will find the images will be present in 
> *beaglebone_yocto/build/tmp/deploy/images/beaglebone-yocto* folder
>
> Step6: Take memory card and make two partitions using gparted:
> Partition1 : Size 100 MB, fat16 (boot flag)
> Partition2: Size > 2GB , ext4
>
> Step7: Copy the files in the required partition.
> *$ cd beaglebone_yocto/build/tmp/deploy/images/beaglebone-yocto *
> *$ cp MLO-beaglebone-yocto /media/jamal/boot/MLO*
> *$ cp u-boot.img /media/jamal/boot/u-boot.img*
> *$ sudo tar -xf core-image-minimal-beaglebone-yocto.tar.bz2 -C 
> /media/jamal/rootfs*
>
> Step8: Connect the Micro SD Card to the beaglebone black and to boot from 
> MicroSD press the User Button(S2) While applying power. 
>
>
>

-- 
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/b51409ec-4d6f-4e8b-9437-6b1391b92c03%40googlegroups.com.