Boot process issue | i.MX6Q Sabreauto

cancel
Showing results for 
Search instead for 
Did you mean: 

Boot process issue | i.MX6Q Sabreauto

Jump to solution
624 Views
engineer_bsp01
Contributor III

Hi,

Iam building android 7.1.2 SabreAuto BSP for our board ,successfully  flashed images into 16Gb microSD card using script fsl-sd-card-partition.shwhich is attached below.But when we powered on our board it boots up showing bootanimation and it get stuck showing boot image as shown below.IMG_20190625_163715.jpg

 Complete debug log is attached along with this.

    Console: switching to colour dummy device 80x30
    watchdogd: started (interval 10, margin 20)!
    EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode. Opts: barrier=1
    EXT4-fs (mmcblk2p10): Ignoring removed nomblk_io_submit option
    EXT4-fs (mmcblk2p10): recovery complete
    EXT4-fs (mmcblk2p10): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,noauto_da_alloc,errors=panic
    EXT4-fs (mmcblk2p4): Ignoring removed nomblk_io_submit option
    EXT4-fs (mmcblk2p4): recovery complete
    EXT4-fs (mmcblk2p4): mounted filesystem with ordered data mode. Opts: nomblk_io_submit
    EXT4-fs (mmcblk2p5): bad geometry: block count 393216 exceeds size of device (2048 blocks)
    file system registered
    using random self ethernet address
    using random host ethernet address
    zram0: detected capacity change from 0 to 314572800
    logd.auditd: start
    logd.klogd: 6305556999
    Adding 307196k swap on /dev/block/zram0. Priority:-1 extents:1 across:307196k SS
    (stk) :ldisc installation timeout(stk) :ldisc_install = 0
    binder: 254:254 transaction failed 29189, size 0-0
    type=1400 audit(456.240:4): avc: denied { chown } for pid=256 comm="uim-sysfs" capability=0 scontext=u:r:hci_attach:s0 tcontext=u:r:hci_attach:s0 tclass=capability permissive=0
    read descriptors
    read strings
    logd.daemon: reinit
    sabreauto_6q:/ # android_work: sent uevent USB_STATE=CONNECTED
    android_work: sent uevent USB_STATE=DISCONNECTED
    android_work: sent uevent USB_STATE=CONNECTED
    configfs-gadget gadget: high-speed config #1: b
    android_work: sent uevent USB_STATE=CONFIGURED
    (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1
    type=1400 audit(457.120:5): avc: denied { dac_override } for pid=256 comm="uim-sysfs" capability=1 scontext=u:r:hci_attach:s0 tcontext=u:r:hci_attach:s0 tclass=capability permissive=0
    healthd: No battery devices found
    (stk) :ldisc installation timeout(stk) :ldisc_install = 0
    (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1
    type=1400 audit(459.280:6): avc: denied { dac_override } for pid=256 comm="uim-sysfs" capability=1 scontext=u:r:hci_attach:s0 tcontext=u:r:hci_attach:s0 tclass=capability permissive=0
    (stk) :ldisc installation timeout(stk) :ldisc_install = 0
    (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1
    type=1400 audit(461.440:7): avc: denied { dac_override } for pid=256 comm="uim-sysfs" capability=1 scontext=u:r:hci_attach:s0 tcontext=u:r:hci_attach:s0 tclass=capability permissive=0
    (stk) :ldisc installation timeout(stk) :ldisc_install = 0
    (stk) : timed out waiting for ldisc to be un-installed(stk) :ldisc_install = 1
    type=1400 audit(463.600:8): avc: denied { dac_override } for pid=256 comm="uim-sysfs" capability=1 scontext=u:r:hci_attach:s0 tcontext=u:r:hci_attach:s0 tclass=capability permissive=0
    (stk) :ldisc installation timeout(stk) :ldisc_install = 0
    (stk) : timed out waiting for ldisc to be un-installedBluetooth: st_register failed -22
    random: crng init done
    android_work: sent uevent USB_STATE=DISCONNECTED
    init: write_file: Unable to write to '/config/usb_gadget/g1/UDC': Device or resource busy
    android_work: sent uevent USB_STATE=CONNECTED
    android_work: sent uevent USB_STATE=DISCONNECTED
    android_work: sent uevent USB_STATE=CONNECTED
    configfs-gadget gadget: high-speed config #1: b
    android_work: sent uevent USB_STATE=CONFIGURED

    Can anyone help me to resolve this?Its urgent!

    Note:  I tried with MFG tools and gets  otg works for loading u-boot and other binaries to ram . Its just mfgtool after "Jumping to OS" it stays at No Device connected"so tried using fsl-sd-card-partition.sh.

    Thanks,

    Richu

    jimmychanigorpadykovqiusheng

    jimmychannikolaos.pasaloukos@andromedadigital.com

    0 Kudos
    1 Solution
    356 Views
    igorpadykov
    NXP TechSupport
    NXP TechSupport

    Hi Richu

    one can try with other sd cards, preferably brand new.

    Best regards
    igor

    View solution in original post

    0 Kudos
    5 Replies
    356 Views
    engineer_bsp01
    Contributor III

    Hi igor,

    Thanks for your prompt reply.

    Actually the board was booting  with out any issues with the same images in another sd card.Unfortunately i lost that sd card and brought another sd card.

    • Boot hangs after "random: crng init done"(log attached above) what that line means.
    • Is there any difference in flashing using MFG tool and fsl-sd-card-partition.sh script(attached above).
    • Is there any changes has to be done in fsl-sd-card-partion.sh

    working sd card log

    old_LI.jpg

    new sd card log

    newsd_LI.jpg

    both are part of logs of two sd cards(full log is attached along with this)

    as you can see filesystem is not getting mounted in mmcblk2p5 in new sd card.

    Is that flashed properly??

    Please help me to resolve?

    Thanks,

    Richu

    0 Kudos
    357 Views
    igorpadykov
    NXP TechSupport
    NXP TechSupport

    Hi Richu

    one can try with other sd cards, preferably brand new.

    Best regards
    igor

    View solution in original post

    0 Kudos
    356 Views
    engineer_bsp01
    Contributor III

    Hi igor,

    I finally got this work when execute commands in fsl-csrd-partition.sh manually.

    0 Kudos
    303 Views
    vinays
    Contributor II

    Hi Richu,

    I am also facing the same issue now, executing the script commands manually means do we need to partition the sd card manually using the gdisk command and copy the respective files to the sd card partitions?

    Regards,

    Parvathi.

     

    0 Kudos
    356 Views
    igorpadykov
    NXP TechSupport
    NXP TechSupport

    Hi RICHU

    one can try to run latest ddr test

    i.MX6/7 DDR Stress Test Tool V3.00 

    and rebuild image with updated ddr calibration coefficients found from ddr test

    in uboot ..freescale/mx7dsabresd/*.cfg file

    Best regards
    igor
    -----------------------------------------------------------------------------------------------------------------------
    Note: If this post answers your question, please click the Correct Answer button. Thank you!
    -----------------------------------------------------------------------------------------------------------------------

    0 Kudos