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.

PROCESSOR-SDK-AM65X: Loading through JTAG

Part Number: PROCESSOR-SDK-AM65X
Other Parts Discussed in Thread: PCF8575

What's the proper process of loading and debugging u-boot through CCS on AM65x? Is there an available script we can use to load our build files? We attempted to follow the directions here: https://training.ti.com/linux-board-porting-series-module-8-installing-sdk-and-building-kernel-debug-symbols?cu=399066 but the architecture and files have changed enough that many of the variables and load program/load memory instructions aren't enough to start the AM65x.

We've tried to do this through JTAG:

1. Connect to the M3, allow it to initialize and run
2. Connect to the R5 and initialize DDR4. Tell it to run
3. Load uboot-spl.bin in the r5 build to the location 0x41c00000 (CONFIG_SPL_TEXT_BASE), setting the program counter to 0x41c00000, pausing the program, then load program/run the full u-boot image. Program counter restarts and the microcontroller says it's running, but nothing seems to happen
4. So then we tried connect to the A53 and then load the a53 build uboot-spl.bin to 0x80080000 (A53 target CONFIG_SPL_TEXT_BASE), run. On UART, we will see that the SPL tries to load but cannot load the sysfw and stops there. We'll get a mailbox error and a few other errors. From there, we tried loading the u-boot image and running that just to see if anything would happen, but nothing happened as expected.

There's definitely something important we're missing. We never load sysfw.itb it seems, tiboot3.bin we skipped, and tispl.bin we don't know where to place. Is there a location these files should go in memory and in which processor?

And if there's a way to load the Linux kernel from JTAG once u-boot is up, that would be extremely helpful as well. 

Thanks

  • Hi,

    There are several steps being discussed here. I would like to propose falling back a bit.  If allowing the boot to occur as intended out of the SD card say for example is there anything coming out of the console if you don't use JTAG? 

    You mentioned skipping tiboot3.bin, this binary loads the sysfw.itb and sets up DDR etc. What is the reason for skipping using this image? You also listed some steps that I am not sure that are needed. For example the M3 step should not be needed but we need to understand what is leading you to think this step is necessary.

    Best Regards,

    Schuyler

  • Hello,

    As mentioned by Schuyler, I am wondering if you have tried booting from the SD card. If no output is observed on the serial terminal, it is a good indication that the code is stuck in the R5 stage. In order to debug the R5, please add the following line of code in the file "<u-boot_dir>/arch/arm/mach-k3/am6_init.c":

    void board_init_f(ulong dummy)
    {
    #if defined(CONFIG_K3_LOAD_SYSFW) || defined(CONFIG_K3_AM654_DDRSS)
    	struct udevice *dev;
    	int ret;
    #endif
    	/*
    	 * Cannot delay this further as there is a chance that
    	 * K3_BOOT_PARAM_TABLE_INDEX can be over written by SPL MALLOC section.
    	 */
    	store_boot_index_from_rom();
    
    	/* Make all control module registers accessible */
    	ctrl_mmr_unlock();
    
    +       asm("test: nop");
    +       asm("       nop");
    +       asm("  b test ");
    +       asm(" nop");
    +       asm(" nop");
    
    
    	setup_am654_navss_northbridge();

    After adding the above code, please compile Uboot and copy the required images on the SD card as mentioned in the following guide. Plug the SD card and boot the board. Once the board is powered on, please connect to the A53 core using CCS (Please make sure no GEL files are loaded). In CCS, load the symbol from the following location "<u-boot_build_dir>/r5/spl/u-boot-spl". At this point, the test should be stuck inside the loop we previously added. Changing the Program Counter will allows us break out of the loop and step through the R5 code.

    Lastly, I am assuming you are using a custom board and please share how the DDR is configured for the custom board (Please refer to the following EMIF tool guide).

    Regards,
    Krunal

  • Hi Krunal,

    Our main issue is that we aren't getting good data over the SD card, so we're looking for an alternate boot method. We can get the kernel to attempt to start, but it will kernel panic or freeze, so the SD card is an unreliable boot source. We also don't always make it out of u-boot before the system freezes. I'll give the test code a try.

    Schuyler,

    We're not sure where we should be loading tiboot3.bin to through load memory on CCS. It's not being skipped on the SD card side, but the gel files on CCS seem to do all the DDR configuration already, so we're not sure if we need to load it if we're going through JTAG.

    Thanks,

    Andrea

  • Hello Andrea,

    Please correct me if I am wrong but sometimes you are able to get to the Uboot prompt but Kernel crashes. I am wondering if you could please share the boot logs that way we could inspect it further. Initially, I was under the impression that you are not observing any output on the terminal. Compared to the AM65 EVM, please share the DDR differences in terms of the memory size.

    Regards,
    Krunal

  • Hi All, 

    I would like to synchronize all sides: 

    1. Initialization of DDR4 with GEL file is ok, all RAM tests are ok

    2. Booting from SD CARD :  u-boot runs , we see randomize kernel crashes, no known pattern observed. Out tests: 

    a.) We start u-boot from SD CARD, most of u-boot starts are ok

    b.) We start u-boot command line and we also connect to processor with JTAG in parallel 

    c.) We load kernel from SD-card to DDR with u-boot ( command line ) , but we do not start kernel 

    d.) we download kernel from DDR to file via JTAG

    Result:

    If we compare binary kernel file we are loading to DDR with u-boot and downloaded binary from DDR to file via JTAG we see byte erros

    Frequency of Byte errors is different with different SD cards in use. Slower SD card , less byte errors

    Second test:

    - Starting u-boot interrupting auto boot, connecting JTAG.  Loading kernel to DDR and downloading back form DDR, comparing, does not show any diff in files.

    Notes:

    We measured SD card data integrity and power , results are not so bad. But still we suspect that we have issue with SD card data integrity or controller , this is the reason we are looking for alternative methods. 

    We can go step by step, but to speed up: we use SD for debug only, for production we have eMMC on the board. We put way more attention in eMMC routing and signal integrity.

    Questions:

    What is best and fastest way to program eMMC with JTAG without using SD card?

    br,

    Ales 

     

  • 1. Initialization of DDR4 with GEL file is ok, all RAM tests are ok 

    If you could please share the name of the tests that were ran to verify the RAM.

     We start u-boot from SD CARD, most of u-boot starts are ok 

    I just wanted to confirm that you are able to get to the Uboot prompt without any problems. Please keep in mind that there are 3 stages in the bootloader: tiboot3.bin -> tispl.bin -> u-boot.img and here is what successful Uboot prompt looks like:

    U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)<---------------------tiboot3.bin
    SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
    Trying to boot from MMC2
    Starting ATF on ARM64 core...
    
    NOTICE:  BL31: v2.1(release):ti2019.01-rc2
    NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
    I/TC: 
    I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
    I/TC: Initialized
    
    U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)<---------------------tispl.bin
    Trying to boot from MMC2
    
    
    U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)<---------------------u-boot.img
    
    Model: Texas Instruments AM654 Base Board
    DRAM:  4 GiB
    MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
    Loading Environment from MMC... OK
    In:    serial
    Out:   serial
    Err:   serial
    Net:   
    Warning: cpsw_nuss@046000000 using MAC address from ROM
    eth0: cpsw_nuss@046000000, eth1: pruss2_eth
    Hit any key to stop autoboot:  0 
    => <---------------------u-boot prompt

    c.) We load kernel from SD-card to DDR with u-boot ( command line ) , but we do not start kernel 

    In order to verify the kernel image, please run the following commands in the Uboot prompt "run get_kern_mmc" and "crc32 0x80080000 <size of Image in hex>. Similarly, run the command "crc32 Image" on the host PC and compare the two values.

    Regards,
    Krunal

  • Yes we are aware of booting process and yes we are in u-boot prompt. 

    SD card is for debug purpose on our board we did not put too much attention to signal integrity. We confirmed the signals on SD card are marginal enough to expect errors.

    eMMC is routed with signal integrity in mind, so we need to program eMMC without working SD card interface.

    What would you suggest as easiest set up and what is tested on AM65 EVB:

    - USB boot mode

    -u-boot DFU 

    -JTAG programming of eMMC

    Br, 

    Ales

  • Hello Ales,

    Currently, we have four boot modes tested on the AM65 EVM (SD card, OSPI, eMMC, and UART). Here is a reference document: http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components_U-Boot.html#supported-boot-modes 

    Also, I am wondering if you have a network interface enabled on the board. If there is a network interface, we could initially boot from UART/SD and copy/flash the images over the network.

    Regards,
    Krunal

  • Hi Krunal,

    We have network interface ports, though none of them have been verified as working. We will give the TFTP a try.

    Thanks,

  • Hello Andrea,

    I will be closing the ticket but if you have any further questions on TFTP, please feel free to open the ticket.

    Regards,
    Krunal

  • Hi Krunal,

    We've made some progress with the tftp server and it seems like the board is making more progress booting than before. Our system is stopping at the same point every time after loading the tftp files. I have a log attached. Do you know what the AM65 is looking for to continue the boot process?

    Thanks,

    Andrea

    U-Boot 2018.01-g1b80d3b9f3 (Apr 06 2019 - 03:30:36 +0000)

    Model: Texas Instruments AM654 Base Board
    DRAM: 4 GiB
    MMC: sdhci@0: 0, sdhci@0: 1
    *** Warning - bad CRC, using default environment

    In: serial@2800000
    Out: serial@2800000
    Err: serial@2800000
    i2c_write: error waiting for data ACK (status=0x116)
    Reading on-board EEPROM at 0x50 failed -121
    Warning: fastboot.board_rev: unknown board revision
    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
    part_get_info_efi: *** ERROR: Invalid GPT ***
    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
    part_get_info_efi: *** ERROR: Invalid Backup GPT ***
    i2c_write: error waiting for data ACK (status=0x116)
    pcf8575_i2c_write_le16 i2c write failed to addr 38
    Net:
    Warning: cpsw_nuss@046000000 using MAC address from ROM
    eth0: cpsw_nuss@046000000
    Hit any key to stop autoboot: 0
    => setenv serverip 192.168.1.20
    => setenv nfs_root /home/lam/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS
    => setenv name_kern Image
    => setenv bootcmd 'run findfdt; run envboot; run setup_${kern_boot}; run init_${rootfs_boot}; run get_kern_${kern_boot}; run get_fdt_${kern_boot}; run run_kern'
    => setenv init_net 'run args_all args_net; setenv autoload no; dhcp'
    => setenv args_net 'setenv bootargs ${optargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp'
    => setenv get_kern_net 'tftp ${loadaddr} ${name_kern}'
    => setenv get_fdt_net 'tftp ${fdtaddr} ${name_fdt}'
    => setenv get_overlay_net 'fdt address ${fdtaddr};fdt resize 0x100000;for overlay in ${overlay_files};do;tftp ${overlayaddr} ${overlay};fdt apply ${overlayaddr}; done'
    => setenv nfs_options 'nolock,v3,tcp,rsize=4096,wsize=4096'
    => setenv setup_mmc ''
    => setenv setup_net 'setenv autoload no; dhcp'
    => setenv kern_boot net
    => setenv rootfs_boot net
    => setenv name_fdt k3-am654-base-board.dtb
    => setenv serial# 0000000000000165
    => setenv bootargs 'earlycon=ns16550a,mmio32,0x02800000 rootfstype=nfp'
    => setenv ethact cpsw_nuss@046000000
    => setenv ipaddr 192.168.1.2
    => setenv name_overlays k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo
    => setenv fdtaddr 82000000
    => setenv fdtfile k3-am654-base-board.dtb
    => setenv loglevel 8
    => setenv args_all setenv optargs earlycon=ns16550a,mmio32,0x02800000
    => run bootcmd
    switch to partitions #0, OK
    mmc1 is current device
    SD/MMC found on device 1
    ** Unable to read file boot.scr **
    1490 bytes read in 13 ms (111.3 KiB/s)
    Loaded env from uEnv.txt
    Importing environment from mmc1 ...
    Running uenvcmd ...
    1 bytes read in 8 ms (0 Bytes/s)
    Already setup.
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    DHCP client bound to address 192.168.1.4 (1008 ms)
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 192.168.1.4 (4 ms)
    link up on port 1, speed 1000, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.1.20; our IP address is 192.168.1.4
    Filename 'Image'.
    Load address: 0x80080000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ################
    2.6 MiB/s
    done
    Bytes transferred = 12632072 (c0c008 hex)
    link up on port 1, speed 1000, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.1.20; our IP address is 192.168.1.4
    Filename 'k3-am654-base-board.dtb'.
    Load address: 0x82000000
    Loading: #####
    1.8 MiB/s
    done
    Bytes transferred = 71809 (11881 hex)
    ## Flattened Device Tree blob at 82000000
    Booting using the fdt blob at 0x82000000
    Loading Device Tree to 00000000fdeae000, end 00000000fdec2880 ... OK

    Starting kernel ...

    [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
    [ 0.000000] Linux version 4.19.38-g4dae378bbe (oe-user@oe-host) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 SMP PREEMPT Sun Jul 7 03:42:51 UTC 2019
    [ 0.000000] Machine model: Texas Instruments AM654 Base Board
    [ 0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
    [ 0.000000] bootconsole [ns16550a0] enabled
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009b000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@9b000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009b100000, size 15 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-memory@9b100000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009c000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@9c000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009c100000, size 7 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-memory@9c100000, compatible id shared-dma-pool
    [ 0.000000] cma: Reserved 512 MiB at 0x00000000c0000000
    [ 0.000000] psci: probing for conduit method from DT.
    [ 0.000000] psci: PSCIv1.1 detected in firmware.
    [ 0.000000] psci: Using standard PSCI v0.2 function IDs
    [ 0.000000] psci: Trusted OS migration not required
    [ 0.000000] psci: SMC Calling Convention v1.1
    [ 0.000000] random: get_random_bytes called from start_kernel+0x94/0x3e4 with crng_init=0
    [ 0.000000] percpu: Embedded 2 pages/cpu s48536 r8192 d74344 u131072
    [ 0.000000] Detected VIPT I-cache on CPU0
    [ 0.000000] CPU features: enabling workaround for ARM erratum 845719
    [ 0.000000] Speculative Store Bypass Disable mitigation not required
    [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
    [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 64704
    [ 0.000000] Kernel command line: earlycon=ns16550a,mmio32,0x02800000 rootfstype=nfs root=/dev/nfs rw nfsroot=192.168.1.20:/home/lam/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS,nolock,v3,tcp,rsize=4096,wsize=4096 ip=dhcp
    [ 0.000000] Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes)
    [ 0.000000] Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes)
    [ 0.000000] software IO TLB: mapped [mem 0xf9ea0000-0xfdea0000] (64MB)
    [ 0.000000] Memory: 3529856K/4145152K available (8062K kernel code, 752K rwdata, 2880K rodata, 576K init, 614K bss, 91008K reserved, 524288K cma-reserved)
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [ 0.000000] rcu: Preemptible hierarchical RCU implementation.
    [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
    [ 0.000000] Tasks RCU enabled.
    [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
    [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
    [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode
    [ 0.000000] GICv3: Distributor has no Range Selector support
    [ 0.000000] GICv3: no VLPI support, no direct LPI support
    [ 0.000000] ITS [mem 0x01820000-0x0182ffff]
    [ 0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
    [ 0.000000] ITS@0x0000000001820000: allocated 1048576 Devices @8c0800000 (flat, esz 8, psz 64K, shr 0)
    [ 0.000000] ITS: using cache flushing for cmd queue
    [ 0.000000] GIC: using LPI property table @0x00000008c00c0000
    [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001880000
    [ 0.000000] CPU0: using LPI pending table @0x00000008c00d0000
    [ 0.000000] GIC: using cache flushing for LPI property table
    [ 0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
    [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
    [ 0.000006] sched_clock: 56 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
    [ 0.008685] Console: colour dummy device 80x25
    [ 0.013239] console [tty0] enabled
    [ 0.016722] bootconsole [ns16550a0] disabled

  • Hello Andrea,

    In the Kernel command line ([ 0.000000] Kernel command line: earlycon=ns16550a,mmio32,0x02800000 rootfstype=nfs root=/dev/nfs rw nfsroot=192.168.1.20:/home/lam/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS,nolock,v3,tcp,rsize=4096,wsize=4096 ip=dhcp), it seems like you are missing the following information: "console=ttyS2,115200n8"

    Regards,
    Krunal

  • Hi Krunal,

    We set that variable and it is still stopping at the same location with the same boot log.

    Thanks,
    Andrea

  • Hello Andrea,

    After adding the console commands, could you please share the boot logs again?

    Regards,
    Krunal

  • Hi Krunal,

    Here is the console boot log. We also ran a diff on the u-boot once it relocated into DDR4 to check if it's the same as the one on the SD card and that looks to be the same except for a byte at the start. We're digging into the rest of the setup for the time being.

    Thanks
    Andrea

    switch to partitions #0, OK
    mmc1 is current device
    SD/MMC found on device 1
    ** Unable to read file boot.scr **
    1490 bytes read in 13 ms (111.3 KiB/s)
    Loaded env from uEnv.txt
    Importing environment from mmc1 ...
    Running uenvcmd ...
    1 bytes read in 8 ms (0 Bytes/s)
    Already setup.
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 192.168.1.4 (4 ms)
    link up on port 1, speed 1000, full duplex
    BOOTP broadcast 1
    DHCP client bound to address 192.168.1.4 (4 ms)
    link up on port 1, speed 1000, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.1.20; our IP address is 192.168.1.4
    Filename 'Image'.
    Load address: 0x80080000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ################
    2.6 MiB/s
    done
    Bytes transferred = 12632072 (c0c008 hex)
    link up on port 1, speed 1000, full duplex
    Using cpsw_nuss@046000000 device
    TFTP from server 192.168.1.20; our IP address is 192.168.1.4
    Filename 'k3-am654-base-board.dtb'.
    Load address: 0x82000000
    Loading: #####
    1.7 MiB/s
    done
    Bytes transferred = 71809 (11881 hex)
    ## Flattened Device Tree blob at 82000000
    Booting using the fdt blob at 0x82000000
    Loading Device Tree to 00000000fdeae000, end 00000000fdec2880 ... OK

    Starting kernel ...

    [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
    [ 0.000000] Linux version 4.19.38-g4dae378bbe (oe-user@oe-host) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 SMP PREEMPT Sun Jul 7 03:42:51 UTC 2019
    [ 0.000000] Machine model: Texas Instruments AM654 Base Board
    [ 0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
    [ 0.000000] bootconsole [ns16550a0] enabled
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009b000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@9b000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009b100000, size 15 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-memory@9b100000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009c000000, size 1 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@9c000000, compatible id shared-dma-pool
    [ 0.000000] Reserved memory: created DMA memory pool at 0x000000009c100000, size 7 MiB
    [ 0.000000] OF: reserved mem: initialized node r5f-memory@9c100000, compatible id shared-dma-pool
    [ 0.000000] cma: Reserved 512 MiB at 0x00000000c0000000
    [ 0.000000] psci: probing for conduit method from DT.
    [ 0.000000] psci: PSCIv1.1 detected in firmware.
    [ 0.000000] psci: Using standard PSCI v0.2 function IDs
    [ 0.000000] psci: Trusted OS migration not required
    [ 0.000000] psci: SMC Calling Convention v1.1
    [ 0.000000] random: get_random_bytes called from start_kernel+0x94/0x3e4 with crng_init=0
    [ 0.000000] percpu: Embedded 2 pages/cpu s48536 r8192 d74344 u131072
    [ 0.000000] Detected VIPT I-cache on CPU0
    [ 0.000000] CPU features: enabling workaround for ARM erratum 845719
    [ 0.000000] Speculative Store Bypass Disable mitigation not required
    [ 0.000000] CPU features: detected: Kernel page table isolation (KPTI)
    [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 64704
    [ 0.000000] Kernel command line: earlycon=ns16550a,mmio32,0x02800000 rootfstype=nfs root=/dev/nfs rw nfsroot=192.168.1.20:/home/lam/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS,nolock,v3,tcp,rsize=4096,wsize=4096 ip=dhcp
    [ 0.000000] Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes)
    [ 0.000000] Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes)
    [ 0.000000] software IO TLB: mapped [mem 0xf9ea0000-0xfdea0000] (64MB)
    [ 0.000000] Memory: 3529856K/4145152K available (8062K kernel code, 752K rwdata, 2880K rodata, 576K init, 614K bss, 91008K reserved, 524288K cma-reserved)
    [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    [ 0.000000] rcu: Preemptible hierarchical RCU implementation.
    [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
    [ 0.000000] Tasks RCU enabled.
    [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
    [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
    [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode
    [ 0.000000] GICv3: Distributor has no Range Selector support
    [ 0.000000] GICv3: no VLPI support, no direct LPI support
    [ 0.000000] ITS [mem 0x01820000-0x0182ffff]
    [ 0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
    [ 0.000000] ITS@0x0000000001820000: allocated 1048576 Devices @8c0800000 (flat, esz 8, psz 64K, shr 0)
    [ 0.000000] ITS: using cache flushing for cmd queue
    [ 0.000000] GIC: using LPI property table @0x00000008c00c0000
    [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001880000
    [ 0.000000] CPU0: using LPI pending table @0x00000008c00d0000
    [ 0.000000] GIC: using cache flushing for LPI property table
    [ 0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
    [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns
    [ 0.000005] sched_clock: 56 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns
    [ 0.008684] Console: colour dummy device 80x25
    [ 0.013240] console [tty0] enabled
    [ 0.016722] bootconsole [ns16550a0] disabled

    Here are also the environment variables from u-boot

    arch=arm
    args_all=setenv optargs earlycon=ns16550a,mmio32,0x02800000
    args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}
    args_net=setenv bootargs ${optargs} rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp
    args_ubi=setenv bootargs ${console} ${optargs} rootfstype=ubifs root=ubi0:rootfs rw ubi.mtd=ospi.rootfs
    baudrate=115200
    board=am65x
    board_name=am65x
    board_rev=E3
    board_serial=0165
    board_software_revision=01
    boot=mmc
    bootargs=earlycon=ns16550a,mmio32,0x02800000 rootfstype=nfp console=ttyS2,115200
    bootcmd=run findfdt; run envboot; run setup_${kern_boot}; run init_${rootfs_boot}; run get_kern_${kern_boot}; run get_fdt_${kern_boot}; run run_kern
    bootdelay=2
    bootdir=/boot
    bootenvfile=uEnv.txt
    bootpart=1:2
    bootscript=echo Running bootscript from mmc${mmcdev} ...; source ${loadaddr}
    check_android=setenv mmcdev 0; env delete boot_start; part start mmc ${mmcdev} boot boot_start; if test "$boot_start" = ""; then env set is_android 0; else env set is_android 1; fi; env delete boot_start
    check_dofastboot=if test "${dofastboot}" -eq 1; then echo Boot fastboot requested, resetting dofastboot ...;setenv dofastboot 0; env save; echo Booting into fastboot ...; fastboot 0; fi
    console=ttyS2,115200n8
    cpu=armv8
    dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1;rootfs part 0 1 mmcpart 0;tiboot3.bin.raw raw 0x0 0x400 mmcpart 1;tispl.bin.raw raw 0x400 0x1000 mmcpart 1;u-boot.img.raw raw 0x1400 0x2000 mmcpart 1;u-env.raw raw 0x3400 0x100 mmcpart 1;sysfw.itb.raw raw 0x3600 0x800 mmcpart 1
    dfu_alt_info_mmc=boot part 1 1;rootfs part 1 2;tiboot3.bin fat 1 1;tispl.bin fat 1 1;u-boot.img fat 1 1;uEnv.txt fat 1 1;sysfw.itb fat 1 1
    dfu_alt_info_ospi=tiboot3.bin raw 0x0 0x080000;tispl.bin raw 0x080000 0x200000;u-boot.img raw 0x280000 0x400000;u-boot-env raw 0x680000 0x020000;sysfw.itb raw 0x6c0000 0x100000;rootfs raw 0x800000 0x3800000
    dfu_bufsiz=0x20000
    emmc_android_boot=echo Trying to boot Android from eMMC ...; setenv fit_loadaddr 0x87000000; setenv loadaddr ${fit_loadaddr}; setenv eval_bootargs setenv bootargs $bootargs; run eval_bootargs; setenv mmcdev 0; mmc dev $mmcdev; mmc rescan; part start mmc ${mmcdev} boot boot_start; part size mmc ${mmcdev} boot boot_size; mmc read ${fit_loadaddr} ${boot_start} ${boot_size}; for overlay in $overlay_files;do;setenv overlaystring ${overlaystring}'#'${overlay};done;bootm ${fit_loadaddr}#${fdtfile}${overlaystring}
    envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootscript; then run bootscript;else if run loadbootenv; then echo Loaded env from ${bootenvfile};run importbootenv;fi;if test -n $uenvcmd; then echo Running uenvcmd ...;run uenvcmd;fi;fi;fi;
    ethact=cpsw_nuss@046000000
    ethaddr=4c:24:98:0d:c8:0b
    fastboot.cpu=AM654
    fastboot.secure=GP
    fdtaddr=82000000
    fdtcontroladdr=fdec4d18
    fdtfile=k3-am654-base-board.dtb
    findfdt=setenv name_fdt k3-am654-base-board.dtb;setenv fdtfile ${name_fdt};setenv overlay_files ${name_overlays}
    finduuid=part uuid mmc ${bootpart} uuid
    get_fdt_mmc=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${name_fdt}
    get_fdt_net=tftp ${fdtaddr} ${name_fdt}
    get_fdt_ubi=ubifsload ${fdtaddr} ${bootdir}/${name_fdt}
    get_kern_mmc=load mmc ${bootpart} ${loadaddr} ${bootdir}/${name_kern}
    get_kern_net=tftp ${loadaddr} ${name_kern}
    get_kern_ubi=ubifsload ${loadaddr} ${bootdir}/${name_kern}
    get_overlay_mmc=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in $overlay_files;do;load mmc ${bootpart} ${overlayaddr} ${bootdir}/${overlay};fdt apply ${overlayaddr};done;
    get_overlay_net=fdt address ${fdtaddr};fdt resize 0x100000;for overlay in ${overlay_files};do;tftp ${overlayaddr} ${overlay};fdt apply ${overlayaddr}; done
    importbootenv=echo Importing environment from mmc${mmcdev} ...; env import -t ${loadaddr} ${filesize}
    init_mmc=run args_all args_mmc
    init_net=run args_all args_net; setenv autoload no; dhcp
    init_ubi=run args_all args_ubi; sf probe; ubi part ospi.rootfs; ubifsmount ubi:rootfs;
    ipaddr=192.168.1.2
    kern_boot=net
    loadaddr=0x80080000
    loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
    loadbootscript=load mmc ${mmcdev} ${loadaddr} boot.scr
    loadfdt=load ${devtype} ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile}
    loadimage=load ${devtype} ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
    loglevel=8
    mmcboot=mmc dev ${mmcdev}; setenv devnum ${mmcdev}; setenv devtype mmc; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadimage; then if test ${boot_fit} -eq 1; then run loadfit; else run mmcloados;fi;fi;fi;
    mmcdev=1
    mmcloados=run args_mmc; if test ${boot_fdt} = yes || test ${boot_fdt} = try; then if run loadfdt; then bootz ${loadaddr} - ${fdtaddr}; else if test ${boot_fdt} = try; then bootz; else echo WARN: Cannot load the DT; fi; fi; else bootz; fi;
    mmcrootfstype=ext4 rootwait
    mtdids=nor0=47040000.ospi.0
    mtdparts=mtdparts=47040000.ospi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128k(ospi.env.backup),1m(ospi.sysfw),-@8m(ospi.rootfs)
    name_fdt=k3-am654-base-board.dtb
    name_kern=Image
    name_overlays=k3-am654-idk.dtbo k3-am654-pcie-usb2.dtbo
    nfs_options=nolock,v3,tcp,rsize=4096,wsize=4096
    nfs_root=/home/lam/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS
    overlayaddr=0x83000000
    partitions=uuid_disk=${uuid_gpt_disk};name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}
    partitions_android=uuid_disk=${uuid_gpt_disk};name=bootloader,start=5M,size=8M,uuid=${uuid_gpt_bootloader};name=tiboot3,start=4M,size=1M,uuid=${uuid_gpt_tiboot3};name=boot,start=13M,size=40M,uuid=${uuid_gpt_boot};name=vendor,size=512M,uuid=${uuid_gpt_vendor};name=system,size=2048M,uuid=${uuid_gpt_system};name=userdata,size=-,uuid=${uuid_gpt_userdata}
    rd_spec=-
    rootfs_boot=net
    run_kern=booti ${loadaddr} ${rd_spec} ${fdtaddr}
    serial#=0000000000000165
    serverip=192.168.1.20
    setup_mmc=
    setup_net=setenv autoload no; dhcp
    soc=k3
    stderr=serial@2800000
    stdin=serial@2800000
    stdout=serial@2800000
    vendor=ti

  • Hi Andrea,

    As an experiment, could you please remove all the custom Uboot environment variables using the following command: "env default -f -a;saveenv;reset". Next, please use the following commands to setup NFS boot:

    => setenv serverip 192.168.0.1
    => setenv rootpath /home/psdk_linux/am65xx/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS
    => setenv bootfile Image
    => setenv ip_method dhcp
    => setenv nfs_bootfile 'nfs ${loadaddr} ${serverip}:${rootpath}${bootdir}/${name_kern}'
    => setenv nfs_fdtfile 'nfs ${fdtaddr} ${serverip}:${rootpath}${bootdir}/${fdtfile}'
    => setenv nfsargs 'setenv bootargs console=${console} root=/dev/nfs nfsroot=${serverip}:${rootpath},v3 rw ip=dhcp' 
    => setenv bootcmd 'setenv autoload no; dhcp; run nfs_bootfile; run findfdt; run nfs_fdtfile; run nfsargs; booti ${loadaddr} - ${fdtaddr}'

    Regards,
    Krunal

  • With regards to the Uboot environment variables, you have the following command: "init_net=run args_all args_net; setenv autoload no; dhcp". The previous command, first runs "args_all" and sets the optargs to "earlycon=ns16550a,mmio32,0x02800000". Next, it will run the command "args_net" and set the bootargs to "earlycon=ns16550a,mmio32,0x02800000 + rootfstype=nfs root=/dev/nfs rw nfsroot=${serverip}:${nfs_root},${nfs_options} ip=dhcp". 

    As you can see, you are basically overwriting the bootargs command you defined in the following variable: "bootargs=earlycon=ns16550a,mmio32,0x02800000 rootfstype=nfp (<--should be equal to nfs) console=ttyS2,115200".

    Regards,
    Krunal

  • Thanks for looking through the logs. We tried both options. With the nfp fix, it still resulted in the same behavior of freezing at the 'bootconsole [disabled]' message.. With the default environment, we saw that it downloaded the filesystem off of the targetNFS location but it would freeze right at the starting kernel message.

    Thanks,
    Andrea

  • Hi Andrea,

    Could you please share the boot logs?

    Regards,
    Krunal

  • Hi Krunal,

    Here is the log from setting the variables to default and then setting the variables from the previous message. It looked as if it downloaded a lot more data than our previous tests, but it froze very soon after and didn't give us a lot of information to work with.

    Thanks,
    Andrea

     

    U-Boot SPL 2018.01-g0f5ca39299 (Apr 06 2019 - 03:36:26)

    SYSFW ABI: 2.5 (firmware rev 0x0013 '19.2.0-v2019.02 (Curious Crow)')

    i2c_write: error waiting for data ACK (status=0x116)

    Reading on-board EEPROM at 0x50 failed -121

    Trying to boot from MMC2

    Starting ATF on ARM64 core...

     

    NOTICE:  BL31: v1.5(release):ti2018.04-rc1-dirty

    NOTICE:  BL31: Built : 02:50:56, Apr  6 2019

    I/TC:

    I/TC: OP-TEE version: 3.2.0-81-g48952f9-dev #1 Sat Apr  6 03:30:27 UTC 2019 aarch64

    I/TC: Initialized

     

    U-Boot SPL 2018.01-g1b80d3b9f3 (Apr 06 2019 - 03:30:36)

    i2c_write: error waiting for data ACK (status=0x116)

    Reading on-board EEPROM at 0x50 failed -121

    Trying to boot from MMC2

     

     

    U-Boot 2018.01-g1b80d3b9f3 (Apr 06 2019 - 03:30:36 +0000)

     

    Model: Texas Instruments AM654 Base Board

    DRAM:  4 GiB

    MMC:   sdhci@0: 0, sdhci@0: 1

    In:    serial@2800000

    Out:   serial@2800000

    Err:   serial@2800000

    i2c_write: error waiting for data ACK (status=0x116)

    Reading on-board EEPROM at 0x50 failed -121

    Warning: fastboot.board_rev: unknown board revision

    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645

    part_get_info_efi: *** ERROR: Invalid GPT ***

    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645

    part_get_info_efi: *** ERROR: Invalid Backup GPT ***

    i2c_write: error waiting for data ACK (status=0x116)

    pcf8575_i2c_write_le16 i2c write failed to addr 38

    Net:

    Warning: cpsw_nuss@046000000 using MAC address from ROM

    eth0: cpsw_nuss@046000000

    Hit any key to stop autoboot:  0

    => run bootcmd

    link up on port 1, speed 1000, full duplex

    BOOTP broadcast 1

    BOOTP broadcast 2

    BOOTP broadcast 3

    DHCP client bound to address 192.168.1.4 (1008 ms)

    link up on port 1, speed 1000, full duplex

    #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             ###############################################################

    done

    Bytes transferred = 12632072 (c0c008 hex)

    link up on port 1, speed 1000, full duplex

    ###############

    done

    Bytes transferred = 71809 (11881 hex)

    ## Flattened Device Tree blob at 82000000

       Booting using the fdt blob at 0x82000000

       Loading Device Tree to 00000000fdeae000, end 00000000fdec2880 ... OK

     

    Starting kernel ...

  • Please share the latest boot logs where you are stuck at the following message "[ 0.013239] console [tty0] enabled [ 0.016722] bootconsole [ns16550a0] disabled. I just wanted to confirm that the Kernel command line has the console information.

    Regards,
    Krunal

  • Hello Andrea,

    I am wondering if you have any updates.

    Regards,
    Krunal

  • Hi Krunal,

    Not many updates at the moment. We're digging into the device tree files at the moment since we don't have a lot of the hardware the evm board supports and we're also running into kernel panics. Here's one log we had yesterday, but the panics aren't consistent. Oftentimes we're getting a bad page state in process swap errors. 

    Thanks,
    Andrea

    U-Boot 2018.01-g1b80d3b9f3 (Apr 06 2019 - 03:30:36 +0000)

     

    Model: Texas Instruments AM654 Base Board

    DRAM:  4 GiB

    MMC:   sdhci@0: 0, sdhci@0: 1

    In:    serial@2800000

    Out:   serial@2800000

    Err:   serial@2800000

    i2c_write: error waiting for data ACK (status=0x116)

    Reading on-board EEPROM at 0x50 failed -121

    Warning: fastboot.board_rev: unknown board revision

    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645

    part_get_info_efi: *** ERROR: Invalid GPT ***

    GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645

    part_get_info_efi: *** ERROR: Invalid Backup GPT ***

    i2c_write: error waiting for data ACK (status=0x116)

    pcf8575_i2c_write_le16 i2c write failed to addr 38

    Net:   eth0: cpsw_nuss@046000000

    Hit any key to stop autoboot:  0

    syntax error

    cpsw_nuss@046000000 Waiting for PHY auto negotiation to complete... done

    link up on port 1, speed 1000, full duplex

    BOOTP broadcast 1

    BOOTP broadcast 2

    DHCP client bound to address 192.168.1.2 (257 ms)

    link up on port 1, speed 1000, full duplex

    BOOTP broadcast 1

    DHCP client bound to address 192.168.1.2 (4 ms)

    link up on port 1, speed 1000, full duplex

    Using cpsw_nuss@046000000 device

    TFTP from server 192.168.1.20; our IP address is 192.168.1.2

    Filename 'Image'.

    Load address: 0x80080000

    Loading: #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             ################

             2.6 MiB/s

    done

    Bytes transferred = 12632072 (c0c008 hex)

    link up on port 1, speed 1000, full duplex

    Using cpsw_nuss@046000000 device

    TFTP from server 192.168.1.20; our IP address is 192.168.1.2

    Filename 'k3-am654-base-board.dtb'.

    Load address: 0x82000000

    Loading: #####

             1.7 MiB/s

    done

    Bytes transferred = 71809 (11881 hex)

    link up on port 1, speed 1000, full duplex

    Using cpsw_nuss@046000000 device

    TFTP from server 192.168.1.20; our IP address is 192.168.1.2

    Filename 'k3-am654-idk.dtbo'.

    Load address: 0x83000000

    Loading: #

             1.1 MiB/s

    done

    Bytes transferred = 11402 (2c8a hex)

    link up on port 1, speed 1000, full duplex

    Using cpsw_nuss@046000000 device

    TFTP from server 192.168.1.20; our IP address is 192.168.1.2

    Filename 'k3-am654-pcie-usb2.dtbo'.

    Load address: 0x83000000

    Loading: #

             338.9 KiB/s

    done

    Bytes transferred = 2084 (824 hex)

    ## Flattened Device Tree blob at 82000000

       Booting using the fdt blob at 0x82000000

       reserving fdt memory region: addr=82000000 size=112000

       Loading Device Tree to 00000000fddae000, end 00000000fdec2fff ... OK

     

    Starting kernel ...

     

    [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]

    [    0.000000] Linux version 4.19.38-g4dae378bbe (oe-user@oe-host) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 SMP PREEMPT Sun Jul 7 03:42:51 UTC 2019

    [    0.000000] Machine model: Texas Instruments AM654 Base Board

    [    0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')

    [    0.000000] bootconsole [ns16550a0] enabled

    [    0.000000] Reserved memory: created DMA memory pool at 0x000000009b000000, size 1 MiB

    [    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9b000000, compatible id shared-dma-pool

    [    0.000000] Reserved memory: created DMA memory pool at 0x000000009b100000, size 15 MiB

    [    0.000000] OF: reserved mem: initialized node r5f-memory@9b100000, compatible id shared-dma-pool

    [    0.000000] Reserved memory: created DMA memory pool at 0x000000009c000000, size 1 MiB

    [    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9c000000, compatible id shared-dma-pool

    [    0.000000] Reserved memory: created DMA memory pool at 0x000000009c100000, size 7 MiB

    [    0.000000] OF: reserved mem: initialized node r5f-memory@9c100000, compatible id shared-dma-pool

    [    0.000000] cma: Reserved 512 MiB at 0x00000000c0000000

    [    0.000000] psci: probing for conduit method from DT.

    [    0.000000] psci: PSCIv1.1 detected in firmware.

    [    0.000000] psci: Using standard PSCI v0.2 function IDs

    [    0.000000] psci: Trusted OS migration not required

    [    0.000000] psci: SMC Calling Convention v1.1

    [    0.000000] random: get_random_bytes called from start_kernel+0x94/0x3e4 with crng_init=0

    [    0.000000] percpu: Embedded 2 pages/cpu s48536 r8192 d74344 u131072

    [    0.000000] Detected VIPT I-cache on CPU0

    [    0.000000] CPU features: enabling workaround for ARM erratum 845719

    [    0.000000] Speculative Store Bypass Disable mitigation not required

    [    0.000000] CPU features: detected: Kernel page table isolation (KPTI)

    [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 64704

    [    0.000000] Kernel command line: earlycon=ns16550a,mmio32,0x02800000 mtdparts=47040000.ospi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),128k(ospi.env),128k(ospi.env.backup),1m(ospi.sysfw),-@8m(ospi.rootfs) console=ttyS2,115200 rootfstype=nfs root=/dev/nfs rw nfsroot=192.168.1.20:/home/lam/ti-processor-sdk-linux-am65xx-evm-06.00.00.07/targetNFS,nolock,v3,tcp,rsize=4096,wsize=4096 ip=dhcp

    [    0.000000] Dentry cache hash table entries: 524288 (order: 6, 4194304 bytes)

    [    0.000000] Inode-cache hash table entries: 262144 (order: 5, 2097152 bytes)

    [    0.000000] software IO TLB: mapped [mem 0xf9da0000-0xfdda0000] (64MB)

    [    0.000000] Memory: 3528640K/4145152K available (8062K kernel code, 752K rwdata, 2880K rodata, 576K init, 614K bss, 92224K reserved, 524288K cma-reserved)

    [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

    [    0.000000] rcu: Preemptible hierarchical RCU implementation.

    [    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.

    [    0.000000]  Tasks RCU enabled.

    [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4

    [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0

    [    0.000000] GICv3: GIC: Using split EOI/Deactivate mode

    [    0.000000] GICv3: Distributor has no Range Selector support

    [    0.000000] GICv3: no VLPI support, no direct LPI support

    [    0.000000] ITS [mem 0x01820000-0x0182ffff]

    [    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS

    [    0.000000] ITS@0x0000000001820000: allocated 1048576 Devices @8c0800000 (flat, esz 8, psz 64K, shr 0)

    [    0.000000] ITS: using cache flushing for cmd queue

    [    0.000000] GIC: using LPI property table @0x00000008c00c0000

    [    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001880000

    [    0.000000] CPU0: using LPI pending table @0x00000008c00d0000

    [    0.000000] GIC: using cache flushing for LPI property table

    [    0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).

    [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns: 440795210634 ns

    [    0.000006] sched_clock: 56 bits at 200MHz, resolution 5ns, wraps every 4398046511102ns

    [    0.008706] Console: colour dummy device 80x25

    [    0.013312] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)

    [    0.024001] pid_max: default: 32768 minimum: 301

    [    0.028831] Security Framework initialized

    [    0.033092] Mount-cache hash table entries: 8192 (order: 0, 65536 bytes)

    [    0.039975] Mountpoint-cache hash table entries: 8192 (order: 0, 65536 bytes)

    [    0.071420] ASID allocator initialised with 32768 entries

    [    0.084989] rcu: Hierarchical SRCU implementation.

    [    0.098079] Platform MSI: gic-its@18200000 domain created

    [    0.103915] PCI/MSI: /interconnect@100000/interrupt-controller@1800000/gic-its@18200000 domain created

    [    0.121485] smp: Bringing up secondary CPUs ...

    [    0.158656] Detected VIPT I-cache on CPU1

    [    0.158695] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000

    [    0.158745] CPU1: using LPI pending table @0x00000008c0330000

    [    0.158792] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]

    [    0.220320] Detected VIPT I-cache on CPU2

    [    0.220363] GICv3: CPU2: found redistributor 100 region 0:0x00000000018c0000

    [    0.220416] CPU2: using LPI pending table @0x00000008c03c0000

    [    0.220465] CPU2: Booted secondary processor 0x0000000100 [0x410fd034]

    [    0.252759] Detected VIPT I-cache on CPU3

    [    0.252786] GICv3: CPU3: found redistributor 101 region 0:0x00000000018e0000

    [    0.252834] CPU3: using LPI pending table @0x00000008c0450000

    [    0.252869] CPU3: Booted secondary processor 0x0000000101 [0x410fd034]

    [    0.253014] smp: Brought up 1 node, 4 CPUs

    [    0.328649] SMP: Total of 4 processors activated.

    [    0.333471] CPU features: detected: GIC system register CPU interface

    [    0.340081] CPU features: detected: 32-bit EL0 Support

    [    0.367865] CPU: All CPU(s) started at EL2

    [    0.372085] alternatives: patching kernel code

    [    0.378093] devtmpfs: initialized

    [    0.393322] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns

    [    0.403330] futex hash table entries: 1024 (order: 0, 65536 bytes)

    [    0.411188] pinctrl core: initialized pinctrl subsystem

    [    0.417208] NET: Registered protocol family 16

    [    0.423065] vdso: 2 pages (1 code @ (____ptrval____), 1 data @ (____ptrval____))

    [    0.430656] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.

    [    0.444388] DMA: preallocated 256 KiB pool for atomic allocations

    [    0.453298] davinci_gpio 42110000.wkup_gpio0: IRQ not populated, err = -517

    [    0.467654] davinci_gpio 600000.main_gpio0: IRQ not populated, err = -517

    [    0.474858] davinci_gpio 601000.main_gpio1: IRQ not populated, err = -517

    [    0.493018] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages

    [    0.499902] HugeTLB registered 512 MiB page size, pre-allocated 0 pages

    [    0.508717] cryptd: max_cpu_qlen set to 1000

    [    0.514991] media: Linux media interface: v0.10

    [    0.519709] videodev: Linux video capture interface: v2.00

    [    0.525370] pps_core: LinuxPPS API ver. 1 registered

    [    0.530454] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>

    [    0.539814] PTP clock support registered

    [    0.543855] EDAC MC: Ver: 3.0.0

    [    0.548358] Advanced Linux Sound Architecture Driver Initialized.

    [    0.555579] clocksource: Switched to clocksource arch_sys_counter

    [    0.562065] VFS: Disk quotas dquot_6.6.0

    [    0.566188] VFS: Dquot-cache hash table entries: 8192 (order 0, 65536 bytes)

    [    0.580617] NET: Registered protocol family 2

    [    0.585797] tcp_listen_portaddr_hash hash table entries: 4096 (order: 0, 65536 bytes)

    [    0.593956] TCP established hash table entries: 32768 (order: 2, 262144 bytes)

    [    0.601653] TCP bind hash table entries: 32768 (order: 3, 524288 bytes)

    [    0.609004] TCP: Hash tables configured (established 32768 bind 32768)

    [    0.615848] UDP hash table entries: 2048 (order: 0, 65536 bytes)

    [    0.622126] UDP-Lite hash table entries: 2048 (order: 0, 65536 bytes)

    [    0.629020] NET: Registered protocol family 1

    [    0.634106] RPC: Registered named UNIX socket transport module.

    [    0.640190] RPC: Registered udp transport module.

    [    0.645008] RPC: Registered tcp transport module.

    [    0.649824] RPC: Registered tcp NFSv4.1 backchannel transport module.

    [    0.657561] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available

    [    0.670432] Initialise system trusted keyrings

    [    0.675201] workingset: timestamp_bits=46 max_order=16 bucket_order=0

    [    0.687101] squashfs: version 4.0 (2009/01/31) Phillip Lougher

    [    0.693852] NFS: Registering the id_resolver key type

    [    0.699060] Key type id_resolver registered

    [    0.703351] Key type id_legacy registered

    [    0.707469] nfs4filelayout_init: NFSv4 File Layout Driver Registering...

    [    0.714521] 9p: Installing v9fs 9p2000 file system support

    [    0.724705] Key type asymmetric registered

    [    0.728915] Asymmetric key parser 'x509' registered

    [    0.733968] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)

    [    0.741546] io scheduler noop registered

    [    0.745575] io scheduler deadline registered

    [    0.750095] io scheduler cfq registered (default)

    [    0.754922] io scheduler mq-deadline registered

    [    0.759570] io scheduler kyber registered

    [    0.765488] pinctrl-single 4301c000.pinmux: 70 pins, size 280

    [    0.772103] pinctrl-single 11c000.pinmux: 185 pins, size 740

    [    0.778045] pinctrl-single 11c2e8.pinmux: 9 pins, size 36

    [    0.784797] pinctrl-single a40000.timesync_router: 512 pins, size 2048

    [    0.800331] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled

    [    0.823645] brd: module loaded

    [    0.826962] Internal error: undefined instruction: 0 [#1] PREEMPT SMP

    [    0.833550] Modules linked in:

    [    0.836673] Process swapper/0 (pid: 1, stack limit = 0x(____ptrval____))

    [    0.843527] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.19.38-g4dae378bbe #1

    [    0.850730] Hardware name: Texas Instruments AM654 Base Board (DT)

    [    0.857049] pstate: 00000005 (nzcv daif -PAN -UAO)

    [    0.861943] pc :           (null)

    [    0.865325] lr :           (null)

    [    0.868708] sp : 0000000000000000

    [    0.872092] x29: 0000000000000000 x28: 0000000000000000

    [    0.877523] x27: 0000000000000000 x26: 0000000000000000

    [    0.882954] x25: 0000000000000000 x24: 0000000000000000

    [    0.888387] x23: 0000000000000000 x22: 0000000000000000

    [    0.893818] x21: 0000000000000000 x20: 0000000000000000

    [    0.899250] x19: 0000000000000000 x18: 0000000000000000

    [    0.904683] x17: 0000000000000000 x16: 0000000000000000

    [    0.910115] x15: 0000000000000000 x14: 0000000000000000

    [    0.915547] x13: 0000000000000000 x12: 0000000000000000

    [    0.920977] x11: 0000000000000000 x10: 0000000000000000

    [    0.926408] x9 : 0000000000000000 x8 : 0000000000000000

    [    0.931839] x7 : 0000000000000000 x6 : 0000000000000000

    [    0.937271] x5 : 0000000000000000 x4 : 0000000000000000

    [    0.942702] x3 : 0000000000000000 x2 : 0000000000000000

    [    0.948134] x1 : 0000000000000000 x0 : 0000000000000000

    [    0.953567] Call trace:

    [    0.956061]            (null)

    [    0.959097] Code: bad PC value

    [    0.962231] ---[ end trace db568ddba5ae6915 ]---

    [    0.967027] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

    [    0.967027]

    [    0.976370] SMP: stopping secondary CPUs

    [    0.980382] Kernel Offset: disabled

    [    0.983945] CPU features: 0x0,2080200c

    [    0.987772] Memory Limit: none

    [    0.990894] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

    [    0.990894]  ]---

  • Hello Andrea,

    Are you still experiencing the Kernel panics and do you have any questions regarding the DT files?

    Regards,
    Krunal

  • Hi Krunal,

    We are still experiencing the kernel panics. I've also posted a related question just now about something we think may be triggering the errors before the DT files come into play.

    Thanks,
    Andrea

  • Hello Andrea,

    I see the new thread you have created about the DT/Kernel panics and we will post our comments directly on the new thread. I will be closing the current thread but if you have any further questions, please feel free to continue the conversation.

    Regards,
    Krunal