Can't flash OS to eMMC and no HDMI monitor output on DragonBoard410c


#1

Hello,

My dragonboard 410c(db410c) was running Android 5.1 and was working just fine for the past 5 months, but today when i tried to unlock it, the db410c hanged at boot. I powered it off and on manually and then it wasn’t booting, no HDMI monitor output, no LED indication that the boot process took place and it can’t enter fastboot. I connected it to UART and there were no logs.

My goal is to flash Android again.

I followed this guide with Shanpshot99 SD card image to recover the db410c. It boots from the SD card and i can see the logs from the boot phase. Finally enters the buildroot prompt where i can successfully log in with username “root”, but there is no HDMI monitor output where accorrding to the guide i am supposed to flash an image to eMMC with the GUI and reboot.

logs from booting phase

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, 0x000002e3
S - Core 0 Frequency, 0 MHz
B - 1547 - PBL, Start
B - 3493 - bootable_media_detect_entry, Start
B - 270853 - bootable_media_detect_success, Start
B - 270858 - elf_loader_entry, Start
B - 274871 - auth_hash_seg_entry, Start
B - 275081 - auth_hash_seg_exit, Start
B - 307500 - elf_segs_hash_verify_entry, Start
B - 366728 - PBL, End
B - 297832 - SBL1, Start
B - 348066 - pm_device_init, Start
D - 14243 - pm_device_init, Delta
B - 362797 - boot_flash_init, Start
D - 0 - boot_flash_init, Delta
B - 366823 - boot_config_data_table_init, Start
D - 165554 - boot_config_data_table_init, Delta - (0 Bytes)
B - 536952 - CDT version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B - 543144 - sbl1_ddr_set_params, Start
B - 546834 - cpr_init, Start
D - 0 - cpr_init, Delta
B - 552477 - Pre_DDR_clock_init, Start
D - 213 - Pre_DDR_clock_init, Delta
D - 0 - sbl1_ddr_set_params, Delta
B - 564982 - pm_driver_init, Start
D - 6832 - pm_driver_init, Delta
B - 580476 - clock_init, Start
D - 30 - clock_init, Delta
B - 590632 - Image Load, Start
D - 63532 - QSEE Image Loaded, Delta - (460664 Bytes)
B - 654194 - Image Load, Start
D - 1555 - SEC Image Loaded, Delta - (2048 Bytes)
B - 661301 - sbl1_efs_handle_cookies, Start
D - 0 - sbl1_efs_handle_cookies, Delta
B - 669200 - Image Load, Start
D - 18819 - QHEE Image Loaded, Delta - (51952 Bytes)
B - 688049 - Image Load, Start
D - 28487 - RPM Image Loaded, Delta - (149492 Bytes)
B - 716536 - Image Load, Start
D - 30775 - APPSBL Image Loaded, Delta - (479072 Bytes)
B - 747341 - QSEE Execution, Start
D - 61 - QSEE Execution, Delta
B - 753014 - SBL1, End
D - 457561 - SBL1, Delta
S - Flash Throughput, 42000 KB/s (1143228 Bytes, 26657 us)
S - DDR Frequency, 400 MHz
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk

[10] platform_init()
[10] target_init()
[20] initialising mmc_slot =2
[20] Error: Command timeout error
[20] Failure getting OCR response from MMC Card
[30] MMC card failed to respond, try for SD card
[90] Done initialization of the card
[90] pm8x41_get_is_cold_boot: cold boot
[90] Not able to search the panel:
[100] Display not enabled for 24 HW type
[100] Target panel init not found!
[100] pm8x41_get_is_cold_boot: cold boot
[110] partition misc doesn’t exist
[110] error in emmc_recovery_init
[110] Unable to locate /bootselect partition
[120] No ‘misc’ partition found
[120] Error reading MISC partition
[120] failed to get ffbm cookie[130] use_signed_kernel=0, is_unlocked=0, is_tampered=0.
[130] Loading boot image (35387392): start
[1940] Loading boot image (35387392): done
[2190] DTB Total entry: 15, DTB version: 2
[2200] Using DTB entry 0x000000f7/00000000/0x00010018/0 for device 0x000000f7/00010000/0x00010018/0
[2210] Using pmic info 0x2000b/0x0/0x0/0x0 for device 0x2000b/0x0/0x0/0x0
[2210] cmdline: root=/dev/ram0 rw rootwait console=ttyMSM0,115200n8 androidboot.emmc=true androidboot.serialno=153a9dd0 androidboot.baseband=apq mdss_mdp.panel=0:dsi:0:[2230] Updating device tree: start
[2300] Updating device tree: done
[2300] Error: Command timeout error
[2310] card sleep error: mmc_put_card_to_sleep
[2310] booting linux @ 0x80080000, ramdisk @ 0x82000000 (25272261), tags/device tree @ 0x81e00000
[2320] Jumping to kernel via monitor
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.0.0-00920-gcf20a91 (ndec@nikaia) (gcc version 4.9.2 20140904 (prerelease) (crosstool-NG linaro-1.13.1-4.9-2014.09 - Linaro GCC 4.9-2014.09) ) #25 SMP PREEMPT Wed Jun 17 09:43:51 CEST 2015
[ 0.000000] CPU: AArch64 Processor [410fd030] revision 0
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] alternatives: enabling workaround for ARM errata 826319, 827319, 824069
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created CMA memory pool at 0x0000000086000000, size 8 MiB
[ 0.000000] Reserved memory: initialized node external_image_region@86000000, compatible id removed-dma-pool
[ 0.000000] Reserved memory: created CMA memory pool at 0x0000000086800000, size 78 MiB
[ 0.000000] Reserved memory: initialized node modem_adsp_region@86800000, compatible id removed-dma-pool
[ 0.000000] Reserved memory: created CMA memory pool at 0x000000008b600000, size 6 MiB
[ 0.000000] Reserved memory: initialized node peripheral_region@8b600000, compatible id removed-dma-pool
[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000b9000000, size 112 MiB
[ 0.000000] Reserved memory: initialized node secure_region, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created CMA memory pool at 0x000000008ec00000, size 20 MiB
[ 0.000000] Reserved memory: initialized node venus_qseecom_region, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created CMA memory pool at 0x00000000b8c00000, size 4 MiB
[ 0.000000] Reserved memory: initialized node audio_region, compatible id shared-dma-pool
[ 0.000000] cma: Reserved 64 MiB at 0x00000000b4c00000
[ 0.000000] PERCPU: Embedded 14 pages/cpu @ffffffc034b76000 s19328 r8192 d29824 u57344
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 234864
[ 0.000000] Kernel command line: root=/dev/ram0 rw rootwait console=ttyMSM0,115200n8 androidboot.emmc=true androidboot.serialno=153a9dd0 androidboot.baseband=apq mdss_mdp.panel=0:dsi:0:
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.000000] software IO TLB [mem 0xaf800000-0xb3800000] (64MB) mapped at [ffffffc02f800000-ffffffc0337fffff]
[ 0.000000] Memory: 618196K/954368K available (6496K kernel code, 425K rwdata, 2560K rodata, 268K init, 2246K bss, 131372K reserved, 204800K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vmalloc : 0xffffff8000000000 - 0xffffffbdbfff0000 ( 246 GB)
[ 0.000000] vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum)
[ 0.000000] 0xffffffbdc2000000 - 0xffffffbdc3000000 ( 16 MB actual)
[ 0.000000] fixed : 0xffffffbffabfe000 - 0xffffffbffac00000 ( 8 KB)
[ 0.000000] PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000 ( 16 MB)
[ 0.000000] modules : 0xffffffbffc000000 - 0xffffffc000000000 ( 64 MB)
[ 0.000000] memory : 0xffffffc000000000 - 0xffffffc040000000 ( 1024 MB)
[ 0.000000] .init : 0xffffffc00095b000 - 0xffffffc00099e000 ( 268 KB)
[ 0.000000] .text : 0xffffffc000080000 - 0xffffffc00095a324 ( 9065 KB)
[ 0.000000] .data : 0xffffffc0009a3000 - 0xffffffc000a0d600 ( 426 KB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[ 0.000000] NR_IRQS:64 nr_irqs:64 0
[ 0.000000] Architected cp15 and mmio timer(s) running at 19.20MHz (virt/virt).
[ 0.000005] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 3579139424256ns
[ 0.000240] Console: colour dummy device 80x25
[ 0.000256] Calibrating delay loop (skipped), value calculated using timer frequency… 38.40 BogoMIPS (lpj=192000)
[ 0.000266] pid_max: default: 32768 minimum: 301
[ 0.000329] Security Framework initialized
[ 0.000376] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.000385] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.000915] Initializing cgroup subsys blkio
[ 0.000929] Initializing cgroup subsys memory
[ 0.000955] Initializing cgroup subsys devices
[ 0.000966] Initializing cgroup subsys hugetlb
[ 0.001258] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 7 counters available
[ 0.001289] EFI services will not be available.
[ 0.079992] CPU1: Booted secondary processor
[ 0.080003] Detected VIPT I-cache on CPU1
[ 0.099971] CPU2: Booted secondary processor
[ 0.099990] Detected VIPT I-cache on CPU2
[ 0.119976] CPU3: Booted secondary processor
[ 0.119985] Detected VIPT I-cache on CPU3
[ 0.120051] Brought up 4 CPUs
[ 0.120076] SMP: Total of 4 processors activated.
[ 0.120098] alternatives: patching kernel code
[ 0.120548] devtmpfs: initialized
[ 0.121364] DMI not present or invalid.
[ 0.127072] pinctrl core: initialized pinctrl subsystem
[ 0.138913] NET: Registered protocol family 16
[ 0.169732] cpuidle: using governor ladder
[ 0.199746] cpuidle: using governor menu
[ 0.199910] vdso: 2 pages (1 code @ ffffffc0009a9000, 1 data @ ffffffc0009a8000)
[ 0.199953] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.200709] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.200794] msm_smd_init: unable to create SMD logging context
[ 0.200800] msm_smd_init: unable to create SMSM logging context
[ 0.200989] msm_smem_init: unable to create logging context
[ 0.201188] Serial: AMBA PL011 UART driver
[ 0.204574] msm_smd_probe: enable_irq_wake() failed on 130
[ 0.204586] smd_channel_probe_now: allocation table not initialized
[ 0.204836] msm_smsm_probe: enable_irq_wake() failed on 131
[ 0.205279] msm_smd_probe: enable_irq_wake() failed on 132
[ 0.205289] smd_channel_probe_now: allocation table not initialized
[ 0.205540] msm_smsm_probe: enable_irq_wake() failed on 133
[ 0.205808] msm_smd_probe: enable_irq_wake() failed on 134
[ 0.225021] platform a21b000.qcom,pronto: assigned reserved memory node peripheral_region@8b600000
[ 0.225136] platform 1de0000.qcom,venus: assigned reserved memory node venus_qseecom_region
[ 0.225972] irq: no irq domain found for /soc/qcom,mdss_mdp@1a00000 !
[ 0.262186] msm_iommu 1f00000.qcom,iommu: invalid resource
[ 0.262287] msm_iommu 1f00000.qcom,iommu: iface: 100000000, core: 0
[ 0.262309] msm_iommu 1f00000.qcom,iommu: device gfx_iommu (model: 500) mapped at ffffff80003a0000, with 2 ctx banks
[ 0.262399] genirq: Setting trigger mode 1 for irq 153 failed (gic_set_type+0x0/0xdc)
[ 0.262460] msm_iommu 1f00000.qcom,iommu: Request Global CFG IRQ 153 failed with ret=-22
[ 0.263021] msm_iommu 1e00000.qcom,iommu: iface: 100000000, core: 0
[ 0.263058] msm_iommu 1e00000.qcom,iommu: device apps_iommu (model: 500) mapped at ffffff8000680000, with 20 ctx banks
[ 0.263156] genirq: Setting trigger mode 1 for irq 153 failed (gic_set_type+0x0/0xdc)
[ 0.263202] msm_iommu 1e00000.qcom,iommu: Request Global CFG IRQ 153 failed with ret=-22
[ 0.267439] msm_iommu_ctx 1f09000.qcom,iommu-ctx: context gfx3d_user using bank 1
[ 0.267597] msm_iommu_ctx 1f0a000.qcom,iommu-ctx: context gfx3d_priv using bank 2
[ 0.267746] msm_iommu_ctx 1e22000.qcom,iommu-ctx: context jpeg_enc0 using bank 2
[ 0.267867] msm_iommu_ctx 1e23000.qcom,iommu-ctx: context vfe using bank 3
[ 0.267987] msm_iommu_ctx 1e24000.qcom,iommu-ctx: context mdp_0 using bank 4
[ 0.268106] msm_iommu_ctx 1e25000.qcom,iommu-ctx: context venus_ns using bank 5
[ 0.268228] msm_iommu_ctx 1e26000.qcom,iommu-ctx: context cpp using bank 6
[ 0.268346] msm_iommu_ctx 1e27000.qcom,iommu-ctx: context mDSP using bank 7
[ 0.268465] msm_iommu_ctx 1e28000.qcom,iommu-ctx: context gss using bank 8
[ 0.268583] msm_iommu_ctx 1e29000.qcom,iommu-ctx: context a2 using bank 9
[ 0.268709] msm_iommu_ctx 1e32000.qcom,iommu-ctx: context mdp_1 using bank 18
[ 0.268837] msm_iommu_ctx 1e33000.qcom,iommu-ctx: context venus_sec_pixel using bank 19
[ 0.268957] msm_iommu_ctx 1e34000.qcom,iommu-ctx: context venus_sec_bitstream using bank 20
[ 0.269081] msm_iommu_ctx 1e35000.qcom,iommu-ctx: context venus_sec_non_pixel using bank 21
[ 0.269200] msm_iommu_ctx 1e36000.qcom,iommu-ctx: context venus_fw using bank 22
[ 0.269325] msm_iommu_ctx 1e37000.qcom,iommu-ctx: context periph_rpm using bank 23
[ 0.269445] msm_iommu_ctx 1e38000.qcom,iommu-ctx: context periph_CE using bank 24
[ 0.269566] msm_iommu_ctx 1e39000.qcom,iommu-ctx: context periph_BLSP using bank 25
[ 0.269688] msm_iommu_ctx 1e3a000.qcom,iommu-ctx: context periph_SDC1 using bank 26
[ 0.269809] msm_iommu_ctx 1e3b000.qcom,iommu-ctx: context periph_SDC2 using bank 27
[ 0.269942] msm_iommu_ctx 1e3c000.qcom,iommu-ctx: context periph_audio using bank 28
[ 0.270062] msm_iommu_ctx 1e3d000.qcom,iommu-ctx: context periph_USB_HS1 using bank 29
[ 0.270483] qcom_iommu: iommu sec: psize[0]: 94208, psize[1]: 0
[ 0.270833] vgaarb: loaded
[ 0.271105] SCSI subsystem initialized
[ 0.271466] usbcore: registered new interface driver usbfs
[ 0.271515] usbcore: registered new interface driver hub
[ 0.271573] usbcore: registered new device driver usb
[ 0.272328] Advanced Linux Sound Architecture Driver Initialized.
[ 0.273311] cfg80211: Calling CRDA to update world regulatory domain
[ 0.273340] Switched to clocksource arch_sys_counter
[ 0.280630] NET: Registered protocol family 2
[ 0.281135] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.281246] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[ 0.281432] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.281491] TCP: reno registered
[ 0.281503] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.281540] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.281701] NET: Registered protocol family 1
[ 0.281894] RPC: Registered named UNIX socket transport module.
[ 0.281902] RPC: Registered udp transport module.
[ 0.281907] RPC: Registered tcp transport module.
[ 0.281913] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.282096] Unpacking initramfs…
[ 1.655909] Freeing initrd memory: 24676K (ffffffc002000000 - ffffffc003819000)
[ 1.656412] kvm [1]: HYP mode not available
[ 1.657843] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 1.657956] audit: initializing netlink subsys (disabled)
[ 1.657995] audit: type=2000 audit(1.649:1): initialized
[ 1.658419] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 1.666042] VFS: Disk quotas dquot_6.5.2
[ 1.666210] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.669141] fuse init (API version 7.23)
[ 1.669618] 9p: Installing v9fs 9p2000 file system support
[ 1.670692] io scheduler noop registered
[ 1.670975] io scheduler cfq registered (default)
[ 1.672866] pil: failed to find qcom,msm-imem-pil node
[ 1.673017] pil_tz_driver_probe: enter
[ 1.673890] venus: Power-on latency exceeded, new value 25833 ns
[ 1.673898] pil_tz_driver_probe: enter
[ 1.677494] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 1.678962] msm_serial 78b0000.serial: msm_serial: detected port #0
[ 1.679058] msm_serial 78b0000.serial: uartclk = 3686400
[ 1.679106] 78b0000.serial: ttyMSM0 at MMIO 0x78b0000 (irq = 135, base_baud = 230400) is a MSM
[ 1.679277] msm_serial: console setup on port #0
[ 2.736461] console [ttyMSM0] enabled
[ 2.741511] msm_serial: driver initialized
[ 2.745560] [drm] Initialized drm 1.1.0 20060810
[ 2.749001] mdss: Power-on latency exceeded, new value 22448 ns
[ 2.754743] oxili: Power-on latency exceeded, new value 19531 ns
[ 2.760653] 1a98000.qcom,mdss_dsi supply gdsc not found, using dummy regulator
[ 2.765535] 1a98000.qcom,mdss_dsi supply gdsc not found, using dummy regulator
[ 2.772742] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0
[ 2.779875] msm 1a00000.qcom,mdss_mdp: failed to bind 1a98000.qcom,mdss_dsi (ops dsi_ops): -517
[ 2.787728] msm 1a00000.qcom,mdss_mdp: master bind failed: -517
[ 2.795683] platform 1a00000.qcom,mdss_mdp: Driver msm requests probe deferral
[ 2.806573] loop: module loaded
[ 2.810092] spmi spmi-0: PMIC Arb Version-2 (0x20010000)
[ 2.814150] tun: Universal TUN/TAP device driver, 1.6
[ 2.817422] tun: © 1999-2004 Max Krasnyansky maxk@qualcomm.com
[ 2.823163] usbcore: registered new interface driver asix
[ 2.828514] usbcore: registered new interface driver ax88179_178a
[ 2.834018] usbcore: registered new interface driver cdc_ether
[ 2.840031] usbcore: registered new interface driver dm9601
[ 2.845775] usbcore: registered new interface driver net1080
[ 2.851236] usbcore: registered new interface driver plusb
[ 2.857147] usbcore: registered new interface driver cdc_subset
[ 2.862426] usbcore: registered new interface driver zaurus
[ 2.868286] usbcore: registered new interface driver cdc_ncm
[ 2.873928] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 2.879670] ehci-pci: EHCI PCI platform driver
[ 2.886055] ehci-platform: EHCI generic platform driver
[ 2.890693] ehci-msm: Qualcomm On-Chip EHCI Host Controller
[ 2.895768] msm_hsusb_host 78d9000.ehci: unable to find transceiver
[ 2.901120] platform 78d9000.ehci: Driver msm_hsusb_host requests probe deferral
[ 2.907446] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 2.915017] ohci-pci: OHCI PCI platform driver
[ 2.921024] ohci-platform: OHCI generic platform driver
[ 2.925659] usbcore: registered new interface driver cdc_acm
[ 2.930531] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.936503] usbcore: registered new interface driver usblp
[ 2.944209] usbcore: registered new interface driver cdc_wdm
[ 2.949752] usbcore: registered new interface driver uas
[ 2.955598] usbcore: registered new interface driver usb-storage
[ 2.960936] usbcore: registered new interface driver usbserial
[ 2.977296] usb3503 usb2513: switched to HUB mode
[ 2.977315] usb3503 usb2513: usb3503_probe: probed in hub mode
[ 2.981386] msm_otg 78d9000.phy: OTG regs = ffffff80003be000
[ 2.987107] platform 78d9000.phy: Driver msm_otg requests probe deferral
[ 2.992977] platform 78d9000.usb: Driver msm_hsusb requests probe deferral
[ 3.000016] usbip_core: USB/IP Core v1.0.0
[ 3.005932] usbcore: registered new device driver usbip-host
[ 3.009964] usbip_host: USB/IP Host Driver v1.0.0
[ 3.016097] mousedev: PS/2 mouse device common for all mice
[ 3.021250] i2c_qup 78b8000.i2c:
[ 3.021250] tx channel not available
[ 3.026824] qcom-tsens 4a8000.thermal-sensor: tsens calibration failed
[ 3.032714] platform 4a8000.thermal-sensor: Driver qcom-tsens requests probe deferral
[ 3.039445] Driver ‘mmcblk’ needs updating - please use bus_type methods
[ 3.047275] sdhci: Secure Digital Host Controller Interface driver
[ 3.053979] sdhci: Copyright© Pierre Ossman
[ 3.059993] sdhci-pltfm: SDHCI platform and OF driver helper
[ 3.072969] 8916_l5: unsupportable voltage range: 2700000-1800000uV
[ 3.072990] mmc0: Switching to 3.3V signalling voltage failed
[ 3.113318] mmc0: SDHCI controller on 7824900.sdhci [7824900.sdhci] using ADMA 64-bit
[ 3.114040] sdhci_msm 7864900.sdhci: Got CD GPIO
[ 3.173410] mmc1: SDHCI controller on 7864900.sdhci [7864900.sdhci] using ADMA 64-bit
[ 3.175124] ledtrig-cpu: registered to indicate activity on CPUs
[ 3.180801] usbcore: registered new interface driver usbhid
[ 3.186294] usbhid: USB HID core driver
[ 3.191887] msm8916-pinctrl 1000000.pinctrl: Invalid config param 000a
[ 3.195416] msm8916-pinctrl 1000000.pinctrl: pin_config_group_set op failed for group 121
[ 3.202000] extcon-usb-gpio usb-id: Error applying setting, reverse things back
[ 3.213820] qcom-apq8016 7702000.sound: error getting codec dai name
[ 3.217361] qcom-apq8016 7702000.sound: Error resolving dai links: -517
[ 3.224012] platform 7702000.sound: Driver qcom-apq8016 requests probe deferral
[ 3.230516] TCP: cubic registered
[ 3.237611] NET: Registered protocol family 17
[ 3.241091] 9pnet: Installing 9P2000 support
[ 3.245487] Key type dns_resolver registered
[ 3.250483] registered taskstats version 1
[ 3.255995] 1a98000.qcom,mdss_dsi supply gdsc not found, using dummy regulator
[ 3.258086] 1a98000.qcom,mdss_dsi supply gdsc not found, using dummy regulator
[ 3.280190] msm 1a00000.qcom,mdss_mdp: bound 1a98000.qcom,mdss_dsi (ops dsi_ops)
[ 3.280227] msm 1a00000.qcom,mdss_mdp: bound 1c00000.qcom,adreno-3xx (ops a3xx_ops)
[ 3.286698] 1a00000.qcom,mdss_mdp supply vdd not found, using dummy regulator
[ 3.310753] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.310773] [drm] No driver support for vblank timestamp query.
[ 3.317388] msm 1a00000.qcom,mdss_mdp: No connectors reported connected with modes
[ 3.322068] [drm] Cannot find any crtc or sizes - going 1024x768
[ 3.348012] Console: switching to colour frame buffer device 128x48
[ 3.362078] msm 1a00000.qcom,mdss_mdp: fb0: msm frame buffer device
[ 3.367125] msm 1a00000.qcom,mdss_mdp: registered panic notifier
[ 3.403335] [drm] Initialized msm 1.0.0 20130625 on minor 0
[ 3.403593] msm_hsusb_host 78d9000.ehci: unable to find transceiver
[ 3.407717] platform 78d9000.ehci: Driver msm_hsusb_host requests probe deferral
[ 3.414371] msm_otg 78d9000.phy: OTG regs = ffffff8000502000
[ 3.538941] qcom-apq8016 7702000.sound: adv7511 <-> Quatenary MI2S mapping ok
[ 3.539782] msm_hsusb_host 78d9000.ehci: EHCI Host Controller
[ 3.545179] …/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 3.557725] ALSA devi�[ 3.560575] Freeing unused kernel memory: 268K (ffffffc00095b000 - ffffffc00099e000)
[ 3.560608] Freeing alternatives memory: 12K (ffffffc00099e000 - ffffffc0009a1000)
[ 3.567517] msm_hsusb_host 78d9000.ehci: new USB bus registered, assigned bus number 1
[ 3.577513] msm_hsusb_host 78d9000.ehci: irq 144, io mem 0x078d9000
[ 3.594872] msm_hsusb_host 78d9000.ehci: USB 2.0 started, EHCI 1.00
[ 3.595040] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 3.599948] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.606932] usb usb1: Product: EHCI Host Controller
[ 3.614023] usb usb1: Manufacturer: Linux 4.0.0-00920-gcf20a91 ehci_hcd
[ 3.618774] usb usb1: SerialNumber: 78d9000.ehci
[ 3.625953] hub 1-0:1.0: USB hub found
[ 3.630267] hub 1-0:1.0: 1 port detected
Starting logging: OK
Initializing random number generator… [ 3.648999] random: dd urandom read with 4 bits of entropy available
done.
Starting network…
mount: mounting /dev/mmcblk1p10 on /mnt failed: No such file or directory

Welcome to Buildroot
buildroot login: [ 3.953362] usb 1-1: new high-speed USB device number 2 using msm_hsusb_host
[ 4.103772] usb 1-1: New USB device found, idVendor=0424, idProduct=2513
[ 4.103802] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 4.110163] hub 1-1:1.0: USB hub found
[ 4.117141] hub 1-1:1.0: 3 ports detected
[ 5.173317] mmc0: error -110 whilst initialising MMC card
[ 5.273376] mmc0: Reset 0x1 never completed.
[ 5.275035] 8916_l5: unsupportable voltage range: 2700000-1800000uV
[ 5.276699] mmc0: Switching to 3.3V signalling voltage failed
[ 7.343316] mmc0: error -110 whilst initialising MMC card
[ 7.443375] mmc0: Reset 0x1 never completed.
[ 7.445220] 8916_l5: unsupportable voltage range: 2700000-1800000uV
[ 7.446698] mmc0: Switching to 3.3V signalling voltage failed
[ 8.256111] mmc0: error -110 whilst initialising MMC card
[ 8.356163] mmc0: Reset 0x1 never completed.
[ 8.357927] 8916_l5: unsupportable voltage range: 2700000-1800000uV
[ 8.359486] mmc0: Switching to 3.3V signalling voltage failed
[ 10.453311] mmc0: error -110 whilst initialising MMC card
[ 10.553364] mmc0: Reset 0x1 never completed.
[ 10.604070] mmc1: new high speed SDHC card at address 1234
[ 10.604415] mmcblk0: mmc1:1234 SA04G 3.67 GiB
[ 10.614130] GPT:Primary header thinks Alt. header is not at the end of the disk.
[ 10.614154] GPT:4194303 != 7716863
[ 10.620574] GPT:Alternate GPT header not at the end of the disk.
[ 10.623832] GPT:4194303 != 7716863
[ 10.629949] GPT: Use GNU Parted to correct GPT errors.
[ 10.633197] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10

Welcome to Buildroot
buildroot login: root

ls /.

Settings etc lib media proc sbin usr
bin home lib64 mnt root sys var
dev init linuxrc opt run tmp

uname -a

Linux buildroot 4.0.0-00920-gcf20a91 #25 SMP PREEMPT Wed Jun 17 09:43:51 CEST 2015 aarch64 GNU/Linux

I even tried to blindly flash the eMMC using a keyboard, so i pressed “i” (install), after 10 minutes i removed the SD card, returned the S6[0-1-0-0] switch to S6[0-0-0-0] and pressed OK(Enter) and at first from UART logs i got:
Available slides ()
“Finish writing (sync)”, then:

rebooted

[ 167.243929] mmc1: card 1234 removed
[ 180.282545] usb 1-1: USB disconnect, device number 2
[ 180.284496] usb 1-1.1: USB disconnect, device number 3
[ 180.289565] reboot: Restarting system

After reboot, the Dragonboard didn’t boot nor it gave any logs.

I also tried to boot debian installer(option1) with the SD card and it boots to the linaro-installer prompt, but again no HDMI monitor output.
Changing the HDMI cables, host machines and monitors brings the same results.

In Debian prompt, executing 96boards-installer-session gives:

96boards-installer-session logs

root@linaro-installer:/usr/bin# ./96boards-installer-session
xsetroot: unable to open display ‘’
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any X display.

Checking the HDMI status gives:

HDMI status

root@linaro-installer:/# cat /sys/class/drm/card0-HDMI-A-1/enabled
disabled
root@linaro-installer:/# cat /sys/class/drm/card0-HDMI-A-1/status
disconnected

After that following this guide i tried flashing over USB and on the host machine i got:

USB flashing host logs

Waiting for EDL device
/dev/bus/usb/003/028
HELLO version: 0x2 compatible: 0x1 max_len: 1024 mode: 0
READ image: 13 offset: 0x0 length: 0x34
READ image: 13 offset: 0x34 length: 0x60
READ image: 13 offset: 0x1000 length: 0x1000
READ image: 13 offset: 0x2000 length: 0x988
READ image: 13 offset: 0x3000 length: 0x1000
READ image: 13 offset: 0x4000 length: 0x1000
READ image: 13 offset: 0x5000 length: 0x1000
READ image: 13 offset: 0x6000 length: 0x1000
READ image: 13 offset: 0x7000 length: 0x1000
READ image: 13 offset: 0x8000 length: 0x1000
READ image: 13 offset: 0x9000 length: 0x1000
READ image: 13 offset: 0xa000 length: 0x1000
READ image: 13 offset: 0xb000 length: 0x1000
READ image: 13 offset: 0xc000 length: 0x1000
READ image: 13 offset: 0xd000 length: 0x1000
READ image: 13 offset: 0xe000 length: 0x1000
READ image: 13 offset: 0xf000 length: 0x1000
READ image: 13 offset: 0x10000 length: 0x1000
READ image: 13 offset: 0x11000 length: 0x1000
READ image: 13 offset: 0x12000 length: 0x1000
READ image: 13 offset: 0x13000 length: 0x1000
READ image: 13 offset: 0x14000 length: 0x1000
READ image: 13 offset: 0x15000 length: 0x1000
READ image: 13 offset: 0x16000 length: 0x1000
READ image: 13 offset: 0x17000 length: 0xbd8
END OF IMAGE image: 13 status: 0
DONE status: 0
LOG: init storage:fail
qdl: failed to read: Connection timed out

For flashing with SD card S6 is set as [0-1-0-0].
For flashing with USB S6 is set as [1-0-0-0].
The following SD cards were used: SDHC 4GB class4 and 16GB class10.

Regards,
Ivan


#2

What display device are you using? It looks like it does not correctly report the video modes it supports to the DB410C. This does not affect Android because the Android display stack completely ignores the monitor and adopts a fixed video mode. Debian and the installer have a more sophisticated stack but it requires the monitor to identify correctly.

If possible trying with an alternative display device might be a good idea.


#3

I am using Samsung monitor and i was working with that monitor before the dv410c stopped working.

I tried to boot Debian installer with other two monitors but again there was nothing on the monitor.


#4

That’s strange. It is very unusual to see errors like this from a “real” monitor.

As I explained a monitor working with Android doesn’t tell is if the video modes are reported correctly because AFAIK Android ignores them.

I guess it is possible there is physical damage somewhere along the way. When you tried with different monitors were you using different HDMI cabling (and the monitors were a different model, right?).


#5

Yes, the monitors are different models and i hooked them with different HDMI cables. All monitors and cables work when i connect them on PC.
I tried with benq and other samsung model.
Still no luck. What physical damage may have occured and how do i check it out for sure?
Thank you for your time :slight_smile:


#6

Thoughts that crossed my mind:

  • Can i flash images from linaro-installer/buildroot prompt i.e. do the same thing that the GUI is supposed to do, but from the prompt?

  • Can i do anything in the debian/buildroot prompt to get into fastboot and then flash my images?

  • Is it possible that the eMMC is dead or the supply voltage for it and the HDMI port is dead if they share the same supply voltage?


#7

I tried to flash the eMMC from booted SD card image and the problem is that i can’t locate the eMMC.

From Android SD card image prompt when i list with fdisk -l i get:

fdisk -l
fdisk -l
Found valid GPT with protective MBR; using GPT

Disk /dev/mmcblk0: 31116288 sectors, 2905M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 12 entries
First usable sector is 34, last usable sector is 4194270

Number  Start (sector)    End (sector)  Size       Code  Name
   1          131072          262143       64.0M   0700  modem
   2          262144          263167        512K   0700  sbl1
   3          263168          264191        512K   0700  rpm
   4          264192          265215        512K   0700  tz
   5          265216          266239        512K   0700  hyp
   6          393216          393247       16384   0700  sec
   7          393248          395295       1024K   0700  aboot
   8          395296          493599       48.0M   0700  boot
   9          493600          495647       1024K   0700  devinfo
  10          495648         4194270       1805M   0700  os

From Debian SD card installer i get:

fdisk -l
root@linaro-installer:~# sudo fdisk -l
GPT PMBR size mismatch (9363455 != 31116287) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/mmcblk1: 14.9 GiB, 15931539456 bytes, 31116288 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C185BF9D-5CB1-4913-90BF-1CF7A17EF598


na debian 

Device           Start     End Sectors  Size Type
/dev/mmcblk1p1      34    1057    1024  512K unknown
/dev/mmcblk1p2    1058    2081    1024  512K unknown
/dev/mmcblk1p3    2082    4129    2048    1M unknown
/dev/mmcblk1p4    4130    5153    1024  512K unknown
/dev/mmcblk1p5    5154    5185      32   16K unknown
/dev/mmcblk1p6    5186    7233    2048    1M unknown
/dev/mmcblk1p7    7234  138305  131072   64M unknown
/dev/mmcblk1p8  138306 3210305 3072000  1.5G Linux filesystem
/dev/mmcblk1p9 3210306 9363422 6153117    3G Linux filesystem

root@linaro-installer:~# lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1     179:0    0 14.9G  0 disk 
├─mmcblk1p1 179:1    0  512K  0 part 
├─mmcblk1p2 179:2    0  512K  0 part 
├─mmcblk1p3 179:3    0    1M  0 part 
├─mmcblk1p4 179:4    0  512K  0 part 
├─mmcblk1p5 179:5    0   16K  0 part 
├─mmcblk1p6 179:6    0    1M  0 part 
├─mmcblk1p7 179:7    0   64M  0 part 
├─mmcblk1p8 179:8    0  1.5G  0 part /
└─mmcblk1p9 179:9    0    3G  0 part /mnt

I can’t locate two mmcblk in /dev which means that only the SD card is recognised.
Also, the voltage on 18th pin form the J6(HDMI) connector that according to the schematic is the supply voltage 5V for HDMI port is 0V.


#8

If that’s true that could definitely stop the monitor detecting.

Can you double check your readings by checking pin 37 on the LS connector and from pins 3 & 4 on U14 (if they are too small there is an unpopulated SMD component just below U14 which almost R82… you could read off there).


#9

Little correction, i double checked my measurement and the measured voltage on J6 18th pin is 0.6V. I was able to measure 3 and 4 pins from U14 and the result is again 0.6V. From the LS connector 37 pin is 5V.

I suppose that something is wrong with this chip :frowning: ?

Now I am searching where to measure if there is a power supply on the eMMC, but I can’t find U2(eMMC chip). Is it under the shield? Is there any pin on the board where i can measure the power supply to eMMC?


#10

That is very odd. The be honest I was expecting either different voltages between pin 3 and 4 or the same voltage across all the pins. Voltage difference between U14 pin 3 and LS pin 37 is really weird because they are the same SYS_5P0. Can’t really offer any explanation for this.

Can’t really say… the results from the above tests are not either of the cases I would have predicted.

However it certainly does sound like there is physical damage to your board. If you have access to a spare board it is certainly worth comparing results.

Pretty sure this is under the shield (DB410C uses a combo DDR and eMMC module and I think the RAM would want to be under the shielding).


#12

I double checked the results and it checks out that pin3 is 5V and pin4 is 0V(i measured 10 and 9 instead :sweat_smile:).

Can i remove the shield and than measure some voltages on the eMMC?

Well the problem is that I don’t have another db410c, so i can’t compare them. I just want to be sure that it is a hardware problem, if it is, I will buy other db410c.


#13

To be honest that’s why I recommend reading the same signal from as many points on the board as you can find… it helps bring mechanical mistakes to the surface!

As it happens things still look inconsistent. You are reading 0.6v on pin 18 of J6 and 0v from the ESD protection chip (U14). Having said that don’t worry too much… compared to what I think it correct operation both 0v and 0.6v seem pretty bogus to me. There are no GPIOs or anything like that going to U14 so I don’t think there is any scope at all for this to be a software problem. If 5v (and ground) goes in then 5v should come out. Whether this is caused by U14 failing or by a short circuit downstream we can’t tell… if something shorted then the current limiter in U14 should kick in and lower the output voltage. Might be worth measuring the resistance from HDMI_5V to ground to see if there is a short.

I wouldn’t bother removing the shield. I can be desoldered but the DDR+eMMC chip is ball grid area so you won’t be able to observe much (given the decoupling caps are not labelled):