On Jun 24, 2016, at 2:24 AM, Sven Eckelmann <sven.eckelmann@xxxxxxxxxxxxx> wrote: > > On Thursday 23 June 2016 11:55:46 Matthew McClintock wrote: >> What is the command line? What is the FDT load address from u-boot? > > 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.1-00072 > S - IMAGE_VARIANT_STRING=DAABANAZA > S - OEM_IMAGE_VERSION_STRING=CRM > S - Boot Config, 0x00000021 > S - Core 0 Frequency, 0 MHz > B - 261 - PBL, Start > B - 1339 - bootable_media_detect_entry, Start > B - 1679 - bootable_media_detect_success, Start > B - 1692 - elf_loader_entry, Start > B - 5068 - auth_hash_seg_entry, Start > B - 7212 - auth_hash_seg_exit, Start > B - 568520 - elf_segs_hash_verify_entry, Start > B - 682592 - PBL, End > B - 682616 - SBL1, Start > B - 772516 - pm_device_init, Start > D - 6 - pm_device_init, Delta > B - 773957 - boot_flash_init, Start > D - 52725 - boot_flash_init, Delta > B - 830856 - boot_config_data_table_init, Start > D - 3805 - boot_config_data_table_init, Delta - (419 Bytes) > B - 838058 - clock_init, Start > D - 7583 - clock_init, Delta > B - 850162 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:2,Subtype:0 > B - 853653 - sbl1_ddr_set_params, Start > B - 858644 - cpr_init, Start > D - 2 - cpr_init, Delta > B - 863030 - Pre_DDR_clock_init, Start > D - 4 - Pre_DDR_clock_init, Delta > D - 13154 - sbl1_ddr_set_params, Delta > B - 876854 - pm_driver_init, Start > D - 2 - pm_driver_init, Delta > B - 883505 - sbl1_wait_for_ddr_training, Start > D - 31 - sbl1_wait_for_ddr_training, Delta > B - 902916 - Image Load, Start > D - 138201 - QSEE Image Loaded, Delta - (267732 Bytes) > B - 1041617 - Image Load, Start > D - 1448 - SEC Image Loaded, Delta - (2048 Bytes) > B - 1051836 - Image Load, Start > D - 173993 - APPSBL Image Loaded, Delta - (353891 Bytes) > B - 1226254 - QSEE Execution, Start > D - 66 - QSEE Execution, Delta > B - 1232440 - SBL1, End > D - 551938 - SBL1, Delta > S - Flash Throughput, 1991 KB/s (624090 Bytes, 313384 us) > S - DDR Fre� > > U-Boot 2012.07 [Barrier Breaker r40864,r40864] (Feb 16 2016 - 23:33:08) > > smem ram ptable found: ver: 1 len: 3 > DRAM: 128 MiB > WARNING: Caches not enabled > machid : 0x8010200 > NAND: SF: Detected Spansion with page size 64 KiB, total 32 MiB > ipq_spi: page_size: 0x100, sector_size: 0x10000, size: 0x2000000 > 32 MiB > MMC: > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serial > machid: 8010200 > Net: > OM3 standard: change gpio 59 -> 63 > MAC0 addr:0:3:7f:ba:db:ad > ipq40xx_ess_sw_init done > PHY ID1: 0x4d > PHY ID2: 0xd0b2 > eth0 > Hit any key to stop autoboot: 0 > (IPQ40xx) # > (IPQ40xx) # > (IPQ40xx) # setenv serverip 192.168.2.227 > (IPQ40xx) # setenv ipaddr 192.168.2.3 > (IPQ40xx) # setenv bootargs loglevel=8 earlyprintk console=ttyS0,115200 > (IPQ40xx) # tftpboot 0x81000000 lede-ipq806x-APDK01-initramfs-fit-uImage.itb > eth0 PHY0 Down Speed :10 Half duplex > eth0 PHY1 Down Speed :10 Half duplex > eth0 PHY2 Down Speed :10 Half duplex > eth0 PHY3 Down Speed :10 Half duplex > eth0 PHY4 up Speed :1000 Full duplex > Using eth0 device > TFTP from server 192.168.2.227; our IP address is 192.168.2.3 > Filename 'lede-ipq806x-APDK01-initramfs-fit-uImage.itb'. > Load address: 0x81000000 > Loading: ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > ################################################################# > ########################################### > done > Bytes transferred = 6347916 (60dc8c hex) > (IPQ40xx) # bootm 0x81000000 > ## Booting kernel from FIT Image at 81000000 ... > Using 'config@1' configuration > Trying 'kernel@1' kernel subimage > Description: ARM OpenWrt Linux-4.7-rc3 > Type: Kernel Image > Compression: gzip compressed > Data Start: 0x810000e4 > Data Size: 6340562 Bytes = 6 MiB > Architecture: ARM > OS: Linux > Load Address: 0x80208000 > Entry Point: 0x80208000 > Hash algo: crc32 > Hash value: d12421ed > Hash algo: sha1 > Hash value: b25692f363b076c63134e3d452316117002c3c85 > Verifying Hash Integrity ... crc32+ sha1+ OK > ## Flattened Device Tree from FIT Image at 81000000 > Using 'config@1' configuration > Trying 'fdt@1' FDT blob subimage > Description: ARM OpenWrt APDK01 device tree blob > Type: Flat Device Tree > Compression: uncompressed > Data Start: 0x8160c1e8 > Data Size: 6014 Bytes = 5.9 KiB > Architecture: ARM > Hash algo: crc32 > Hash value: 337abac9 > Hash algo: sha1 > Hash value: 8193d932fb65464c0f12822f777aa220638a9e0f > Verifying Hash Integrity ... crc32+ sha1+ OK > Booting using the fdt blob at 0x8160c1e8 > Uncompressing Kernel Image ... OK > Loading Device Tree to 8722b000, end 8722f77d ... OK > ipq: fdt fixup unable to find compatible node > eth0 MAC Address from ART is not valid > eth1 MAC Address from ART is not valid > Using machid 0x8010200 from environment > > Starting kernel ... > > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Linux version 4.7.0-rc3 (sven@bentobox) (gcc version 5.3.0 (LEDE GCC 5.3.0 r611) ) #4 SMP PREEMPT Thu Jun 23 15:38:04 UTC 2016 > [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d > [ 0.000000] CPU: div instructions available: patching division code > [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache > [ 0.000000] Machine model: Qualcomm Technologies, Inc. IPQ40xx/AP-DK01.1-C1 > [ 0.000000] bootconsole [earlycon0] enabled > [ 0.000000] Memory policy: Data cache writealloc Can you compare to this? https://gist.github.com/anonymous/38a44876ff4d2033e16e941408561b64 This is loading an initramfs image, also the earlycon cmdline bits should work properly as well. -M -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
