Inforce Computing Forums

inforce computing forums to discuss about inforce products

A problem on flash the image

Questions and discussions related to Inforce 6640 Micro SBC

by meiyulaishi » Wed Sep 25, 2019 11:01 pm

Dear :
I have a problem here;
I have built the whole source for 6640 successfully.
I flashed the emmc_appsboot.mbn use the following instruction:

fastboot flash aboot emmc_appsboot.mbn

Then reboot the board using instruction: fastboot reboot.

But the 6640 board couldn`t boot successfully. The log are 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 - 47072 - bootable_media_detect_success, Start
B - 47076 - elf_loader_entry, Start
B - 48098 - auth_hash_seg_entry, Start
B - 48199 - auth_hash_seg_exit, Start
B - 79993 - elf_segs_hash_verify_entry, Start
B - 82479 - PBL, End
B - 84515 - SBL1, Start
B - 180529 - usb: hs_phy_nondrive_start
B - 180865 - usb: hs_phy_nondrive_finish
B - 183823 - boot_flash_init, Start
D - 30 - boot_flash_init, Delta
B - 191204 - sbl1_ddr_set_default_params, Start
D - 30 - sbl1_ddr_set_default_params, Delta
B - 199165 - boot_config_data_table_init, Start
D - 100345 - boot_config_data_table_init, Delta - (60 Bytes)
B - 304024 - CDT Version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B - 308721 - Image Load, Start
D - 22234 - PMIC Image Loaded, Delta - (37248 Bytes)
B - 330986 - pm_device_init, Start
B - 336720 - PON REASON:PM0:0x200000021 PM1:0x200000021
B - 373045 - PM_SET_VAL:Skip
D - 39955 - pm_device_init, Delta
B - 374967 - pm_driver_init, Start
D - 2928 - pm_driver_init, Delta
B - 381555 - pm_sbl_chg_init, Start
D - 0 - pm_sbl_chg_init, Delta
B - 388326 - vsense_init, Start
D - 0 - vsense_init, Delta
B - 396408 - Pre_DDR_clock_init, Start
D - 335 - Pre_DDR_clock_init, Delta
B - 401959 - ddr_initialize_device, Start
B - 405650 - 8996 v3.x detected, Max frequency = 1.8 GHz
B - 415135 - ddr_initialize_device, Delta
B - 415166 - DDR ID, Rank 0, Rank 1, 0x6, 0x400, 0x400
B - 419131 - Basic DDR tests done
B - 487725 - clock_init, Start
D - 244 - clock_init, Delta
B - 489708 - Image Load, Start
D - 5154 - QSEE Dev Config Image Loaded, Delta - (34528 Bytes)
B - 496021 - Image Load, Start
D - 5856 - APDP Image Loaded, Delta - (0 Bytes)
B - 504805 - usb: UFS Serial - 4c7ad14
B - 509502 - usb: fedl, vbus_low
B - 513132 - Image Load, Start
D - 52094 - QSEE Image Loaded, Delta - (1612784 Bytes)
B - 565226 - Image Load, Start
D - 213 - SEC Image Loaded, Delta - (4096 Bytes)
B - 572790 - sbl1_efs_handle_cookies, Start
D - 213 - sbl1_efs_handle_cookies, Delta
B - 581299 - Image Load, Start
D - 14091 - QHEE Image Loaded, Delta - (258728 Bytes)
B - 595390 - Image Load, Start
D - 13664 - RPM Image Loaded, Delta - (223900 Bytes)
B - 609268 - Image Load, Start
D - 3812 - STI Image Loaded, Delta - (0 Bytes)
B - 616313 - Image Load, Start
[color=#FF4040]B - 621041 - Error code 126 at /local/mnt/workspace/CRMBuilds/BOOT.XF.1.0-00291-M8996LZB-1_20160222_153334/b/boot_images/QcomPkg/XBLLoader/boot_config.c Line 244[/color]
B - 623694 - Image Load, Start
D - 21655 - XBLRamDump Image Loaded, Delta - (343102 Bytes)
B - 699639 - usb: init start

It looks like that i couldn`t flash the emmc_appsboot.mbn that I built. Although I didn`t modify anything in the source code.
I have tried to flash the emmc_appsboot.mbn in the recovery packge down loaded form the tech web, the board can power on normally.

Any help would be greatly apprieciated.
meiyulaishi
 
Posts: 6
Joined: Mon Sep 11, 2017 11:43 pm

by ashwin » Thu Sep 26, 2019 3:13 am

Hi,

Please only flash the emmc_appsboot.mbn from the release package.

Flashing a source built apps boot image will result in a bricked board as the binary is not signed.

Not to worry, you can recover the board using the recovery package available in techweb.
https://www.inforcecomputing.com/techweb/index.php

Regards,
Ashwin
ashwin
 
Posts: 66
Joined: Wed Jul 01, 2015 10:07 pm

by meiyulaishi » Thu Sep 26, 2019 5:16 pm

Dear:
Thanks so much for you reply.
I have recovered my board.
But I have a question here, I want to make some modification in lk. Now that I want to use a custom display panel, so I have to make some modification in the lk source code. Can I signed the emmc_appsboot.mbn by myself? Or should I need to buy some service for this.
Thanks for your reply.
meiyulaishi
 
Posts: 6
Joined: Mon Sep 11, 2017 11:43 pm

by meiyulaishi » Sun Sep 29, 2019 6:03 pm

Dear:
Thanks so much for you reply.
I have recovered my board.
But I have a question here, I want to make some modification in lk. Now that I want to use a custom display panel, so I have to make some modification in the lk source code. Can I signed the emmc_appsboot.mbn by myself? Or should I need to buy some service for this.
Thanks for your reply.
meiyulaishi
 
Posts: 6
Joined: Mon Sep 11, 2017 11:43 pm


Return to INFORCE 6640™ Micro SBC

cron

Contact Us.