Inforce Computing Forums

inforce computing forums to discuss about inforce products

6601: Q: How to burn Linux binaries

Questions and discussions related to Inforce 6501™ development kit

by tamo2 » Mon Nov 06, 2017 3:37 pm

Hi, since I wasn't able to post to 6601 forum, I am posting the question here.

I have Inforce 6601 Dev Kit, which has Android pre-burned.
Following "Inforce_6601_Debian_Linux_Release_Note_V0.4_003127_Rev_A.pdf", I am trying to flash the Linux binaries.
Here is what I tried:
- Connect a serial cable to the Dev board.
- Holding down VOL- button, then push POWER button.
- Then it starts but then stops at "fastboot_init()". At this point, the serial console is not responsive.

What am I doing wrong?

--- here is the log ---
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 = 0x55312939
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 - 45908 - bootable_media_detect_success, Start
B - 45909 - elf_loader_entry, Start
B - 46894 - auth_hash_seg_entry, Start
B - 46998 - auth_hash_seg_exit, Start
B - 78835 - elf_segs_hash_verify_entry, Start
B - 81317 - PBL, End
B - 83357 - SBL1, Start
B - 179370 - usb: hs_phy_nondrive_start
B - 179706 - usb: hs_phy_nondrive_finish
B - 182695 - boot_flash_init, Start
D - 0 - boot_flash_init, Delta
B - 190045 - sbl1_ddr_set_default_params, Start
D - 0 - sbl1_ddr_set_default_params, Delta
B - 198036 - boot_config_data_table_init, Start
D - 293501 - boot_config_data_table_init, Delta - (60 Bytes)
B - 496052 - CDT Version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B - 500749 - Image Load, Start
D - 22265 - PMIC Image Loaded, Delta - (37248 Bytes)
B - 523044 - pm_device_init, Start
B - 528778 - PON REASON:PM0:0xa0 PM1:0xa0
B - 565104 - PM_SET_VAL:Skip
D - 39894 - pm_device_init, Delta
B - 567025 - pm_driver_init, Start
D - 2928 - pm_driver_init, Delta
B - 573613 - pm_sbl_chg_init, Start
D - 0 - pm_sbl_chg_init, Delta
B - 580384 - vsense_init, Start
D - 30 - vsense_init, Delta
B - 588558 - Pre_DDR_clock_init, Start
D - 366 - Pre_DDR_clock_init, Delta
B - 593987 - ddr_initialize_device, Start
B - 597678 - 8996 v3.x detected, Max frequency = 1.8 GHz
B - 607194 - ddr_initialize_device, Delta
B - 607224 - DDR ID, Rank 0, Rank 1, 0x1, 0x400, 0x400
B - 611189 - Basic DDR tests done
B - 679753 - clock_init, Start
D - 244 - clock_init, Delta
B - 681766 - Image Load, Start
D - 5063 - QSEE Dev Config Image Loaded, Delta - (34528 Bytes)
B - 688049 - Image Load, Start
D - 5856 - APDP Image Loaded, Delta - (0 Bytes)
B - 696864 - usb: UFS Serial - 91390ac
B - 701530 - usb: fedl, vbus_low
B - 705190 - Image Load, Start
D - 51881 - QSEE Image Loaded, Delta - (1612784 Bytes)
B - 757071 - Image Load, Start
D - 183 - SEC Image Loaded, Delta - (4096 Bytes)
B - 764635 - sbl1_efs_handle_cookies, Start
D - 244 - sbl1_efs_handle_cookies, Delta
B - 773114 - Image Load, Start
D - 14060 - QHEE Image Loaded, Delta - (258728 Bytes)
B - 787205 - Image Load, Start
D - 13664 - RPM Image Loaded, Delta - (223900 Bytes)
B - 801143 - Image Load, Start
D - 3721 - STI Image Loaded, Delta - (0 Bytes)
B - 808036 - Image Load, Start
D - 40565 - APPSBL Image Loaded, Delta - (742884 Bytes)
B - 848693 - SBL1, End
D - 769606 - SBL1, Delta
S - Flash Throughput, 103000 KB/s (2918444 Bytes, 28292 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:916d2000 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] Not able to search the panel:
[110] panel_operating_mode=0x0
[110] Return value from recv_data: 14
[120] Return value from recv_data: 14
[130] Return value from recv_data: 14
[210] ERROR: Splash image header invalid
[220] Config MIPI_VIDEO_PANEL.
[560] mdss_dsi_panel_initialize:[Arjun] No dispaly panel Connected !!!
[560] dsi panel init error
[570] Return value from recv_data: 14
[630] mdss_hdmi_read_edid: EDID read successful
[630] mdss_hdmi_add_video_format: vic=4
[630] mdss_hdmi_add_video_format: vic=16
[940] hdmi_vco_enable: pll_locked = 1
[940] hdmi_vco_enable: phy_ready = 1
[940] ERROR: Splash image header invalid
[960] pm8x41_get_is_cold_boot: cold boot
[960] fastboot_init()
tamo2
 
Posts: 1
Joined: Tue Jun 13, 2017 4:39 pm

by Sundeep » Sun Nov 19, 2017 10:51 pm

Hi tamo2,
Are you able to boot into Android?
Just to confirm, the procedure to enter fastboot is to keep the Vol- button pressed before powering on the board and release it after the board has powered on. Once in fastboot mode, you can load Linux binaries using the commands (available in the Linux release note):
$cd <RELEASE DIRECTORY>/binaries
$fastboot flash aboot emmc_appsboot.mbn
$fastboot flash boot boot-<RELEASE>.img
$gunzip <ROOTFS>.img.gz
$fastboot flash userdata <ROOTFS>.img
$fastboot reboot The platform shall reboot into Linaro.

Yes, the Android and Linux binaries will both work on the Inforce 6601 Dev Kit interchangeably.

Cheers,
Sundeep
Sundeep
 
Posts: 33
Joined: Wed Jul 01, 2015 9:10 pm


Return to INFORCE 6501™ DEVELOPMENT KIT

cron

Contact Us.