Inforce Computing Forums

inforce computing forums to discuss about inforce products

6601 wedged reboot with "usb: init start"

Questions and discussions related to Inforce 6601 Micro SOM

by MikeHermann » Thu Jun 06, 2019 9:26 am

Recently, we noticed our 6601 SOM, when we suffered a GPF or other server fault, would get wedged during the reboot.

From reading elsewhere in this forum (*), the line "XBLRamDump Image Loaded..." followed by "usb: init start" indicates that the device is rebooting in a debug mode, and has chosen an alternative USB boot device, and is trying to connect with a debugger, to help diagnose the fault. The same article says that this is locked down behavior, because the bootloader is a binary from Qualcomm, and they don't share the sources.

Question 1) is there a work-around, some pin, mechanism, or setting to have the 820 SOM system reboot automatically? Perhaps a watchdog timer?
Question 2) where can we find documentation for the "PON REASON" that is cited in the boot-up preamble - we'd like to diagnose what happened as well. We'd like to be able to isolate the cause of the PowerOn Reset.

Here is the reboot preamble:
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 = 0xe9344292
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 - 45868 - bootable_media_detect_success, Start
B - 45871 - elf_loader_entry, Start
B - 46866 - auth_hash_seg_entry, Start
B - 46968 - auth_hash_seg_exit, Start
B - 78791 - elf_segs_hash_verify_entry, Start
B - 81276 - PBL, End
B - 83326 - SBL1, Start
B - 179309 - usb: hs_phy_nondrive_start
B - 179645 - usb: hs_phy_nondrive_finish
B - 182603 - boot_flash_init, Start
D - 0 - boot_flash_init, Delta
B - 189984 - sbl1_ddr_set_default_params, Start
D - 0 - sbl1_ddr_set_default_params, Delta
B - 197975 - boot_config_data_table_init, Start
D - 313845 - boot_config_data_table_init, Delta - (60 Bytes)
B - 516334 - CDT Version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B - 521031 - Image Load, Start
D - 22204 - PMIC Image Loaded, Delta - (37248 Bytes)
B - 543235 - pm_device_init, Start
B - 549030 - PON REASON:PM0:0x200a0 PM1:0x200a0
B - 585295 - PM_SET_VAL:Skip
D - 39924 - pm_device_init, Delta
B - 587216 - pm_driver_init, Start
D - 2897 - pm_driver_init, Delta
B - 593804 - pm_sbl_chg_init, Start
D - 30 - pm_sbl_chg_init, Delta
B - 600575 - vsense_init, Start
D - 0 - vsense_init, Delta
B - 608627 - Pre_DDR_clock_init, Start
D - 396 - Pre_DDR_clock_init, Delta
B - 614209 - ddr_initialize_device, Start
B - 617899 - 8996 v3.x detected, Max frequency = 1.8 GHz
B - 625463 - ddr_initialize_device, Delta
B - 627476 - Basic DDR tests done
B - 2190571 - clock_init, Start
D - 244 - clock_init, Delta
B - 2192614 - Image Load, Start
D - 5704 - QSEE Dev Config Image Loaded, Delta - (34528 Bytes)
B - 2198897 - Image Load, Start
D - 5856 - APDP Image Loaded, Delta - (0 Bytes)
B - 2228940 - usb: fedl, vbus_low
B - 2229001 - Image Load, Start
D - 10644 - XBLRamDump Image Loaded, Delta - (343102 Bytes)
B - 2294271 - usb: init start


Possibly related posts:
http://forums.inforcecomputing.com/viewtopic.php?f=19&t=1001
http://forums.inforcecomputing.com/viewtopic.php?f=19&t=1004
-- Mike Hermann
QuirkLogic Inc
MikeHermann
 
Posts: 1
Joined: Tue May 01, 2018 9:28 am
Location: Calgary AB

Return to INFORCE 6601™ MICRO SYSTEM-ON-MODULE (SOM)

cron

Contact Us.