Hi All,
I am using tisdk9.1 from Texas instrument. Here what I am facing is the
I have configured the ip address statically but when we do reboot/power cycle
we are losing ip address configured.
I have found internally that dhcpcd is overwriting existing static ip assigned
to controller.
When I further debug sysctl status this is what I found root@SIEMENS-SEM3T:~#
systemctl status sem3startup.service is the propritery service which we have
run using our custom application
* hostname
State: running
Jobs: 0 queued
Failed: 0 units
Since: Sun 2025-01-26 04:00:38 EST; 6min ago
CGroup: /
|-init.scope
| `- 1 /sbin/init
|-system.slice
| |-avahi-daemon.service
| | |- 231 "avahi-daemon: running [SIEMENS-SEM3T-3.local]"
| | `- 235 "avahi-daemon: chroot helper"
| |-busybox-klogd.service
| | `- 178 /sbin/klogd -n
| |-busybox-syslog.service
| | `- 179 /sbin/syslogd -n
| |-dbus.service
| | `- 180 /usr/bin/dbus-daemon --system --address=systemd: --nofork
--nopidfile --systemd-activation --syslog-only
| |-dhcpcd.service
| | |- 181 "dhcpcd: [manager] [ip4] [ip6]"
| | |- 184 "dhcpcd: [privileged proxy]"
| | |- 185 "dhcpcd: [network proxy]"
| | |- 186 "dhcpcd: [control proxy]"
| | |- 532 "dhcpcd: [BPF BOOTP] eth0"
| | `- 598 "dhcpcd: [BPF ARP] eth0 169.254.251.26"
| |-lighttpd.service
| | `- 410 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf
| |-lldpd.service
| | |- 234 "lldpd: monitor. "
| | `- 279 "lldpd: no neighbor."
| |-ofono.service
| | `- 189 /usr/sbin/ofonod -n
| |-rpcbind.service
| | `- 109 /usr/sbin/rpcbind -w -f
| |-sem3startup.service
| | `- 550 ./core-app
| |-system-getty.slice
| | `-getty@tty1.service
| | `- 255 /sbin/agetty -o "-p -- \\u<file://u>" --noclear - linux
| |-systemd-journald.service
| | `- 110 /lib/systemd/systemd-journald
| |-systemd-logind.service
| | `- 193 /lib/systemd/systemd-logind
| |-systemd-networkd.service
| | `- 205 /lib/systemd/systemd-networkd
| |-systemd-resolved.service
| | `- 221 /lib/systemd/systemd-resolved
| |-systemd-udevd.service
| | `- 130 /lib/systemd/systemd-udevd
| `-systemd-userdbd.service
| |- 302 /lib/systemd/systemd-userdbd
| |- 309 systemd-userwork
| |- 310 systemd-userwork
| `- 311 systemd-userwork
`-user.slice
`-user-0.slice
|-session-c1.scope
| |- 260 /bin/login -p --
| |- 379 -sh
| `- 740 systemctl status
`-user@0.service
`-init.scope
|- 317 /lib/systemd/systemd --user
`- 319 "(sd-pam)"
root@hostnmae:~#
what we have observed is if we run same application (i.e, when we configured ip
statically) in tisdk8.2 even after multiple reboot/power cycle static ip is
persistent.
root@hostname:~# vi 1.txt
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Sun 2025-01-26 03:30:42 EST; 13min ago
CGroup: /
|-user.slice
| `-user-0.slice
| |-session-c1.scope
| | |- 479 /bin/login --
| | |-1066 -sh
| | `-1765 systemctl status
| `-user@0.service ...
| `-init.scope
| |-1058 /lib/systemd/systemd --user
| `-1059 (sd-pam)
|-init.scope
| `-1 /sbin/init
`-system.slice
|-dbus.service
| `-200 /usr/bin/dbus-daemon --system --address=systemd: --nofork
--nopidfile --systemd-activation --syslog-only
|-lldpd.service
| |-454 lldpd: monitor.
| `-537 lldpd: 1 neighbor.
|-avahi-daemon.service
| |-449 avahi-daemon: running [SIEMENS-SEM3T.local]
| `-458 avahi-daemon: chroot helper
|-system-serial\x2dgetty.slice
| |-serial-getty@ttyS3.service<mailto:|-serial-getty@ttyS3.service>
| | `-1764 /sbin/agetty -8 -L ttyS3 115200 xterm
| `-serial-getty@ttyS0.service
| `-1763 /sbin/agetty -8 -L ttyS0 115200 xterm
|-system-getty.slice
| `-getty@tty1.service
| `-474 /sbin/agetty -o -p -- \x5cu --noclear tty1 linux
|-rpcbind.service
| `-113 /usr/sbin/rpcbind -w -f
|-systemd-logind.service
| `-345 /lib/systemd/systemd-logind
|-systemd-resolved.service
| `-412 /lib/systemd/systemd-resolved
|-systemd-udevd.service
| `-129 /lib/systemd/systemd-udevd
|-sem3startup.service
| |-882 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
| `-935 ./core-app
|-ofono.service
| `-219 /usr/sbin/ofonod -n
|-busybox-syslog.service
| `-199 /sbin/syslogd -n
|-systemd-journald.service
| `-114 /lib/systemd/systemd-journald
|-busybox-klogd.service
| `-197 /sbin/klogd -n
`-systemd-networkd.service
`-278 /lib/systemd/systemd-networkd
I found that in latest tisdk9.1 version there is no support for SysV init
scripts only supporting systemd..
Also I am not seeing any init.d scripts/directory
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64688): https://lists.yoctoproject.org/g/yocto/message/64688
Mute This Topic: https://lists.yoctoproject.org/mt/110909970/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
