This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to load firmware for Keystone navigator QMSS pdsp



Hi,

I have a custom K2L board. I have been trying to figure out how to load the firmware binary for the Keystone navigator qmss pdsp.

I have found the binary package "k2-fw-initrd.cpio.gz" from the SDK site and included it into my UBI filesystem volumes "boot" and "rootfs" (both of them to make sure it is found from somewhere) before ubinizing them and burning into the NAND.

In addition to this I have also tried adding this in the device tree, although not directly adviced in the TI documentation:

    pdsps {
        #address-cells = <1>;
        #size-cells = <1>;
        ranges;
        pdsp0@0x2a10000 {
            firmware = "/lib/firmware/ks2_qmss_pdsp_acc48.bin";
            syscon-intd = <&pdsp_intd>;
            reg = <0x2a10000 0x1000    /*iram */
                   0x2a0f000 0x100     /*reg*/
                   0x2a20000 0x4000>;  /*cmd*/
            id = <0>;
        };
        pdsp3@0x2a13000 {
            firmware = "/lib/firmware/ks2_qmss_pdsp_acc48.bin";
            firmware_type = "qos";
            syscon-intd = <&pdsp_intd>;
            reg = <0x2a13000 0x1000>,
                  <0x2a0f300 0x100>,
                  <0x2a2c000 0x4000>;
            reg-names = "iram", "regs", "command";
            id = <3>;
        };
        pdsp7@0x2a17000 {
            firmware = "/lib/firmware/ks2_qmss_pdsp_acc48.bin";
            firmware_type = "qos";
            syscon-intd = <&pdsp_intd>;
            reg = <0x2a17000 0x1000>,
                  <0x2a0f700 0x100>,
                  <0x2a3c000 0x4000>;
            reg-names = "iram", "regs", "command";
            id = <7>;
        };
    };

I am really lost. Please help. All I get is a kernel panic:

[    0.566660] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp0
[    0.575176] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp3
[    0.583684] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp7
[    0.592745] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 3 not started for range qos-inputs-0
[    0.601864] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 7 not started for range qos-inputs-1
[    0.610955] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 0 not started for range acc-low-0
[    0.629161] Unhandled fault: asynchronous external abort (0x211) at 0x0000000

[    0.636481] pgd = c0003000
[    0.639272] [00000000] *pgd=80000800004003, *pmd=00000000
[    0.644770] Internal error: : 211 [#1] PREEMPT SMP ARM
[    0.650000] Modules linked in:
[    0.653143] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.19-gdb0b54cdad #9
[    0.660201] Hardware name: Keystone
[    0.663777] task: de478000 ti: de466000 task.ti: de466000
[    0.669272] PC is at knav_dma_hw_init+0x4c/0xc0
[    0.673896] LR is at get_parent_ip+0x10/0x2c
[    0.678255] pc : [<c0422238>]    lr : [<c0048228>] psr: 60000013
[    0.678255] sp : de467e48  ip : f09a6000  fp : de64ddf8
[    0.689930] r10: c0881944  r9 : debe6b50  r8 : c0881944
[    0.695246] r7 : debe696c  r6 : 00000080  r5 : de64de08  r4 : de64dd90
[    0.701869] r3 : 0000445c  r2 : 00000000  r1 : 00000000  r0 : 00000000
[    0.708493] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM Segment kernel
[    0.715900] Control: 30c5387d  Table: 00003000  DAC: fffffffd
[    0.721739] Process swapper/0 (pid: 1, stack limit = 0xde466210)
[    0.727839] Stack: (0xde467e48 to 0xde468000)
[    0.732286] 7e40:                   00000095 de64dd90 de64de00 c0305868 00000000 00000000
[    0.740565] 7e60: 00000000 c016d518 00000095 de60b010 debe696c de64ddd4 00000b60 00000000
[    0.748843] 7e80: 00000080 00000000 00000008 0000445c 00001000 00000000 c07ed83c ffffffef
[    0.757121] 7ea0: de60b010 fffffdfb c082d97c 00000000 c07ed83c c07a6598 00000000 c0335d2c
[    0.765400] 7ec0: c0335cdc de60b010 c088314c 00000000 c082d97c c0334a48 de60b010 c082d97c
[    0.773678] 7ee0: de60b044 00000000 c07ceea0 c0334b9c 00000000 c082d97c c0334b10 c033317c
[    0.781957] 7f00: de406f5c de5604b4 c082d97c de7eaf80 c08354b0 c0334148 c07040c4 c082d97c
[    0.790235] 7f20: 00000006 c082d97c 00000006 2282743c 00000000 c033513c c0335c70 c07f9af0
[    0.798514] 7f40: 00000006 c00096e0 000139a1 00000000 2282743c 00000000 00000006 c07f9af0
[    0.806792] 7f60: 00000006 c07ed830 c085d000 00000095 c07a6598 c07a6dbc 00000006 00000006
[    0.815070] 7f80: 00000000 c07a6598 00000000 c057ae30 00000000 00000000 00000000 00000000
[    0.823348] 7fa0: 00000000 c057ae38 00000000 c000f668 00000000 00000000 00000000 00000000
[    0.831626] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    0.839904] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[    0.848194] [<c0422238>] (knav_dma_hw_init) from [<c0305868>] (knav_dma_probe+0x62c/0x6c0)
[    0.856564] [<c0305868>] (knav_dma_probe) from [<c0335d2c>] (platform_drv_probe+0x50/0xb0)
[    0.864932] [<c0335d2c>] (platform_drv_probe) from [<c0334a48>] (driver_probe_device+0x1e0/0x2a8)
[    0.873911] [<c0334a48>] (driver_probe_device) from [<c0334b9c>] (__driver_attach+0x8c/0x90)
[    0.882453] [<c0334b9c>] (__driver_attach) from [<c033317c>] (bus_for_each_dev+0x54/0x88)
[    0.890734] [<c033317c>] (bus_for_each_dev) from [<c0334148>] (bus_add_driver+0xec/0x1f8)
[    0.899015] [<c0334148>] (bus_add_driver) from [<c033513c>] (driver_register+0x78/0xf4)
[    0.907123] [<c033513c>] (driver_register) from [<c00096e0>] (do_one_initcall_debug+0x40/0x88)
[    0.915841] [<c00096e0>] (do_one_initcall_debug) from [<c07a6dbc>] (kernel_init_freeable+0x118/0x1e4)
[    0.925169] [<c07a6dbc>] (kernel_init_freeable) from [<c057ae38>] (kernel_init+0x8/0xf8)
[    0.933363] [<c057ae38>] (kernel_init) from [<c000f668>] (ret_from_fork+0x14/0x2c)
[    0.941033] Code: e594300c e7f03053 e1823003 e58c3004 (e5942008)
[    0.947231] ---[ end trace 7166a7bfb948fa03 ]---
[    0.951941] note: swapper/0[1] exited with preempt_count 1
[    0.957561] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    0.957561]
[    0.966888] CPU1: stopping
[    0.969683] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G D         4.4.19-gdb0b54cdad #9
[    0.977960] Hardware name: Keystone
[    0.981547] [<c0016320>] (unwind_backtrace) from [<c0012980>] (show_stack+0x10/0x14)
[    0.989396] [<c0012980>] (show_stack) from [<c02aa2fc>] (dump_stack+0x74/0x94)
[    0.996719] [<c02aa2fc>] (dump_stack) from [<c00152a0>] (handle_IPI+0x1bc/0x36c)
[    1.004216] [<c00152a0>] (handle_IPI) from [<c0009454>] (gic_handle_irq+0x80/0x8c)
[    1.011888] [<c0009454>] (gic_handle_irq) from [<c0580d80>] (__irq_svc+0x40/0x74)
[    1.019468] Exception stack(0xde49df90 to 0xde49dfd8)
[    1.024611] df80:                                     00000001 00000000 de49dfe8 c001f420
[    1.032890] dfa0: c08595c0 c058522c c08595c0 c07fa3a4 c0858d86 c080394c 00000000 00000001
[    1.041168] dfc0: 00000001 de49dfe0 c0010084 c0010088 60000013 ffffffff
[    1.047881] [<c0580d80>] (__irq_svc) from [<c0010088>] (arch_cpu_idle+0x30/0x3c)
[    1.055386] [<c0010088>] (arch_cpu_idle) from [<c005c33c>] (cpu_startup_entry+0x120/0x340)
[    1.063754] [<c005c33c>] (cpu_startup_entry) from [<800094ec>] (0x800094ec)
[    1.070815] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[    1.070815]

Best regards,

Ari

  • Hi Ari,

    I've forwarded this to the software experts. Their feedback should be posted here.

    BR
    Tsvetolin Shulev
  • Hello Tsvetolin,

    any news from the sw experts?

    BR, Ari

  • Hi Ari,

    I'm still waiting for their response.

    BR
    Tsvetolin Shulev
  • Hi Ari,

    I am not entirely familiar with that release, but looking through this: 

    processors.wiki.ti.com/.../MCSDK_to_Processor_SDK_Migration

    And what I know from MCSDK, what might be happening is that when you put the firmware under /lib/firmware, the filesystem is not yet mounted, so the driver is not finding it.

    The link above mentions that the firmware package you downloaded has to be passed to the kernel from U-boot.

    Regards,

    Mike

  • Hello Mike,

    thanks for your response.

    The file system is mounted alright, since the boot procedure finds the images for kernel, boot-monitor and device tree just fine. But according to the migration guide you mentioned I need to use an environment variable "name_fw_rd" and add the "k2-fw-initrd.cpio.gz" file into the boot volume of my UBI file system.

    I will try that and tell you how it succeeds.

    Best regards,

    Ari

  • Hello Mike,

    I added the environment variable "name_fw_rd" and also added the files "k2-fw-initrd.cpio.gz" and "k2-fw-initrd.cpio" into the "boot" volume of my UBI file system.

    K2L EVM # printenv name_fw_rd

    name_fw_rd=k2-fw-initrd.cpio.gz

    K2L EVM # ubifsls

             4348536  Tue Nov 29 11:14:33 2016  uImage-keystone-sri.bin

               44696  Tue Nov 29 14:20:40 2016  keystone-k2l-sri.dtb

               45056  Fri Nov 04 10:11:41 2016  skern-keystone-sri.bin

              218624  Wed Dec 07 10:23:47 2016  k2-fw-initrd.cpio

               64895  Tue Oct 04 05:23:20 2016  k2-fw-initrd.cpio.gz

    Still I cannot get it working. Now the u-boot complains about wrong ramdisk image format.

    K2L EVM # run get_fdt_ubi

    Loading file 'keystone-k2l-sri.dtb' to addr 0x87000000 with size 44696 (0x0000ae

    98)...

    Done

    K2L EVM # run get_mon_ubi

    Loading file 'skern-keystone-sri.bin' to addr 0x0c140000 with size 45056 (0x0000

    b000)...

    Done

    K2L EVM # run get_kern_ubi

    Loading file 'uImage-keystone-sri.bin' to addr 0x88000000 with size 4348536 (0x0

    0425a78)...

    Done

    K2L EVM # run run_mon

    ## installed monitor, freq [199680000], status 0

    K2L EVM # env print bootargs
    bootargs=console=ttyS0,115200n8 rootwait=1 earlyprintk rootfstype=ubifs root=ubi
    0:rootfs rootflags=sync rw ubi.mtd=2,2048 initrd=0x81000000,1M
    K2L EVM # bootm 0x88000000 0x81000000 0x87000000
    ## Booting kernel from Legacy Image at 88000000 ...
       Image Name:
       Created:      2016-11-29  11:14:33 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    4348472 Bytes = 4.1 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    Wrong Ramdisk Image Format
    Ramdisk image is corrupt or invalid


    I have tried also with k2-fw-initrd.cpio (the corresponding cpio.gz unzipped) also with the same result. Is there something wrong with my setup, do I need to define/edit some more environment variables and / or do I need to make an image header for the cpio.gz image and then put that into the "boot" volume of the UBI fs?

    Best regards,

    Ari

  • An update to my previous post:

    Making a header with mkimage tool fixed the problem of the "wrong ramdisk image format". Now the cpio.gz is accepted.

    But still the kernel does not find the firmware binaries:

    K2L EVM # bootm 0x88000000 0x81000000 0x87000000
    ## Booting kernel from Legacy Image at 88000000 ...
       Image Name:
       Created:      2016-11-29  11:14:33 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    4348472 Bytes = 4.1 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    ## Loading init Ramdisk from Legacy Image at 81000000 ...
       Image Name:
       Created:      2016-12-07  12:58:11 UTC
       Image Type:   ARM Linux RAMDisk Image (gzip compressed)
       Data Size:    64895 Bytes = 63.4 KiB
       Load Address: 00000000
       Entry Point:  00000000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 87000000
       Booting using the fdt blob at 0x87000000
       Loading Kernel Image ... OK
    OK
       Using Device Tree in place at 87000000, end 8700de97

    [    0.618837] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware

    for pdsp pdsp0

    [    0.627376] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware

    for pdsp pdsp3

    [    0.635857] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware

    for pdsp pdsp7

    On the other hand, now there is a new error message much before the above messages:

    [    0.000000] INITRD: 0x781000040+0x0000fd7f is not a memory region - disabling
     initrd

    Should I use some specific memory area for loading the firmware before giving the bootm command, or how should I provide the firmware into the system? I used now 0x81000000.

    Best regards,

    Ari

  • Hi,
    please see the posts above. As an update I made the ramdisk image have load address of 0x81000000, but it resultes the same failure. Also load address of 0x0c000000 did the same. The kernel fails getting firmware for pdsp.

    Please help, I have tried all tricks I can imagine so far.

    - Ari
  • You are on Processors SDK, right? Is it a recent version?

    Looking further into it, the firmware package is actually it's own ramfs filesystem image that has to be mounted separately from the rest of the filesystem to get the firmware images.

    I found this patch submission from one of our developers that implemented this feature:  

    lists.denx.de/.../247685.html

    This patch tells me that U-boot has to have support for this feature. The file, k2-fw-initrd.cpio.gz, has to be located somewhere that U-boot can download it, along with your Linux kernel, dts, and boot monitor.

    U-boot will download the package, and provide an address for it through the bootz command.

    Make sure you are running a U-boot with this patch. If you previously used an older version without this patch, you might be loading an old environment, you can reset the environment with "env default -a"

    Regards,

    Mike

  • Hello Mike!

    Yes, I use the kernel 4.4.19 from the Processor SDK, but the u-boot is from kernel 3.10. U-boot from 4.4 fails using the NAND for some reason fro me. Therefore I prefer using my "good old" u-boot. All the versions should be new enough to support cpio and gz formats and firmware.

    I have seen the new kernel boot uses bootz while I am still stuck to bootm. I cannot see much difference between them when it comes to loading the firmware. I can bootm / bootz the kernel image with both formats as well.

    I studied the link you sent in the last post and made a slight progress. It now seems the kernel loads the image, please confirm:

    ## installed monitor, freq [199680000], status 0
    ## Booting kernel from Legacy Image at 88000000 ...
    Image Name:
    Created: 2016-11-29 11:14:33 UTC
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 4348472 Bytes = 4.1 MiB
    Load Address: 80008000
    Entry Point: 80008000
    Verifying Checksum ... OK

    ## Loading init Ramdisk from Legacy Image at 0c000000 ... Image Name: Created: 2016-12-08 10:11:47 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 218624 Bytes = 213.5 KiB
    Load Address: 99000000 <----- These could be 0 as well, right? Just tried several tricks. Entry Point: 99000000 <-----
    Verifying Checksum ... OK
    ## Flattened Device Tree blob at 87000000
    Booting using the fdt blob at 0x87000000
    Loading Kernel Image ... OK
    OK
    Using Device Tree in place at 87000000, end 8700de97

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    [ 0.000000] Booting Linux on physical CPU 0x0


    ...
    [    0.446954] Unpacking initramfs...
    [    0.451959] Freeing initrd memory: 216K (cc000000 - cc036000)      <---- I put it 0c000000, why is it now cc000000???


    But still the firmware is missing and the kernel panics:

    [    0.577202] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp0
    [    0.585703] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp3
    [    0.594199] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp7
    
    [    0.603250] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 3 not started for range qos-inputs-0
    [    0.612349] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 7 not started for range qos-inputs-1
    [    0.621460] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 0 not started for range acc-low-0
     [ 0.639623] Unhandled fault: asynchronous external abort (0x211) at 0x00000000

    There is also a problem with IRQ:

    [    0.251688] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.258351] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.264973] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.271637] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    

    but I don't know if it is fatal or not.

    I put the complete log to below. I hope it leads to the source of the problems.

     

    Best regards,

    Ari

    Creating 1 MTD partitions on "nand0":
    0x000000180000-0x000020000000 : "mtd=2"
    UBI: attaching mtd1 to ubi0
    UBI: physical eraseblock size:   131072 bytes (128 KiB)
    UBI: logical eraseblock size:    126976 bytes
    UBI: smallest flash I/O unit:    2048
    UBI: VID header offset:          2048 (aligned 2048)
    UBI: data offset:                4096
    UBI: attached mtd1 to ubi0
    UBI: MTD device name:            "mtd=2"
    UBI: MTD device size:            510 MiB
    UBI: number of good PEBs:        4080
    UBI: number of bad PEBs:         4
    UBI: max. allowed volumes:       128
    UBI: wear-leveling threshold:    4096
    UBI: number of internal volumes: 1
    UBI: number of user volumes:     2
    UBI: available PEBs:             0
    UBI: total number of reserved PEBs: 4080
    UBI: number of PEBs reserved for bad PEB handling: 40
    UBI: max/mean erase counter: 1/0
    UBIFS: mounted UBI device 0, volume 0, name "boot"
    UBIFS: mounted read-only
    UBIFS: file system size:   19046400 bytes (18600 KiB, 18 MiB, 150 LEBs)
    UBIFS: journal size:       2920448 bytes (2852 KiB, 2 MiB, 23 LEBs)
    UBIFS: media format:       w4/r0 (latest is w4/r0)
    UBIFS: default compressor: LZO
    UBIFS: reserved for root:  0 bytes (0 KiB)
    Loading file 'k2-fw-sri.gz' to addr 0x0c000000 with size 218688 (0x00035640)...
    Done
    Loading file 'keystone-k2l-sri.dtb' to addr 0x87000000 with size 44696 (0x0000ae98)...
    Done
    Loading file 'skern-keystone-sri.bin' to addr 0x0c140000 with size 45056 (0x0000b000)...
    Done
    Loading file 'uImage-keystone-sri.bin' to addr 0x88000000 with size 4348536 (0x00425a78)...
    Done
    ## installed monitor, freq [199680000], status 0
    ## Booting kernel from Legacy Image at 88000000 ...
       Image Name:
       Created:      2016-11-29  11:14:33 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    4348472 Bytes = 4.1 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    ## Loading init Ramdisk from Legacy Image at 0c000000 ...
       Image Name:
       Created:      2016-12-08  10:11:47 UTC
       Image Type:   ARM Linux RAMDisk Image (gzip compressed)
       Data Size:    218624 Bytes = 213.5 KiB
       Load Address: 99000000
       Entry Point:  99000000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 87000000
       Booting using the fdt blob at 0x87000000
       Loading Kernel Image ... OK
    OK
       Using Device Tree in place at 87000000, end 8700de97
    
    Starting kernel ...
    
    Uncompressing Linux... done, booting the kernel.
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Initializing cgroup subsys cpu
    [    0.000000] Initializing cgroup subsys cpuacct
    [    0.000000] Linux version 4.4.19-gdb0b54cdad (neukkari@xskybex-laptop)
     (gcc version 4.7.3 20130205 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.02-01-20130221 - Linaro GCC 2013.02) )
     #9 SMP PREEMPT Tue Nov 29 13:07:27 EET 2016
    [    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c5387d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
    [    0.000000] Machine model: Texas Instruments Keystone 2 Lamarr EVM
    [    0.000000] bootconsole [earlycon0] enabled
    [    0.000000] Switching physical address space to 0x800000000
    [    0.000000] Reserved memory: created CMA memory pool at 0x000000081f800000, size 8 MiB
    [    0.000000] Reserved memory: initialized node dsp_common_cma_pool, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x0000000820000000, size 512 MiB
    [    0.000000] Reserved memory: initialized node dsp_reserved_mpm_area, compatible id shared-dma-pool
    [    0.000000] cma: Reserved 16 MiB at 0x000000085f000000
    [    0.000000] Forcing write-allocate cache policy for SMP
    [    0.000000] Memory policy: Data cache writealloc
    [    0.000000] psci: probing for conduit method from DT.
    [    0.000000] psci: Using PSCI v0.1 Function IDs from DT
    [    0.000000] PERCPU: Embedded 13 pages/cpu @debaf000 s21248 r8192 d23808 u53248
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260608
    [    0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 earlyprintk rootfstype=ubifs
     root=ubi0:rootfs rootflags=sync rw ubi.mtd=ubifs,2048
    [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    [    0.000000] Memory: 1006072K/1048576K available (5804K kernel code, 365K rwdata, 1992K rodata,
     360K init, 200K bss, 17928K reserved, 24576K cma-reserved, 507904K highmem)
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    [    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
    [    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
    [    0.000000]       .text : 0xc0008000 - 0xc07a56a8   (7798 kB)
    [    0.000000]       .init : 0xc07a6000 - 0xc0800000   ( 360 kB)
    [    0.000000]       .data : 0xc0800000 - 0xc085b614   ( 366 kB)
    [    0.000000]        .bss : 0xc085d000 - 0xc088f184   ( 201 kB)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    [    0.000000] Preemptible hierarchical RCU implementation.
    [    0.000000]  Build-time adjustment of leaf fanout to 32.
    [    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
    [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
    [    0.000000] NR_IRQS:16 nr_irqs:16 16
    [    0.000000] of_psc_clk_init: error registering clk clkpcie1
    [    0.000000] Architected cp15 timer(s) running at 199.68MHz (virt).
    [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
     0x2e0d652267, max_idle_ns: 440795206693 ns
    [    0.000003] sched_clock: 56 bits at 199MHz, resolution 5ns, wraps every 4398046511101ns
    [    0.008108] Switching to timer-based delay loop, resolution 5ns
    [    0.014235] keystone timer clock @199680000 Hz
    [    0.018960] Console: colour dummy device 80x30
    [    0.023504] Calibrating delay loop (skipped), value calculated using timer frequency.. 399.36 BogoMIPS (lpj=1996800)
    [    0.034143] pid_max: default: 4096 minimum: 301
    [    0.038817] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.045535] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.053030] Initializing cgroup subsys io
    [    0.057146] Initializing cgroup subsys devices
    [    0.061682] Initializing cgroup subsys freezer
    [    0.066226] CPU: Testing write buffer coherency: ok
    [    0.071363] /cpus/cpu@0 missing clock-frequency property
    [    0.076783] /cpus/cpu@1 missing clock-frequency property
    [    0.082203] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    [    0.087985] Setting up static identity map for 0x80008300 - 0x8000840c
    [    0.175932] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    [    0.176002] Brought up 2 CPUs
    [    0.184827] SMP: Total of 2 processors activated (798.72 BogoMIPS).
    [    0.191189] CPU: All CPU(s) started in SVC mode.
    [    0.196174] devtmpfs: initialized
    [    0.208013] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
    [    0.216126] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    [    0.226633] pinctrl core: initialized pinctrl subsystem
    [    0.232250] NET: Registered protocol family 16
    [    0.237499] DMA: preallocated 256 KiB pool for atomic coherent allocations
    [    0.251688] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.258351] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.264973] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.271637] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.284112] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
    [    0.292244] hw-breakpoint: maximum watchpoint size is 8 bytes.
    [    0.307048] vgaarb: loaded
    [    0.310102] SCSI subsystem initialized
    [    0.314321] usbcore: registered new interface driver usbfs
    [    0.319977] usbcore: registered new interface driver hub
    [    0.325473] usbcore: registered new device driver usb
    [    0.331819] pps_core: LinuxPPS API ver. 1 registered
    [    0.336890] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [    0.346182] PTP clock support registered
    [    0.351110] clocksource: Switched to clocksource arch_sys_counter
    [    0.382386] NET: Registered protocol family 2
    [    0.387242] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.394437] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
    [    0.401016] TCP: Hash tables configured (established 4096 bind 4096)
    [    0.407527] UDP hash table entries: 256 (order: 1, 8192 bytes)
    [    0.413478] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
    [    0.419970] NET: Registered protocol family 1
    [    0.424622] RPC: Registered named UNIX socket transport module.
    [    0.430636] RPC: Registered udp transport module.
    [    0.435443] RPC: Registered tcp transport module.
    [    0.440238] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.446954] Unpacking initramfs...
    [    0.451959] Freeing initrd memory: 216K (cc000000 - cc036000)
    [    0.457962] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
    [    0.467086] platform alarmtimer: set dma_pfn_offset00780000
    [    0.473212] futex hash table entries: 16 (order: -2, 1024 bytes)
    [    0.489831] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    [    0.496418] ntfs: driver 2.1.32 [Flags: R/O].
    [    0.501177] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    [    0.509969] NET: Registered protocol family 38
    [    0.514611] bounce: pool size: 64 pages
    [    0.518755] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
    [    0.526282] io scheduler noop registered
    [    0.530305] io scheduler deadline registered
    [    0.534711] io scheduler cfq registered (default)
    [    0.539656] keystone_irq soc:keystone_irq@26202a0: irqchip registered, nr_irqs 28
    [    0.548607] keystone-navigator-qmss soc:qmss@2a40000: qmgr start queue 0, number of queues 8192
    [    0.557533] keystone-navigator-qmss soc:qmss@2a40000: added qmgr start queue
    0, num of queues 8192, reg_peek f09c0000, reg_status f0986000, reg_config f0988000,
     reg_region f098a000, reg_push f0a00000, reg_pop f0a40000
    [    0.577202] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp0
    [    0.585703] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp3
    [    0.594199] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp7
    [    0.603250] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 3 not started for range qos-inputs-0
    [    0.612349] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 7 not started for range qos-inputs-1
    [    0.621460] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 0 not started for range acc-low-0
    [    0.639623] Unhandled fault: asynchronous external abort (0x211) at 0x00000000
    [    0.646942] pgd = c0003000
    [    0.649733] [00000000] *pgd=80000800004003, *pmd=00000000
    [    0.655232] Internal error: : 211 [#1] PREEMPT SMP ARM
    [    0.660462] Modules linked in:
    [    0.663606] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.19-gdb0b54cdad #9
    [    0.670663] Hardware name: Keystone
    [    0.674238] task: de478000 ti: de466000 task.ti: de466000
    [    0.679734] PC is at knav_dma_hw_init+0x4c/0xc0
    [    0.684358] LR is at get_parent_ip+0x10/0x2c
    [    0.688718] pc : [<c0422238>]    lr : [<c0048228>]    psr: 60000013
    [    0.688718] sp : de467e48  ip : f09a6000  fp : de7fa138
    [    0.700392] r10: c0881944  r9 : debe6b50  r8 : c0881944
    [    0.705708] r7 : debe696c  r6 : 00000080  r5 : de7fa148  r4 : de7fa0d0
    [    0.712331] r3 : 0000445c  r2 : 00000000  r1 : 00000000  r0 : 00000000
    [    0.718955] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
    [    0.726362] Control: 30c5387d  Table: 00003000  DAC: fffffffd
    [    0.732201] Process swapper/0 (pid: 1, stack limit = 0xde466210)
    [    0.738301] Stack: (0xde467e48 to 0xde468000)
    [    0.742749] 7e40:                   00000095 de7fa0d0 de7fa140 c0305868 00000000 00000000
    [    0.751028] 7e60: 00000000 c016d518 00000095 de60b010 debe696c de7fa114 00000b60 00000000
    [    0.759307] 7e80: 00000080 00000000 00000008 0000445c 00001000 00000000 c07ed83c ffffffef
    [    0.767586] 7ea0: de60b010 fffffdfb c082d97c 00000000 c07ed83c c07a6598 00000000 c0335d2c
    [    0.775864] 7ec0: c0335cdc de60b010 c088314c 00000000 c082d97c c0334a48 de60b010 c082d97c
    [    0.784142] 7ee0: de60b044 00000000 c07ceea0 c0334b9c 00000000 c082d97c c0334b10 c033317c
    [    0.792421] 7f00: de406f5c de5604b4 c082d97c de54a680 c08354b0 c0334148 c07040c4 c082d97c
    [    0.800699] 7f20: 00000006 c082d97c 00000006 2323ac4e 00000000 c033513c c0335c70 c07f9af0
    [    0.808977] 7f40: 00000006 c00096e0 00013943 00000000 2323ac4e 00000000 00000006 c07f9af0
    [    0.817256] 7f60: 00000006 c07ed830 c085d000 00000095 c07a6598 c07a6dbc 00000006 00000006
    [    0.825534] 7f80: 00000000 c07a6598 00000000 c057ae30 00000000 00000000 00000000 00000000
    [    0.833812] 7fa0: 00000000 c057ae38 00000000 c000f668 00000000 00000000 00000000 00000000
    [    0.842090] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    [    0.850368] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
    [    0.858657] [<c0422238>] (knav_dma_hw_init) from [<c0305868>] (knav_dma_probe+0x62c/0x6c0)
    [    0.867028] [<c0305868>] (knav_dma_probe) from [<c0335d2c>] (platform_drv_probe+0x50/0xb0)
    [    0.875397] [<c0335d2c>] (platform_drv_probe) from [<c0334a48>] (driver_probe_device+0x1e0/0x2a8)
    [    0.884375] [<c0334a48>] (driver_probe_device) from [<c0334b9c>] (__driver_attach+0x8c/0x90)
    [    0.892917] [<c0334b9c>] (__driver_attach) from [<c033317c>] (bus_for_each_dev+0x54/0x88)
    [    0.901198] [<c033317c>] (bus_for_each_dev) from [<c0334148>] (bus_add_driver+0xec/0x1f8)
    [    0.909480] [<c0334148>] (bus_add_driver) from [<c033513c>] (driver_register+0x78/0xf4)
    [    0.917587] [<c033513c>] (driver_register) from [<c00096e0>] (do_one_initcall_debug+0x40/0x88)
    [    0.926306] [<c00096e0>] (do_one_initcall_debug) from [<c07a6dbc>] (kernel_init_freeable+0x118/0x1e4)
    [    0.935634] [<c07a6dbc>] (kernel_init_freeable) from [<c057ae38>] (kernel_init+0x8/0xf8)
    [    0.943829] [<c057ae38>] (kernel_init) from [<c000f668>] (ret_from_fork+0x14/0x2c)
    [    0.951500] Code: e594300c e7f03053 e1823003 e58c3004 (e5942008)
    [    0.957698] ---[ end trace 3d4816224244a80f ]---
    [    0.962407] note: swapper/0[1] exited with preempt_count 1
    [    0.968015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
    [    0.968015]
    [    0.977341] CPU1: stopping
    [    0.980136] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G      D         4.4.19-gdb0b54cdad #9
    [    0.988414] Hardware name: Keystone
    [    0.992000] [<c0016320>] (unwind_backtrace) from [<c0012980>] (show_stack+0x10/0x14)
    [    0.999849] [<c0012980>] (show_stack) from [<c02aa2fc>] (dump_stack+0x74/0x94)
    [    1.007172] [<c02aa2fc>] (dump_stack) from [<c00152a0>] (handle_IPI+0x1bc/0x36c)
    [    1.014669] [<c00152a0>] (handle_IPI) from [<c0009454>] (gic_handle_irq+0x80/0x8c)
    [    1.022340] [<c0009454>] (gic_handle_irq) from [<c0580d80>] (__irq_svc+0x40/0x74)
    [    1.029921] Exception stack(0xde49df90 to 0xde49dfd8)
    [    1.035064] df80:                                     00000001 00000000 de49dfe8 c001f420
    [    1.043342] dfa0: c08595c0 c058522c c08595c0 c07fa3a4 c0858d86 c080394c 00000000 00000001
    [    1.051620] dfc0: 00000001 de49dfe0 c0010084 c0010088 60000013 ffffffff
    [    1.058334] [<c0580d80>] (__irq_svc) from [<c0010088>] (arch_cpu_idle+0x30/0x3c)
    [    1.065835] [<c0010088>] (arch_cpu_idle) from [<c005c33c>] (cpu_startup_entry+0x120/0x340)
    [    1.074204] [<c005c33c>] (cpu_startup_entry) from [<800094ec>] (0x800094ec)
    [    1.081266] ---[ end Kernel panic - not syncing: Attempted to kill init! exit code=0x0000000b
    [    1.081266]
    
    
    

     

  • Hi, Ari,

    Please give me some time to understand the issue and try it myself. Then, I'll post the answer on this thread. If you created another thread on the same issue, do you mind post the link in this thead as well so we can link both together.

    Thanks for your patience.

    Rex

  • Hello Rex,
    nice to hear from you! :-)
    I have described my problem already in the following thread.

    e2e.ti.com/.../2052093

    Please tell me if you need more details.
    Thanks for your patience from my side, too!

    BRS, Ari
  • Hi, Ari,

    First of all, do you simply want to get the k2-fw-initrd.cpio.gz onto the filesystem so kernel will boot with it? And you tried to build the filesystem with this fw-initrd file but having issue?

    I don't get a clear picture on how you are booting your kernel. It looks to me that you are using UBI boot. That is u-boot in NOR, and Kernel/DTB/filesystem on NAND. If that is the case, TI's prebuilt image in filesystem/tisdk-server-rootfs-image-k2e-evm.ubi already has k2-fw-initrd.cpio.gz in the filesystem. Can you use this ubi file?

    You also mentioned that you have 2 volumes, boot and rootfs, on the UBI filesystem which puzzles me, It seems to me that you are booting off a media, such as a SD card, or u-boot is also on NAND in different partition? The k2-fw-initrd.cpio.gz file should be in rootfs partition under /boot directory together with kernel and dtb images.

    I boot up my EVM using UBI boot by setting u-boot env variable, "setenv boot ubi", and it shows

    root@k2e-evm:/boot# ls
    devicetree-zImage-keystone-k2e-evm.dtb  vmlinux-4.4.19-gdb0b54cdad
    k2-fw-initrd.cpio.gz                    zImage
    keystone-k2e-evm.dtb                    zImage-4.4.19-gdb0b54cdad
    skern-k2e.bin
    root@k2e-evm:/boot#

    If the UBI image is not pre-burnt in the NAND, you can use the following commands in u-boot to burn it if you have tftp server setup.

    => run get_ubi_net

    => run burn_ubi

    Make sure soft link tisdk-server-rootfs-image-k2e-evm.ubi to the file name shown in name_ubi. That is

       k2e-evm-ubifs.ubi -> tisdk-server-rootfs-image-k2e-evm.ubi on the tftp server.

    You also mentioned mkimage. That further confused me. It seems to be related to booting kernel using uinitrd. If you tried to boot using uinitrd, I'll need some more time to port it from MCSDK to Proc SDK. Because the load addresses for FDT, and kernel have been changed in ProcSDk, the uinitrd boot does not work any more, and I need to figure out how to work around in ProcSDK. If you are not booting kernel using uinitrd, then ignore this paragraph.

    I hope the info above would provide some useful tips for you. If not, I need to go through how you boot, what you have, etc. to get an overall picture.

    Rex

  • Hello Rex!

    > First of all, do you simply want to get the k2-fw-initrd.cpio.gz onto the filesystem so kernel will boot with it?

    > And you tried to build the filesystem with this fw-initrd file but having issue?

    Yes, this is exactly and simply what I have been trying to do. I have built my own UBI fs file and it mounts alright. The only problem with it is that the boot does not find the firmware files although included in my UBI fs and the u-boot also loads the firmware image "k2-fw-initrd.cpio.gz" without errors at the same phase it loads the device tree, boot-monitor and the kernel image. All these succeed so I think the UBI fs itself is working.

    > It looks to me that you are using UBI boot. That is u-boot in NOR, and Kernel/DTB/filesystem on NAND.

    > If that is the case, TI's prebuilt image in filesystem/tisdk-server-rootfs-image-k2e-evm.ubi

    > already has k2-fw-initrd.cpio.gz in the filesystem. Can you use this ubi file?

    You are right. I have the u-boot in NOR and the rest of files (uImage, dtb, skern + all the Linux stuff) in NAND in a UBI fs. My UBI fs has 2 volumes:

    boot

    this volume has dtb, skern, uImage and k2-fw-initrd.cpio.gz

    rootfs

    this volume has the complete Linux file system.

    I can "ubifsmount" both these volumes one at a time, and see the contents of them by using "ubifsls" command, so they work alright. I am not 100% sure whether it is right to arrange the volumes like this or should I use only one volume or create some more volumes like "initrd" etc I have seen somebody using in some forum posts I have read. It does not matter much to me. I only want the Linux to boot on my board from the UBI file system.

    I will try the "tisdk-server-rootfs-image-k2e-evm.ubi" as you suggest. If there is a simular image for K2L I could try that instead, but I guess they don't have much difference in this case. I let you know when I have tried that.

    > The k2-fw-initrd.cpio.gz file should be in rootfs partition under /boot directory together with kernel and dtb images.

    This I have not tried yet, but I will. I have tried also using only rootfs volume and put the firmware binaries unzipped into /lib/firmware like told in some user guides referenced in some forum posts, but still the boot did not find them.

    So you mean that "rootfs" (or "boot", I can name it as I want, of course) is the only volume I should have in the UBI fs?

    I tried it in that way in the first place but while reading various posts and user guides I was (mis)lead to use several volumes. Nevertheless, I will give it a try like you suggest - putting all the boot stuff into /boot of the "rootfs" volume. That way they are available all the time starting from the boot procedure. Sounds like it might work.

    > If the UBI image is not pre-burnt in the NAND,

    > you can use the following commands in u-boot to burn it if you have tftp server setup.

    I have still some issues with the network so I prefer transferring the images into DDR3 through CCS for "burn_ubi". For some reason the PSC cannot be enabled for the net-cp domain, but that is being investigated in another thread (been waiting for an answer there for a week now, though).

    > You also mentioned mkimage. That further confused me. It seems to be related to booting kernel using uinitrd.

    I used "mkimage" only for making the "k2-fw-initrd.cpio.gz" loadable for the u-boot. But if it needs be in the /boot, then I don't need to use the mkimage any more for that purpose. No, I am not willing to do any uinitrd boot. The normal UBI boot is what I want, just like the TI EVM boards boot.

    Thanks for these hints, I will try them ASAP and let you know what happens.

    Best regards,

    Ari

  • Hello Rex,

    I have now tried to follow your suggestions as well as possible.

    1. Relocating the firmware image.

    I tried adding the firmware cpio.gz into /boot of the rootfs volume and modified the u-boot environment parameters accordingly to mount the "rootfs" instead of "boot". Amazingly it booted without kernel panic into the login prompt, but still the firmware was not found.

    [    0.566660] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp0

    [    0.575176] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp3

    [    0.583684] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmware for pdsp pdsp7

    This means that the missing firmware is not the reason for the kernel panic like I have been believing until now, because the panic happens immediately after the firmware error.

    The second time after power cycling the board, and all the times after that, the kernel panics at the same point like before, so I am back in the point where I have been for weeks already.

    2. Using tisdk-server-rootfs-image-k2e-evm.ubi

    For some reason the image does not work. Mounting it fails. I will try re-burning it. Now it only gives this:

    Creating 1 MTD partitions on "nand0":

    0x000000180000-0x000020000000 : "mtd=2"

    UBI: attaching mtd1 to ubi0

    UBI: physical eraseblock size:   131072 bytes (128 KiB)

    UBI: logical eraseblock size:    126976 bytes

    UBI: smallest flash I/O unit:    2048

    UBI: VID header offset:          2048 (aligned 2048)

    UBI: data offset:                4096

    UBI error: validate_ec_hdr: bad VID header offset 4096, expected 2048

    UBI error: validate_ec_hdr: bad EC header

    UBI error: ubi_io_read_ec_hdr: validation failed for PEB 0

    UBI error: ubi_init: cannot attach mtd1

    UBI error: ubi_init: UBI error: cannot initialize UBI, error -22

    UBI init error 22

    UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19

    UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'ubi:rootfs

    ' errno=-19!

    ubifsmount - mount UBIFS volume

    Usage:

    ubifsmount <volume-name>

       - mount 'volume-name' volume

    K2L EVM #

     

    For me this indicates the UBI image is corrupted.

    I suppose I don't need to ubinize the "tisdk-server-rootfs-image-k2e-evm.ubi", right? It should be enough just burn it into the NAND as such, right?

    Best regards,

    Ari

  • One more thing:
    Could the enable PSC failure be the reason for the kernel panic? It happens that the PSC enabling succeeds about once per day when trying it now and then in our board. Could it be so that the kernel boot also works at the same moment when the PSC enable for the net-cp happens to work?

    I will request the experts in my "PSC" thread to say something.

    BRS, Ari
  • I retried re-burning the "tisdk-server-rootfs-image-k2e-evm.ubi". Again the same failure. The image is somehow corrupted. I don't know how. I have not modified it in any way. Only unzipped from the Processor SDK's K2L binary package and Flashed as such.
    - Ari
  • Hello Rex,
    it looks that the site does not send the email notifications about the new posts. Have you seen my latest posts?
    - Ari

  • Ari,

    I got all the notifications from your posts.

    You mentioned "the u-boot also loads the firmware image "k2-fw-initrd.cpio.gz" without errors". I am not sure what this means. My impression is that u-boot does not load the firmware.

    You have:

    My UBI fs has 2 volumes:
      boot
         this volume has dtb, skern, uImage and k2-fw-initrd.cpio.gz
      rootfs
         this volume has the complete Linux file system.

    That is not the way I understand how it should be. I think the ubi has only one partition, rootfs. The kernel, dtb, skern, and k2-fw-initrd.cpio.gz should be in rootfs:/boot directory. From the ubi image on the nand, it only shows one partition.

    => ubi part
    Device 0: nand0, partition ubifs

    => run init_ubi
    Unmounting UBIFS volume rootfs!
    ubi0: detaching mtd1
    ubi0: mtd1 is detached
    ubi0: attaching mtd1
    ubi0: scanning is finished
    ubi0: volume 0 ("rootfs") re-sized from 3159 to 4000 LEBs
    ubi0: attached mtd1 (name "mtd=2", size 510 MiB)
    ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
    ubi0: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0
    ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
    ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1710674976
    ubi0: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB handling: 76
    => ubifsls
    <DIR>        6352  Mon Oct 03 23:43:20 2016  bin
    <DIR>         160  Mon Oct 03 21:51:08 2016  dev
    <DIR>        7408  Mon Oct 03 23:43:39 2016  etc
    <DIR>        9736  Mon Oct 03 22:22:26 2016  lib
    <DIR>         304  Mon Oct 03 23:41:56 2016  mnt
    <DIR>         224  Mon Oct 03 22:38:57 2016  opt
    <DIR>         160  Mon Oct 03 23:43:29 2016  run
    <DIR>         224  Mon Oct 03 22:20:38 2016  srv
    <DIR>         160  Mon Oct 03 21:51:08 2016  tmp
    <DIR>         160  Mon Oct 03 21:51:08 2016  sys
    <DIR>         808  Mon Oct 03 22:22:13 2016  var
    <DIR>         752  Mon Oct 03 22:22:26 2016  usr
    <DIR>         352  Mon Oct 03 22:23:47 2016  www
    <DIR>         728  Mon Oct 03 23:43:29 2016  boot
    <DIR>         224  Mon Oct 03 21:51:08 2016  home
    <LNK>          20  Mon Oct 03 22:25:12 2016  init
    <DIR>         160  Mon Oct 03 21:51:08 2016  proc
    <DIR>        7976  Mon Oct 03 23:43:23 2016  sbin
    <DIR>         224  Mon Oct 03 21:51:35 2016  include
    <DIR>         160  Mon Oct 03 21:51:08 2016  media
    => ubifsls boot
             13325820  Mon Oct 03 22:40:24 2016  vmlinux-4.4.19-gdb0b54cdad
                45056  Mon Oct 03 22:08:00 2016  skern-k2e.bin
                44512  Mon Oct 03 22:40:24 2016  devicetree-zImage-keystone-k2e-evm.dtb
              3462456  Mon Oct 03 22:40:24 2016  zImage-4.4.19-gdb0b54cdad
    <LNK>          38  Mon Oct 03 23:43:29 2016  keystone-k2e-evm.dtb
    <LNK>          25  Mon Oct 03 23:43:29 2016  zImage
                64900  Mon Oct 03 22:45:10 2016  k2-fw-initrd.cpio.gz
    =>

    Please send me your u-boot version.and the output from printenv. I asuume your kernel and filesytem are from the same release package. Are you trying the images on TI EVM? I don't have a K2L EVM, but K2E is the same platform without wireless. You should stay with the K2L package which can be downloaded from Linux procSDK site. The commands and steps I used on K2E apply to K2L

    Not sure how you transfer images through CCS, but if you have u-boot up and then connect the CCS, the power for the necessary components should have been handled. Copying images to NAND, I don't believe the power for NetCP matters.

    I suggested you use TI EVM, and boot with prebuilt images. Once it works for you, then copy the what you learn from EVM and apply them to custom board.

    Attached is the boot logs from KS2 using ubi boot. The image in NAND is tisdk-server-rootfs-image-k2e-evm.ubi from Proc SDK 3.1.0.6.

    Please let me know if you can get EVM up and running. We can only support TI platform and be sure it does not have issues.

    Rex

    
    

     

    My UBI fs has 2 volumes:

    boot

    this volume has dtb, skern, uImage and k2-fw-initrd.cpio.gz

    rootfs

    this volume has the complete Linux file system.

  • just realized that I didn't attach the logs, and here it is.

    => ubi part
    Device 0: nand0, partition ubifs
    => run init_ubi
    Unmounting UBIFS volume rootfs!
    ubi0: detaching mtd1
    ubi0: mtd1 is detached
    ubi0: attaching mtd1
    ubi0: scanning is finished
    ubi0: volume 0 ("rootfs") re-sized from 3159 to 4000 LEBs
    ubi0: attached mtd1 (name "mtd=2", size 510 MiB)
    ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
    ubi0: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0
    ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
    ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1710674976
    ubi0: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB handling: 76
    => ubifsls
    <DIR>        6352  Mon Oct 03 23:43:20 2016  bin
    <DIR>         160  Mon Oct 03 21:51:08 2016  dev
    <DIR>        7408  Mon Oct 03 23:43:39 2016  etc
    <DIR>        9736  Mon Oct 03 22:22:26 2016  lib
    <DIR>         304  Mon Oct 03 23:41:56 2016  mnt
    <DIR>         224  Mon Oct 03 22:38:57 2016  opt
    <DIR>         160  Mon Oct 03 23:43:29 2016  run
    <DIR>         224  Mon Oct 03 22:20:38 2016  srv
    <DIR>         160  Mon Oct 03 21:51:08 2016  tmp
    <DIR>         160  Mon Oct 03 21:51:08 2016  sys
    <DIR>         808  Mon Oct 03 22:22:13 2016  var
    <DIR>         752  Mon Oct 03 22:22:26 2016  usr
    <DIR>         352  Mon Oct 03 22:23:47 2016  www
    <DIR>         728  Mon Oct 03 23:43:29 2016  boot
    <DIR>         224  Mon Oct 03 21:51:08 2016  home
    <LNK>          20  Mon Oct 03 22:25:12 2016  init
    <DIR>         160  Mon Oct 03 21:51:08 2016  proc
    <DIR>        7976  Mon Oct 03 23:43:23 2016  sbin
    <DIR>         224  Mon Oct 03 21:51:35 2016  include
    <DIR>         160  Mon Oct 03 21:51:08 2016  media
    => ubifsls boot
             13325820  Mon Oct 03 22:40:24 2016  vmlinux-4.4.19-gdb0b54cdad
                45056  Mon Oct 03 22:08:00 2016  skern-k2e.bin
                44512  Mon Oct 03 22:40:24 2016  devicetree-zImage-keystone-k2e-evm.dtb
              3462456  Mon Oct 03 22:40:24 2016  zImage-4.4.19-gdb0b54cdad
    <LNK>          38  Mon Oct 03 23:43:29 2016  keystone-k2e-evm.dtb
    <LNK>          25  Mon Oct 03 23:43:29 2016  zImage
                64900  Mon Oct 03 22:45:10 2016  k2-fw-initrd.cpio.gz
    => setenv boot ubi
    => saveenv
    Saving Environment to NAND...
    Erasing NAND...
    Erasing at 0x120000 -- 100% complete.
    Writing to NAND... OK
    => boot
    Unmounting UBIFS volume rootfs!
    ubi0: detaching mtd1
    ubi0: mtd1 is detached
    ubi0: attaching mtd1
    ubi0: scanning is finished
    ubi0: attached mtd1 (name "mtd=2", size 510 MiB)
    ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
    ubi0: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0
    ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
    ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1710674976
    ubi0: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB handling: 76
    Loading file '/boot/k2-fw-initrd.cpio.gz' to addr 0x88080000...
    Done
    Loading file '/boot/keystone-k2e-evm.dtb' to addr 0x88000000...
    Done
    Loading file '/boot/skern-k2e.bin' to addr 0x0c140000...
    Done
    Loading file '/boot/zImage' to addr 0x82000000...
    Done
    K2_BM_15.07-39-g035329c SoC:k2e built:18:01:05, Oct  3 2016
    
    ## installed monitor, freq [208333333], status 0
    Kernel image @ 0x82000000 [ 0x000000 - 0x34d538 ]
    ## Flattened Device Tree blob at 88000000
       Booting using the fdt blob at 0x88000000
       Loading Ramdisk to 8fff0000, end 8ffffd84 ... OK
       Loading Device Tree to 8ffe2000, end 8ffefddf ... OK
    
    Starting kernel ...
    
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Initializing cgroup subsys cpuset
    [    0.000000] Initializing cgroup subsys cpu
    [    0.000000] Initializing cgroup subsys cpuacct
    [    0.000000] Linux version 4.4.19-gdb0b54cdad (gtbldadm@ubuntu-16) (gcc version 5.3.1 20160113 (Linaro GCC 5.3-2016.02) ) #1 SMP PREEMPT Mon Oct 3 18:31:11 EDT 2016
    [    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c5387d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
    [    0.000000] Machine model: Texas Instruments Keystone 2 Edison EVM
    [    0.000000] Switching physical address space to 0x800000000
    [    0.000000] Reserved memory: OVERLAP DETECTED!
    [    0.000000] mpm_block_mem@820000000 (0x0000000820000000--0x0000000822000000) overlaps with dsp_reserved_mpm_area (0x0000000820000000--0x0000000840000000)
    [    0.000000] Reserved memory: OVERLAP DETECTED!
    [    0.000000] dsp_reserved_mpm_area (0x0000000820000000--0x0000000840000000) overlaps with cmem_block_mem@829000000 (0x0000000822000000--0x0000000840000000)
    [    0.000000] Reserved memory: created CMA memory pool at 0x000000081f800000, size 8 MiB
    [    0.000000] Reserved memory: initialized node dsp_common_cma_pool, compatible id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x0000000820000000, size 512 MiB
    [    0.000000] Reserved memory: initialized node dsp_reserved_mpm_area, compatible id shared-dma-pool
    [    0.000000] cma: Reserved 24 MiB at 0x000000087e400000
    [    0.000000] Forcing write-allocate cache policy for SMP
    [    0.000000] Memory policy: Data cache writealloc
    [    0.000000] psci: probing for conduit method from DT.
    [    0.000000] psci: Using PSCI v0.1 Function IDs from DT
    [    0.000000] PERCPU: Embedded 11 pages/cpu @dd395000 s14784 r8192 d22080 u45056
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 915776
    [    0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=ubifs,2048
    [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    [    0.000000] Memory: 3594344K/3670016K available (6535K kernel code, 252K rwdata, 2320K rodata, 284K init, 296K bss, 42904K reserved, 32768K cma-reserved, 3121152K highmem)
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    [    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
    [    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
    [    0.000000]       .text : 0xc0008000 - 0xc08ae04c   (8857 kB)
    [    0.000000]       .init : 0xc08af000 - 0xc08f6000   ( 284 kB)
    [    0.000000]       .data : 0xc08f6000 - 0xc09352f0   ( 253 kB)
    [    0.000000]        .bss : 0xc0937000 - 0xc09810c4   ( 297 kB)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [    0.000000] Preemptible hierarchical RCU implementation.
    [    0.000000]  Build-time adjustment of leaf fanout to 32.
    [    0.000000]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
    [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=4
    [    0.000000] NR_IRQS:16 nr_irqs:16 16
    [    0.000000] Architected cp15 timer(s) running at 208.33MHz (virt).
    [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x300c4cdf1c, max_idle_ns: 440795202901 ns
    [    0.000003] sched_clock: 56 bits at 208MHz, resolution 4ns, wraps every 4398046511101ns
    [    0.000012] Switching to timer-based delay loop, resolution 4ns
    [    0.000152] keystone timer clock @208333333 Hz
    [    0.000395] Console: colour dummy device 80x30
    [    0.000415] Calibrating delay loop (skipped), value calculated using timer frequency.. 416.66 BogoMIPS (lpj=2083333)
    [    0.000425] pid_max: default: 32768 minimum: 301
    [    0.000508] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.000516] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.000972] Initializing cgroup subsys io
    [    0.000986] Initializing cgroup subsys memory
    [    0.001007] Initializing cgroup subsys devices
    [    0.001018] Initializing cgroup subsys freezer
    [    0.001027] Initializing cgroup subsys perf_event
    [    0.001036] Initializing cgroup subsys pids
    [    0.001059] CPU: Testing write buffer coherency: ok
    [    0.001252] /cpus/cpu@0 missing clock-frequency property
    [    0.001278] /cpus/cpu@1 missing clock-frequency property
    [    0.001304] /cpus/cpu@2 missing clock-frequency property
    [    0.001331] /cpus/cpu@3 missing clock-frequency property
    [    0.001339] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    [    0.001368] Setting up static identity map for 0x800082c0 - 0x800083f0
    [    0.084671] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    [    0.114715] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
    [    0.144759] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
    [    0.144845] Brought up 4 CPUs
    [    0.144861] SMP: Total of 4 processors activated (1666.66 BogoMIPS).
    [    0.144868] CPU: All CPU(s) started in SVC mode.
    [    0.145267] devtmpfs: initialized
    [    0.155566] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
    [    0.155809] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    [    0.156512] pinctrl core: initialized pinctrl subsystem
    [    0.157102] NET: Registered protocol family 16
    [    0.157844] DMA: preallocated 256 KiB pool for atomic coherent allocations
    [    0.180136] cpuidle: using governor ladder
    [    0.210157] cpuidle: using governor menu
    [    0.215788] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.222657] No ATAGs?
    [    0.222679] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
    [    0.222686] hw-breakpoint: maximum watchpoint size is 8 bytes.
    [    0.253949] media: Linux media interface: v0.10
    [    0.253996] Linux video capture interface: v2.00
    [    0.254028] pps_core: LinuxPPS API ver. 1 registered
    [    0.254035] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [    0.254057] PTP clock support registered
    [    0.254098] EDAC MC: Ver: 3.0.0
    [    0.254680] Advanced Linux Sound Architecture Driver Initialized.
    [    0.255329] clocksource: Switched to clocksource arch_sys_counter
    [    0.263087] NET: Registered protocol family 2
    [    0.263555] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.263585] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
    [    0.263638] TCP: Hash tables configured (established 4096 bind 4096)
    [    0.263673] UDP hash table entries: 256 (order: 1, 8192 bytes)
    [    0.263689] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
    [    0.263800] NET: Registered protocol family 1
    [    0.263979] RPC: Registered named UNIX socket transport module.
    [    0.263986] RPC: Registered udp transport module.
    [    0.263992] RPC: Registered tcp transport module.
    [    0.263998] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.264158] Unpacking initramfs...
    [    0.268032] Freeing initrd memory: 64K (cfff0000 - d0000000)
    [    0.268172] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
    [    0.268736] platform alarmtimer: set dma_pfn_offset00780000
    [    0.269131] futex hash table entries: 1024 (order: 4, 65536 bytes)
    [    0.275553] squashfs: version 4.0 (2009/01/31) Phillip Lougher
    [    0.276095] NFS: Registering the id_resolver key type
    [    0.276123] Key type id_resolver registered
    [    0.276129] Key type id_legacy registered
    [    0.276179] ntfs: driver 2.1.32 [Flags: R/O].
    [    0.277260] bounce: pool size: 64 pages
    [    0.277386] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
    [    0.277401] io scheduler noop registered
    [    0.277411] io scheduler deadline registered
    [    0.277440] io scheduler cfq registered (default)
    [    0.277551] keystone_irq soc:keystone_irq@26202a0: irqchip registered, nr_irqs 28
    [    0.277861] ti,keystone-serdes 2326000.phy: init fw ks2_pcie_serdes.bin: version 3.3.0.2c
    [    0.278697] ti,keystone-serdes 232a000.phy: init fw ks2_gbe_serdes.bin: version 3.3.0.2c
    [    0.280841] PCI host bridge /soc/pcie@21020000 ranges:
    [    0.280851]   No bus range found for /soc/pcie@21020000, using [bus 00-ff]
    [    0.280867]   MEM 0x60000000..0x6fffffff -> 0x60000000
    [    0.285220] keystone-pcie 21021000.pcie: PCI host bridge to bus 0000:00
    [    0.285230] pci_bus 0000:00: root bus resource [bus 00-ff]
    [    0.285239] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
    [    0.285569] PCI: bus0: Fast back to back transfers disabled
    [    0.305401] PCI: bus1: Fast back to back transfers disabled
    [    0.305481] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
    [    0.305491] pci 0000:00:00.0: BAR 9: assigned [mem 0x60100000-0x601fffff pref]
    [    0.305500] pci 0000:00:00.0: BAR 7: no space for [io  size 0x1000]
    [    0.305507] pci 0000:00:00.0: BAR 7: failed to assign [io  size 0x1000]
    [    0.305524] pci 0000:01:00.0: BAR 6: assigned [mem 0x60100000-0x6010ffff pref]
    [    0.305533] pci 0000:01:00.0: BAR 5: assigned [mem 0x60000000-0x600001ff]
    [    0.305545] pci 0000:01:00.0: BAR 4: no space for [io  size 0x0010]
    [    0.305552] pci 0000:01:00.0: BAR 4: failed to assign [io  size 0x0010]
    [    0.305560] pci 0000:01:00.0: BAR 0: no space for [io  size 0x0008]
    [    0.305566] pci 0000:01:00.0: BAR 0: failed to assign [io  size 0x0008]
    [    0.305573] pci 0000:01:00.0: BAR 2: no space for [io  size 0x0008]
    [    0.305580] pci 0000:01:00.0: BAR 2: failed to assign [io  size 0x0008]
    [    0.305586] pci 0000:01:00.0: BAR 1: no space for [io  size 0x0004]
    [    0.305593] pci 0000:01:00.0: BAR 1: failed to assign [io  size 0x0004]
    [    0.305599] pci 0000:01:00.0: BAR 3: no space for [io  size 0x0004]
    [    0.305605] pci 0000:01:00.0: BAR 3: failed to assign [io  size 0x0004]
    [    0.305616] pci 0000:00:00.0: PCI bridge to [bus 01]
    [    0.305626] pci 0000:00:00.0:   bridge window [mem 0x60000000-0x600fffff]
    [    0.305635] pci 0000:00:00.0:   bridge window [mem 0x60100000-0x601fffff pref]
    [    0.305822] pcieport 0000:00:00.0: Signaling PME through PCIe PME interrupt
    [    0.305831] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    [    0.306823] keystone-navigator-qmss soc:qmss@2a40000: qmgr start queue 0, number of queues 8192
    [    0.306948] keystone-navigator-qmss soc:qmss@2a40000: added qmgr start queue 0, num of queues 8192, reg_peek f0900000, reg_status f08fc000, reg_config f08fe000, reg_region f0922000, reg_push f0940000, reg_pop f0980000
    [    0.307234] keystone-navigator-qmss soc:qmss@2a40000: firmware file ks2_qmss_pdsp_acc48.bin downloaded for pdsp0
    [    0.307304] keystone-navigator-qmss soc:qmss@2a40000: firmware file ks2_qmss_pdsp_qos.bin downloaded for pdsp3
    [    0.307373] keystone-navigator-qmss soc:qmss@2a40000: firmware file ks2_qmss_pdsp_qos.bin downloaded for pdsp7
    [    0.308366] keystone-navigator-qmss soc:qmss@2a40000: qos: sched port @8096, drop sched @8000
    [    0.309971] keystone-navigator-qmss soc:qmss@2a40000: qos: sched port @6496, drop sched @6400
    [    0.312075] keystone-navigator-qmss soc:qmss@2a40000: qos version 0x200010b, magic valid
    [    0.312612] keystone-navigator-qmss soc:qmss@2a40000: qos version 0x200010b, magic valid
    [    0.313664] keystone-navigator-dma soc:knav_dmas@0: DMA dma_gbe registered 149 logical channels, flows 128, tx chans: 21, rx chans: 91
    [    0.313784] keystone-navigator-dma soc:knav_dmas@0: DMA dma_xgbe registered 48 logical channels, flows 32, tx chans: 16, rx chans: 16
    [    0.361250] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
    [    0.361323] platform serial8250: set dma_pfn_offset00780000
    [    0.363843] console [ttyS0] disabled
    [    0.363888] 2530c00.serial: ttyS0 at MMIO 0x2530c00 (irq = 26, base_baud = 13020833) is a 16550A
    [    1.435142] console [ttyS0] enabled
    [    1.439335] 2531000.serial: ttyS1 at MMIO 0x2531000 (irq = 27, base_baud = 13020833) is a 16550A
    [    1.448632] [drm] Initialized drm 1.1.0 20060810
    [    1.459385] loop: module loaded
    [    1.462788] at24 0-0050: 131072 byte 24c1024 EEPROM, writable, 1 bytes/write
    [    1.471080] spi_davinci 21000400.spi: DMA is not supported (-19)
    [    1.477691] m25p80 spi32766.0: n25q128a11 (16384 Kbytes)
    [    1.483016] 2 ofpart partitions found on MTD device spi32766.0
    [    1.488855] Creating 2 MTD partitions on "spi32766.0":
    [    1.493987] 0x000000000000-0x000000100000 : "u-boot-spl"
    [    1.500140] 0x000000100000-0x000001000000 : "misc"
    [    1.505744] spi_davinci 21000400.spi: Controller at 0xf0a28400
    [    1.511763] spi_davinci 21000600.spi: DMA is not supported (-19)
    [    1.518107] spi_davinci 21000600.spi: Controller at 0xf0a2a600
    [    1.524116] spi_davinci 21000800.spi: DMA is not supported (-19)
    [    1.530453] spi_davinci 21000800.spi: Controller at 0xf0a2c800
    [    1.536868] platform Fixed MDIO bus.0: set dma_pfn_offset00780000
    [    1.543077] libphy: Fixed MDIO Bus: probed
    [    1.595352] davinci_mdio 24200f00.mdio: davinci mdio revision 1.7
    [    1.601438] libphy: 24200f00.mdio: probed
    [    1.606191] davinci_mdio 24200f00.mdio: phy[0]: device 24200f00.mdio:00, driver Marvell 88E1510
    [    1.614882] davinci_mdio 24200f00.mdio: phy[1]: device 24200f00.mdio:01, driver Marvell 88E1510
    [    1.624127] ti,keystone-serdes 232a000.phy: Requested PHY is disabled
    [    3.643169] serdes PLL not locked
    [    4.158567] ti,keystone-serdes 232a000.phy: Requested PHY is disabled
    [    6.177891] serdes PLL not locked
    [    8.749830] netcp-1.0 2620110.netcp: initialized cpsw ale version 1.4
    [    8.756284] netcp-1.0 2620110.netcp: ALE Table size 8192
    [    8.763257] netcp-1.0 2620110.netcp: module(netcp-xgbe) not used for device
    [    8.770245] netcp-1.0 2620110.netcp: module(netcp-pa) not used for device
    [    8.777079] netcp-1.0 2620110.netcp: No ip-lut-ranges array in dt bindings for PA
    [    8.786361] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 0
    [    8.794618] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 1
    [    8.802917] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 2
    [    8.811195] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 3
    [    8.819480] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 4
    [    8.827753] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 5
    [    8.836061] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 6
    [    8.844315] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 7
    [    8.852588] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 8
    [    8.860853] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 9
    [    8.869121] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 10
    [    8.877474] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 11
    [    8.885828] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 12
    [    8.894170] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 13
    [    8.902523] netcp-1.0 2620110.netcp: Using PA fw version 03.00.02.00:0x03000200 for pdsp 14
    [    8.911287] netcp-1.0 2620110.netcp: rx_chan_name netrx0-pa for port 1
    [    8.917837] netcp-1.0 2620110.netcp: rx_chan_name netrx1-pa for port 2
    [    8.925102] 2620738.usb_phy supply vcc not found, using dummy regulator
    [    8.931902] 2620750.usb_phy supply vcc not found, using dummy regulator
    [    8.938907] mousedev: PS/2 mouse device common for all mice
    [    8.944843] i2c /dev entries driver
    [    8.950127] ledtrig-cpu: registered to indicate activity on CPUs
    [    8.957750] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xac
    [    8.964096] nand: Micron MT29F4G08ABBDAH4
    [    8.968113] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
    [    8.975974] Bad block table found at page 262080, version 0x01
    [    8.982306] Bad block table found at page 262016, version 0x01
    [    8.988462] 3 ofpart partitions found on MTD device 30000000.nand
    [    8.994545] Creating 3 MTD partitions on "30000000.nand":
    [    8.999950] 0x000000000000-0x000000100000 : "u-boot"
    [    9.005748] 0x000000100000-0x000000180000 : "params"
    [    9.011489] 0x000000180000-0x000020000000 : "ubifs"
    [    9.017524] davinci_nand 30000000.nand: controller rev. 2.5
    [    9.023474] platform snd-soc-dummy: set dma_pfn_offset00780000
    [    9.030533] NET: Registered protocol family 10
    [    9.035697] sit: IPv6 over IPv4 tunneling driver
    [    9.040761] NET: Registered protocol family 17
    [    9.045400] Key type dns_resolver registered
    [    9.049743] Registering SWP/SWPB emulation handler
    [    9.055932] ubi0: attaching mtd4
    [   11.152414] ubi0: scanning is finished
    [   11.166345] ubi0: attached mtd4 (name "ubifs", size 510 MiB)
    [   11.171998] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    [   11.178876] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    [   11.185667] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
    [   11.192620] ubi0: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0
    [   11.198715] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
    [   11.205938] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1710674976
    [   11.215060] ubi0: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB handling: 76
    [   11.224383] ubi0: background thread "ubi_bgt0d" started, PID 72
    [   11.224537] hctosys: unable to open rtc device (rtc0)
    [   11.237201] ALSA device list:
    [   11.240163]   No soundcards found.
    [   11.244169] UBIFS: parse sync
    [   11.248966] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 73
    [   11.282237] UBIFS (ubi0:0): start fixing up free space
    [   33.181943] UBIFS (ubi0:0): free space fixup complete
    [   33.205126] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
    [   33.212530] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
    [   33.222446] UBIFS (ubi0:0): FS size: 488222720 bytes (465 MiB, 3845 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
    [   33.233141] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
    [   33.238979] UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 02D63BE4-8E77-4DC6-AEE2-4121E543AF4F, small LPT model
    [   33.252123] VFS: Mounted root (ubifs filesystem) on device 0:14.
    [   33.259850] devtmpfs: mounted
    [   33.262956] Freeing unused kernel memory: 284K (c08af000 - c08f6000)
    [   33.269315] This architecture does not have kernel memory protection.
    [   33.472691] systemd[1]: System time before build time, advancing clock.
    [   33.528991] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.556725] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.568066] systemd[1]: systemd 229 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
    [   33.586961] systemd[1]: Detected architecture arm.
    
    Welcome to Arago 2016.08!
    
    [   33.616819] systemd[1]: Set hostname to <k2e-evm>.
    [   33.626517] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.636233] systemd[1]: Initializing machine ID from random generator.
    [   33.778525] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.807555] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.833139] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.904892] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.969125] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.978511] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   33.988089] random: systemd: uninitialized urandom read (16 bytes read, 0 bits of entropy available)
    [   34.131358] systemd[1]: [/lib/systemd/system/syslog-ng.service:6] Executable path is not absolute, ignoring: @SBINDIR@/syslog-ng -F -p @LOCALSTATEDIR@/run/syslogd.pid
    [   34.146256] systemd[1]: [/lib/systemd/system/syslog-ng.service:7] Executable path is not absolute, ignoring: @BASEBINDIR@/kill -HUP $MAINPID
    [   34.159126] systemd[1]: syslog-ng.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
    [   34.259753] systemd[1]: syslog-ng.service: Cannot add dependency job, ignoring: Unit syslog-ng.service is not loaded properly: Invalid argument.
    [   34.278631] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [  OK  ] Started Forward Password Requests to Wall Directory Watch.
    [   34.308305] systemd[1]: Listening on Journal Socket (/dev/log).
    [  OK  ] Listening on Journal Socket (/dev/log).
    [   34.335483] systemd[1]: Listening on udev Kernel Socket.
    [  OK  ] Listening on udev Kernel Socket.
    [   34.355513] systemd[1]: Listening on udev Control Socket.
    [  OK  ] Listening on udev Control Socket.
    [   34.387766] systemd[1]: Created slice System Slice.
    [  OK  ] Created slice System Slice.
    [   34.415991] systemd[1]: Created slice User and Session Slice.
    [  OK  ] Created slice User and Session Slice.
    [   34.445471] systemd[1]: Reached target Remote File Systems.
    [  OK  ] Reached target Remote File Systems.
    [   34.476192] systemd[1]: Listening on Network Service Netlink Socket.
    [  OK  ] Listening on Network Service Netlink Socket.
    [   34.505447] systemd[1]: Reached target Slices.
    [  OK  ] Reached target Slices.
    [   34.525540] systemd[1]: Listening on Journal Socket.
    [  OK  ] Listening on Journal Socket.
    [   34.585718] systemd[1]: Starting Setup Virtual Console...
             Starting Setup Virtual Console...
    [   34.621001] systemd[1]: Mounting Temporary Directory...
             Mounting Temporary Directory...
    [   34.647465] systemd[1]: Mounting Debug File System...
             Mounting Debug File System...
    [   34.677975] systemd[1]: Starting Create list of required static device nodes for the current kernel...
             Starting Create list of required st... nodes for the current kernel...
    [   34.705428] systemd[1]: syslog.socket: Socket service syslog-ng.service not loaded, refusing.
    [   34.713963] systemd[1]: Failed to listen on Syslog Socket.
    [FAILED] Failed to listen on Syslog Socket.
    See 'systemctl status syslog.socket' for details.
    [   34.756060] systemd[1]: Created slice system-serial\x2dgetty.slice.
    [  OK  ] Created slice system-serial\x2dgetty.slice.
    [   34.825585] systemd[1]: Mounting POSIX Message Queue File System...
             Mounting POSIX Message Queue File System...
    [   34.870219] systemd[1]: Starting Journal Service...
             Starting Journal Service...
    [   34.911218] systemd[1]: Starting Load Kernel Modules...
             Starting Load Kernel Modules...
    [   34.939917] systemd[1]: Starting Remount Root and Kernel File Systems...
    [   34.943756] CMEMK module: reference Linux version 4.4.19
    [   34.944480] allocated heap buffer 0xc080000 of size 0xc0000
    [   34.944627] cmemk initialized
             Starting Remount Root and Kernel File Systems...
    [   34.972608] cryptodev: driver 1.8 loaded.
    [   34.985652] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
    [   35.015655] systemd[1]: Reached target Swap.
    [  OK  ] Reached target Swap.
    [   35.032657] NET: Registered protocol family 41
    [   35.043882] uio_module_drv soc:mpax: registered misc device mpax
    [   35.050167] uio_module_drv soc:edma3: registered misc device edma3
    [   35.050753] systemd[1]: Created slice system-getty.slice.
    [   35.062372] uio_module_drv soc:secmgr: registered misc device secmgr
    [  OK     35.069283] uio_module_drv soc:qmss: registered misc device qmss
    m] Created slice system-getty.slice.
    [   35.083053] uio_module_drv soc:hyperlink0: registered misc device hyperlink0
    [   35.090566] uio_module_drv soc:srss: registered misc device srss
    [   35.105656] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    [  OK  ] Started Dispatch Password Requests to Console Directory Watch.
    [   35.135464] systemd[1]: Reached target Paths.
    [  OK  ] Reached target Paths.
    [   35.189136] systemd[1]: Mounted Debug File System.
    [  OK  ] Mounted Debug File System.
    [   35.215546] systemd[1]: Mounted POSIX Message Queue File System.
    [  OK  ] Mounted POSIX Message Queue File System.
    [   35.245481] systemd[1]: Mounted Temporary Directory.
    [  OK  ] Mounted Temporary Directory.
    [   35.265658] systemd[1]: Started Journal Service.
    [  OK  ] Started Journal Service.
    [  OK  ] Started Setup Virtual Console.
    [  OK  ] Started Create list of required sta...ce nodes for the current kernel.
    [  OK  ] Started Load Kernel Modules.
    [  OK  ] Started Remount Root and Kernel File Systems.
             Starting Rebuild Dynamic Linker Cache...
             Starting Rebuild Hardware Database...
             Starting Apply Kernel Variables...
             Starting Create Static Device Nodes in /dev...
             Starting Flush Journal to Persistent Storage...
    [  OK  ] Started Apply Kernel Variables.
    [   35.936652] systemd-journald[110]: Received request to flush runtime journal from PID 1
    [  OK  ] Started Flush Journal to Persistent Storage.
    [  OK  ] Started Create Static Device Nodes in /dev.
             Starting udev Kernel Device Manager...
    [  OK  ] Reached target Local File Systems (Pre).
             Mounting /var/volatile...
             Mounting /media/ram...
    [  OK  ] Mounted /var/volatile.
    [  OK  ] Mounted /media/ram.
             Starting Load/Save Random Seed...
    [  OK  ] Reached target Local File Systems.
             Starting Create Volatile Files and Directories...
             Starting Rebuild Journal Catalog...
    [  OK  ] Started Load/Save Random Seed.
    [  OK  ] Started Create Volatile Files and Directories.
    [  OK  ] Started udev Kernel Device Manager.
    [  OK  ] Started Rebuild Journal Catalog.
             Starting Opkg first boot configure...
             Starting Network Time Synchronization...
             Starting Update UTMP about System Boot/Shutdown...
    [  OK  ] Started Network Time Synchronization.
    [  OK  ] Started Update UTMP about System Boot/Shutdown.
    [  OK  ] Reached target System Time Synchronized.
             Starting Synchronize System and HW clocks...
    [FAILED] Failed to start Synchronize System and HW clocks.
    See 'systemctl status sync-clocks.service' for details.
    [  OK  ] Started Rebuild Dynamic Linker Cache.
    [  OK  ] Started Opkg first boot configure.
    [  OK  ] Started Rebuild Hardware Database.
             Starting Update is Completed...
             Starting udev Coldplug all Devices...
    [  OK  ] Started Update is Completed.
    [  OK  ] Started udev Coldplug all Devices.
    [   38.628977] keystone-rproc 10800000.dsp0: assigned reserved memory node dsp_common_cma_pool
    [   38.646805]  remoteproc0: 10800000.dsp0 is available
    [   38.654242]  remoteproc0: Note: remoteproc is still under development and considered experimental.
    [  OK  ] Reached target System Initialization.
    [   38.686725]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [   38.707103] davinci-wdt 22f0080.wdt: heartbeat 60 sec
    [  OK  ] Listening on D-Bus System Message Bus Socket.
    [   38.740033] keystone-dsp-mem c000000.dspmem: registered misc device dspmem
    [  OK  ] Listening on dropbear.socket.
    [  OK  ] Listening on RPCbind Server Activation Socket.
    [   38.828413] SCSI subsystem initialized
    [  OK  ] Reached target Sockets.
    [  OK  ] Reached target Basic System.
             Starting Print notice about GPLv3 packages...
    [  OK  ] Started D-Bus System Message Bus.
    [   38.969597] ahci 0000:01:00.0: limiting MRRS to 256
    [   38.984674] keystone-crypto soc:subsys@24080000:crypto@0: crypto accelerator enabled
    [   38.993390] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
    [   39.045476] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
    [   39.059000] scsi host0: ahci
    [   39.118353] scsi host1: ahci
    [   39.121942] ata1: SATA max UDMA/133 abar m512@0x60000000 port 0x60000100 irq 114
    [   39.129485] ata2: SATA max UDMA/133 abar m512@0x60000000 port 0x60000180 irq 114
    [   39.485463] ata1: SATA link down (SStatus 0 SControl 300)
    [   39.490928] ata2: SATA link down (SStatus 0 SControl 300)
             Starting Network Service...
             Starting Permit User Sessions...
             Starting Login Service...
    [  OK  ] Started System Logging Service.
             Starting run_srss_tc.service...
    [  OK  ] Started Kernel Logging Service.
             Starting TI Multiproc Manager...
             Starting tiipclad-daemon.service...
    [  OK  ] Started Daily Cleanup of Temporary Directories.
    [  OK  ] Reached target Timers.
    [  OK  ] Started strongSwan IPsec IKEv1/IKEv2 daemon using ipsec.conf.
             Starting Ethernet Bridge Filtering Tables...
             Starting telnetd.service...
             Starting softhsm-daemon.service...
    [  OK  ] Started Permit User Sessions.
    [  OK  ] Found device /dev/ttyS0.
    [  OK  ] Started run_srss_tc.service.
    [  OK  ] Started Ethernet Bridge Filtering Tables.
    [  OK  ] Started telnetd.service.
    [  OK  ] Started tiipclad-daemon.service.
    [   40.426331] platform xhci-hcd.0.auto: set dma_pfn_offset00780000
    [  OK  ] Started Network Service.
    [  OK  ] Started TI Multiproc Manager.
    [   40.653781] netcp-1.0 2620110.netcp eth1: Link is Up - 1Gbps/Full - flow control off
    [   40.662536] pps pps0: new PPS source ptp0
    [   40.670931] cpts rftclk: sel(0),rate(625000000 HZ),mult(4096),shift(9),div(5)
    [   40.710653] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [   40.851708] usbcore: registered new interface driver usbfs
    [   40.859271] uio_module_drv soc:secmgr: request address 0x0 is not in the allowed ranges
    [   40.875518] usbcore: registered new interface driver hub
    [   40.881068] usbcore: registered new device driver usb
    [   40.893334] NET: Registered protocol family 15
    [  OK  ] Started softhsm-daemon.service.
    [   40.960344] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    [   40.965963] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
    [   40.969274] IPsec: esp4_init: can't add xfrm type
    [   40.983233] xhci-hcd xhci-hcd.0.auto: hcc params 0x0298f06d hci version 0x100 quirks 0x00010010
    [   40.992044] xhci-hcd xhci-hcd.0.auto: irq 34, io mem 0x02690000
    [   40.999474] hub 1-0:1.0: USB hub found
    [   41.003249] hub 1-0:1.0: 1 port detected
    [   41.007922] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    [   41.013410] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
    [   41.021334] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
    [   41.030865] hub 2-0:1.0: USB hub found
    [   41.034655] hub 2-0:1.0: 1 port detected
    [   41.144297] Initializing XFRM netlink socket
    [   41.284852] netcp-1.0 2620110.netcp eth0: Link is Down
    [   41.305579] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   41.755349] netcp-1.0 2620110.netcp eth1: Link is Up - 1Gbps/Full - flow control off
    [  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
    [  OK  ] Reached target Network.
             Starting Lightning Fast Webserver With Light System Requirements...
    [  OK  ] Started Vsftpd ftp daemon.
             Starting Network Name Resolution...
             Starting thttpd.service...
    [  OK  ] Started Serial Getty on ttyS0.
    [  OK  ] Started Getty on tty1.
    [  OK  ] Started Login Service.
    [  OK  ] Started Lightning Fast Webserver With Light System Requirements.
    [  OK  ] Started thttpd.service.
             Starting rng-tools.service...
    [  OK  ] Started rng-tools.service.
             Starting gdbserverproxy.service...
    [  OK  ] Started gdbserverproxy.service.
    ***************************************************************
    ***************************************************************
    NOTICE: This file system contains the following GPLv3 packages:
             Starting matrix-gui-2.0.service...
            autoconf
            binutils
            cpp-symlinks
            cpp
            dosfstools
            g++-symlinks
            g++
            gawk
            gcc-symlinks
            gcc
            gdb
            gdbc6x
            gdbserver
            libgmp10
            libmpc3
            libmpfr4
            make
    
    [  OK  ] Started matrix-gui-2.0.service.
    If you do not wish to distribute GPLv3 components please remove
    the above packages prior to distribution.  This can be done using
    the opkg remove command.  i.e.:
        opkg remove <package>
    Where <package> is the name printed in the list above
    
    NOTE: If the package is a dependency of another package you
          will be notified of the dependent packages.  You should
          use the --force-removal-of-dependent-packages option to
          also remove the dependent packages as well
    ***************************************************************
    ***************************************************************
             Starting parse-ip.service...
             Starting thermal-zone-init.service...
    [  OK  ] Started Network Name Resolution.
    [  OK  ] Started Print notice about GPLv3 packages.
    [  OK  ] Started thermal-zone-init.service.
    
    
    #>>>>> LCD 12
    IP Address:
    
    [   44.645720] netcp-1.0 2620110.netcp eth1: Link is Up - 1Gbps/Full - flow control off
    [   44.653474] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    [  OK  ] Started parse-ip.service.
             Starting Hostname Service...
    [  OK  ] Started Hostname Service.
    
     _____                    _____           _         _
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|
    
    Arago Project http://arago-project.org k2e-evm ttyS0
    
    Arago 2016.08 k2e-evm ttyS0
    
    k2e-evm login:

  • Hello Rex,

    > You mentioned "the u-boot also loads the firmware image "k2-fw-initrd.cpio.gz" without errors".

    > I am not sure what this means. My impression is that u-boot does not load the firmware.

    This is just one of my numerous attempts to include the firmware within the boot procedure. I found this method from one of the posts I have read so far. Also some user guides suggest using this approach (see chapter U-Boot):

    processors.wiki.ti.com/.../MCSDK_to_Processor_SDK_Migration

    Setting the environment variables for firmware in U-boot is described in the chapter "U-Boot environment/scripts" of:

    processors.wiki.ti.com/.../Linux_Core_PCIE_User's_Guide

    I am sure you can understand that I am confused. One guide says this and other guide says that, but none of the tricks has worked so far.

    But since only the "rootfs" is going to be used, I will not load the firmware by the u-boot anymore. I let the kernel boot to do that as you suggest.

    So, I removed the "boot" volume, and put the firmware cpio..gz into the "rootfs" /boot. Also the skern, kernel and dtb are no in "rootfs" /boot, like you say:

    > That is not the way I understand how it should be. I think the ubi has only one partition, rootfs.

    > The kernel, dtb, skern, and k2-fw-initrd.cpio.gz should be in rootfs:/boot directory.

    > From the ubi image on the nand, it only shows one partition.

    Actually I let the "boot" be there, but only switch the boot volume be "rootfs". I will finally remove the "boot" from the UBI when the booting works from "rootfs".


    > Please send me your u-boot version.and the output from printenv.

    > I asuume your kernel and filesytem are from the same release package.

    See my environment variables below. But now you mention the "same release", I just realized that  I took my rootfs file system from the MCSDK "tisdk-rootfs-k2l-evm.tar.gz", but the kernel image is built from the Processor SDK sources (kernel 4.4.19). Can this make some conflict? Yesterday the board booted once to the login, but only once. Nevertheless, I probably need to use the "tisdk-server-rootfs-image-k2l-evm.tar.xz", check that the firmware is in /boot, ubinize it, burn it to NAND, reset the board and, with a bit of luck, be happy, right?

    U-Boot SPL 2013.01-00003-g9ee5306-dirty (Nov 29 2016 - 11:48:11)
    SF: Detected N25Q128A with page size 64 KiB, total 16 MiB

    U-Boot 2013.01-00003-g9ee5306-dirty (Nov 29 2016 - 11:48:11)

    I2C:   ready
    DRAM: 2 GiB

    Reseting entire DDR3 memory to 0 ...
    DRAM:  2 GiB
    NAND:  512 MiB
    Hit any key to stop autoboot:  0
    K2L EVM #
    K2L EVM #
    K2L EVM # printenv
    addr_fdt=0x87000000
    addr_fs=0x82000000
    addr_kern=0x88000000
    addr_mon=0x0c140000
    addr_secdb_key=0xc000000
    addr_ubi=0x82000000
    addr_uboot=0x87000000
    addr_uinitrd=-
    args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1 earlyprintk
    args_net=setenv bootargs ${bootargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${s
    erverip}:${nfs_root},${nfs_options} ip=dhcp
    args_ramfs=setenv bootargs ${bootargs} earlyprintkrdinit=/sbin/init rw root=/dev
    /ram0 initrd=0x802000000,38M
    args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags
    =sync rw ubi.mtd=ubifs,2048
    args_uinitrd=setenv bootargs ${bootargs} earlyprintk rdinit=/sbin/init rw
    baudrate=115200
    boot=ubi
    bootargs=console=ttyS0,115200n8 rootwait=1 earlyprintk rootfstype=ubifs root=ubi
    0:rootfs rootflags=sync rw ubi.mtd=ubifs,2048
    bootcmd=run init_${boot} init_fw_rd_${boot} get_fdt_${boot} get_mon_${boot} get_
    kern_${boot} run_mon run_kern
    bootdelay=3
    bootfile=uImage
    burn_ubi=nand erase.part ubifs; nand write ${addr_ubi} ubifs ${filesize}
    burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}
    debug_options=1
    ethact=K2L_EMAC0
    fdt_high=0xffffffff
    filesize=0xAFA0000
    get_fdt_net=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}
    get_fdt_ramfs=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}
    get_fdt_ubi=ubifsload ${addr_fdt} ${name_fdt}
    get_fdt_uinitrd=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}
    get_fs_ramfs=dhcp ${addr_fs} ${tftp_root}/${name_fs}
    get_fs_uinitrd=dhcp ${addr_fs} ${tftp_root}/${name_uinitrd}
    get_kern_net=dhcp ${addr_kern} ${tftp_root}/${name_kern}
    get_kern_ramfs=dhcp ${addr_kern} ${tftp_root}/${name_kern}
    get_kern_ubi=ubifsload ${addr_kern} ${name_kern}
    get_kern_uinitrd=dhcp ${addr_kern} ${tftp_root}/${name_kern}
    get_mon_net=dhcp ${addr_mon} ${tftp_root}/${name_mon}
    get_mon_ramfs=dhcp ${addr_mon} ${tftp_root}/${name_mon}
    get_mon_ubi=ubifsload ${addr_mon} ${name_mon}
    get_mon_uinitrd=dhcp ${addr_mon} ${tftp_root}/${name_mon}
    get_tftp_ubi=dhcp ${addr_fs} ${tftp_root}/${name_ubi}
    get_ubi_net=dhcp ${addr_ubi} ${tftp_root}/${name_ubi}
    get_uboot_net=dhcp ${addr_uboot} ${tftp_root}/${name_uboot}
    has_mdio=0
    init_fw_rd_net=dhcp ${rdaddr} ${tftp_root}/${name_fw_rd}; run set_rd_spec
    init_fw_rd_ramfs=setenv rd_spec -
    init_fw_rd_ubi=ubifsload ${rdaddr} ${name_fw_rd}; run set_rd_spec
    init_net=run set_fs_none args_all args_net
    init_ramfs=run set_fs_none args_all args_ramfs get_fs_ramfs
    init_ubi=run set_fs_none args_all args_ubi; ubi part ubifs; ubifsmount rootfs
    init_uinitrd=run set_fs_uinitrd args_all args_uinitrd get_fs_uinitrd
    initrd_high=0xffffffff
    ldaddr=0x98000000
    mem_lpae=1
    mem_reserve=512M
    mtddevname=bootloader
    mtddevnum=0
    mtdids=nand0=davinci_nand.0
    mtdparts=mtdparts=davinci_nand.0:1024k(bootloader)ro,512k(params)ro,522752k(ubif
    s)
    name_fdt=/boot/keystone-k2l-sri.dtb
    name_fs=tisdk-rootfs.cpio.gz
    name_fw_rd=/boot/k2-fw-initrd.cpio.gz
    name_kern=/boot/uImage-keystone-sri.bin
    name_mon=/boot/skern-keystone-sri.bin
    name_ubi=k2l-evm-ubifs.ubi
    name_uboot=u-boot-spi.gph
    name_uinitrd=uinitrd.bin
    nfs_options=v3,tcp,rsize=4096,wsize=4096
    nfs_root=/export
    no_post=1
    partition=nand0,0
    rdaddr=0x0c000000
    root=/dev/ram0
    run_kern=bootm ${addr_kern} ${rd_spec} ${addr_fdt}
    run_mon=mon_install ${addr_mon}
    serverip=157.87.43.15
    set_fs_none=setenv addr_uinitrd -
    set_fs_uinitrd=setenv addr_uinitrd ${addr_fs}
    set_rd_spec=setenv rd_spec ${rdaddr}:${filesize}
    setenv=bootargs console=ttyS0,115200n8 rootwait=1 rootfstype=ubifs root=ubi0:roo
    tfs rootflags=sync rw ubi.mtd=2,2048 earlyprintk rdinit=/sbin/init rw root=/dev/
    ram0
    size_ubi=0xCD6000
    stderr=serial
    stdin=serial
    stdout=serial
    tftp_root=/
    uinitrd_fixup=1
    ver=U-Boot 2013.01-00003-g9ee5306-dirty (Nov 29 2016 - 11:48:11)

    Environment size: 3847/262140 bytes
    K2L EVM #

    > Are you trying the images on TI EVM?

    I have a K2H EVM with different network chip, so I cannot boot it successfully with this image either. It also panics at the same spot. So, could it be that the MCSDK rootfs and Processor SDK kernel are incompatible because both boards produce kernel panic. I really should give a try for a properly made UBI fs image (everything from the same release package), like I described above.

    > Copying images to NAND, I don't believe the power for NetCP matters.

    No, I don't have issues with NAND. I meant PSC of the NetCP might affect to the kernel panic at the certain point every boot. But of course, there can be also other reasons, like incompatible sw packages. The latter sounds now more probable since the K2H EVM also panics with this UBI image although that board has no issues with the NetCP PSC.

    > I suggested you use TI EVM, and boot with prebuilt images.

    > Once it works for you, then copy the what you learn from EVM and apply them to custom board.

    I would if I could. I only have K2H EVM. In our custom K2L board we have different DDR3 settings and different ethernet chip, so that I cannot use any prebuilt images for the K2L EVM. But I guess, a prebuilt image should still boot up to login prompt without kernel panic and without a working network.

    I attach here my u-boot.bin. I just drag'n'dropped it from Explorer. I hope this works that way easily. But I just wonder if it is for any use for you because of the different DDR3 timings etc custom modifications necessary to run it in our board.

    I try it once more with a proper UBI fs image and let you know what happens.

    Best regards,

    Ari

    u-boot_nandEnv.zip

  • Hello Rex,

    I did a new UBI fs from the "tisdk-server-rootfs-image-k2l-evm.tar.xz" of the Processor SDK package. Now the kernel and the file system are 100% sure from the same package. But again the firmware loading fails and the kernel panics. The "rootfs" volume looks now like this:

    K2L EVM # ubifsmount rootfs
    UBIFS: mounted UBI device 0, volume 1, name "rootfs"
    UBIFS: mounted read-only
    UBIFS: file system size:   490000384 bytes (478516 KiB, 467 MiB, 3859 LEBs)
    UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
    UBIFS: media format:       w4/r0 (latest is w4/r0)
    UBIFS: default compressor: LZO
    UBIFS: reserved for root:  0 bytes (0 KiB)
    K2L EVM # ubifsls
    <DIR>        6352  Tue Oct 04 03:11:06 2016  bin
    <DIR>         160  Mon Oct 03 22:24:03 2016  dev
    <DIR>        7408  Tue Oct 04 03:11:46 2016  etc
    <DIR>        9736  Mon Oct 03 23:45:10 2016  lib
    <DIR>         304  Tue Oct 04 03:09:26 2016  mnt
    <DIR>         224  Tue Oct 04 00:12:55 2016  opt
    <DIR>         160  Tue Oct 04 03:11:26 2016  run
    <DIR>         224  Mon Oct 03 23:39:54 2016  srv
    <DIR>         160  Mon Oct 03 22:24:03 2016  tmp
    <DIR>         160  Mon Oct 03 22:24:03 2016  sys
    <DIR>         808  Mon Oct 03 23:59:55 2016  var
    <DIR>         752  Mon Oct 03 23:45:10 2016  usr
    <DIR>         352  Tue Oct 04 00:02:25 2016  www
    <DIR>         968  Tue Dec 13 10:07:58 2016  boot
    <DIR>         224  Mon Oct 03 22:24:04 2016  home
    <LNK>          20  Mon Oct 03 23:43:20 2016  init
    <DIR>         160  Mon Oct 03 22:24:03 2016  proc
    <DIR>        7976  Tue Oct 04 03:11:15 2016  sbin
    <DIR>         224  Mon Oct 03 22:25:32 2016  include
    <DIR>         160  Mon Oct 03 22:24:03 2016  media
    K2L EVM # ubifsls boot
             13325820  Mon Oct 03 23:49:09 2016  vmlinux-4.4.19-gdb0b54cdad
              4348536  Tue Nov 29 11:14:33 2016  uImage-keystone-sri.bin
                44991  Mon Oct 03 23:49:09 2016  devicetree-zImage-keystone-k2l-evm.
    dtb
                45056  Mon Oct 03 22:57:21 2016  skern-k2l.bin
                44696  Tue Nov 29 14:20:40 2016  keystone-k2l-sri.dtb
    <LNK>          38  Tue Oct 04 03:11:26 2016  keystone-k2l-evm.dtb
              3462440  Mon Oct 03 23:49:08 2016  zImage-4.4.19-gdb0b54cdad
                45056  Fri Nov 04 10:11:41 2016  skern-keystone-sri.bin
    <LNK>          25  Tue Oct 04 03:11:26 2016  zImage
                64895  Tue Oct 04 00:30:00 2016  k2-fw-initrd.cpio.gz
    K2L EVM #

    I also noticed from your boot log that you load the firmware already in the u-boot although I understood that it must not be done until in the kernel boot. I had used another address for loading the firmware from NAND. If I used the same address ('rdaddr' = 0x8808 0000) as you, and about all the user guides I have read, I get an error:

    [    0.000000] INITRD: 0x788080000+0x0000fd7f is not a memory region - disabling  initrd

    Why is this?

    I use also different load addresses for the device tree and the kernel image, but I suppose it makes no difference. What you think?

    Your My
    dtb 0x88000000 0x87000000
    skern 0x0c140000 0x0c140000
    kernel 0x82000000 0x88000000
    fw 0x88080000 0x88080000

    How can you use the 0x82000000 for kernel? I have thought the UBI uses that area. Or is it so that the UBI file system is never loaded into RAM at all but instead kept in the NAND and read/written directly from/to there?

    In addition to these there is this error in your boot log:

    [    0.000000] Reserved memory: OVERLAP DETECTED!
    [    0.000000] mpm_block_mem@820000000 (0x0000000820000000--0x0000000822000000) overlaps with dsp_reserved_mpm_area (0x0000000820000000--0x0000000840000000)
    [    0.000000] Reserved memory: OVERLAP DETECTED!
    [    0.000000] dsp_reserved_mpm_area (0x0000000820000000--0x0000000840000000) overlaps with cmem_block_mem@829000000 (0x0000000822000000--0x0000000840000000)

    This is not happening with my device tree any more since I have modified it like it is done in the K2H EVM board. I don't know whether it affects to the file system some how. Should I move back using the K2L device tree although it  produces the error like above? I have understood from forum posts that this is not a fatal error, but because my kernel panics, I wanted to eliminate all possible errors.

    Here is the complete boot log from the newest UBI fs and environment variables:

    K2L EVM # boot
    Unmounting UBIFS volume rootfs!
    UBI: mtd1 is detached from ubi0
    Creating 1 MTD partitions on "nand0":
    0x000000180000-0x000020000000 : "mtd=2"
    UBI: attaching mtd1 to ubi0
    UBI: physical eraseblock size:   131072 bytes (128 KiB)
    UBI: logical eraseblock size:    126976 bytes
    UBI: smallest flash I/O unit:    2048
    UBI: VID header offset:          2048 (aligned 2048)
    UBI: data offset:                4096
    UBI: attached mtd1 to ubi0
    UBI: MTD device name:            "mtd=2"
    UBI: MTD device size:            510 MiB
    UBI: number of good PEBs:        4080
    UBI: number of bad PEBs:         4
    UBI: max. allowed volumes:       128
    UBI: wear-leveling threshold:    4096
    UBI: number of internal volumes: 1
    UBI: number of user volumes:     2
    UBI: available PEBs:             0
    UBI: total number of reserved PEBs: 4080
    UBI: number of PEBs reserved for bad PEB handling: 40
    UBI: max/mean erase counter: 1/0
    UBIFS: mounted UBI device 0, volume 1, name "rootfs"
    UBIFS: mounted read-only
    UBIFS: file system size:   490000384 bytes (478516 KiB, 467 MiB, 3859 LEBs)
    UBIFS: journal size:       9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
    UBIFS: media format:       w4/r0 (latest is w4/r0)
    UBIFS: default compressor: LZO
    UBIFS: reserved for root:  0 bytes (0 KiB)
    Loading file '/boot/k2-fw-initrd.cpio.gz' to addr 0x88080000 with size 64895 (0x0000fd7f)...
    Done
    Loading file '/boot/keystone-k2l-sri.dtb' to addr 0x87000000 with size 44696 (0x0000ae98)...
    Done
    Loading file '/boot/skern-keystone-sri.bin' to addr 0x0c140000 with size 45056 (0x0000b000)...
    Done
    Loading file '/boot/uImage-keystone-sri.bin' to addr 0x88000000 with size 4348536 (0x00425a78)...
    Done
    ## installed monitor, freq [199680000], status 0
    ## Booting kernel from Legacy Image at 88000000 ...
       Image Name:
       Created:      2016-11-29  11:14:33 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    4348472 Bytes = 4.1 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 87000000
       Booting using the fdt blob at 0x87000000
       Loading Kernel Image ... OK
    OK
       Using Device Tree in place at 87000000, end 8700de97

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Initializing cgroup subsys cpu
    [    0.000000] Initializing cgroup subsys cpuacct
    [    0.000000] Linux version 4.4.19-gdb0b54cdad (neukkari@xskybex-laptop) (gcc v
    ersion 4.7.3 20130205 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.02-01-20
    130221 - Linaro GCC 2013.02) ) #9 SMP PREEMPT Tue Nov 29 13:07:27 EET 2016
    [    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c5387d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
    [    0.000000] Machine model: Texas Instruments Keystone 2 Lamarr EVM
    [    0.000000] bootconsole [earlycon0] enabled
    [    0.000000] Switching physical address space to 0x800000000
    [    0.000000] INITRD: 0x788080000+0x0000fd7f is not a memory region - disabling initrd
    [    0.000000] Reserved memory: created CMA memory pool at 0x000000081f800000, size 8 MiB
    [    0.000000] Reserved memory: initialized node dsp_common_cma_pool, compatible
     id shared-dma-pool
    [    0.000000] Reserved memory: created DMA memory pool at 0x0000000820000000, size 512 MiB
    [    0.000000] Reserved memory: initialized node dsp_reserved_mpm_area, compatible id shared-dma-pool
    [    0.000000] cma: Reserved 16 MiB at 0x000000085f000000
    [    0.000000] Forcing write-allocate cache policy for SMP
    [    0.000000] Memory policy: Data cache writealloc
    [    0.000000] psci: probing for conduit method from DT.
    [    0.000000] psci: Using PSCI v0.1 Function IDs from DT
    [    0.000000] PERCPU: Embedded 13 pages/cpu @debaf000 s21248 r8192 d23808 u53248
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260608
    [    0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 earlyprintk rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=ubifs,2048
    [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
    [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
    [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
    [    0.000000] Memory: 1006224K/1048576K available (5804K kernel code, 365K rwdata, 1992K rodata, 360K init, 200K bss, 17776K reserved, 24576K cma-reserved, 507904K highmem)
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    [    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
    [    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
    [    0.000000]       .text : 0xc0008000 - 0xc07a56a8   (7798 kB)
    [    0.000000]       .init : 0xc07a6000 - 0xc0800000   ( 360 kB)
    [    0.000000]       .data : 0xc0800000 - 0xc085b614   ( 366 kB)
    [    0.000000]        .bss : 0xc085d000 - 0xc088f184   ( 201 kB)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
    [    0.000000] Preemptible hierarchical RCU implementation.
    [    0.000000]  Build-time adjustment of leaf fanout to 32.
    [    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
    [    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
    [    0.000000] NR_IRQS:16 nr_irqs:16 16
    [    0.000000] of_psc_clk_init: error registering clk clkpcie1
    [    0.000000] Architected cp15 timer(s) running at 199.68MHz (virt).
    [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles:
     0x2e0d652267, max_idle_ns: 440795206693 ns
    [    0.000003] sched_clock: 56 bits at 199MHz, resolution 5ns, wraps every 4398046511101ns
    [    0.008108] Switching to timer-based delay loop, resolution 5ns
    [    0.014233] keystone timer clock @199680000 Hz
    [    0.018963] Console: colour dummy device 80x30
    [    0.023506] Calibrating delay loop (skipped), value calculated using timer frequency.. 399.36 BogoMIPS (lpj=1996800)
    [    0.034146] pid_max: default: 4096 minimum: 301
    [    0.038820] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.045540] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
    [    0.053041] Initializing cgroup subsys io
    [    0.057158] Initializing cgroup subsys devices
    [    0.061695] Initializing cgroup subsys freezer
    [    0.066239] CPU: Testing write buffer coherency: ok
    [    0.071372] /cpus/cpu@0 missing clock-frequency property
    [    0.076793] /cpus/cpu@1 missing clock-frequency property
    [    0.082212] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    [    0.087996] Setting up static identity map for 0x80008300 - 0x8000840c
    [    0.175945] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    [    0.176017] Brought up 2 CPUs
    [    0.184841] SMP: Total of 2 processors activated (798.72 BogoMIPS).
    [    0.191202] CPU: All CPU(s) started in SVC mode.
    [    0.196185] devtmpfs: initialized
    [    0.207975] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
    [    0.216098] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
    [    0.226601] pinctrl core: initialized pinctrl subsystem
    [    0.232222] NET: Registered protocol family 16
    [    0.237461] DMA: preallocated 256 KiB pool for atomic coherent allocations
    [    0.251629] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.258288] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.264909] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.271572] irq: no irq domain found for /soc/keystone_irq@26202a0 !
    [    0.284078] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
    [    0.292210] hw-breakpoint: maximum watchpoint size is 8 bytes.
    [    0.307073] vgaarb: loaded
    [    0.310128] SCSI subsystem initialized
    [    0.314359] usbcore: registered new interface driver usbfs
    [    0.320038] usbcore: registered new interface driver hub
    [    0.325547] usbcore: registered new device driver usb
    [    0.331883] pps_core: LinuxPPS API ver. 1 registered
    [    0.336968] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [    0.346259] PTP clock support registered
    [    0.351185] clocksource: Switched to clocksource arch_sys_counter
    [    0.382495] NET: Registered protocol family 2
    [    0.387356] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.394564] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
    [    0.401143] TCP: Hash tables configured (established 4096 bind 4096)
    [    0.407666] UDP hash table entries: 256 (order: 1, 8192 bytes)
    [    0.413632] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
    [    0.420121] NET: Registered protocol family 1
    [    0.424781] RPC: Registered named UNIX socket transport module.
    [    0.430795] RPC: Registered udp transport module.
    [    0.435616] RPC: Registered tcp transport module.
    [    0.440411] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [    0.447294] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
    [    0.456412] platform alarmtimer: set dma_pfn_offset00780000
    [    0.462541] futex hash table entries: 16 (order: -2, 1024 bytes)
    [    0.479190] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    [    0.485794] ntfs: driver 2.1.32 [Flags: R/O].
    [    0.490544] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    [    0.499382] NET: Registered protocol family 38
    [    0.504040] bounce: pool size: 64 pages
    [    0.508173] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
    [    0.515713] io scheduler noop registered
    [    0.519737] io scheduler deadline registered
    [    0.524149] io scheduler cfq registered (default)
    [    0.529101] keystone_irq soc:keystone_irq@26202a0: irqchip registered, nr_irqs 28
    [    0.538033] keystone-navigator-qmss soc:qmss@2a40000: qmgr start queue 0, number of queues 8192
    [    0.546975] keystone-navigator-qmss soc:qmss@2a40000: added qmgr start queue0, num of queues 8192, reg_peek f09c0000, reg_status f0986000, reg_config f0988000, reg_region f098a000, reg_push f0a00000, reg_pop f0a40000
    [    0.566658] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmwarefor pdsp pdsp0
    [    0.575171] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmwarefor pdsp pdsp3
    [    0.583680] keystone-navigator-qmss soc:qmss@2a40000: failed to get firmwarefor pdsp pdsp7
    [    0.592743] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 3 not started for range qos-inputs-0
    [    0.601857] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 7 not started for range qos-inputs-1
    [    0.610948] keystone-navigator-qmss soc:qmss@2a40000: pdsp id 0 not started for range acc-low-0
    [    0.629135] Unhandled fault: asynchronous external abort (0x211) at 0x00000000
    [    0.636454] pgd = c0003000
    [    0.639245] [00000000] *pgd=80000800004003, *pmd=00000000
    [    0.644743] Internal error: : 211 [#1] PREEMPT SMP ARM
    [    0.649973] Modules linked in:
    [    0.653116] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.19-gdb0b54cdad #9
    [    0.660174] Hardware name: Keystone
    [    0.663749] task: de478000 ti: de466000 task.ti: de466000
    [    0.669246] PC is at knav_dma_hw_init+0x4c/0xc0
    [    0.673869] LR is at get_parent_ip+0x10/0x2c
    [    0.678229] pc : [<c0422238>]    lr : [<c0048228>]    psr: 60000013
    [    0.678229] sp : de467e48  ip : f09a6000  fp : de6a4df8
    [    0.689903] r10: c0881944  r9 : debe6b50  r8 : c0881944
    [    0.695219] r7 : debe696c  r6 : 00000080  r5 : de6a4e08  r4 : de6a4d90
    [    0.701842] r3 : 0000445c  r2 : 00000000  r1 : 00000000  r0 : 00000000
    [    0.708466] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
    [    0.715872] Control: 30c5387d  Table: 00003000  DAC: fffffffd
    [    0.721712] Process swapper/0 (pid: 1, stack limit = 0xde466210)
    [    0.727812] Stack: (0xde467e48 to 0xde468000)
    [    0.732260] 7e40:                   00000095 de6a4d90 de6a4e00 c0305868 00000000 00000000
    [    0.740539] 7e60: 00000000 c016d518 00000095 de60b010 debe696c de6a4dd4 00000b60 00000000
    [    0.748817] 7e80: 00000080 00000000 00000008 0000445c 00001000 00000000 c07ed83c ffffffef
    [    0.757095] 7ea0: de60b010 fffffdfb c082d97c 00000000 c07ed83c c07a6598 00000000 c0335d2c
    [    0.765374] 7ec0: c0335cdc de60b010 c088314c 00000000 c082d97c c0334a48 de60b010 c082d97c
    [    0.773652] 7ee0: de60b044 00000000 c07ceea0 c0334b9c 00000000 c082d97c c0334b10 c033317c
    [    0.781930] 7f00: de406f5c de5604b4 c082d97c de68df80 c08354b0 c0334148 c07040c4 c082d97c
    [    0.790208] 7f20: 00000006 c082d97c 00000006 228253d1 00000000 c033513c c0335c70 c07f9af0
    [    0.798486] 7f40: 00000006 c00096e0 0001398d 00000000 228253d1 00000000 00000006 c07f9af0
    [    0.806764] 7f60: 00000006 c07ed830 c085d000 00000095 c07a6598 c07a6dbc 00000006 00000006
    [    0.815043] 7f80: 00000000 c07a6598 00000000 c057ae30 00000000 00000000 00000000 00000000
    [    0.823321] 7fa0: 00000000 c057ae38 00000000 c000f668 00000000 00000000 00000000 00000000
    [    0.831599] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    [    0.839876] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
    [    0.848165] [<c0422238>] (knav_dma_hw_init) from [<c0305868>] (knav_dma_probe+0x62c/0x6c0)
    [    0.856536] [<c0305868>] (knav_dma_probe) from [<c0335d2c>] (platform_drv_probe+0x50/0xb0)
    [    0.864905] [<c0335d2c>] (platform_drv_probe) from [<c0334a48>] (driver_probe_device+0x1e0/0x2a8)
    [    0.873884] [<c0334a48>] (driver_probe_device) from [<c0334b9c>] (__driver_attach+0x8c/0x90)
    [    0.882426] [<c0334b9c>] (__driver_attach) from [<c033317c>] (bus_for_each_dev+0x54/0x88)
    [    0.890707] [<c033317c>] (bus_for_each_dev) from [<c0334148>] (bus_add_driver+0xec/0x1f8)
    [    0.898988] [<c0334148>] (bus_add_driver) from [<c033513c>] (driver_register+0x78/0xf4)
    [    0.907096] [<c033513c>] (driver_register) from [<c00096e0>] (do_one_initcall_debug+0x40/0x88)
    [    0.915814] [<c00096e0>] (do_one_initcall_debug) from [<c07a6dbc>] (kernel_init_freeable+0x118/0x1e4)
    [    0.925143] [<c07a6dbc>] (kernel_init_freeable) from [<c057ae38>] (kernel_init+0x8/0xf8)
    [    0.933337] [<c057ae38>] (kernel_init) from [<c000f668>] (ret_from_fork+0x14/0x2c)
    [    0.941007] Code: e594300c e7f03053 e1823003 e58c3004 (e5942008)
    [    0.947206] ---[ end trace 5d604c33f08e143b ]---
    [    0.951915] note: swapper/0[1] exited with preempt_count 1
    [    0.957534] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
    [    0.957534]
    [    0.966860] CPU1: stopping
    [    0.969656] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G      D         4.4.19-gdb0b54cdad #9
    [    0.977933] Hardware name: Keystone
    [    0.981520] [<c0016320>] (unwind_backtrace) from [<c0012980>] (show_stack+0x10/0x14)
    [    0.989369] [<c0012980>] (show_stack) from [<c02aa2fc>] (dump_stack+0x74/0x94)
    [    0.996693] [<c02aa2fc>] (dump_stack) from [<c00152a0>] (handle_IPI+0x1bc/0x36c)
    [    1.004190] [<c00152a0>] (handle_IPI) from [<c0009454>] (gic_handle_irq+0x80/0x8c)
    [    1.011862] [<c0009454>] (gic_handle_irq) from [<c0580d80>] (__irq_svc+0x40/0x74)
    [    1.019442] Exception stack(0xde49df90 to 0xde49dfd8)
    [    1.024585] df80:                                     00000001 00000000 de49dfe8 c001f420
    [    1.032864] dfa0: c08595c0 c058522c c08595c0 c07fa3a4 c0858d86 c080394c 00000000 00000001
    [    1.041142] dfc0: 00000001 de49dfe0 c0010084 c0010088 60000013 ffffffff
    [    1.047856] [<c0580d80>] (__irq_svc) from [<c0010088>] (arch_cpu_idle+0x30/0x3c)
    [    1.055357] [<c0010088>] (arch_cpu_idle) from [<c005c33c>] (cpu_startup_entry+0x120/0x340)
    [    1.063726] [<c005c33c>] (cpu_startup_entry) from [<800094ec>] (0x800094ec)
    [    1.070788] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
    [    1.070788]


    Best regards,

    Ari

  • Ari,

    Before trying to rebuild the UBI image, please use the released images to see if you can boot from UBI. You have not provided me the u-boot version and the images you are based from. From the logs, it appears to me that you are using the old u-boot from MCSDK, but filesystem from ProcSDK. If that is the case, they don't work together. Please go through the User's Guide to upgrade the u-boot to the same release.

    Rex

  • Hello Rex,

    thanks for your suggestions. I have tried with the released K2L rootfs kernel image, but it displays nothing for me after the u-boot's "Starting kernel...". In my own image I have set low level debugging ON and also enabled "earlyprintk" in the menuconfig before building the kernel. Otherwise I get nothing visible. The same is probably not done in the prebuilt image and I don't understand why I have to do it, since the kernel boot log (like dmesg in PC environment) is standard stuff and should be always displayed, from my opinion.

    Using the u-boot from the processor SDK gives me issues with NAND although otherwise it seems to work; even the DDR3 is stable although timings not set specifically for our board. Therefore, I prefer to use the old MCSDK u-boot, since it is able enough to load the images from NAND and start the kernel. It is easier for me to program some more functions into the old u-boot than to debug the NAND issues of the new u-boot,. So if I need something more, I prefer adding it into my good old MCSDK u-boot which I know now pretty well and I should be able to modify relatively easily. :-) I also don't think it is u-boot's fault if kernel fails to load some files, since u-boot is not even running any more when the kernel is booting (after "Starting kernel..." message), right?

    Nevertheless, I had some progress today. I added some debug prints into the kernel and found out that it tries to load the firmware from the following paths:

    pdsp0

    path=/lib/firmware/updates/4.4.19-gdb0b54cdad/ks2_qmss_pdsp_acc48.bin

    path=/lib/firmware/updates/ks2_qmss_pdsp_acc48.bin

    path=/lib/firmware/4.4.19-gdb0b54cdad/ks2_qmss_pdsp_acc48.bin

    path=/lib/firmware/ks2_qmss_pdsp_acc48.bin

    pdsp3

    path=/lib/firmware/updates/4.4.19-gdb0b54cdad/ks2_qmss_pdsp_qos.bin

    path=/lib/firmware/updates/ks2_qmss_pdsp_qos.bin

    path=/lib/firmware/4.4.19-gdb0b54cdad/ks2_qmss_pdsp_qos.bin

    path=/lib/firmware/ks2_qmss_pdsp_qos.bin

    pdsp7

    path=/lib/firmware/updates/4.4.19-gdb0b54cdad/ks2_qmss_pdsp_qos.bin

    path=/lib/firmware/updates/ks2_qmss_pdsp_qos.bin

    path=/lib/firmware/4.4.19-gdb0b54cdad/ks2_qmss_pdsp_qos.bin

    path=/lib/firmware/ks2_qmss_pdsp_qos.bin


    Now the problem still is, why the kernel cannot read the files. They are in place inside the UBI:

    K2L EVM # ubifsls /lib/firmware
    <DIR>         256  Tue Oct 04 01:07:57 2016  ipc
                 5556  Mon Oct 03 22:39:00 2016  ks2_pa_post_pdsp0.bin
                 3872  Mon Oct 03 22:39:00 2016  ks2_pa_post_pdsp1.bin
                 3952  Mon Oct 03 22:39:02 2016  ks2_qmss_pdsp_qos.bin
                 6860  Mon Oct 03 22:39:00 2016  ks2_pa_eg2_pdsp0.bin
                 2856  Mon Oct 03 22:39:03 2016  ks2_xgbe_serdes.bin
                 2840  Mon Oct 03 22:39:03 2016  ks2_pcie_serdes.bin
                 5872  Mon Oct 03 22:39:00 2016  ks2_pa_eg1_pdsp0.bin
                 7432  Mon Oct 03 22:39:00 2016  ks2_pa_in4_pdsp0.bin
                 5076  Mon Oct 03 22:39:00 2016  ks2_pa_in4_pdsp1.bin
                 4280  Mon Oct 03 22:39:01 2016  ks2_pa_eg0_pdsp0.bin
                 8384  Mon Oct 03 22:39:00 2016  ks2_pa_eg0_pdsp1.bin
                 7752  Mon Oct 03 22:39:01 2016  ks2_pa_eg0_pdsp2.bin
                 6944  Mon Oct 03 22:39:00 2016  ks2_pa_in3_pdsp0.bin
                 5588  Mon Oct 03 22:39:01 2016  ks2_pa_in2_pdsp0.bin
                 7472  Mon Oct 03 22:39:00 2016  ks2_pa_in1_pdsp0.bin
                 5748  Mon Oct 03 22:39:00 2016  ks2_pa_in1_pdsp1.bin
                 7328  Mon Oct 03 22:39:00 2016  ks2_pa_in0_pdsp0.bin
                 8496  Mon Oct 03 22:39:00 2016  ks2_pa_in0_pdsp1.bin
                 2488  Mon Oct 03 22:39:03 2016  ks2_gbe_serdes.bin
               104200  Mon Oct 03 22:39:03 2016  ks2_xgbe_serdes_mcu_fw.bin
                 2160  Mon Oct 03 22:57:42 2016  sa_mci.fw
                 1764  Mon Oct 03 22:39:02 2016  ks2_qmss_pdsp_acc48.bin
    K2L EVM #

    The file reading fails in "drivers/base/firmware_class.c" function "fw_get_filesystem_firmware(struct device *device, struct firmware_buf *buf)

    file = filp_open(path, O_RDONLY, 0);

    if (IS_ERR(file))

    continue;              <---- the execution comes here thus preventing the loading to work

    rc = fw_read_file_contents(file, buf);              <---- this line is not reached, the actual loading would have been done here

    The strange this is that if I read one of the files in u-boot, there is no problem:

    K2L EVM # ubifsload 0xffff0000 /lib/firmware/ks2_qmss_pdsp_qos.bin
    Loading file '/lib/firmware/ks2_qmss_pdsp_qos.bin' to addr 0xffff0000 with size 3952 (0x00000f70)...
    Done
    K2L EVM #

    Could this be some I/O access right issue of the kernel etc?

    Best regards,

    Ari

  • Hi, Ari,

    The ProcSDK has gone through major changes and won't work with u-boot from MCSDK. That is probably why the kernel does not boot. The mix match is not supported. I discourage you to proceed this way.

    Rex

  • Hello Rex,

    I fixed the NAND issue in our SDK u-boot. There was a 4k page size in the code, but our board has 2k NAND page size. After this correction the NAND seems to work OK with the u-boot. So now I have everything: u-boot, kernel and the UBI file system from the same release package, like you recommend to do.

    But still, the UBI images cannot be mounted, neither TI prebuilt nor our own.

    I took the "tisdk-server-rootfs-image-k2l-evm.ubi" from the SDK release package. With that I have tried the following:

    1. I burnt it as such, but it failed to mount.

    2. I ubinized it and then burnt to NAND, but it failed to mount, see log below.

    3. I burnt our own UBI image, but it failed to mount, but with the "good old" MCSDK u-boot it mounts perfectly.

    4. I verified with our K2H EVM by burning the K2HK server rootfs ubi into the EVM's NAND, but it also fails to mount.

    5. I unzipped the "tisdk-server-rootfs-image-k2l-evm.tar.gz", built an ubi file from the files inside it with the "mkfs.ubifs" tool, ubinized that and finally burnt it to NAND, but it also fails to mount with the same result than the attempt 2 above (see the log below)

    Should the ubi from the release package be ubinized or not, and if it should, how should it be done? Are there some extra steps or parameters to do compared to the MCSDK ubinize?

    Are there some extra u-boot commands to perform before mounting for the NAND or UBI in the new (SDK kernel 4.4) u-boot compared to MCSDK?

    Best regards,

    Ari



    u-boot log

    => ubi part ubifs
    ubi0: detaching mtd1
    ubi0: mtd1 is detached
    ubi0: attaching mtd1
    ubi0: scanning is finished
    ubi0: volume 1 ("rootfs") re-sized from 3584 to 4000 LEBs
    ubi0: attached mtd1 (name "mtd=2", size 510 MiB)
    ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
    ubi0: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0
    ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
    ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 11
    58873810
    ubi0: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB ha
    ndling: 76
    => ubifsmount rootfs
    Error reading superblock on volume 'rootfs' errno=-22!
    ubifsmount - mount UBIFS volume

    Usage:
    ubifsmount <volume-name>
        - mount 'volume-name' volume
    =>

  • Hi, Ari,

    I am interested in the 4th bullet of failure which you used K2H EVM. Since you want to stick with MCSDK u-boot, let's use MCSDK 3.1.4.7 (the latest of MCSDK) release in this post. All images should be used as is. You don't need to do anything more for these pre-built images. All necessary steps, such as ubinization, etc., were done during the build. Your u-boot environment setting is even older than MCSDK 3.1.4.7. I suggest you to reset the environment variables if you have not done it since u-boot upgrade. My printenv from MCSDK 3.1.4.7 u-boot is shown below. Yours has some important setting missing. The attachment is the console logs in which It contains the steps I did to bring up Kernel. I use CCS to load all images because it seems to be your preferred way.

    
    1) DIP switch set to ARM-SPI boot
       get u-boot up and interrupt the boot to get the u-boot prompt
    
    ver=U-Boot 2013.01 (Sep 30 2015 - 00:58:09)
    
    Environment size: 3046/262140 bytes
    K2HK EVM # 
    
    2) Start CCS, launch the K2H EVM, and connect to the ARM Cortex-A15 core 0
    
    3) Load the UBI image to the memory using CCS
       a) Pause CCS
       b) load memory -> File:k2hk-evm-ubifs.ubi, File Type:TI RAW Data
                      -> Start Address:0x82000000, Type Size:32 bits
                      -> Finish
       c) Resume CCS
    
       (Note: I don't understand why you prefer CCS to TFTP. I just mimic what you did here)
    
    4) Program NAND with the UBI image in the memory using the commands below
    
          K2HK EVM # nand erase.part ubifs
          NAND erase.part: device 0 offset 0x180000, size 0x1fe80000
          Skipping bad block at  0x1ff80000
          Skipping bad block at  0x1ffa0000
          Skipping bad block at  0x1ffc0000
          Skipping bad block at  0x1ffe0000
    
          OK
       
          K2HK EVM # nand write 0x82000000 ubifs 0x19000000
    
          NAND write: device 0 offset 0x180000, size 0x19000000
          419430400 bytes written: OK
    
    5) Configure the bootargs
    
          K2HK EVM # setenv bootargs 'console=ttyS0,115200n8 rootwait=1 rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048'
    
    6) Load the secure key from NAND filessytem
    
          K2HK EVM # ubi part ubifs
          Creating 1 MTD partitions on "nand0":
          0x000000180000-0x000020000000 : "mtd=2"
          UBI: attaching mtd1 to ubi0
          UBI: physical eraseblock size:   131072 bytes (128 KiB)
          UBI: logical eraseblock size:    126976 bytes
          UBI: smallest flash I/O unit:    2048
          UBI: VID header offset:          2048 (aligned 2048)
          UBI: data offset:                4096
          UBI: volume 2 ("rootfs") re-sized from 3046 to 3703 LEBs
          UBI: attached mtd1 to ubi0
          UBI: MTD device name:            "mtd=2"
          UBI: MTD device size:            510 MiB
          UBI: number of good PEBs:        4080
          UBI: number of bad PEBs:         4
          UBI: max. allowed volumes:       128
          UBI: wear-leveling threshold:    4096
          UBI: number of internal volumes: 1
          UBI: number of user volumes:     5
          UBI: available PEBs:             0
          UBI: total number of reserved PEBs: 4080
          UBI: number of PEBs reserved for bad PEB handling: 40
          UBI: max/mean erase counter: 1/0
    
          K2HK EVM # ubifsmount boot
          UBIFS: mounted UBI device 0, volume 0, name "boot"
          UBIFS: mounted read-only
          UBIFS: file system size:   9269248 bytes (9052 KiB, 8 MiB, 73 LEBs)
          UBIFS: journal size:       1650688 bytes (1612 KiB, 1 MiB, 13 LEBs)
          UBIFS: media format:       w4/r0 (latest is w4/r0)
          UBIFS: default compressor: LZO
          UBIFS: reserved for root:  0 bytes (0 KiB)
    
          (Note: Checking what are in this partition)
          K2HK EVM # ubifsls
                46348  Wed Sep 30 08:12:08 2015  uImage-k2l-evm.dtb
                45056  Wed Sep 30 10:57:25 2015  skern-k2l-evm.bin
                46081  Wed Sep 30 08:07:01 2015  uImage-k2e-evm.dtb
              4083176  Wed Sep 30 08:12:08 2015  uImage-keystone-evm.bin
                45056  Wed Sep 30 10:27:39 2015  skern-k2hk-evm.bin
                45056  Wed Sep 30 10:43:50 2015  skern-k2e-evm.bin
                55893  Wed Sep 30 08:10:48 2015  uImage-k2hk-evm.dtb
                   28  Wed Sep 30 10:57:25 2015  securedb.key.bin
    
          K2HK EVM # ubifsload 0x0c000000 securedb.key.bin
          Loading file 'securedb.key.bin' to addr 0x0c000000 with size 28 (0x0000001c)...
          Done
    
    7) Load DTB, Boot Monitor, and Kernel into memory using CCS
    
          K2HK EVM # ubifsload 0x87000000 uImage-k2hk-evm.dtb
          Loading file 'uImage-k2hk-evm.dtb' to addr 0x87000000 with size 55893 (0x0000da55)...
          Done
    
          K2HK EVM # ubifsload 0x0c5f0000 skern-k2hk-evm.bin
          Loading file 'skern-k2hk-evm.bin' to addr 0x0c5f0000 with size 45056 (0x0000b000)...
          Done
    
          K2HK EVM # ubifsload 0x88000000 uImage-keystone-evm.bin
          Loading file 'uImage-keystone-evm.bin' to addr 0x88000000 with size 4083176 (0x003e4de8)...
          Done
    
    
    8) Install Boot Monitor
    
          K2HK EVM # mon_install 0x0c5f0000
          ## installed monitor, freq [200000000], status 0
    
    9) Boot Kernel
    
          K2HK EVM # bootm 0x88000000 - 0x87000000
          ## Booting kernel from Legacy Image at 88000000 ...
             Image Name:   Linux-3.10.72-gca334de
             Created:      2015-09-30   7:51:42 UTC
             Image Type:   ARM Linux Kernel Image (uncompressed)
             Data Size:    4083112 Bytes = 3.9 MiB
             Load Address: 80008000
             Entry Point:  80008000
             Verifying Checksum ... OK
          ## Flattened Device Tree blob at 87000000
             Booting using the fdt blob at 0x87000000
             Loading Kernel Image ... OK
          OK
             Using Device Tree in place at 87000000, end 87010a54
    
    Starting kernel ...
    
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Linux version 3.10.72-gca334de (gtbldadm@ubuntu-12) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 SMP Wed Sep 30 03:51:28 EDT 2015
    [    0.000000] CPU: ARMv7 Processor [412fc0f4] revision 4 (ARMv7), cr=30c7387d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
    [    0.000000] Machine: KeyStone2, model: Texas Instruments Keystone 2 SoC
    [    0.000000] switching to high address space at 0x800000000
    [    0.000000] cma: CMA: reserved 16 MiB at 2e800000
    [    0.000000] Memory policy: ECC disabled, Data cache writealloc
    [    0.000000] PERCPU: Embedded 8 pages/cpu @c4849000 s11264 r8192 d13312 u32768
    [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 1964560
    [    0.000000] Kernel command line: console=ttyS0,115200n8 rootwait=1 rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048
    [    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
    [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    [    0.000000] Memory: 1536MB 6144MB = 7680MB total
    [    0.000000] Memory: 7776984k/7776984k available, 87336k reserved, 7086080K highmem
    [    0.000000] Virtual kernel memory layout:
    [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    [    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    [    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    [    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    [    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
    [    0.000000]       .text : 0xc0008000 - 0xc0733c1c   (7344 kB)
    [    0.000000]       .init : 0xc0734000 - 0xc0786c00   ( 331 kB)
    [    0.000000]       .data : 0xc0788000 - 0xc07ea618   ( 394 kB)
    [    0.000000]        .bss : 0xc07ea618 - 0xc081c2bc   ( 200 kB)
    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [    0.000000] Hierarchical RCU implementation.
    [    0.000000] NR_IRQS:16 nr_irqs:16 16
    [    0.000000] ipc irq: irqchip registered, range 512-539
    [    0.000000] Main PLL clk (1200000000 Hz), parent (122880000 Hz),postdiv = 2, mult = 624, prediv = 31
    [    0.000000] Generic PLL clk (1400000000 Hz), parent (125000000 Hz),postdiv = 1, mult = 55, prediv = 4
    [    0.000000] Generic PLL clk (983040000 Hz), parent (122880000 Hz),postdiv = 2, mult = 15, prediv = 0
    [    0.000000] Generic PLL clk (400000000 Hz), parent (100000000 Hz),postdiv = 4, mult = 15, prediv = 0
    [    0.000000] Generic PLL clk (333333333 Hz), parent (100000000 Hz),postdiv = 6, mult = 19, prediv = 0
    [    0.000000] Architected local timer running at 200.00MHz (phys).
    [    0.000000] Switching to timer-based delay loop
    [    0.000000] sched_clock: ARM arch timer >56 bits at 200000kHz, resolution 640/128ns
    [    0.000000] keystone timer clock @200000000 MHz
    [    0.000000] sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
    [    0.000000] Console: colour dummy device 80x30
    [ 6856.214690] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
    [ 6856.214699] pid_max: default: 4096 minimum: 301
    [ 6856.214814] Mount-cache hash table entries: 512
    [ 6856.222770] CPU: Testing write buffer coherency: ok
    [ 6856.222918] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
    [ 6856.222927] psci: probing function IDs from device-tree
    [ 6856.222937] Setting up static identity map for 0xc05117a0 - 0xc05117f8
    [ 6856.227729] CPU1: Booted secondary processor
    [ 6856.227753] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    [ 6856.232325] CPU2: Booted secondary processor
    [ 6856.232349] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
    [ 6856.236915] CPU3: Booted secondary processor
    [ 6856.236939] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
    [ 6856.237005] Brought up 4 CPUs
    [ 6856.237020] SMP: Total of 4 processors activated (1600.00 BogoMIPS).
    [ 6856.237024] CPU: All CPU(s) started in SVC mode.
    [ 6856.237411] devtmpfs: initialized
    [ 6856.248237] NET: Registered protocol family 16
    [ 6856.249010] DMA: preallocated 256 KiB pool for atomic coherent allocations
    [ 6856.259775] No ATAGs?
    [ 6856.259790] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
    [ 6856.259795] hw-breakpoint: maximum watchpoint size is 8 bytes.
    [ 6856.268384] bio: create slab <bio-0> at 0
    [ 6856.268724] keystone-pcie: keystone_pcie_rc_init - start
    [ 6856.268743] keystone2_pcie_serdes_setup for domain 0
    [ 6856.270863] keystone2_pcie_serdes_setup done domain 0, en_link_train = 1
    [ 6856.270887] keystone-pcie: MEM 0x0000000050000000..0x000000005fffffff -> 0x0000000050000000
    [ 6856.270895] keystone-pcie: IO 0x0000000023250000..0x0000000023253fff -> 0x0000000000000000
    [ 6856.270922] keystone-pcie: pcie - number of legacy irqs = 4
    [ 6856.270960] keystone-pcie: pcie - number of MSI host irqs = 8, msi_irqs = 32
    [ 6856.374668] keystone-pcie: Doing PCI Setup...Done
    [ 6856.374673] keystone-pcie: Starting PCI scan, nr 0...
    [ 6856.374783] PCI host bridge to bus 0000:00
    [ 6856.374792] pci_bus 0000:00: root bus resource [mem 0x50000000-0x5fffffff]
    [ 6856.374798] pci_bus 0000:00: root bus resource [io  0x0000-0x3fff]
    [ 6856.374804] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
    [ 6856.374840] PCI: bus0: Fast back to back transfers enabled
    [ 6856.374854] keystone-pcie: Ending PCI scan...
    [ 6856.374860] keystone-pcie: keystone_pcie_rc_init - end
    [ 6856.375090] vgaarb: loaded
    [ 6856.375351] SCSI subsystem initialized
    [ 6856.375846] usbcore: registered new interface driver usbfs
    [ 6856.375913] usbcore: registered new interface driver hub
    [ 6856.375994] usbcore: registered new device driver usb
    [ 6856.376941] pps_core: LinuxPPS API ver. 1 registered
    [ 6856.376946] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
    [ 6856.376999] PTP clock support registered
    [ 6856.377120] keystone-hwqueue hwqueue.36: qmgr start queue 0, number of queues 8192
    [ 6856.377184] keystone-hwqueue hwqueue.36: added qmgr start queue 0, num of queues 8192, reg_peek f0040000, reg_status f0006000, reg_config f0008000, reg_region f000a000, reg_push f0080000, reg_pop f00c0000
    [ 6856.377192] keystone-hwqueue hwqueue.36: qmgr start queue 8192, number of queues 8192
    [ 6856.377251] keystone-hwqueue hwqueue.36: added qmgr start queue 8192, num of queues 8192, reg_peek f0100000, reg_status f000c400, reg_config f000e000, reg_region f001a000, reg_push f0140000, reg_pop f0180000
    [ 6856.377895] keystone-hwqueue hwqueue.36: qos: sched port @8096, drop sched @8000
    [ 6856.378750] keystone-hwqueue hwqueue.36: qos: sched port @6496, drop sched @6400
    [ 6856.379543] keystone-hwqueue hwqueue.36: added pool pool-rio: 128 descriptors of size 256
    [ 6856.379551] keystone-hwqueue hwqueue.36: added pool pool-xge: 1024 descriptors of size 128
    [ 6856.379558] keystone-hwqueue hwqueue.36: added pool pool-crypto: 1024 descriptors of size 128
    [ 6856.379565] keystone-hwqueue hwqueue.36: added pool pool-net: 11264 descriptors of size 128
    [ 6856.379572] keystone-hwqueue hwqueue.36: added pool pool-udma: 1920 descriptors of size 256
    [ 6856.381608] keystone-hwqueue hwqueue.36: registered queues 0-16383
    [ 6856.381863] keystone-hwqueue hwqueue.36: qos version 0x200010b, magic valid
    [ 6856.382337] keystone-hwqueue hwqueue.36: qos version 0x200010b, magic valid
    [ 6856.388418] keystone-pktdma 2a08000.pktdma: registered 32 logical channels, flows 32, tx chans: 32, rx chans: 32, loopback
    [ 6856.391443] keystone-pktdma 2004000.pktdma: registered 33 logical channels, flows 32, tx chans: 9, rx chans: 24
    [ 6856.391874] keystone-pktdma 2fa1000.pktdma: registered 4 logical channels, flows 32, tx chans: 16, rx chans: 16
    [ 6856.391987] Switching to clocksource arch_sys_counter
    [ 6856.407359] NET: Registered protocol family 2
    [ 6856.407776] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
    [ 6856.407871] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
    [ 6856.407964] TCP: Hash tables configured (established 8192 bind 8192)
    [ 6856.408007] TCP: reno registered
    [ 6856.408014] UDP hash table entries: 512 (order: 2, 16384 bytes)
    [ 6856.408036] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
    [ 6856.408182] NET: Registered protocol family 1
    [ 6856.408316] RPC: Registered named UNIX socket transport module.
    [ 6856.408321] RPC: Registered udp transport module.
    [ 6856.408325] RPC: Registered tcp transport module.
    [ 6856.408329] RPC: Registered tcp NFSv4.1 backchannel transport module.
    [ 6856.408676] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
    [ 6856.473699] bounce pool size: 64 pages
    [ 6856.479699] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    [ 6856.479836] NTFS driver 2.1.30 [Flags: R/O].
    [ 6856.480025] jffs2: version 2.2. (NAND) � 2001-2006 Red Hat, Inc.
    [ 6856.480268] msgmni has been set to 1381
    [ 6856.481025] NET: Registered protocol family 38
    [ 6856.481186] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 6856.481192] io scheduler noop registered
    [ 6856.481197] io scheduler deadline registered
    [ 6856.481291] io scheduler cfq registered (default)
    [ 6856.482558] keystone-udma udma0.37: registered udma device udma0
    [ 6856.528238] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 6856.529528] 2530c00.serial: ttyS0 at MMIO 0x2530c00 (irq = 309) is a 16550A
    [ 6857.377255] console [ttyS0] enabled
    [ 6857.381269] 2531000.serial: ttyS1 at MMIO 0x2531000 (irq = 312) is a 16550A
    [ 6857.390755] loop: module loaded
    [ 6857.395043] at24 0-0050: 131072 byte 24c1024 EEPROM, writable, 1 bytes/write
    [ 6857.403213] Generic platform RAM MTD, (c) 2004 Simtec Electronics
    [ 6857.410080] ONFI param page 0 valid
    [ 6857.413584] ONFI flash detected
    [ 6857.416732] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xac (Micron MT29F4G08ABBDAHC), 512MiB, page size: 2048, OOB size: 64
    [ 6857.428397] Bad block table found at page 262080, version 0x01
    [ 6857.434645] Bad block table found at page 262016, version 0x01
    [ 6857.440744] 3 ofpart partitions found on MTD device 30000000.nand
    [ 6857.446860] Creating 3 MTD partitions on "30000000.nand":
    [ 6857.452279] 0x000000000000-0x000000100000 : "u-boot"
    [ 6857.457789] 0x000000100000-0x000000180000 : "params"
    [ 6857.463273] 0x000000180000-0x000020000000 : "ubifs"
    [ 6857.468796] davinci_nand 30000000.nand: controller rev. 2.5
    [ 6857.474922] spi_davinci 21000400.spi: master is unqueued, this is deprecated
    [ 6857.482229] m25p80 spi32766.0: found n25q128a11, expected n25q128
    [ 6857.488343] m25p80 spi32766.0: n25q128a11 (16384 Kbytes)
    [ 6857.493686] 2 ofpart partitions found on MTD device spi32766.0
    [ 6857.499535] Creating 2 MTD partitions on "spi32766.0":
    [ 6857.504693] 0x000000000000-0x000000080000 : "u-boot-spl"
    [ 6857.510507] 0x000000080000-0x000001000000 : "test"
    [ 6857.516059] spi_davinci 21000400.spi: Controller at 0xf007a400
    [ 6857.522196] spi_davinci 21000600.spi: master is unqueued, this is deprecated
    [ 6857.529267] spi_davinci 21000600.spi: Controller at 0xf007c600
    [ 6857.535385] spi_davinci 21000800.spi: master is unqueued, this is deprecated
    [ 6857.542467] spi_davinci 21000800.spi: Controller at 0xf007e800
    [ 6857.549203] tun: Universal TUN/TAP device driver, 1.6
    [ 6857.554275] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
    [ 6857.560908] keystone-netcp 2090000.netcp: number of serdeses 1
    [ 6857.566776] keystone-netcp 2090000.netcp: Missing cpts_clock_mult property in the DT.
    [ 6857.574637] keystone-netcp 2090000.netcp: Missing cpts_clock_shift property in the DT.
    [ 6857.582587] keystone-netcp 2090000.netcp: Missing cpts_clock_div property in the DT.
    [ 6857.591315] keystone-netcp 2090000.netcp: cpsw serdes 0 config done lanes(mask) 0x3
    [ 6857.599702] keystone-netcp 2090000.netcp: Created interface "eth0"
    [ 6857.605915] keystone-netcp 2090000.netcp: dma_chan_name nettx0
    [ 6857.612532] keystone-netcp 2090000.netcp: Created interface "eth1"
    [ 6857.618736] keystone-netcp 2090000.netcp: dma_chan_name nettx1
    [ 6857.625252] keystone-netcp 2090000.netcp: Created interface "eth2"
    [ 6857.631456] keystone-netcp 2090000.netcp: dma_chan_name nettx2
    [ 6857.637978] keystone-netcp 2090000.netcp: Created interface "eth3"
    [ 6857.644188] keystone-netcp 2090000.netcp: dma_chan_name nettx3
    [ 6857.650161] keystone-netcp 2090000.netcp: pdsp 0 firmware: keystone/pa_pdsp0_classify1.fw
    [ 6857.658375] keystone-netcp 2090000.netcp: pdsp 1 firmware: keystone/pa_pdsp1_classify1.fw
    [ 6857.666585] keystone-netcp 2090000.netcp: pdsp 2 firmware: keystone/pa_pdsp2_classify1.fw
    [ 6857.674795] keystone-netcp 2090000.netcp: pdsp 3 firmware: keystone/pa_pdsp3_classify2.fw
    [ 6857.683006] keystone-netcp 2090000.netcp: pdsp 4 firmware: keystone/pa_pdsp45_pam.fw
    [ 6857.690775] keystone-netcp 2090000.netcp: pdsp 5 firmware: keystone/pa_pdsp45_pam.fw
    [ 6857.698682] keystone-netcp 2090000.netcp: could not find interface 2 node in device tree
    [ 6857.706806] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
    [ 6857.715017] keystone-netcp 2090000.netcp: could not find interface 3 node in device tree
    [ 6857.723139] keystone-netcp 2090000.netcp: Attach of module keystone-qos declined with -19
    [ 6857.731357] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
    [ 6857.739480] keystone-netcp 2090000.netcp: Attach of module keystone-sa declined with -19
    [ 6857.748428] dwc3 2690000.dwc3: no usb2 phy configured
    [ 6857.753512] platform 2690000.dwc3: Driver dwc3 requests probe deferral
    [ 6857.760426] usbcore: registered new interface driver usb-storage
    [ 6857.766811] mousedev: PS/2 mouse device common for all mice
    [ 6857.772573] i2c /dev entries driver
    [ 6857.776613] watchdog 22f0080.wdt: heartbeat 60 sec
    [ 6857.792290] keystone-crypto 20c0000.crypto: crypto accelerator enabled
    [ 6857.799091] usbcore: registered new interface driver usbhid
    [ 6857.804686] usbhid: USB HID core driver
    [ 6857.808811]  remoteproc0: 2620040.dsp0 is available
    [ 6857.813709]  remoteproc0: Note: remoteproc is still under development and considered experimental.
    [ 6857.822702]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6857.833107]  remoteproc0: no firmware found
    [ 6857.837397] rproc-user 2620040.dsp0: registered misc device dsp0
    [ 6857.843612]  remoteproc1: 2620044.dsp1 is available
    [ 6857.848503]  remoteproc1: Note: remoteproc is still under development and considered experimental.
    [ 6857.857497]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6857.867910]  remoteproc1: no firmware found
    [ 6857.872207] rproc-user 2620044.dsp1: registered misc device dsp1
    [ 6857.878413]  remoteproc2: 2620048.dsp2 is available
    [ 6857.883311]  remoteproc2: Note: remoteproc is still under development and considered experimental.
    [ 6857.892306]  remoteproc2: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6857.902708]  remoteproc2: no firmware found
    [ 6857.906999] rproc-user 2620048.dsp2: registered misc device dsp2
    [ 6857.913215]  remoteproc3: 262004c.dsp3 is available
    [ 6857.918105]  remoteproc3: Note: remoteproc is still under development and considered experimental.
    [ 6857.927100]  remoteproc3: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6857.937504]  remoteproc3: no firmware found
    [ 6857.941795] rproc-user 262004c.dsp3: registered misc device dsp3
    [ 6857.948008]  remoteproc4: 2620050.dsp4 is available
    [ 6857.952905]  remoteproc4: Note: remoteproc is still under development and considered experimental.
    [ 6857.961892]  remoteproc4: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6857.972296]  remoteproc4: no firmware found
    [ 6857.976589] rproc-user 2620050.dsp4: registered misc device dsp4
    [ 6857.982802]  remoteproc5: 2620054.dsp5 is available
    [ 6857.987693]  remoteproc5: Note: remoteproc is still under development and considered experimental.
    [ 6857.996687]  remoteproc5: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6858.007089]  remoteproc5: no firmware found
    [ 6858.011379] rproc-user 2620054.dsp5: registered misc device dsp5
    [ 6858.017600]  remoteproc6: 2620058.dsp6 is available
    [ 6858.022497]  remoteproc6: Note: remoteproc is still under development and considered experimental.
    [ 6858.031485]  remoteproc6: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6858.041887]  remoteproc6: no firmware found
    [ 6858.046180] rproc-user 2620058.dsp6: registered misc device dsp6
    [ 6858.052394]  remoteproc7: 262005c.dsp7 is available
    [ 6858.057285]  remoteproc7: Note: remoteproc is still under development and considered experimental.
    [ 6858.066279]  remoteproc7: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
    [ 6858.076690]  remoteproc7: no firmware found
    [ 6858.080985] rproc-user 262005c.dsp7: registered misc device dsp7
    [ 6858.087034] rproc-user dspmem.38: kick gpio
    [ 6858.091333] rproc-user dspmem.38: registered misc device dspmem
    [ 6858.097540] oprofile: using arm/armv7-ca15
    [ 6858.101740] ipip: IPv4 over IPv4 tunneling driver
    [ 6858.106785] gre: GRE over IPv4 demultiplexor driver
    [ 6858.111675] ip_gre: GRE over IPv4 tunneling driver
    [ 6858.117124] TCP: cubic registered
    [ 6858.120445] Initializing XFRM netlink socket
    [ 6858.125078] NET: Registered protocol family 10
    [ 6858.130408] NET: Registered protocol family 17
    [ 6858.134882] NET: Registered protocol family 15
    [ 6858.139376] Bridge firewalling registered
    [ 6858.143403] 8021q: 802.1Q VLAN Support v1.8
    [ 6858.149040] sctp: Hash tables configured (established 65536 bind 65536)
    [ 6858.155854] NET: Registered protocol family 41
    [ 6858.160413] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
    [ 6858.168120] Registering SWP/SWPB emulation handler
    [ 6858.374666] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    [ 6858.380178] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
    [ 6858.388314] xhci-hcd xhci-hcd.0.auto: irq 425, io mem 0x02690000
    [ 6858.394405] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    [ 6858.401215] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [ 6858.408467] usb usb1: Product: xHCI Host Controller
    [ 6858.413363] usb usb1: Manufacturer: Linux 3.10.72-gca334de xhci-hcd
    [ 6858.419649] usb usb1: SerialNumber: xhci-hcd.0.auto
    [ 6858.424894] hub 1-0:1.0: USB hub found
    [ 6858.428656] hub 1-0:1.0: 1 port detected
    [ 6858.432752] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    [ 6858.438258] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
    [ 6858.446006] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
    [ 6858.452823] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    [ 6858.460069] usb usb2: Product: xHCI Host Controller
    [ 6858.464965] usb usb2: Manufacturer: Linux 3.10.72-gca334de xhci-hcd
    [ 6858.471251] usb usb2: SerialNumber: xhci-hcd.0.auto
    [ 6858.476471] hub 2-0:1.0: USB hub found
    [ 6858.480237] hub 2-0:1.0: 1 port detected
    [ 6858.484516] UBI: attaching mtd2 to ubi0
    [ 6860.097608] UBI: scanning is finished
    [ 6860.107920] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 40, need 76
    [ 6860.120276] UBI: attached mtd2 (name "ubifs", size 510 MiB) to ubi0
    [ 6860.126570] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
    [ 6860.133384] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
    [ 6860.140105] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
    [ 6860.147003] UBI: good PEBs: 4080, bad PEBs: 4, corrupted PEBs: 0
    [ 6860.153030] UBI: user volume: 5, internal volumes: 1, max. volumes count: 128
    [ 6860.160188] UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1624713962
    [ 6860.169270] UBI: available PEBs: 0, total reserved PEBs: 4080, PEBs reserved for bad PEB handling: 40
    [ 6860.178532] UBI: background thread "ubi_bgt0d" started, PID 1348
    [ 6860.185090] UBIFS: parse sync
    [ 6860.189465] UBIFS: background thread "ubifs_bgt0_2" started, PID 1351
    [ 6860.220890] UBIFS: start fixing up free space
    [ 6878.214598] UBIFS: free space fixup complete
    [ 6878.231715] UBIFS: mounted UBI device 0, volume 2, name "rootfs"
    [ 6878.237748] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
    [ 6878.246918] UBIFS: FS size: 468795392 bytes (447 MiB, 3692 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
    [ 6878.256870] UBIFS: reserved for root: 0 bytes (0 KiB)
    [ 6878.261937] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 91ADB375-6ABB-4B9A-B5DA-8FD49B2C3EED, small LPT model
    [ 6878.273941] VFS: Mounted root (ubifs filesystem) on device 0:12.
    [ 6878.281002] devtmpfs: mounted
    [ 6878.284103] Freeing unused kernel memory: 328K (c0734000 - c0786000)
    INIT: version 2.88 booting
    Starting udev
    [ 6878.785158] udevd[1374]: starting version 182
    [ 6878.940243] temperature_kmodule: Unknown symbol hwmon_device_register (err 0)
    [ 6878.947484] temperature_kmodule: Unknown symbol hwmon_device_unregister (err 0)
    [ 6879.021801] uio_module_drv mpax.4: registered misc device mpax
    [ 6879.027330] temperature_kmodule: Unknown symbol hwmon_device_register (err 0)
    [ 6879.027368] temperature_kmodule: Unknown symbol hwmon_device_unregister (err 0)
    [ 6879.049228] uio_module_drv edma3.5: registered misc device edma3
    [ 6879.086905] uio_module_drv secmgr.6: registered misc device secmgr
    [ 6879.097336] uio_module_drv qmss.7: registered misc device qmss
    [ 6879.115965] uio_module_drv hyperlink0.41: registered misc device hyperlink0
    [ 6879.132200] uio_module_drv hyperlink1.42: registered misc device hyperlink1
    [ 6879.159705] uio_module_drv srio.43: registered misc device srio
    [ 6879.496463] CMEMK module: built on Sep 30 2015 at 00:40:48
    [ 6879.501969]   Reference Linux version 3.10.72
    [ 6879.506452] no physical memory specified
    [ 6879.510393] cmemk initialized
    Starting Bootlog daemon: bootlogd.
    Populating dev cache
    net.ipv4.conf.default.rp_filter = 1
    net.ipv4.conf.all.rp_filter = 1
    Wed Sep 30 05:59:00 UTC 2015
    update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
     Removing any system startup links for run-postinsts ...
      /etc/rcS.d/S99run-postinsts
    INIT: Entering runlevel: 5
    Configuring network interfaces... [ 6880.977312] keystone-netcp 2090000.netcp: initializing cpsw version 1.3 (1) SGMII identification value 0x4ed1
    [ 6880.987383] keystone-netcp 2090000.netcp: Created a cpsw ale engine
    [ 6881.072252] pps pps0: new PPS source ptp0
    [ 6881.076287] cpts rftclk rate(600000000 HZ),mult(5120),shift(10),div(3)
    [ 6881.117959] keystone-netcp 2090000.netcp: Using Packet Accelerator Firmware version 0x03000105
    [ 6881.126611] keystone-netcp 2090000.netcp: pa_clk_rate(163840000 HZ),mult(25000),shift(12)
    [ 6881.412317] net eth0: netcp device eth0 opened
    [ 6881.418917] 8021q: adding VLAN 0 to HW filter on device eth0
    udhcpc (v1.22.1) started
    Sending discover...
    Sending select for 158.218.109.209...
    Lease of 158.218.109.209 obtained, lease time 3600
    /etc/udhcpc.d/50default: Adding DNS 192.0.2.2
    /etc/udhcpc.d/50default: Adding DNS 192.0.2.3
    done.
    Starting system message bus: dbus.
    Removing existing CMEMK module[ 6882.890133] cmemk unregistered
    Inserting CMEMK module[ 6882.896483] CMEMK module: built on Sep 30 2015 at 00:40:48
    [ 6882.901987]   Reference Linux version 3.10.72
    [ 6882.906477] CMEMK Error: Failed to request_mem_region(0x829000000, 0x57000000)
    modprobe: ERROR: could not insert 'cmemk': Bad address
    .
    Starting Dropbear SSH server: Generating key, this may take a while...
    Public key portion is:
    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDCo0ZPi/6qYnvh2SywHrv5vd09fzqsoXlPtWOu2GKYIiT2N3KLLglgwFfriTdbJPttcOGpYST/QgUcpk5rDi1ENmg4pbVJ+zt7k5uMx3F4gE/A3smZnHgGC1bKHzJL/4S4+DN1UgEFxo6f4cTuBnFjeleESvqtsvRU7tQI0wJ5dVGNF62d1/r1GEDWSv1xQj9mTYPAFRrilkzBw4I0WAz/5rmwmLPOWkGa7hHMFMfJAFPtAmnKhKKuBtgHhQRcRnG8airN4OxC6HjU01jbE3UlNS8TmQfoM/4Hyprz7CdrZGvqZmrsrE9i+wiUhAX/K8adauEyG227QFmQHcAKY+m5 root@k2hk-evm
    Fingerprint: md5 83:28:08:c9:0f:25:cb:1b:7d:27:ef:22:84:03:93:89
    dropbear.
    cppi library link established for device : k2hk
    hyplnk library link established for device : k2hk
    PA library link established for device : k2hk
    qmss library link established for device : k2hk
    Starting mpmsrv daemon.
    Starting rmsrv daemonStarting /usr/bin/rmServer.out
    Daemon returned 0 as return value.
    .
    platform: k2hk-evm
    Starting softhsm daemon.
    Starting telnet daemon.
    Starting tiipclad daemon
    GateMP is not supported for this device
    
    Opened log file: lad.txt
    
    numProcessors = 9 id = 0 baseId = 0
    
    Spawned daemon: /usr/bin/lad_tci6638
    
    .
    UDEV trigger to register devices opened before udev came up
    [ 6888.887901] temperature_kmodule: Unknown symbol hwmon_device_register (err 0)
    [ 6888.895112] temperature_kmodule: Unknown symbol hwmon_device_unregister (err 0)
    Starting rpcbind daemon...done.
    creating NFS state directory: done
    starting statd: done
    Enabling Hyperlink Txtransport open_tx_only succeeded for arm-remote-hyplnk-0
    Starting thttpd.
    Starting Lighttpd Web Server: lighttpd.
    2015-09-30 05:59:09: (/home/gtbldadm/yocto/mcsdk-3_01_04_07/oe-layersetup-mcsdk/build/arago-tmp-external-linaro-toolchain/work/cortexa15t2hf-vfp-neon-linux-gnueabi/lighttpd/1.4.33-r1/lighttpd-1.4.33/src/log.c.166) server started
    * starting FTP Server: vsftpd... done.
    
    
    #>>>>> LCD 12
    IP Address:
    158.218.109.209
    Enabling thermal zones...
    /etc/rc5.d/S98thermal-zone-init: line 7: /sys/class/thermal/thermal_zone*/mode: No such file or directory
    ***************************************************************
    ***************************************************************
    NOTICE: This file system contains the following GPLv3 packages:
            autoconf
            binutils-dev
            binutils
            bison-dev
            bison
            coreutils-dev
            coreutils
            cpp-symlinks
            cpp
            g++-symlinks
            g++
            gawk-common
            gawk-dev
            gawk
            gcc-symlinks
            gcc
            gdb
            gdbc6x
            gdbserver
            libgmp-dev
            libgmp10
            libgmpxx4
            libmpc3
            libmpfr4
            make
    
    If you do not wish to distribute GPLv3 components please remove
    the above packages prior to distribution.  This can be done using
    the opkg remove command.  i.e.:
        opkg remove <package>
    Where <package> is the name printed in the list above
    
    NOTE: If the package is a dependency of another package you
          will be notified of the dependent packages.  You should
          use the --force-removal-of-dependent-packages option to
          also remove the dependent packages as well
    ***************************************************************
    ***************************************************************
    Stopping Bootlog daemon: bootlogd.
    
     _____                    _____           _         _
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|
    
    Arago Project http://arago-project.org k2hk-evm /dev/ttyS0
    
    Arago 2015.05 k2hk-evm /dev/ttyS0
    
    k2hk-evm login:
    
    

    I would like to repeat that don't mix match the u-boot and kernel/filesystem from different packages.There are some significant changes in ProcSDK which don't make them work seamlessly. If you can bring up TI EVM with released images, the same would apply to your board.

    addr_fdt=0x87000000

    addr_fs=0x82000000

    addr_kern=0x88000000

    addr_mon=0x0c5f0000

    addr_secdb_key=0xc000000

    addr_ubi=0x82000000

    addr_uboot=0x87000000

    args_all=setenv bootargs console=ttyS0,115200n8 rootwait=1

    args_net=setenv bootargs ${bootargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp

    args_ramfs=setenv bootargs ${bootargs} rdinit=/sbin/init rw root=/dev/ram0 initrd=0x802000000,9M

    args_ubi=setenv bootargs ${bootargs} rootfstype=ubifs root=ubi0:rootfs rootflags=sync rw ubi.mtd=2,2048

    args_uinitrd=setenv bootargs ${bootargs} rdinit=/sbin/init rw root=/dev/ram0

    baudrate=115200

    boot=net

    bootcmd=run init_${boot} get_fdt_${boot} get_mon_${boot} get_kern_${boot} run_mon run_kern

    bootdelay=3

    bootfile=uImage

    burn_ubi=nand erase.part ubifs; nand write ${addr_ubi} ubifs ${filesize}

    burn_uboot=sf probe; sf erase 0 0x100000; sf write ${addr_uboot} 0 ${filesize}

    ethact=K2HK_EMAC

    ethaddr=b4:99:4c:9f:7f:f9

    fdt_high=0xffffffff

    get_fdt_net=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}

    get_fdt_ramfs=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}

    get_fdt_ubi=ubifsload ${addr_fdt} ${name_fdt}

    get_fdt_uinitrd=dhcp ${addr_fdt} ${tftp_root}/${name_fdt}

    get_fs_ramfs=dhcp ${addr_fs} ${tftp_root}/${name_fs}

    get_fs_uinitrd=dhcp ${addr_fs} ${tftp_root}/${name_uinitrd}

    get_kern_net=dhcp ${addr_kern} ${tftp_root}/${name_kern}

    get_kern_ramfs=dhcp ${addr_kern} ${tftp_root}/${name_kern}

    get_kern_ubi=ubifsload ${addr_kern} ${name_kern}

    get_kern_uinitrd=dhcp ${addr_kern} ${tftp_root}/${name_kern}

    get_mon_net=dhcp ${addr_mon} ${tftp_root}/${name_mon}

    get_mon_ramfs=dhcp ${addr_mon} ${tftp_root}/${name_mon}

    get_mon_ubi=ubifsload ${addr_mon} ${name_mon}

    get_mon_uinitrd=dhcp ${addr_mon} ${tftp_root}/${name_mon}

    get_ubi_net=dhcp ${addr_ubi} ${tftp_root}/${name_ubi}

    get_uboot_net=dhcp ${addr_uboot} ${tftp_root}/${name_uboot}

    has_mdio=0

    init_net=run set_fs_none args_all args_net

    init_ramfs=run set_fs_none args_all args_ramfs get_fs_ramfs

    init_ubi=run set_fs_none args_all args_ubi; ubi part ubifs; ubifsmount boot;ubifsload ${addr_secdb_key} securedb.key.bin;

    init_uinitrd=run set_fs_uinitrd args_all args_uinitrd get_fs_uinitrd

    initrd_high=0xffffffff

    mem_lpae=1

    mem_reserve=512M

    mtdparts=mtdparts=davinci_nand.0:1024k(bootloader)ro,512k(params)ro,-(ubifs)

    name_fdt=uImage-k2hk-evm.dtb

    name_fs=arago-console-image-k2hk-evm.cpio.gz

    name_kern=uImage-keystone-evm.bin

    name_mon=skern-k2hk-evm.bin

    name_ubi=k2hk-evm-ubifs.ubi

    name_uboot=u-boot-spi-k2hk-evm.gph

    name_uinitrd=uinitrd.bin

    nfs_options=v3,tcp,rsize=4096,wsize=4096

    nfs_root=/nfs/k2h_fs

    no_post=1

    run_kern=bootm ${addr_kern} ${addr_uinitrd} ${addr_fdt}

    run_mon=mon_install ${addr_mon}

    serverip=158.218.109.254

    set_fs_none=setenv addr_uinitrd -

    set_fs_uinitrd=setenv addr_uinitrd ${addr_fs}

    stderr=serial

    stdin=serial

    stdout=serial

    tftp_root=mcs3147

     

     

  • Hello Rex,

    the reason I prefer CCS loading instead of TFTP is that the network is not yet working in our board because a strange PSC issue of the NetCP I told you before.

    Could you please provide me the environment variables you use for booting the 4.4 kernel from the Processor SDK release. I know I should see them in the u-boot code as well, but just to make sure I haven't forgotten / unnoticed something I would like to see a set of variables which really work.

    Also the boot log would be nice to see for comparing to ours.

    Today I spent whole day trying to mount the tisdk UBI fs image from the processor SDK release package, but it fails with both u-boot versions and with K2H EVM and with our K2L board. The MCSDK u-boot mounts all my self built UBi fs images, but not the tisdk UBI from the release package. To summarize the tried alternatives:

    u-boot / UBI combination "ubifsmount rootfs" in K2H EVM from TI "ubifsmount rootfs" in our K2L board
    MCSDK u-boot + MCSDK release package UBI image

    mounts OK

    mounts OK
    MCSDK u-boot + self built UBI image not tried mounts OK
    MCSDK u-boot + Processor SDK UBI image not tried error -22
    Processor SDK u-boot + Processor SDK UBI image error -22 error -22
    Processor SDK u-boot + MCSDK release package UBI image not tried error -22
    Processor SDK u-boot + self built UBI image not tried error -22

    I understand your concern about mixing SW components from different releases and I would also avoid such, if I could. But as you can see from the table above, for some reason I cannot use the SDK u-boot nor the prebuilt SDK UBI image. The u-boot just refuses to mount all kind of images.

    Maybe some environment variable is missing or wrong. That's why I ask you to show your set of them used with the Processor SDK u-boot + UBI. From what I understand, it is the only possible source of problem unless I have completely messed up the u-boot when fixing the NAND 4k/2k issue in it for our board, but I don't believe I have.

    Best regards,

    Ari

  • Hi, Ari,

    You have a TI EVM and can easily get the setting by upgrading the EVM to the Proc SDK release. It will also be beneficial to you if you do it yourself. Always issue "env default -f -a" to reset the u-boot environment variables after you perform an upgrade or downgrade.

    Rex

  • Hi Rex,

    I'm working in the same team as Ari but I'm responsible for the HW implementation. I've followed closely this conversation and so far we have not made any progress in taking the Linux in use.

    Here are a few questions:

    1. Are the currently available prebuilt images really working for K2H?
    We have tried the prebuilt images for K2H EVM but they don't work, fails with error 22 (Processor SDK u-boot). Can you try yourself and let us know if you succeed or not.

    2. Have you compiled and built the u-boot from the source codes and successfully run the u-boot?
    I would like to know if you have ever done this OR are you simply just using what others have compiled and built?

    This is now very urgent issue for us, we would need to get a step ahead. Like you see from Ari's previous mailing, the only combination that works is the MCSDK u-boot + MCSDK release package UBI image. Nothing else works 'as is', no matter which version we use.

    - Zeb
  • Hi, Zeb,

    1) yes, the prebuilt images work. Please see the attached logs in my previous post.

    2) Yes, in addition to the prebuilt images, I also built my own u-boot, kernel from release package. The EVM was able to boot from these newly built images without any issues.

    I mentioned many times to Ari that don't mix match the u-boot and kernel from different MCSDK and ProcSDK packages. Things changed quite a bit. The Kernel starting boot address, u-boot configuration method, firmware loading, etc. are  different in ProcSDK. My suggestion is to take prebuilt images from the same release and boot up on a TI EVM. Learn and understand how it works, then try to port them to your platform.  Keystone-2 platforms have been used by many companies and have been out for at least 3+ years. I have not heard any issues that the Keystone-2 platform does not boot from UBI.

    Rex

  • Hello Rex,
    the kernel loads the firmware now alright.

    Using the default environment settings after upgrading the u-boot and the UBI image finally did the trick as you suggested. Although I checked them many times, I just could not find anything wrong in them, and therefore I did not first believe it would do any good resetting them to the defaults.

    Thank you very much!

    Best regards,
    Ari