how to start your application on boot in yocto

-
1. Create "recipes-support" folder in your own custom layer
2. Inside the "recipes-support" folder, create a folder for example "test"
3. Inside "test" folder, create "test" recipe, $touch test_0.1.bb
4. Open test_0.1.bb and update it with the following:

SUMMARY = "Test Application"
LICENSE = "CLOSED"

inherit update-rc.d
SRC_URI = "file://test.c \

       "

do_compile () {
    ${CC} ${CFLAGS} ${LDFLAGS} ${WORKDIR}/test.c  -o ${WORKDIR}/test
}

do_install () {
    install -d ${D}${sysconfdir}/init.d
    install -m 0755 ${WORKDIR}/test_service ${D}${sysconfdir}/init.d/test_service

    install -d ${D}${sbindir}
    install -m 0755 ${WORKDIR}/test ${D}${sbindir}/
}

INITSCRIPT_NAME = "test_service"
INITSCRIPT_PARAMS = "start 99 1 2 3 4 5 . stop 20 0 1 6 ."
RDEPENDS_${PN} = "initscripts"
CONFFILES_${PN} += "${sysconfdir}/init.d/test_service"


5. Make sure you create "files" folder and put test.c, and test_service in it

test_service:

case "$1" in
  start)
    echo -n "Starting test application: "
    start-stop-daemon --start --exec  /usr/sbin/test
    echo "done"
    ;;  
  stop)
    echo -n "Stopping test application"
    start-stop-daemon --stop --exec /usr/sbin/test
    echo "done"
    ;;  
  restart)
    $0 stop
    $0 start
    ;;  
  *)  
    echo "Usage: test_service { start | stop | restart }" >&2
    exit 1
    ;;
esac

exit 0




Comments

  1. Rohit29 September 2021 at 23:36

    INITSCRIPT_PARAMS = "start 99 1 2 3 4 5 . stop 20 0 1 6 ." Can you explain more on this?

    ReplyDelete
  2. Topper9 November 2021 at 04:27

    Here it is, that's init levels
    https://www.linux.com/news/introduction-services-runlevels-and-rcd-scripts/

    ReplyDelete
  3. Unknown3 January 2022 at 04:59

    Hello,
    I tried your example with hello.c to print "hello world" in boot
    My bb file is:
    DESCRIPTION = "A friendly program that prints Hello World!"
    PRIORITY = "optional"
    SECTION = "examples"
    LICENSE = "MIT"
    LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
    inherit update-rc.d
    SRC_URI = "file://hello.c"
    S = "${WORKDIR}"
    do_compile() {
    ${CC} ${CFLAGS} ${LDFLAGS} hello.c -o hello
    }
    do_install() {
    install -d ${D}${bindir}
    install -m 0755 hello ${D}${bindir}
    install -d ${D}${sysconfdir}/init.d
    install -m 0755 test_service ${D}${sysconfdir}/init.d/test_service
    }

    INITSCRIPT_NAME = "test_service"
    INITSCRIPT_PARAMS = "start 99 1 2 3 4 5 . stop 20 0 1 6 ."
    RDEPENDS_${PN} = "initscripts"
    CONFFILES_${PN} += "${sysconfdir}/init.d/test_service"


    But i have an error in do_install, can you help me?

    ReplyDelete
    Replies
    1. Saddem24 January 2022 at 19:49

      I had the same problem, I have solved it by simply adding test_service into SRC_URI

      SRC_URI = "file://hello.c \
      file://test_service \
      "

      Delete
  4. Anonymous9 February 2022 at 22:42

    I'm getting this error.
    ERROR: ParseError at /home/prutha/02_02_2022/poky/meta-mylayer/recipes-support/test/test_0.1.bb:9: unparsed line: 'do_compile ()'

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more