• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 43 subscribers
  • Views 3674 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

WL18xx driver building - WL18xx_System_Build_Scripts - Database signature verification failure.

Vasantha Ahilan
Prodigy 130 points

Hi,

I am porting the WiFi version R8.5  to our kernel setup as per the the link.processors.wiki.ti.com/.../WL18xx_System_Build_Scripts

But I see that signature verification is failing even though it says build is successful.Could you please provide some support regarding this crda related failure.

build-utilites$./sudo_build_wl18xx.sh update R8.5
:
:
Verifying filesystem skeleton...
Database signature verification failed.
Please update your public key used to verify the DB
Wifi Package Build Successful

 

Thanks,

Vasantha

  • 0
    TI__Guru* 85400 points
    Hi Vasantha,

    Can you manually copy the *.pem file (root.key.pub.pem) from to "ROOTFS/etc/wireless-regdb/pubkeys/" and see if the build is successful?

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Thank you for you immediate response. I am not finding root.key.pub.pem in my PC . which is the path I need to copy from.

    I find pem in the following location

    ROOTFS/etc/wireless-regdb/pubkeys/linville.key.pub.pem
    /build-utilites/src/crda/pubkeys/linville.key.pub.pem

    /lib/crda/pubkeys/linville.key.pub.pem


    /build-utilites/src/wireless_regdb/sforshee.key.pub.pem

    The first three are same the last one is different

  • 0 in reply to Vasantha Ahilan
    TI__Guru* 85400 points
    Hi,

    Please try copying: "sforshee.key.pub.pem" to ROOTFS/etc/wireless-regdb/pubkeys/

    Regards,
    Gigi Joseph.
  • 0 in reply to Vasantha Ahilan
    Prodigy 130 points
    I tried manually tried make and installing the root.key.pub.pem created in /usr/lib/crda/pub-keys by the below process to ROOTFS path but still it fails. please help in sorting this issue
    build-utilities/src/wireless_regdb$ make install
    build-utilites/src/wireless_regdb$ sudo make install
  • 0 in reply to Vasantha Ahilan
    TI__Guru* 85400 points
    Hi Vasantha,

    Have you modified the db.txt from wireless_regdb repository?
    Can you please try the below and let me know the results?

    build-utilities/src/wireless_regdb$ regdbdump regulatory.bin

    If you don't see any error, copy this regulatory.bin file to the ROOTFS and see...

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Hi Gigi ,


    Thanks for the support. No I have not modified the db.txt.

    build-utilites/src/wireless_regdb$ regdbdump regulatory.bin
    Database signature verification failed.

    It is failing.

  • 0 in reply to Joseph Gigi
    Prodigy 130 points
    This didn't help. From what I understand when the script is run /build-utilites/src/crda/pubkeys/linville.key.pub.pem is copied to ROOTFS/etc/wireless-regdb/pubkeys/linville.key.pub.pem
    not the /build-utilites/src/wireless_regdb/sforshee.key.pub.pem

    sudo cp `repo_path wireless_regdb`/regulatory.bin `path filesystem`/usr/lib/crda/regulatory.bin
    sudo cp `repo_path crda`/pubkeys/* `path filesystem`/etc/wireless-regdb/pubkeys/
    cd_repo crda

    I tried copying the /build-utilites/src/wireless_regdb/sforshee.key.pub.pem to ROOTFS/etc/wireless-regdb/pubkeys/
    as sforshee.key.pub.pem /root.key.pub.pem it didn't help.

    All the cases it failed .
  • 0 in reply to Vasantha Ahilan
    TI__Guru* 85400 points
    Hi Vasantha,

    I think you can ignore this as long as "regdbdump" works on the target.
    Is this the case? Please note that you will also have to copy the private key. Usually : "~/.wireless-regdb-root.key.priv.pem".

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    Prodigy 130 points

    Thank you Gigi for your continuing support. Will check in the board and let you know if I face any issues.

    Also I wanted to confirm the following 1. setenv  configured by us is correct for our Yocto kernel 3.4.91  for arm based processor to port the WiFi release R8.5( which is the latest and stable release from TI) ?
    2. I am retaining the export KERNEL_VARIANT=DEFAULT which I wanted to confirm with you in specific if it is ok to use this for our case or should we use anything else.(This uses imx-3.10.53 kernel patches as per my understanding)
    #                            \\\//
    #                           -(o o)-
    #========================oOO==(_)==OOo=======================
    # This file contains the exports needed for automating the
    # build process of WLAN components.
    # Place this file in the same directory with wl18xx_build.sh
    # build scripts. No need to run 'source setup-env', the build
    # scripts will perfom it internaly.
    #===========================================================
    # User specific environment settings - use full PATH

    # if DEFAULT toolchain path is set toolchain will be downloaded to ./toolchain.
    export TOOLCHAIN_PATH=/Yocto1504/build_bin/tmp/sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi

    # if DEFAULT path to root filesystem is set ./fs folder will be used.
    export ROOTFS=/Yocto1504/build_bin/tmp/sysroots/swi-mdm9x15

    #if DEFAULT kernel path is set - kernel will be downloaded (set branch to match kernel version)
    export KERNEL_PATH=/Yocto1504/build_bin/tmp/work/swi_mdm9x15-poky-linux-gnueabi/linux-yocto/3.4.91+gitAUTOINC+b5be1ab688_70dd662ebc-r4.5.1/linux-swi_mdm9x15-standard-build/

    # if KERNEL_VARIANT below is set the build script will look for kernel specific
    # patches under the patches directory:
    # - patches under the pathces/driver_patches/$KERNEL_VARIANT directory would be
    #   applied during "modules" build.
    # - patches under the patches/kernel_patches/$/$KERNEL_VARIANT directory would
    #   be applied to the kernel pointed by KERNEL_PATH in case the "patch_kernel"
    #   command is used.
    #   Note: the kernel is not built automatically after the patches are applied
    export KERNEL_VARIANT=DEFAULT

    export CROSS_COMPILE=arm-poky-linux-gnueabi-
    export ARCH=arm
    [ "$TOOLCHAIN_PATH" != "DEFAULT" ] && export PATH=$TOOLCHAIN_PATH:$PATH

    3. Also I see some rejects happening while building , but I could not find them in the path. Wanted to confirm with you if it is ok to ignore them and consider the WiFi ported successfully as the modules are getting generated? The log is attached for your reference

    Thanks

    7823.Build_log.txt

  • 0 in reply to Vasantha Ahilan
    Prodigy 130 points

    Then followed the command mentioned for porting in TI site.

    ./build_wl18xx.sh init
    ./sudo_build_wl18xx.sh update R8.5

  • 0
    Prodigy 70 points
    Hi Vasantha,

    I got the same error while doing build_wl18xx.sh update R8.7_SP1. I want to know how you fix up this error.


    Thanks,

    Aditya
  • 0 in reply to Aditya Garg
    TI__Mastermind 20285 points
    Hi,
    It may be just false alarm.
    Di you get the file "fs_skeleton.tbz2" under the ./outputs directory?

    In case you have it, you can probably ignore this messge.
    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Prodigy 70 points

    No,I don't get any file under outputs directory

  • 0 in reply to Aditya Garg
    TI__Mastermind 20285 points
    Hi,

    This is probably some local permission issue with your build system.

    All the artifact are created inside the ./fs directory.
    You can manually zip everything in this directory in order to create this tar file.

    BR,
    Eyal