<?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: IMX95 Android Enabling Flexcan1 interface crashes in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/IMX95-Android-Enabling-Flexcan1-interface-crashes/m-p/2119418#M238393</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The FlexCAN is not tested in android for the MX95 is on beta stage, however it is for M-core. You have to go with third party, and unfortunately I cannot comment much about the Toradex board, but as I see on their devcie tree there is 2 flexcan interfaces already enabled:&lt;BR /&gt;&lt;A href="https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts#L356" target="_blank" rel="nofollow noopener noreferrer"&gt;https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts...&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Please note that, or at least in what I saw, they use our EVK dts as a base.&lt;BR /&gt;&lt;BR /&gt;Which one are you trying to use?&lt;BR /&gt;Also, if you are just using a different device tree, creating a layer with the device tree addition you will use should be enough.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jun 2025 13:51:48 GMT</pubDate>
    <dc:creator>Bio_TICFSL</dc:creator>
    <dc:date>2025-06-19T13:51:48Z</dc:date>
    <item>
      <title>IMX95 Android Enabling Flexcan1 interface crashes</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX95-Android-Enabling-Flexcan1-interface-crashes/m-p/2119156#M238379</link>
      <description>&lt;P&gt;enabled flexcan5 with following device tree added and it works,&lt;BR /&gt;&lt;BR /&gt;&amp;amp;flexcan5 {&lt;BR /&gt;pinctrl-names = "default";&lt;BR /&gt;pinctrl-0 = &amp;lt;&amp;amp;pinctrl_flexcan5&amp;gt;;&lt;BR /&gt;status = "okay";&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;pinctrl_flexcan5: flexcan5grp {&lt;BR /&gt;fsl,pins = &amp;lt;&lt;BR /&gt;IMX95_PAD_GPIO_IO30__CAN5_TX 0x39e&lt;BR /&gt;IMX95_PAD_GPIO_IO31__CAN5_RX 0x39e&lt;BR /&gt;&amp;gt;;&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sameway enabling the flexcan1 into device tree as below, creates crash on boot up.&lt;BR /&gt;&amp;amp;flexcan1 {&lt;BR /&gt;pinctrl-names = "default";&lt;BR /&gt;pinctrl-0 = &amp;lt;&amp;amp;pinctrl_flexcan1&amp;gt;;&lt;BR /&gt;status = "okay";&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;pinctrl_flexcan1: flexcan1grp {&lt;BR /&gt;fsl,pins = &amp;lt;&lt;BR /&gt;IMX95_PAD_PDM_CLK__AONMIX_TOP_CAN1_TX 0x39e&lt;BR /&gt;IMX95_PAD_PDM_BIT_STREAM0__AONMIX_TOP_CAN1_RX 0x39e&lt;BR /&gt;&amp;gt;;&lt;BR /&gt;};&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Enabled with flexcan1, getting the following crash on android system boot up itself,&lt;BR /&gt;&lt;BR /&gt;[ 18.272436][ T266] pwm_imx_tpm(E) pwrseq_simple(E) nvmem_imx_ocotp_fsb_s400(E) nvmem_imx_ocotp(E) sdhci_esdhc_imx(E) busfreq_imx8mq(E) cqhci(E) sec_enclave(E) imx7ulp_wdt(E) dma_buf_imx(E) cma_heap(E) dsp_heap(E) system_heap(E) cpufreq_dt(E) pwm_bl(E) led_bl(E) sm_misc(E) sm_bbm(E) irq_imx_irqsteer(E) i2c_mux(E) i2c_rpmsg_imx(E) i2c_dev(E) i2c_imx_lpi2c(E) trusty_virtio(E) trusty_ipc(E) trusty_log(E) trusty_core(E) fsl_lpuart(E) fsl_edma_v3(E) pinctrl_imx_scmi(E) pinctrl_imx(E) imx_rproc(E) virtio_rpmsg_bus(E) rpmsg_ns(E) imx_mailbox(E) timer_imx_sysctr(E) imx95_blk_ctrl(E) mxc_clk(E) clk_scmi(E) arm_smmu_v3(E) scmi_power_control(E) scmi_pm_domain(E) imx_sm_misc(E) imx_sm_bbm(E) scmi_hwmon(E) hwmon(E)&lt;BR /&gt;[ 18.343989][ T266] CPU: 3 PID: 266 Comm: modprobe Tainted: G E 6.6.56-4k-g7febc6b99bf1-dirty #25 1400000003000000474e550082c1a91e1218fbed&lt;BR /&gt;[ 18.357785][ T266] Hardware name: ADLINK i.MX95 19X19 board (DT)&lt;BR /&gt;[ 18.363861][ T266] pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)&lt;BR /&gt;[ 18.371504][ T266] pc : readl+0x38/0x80 [flexcan]&lt;BR /&gt;[ 18.376322][ T266] lr : readl+0x38/0x80 [flexcan]&lt;BR /&gt;[ 18.381115][ T266] sp : ffffffc08309b640&lt;BR /&gt;[ 18.385110][ T266] x29: ffffffc08309b640 x28: 0000000000000000 x27: ffffffe2c59e7038&lt;BR /&gt;[ 18.392927][ T266] x26: ffffffc082d90000 x25: ffffff808b191d20 x24: ffffffc082d90000&lt;BR /&gt;[ 18.400745][ T266] x23: ffffff808b3b8a80 x22: ffffffc082d90000 x21: ffffff808b3b8000&lt;BR /&gt;[ 18.408562][ T266] x20: ffffffe2c59e2e44 x19: ffffffc082d90000 x18: ffffffc080d3d0b8&lt;BR /&gt;[ 18.416379][ T266] x17: 000000001a23ed84 x16: 000000001a23ed84 x15: 001f00003fffffff&lt;BR /&gt;[ 18.424197][ T266] x14: 0000000000000901 x13: 0000000000001f62 x12: 0000000029aaaaab&lt;BR /&gt;[ 18.432014][ T266] x11: 0000000000000000 x10: 0000000000000001 x9 : 0000000100000000&lt;BR /&gt;[ 18.439832][ T266] x8 : ffffffe2c59e2e34 x7 : 6e6169646e652d67 x6 : 0c080a48653d3d3a&lt;BR /&gt;[ 18.440281][ T245] F2FS-fs (dm-49): Start checkpoint disabled!&lt;BR /&gt;[ 18.447648][ T266] x5 : 3a3d3d65480a080c x4 : 0000000000000000 x3 : ffffffe2c59e2e44&lt;BR /&gt;[ 18.447664][ T266] x2 : ffffffe2c59e5518 x1 : ffffffc082d90000 x0 : 0000000000000020&lt;BR /&gt;[ 18.447671][ T266] Call trace:&lt;BR /&gt;[ 18.447674][ T266] readl+0x38/0x80 [flexcan 1400000003000000474e55002988bead4d752179]&lt;BR /&gt;[ 18.456615][ T245] F2FS-fs (dm-49): Mounted with checkpoint version = 67638750&lt;BR /&gt;[ 18.461395][ T266] flexcan_read_le+0x10/0x20 [flexcan 1400000003000000474e55002988bead4d752179]&lt;BR /&gt;[ 18.469834][ T161] init: Unable to set property 'ro.boottime.init.mount.data' from uid:0 gid:0 pid:245: Read-only property was already set&lt;BR /&gt;[ 18.472358][ T266] flexcan_probe+0x384/0x9e0 [flexcan 1400000003000000474e55002988bead4d752179]&lt;BR /&gt;[ 18.472378][ T266] platform_probe+0xc0/0xec&lt;BR /&gt;[ 18.481964][ T250] NetlinkListener: recvmsg failed (No buffer space available)&lt;BR /&gt;[ 18.487654][ T266] really_probe+0x190/0x374&lt;BR /&gt;[ 18.487661][ T266] __driver_probe_device+0xa0/0x12c&lt;BR /&gt;[ 18.487665][ T266] driver_probe_device+0x3c/0x218&lt;BR /&gt;[ 18.487669][ T266] __driver_attach+0x110/0x1ec&lt;BR /&gt;[ 18.487674][ T266] bus_for_each_dev+0x104/0x160&lt;BR /&gt;[ 18.487680][ T266] driver_attach+0x24/0x34&lt;BR /&gt;[ 18.487684][ T266] bus_add_driver+0x154/0x270&lt;BR /&gt;[ 18.487690][ T266] driver_register+0x68/0x104&lt;BR /&gt;[ 18.487694][ T266] __platform_driver_register+0x24/0x34&lt;BR /&gt;[ 18.487700][ T266] init_module+0x20/0xfe4 [flexcan 1400000003000000474e55002988bead4d752179]&lt;BR /&gt;[ 18.488151][ T1] init: Userdata mounted using /vendor/etc/fstab.nxp result : 6&lt;BR /&gt;[ 18.488418][ T1] init: Command 'mount_all /vendor/etc/fstab.nxp --late' action=vendor.skip.charger_not_need=0 &amp;amp;&amp;amp; late-fs (/vendor/etc/init/hw/init.nxp.rc:89) took 11488ms and succeeded&lt;BR /&gt;[ 18.493339][ T1] init: starting service 'vpu_firmware_load'...&lt;BR /&gt;[ 18.610566][ T266] do_one_initcall+0xdc/0x360&lt;BR /&gt;[ 18.615089][ T266] do_init_module+0x58/0x1cc&lt;BR /&gt;[ 18.619535][ T266] load_module+0xffc/0x1130[ 18.623895][ T266] __arm64_sys_finit_module+0x260/0x300&lt;BR /&gt;[ 18.629294][ T266] invoke_syscall+0x58/0x114&lt;BR /&gt;[ 18.633740][ T266] el0_svc_common+0xac/0xe0&lt;BR /&gt;[ 18.638099][ T266] do_el0_svc+0x1c/0x28&lt;BR /&gt;[ 18.642103][ T266] el0_svc+0x38/0x68&lt;BR /&gt;[ 18.645865][ T266] el0t_64_sync_handler+0x68/0xbc&lt;BR /&gt;[ 18.650735][ T266] el0t_64_sync+0x1a8/0x1ac&lt;BR /&gt;[ 18.655090][ T266] Code: aa1303e1 aa1e03e3 aa1e03f4 9424e90a (b9400268)&lt;BR /&gt;[ 18.661873][ T266] ---[ end trace 0000000000000000 ]---&lt;BR /&gt;[ 18.667169][ T266] Kernel panic - not syncing: synchronous external abort: Fatal exception&lt;BR /&gt;[ 18.675514][ T266] SMP: stopping secondary CPUs&lt;BR /&gt;[ 18.680178][ T266] Kernel Offset: 0x2245c00000 from 0xffffffc080000000&lt;BR /&gt;[ 18.686789][ T266] PHYS_OFFSET: 0x80000000&lt;BR /&gt;[ 18.690966][ T266] CPU features: 0x000000,c0000001,400a0143,1001721b&lt;BR /&gt;[ 18.697397][ T266] Memory Limit: none&lt;BR /&gt;&lt;BR /&gt;looks crash occurs on ioread function, share your inputs regarding this.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jun 2025 07:09:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX95-Android-Enabling-Flexcan1-interface-crashes/m-p/2119156#M238379</guid>
      <dc:creator>VeeraH</dc:creator>
      <dc:date>2025-06-19T07:09:38Z</dc:date>
    </item>
    <item>
      <title>Re: IMX95 Android Enabling Flexcan1 interface crashes</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/IMX95-Android-Enabling-Flexcan1-interface-crashes/m-p/2119418#M238393</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The FlexCAN is not tested in android for the MX95 is on beta stage, however it is for M-core. You have to go with third party, and unfortunately I cannot comment much about the Toradex board, but as I see on their devcie tree there is 2 flexcan interfaces already enabled:&lt;BR /&gt;&lt;A href="https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts#L356" target="_blank" rel="nofollow noopener noreferrer"&gt;https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts...&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Please note that, or at least in what I saw, they use our EVK dts as a base.&lt;BR /&gt;&lt;BR /&gt;Which one are you trying to use?&lt;BR /&gt;Also, if you are just using a different device tree, creating a layer with the device tree addition you will use should be enough.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jun 2025 13:51:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/IMX95-Android-Enabling-Flexcan1-interface-crashes/m-p/2119418#M238393</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2025-06-19T13:51:48Z</dc:date>
    </item>
  </channel>
</rss>

