lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: "Vadivel, Arulpandiyan via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Cc: "Krishnakar, Srikanth" <Srikanth_Krishnakar@mentor.com>
Subject: [lttng-dev] Reg: LTTNG Support for arm64 based k3-am654 board
Date: Wed, 17 Mar 2021 13:43:59 +0000	[thread overview]
Message-ID: <1615988639233.71702@mentor.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1893 bytes --]

Hi Team,

    We are working on the Texas Instrument's K3-am654 board(ARM64 based), on 4.19.165-cip41 RT and Non-RT kernel. We would like to have the lttng support on the board. Hence I have added below configurations.  With these configurations enabled I am not able to access the console itself and kernel stuck at Starting kernel itself as below.  Further we have added earlycon to debug the early console.  Bootargs given below. With these earlycon option also we are still stuck at  Starting kernel  itself.


Could you please help me to understand below queries,

  *    Do we have the support of lttng for TI's K3-am654 board?
  *    Or did we miss something in the kernel?


Bootargs
setenv bootargs "console=ttyS3,115200n8 root=/dev/mmcblk0p1 rw rootfstype=ext4 rootwait earlycon=ns16550a,mmio32,0x02810000"
load mmc 0:1 0x82000000 /usr/lib/linux-image-4.19.165-cip41-rt18/ti/k3-am654-base-board.dtb
load mmc 0:1 0x80080000 /boot/vmlinuz-4.19.165-cip41-rt18;
load mmc 0:1 0x81000000 /boot/initrd.img-4.19.165-cip41-rt18;
booti 0x80080000 0x81000000:20000 0x82000000

?
?Boot logs
=>
=> run bootcmd_mmc0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
77332 bytes read in 9 ms (8.2 MiB/s)
16533512 bytes read in 4217 ms (3.7 MiB/s)
8740838 bytes read in 731 ms (11.4 MiB/s)
## Flattened Device Tree blob at 82000000
   Booting using the fdt blob at 0x8200000
   Loading Ramdisk to fd670000, end fdec5fe6 ... OK
   Loading Device Tree to 00000000fd65a000, end 00000000fd66fe13 ... OK

Starting kernel ...

Kernel Configurations.
CONFIG_KPROBES=y
CONFIG_PERF_EVENTS=y
CONFIG_HAVE_SYSCALL_TRACEPOINTS=y
CONFIG_EVENT_TRACING=y
CONFIG_KRETPROBES=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_TRACEPOINTS=y
CONFIG_FTRACE=y
CONFIG_FUNCTION_TRACER=y
CONFIG_LTTNG=m

Regards,
Arulpandiyan V.

[-- Attachment #1.2: Type: text/html, Size: 6389 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2021-03-17 13:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 13:43 Vadivel, Arulpandiyan via lttng-dev [this message]
2021-03-17 15:11 ` [lttng-dev] Reg: LTTNG Support for arm64 based k3-am654 board Jonathan Rajotte-Julien via lttng-dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1615988639233.71702@mentor.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=Arulpandiyan_Vadivel@mentor.com \
    --cc=Srikanth_Krishnakar@mentor.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).