This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM68: Weston sometimes fails to start after reducing boot time by setting bootdelay=0 and adding quiet to args_mmc

Part Number: SK-AM68
Other Parts Discussed in Thread: AM68,

Cold boot time with these simple changes reduces boot time to about 13 seconds, but Weston sometimes fails to start.

Attaching logs of working vs not working.

Key line is:

[FAILED] Failed to start Weston, a …mpositor, as a system service.

I can run systemctl restart weston and it shows the desktop.

U-Boot 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)

SoC:   J721S2 SR1.0 HS-FS
Model: Texas Instruments AM68 SK
Board: AM68-SK-SOM rev E2
DRAM:  16 GiB
Core:  74 devices, 32 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
574 bytes read in 2 ms (280.3 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
## Error: "main_cpsw0_qsgmii_phyinit" not defined
k3_r5f_rproc r5f@41000000: Core 1 is already in use. No rproc commands work
76376 bytes read in 9 ms (8.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 1 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 2 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 9 ms (8.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 3 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 4 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 9 ms (8.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 5 with data@addr=0x82000000 76376 bytes: Success!
10488888 bytes read in 19 ms (526.5 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 6 with data@addr=0x82000000 10488888 bytes: Success!
10488888 bytes read in 20 ms (500.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 7 with data@addr=0x82000000 10488888 bytes: Success!
20302336 bytes read in 807 ms (24 MiB/s)
80375 bytes read in 7 ms (11 MiB/s)
Working FDT set to 88000000
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 000000008fee9000, end 000000008fffffff ... OK
Working FDT set to 8fee9000

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
[    0.000000] Linux version 6.1.46-g247b2535b2 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Wed Dec  6 17:54:04 UTC 2023
[    0.000000] Machine model: Texas Instruments AM68 SK
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002880000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Reserved shared memory is enabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are disabled
[    0.249915] omap-mailbox 31f80000.mailbox: no available mbox devices found
[    0.256954] omap-mailbox 31f81000.mailbox: no available mbox devices found
[    0.263926] omap-mailbox 31f82000.mailbox: no available mbox devices found
[    0.270861] omap-mailbox 31f83000.mailbox: no available mbox devices found
[    0.277793] omap-mailbox 31f84000.mailbox: no available mbox devices found
[    0.284728] omap-mailbox 31f85000.mailbox: no available mbox devices found
[    0.291658] omap-mailbox 31f86000.mailbox: no available mbox devices found
[    0.298588] omap-mailbox 31f87000.mailbox: no available mbox devices found
[    0.305518] omap-mailbox 31f88000.mailbox: no available mbox devices found
[    0.312453] omap-mailbox 31f89000.mailbox: no available mbox devices found
[    0.319383] omap-mailbox 31f8a000.mailbox: no available mbox devices found
[    0.326314] omap-mailbox 31f8b000.mailbox: no available mbox devices found
[    0.333245] omap-mailbox 31f90000.mailbox: no available mbox devices found
[    0.340174] omap-mailbox 31f91000.mailbox: no available mbox devices found
[    0.347103] omap-mailbox 31f92000.mailbox: no available mbox devices found
[    0.354033] omap-mailbox 31f93000.mailbox: no available mbox devices found
[    0.360962] omap-mailbox 31f94000.mailbox: no available mbox devices found
[    0.367893] omap-mailbox 31f95000.mailbox: no available mbox devices found
[    0.374832] omap-mailbox 31f96000.mailbox: no available mbox devices found
[    0.381764] omap-mailbox 31f97000.mailbox: no available mbox devices found
[    0.388696] omap-mailbox 31f98000.mailbox: no available mbox devices found
[    0.395626] omap-mailbox 31f99000.mailbox: no available mbox devices found
[    0.402558] omap-mailbox 31f9a000.mailbox: no available mbox devices found
[    0.409489] omap-mailbox 31f9b000.mailbox: no available mbox devices found
[    0.465615] debugfs: Directory 'pd:39' with parent 'pm_genpd' already present!
[    0.472930] debugfs: Directory 'pd:38' with parent 'pm_genpd' already present!
[    0.481281] debugfs: Directory 'pd:154' with parent 'pm_genpd' already present!
[    1.479023] systemd[1]: Failed to start Start psplash boot splash screen.
[FAILED] Failed to start Start psplash boot splash screen.
[DEPEND] Dependency failed for Star…progress communication helper.
[    2.641954] k3-dsp-rproc 64800000.dsp: device does not reserved memory regions, ret = -22
[    2.650442] k3-dsp-rproc 64800000.dsp: reserved memory init failed, ret = -22
[    2.678922] k3-dsp-rproc 65800000.dsp: device does not reserved memory regions, ret = -22
[    2.718447] k3-dsp-rproc 65800000.dsp: reserved memory init failed, ret = -22
[    3.250617] platform 41000000.r5f: device does not have reserved memory regions, ret = -22
[    3.325754] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: reserved memory init failed, ret = -22
[    3.368496] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: k3_r5_cluster_rproc_init failed, ret = -22
[    3.428105] platform 5c00000.r5f: device does not have reserved memory regions, ret = -22
[    3.546934] k3_r5_rproc bus@100000:r5fss@5c00000: reserved memory init failed, ret = -22
[    3.570755] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init failed, ret = -22
[FAILED] Failed to start Synchronize System and HW clocks.
[    3.656216] platform 5e00000.r5f: device does not have reserved memory regions, ret = -22
[    3.688679] k3_r5_rproc bus@100000:r5fss@5e00000: reserved memory init failed, ret = -22
[    3.755828] k3_r5_rproc bus@100000:r5fss@5e00000: k3_r5_cluster_rproc_init failed, ret = -22
[FAILED] Failed to start Weston, a …mpositor, as a system service.
***************************************************************
***************************************************************
U-Boot 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)

SoC:   J721S2 SR1.0 HS-FS
Model: Texas Instruments AM68 SK
Board: AM68-SK-SOM rev E2
DRAM:  16 GiB
Core:  74 devices, 32 uclasses, devicetree: separate
Flash: 0 Bytes
MMC:   mmc@4fb0000: 1
Loading Environment from nowhere... OK
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
574 bytes read in 1 ms (560.5 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
## Error: "main_cpsw0_qsgmii_phyinit" not defined
k3_r5f_rproc r5f@41000000: Core 1 is already in use. No rproc commands work
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 1 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 2 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 3 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 4 with data@addr=0x82000000 76376 bytes: Success!
76376 bytes read in 8 ms (9.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 5 with data@addr=0x82000000 76376 bytes: Success!
10488888 bytes read in 19 ms (526.5 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 6 with data@addr=0x82000000 10488888 bytes: Success!
10488888 bytes read in 20 ms (500.1 MiB/s)
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Load Remote Processor 7 with data@addr=0x82000000 10488888 bytes: Success!
20302336 bytes read in 805 ms (24.1 MiB/s)
80375 bytes read in 7 ms (11 MiB/s)
Working FDT set to 88000000
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 000000008fee9000, end 000000008fffffff ... OK
Working FDT set to 8fee9000

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
[    0.000000] Linux version 6.1.46-g247b2535b2 (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Wed Dec  6 17:54:04 UTC 2023
[    0.000000] Machine model: Texas Instruments AM68 SK
[    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002880000 (options '')
[    0.000000] printk: bootconsole [ns16550a0] enabled
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Reserved shared memory is enabled
I/TC: Dynamic shared memory is enabled
I/TC: Normal World virtualization support is disabled
I/TC: Asynchronous notifications are disabled
[    0.245442] omap-mailbox 31f80000.mailbox: no available mbox devices found
[    0.252467] omap-mailbox 31f81000.mailbox: no available mbox devices found
[    0.259425] omap-mailbox 31f82000.mailbox: no available mbox devices found
[    0.266368] omap-mailbox 31f83000.mailbox: no available mbox devices found
[    0.273303] omap-mailbox 31f84000.mailbox: no available mbox devices found
[    0.280236] omap-mailbox 31f85000.mailbox: no available mbox devices found
[    0.287166] omap-mailbox 31f86000.mailbox: no available mbox devices found
[    0.294097] omap-mailbox 31f87000.mailbox: no available mbox devices found
[    0.301029] omap-mailbox 31f88000.mailbox: no available mbox devices found
[    0.307960] omap-mailbox 31f89000.mailbox: no available mbox devices found
[    0.314891] omap-mailbox 31f8a000.mailbox: no available mbox devices found
[    0.321824] omap-mailbox 31f8b000.mailbox: no available mbox devices found
[    0.328756] omap-mailbox 31f90000.mailbox: no available mbox devices found
[    0.335686] omap-mailbox 31f91000.mailbox: no available mbox devices found
[    0.342620] omap-mailbox 31f92000.mailbox: no available mbox devices found
[    0.349554] omap-mailbox 31f93000.mailbox: no available mbox devices found
[    0.356494] omap-mailbox 31f94000.mailbox: no available mbox devices found
[    0.363438] omap-mailbox 31f95000.mailbox: no available mbox devices found
[    0.370397] omap-mailbox 31f96000.mailbox: no available mbox devices found
[    0.377331] omap-mailbox 31f97000.mailbox: no available mbox devices found
[    0.384262] omap-mailbox 31f98000.mailbox: no available mbox devices found
[    0.391197] omap-mailbox 31f99000.mailbox: no available mbox devices found
[    0.398128] omap-mailbox 31f9a000.mailbox: no available mbox devices found
[    0.405060] omap-mailbox 31f9b000.mailbox: no available mbox devices found
[    0.461147] debugfs: Directory 'pd:39' with parent 'pm_genpd' already present!
[    0.468467] debugfs: Directory 'pd:38' with parent 'pm_genpd' already present!
[    0.476779] debugfs: Directory 'pd:154' with parent 'pm_genpd' already present!
[    1.723016] systemd[1]: Failed to start Start psplash boot splash screen.
[FAILED] Failed to start Start psplash boot splash screen.
[DEPEND] Dependency failed for Star…progress communication helper.
[    2.662900] k3-dsp-rproc 64800000.dsp: device does not reserved memory regions, ret = -22
[    2.769607] k3-dsp-rproc 64800000.dsp: reserved memory init failed, ret = -22
[    2.804603] k3-dsp-rproc 65800000.dsp: device does not reserved memory regions, ret = -22
[    2.818446] k3-dsp-rproc 65800000.dsp: reserved memory init failed, ret = -22
[    3.032589] platform 41000000.r5f: device does not have reserved memory regions, ret = -22
[    3.041487] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: reserved memory init failed, ret = -22
[    3.050950] k3_r5_rproc bus@100000:bus@28380000:r5fss@41000000: k3_r5_cluster_rproc_init failed, ret = -22
[    3.152175] platform 5c00000.r5f: device does not have reserved memory regions, ret = -22
[    3.162940] k3_r5_rproc bus@100000:r5fss@5c00000: reserved memory init failed, ret = -22
[    3.171359] k3_r5_rproc bus@100000:r5fss@5c00000: k3_r5_cluster_rproc_init failed, ret = -22
[    3.314681] platform 5e00000.r5f: device does not have reserved memory regions, ret = -22
[    3.323234] k3_r5_rproc bus@100000:r5fss@5e00000: reserved memory init failed, ret = -22
[    3.331466] k3_r5_rproc bus@100000:r5fss@5e00000: k3_r5_cluster_rproc_init failed, ret = -22
[FAILED] Failed to start Synchronize System and HW clocks.
[    6.193592] usb usb1-port1: Cannot enable. Maybe the USB cable is bad?
***************************************************************
***************************************************************

  • Hi Evan,

    I am not sure if I have been able to reproduce the issue you are seeing. I have a SK-AM68 and using the prebuilt default image here: https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM68. I also tested with the edgeai image here: https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM68A

    I get similar logs saying Weston failed to start, yet Weston does start automatically. Attached below are logs:

    U-Boot 2023.04-gb0d868ee08 (Nov 02 2023 - 22:53:54 +0000)
    
    SoC:   J721S2 SR1.0 HS-FS
    Model: Texas Instruments AM68 SK
    Board: AM68-SK-SOM rev E2
    DRAM:  16 GiB
    Core:  74 devices, 32 uclasses, devicetree: separate
    Flash: 0 Bytes
    MMC:   mmc@4fb0000: 1
    Loading Environment from nowhere... OK
    In:    serial@2880000
    Out:   serial@2880000
    Err:   serial@2880000
    am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
    Net:   eth0: ethernet@46000000port@1
    Hit any key to stop autoboot:  0
    switch to partitions #0, OK
    mmc1 is current device
    SD/MMC found on device 1
    Failed to load 'boot.scr'
    1167 bytes read in 1 ms (1.1 MiB/s)
    Loaded env from uEnv.txt
    Importing environment from mmc1 ...
    Running uenvcmd ...
    ## Error: "main_cpsw0_qsgmii_phyinit" not defined
    k3_r5f_rproc r5f@41000000: Core 1 is already in use. No rproc commands work
    67324 bytes read in 8 ms (8 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 1 with data@addr=0x82000000 67324 bytes: Success!
    67324 bytes read in 7 ms (9.2 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 2 with data@addr=0x82000000 67324 bytes: Success!
    67324 bytes read in 8 ms (8 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 3 with data@addr=0x82000000 67324 bytes: Success!
    67324 bytes read in 7 ms (9.2 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 4 with data@addr=0x82000000 67324 bytes: Success!
    67324 bytes read in 8 ms (8 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 5 with data@addr=0x82000000 67324 bytes: Success!
    10488888 bytes read in 18 ms (555.7 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 6 with data@addr=0x82000000 10488888 bytes: Success!
    10488888 bytes read in 19 ms (526.5 MiB/s)
    Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
    Load Remote Processor 7 with data@addr=0x82000000 10488888 bytes: Success!
    21582336 bytes read in 860 ms (23.9 MiB/s)
    80375 bytes read in 6 ms (12.8 MiB/s)
    Working FDT set to 88000000
    10448 bytes read in 3 ms (3.3 MiB/s)
    ## Flattened Device Tree blob at 88000000
       Booting using the fdt blob at 0x88000000
    Working FDT set to 88000000
       Loading Device Tree to 000000008fee9000, end 000000008fffffff ... OK
    Working FDT set to 8fee9000
    
    Starting kernel ...
    
    [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x411fd080]
    [    0.000000] Linux version 6.1.46-g7d494fe58c (oe-user@oe-host) (aarch64-oe-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Thu Nov  2 23:14:33 UTC 2023
    [    0.000000] Machine model: Texas Instruments AM68 SK
    [    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002880000 (options '')
    [    0.000000] printk: bootconsole [ns16550a0] enabled
    I/TC: Secondary CPU 1 initializing
    I/TC: Secondary CPU 1 switching to normal world boot
    I/TC: Reserved shared memory is enabled
    I/TC: Dynamic shared memory is enabled
    I/TC: Normal World virtualization support is disabled
    I/TC: Asynchronous notifications are disabled
    [    0.296836] debugfs: Directory 'pd:39' with parent 'pm_genpd' already present!
    [    0.304152] debugfs: Directory 'pd:38' with parent 'pm_genpd' already present!
    [    0.312471] debugfs: Directory 'pd:154' with parent 'pm_genpd' already present!
    [    1.072476] systemd[1]: Failed to start Start psplash boot splash screen.
    [FAILED] Failed to start Start psplash boot splash screen.
    [DEPEND] Dependency failed for Star…progress communication helper.
    [FAILED] Failed to start Print notice about GPLv3 packages.
    [FAILED] Failed to start Enable and…figure wl18xx bluetooth stack.
    [FAILED] Failed to start Synchronize System and HW clocks.
    [FAILED] Failed to start Weston, a …mpositor, as a system service.
    [FAILED] Failed to start Weston, a …mpositor, as a system service.
    
     _____                    _____           _         _
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|
    
    Arago Project am68-sk -
    
    Arago 2023.04 am68-sk -
    
    am68-sk login: root
    root@am68-sk:~# glmark2-es2-wayland
    =======================================================
        glmark2 2021.12
    =======================================================
        OpenGL Information
        GL_VENDOR:     Imagination Technologies
        GL_RENDERER:   PowerVR B-Series BXS-4-64
        GL_VERSION:    OpenGL ES 3.2 build 23.2@6460340
    =======================================================
    [build] use-vbo=false:^C FPS: 616 FrameTime: 1.623 ms
    

    After booting up, I am able to start applications that depend on Weston/Wayland being up, such as glmark2-es2-wayland, and these applications seem to run fine.

    To understand the behavior being seen on your end, could you clarify which SDK and SDK version number is being used, and whether this is a prebuilt SD card image or an image that has some custom changes to the Linux kernel (other than the changes to U-Boot environment variables).

    And are you seeing that Weston comes up automatically even when there are failures, or if the Weston initialization failure message is seen Weston needs to be manually started for any application that depends on Weston to be started?

    Regards,

    Takuma

  • Hi Takuma,

    I'm doing a TI yocto build using config file processor-sdk-analytics-09.01.00-config.txt

    MACHINE=j721s2-evm bitbake tisdk-default-image

    I am not using branding or real-time in this build.

    It looks like your build has weston service running with Restart=always, or something triggering the weston systemd socket, but mine does not.

    I confirmed adding Restart=always allows it to come up and show a similar log (failing twice, then appearing)
  • Hi Evan,

    Ok, understood. I'll let our SDK team know and see if we can fix this, but fixes will most likely not be in the next release as the release is coming up soon. We will see if we can address this in a future release.

    However, in the meantime, would having Restart=always suffice for the purpose of your use case?

    Regards,

    Takuma

  • Hi Takuma,

    Yes, using Restart=always will work for our use-case.

    Thanks