Inforce Computing Forums

inforce computing forums to discuss about inforce products

I can recover my board use the recovery packege

Questions and discussions related to Inforce 6640 Micro SBC

by meiyulaishi » Fri Sep 20, 2019 2:18 am

Dear:
I have followed the procedures in the document "APQ8096_Recovery_of_Boards_using_USB_003228_Rev_B.pdf"。
the log as follows shows i have run successfully.

LOG: Patched sector 8191 with A2C1B304
partition 1 is now bootable
LOG: Inside handlePower() - Requested POWER_RESET
LOG: Issuing bsp_target_reset() after 1 seconds, if this hangs, do you have WATCHDOG enabled?



then i set the IFC6640 board in UFS boot mode, keep the switch in 1-0-0-0-0-0. and connect the board to pc through the USB cable. then power on the board keeping the POWER and VOL- keys pressed, but the board couldn`t went into the fastboot mode.
the log as follows.


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.XF.1.0-00291
S - IMAGE_VARIANT_STRING=M8996LAB
S - OEM_IMAGE_VERSION_STRING=crm-ubuntu67
S - Boot Interface: UFS
S - Secure Boot: Off
S - Boot Config @ 0x00076044 = 0x000001c9
S - JTAG ID @ 0x000760f4 = 0x4003e0e1
S - OEM ID @ 0x000760f8 = 0x00000000
S - Serial Number @ 0x00074138 = 0xc356b8af
S - OEM Config Row 0 @ 0x00074188 = 0x0000000000000000
S - OEM Config Row 1 @ 0x00074190 = 0x0000000000000000
S - Feature Config Row 0 @ 0x000741a0 = 0x0050000010000100
S - Feature Config Row 1 @ 0x000741a8 = 0x00fff00001ffffff
S - Core 0 Frequency, 1228 MHz
B - 0 - PBL, Start
B - 10413 - bootable_media_detect_entry, Start
B - 47079 - bootable_media_detect_success, Start
B - 47083 - elf_loader_entry, Start
B - 48101 - auth_hash_seg_entry, Start
B - 48202 - auth_hash_seg_exit, Start
B - 80101 - elf_segs_hash_verify_entry, Start
B - 82581 - PBL, End
B - 84637 - SBL1, Start
B - 180621 - usb: hs_phy_nondrive_start
B - 180956 - usb: hs_phy_nondrive_finish
B - 183945 - boot_flash_init, Start
D - 30 - boot_flash_init, Delta
B - 191296 - sbl1_ddr_set_default_params, Start
D - 30 - sbl1_ddr_set_default_params, Delta
B - 199287 - boot_config_data_table_init, Start
D - 92384 - boot_config_data_table_init, Delta - (60 Bytes)
B - 296216 - CDT Version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B - 300913 - Image Load, Start
D - 22234 - PMIC Image Loaded, Delta - (37248 Bytes)
B - 323147 - pm_device_init, Start
B - 328912 - PON REASON:PM0:0x2000000000a0 PM1:0x2000000a0
B - 365207 - PM_SET_VAL:Skip
D - 39894 - pm_device_init, Delta
B - 367128 - pm_driver_init, Start
D - 2897 - pm_driver_init, Delta
B - 373716 - pm_sbl_chg_init, Start
D - 0 - pm_sbl_chg_init, Delta
B - 380487 - vsense_init, Start
D - 0 - vsense_init, Delta
B - 388570 - Pre_DDR_clock_init, Start
D - 366 - Pre_DDR_clock_init, Delta
B - 394090 - ddr_initialize_device, Start
B - 397781 - 8996 v3.x detected, Max frequency = 1.8 GHz
B - 407297 - ddr_initialize_device, Delta
B - 407327 - DDR ID, Rank 0, Rank 1, 0x6, 0x400, 0x400
B - 411292 - Basic DDR tests done
B - 479887 - clock_init, Start
D - 244 - clock_init, Delta
B - 481869 - Image Load, Start
D - 5216 - QSEE Dev Config Image Loaded, Delta - (34528 Bytes)
B - 488183 - Image Load, Start
D - 5856 - APDP Image Loaded, Delta - (0 Bytes)
B - 496967 - usb: UFS Serial - 4c7ad14
B - 501664 - usb: fedl, vbus_low
B - 505293 - Image Load, Start
D - 52247 - QSEE Image Loaded, Delta - (1612784 Bytes)
B - 557540 - Image Load, Start
D - 213 - SEC Image Loaded, Delta - (4096 Bytes)
B - 565104 - sbl1_efs_handle_cookies, Start
D - 213 - sbl1_efs_handle_cookies, Delta
B - 573613 - Image Load, Start
D - 14091 - QHEE Image Loaded, Delta - (258728 Bytes)
B - 587735 - Image Load, Start
D - 13725 - RPM Image Loaded, Delta - (223900 Bytes)
B - 601673 - Image Load, Start
D - 3782 - STI Image Loaded, Delta - (0 Bytes)
B - 608658 - Image Load, Start
D - 40168 - APPSBL Image Loaded, Delta - (731612 Bytes)
B - 648918 - SBL1, End
D - 568551 - SBL1, Delta
S - Flash Throughput, 99000 KB/s (2907172 Bytes, 29112 us)
S - DDR Frequency, 1017 MHz
Android Bootloader - UART_DM Initialized!!!
[0] welcome to lk

[10] platform_init()
[10] target_init()
[10] RPM GLink Init
[10] Opening RPM Glink Port success
[10] Opening SSR Glink Port success
[20] Glink Connection between APPS and RPM established
[20] Glink Connection between APPS and RPM established
[40] UFS init success
[40] Qseecom Init Done in Appsbl
[40] secure app region addr=0x86600000 size=0x2200000[50] TZ App region notif returned with status:0 addr:86600000 size:35651584
[60] TZ App log region register returned with status:0 addr:918cd000 size:4096
[60] Qseecom TZ Init Done in Appsbl
[80] Loading cmnlib done
[80] qseecom_start_app: Loading app keymaster for the first time'
[100] <8>keymaster: "\"KEYMASTER Init \""
[110] oem_panel_select:
[110] Not able to search the panel:
[110] panel_operating_mode=0x0
[120] Return value from recv_data: 14
[130] Return value from recv_data: 14
[140] Return value from recv_data: 14
[220] ERROR: Splash image header invalid
[230] Config MIPI_VIDEO_PANEL.
[570] mdss_dsi_panel_initialize:No dispaly panel Connected !!!
[570] dsi panel init error
[580] target_display_init:MIPI failed !! selcting HDMI
[580] Return value from recv_data: 14
[630] mdss_hdmi_read_edid: NACK reading EDID
[650] mdss_hdmi_read_edid: NACK reading EDID
[670] mdss_hdmi_read_edid: NACK reading EDID
[690] mdss_hdmi_read_edid: NACK reading EDID
[720] mdss_hdmi_read_edid: NACK reading EDID
[740] mdss_hdmi_read_edid: NACK reading EDID
[1040] hdmi_vco_enable: pll_locked = 1
[1050] hdmi_vco_enable: phy_ready = 1
[1050] ERROR: Splash image header invalid
[1070] Config HDMI PANEL.
[1070] Turn on HDMI PANEL.
[1070] hdmi resolution 1920x1080@p60Hz (16)
[1080] pm8x41_get_is_cold_boot: cold boot
[1080] fastboot_init()


when i runs : fastboot devices, there is no devices.
meiyulaishi
 
Posts: 6
Joined: Mon Sep 11, 2017 11:43 pm

by ashwin » Fri Sep 20, 2019 4:05 am

Based on the logs, it looks like the IFC6640 is already in fastboot mode.

[1080] pm8x41_get_is_cold_boot: cold boot
[1080] fastboot_init()

Please check your adb/fastboot tool/ usb driver.
ashwin
 
Posts: 66
Joined: Wed Jul 01, 2015 10:07 pm

by meiyulaishi » Sun Sep 22, 2019 5:49 pm

Dear :
Thanks for your reply.
I have tried as follows:
adb>fastboot tool/usb driver,

it shows:
<waiting for device>

It looks like the devices is not identified by the PC. I have checked the Device manager, there is no devices identified by the PC. the usb driver haven`t installed.
meiyulaishi
 
Posts: 6
Joined: Mon Sep 11, 2017 11:43 pm


Return to INFORCE 6640™ Micro SBC

cron

Contact Us.