EC2X start up error on boot flash init

Hi,

I’m using the EC2X to develop a custom board. My boards just arrived and when I tried to deploy my solution my 4G was not working. So I’ve started debugging the EC2X and I saw the following trace:

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-00084
S - IMAGE_VARIANT_STRING=LAATANAZA
S - OEM_IMAGE_VERSION_STRING=SH-SW417P
S - Boot Config, 0x000002e1
B -      1216 - PBL, Start
B -      3723 - bootable_media_detect_entry, Start
B -      4398 - bootable_media_detect_success, Start
B -      4402 - elf_loader_entry, Start
B -      7854 - auth_hash_seg_entry, Start
B -      8076 - auth_hash_seg_exit, Start
B -     54887 - elf_segs_hash_verify_entry, Start
B -     98305 - PBL, End
B -    106780 - SBL1, Start
B -    164913 - pm_device_init, Start
B -    184799 - PM_SET_VAL:Skip
D -     18178 - pm_device_init, Delta
B -    185775 - boot_config_data_table_init, Start
D -    174917 - boot_config_data_table_init, Delta - (420 Bytes)
B -    364231 - CDT version:3,Platform ID:8,Major ID:1,Minor ID:0,Subtype:0
B -    370422 - sbl1_ddr_set_params, Start
B -    374265 - Pre_DDR_clock_init, Start
D -       213 - Pre_DDR_clock_init, Delta
D -         0 - sbl1_ddr_set_params, Delta
B -    386984 - pm_driver_init, Start
D -      4544 - pm_driver_init, Delta
B -    393297 - cpr_init, Start
D -        30 - cpr_init, Delta
B -    397903 - cpr_cx_mx_apc_vol_update, Start
D -        61 - cpr_cx_mx_apc_vol_update, Delta
B -    412451 - sbl1_qhsusb_al_do_fast_enum, Start
D -         0 - sbl1_qhsusb_al_do_fast_enum, Delta
B -    415623 - clock_init, Start
D -       183 - clock_init, Delta
B -    421418 - boot_flash_init, Start
B -    425261 - Error code 303e at boot_flash_dev_nand.c Line 575

We have another EC2X that we are usign in the development board that has firmware version S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2-00055 and this is working just fine.

Can anyone help me with that, or explain what might be wrong?

hi , what firmware do you used ? You can check it with AT command, for example: ATI

The normal and abnormal devices are their the same circuit ? Pls check whether the GPIO level is higher than 1.8V, which may trigger over voltage protection.

Hi Bingo,

I can’t run AT commands because the module didn’t even started, as the debug says:
B - 425261 - Error code 303e at boot_flash_dev_nand.c Line 575
The firmware version is S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.2-00084 I believe.

That debug is the one I got from the debug UART of the module on startup.

On the GPIO level topic I used the own module voltage reference for the voltage translator, and used the reference design for it. That should not be the problem.

You can measure whether module all PINs voltage is high than 1.8V; It may peripherals devices current fow backward.