Hung Boot Android and Recovery Image - UART Output

Products Support DragonBoard410c
#1

Purchased Dragonboard for Coursera course and have not had a successful boot. HDMI Display has only ever come up with the SD Card Android installer.

Recovery Image hangs on boot at:'UDC Start"
[0] [0] BUILD_VERSION=
[0] [0] BUILD_DATE=17:48:57 - May 5 2017
[0] [0] welcome to lk

[10] [10] platform_init()
[10] [10] target_init()
[50] [50] SDHC Running in HS200 mode
[80] [80] Done initialization of the card
[90] [90] pm8x41_get_is_cold_boot: cold boot
[100] [100] Rescue image for DragonBoard 410c, boot into fastboot mode only
[120] [120] Not able to search the panel:
[120] [120] Display not enabled for 24 HW type
[130] [130] Target panel init not found!
[130] [130] pm8x41_get_is_cold_boot: cold boot
[140] [140] fastboot_init()
[150] [150] Loading keystore failed status 5 [250] [250] USB init ept @ 0x8f696000
[270] [270] udc_start()

Android Hangs looking for ipv6 files

9.870505] init: Starting service 'rfs_access'...

[ 9.875758] init: Starting service ‘config_bluetooth’…
[ 9.881298] init: Starting service ‘per_mgr’…
[ 9.895340] init: write_file: Unable to open ‘/proc/sys/net/ipv6/conf/rmnet0/accept_ra’: No such file or directory
[ 9.905059] init: write_file: Unable to open ‘/proc/sys/net/ipv6/conf/rmnet1/accept_ra’: No such file or directory
[ 9.916743] init: write_file: Unable to open ‘/proc/sys/net/ipv6/conf/rmnet2/accept_ra’: No such file or directory
[ 9.926457] init: Service ‘qcom-debug’ (pid 273) exited with status 0
[ 9.932926] init: write_file: Unable to open '/proc/sys/net/ipv6
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start
B - 3498 - bootable_media_detect_entry, Start
B - 168047 - bootable_media_detect_success, Start
B - 168052 - elf_loader_entry, Start
B - 170427 - auth_hash_seg_entry, Start
B - 170639 - auth_hash_seg_exit, Start
B - 186142 - elf_segs_hash_verify_entry, Start
B - 246199 - PBL, Endstrong text

#2

This is normal behaviour for the recovery image: it has started fastboot and is awaiting for instruction via USB on what to flash where.

Regarding the problems you are having with the Android image, which version of Android are you trying to install?

PS New installs take a very long time to complete their initial boot and show a GUI (around three minutes when I tried just now with 16.03), however the log messages you have posted don’t look familiar.

2nd board - Out of the Box - Will not complete boot
#3

Thank you for your reply!

-Apologies then on the recovery image. Another issue for me is getting the usb drivers loaded on windows.

-The Android image was in the ‘Latest’ folder. I tried again this morning with 16.06 with same result indicating failure around the IPV6 loading. I then tried 16.03 and get failure at a different stage. Finally I tried the oldest in the 96boards repository 15.06 and failures at a different task (below)

-Will it reboot several times in the install or just once when it is done?

16.03

[ 12.605548] init: property ‘persist.sys.modem_auth_timeout’ doesn’t exist while expanding ‘${persist.sys.modem_auth_timeout}’
[ 12.616831] init: cannot expand ‘${persist.sys.modem_auth_timeout}’ while writing to ‘/sys/module/pil_msa/parameters/modem_auth_timeout_ms’
[ 12.629478] init: property ‘persist.sys.pil_proxy_timeout’ doesn’t exist while expanding ‘${persist.sys.pil_proxy_timeout}’
[ 12.640435] init: cannot expand ‘${persist.sys.pil_proxy_timeout}’ while writing to ‘/sys/module/peripheral_loader/parameters/proxy_timeout_ms’
[ 12.799586] binder: 247:247 transaction failed 29189, size 0-0
[ 12.868030] init: cannot find ‘/system/bin/cnss_diag’, disabling ‘cnss_diag’
[ 12.877572] init: cannot find ‘/system/bin/dts_configurator’, disabling ‘dts_configurator’
[ 13.121506] enable_store: android_usb: already disabled
[ 13.227409] getprop (291) used greatest stack depth: 11512 bytes left

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start

[ 12.531851] init: property ‘persist.sys.ssr.enable_debug’ doesn’t exist while expanding ‘${persist.sys.ssr.enable_debug}’
[ 12.542292] init: cannot expand ‘${persist.sys.ssr.enable_debug}’ while writing to ‘/sys/module/subsystem_restart/parameters/enable_debug’
[ 12.554668] init: property ‘persist.sys.mba_boot_timeout’ doesn’t exist while expanding ‘${persist.sys.mba_boot_timeout}’
[ 12.565578] init: cannot expand ‘${persist.sys.mba_boot_timeout}’ while writing to ‘/sys/module/pil_msa/parameters/pbl_mba_boot_timeout_ms’
[ 12.578627] init: property ‘persist.sys.modem_auth_timeout’ doesn’t exist while expanding ‘${persist.sys.modem_auth_timeout}’
[ 12.589363] init: cannot expand ‘${persist.sys.modem_auth_timeout}’ while writing to ‘/sys/module/pil_msa/parameters/modem_auth_timeout_ms’
[ 12.601898] init: property ‘persist.sys.pil_proxy_timeout’ doesn’t exist while expanding ‘${persist.sys.pil_proxy_timeout}’
[ 12.612981] init: cannot expand ‘${persist.sys.pil_proxy_timeout}’ while writing to ‘/sys/module/peripheral_loader/parameters/proxy_timeout_ms’
[ 12.730091] binder: 247:247 transaction failed 29189, size 0-0
[ 12.792043] init: cannot find ‘/system/bin/cnss_diag’, disabling ‘cnss_diag’
[ 12.801689] init: cannot find ‘/system/bin/dts_configurator’, disabling ‘dts_configurator’
[ 12.827362] enable_store: android_usb: already disabled

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start

[ 12.531851] init: property ‘persist.sys.ssr.enable_debug’ doesn’t exist while expanding ‘${persist.sys.ssr.enable_debug}’
[ 12.542292] init: cannot expand ‘${persist.sys.ssr.enable_debug}’ while writing to ‘/sys/module/subsystem_restart/parameters/enable_debug’
[ 12.554668] init: property ‘persist.sys.mba_boot_timeout’ doesn’t exist while expanding ‘${persist.sys.mba_boot_timeout}’
[ 12.565578] init: cannot expand ‘${persist.sys.mba_boot_timeout}’ while writing to ‘/sys/module/pil_msa/parameters/pbl_mba_boot_timeout_ms’
[ 12.578627] init: property ‘persist.sys.modem_auth_timeout’ doesn’t exist while expanding ‘${persist.sys.modem_auth_timeout}’
[ 12.589363] init: cannot expand ‘${persist.sys.modem_auth_timeout}’ while writing to ‘/sys/module/pil_msa/parameters/modem_auth_timeout_ms’
[ 12.601898] init: property ‘persist.sys.pil_proxy_timeout’ doesn’t exist while expanding ‘${persist.sys.pil_proxy_timeout}’
[ 12.612981] init: cannot expand ‘${persist.sys.pil_proxy_timeout}’ while writing to ‘/sys/module/peripheral_loader/parameters/proxy_timeout_ms’
[ 12.730091] binder: 247:247 transaction failed 29189, size 0-0
[ 12.792043] init: cannot find ‘/system/bin/cnss_diag’, disabling ‘cnss_diag’
[ 12.801689] init: cannot find ‘/system/bin/dts_configurator’, disabling ‘dts_configurator’
[ 12.827362] enable_store: android_usb: already disabled

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start

15.06

[ 20.283594] binder: 243:243 transaction failed 29189, size 0-0
[ 20.349310] logd.auditd: start
[ 20.435759] warning: `qseecomd’ uses 32-bit capabilities (legacy support in use)
[ 20.669005] avc: denied { set } for property=sys.listeners.registered scontext=u:r:tee:s0 tcontext=u:object_r:system_prop:s0 tclass=property▒ 20.670253] sh (249) used greatest stack depth: 118 80 bytes left
[ 20.686969] mdss_hw_rev_init: MDP Rev=10060000
shell@msm8916_64:/ $ [ 20.734916] init: cannot find ‘/system/bin/cnss_diag’, disabling ‘cnss_diag’
[ 20.751059] init: cannot find ‘/system/bin/qrngd’, disabling ‘qrngd’

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start

[ 20.283594] binder: 243:243 transaction failed 29189, size 0-0
[ 20.349310] logd.auditd: start
[ 20.435759] warning: `qseecomd’ uses 32-bit capabilities (legacy support in use)
[ 20.669005] avc: denied { set } for property=sys.listeners.registered scontext=u:r:tee:s0 tcontext=u:object_r:system_prop:s0 tclass=property▒ 20.670253] sh (249) used greatest stack depth: 118 80 bytes left
[ 20.686969] mdss_hw_rev_init: MDP Rev=10060000
shell@msm8916_64:/ $ [ 20.734916] init: cannot find ‘/system/bin/cnss_diag’, disabling ‘cnss_diag’
[ 20.751059] init: cannot find ‘/system/bin/qrngd’, disabling ‘qrngd’

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start

[ 20.124497] init: cannot expand ‘${persist.sys.pil_proxy_timeout}’ while writing to ‘/sys/module/peripheral_loader/parameters/proxy_timeout_ms’
[ 20.303399] binder: 244:244 transaction failed 29189, size 0-0
[ 20.363054] logd.auditd: start
[ 20.383892] getprop (257) used greatest stack depth: 11448 bytes left
[ 20.473990] warning: `qseecomd’ uses 32-bit capabilities (legacy support in use)
[ 20.701986] mdss_hw_rev_init: MDP Rev=10060000
[ 20.709753] avc: denied { set } for property=sys.listeners.registered scontext=u:r:tee:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service
shell@msm8916_64:/ $ [ 20.775298] init: cannot find ‘/system/bin/cnss_diag’, disabling ‘cnss_diag’
[ 20.790181] init: cannot find ‘/system/bin/qrngd’, disabling ‘qrngd’

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00261
S - IMAGE_VARIANT_STRING=HAAAANAAA
S - OEM_IMAGE_VERSION_STRING=C-BPATTH
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B - 1549 - PBL, Start
B - 3498 - bootable_media_detect_entry, Start

#4

Can we keep this on one thread? I’ll struggle to keep track otherwise…

No particular need to test a whole bunch of different versions. I selected 16.03 because it is (deliberately) what the documentation recommends (I think that is also the version the Coursera material was developed on). Whilst you are trying to get the board(s) to work I suggest you use this as a baseline too.

Anyhow, in the other thread, where you describe the behaviour of a second board, I’ve already asked a question about whether they are using the same power supply. That’s definitely worth exploring further.

If you are interested to compare your boot logs to a working one I’ve recorded a video of the first time boot of 16.03: untitled - asciinema (you can also download the underlying .json file if you want to grep for particular messages). As you will see there are no reboots (other than the one when I powered the board up for the first time).

#5

Yes. Both using same power supply. I went looking for another to try. It’s Output is 9VDC 1A. The original? 9VDC 210mA. I am embarrassed. Both boards now booting into Android with the new supply.

Thank You for your assistance and patience. Also thanks very much for the boot video.

Adam

#6

My pleasure…

To be honest, with a 9W power supply you should probably keep an eye out for funny behaviour if you start plugging in power hungry USB or mezzanine devices. You should be alright with a simple mouse and keyboard but do keep it in mind.

By way of comparison the kit version of the Dragonboard 410C is provided with a 24W power supply!