<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Attaching to Android 14 Kernel using gdb in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2058900#M234877</link>
    <description>&lt;P&gt;Thank you for your reply. The board I am porting the bsp for is indeed based on one of the reference boards in the link you had attached, however it contains custom features that need porting.&lt;/P&gt;&lt;P&gt;In the meantime, I was able to find the problematic driver by adding the following line to BoardConfig.mk, tracing the initcall calls and disabling suspicious drivers until finding the erroneous one.&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;BOARD_KERNEL_CMDLINE += initcall_debug&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 10 Mar 2025 16:56:07 GMT</pubDate>
    <dc:creator>Dmitri</dc:creator>
    <dc:date>2025-03-10T16:56:07Z</dc:date>
    <item>
      <title>Attaching to Android 14 Kernel using gdb</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2057152#M234781</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;I'm porting bsp for imx8m-mini based board from Android 10 to Android 14. In minicom, I can see Kernel booting, however after several seconds of running it just hangs. After having exhausted all available options debugging using debug logs, I am now trying to troubleshoot using gdb.&lt;/P&gt;&lt;P&gt;For that purpose, I rebuilt the kernel with the following configs in my kernel defconfig file:&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;CONFIG_KGDB=y&lt;BR /&gt;CONFIG_KGDB_SERIAL_CONSOLE=y&lt;BR /&gt;CONFIG_KGDB_KDB=y&lt;BR /&gt;CONFIG_FRAME_POINTER=y&lt;BR /&gt;CONFIG_KALLSYMS=y&lt;BR /&gt;CONFIG_DEBUG_INFO=y&lt;BR /&gt;CONFIG_DEBUG_KERNEL=y&lt;BR /&gt;CONFIG_GDB_SCRIPTS=y&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;In addition, I added the following line to BoardConfig.mk, as suggested &lt;A href="https://www.kernel.org/doc/html/v4.18/dev-tools/kgdb.html" target="_self"&gt;here&lt;/A&gt;, expecting the kernel to wait for debugger to attach:&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;BOARD_KERNEL_CMDLINE += kgdboc=ttymxc2 kgdbwait&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;Unfortunately, the kernel boots without waiting. Also, my attempts to connect to it using the sequence below, fail. (I get the error "Remote connection closed" once I turn on the board)&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;sudo gdb vmlinux&lt;BR /&gt;target remote /dev/ttyUSB0&lt;/PRE&gt;&lt;/DIV&gt;&lt;P&gt;Can anyone please suggest what else I can try to troubleshoot the hanging kernel?&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 15:24:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2057152#M234781</guid>
      <dc:creator>Dmitri</dc:creator>
      <dc:date>2025-03-06T15:24:47Z</dc:date>
    </item>
    <item>
      <title>Re: Attaching to Android 14 Kernel using gdb</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2058794#M234870</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;You don't need to port the android 14 and android 15, because is on the BSP section please check it:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/android-os-for-i-mx-applications-processors:IMXANDROID" target="_blank"&gt;https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/android-os-for-i-mx-applications-processors:IMXANDROID&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Mar 2025 14:04:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2058794#M234870</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2025-03-10T14:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: Attaching to Android 14 Kernel using gdb</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2058900#M234877</link>
      <description>&lt;P&gt;Thank you for your reply. The board I am porting the bsp for is indeed based on one of the reference boards in the link you had attached, however it contains custom features that need porting.&lt;/P&gt;&lt;P&gt;In the meantime, I was able to find the problematic driver by adding the following line to BoardConfig.mk, tracing the initcall calls and disabling suspicious drivers until finding the erroneous one.&lt;/P&gt;&lt;DIV&gt;&lt;PRE&gt;&lt;SPAN&gt;BOARD_KERNEL_CMDLINE += initcall_debug&lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 10 Mar 2025 16:56:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Attaching-to-Android-14-Kernel-using-gdb/m-p/2058900#M234877</guid>
      <dc:creator>Dmitri</dc:creator>
      <dc:date>2025-03-10T16:56:07Z</dc:date>
    </item>
  </channel>
</rss>

