SC20-E : SBL failed to load emmc_appsboot.mbn

IoT Modules Smart Module
1

Hello,
I am encountering an issue when I try to load a modified bootloader with the following error :

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.1.2.C2-00060
S - IMAGE_VARIANT_STRING=DAASANAZA
S - OEM_IMAGE_VERSION_STRING=quectel
S - Boot Config, 0x000000e1
B - 1566 - PBL, Start
B - 4542 - bootable_media_detect_entry, Start
B - 149864 - bootable_media_detect_success, Start
B - 149868 - elf_loader_entry, Start
B - 150496 - auth_hash_seg_entry, Start
B - 150757 - auth_hash_seg_exit, Start
B - 164417 - elf_segs_hash_verify_entry, Start
B - 223861 - PBL, End
B - 187727 - SBL1, Start
B - 233691 - boot_flash_init, Start
D - 30 - boot_flash_init, Delta
B - 238998 - boot_config_data_table_init, Start
D - 6039 - boot_config_data_table_init, Delta - (0 Bytes)
B - 248697 - CDT version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
B - 253607 - pm_device_init, Start
B - 256261 - pm_device_init, TEST - MSM8909 detected
B - 260561 - pm_device_init, INFO - PM8909 is selected
B - 273737 - PM_SET_VAL:Skip
D - 19062 - pm_device_init, Delta
B - 275110 - sbl1_ddr_set_params, Start
B - 277519 - cpr_init, Start
D - 0 - cpr_init, Delta
B - 283162 - Pre_DDR_clock_init, Start
D - 183 - Pre_DDR_clock_init, Delta
D - 0 - sbl1_ddr_set_params, Delta
B - 296063 - pm_driver_init, Start
B - 302682 - --> Charge init
B - 3676 - battery voltage
B - 306159 - boot up
B - 10 - Current status
D - 10705 - pm_driver_init, Delta
B - 318511 - clock_init, Start
D - 152 - clock_init, Delta
B - 319487 - Image Load, Start
D - 25437 - QSEE Image Loaded, Delta - (505472 Bytes)
B - 344955 - Image Load, Start
D - 244 - SEC Image Loaded, Delta - (2048 Bytes)
B - 353373 - sbl1_efs_handle_cookies, Start
D - 701 - sbl1_efs_handle_cookies, Delta
B - 359991 - Image Load, Start
D - 12810 - RPM Image Loaded, Delta - (157080 Bytes)
B - 372862 - Image Load, Start
B - 374784 - Error code 302e at boot_config.c Line 285

This was not happening when I previously used SBL version string : S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2.C2-00037 (with the same emmc_appsboot.mbn)

Can anyone help me on this ? What is the source of the issue ?

Thanks for your help

2

Hello clement,

Have you do some midification in your aboot code? from your log, i suggest you check your devices, and you can compare it with other devices.

thanks~

3

Hello Abby,
Thanks for getting back to me.
Indeed, I’ve made some changes in aboot from last SDK 20190527. But nothing changed in my source between the 2 SBL version I loaded.
Again, do you know what is the source of this error code ? And what I am not allow to change in aboot that was not forbidden before ?
Thanks,

4

Hello clement,

What’s your android version in your SC20-E, and if you don’t make some changes in aboot from last SDK 20190527, is boot running normally with emmc_appsboot.mbn ?

thanks~

5

Hi,

I am in Android 8.1.0. My new SBL come from update SC20ESAR06A09_BP01.009.
My previous SBL was delivered already flashed in with version .SC20ESAR06A07_BP01.007
It is vital for me to have SBL comming from update SC20ESAR06A09_BP01.009 because it fixes dump mode after a kernel panic.
It is also vital for me to be able to change aboot to fit our product.
The main changes are in target/msm8909/init.c

6

I can add the following information to my case :
I use the following command to build my own emmc_appsboot.mbn :
"make -j2 -C bootable/bootloader/lk/
TOOLCHAIN_PREFIX=…/…/…/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-
BOOTLOADER_OUT=…/…/…/out/target/product/msm8909/obj/EMMC_BOOTLOADER_OBJ
msm8909 EMMC_BOOT=1 SIGNED_KERNEL=1 VERIFIED_BOOT=1 ENABLE_DISPLAY=1
ENABLE_BOOTDEVICE_MOUNT=0 DEFAULT_UNLOCK=true BOARD_NAME=msm8909
ENABLE_VB_ATTEST=1 OSVERSION_IN_BOOTIMAGE=1
"
This compile well my bootable/bootloader/lk folder.
However when i use the general command “make” or “make aboot” it generates the same emmc_appsboot.mbn as in SC20_Android8.1.0_Quectel_SDK_r00043.1a_20190228/vendor/qcom/proprietary/common/scripts/SecImage/signed/sign/default/appsbl ! (no binaries differences with diff tool)
Is this normal ? The modification of bootable/bootloader/lk/kernel/main.c has no incidence on my build.

Another hint on $OUT/secimage.log generates 2 similar errors :
ERROR: SHA algorithm OU field is missing from certificate.

What is this error and how can I get through this ?

Thanks for your help

7

Hello clement,

Maybe the issue is error from the moudle’s signature.
image
i think you can check this in your motification.

thanks~