LINFlexd in UART mode with eDMA Hi, I configured LinFlexD to UART mode and set up DMA channel 0 for transmission, but it triggered a Destination Bus Error. I'm not sure how to resolve this issue. The code as follow. is something i missed?       LINFLEX_3.LINCR1.B.INIT    = 1;            LINFLEX_3.LINCR1.B.SLEEP   = 0;            LINFLEX_3.LINCR1.B.BF      = 0;           LINFLEX_3.UARTCR.B.UART    = 1;            LINFLEX_3.UARTCR.B.RXEN    = 1;            LINFLEX_3.UARTCR.B.TXEN    = 1;            LINFLEX_3.UARTCR.B.WL0     = 1;            LINFLEX_3.UARTCR.B.PC0     = 1;            LINFLEX_3.UARTCR.B.PCE     = 0;            LINFLEX_3.UARTCR.B.TFBM    = 1;             // LINFLEX_3.UARTCR.B.RFBM    = 1;              LINFLEX_3.LINIBRR.B.DIV_M  = 20 * 10000 / 96 / 16;     // 250k // Baud Rate = 9600, In Case fperi1 = 80 MHz     LINFLEX_3.LINFBRR.B.DIV_F  = 0;      // 7 // Baud Rate = 9600, In Case fperi1 = 80 MHz     LINFLEX_3.LINIER.B.DRIE    = 1;            LINFLEX_3.UARTSR.B.DRFRFE  = 1;       // Clear Data Reception Completed Flag     LINFLEX_3.UARTSR.B.DTFTFF  = 1;       // Clear Data Transmission Completed Flag     LINFLEX_3.LINCR1.B.INIT    = 0;       // Normal Mode     LINFLEX_3.DMATXE.B.DTE0 = 1;     // LINFLEX_3.DMARXE.B.DRE0 = 1;       DMAMUX_0.CHCONFIG[0].R = 0xA5;     // DMAMUX_0.CHCONFIG[1].B.ENBL = 1;    // channel 1 uart rx     // DMAMUX_0.CHCONFIG[1].B.TRIG = 0;     // DMAMUX_0.CHCONFIG[1].B.SOURCE = 0x26;     EDMA_0.TCD[0].CITER = 0x8;     EDMA_0.TCD[0].BITER = 0x8;     EDMA_0.TCD[0].NBYTES = 0x1;     EDMA_0.TCD[0].SADDR = (uint32)&lin3_tx_buffer[0];     EDMA_0.TCD[0].SOFF = 0x1;     EDMA_0.TCD[0].SSIZE = 0;     EDMA_0.TCD[0].SLAST = 0xFFFFFFFFFFFFFFF8;     EDMA_0.TCD[0].DADDR =  (uint32)(&LINFLEX_3.BDRL) + 3;     EDMA_0.TCD[0].DOFF = 0;     EDMA_0.TCD[0].DSIZE = 0;     EDMA_0.TCD[0].D_REQ = 1;     EDMA_0.TCD[0].INT_MAJ = 1;     EDMA_0.DMAERQL.B.ERQ00 = 1;   There are a few more questions. 1. If I want to periodically send 30 bytes of data in a 20ms task, how do I control the sending and stopping of DMA? Can I enable it during the 20ms task by EDMA_0.DMAERQL.B.ERQ00 = 1; and disable it during the DMA completion interrupt by EDMA_0.DMAERQL.B.ERQ00 = 0?  In another words, how should i restart the DMA periodically in 20ms task or i dont have to do that manually?    2. When LINFlexD is in UART FIFO mode (TFBM = 1)，how many bytes are there in BDR? The manual says there is only one byte, is it true? if it is, why call it a FIFO? should't it be 4 bytes.   3. When there is a Destination Bus Error, you can see that the Citer has been decreasing. Why is this? Shouldn't it stop the DMA transmission? I'm sure no signal is coming out of the serial port, so who gives the DMA request?   thanks Re: LINFlexd in UART mode with eDMA   1) Setup certain timer for 20ms and after its expiration set START bit of particular DMA TCD. 2) You haven't specified used device. MPC5643L has is as follows, other may have it differently.   3) Yes, bus error stops transmission. If triggered again, it apparently continues.

FRDM-MCXN947 无法使用配置工具修改 led_blinky 示例项目中使用的 LED。 我正在尝试遵循本教程，其中解释了如何使用 VSCode 的配置工具。（ https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con... ） 以下是快速重现我所遇到的问题的方法： 1. 安装 VS Code、MCUXpresso 扩展和 MCXN947 板的 SDK。（我在英特尔 iMac 上运行它。） 2. 导入、构建并运行 led_blinky 示例项目。这很好用。 3. 在 VSCode 中，右键单击 led_blinky 并开始使用配置工具。 4. 配置工具一打开就报告时钟和引脚中存在许多错误。（大约 20 个错误）。我是 NXP、MCUXpresso 和 VSCode 的新手，所以我不知道如何继续。 我在网上搜索了我遇到的错误，但没有找到任何有用的信息。 感谢您的帮助！ 此外，MCUXpresso VS Code 扩展也给我留下了深刻的印象。你们太棒了！而且我很确定，一旦我更好地了解配置工具，我也会说同样的话。 回复：FRDM-MCXN947 无法使用配置工具修改 led_blinky 示例项目中使用的 LED。 嗯，这次成功了。您将看到上面的屏幕截图。 我确实看到您的配置概述没有显示我收到的错误。我希望我的概览屏幕看起来像你的一样！ 我不知道如何确认配置工具是否安装成功。据我所知，它似乎正在发挥作用。我确实得到了一个与您的类似的配置工具概览屏幕，但仍然存在很多差异。我希望当您看到配置工具概览屏幕之间的差异时，它将帮助您确定出了什么问题。同时，我将卸载我的配置工具程序并从您的网站重新安装它。 回复：FRDM-MCXN947 无法使用配置工具修改 led_blinky 示例项目中使用的 LED。 我添加了几个屏幕截图。我在每个屏幕截图上标记了与错误相关的各个区域。 显示两种类型的错误。 1.设备配置错误似乎表明配置工具不支持 MCNX947 上使用的处理器。我想我误解了这个错误的含义。 2. 缺少驱动程序错误。我在我的 SDK 仓库中找不到这些驱动程序。也许这些文件名（COMMON、PORTR、CLOCK 等）是通用名称而不是实际文件名。如果是这样的话，我不知道如何找到实际的文件名，也不清楚如何使用 VS Code 或配置工具将驱动程序添加到项目中。

BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. Hello,  I am trying to run program in RAM section . I build simple sieve code using S32 design studio with build setting as Debug_RAM. when I debug using PEmicro debugger it works fine , there are no errors. but If I use same elf and program it using Lauterbach script  "s32k344cvd-q257_sieve_sram.cmm" it throws bus error "bus error at EST:0x2043000--0x204310CF".  note: with example elf file provided by Lauterbach, script "s32k344cvd-q257_sieve_sram.cmm" works perfectly fine. What setting I am missing in S32_studio ? Are any changes need to do in linker manually? S32K344-WB  Thanks in advance!! Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. Hi, @davidtosenovjan  Initializing whole RAM in init_ram.cmm script resolved my issue.  Thank you so much. Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. The script 'init_sram.cmm' initialized address range 0x20400000-0x20427FFF i.e. 160kB i.e. only half of SRAM memory of S32K344.init_sram.cmm That's the reason probably Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. Hi, attached Lauterbach scripts I am using. Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. This is rather question to Lauterbach. Could you share mentioned script?

FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. I am attempting to follow this tutorial which explains how to use the Config tool with VSCode. . (https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con...)  Here' is how to quickly reproduce the problem I am having: 1. Install VS Code, the MCUXpresso extension, and the SDK for the MCXN947 board. (I'm running it on an intel iMac.)  2. Import, built, and run the led_blinky example project. This works fine.  3. From VSCode, right click on led_blinky and start using the config tool. 4. As soon as it opens, the Config tool is reporting many errors in Clocks and Pins. (around 20 errors). I'm new with NXP, MCUXpresso, and VSCode so I don't know how to proceed.  I've searched the web for the errors I'm getting and haven't found anything useful. Thank you for your help! Also, I am very impressed with the MCUXpresso VS Code extension. You guys rock! And I'm pretty sure I will say the same thing about the Config tool once I learn it better.  Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  Congratulations! The repo you advised me to obtain does not show any Config errors! Thank you for spending as much time as you did to help me with this problem!  Is it always best to obtain archives from the SDK builder rather than Github? I'm pretty sure the IDE recommended Github. Perhaps it should recommend the SDK builder.  Now I've got a lot to learn about how to use the Config tool. Right now It's pretty confusing to me. I've no doubt I'll figure it out pretty quickly now that you've solved this problem.. Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Hello @ClarkS , Thanks for your information. I have tried the Config Tools v24.12. The problem you mentioned still hasn't occurred. However, I've found that the SDKs we're using are indeed different. You're using the one from GitHub, while mine is from a local repository. I tried using the one from GitHub, but I keep failing to import it. So, I'm wondering if you could try the method of local import to see if it works. 1. Download the 24.12 SDK from Select Board | MCUXpresso SDK Builder 2. After the download is completed, place the SDK in the created directory C:\MCUXpresso_for_vscode.  3. Select the "LOCAL ARCHIVE" method to import the repository.   Choose "Import Repository" -> "LOCAL ARCHIVE" -> "Archive" -> "Browse", then locate the SDK folder downloaded from the SDK Builder. Select the built "SDK_24_12_00_FRDM - MCXN947".  4. Create a new empty folder and name it "MCXN947". Click "Destination" -> "Browse" and select the newly created "MCXN947" folder. Then click "Import", and the SDK will be automatically imported. 5. Click "Import Example from Repository" to import the project "led_blinky" and create a new project.   Hope it can help you. BRs, Celeste Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  We have different versions of Config Tools.  I have 24.12. You have 16.1.  I got mine from here: https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-config-tools-pins-clocks-and-peripherals:MCUXpresso-Config-Tools  Would you be able to test with the later version?  My SDK is 24.12.10. You have both SDK: 24_12_00 and SDK_2_16_100. When I import my repo for the MCXN947 board I see these two choices. What's the difference between the two.? Which one should I select? I'm pretty sure I picked the 2nd one.  Here is another view of my configuration.  Thank you for your help! Clark Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Hello ClarkS, On my end, there was indeed a version warning, but after I closed it, I didn't encounter any problems. Let me list the versions of my tests: Config Tools: v16.1 SDK: 24_12_00, SDK_2_16_100 I've tried the led_blinky in both versions of the SDK, and there were no issues. BRs, Celeste Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  I deleted my Config Tools app, downloaded a new copy from your web site, deleted my led_blinky example, re-imported it from my repo, and relaunched the new copy of Config Tools. It still shows the errors.  I did notice that the errors do not appear until I acknowledge a warning message complaining about the version of the configuration. I will attach two screen shots, the first one showing the warning message, and the second showing the next screen shot. Do you get the version warning? If not, what would explain that? Are we using different led_blinky versions? Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Well, this time it worked. You will see the screenshots above.  I do see that your Configuration Overview does not show the errors that I am getting. I wish my Overview screen looked like yours does! I don't know how to confirm Config tools is successfully installed. As far as I can tell, it appears to be working. I do get a Config Tools Overview screen which is similar to yours, but there are still a lot of difference. I hope when you see the differences between the Config Tools Overview screens, it will help you determine what is going wrong. In the mean time, I will uninstall my Config Tools program and reinstall it from your web site.  Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  I'm having trouble adding the screen shots. Whenever I do I get an error message below the CAPTCHA that says that verification failed.  Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Hello @ClarkS , Thank you for your interest in our products. I have tried it on my end, but I haven't reproduced your problem. The configuration tools can be opened normally. I have checked the Quick Start Guide of the MCUXpresso configuration tools and found that it supports iMac. Could you please confirm whether you have successfully installed the MCUXpresso configuration tools on your Intel iMac? You can also send me a screenshot of the error message that appears when you try to open it. BRs, Celeste Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. I've added a couple screen shots. I've marked the various error related areas on each screen shot.  Two types of errors are shown. 1. The Device Configuration error which seems to say the Config tool does not support the processor used on the MCNX947. I think I misunderstand the meaning of this error. 2. Missing driver errors.  I cannot find those drivers in my SDK repo. Maybe those file names (COMMON, PORTR, CLOCK, etc) are generic names and not actual file names. If that is the case, I have no idea how to find the actual file name, nor is it clear to me how to add drivers to the project using VS Code or the Config tool.  

FRDM-MCXN947 Config ツールを使用して、サンプル プロジェクトで使用されている LED を変更できませんled_blinky VSCodeでConfigツールを使用する方法を説明するこのチュートリアルに従うことを試みています。.(https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con...) ここで'私が抱えている問題を迅速に再現する方法は次のとおりです。 1. VS Code、MCUXpresso 拡張機能、および MCXN947 ボードの SDK をインストールします。(私はそれをIntel iMacで実行しています。 2. led_blinky サンプル プロジェクトをインポートし、ビルドして実行します。これは正常に動作します。 3. VSCodeから、led_blinkyを右クリックして、構成ツールの使用を開始します。 4. Configツールが開くとすぐに、クロックとピンに多くのエラーが報告されます。(約20エラー)。私はNXP、MCUXpresso、およびVSCodeを初めて使用するので、どのように進めればよいかわかりません。 私は私が得ているエラーのためにウェブを検索しましたが、有用なものは何も見つかりませんでした。 ご協力いただきありがとうございます! また、MCUXpresso VS Code拡張機能にも非常に感銘を受けました。あなたたちは最高です!そして、Configツールについてもっとよく学んだら、同じことを言うと確信しています。 Re: FRDM-MCXN947 Config ツールを使用して、サンプル プロジェクトで使用されている LED を変更できませんled_blinky さて、今回はうまくいきました。上のスクリーンショットが表示されます。 構成の概要には、発生しているエラーが表示されていないことがわかります。私の概要画面があなたの画面のように見えたらいいのにと思います! Configツールが正常にインストールされたことを確認する方法がわかりません。私が知る限り、それは機能しているようです。あなたのものと同様の構成ツールの概要画面が表示されますが、それでも多くの違いがあります。Config Tools Overview画面の違いを確認すると、何が問題になっているのかを判断するのに役立つことを願っています。それまでの間、私は私のConfigToolsプログラムをアンインストールし、あなたのWebサイトから再インストールします。 Re: FRDM-MCXN947 Config ツールを使用して、サンプル プロジェクトで使用されている LED を変更できませんled_blinky スクリーンショットをいくつか追加しました。各スクリーンショットでさまざまなエラー関連領域をマークしました。 2 種類のエラーが表示されます。 1.デバイス構成エラーは、構成ツールがMCNX947で使用されているプロセッサをサポートしていないことを示しているようです。私はこのエラーの意味を誤解していると思います。 2.ドライバーのエラーがありません。SDK リポジトリでこれらのドライバーが見つかりません。もしかしたら、これらのファイル名 (COMMON、PORTR、CLOCK など) は一般的な名前であり、実際のファイル名ではないかもしれません。その場合、実際のファイル名を見つける方法がわからず、VSCodeまたはConfigツールを使用してプロジェクトにドライバーを追加する方法も明確ではありません。

UJA1164 SBC芯片/Can收发器配置 我对 UJA1164 SBC 芯片有疑问。我正在通过 SPI 与 SBC 通信。我正在尝试设置一些具有特定值的寄存器，但这些值并未写入寄存器中。配置收发器是否应遵循特定的程序？有这个的演示代码吗？ 回复：UJA1164 SBC芯片/CAN收发器配置 在案例 # 00655722 中进行了内部答复。  

Is it possible to write any data to UTest area in SystemInit for S32K312 Hi I want to write any data to UTest Area(for example : 0x1b000060) in SystemInit. is it possible? Re: Is it possible to write any data to UTest area in SystemInit for S32K312 This issue is resolved. Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hello, Security (HSE) topics are not discussed on public community. Please submit a ticket at NXP.com for support on such theme. Best regards, Peter Re: Is it possible to write any data to UTest area in SystemInit for S32K312 The attached file is the firmware to install hse firmware Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hi. I make SHERPA_HSE_INSTALL_S32K312.sre file to install hse binary(s32k3x2_hse_fw_0.13.0_2.6.0_pb221129.bin.pink). and Power off and on runs after I download this file. But HSE Enable flag does not written to 0x1b000000. Could you please let me know what is problem? Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hello, Is it possible to write the attached file to 0x1b000000 using MCU Programming Tool like FR-Cube There is no restriction o n programming UTEST. It is just a normal flash which is set as OTP in NXP factory. Follow the procedure described in reference manual for UTEST programming. chapter 21.3 UTest NVM sector MCU Programming Tool like FR-Cube without running code for hse enable? Unfortunate I do not know your FR-Cube tool. Please consult such with your tool vendor. Best regards, Peter Re: Is it possible to write any data to UTest area in SystemInit for S32K312 In additional,  Is it possible to write the attached file to 0x1b000000 using MCU Programming Tool like FR-Cube without running code for hse enable? BRs. Hyunung Park  Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hello, In these areas you can store you information. make sure in case you are using UTEST DCF Start or Records, to store your data after 0xFFFF_FFFF_FFFF_FFFF space from your DCf data. Also be aware that storing data after stop record will leave you will no possibility to add additional DCF records. So leave enough space. Best regards, Peter

Is there any difference between the USB1 and USB2 ports on the i.MX 8M PLUS? Hi all, Q1) According to the documentation provided by NXP, the two USB ports on the i.MX8MPLUS appear to have the same functionality. Is our understanding correct? Q2) Does the USB Serial download mode work on either port?        *Is there a setting to prioritize one port over the other? Thanks, George i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Is there any difference between the USB1 and USB2 ports on the i.MX 8M PLUS? Hello @Bio_TICFSL, Thank you for your answer. I have confirmed that Serial-Download mode does indeed work on both USB ports using the IMX8MP-EVK. It seems that which port is used for Serial Download is determined by USBx_VBUS. Thanks, George Re: Is there any difference between the USB1 and USB2 ports on the i.MX 8M PLUS? Hello, a) Yes both works as the same functionality b) Yes, Please refer to the https://www.nxp.com/webapp/Download?colCode=IMX8MMEVKHUG  for details like switch settings and steps to follow for serial download mode. Regards

LPDDR4 recommendation for i.MX 8M Nano Hello, in the "i.MX 8M Quad/8M Mini/8M Nano/8M Plus - LPDDR4, DDR4 and DDR3L memory compatibility guide" all the LPDDR4 for the Nano are marked as obsolete Do you have an updated memory part list compatible with the i.MX 8M Nano ? Thanks Re: LPDDR4 recommendation for i.MX 8M Nano You can follow this: i.MX 8M Quad/8M Mini/8M Nano/8M Plus - LPDDR4, DDR4 and DDR3L memory compatibility guide - NXP Community. We do not have update ddr list, but you can follow this :

CCM_CLK1_N/P pads P16 and P17 on imx6 MCIMX6Y2 how to use as an output? The picture above is from document number: IMX6ULLHDG. It states that CCM_CLKx_P/N can be used as an output. How can this be done? The IMX6 reference manual does not even mention CCM_CLKx_P/N. Can someone post the steps to set them as outputs and rout an internal clock to them? NOTE: I am not talking about CCM_CLKOx!! I am talking about CCM_CLK1_N/P pads P16 and P17 on imx6 MCIMX6Y2. Thank you.   Re: CCM_CLK1_N/P pads P16 and P17 on imx6 MCIMX6Y2 how to use as an output? I was able to output XTAL. Thank you. Re: CCM_CLK1_N/P pads P16 and P17 on imx6 MCIMX6Y2 how to use as an output? Hello @Kevin16  I hope you are doing well. This can be configured from LVDS1_CLK_SEL and LVDSCLK1_OBEN: Best regards, Salas.

Inner row pad size for HDQFP100 Hi, I want to use S32K312NHT0MPAST with HDQFP100 package but I found different footprints for it over the site and I wondered which one is more accurate. My concern is about the inner pins length. In two of them the inner row has exactly the same size as the outer row but there is a footprint which the inner row is shorter (just for 100pin package). Here are the things I found: 1- https://www.nxp.com/part/S32K312NHT0MPAST in the package part the footprint which is provided by the link has the same size (inner and outer rows). 2- https://www.nxp.com/webapp/Download?colCode=S32K3_HW-DesignPackage The inner row for the 100pin package is shorter that the outer row 3- https://www.nxp.com/docs/en/package-information/SOT2045-1.pdf both of the rows have the same size Which one is more accurate? Thanks Re: Inner row pad size for HDQFP100 Seems like error in the model. I will report it. Anyway pdf drawings are relevant, I would recommend to follow that. Re: Inner row pad size for HDQFP100 Pads are shown by arrow. As you can see, in the second one the inner row is shorter that the outer one.        Re: Inner row pad size for HDQFP100 Could you mark on the screenshot what exactly you have on your mind? At least both pdfs (points 2 and 3) seems to be the same.

88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hi, I am using imx8mp with 88w8997 wifi/BT AW-CM276 module for wifi connectivity and bluetooth. we are loadin the firmware "sdsd8997_combo_v4.bin" to the wifi/bt module. after the wifi connection is on going an error is occuring which is find from the dmesg. can you please help me with this? error log ******************************** 10-08 04:37:47.070 4108 4108 W CMD_RESP: cmd 0x256 error, result=0x2 wlan_process_cmdresp_error 10-08 04:37:47.078 4108 4108 E IOCTL failed: 00000000fe461547 id=0x50000, sub_id=0x50009 action=2, status_code=0x3 10-08 04:37:47.087 363 363 E : get link layer statistic fail 10-08 04:37:46.920 571 682 E WifiVendorHal: getWifiLinkLayerStats_1_6_Internal(l.1199) failed {.code = ERROR_UNKNOWN, .description = unknown} Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hi @shaun_wu  we have added the mbtchar driver from the Android 11 , and done some modification in the Bluetooth HAL , right now the we are able to up and run the bluetooth in our device with same "sdsd8997_combo_v4.bin" . Thank you Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hello @jeevanefx123  for driver download: git clone http://source.codeaurora.org/external/imx/mwifiex Best Regards Shaun Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" HI @shaun_wu  can you please mention the driver for the same.? Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" Hello @jeevanefx123  Please try following firmware: imx-firmware/nxp/FwImage_8997_SD/sdiouart8997_combo_v4.bin at lf-5.15.71_2.2.0 · nxp-imx/imx-firmware · GitHub Best Regards Shaun Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hi @shaun_wu , I have loaded this firmware , and i am able to connect both bluetooth and wifi simultaneously. ANd it is working fine.  So you are saying that the above issue is related to using the sdsd8997_combo_v4.bin firmware right? Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" Hello @jeevanefx123  "sdsd8997_combo_v4.bin" this firmware is for sd-bt. AW-CM276 is not support BT with SD interface. Your Wi-Fi is SD interface, so Wi-Fi no problem. If you run BT, there will be problem. Best Regards Shaun Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hi @shaun_wu , This is the log of Wifi and bt driver loading 01-01 00:00:07.276 178 178 F wlan : Loading MWLAN driver 01-01 00:00:07.281 178 178 F wlan : Register to Bus Driver... 01-01 00:00:07.286 178 178 F wlan : Register to SDIO_MMC Bus Driver 01-01 00:00:07.292 178 178 F : vendor=0x02DF device=0x9141 class=0 function=1 01-01 00:00:07.298 178 178 F : Attach moal handle ops, card interface type: 0x104 01-01 00:00:07.305 178 178 F : rps set to 0 from module param 01-01 00:00:07.311 178 178 F SD8997 : init module param from usr cfg 01-01 00:00:07.317 178 178 F card_type: SD8997, config block: 0 01-01 00:00:07.322 178 178 F : cfg80211_wext=0xf 01-01 00:00:07.326 178 178 F : sta_name=wlan 01-01 00:00:07.329 178 178 F : uap_name=wlan 01-01 00:00:07.332 178 178 F : wfd_name=p2p 01-01 00:00:07.336 178 178 F : max_vir_bss=1 01-01 00:00:07.339 178 178 F : cal_data_cfg=none 01-01 00:00:07.342 178 178 F : ps_mode = 1 01-01 00:00:07.346 178 178 F : auto_ds = 1 01-01 00:00:07.349 178 178 F : host_mlme=enable 01-01 00:00:07.352 178 178 F : fw_name=nxp/sdsd8997_combo_v4.bin 01-01 00:00:07.358 178 178 F SDIO : max_segs=128 max_seg_size=65535 01-01 00:00:07.363 178 178 F : rx_work=1 cpu_num=4 01-01 00:00:07.367 178 178 W : Attach mlan adapter operations.card_type is 0x104. 01-01 00:00:07.379 178 178 W wlan : Enable TX SG mode 01-01 00:00:07.383 178 178 W wlan : Enable RX SG mode 01-01 00:00:07.394 178 178 F Request firmware: nxp/sdsd8997_combo_v4.bin 01-01 00:00:07.415 178 178 W : mlan_dnld_fw 01-01 00:00:07.423 178 178 W : Check if firmware is already running 01-01 00:00:07.429 178 178 W wlan_sdio_check_fw_status: Wait for firmware initialization event 01-01 00:00:07.486 1 1 E pstore : crypto_comp_decompress failed, ret = -22! 01-01 00:00:07.503 1 1 I : Registered swp emulation handler 01-01 00:00:07.610 186 186 I logd.auditd: start 01-01 00:00:07.613 193 193 I watchdogd: watchdogd started (interval 10, margin 20)! 01-01 00:00:07.644 186 186 I logd : Loaded bug_map file: /vendor/etc/selinux/selinux_denial_metadata 01-01 00:00:07.653 186 186 I logd : Loaded bug_map file: /system/etc/selinux/bug_map 01-01 00:00:07.809 1 1 I zram0 : detected capacity change from 0 to 1228800 01-01 00:00:07.842 1 1 I mkswap : Swapspace size: 614396k, UUID=610c7397-03f1-42a0-926f-30c0925d3fad 01-01 00:00:07.872 1 1 I : Adding 614396k swap on /dev/block/zram0. Priority:-2 extents:1 across:614396k SS 01-01 00:00:08.033 224 224 D vdc : Waited 0ms for vold 01-01 00:00:08.086 233 233 D vdc : Waited 0ms for vold 01-01 00:00:08.217 201 201 I fsck.f2fs: Info: Fix the reported corruption. 01-01 00:00:08.223 201 201 I fsck.f2fs: Info: not exist /proc/version! 01-01 00:00:08.229 201 201 I fsck.f2fs: Info: Segments per section = 1 01-01 00:00:08.235 201 201 I fsck.f2fs: Info: Sections per zone = 1 01-01 00:00:08.240 201 201 I fsck.f2fs: Info: sector size = 4096 01-01 00:00:08.246 201 201 I fsck.f2fs: Info: total sectors = 6197760 (24210 MB) 01-01 00:00:08.252 201 201 I fsck.f2fs: Info: MKFS version 01-01 00:00:08.257 201 201 I fsck.f2fs: "5.15.74-gd14ab594eb48-dirty" 01-01 00:00:08.263 201 201 I fsck.f2fs: Info: FSCK version 01-01 00:00:08.268 201 201 I fsck.f2fs: from "5.15.74-gd14ab594eb48-dirty" 01-01 00:00:08.358 201 201 I F2FS-fs (dm-38): Using encoding defined by superblock: utf8-12.1.0 with flags 0x0 01-01 00:00:08.453 201 201 I F2FS-fs (dm-38): recover_inode: ino = 317d, name = , inline = 21 01-01 00:00:08.462 201 201 I F2FS-fs (dm-38): recover_data: ino = 317d (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.472 201 201 I F2FS-fs (dm-38): recover_inode: ino = 1d1a, name = , inline = 21 01-01 00:00:08.480 201 201 I F2FS-fs (dm-38): recover_data: ino = 1d1a (i_size: recover) recovered = 0, err = 0 01-01 00:00:08.490 201 201 I F2FS-fs (dm-38): recover_inode: ino = 317e, name = , inline = 21 01-01 00:00:08.499 201 201 I F2FS-fs (dm-38): recover_dentry: ino = 317e, name = , dir = 177a, err = 0 01-01 00:00:08.509 201 201 I F2FS-fs (dm-38): recover_data: ino = 317e (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.518 201 201 I F2FS-fs (dm-38): recover_inode: ino = 3177, name = , inline = 21 01-01 00:00:08.527 201 201 I F2FS-fs (dm-38): recover_data: ino = 3177 (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.536 201 201 I F2FS-fs (dm-38): recover_inode: ino = 1d1a, name = , inline = 21 01-01 00:00:08.545 201 201 I F2FS-fs (dm-38): recover_data: ino = 1d1a (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.561 201 201 I F2FS-fs (dm-38): checkpoint: version = 276aec00 01-01 00:00:08.568 201 201 I F2FS-fs (dm-38): Mounted with checkpoint version = 276aec00 01-01 00:00:08.569 178 178 W Wlan : FW download over, firmwarelen=623240 downloaded 623240 01-01 00:00:08.582 178 178 W wlan_sdio_check_fw_status: Wait for firmware initialization event 01-01 00:00:08.647 259 259 D vdc : Waited 0ms for vold 01-01 00:00:08.673 1 1 I fscrypt : AES-256-CTS-CBC using implementation "cts-cbc-aes-ce" 01-01 00:00:08.776 201 201 E vold : keystore2 Keystore earlyBootEnded returned service specific error: -68 01-01 00:00:08.836 199 199 I logd : logd reinit 01-01 00:00:08.843 199 199 E logd : FrameworkListener: read() failed (Connection reset by peer) 01-01 00:00:08.843 268 268 I apexd : Scanning /system/apex for pre-installed ApexFiles 01-01 00:00:08.859 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.adbd.capex 01-01 00:00:08.867 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.adservices.capex 01-01 00:00:08.877 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.apex.cts.shim.apex 01-01 00:00:08.886 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.appsearch.apex 01-01 00:00:08.895 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.art.capex 01-01 00:00:08.904 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.btservices.apex 01-01 00:00:08.913 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.car.framework.apex 01-01 00:00:08.922 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.cellbroadcast.capex 01-01 00:00:08.931 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.conscrypt.capex 01-01 00:00:09.069 270 270 I loop4 : detected capacity change from 0 to 41784 01-01 00:00:09.077 271 271 I loop5 : detected capacity change from 0 to 6952 01-01 00:00:09.139 270 270 I EXT4-fs (loop4): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.140 271 271 I EXT4-fs (loop5): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.152 270 270 I loop6 : detected capacity change from 0 to 12952 01-01 00:00:09.165 271 271 I loop7 : detected capacity change from 0 to 536 01-01 00:00:09.219 270 270 I EXT4-fs (loop6): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.234 270 270 I loop8 : detected capacity change from 0 to 1728 01-01 00:00:09.237 271 271 I EXT4-fs (loop7): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.254 271 271 I loop9 : detected capacity change from 0 to 536 01-01 00:00:09.296 270 270 I EXT4-fs (loop8): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.307 270 270 I loop10 : detected capacity change from 0 to 74600 01-01 00:00:09.341 271 271 I EXT4-fs (loop9): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.352 271 271 I loop11 : detected capacity change from 0 to 96704 01-01 00:00:09.371 270 270 I EXT4-fs (loop10): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.383 270 270 I loop12 : detected capacity change from 0 to 3920 01-01 00:00:09.411 271 271 I EXT4-fs (loop11): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.420 178 178 F : WLAN FW is active 01-01 00:00:09.422 271 271 I loop13 : detected capacity change from 0 to 16240 01-01 00:00:09.425 178 178 F : on_time is 9252720625 01-01 00:00:09.442 270 270 I EXT4-fs (loop12): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.454 270 270 I loop14 : detected capacity change from 0 to 536 01-01 00:00:09.476 66 66 W : fw_cap_info=0x18fcffa3, dev_cap_mask=0xffffffff 01-01 00:00:09.483 66 66 W : max_p2p_conn = 8, max_sta_conn = 8 01-01 00:00:09.500 178 178 F : Register NXP 802.11 Adapter wlan0 01-01 00:00:09.506 178 178 F wlan : wlan%d set max_mtu 2000 01-01 00:00:09.511 271 271 I EXT4-fs (loop13): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.512 178 178 F : Register NXP 802.11 Adapter wlan1 01-01 00:00:09.522 271 271 I loop15 : detected capacity change from 0 to 1536 01-01 00:00:09.523 270 270 I EXT4-fs (loop14): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.531 178 178 F : Register NXP 802.11 Adapter p2p0 01-01 00:00:09.533 270 270 I loop16 : detected capacity change from 0 to 17256 01-01 00:00:09.542 178 178 F wlan : version = SD8997----16.68.1.p197-MM5X16368.p2-GPL-(FP92) 01-01 00:00:09.562 178 178 E WLAN : SDIO Driver Registration SUCCESS 01-01 00:00:09.568 178 178 F wlan : Register to Bus Driver Done 01-01 00:00:09.573 178 178 F wlan : Driver loaded successfully 01-01 00:00:09.584 178 178 F BT : Loading driver 01-01 00:00:09.597 178 178 F : BT FW is active(0) 01-01 00:00:09.601 270 270 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:09.601 178 178 F BT : FW already downloaded! 01-01 00:00:09.619 271 271 I EXT4-fs (loop15): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.630 271 271 I loop17 : detected capacity change from 0 to 40512 01-01 00:00:09.630 178 178 F BT : Create /dev/mbtchar0 01-01 00:00:09.640 270 270 I EXT4-fs (dm-36): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.653 270 270 I loop18 : detected capacity change from 0 to 17128 01-01 00:00:09.677 271 271 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:09.705 178 178 F BT : Create /dev/mdebugchar0 01-01 00:00:09.709 270 270 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:09.728 271 271 I EXT4-fs (dm-35): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.732 270 270 I EXT4-fs (dm-34): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.734 270 270 I loop19 : detected capacity change from 0 to 29504 01-01 00:00:09.744 178 178 F BT : Driver loaded successfully Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hi @shaun_wu , From the below logs you can see both bluetooth and wifi drivers are up and running. --------- beginning of kernel 01-01 00:00:00.000 0 0 I : Booting Linux on physical CPU 0x0000000000 [0x410fd034] 01-01 00:00:00.000 0 0 I : Linux version 5.15.74-gd14ab594eb48-dirty (jeevan@EFXSEZPC024) (Android (8508608, based on r450784e) clang version 14.0.7 (https://android.googlesource.com/toolchain/llvm-project 4c603efb0cca074e9238af8b4106c30add4418f6), LLD 14.0.7) #22 SMP PREEMPT Fri Sep 27 21:46:43 IST 2024 01-01 00:00:00.000 0 0 I Machine model: ADLINK LEC-iMX8MP SOM module 01-01 00:00:00.000 0 0 I : Stack Depot is disabled 01-01 00:00:00.000 0 0 I earlycon: ec_imx6q0 at MMIO 0x0000000030890000 (options '115200') 01-01 00:00:00.000 0 0 I printk : bootconsole [ec_imx6q0] enabled 01-01 00:00:00.000 0 0 I efi : UEFI not found. 01-01 00:00:00.000 0 0 I Reserved memory: created DMA memory pool at 0x0000000094300000, size 1 MiB 01-01 00:00:00.000 0 0 I OF : reserved mem: initialized node vdev0buffer@94300000, compatible id shared-dma-pool 01-01 00:00:00.000 0 0 I kvm [0] : Reserved 16 MiB at 0xbec00000 01-01 00:00:00.000 0 0 I Zone ranges: 01-01 00:00:00.000 0 0 I : DMA32 [mem 0x0000000040000000-0x00000000bfffffff] 01-01 00:00:00.000 0 0 I : Normal empty 01-01 00:00:00.000 0 0 I : Movable zone start for each node 01-01 00:00:00.000 0 0 I : Early memory node ranges 01-01 00:00:00.000 0 0 I node 0: [mem 0x0000000040000000-0x00000000557fffff] 01-01 00:00:00.000 0 0 I node 0: [mem 0x0000000055800000-0x0000000055ffffff] 01-01 00:00:00.000 0 0 I node 0: [mem 0x0000000056000000-0x00000000823fffff] 01-01 00:00:00.000 0 0 I node 0: [mem 0x0000000082400000-0x00000000943fffff] 01-01 00:00:00.000 0 0 I node 0: [mem 0x0000000094400000-0x00000000bfffffff] 01-01 00:00:00.000 0 0 I : Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff] 01-01 00:00:00.000 0 0 I cma : Reserved 400 MiB at 0x000000009f000000 01-01 00:00:00.000 0 0 I psci : probing for conduit method from DT. 01-01 00:00:00.000 0 0 I psci : PSCIv1.1 detected in firmware. 01-01 00:00:00.000 0 0 I psci : Using standard PSCI v0.2 function IDs 01-01 00:00:00.000 0 0 I psci : MIGRATE_INFO_TYPE not supported. 01-01 00:00:00.000 0 0 I psci : SMC Calling Convention v1.2 01-01 00:00:00.000 0 0 I Load bootconfig: 1030 bytes 65 nodes 01-01 00:00:00.000 0 0 I percpu : Embedded 29 pages/cpu s81816 r8192 d28776 u118784 01-01 00:00:00.000 0 0 D pcpu-alloc: s81816 r8192 d28776 u118784 alloc=29*4096 01-01 00:00:00.000 0 0 D pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 01-01 00:00:00.000 0 0 I : Detected VIPT I-cache on CPU0 01-01 00:00:00.000 0 0 W CPU features: SYS_ID_AA64MMFR1_EL1[11:8]: already set to 0 01-01 00:00:00.000 0 0 I CPU features: detected: GIC system register CPU interface 01-01 00:00:00.000 0 0 I CPU features: detected: ARM erratum 845719 01-01 00:00:00.000 0 0 I : Built 1 zonelists, mobility grouping on. Total pages: 516096 01-01 00:00:00.000 0 0 I : Kernel command line: stack_depot_disable=on kasan.stacktrace=off kvm-arm.mode=protected cgroup_disable=pressure console=ttymxc1,115200 earlycon=ec_imx6q,0x30890000,115200 init=/init firmware_class.path=/vendor/firmware loop.max_part=7 bootconfig transparent_hugepage=never swiotlb=65536 androidboot.selinux=permissive moal.mod_para=wifi_mod_para.conf pci=nomsi cma=400M@0x400M-0xb80M galcore.contiguousSize=33554432 bootconfig buildvariant=userdebug 01-01 00:00:00.000 0 0 I cgroup : Disabling pressure control group feature 01-01 00:00:00.000 0 0 I : Unknown kernel command line parameters "buildvariant=userdebug", will be passed to user space. 01-01 00:00:00.000 0 0 I : Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) 01-01 00:00:00.000 0 0 I : Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear) 01-01 00:00:00.000 0 0 I mem auto-init: stack:all(zero), heap alloc:on, heap free:off 01-01 00:00:00.000 0 0 I Memory : 1262660K/2097152K available (18112K kernel code, 2238K rwdata, 18812K rodata, 1408K init, 604K bss, 424892K reserved, 409600K cma-reserved) 01-01 00:00:00.000 0 0 I SLUB : HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 01-01 00:00:00.000 0 0 I : trace event string verifier disabled 01-01 00:00:00.000 0 0 I rcu : Preemptible hierarchical RCU implementation. 01-01 00:00:00.000 0 0 I rcu : RCU event tracing is enabled. 01-01 00:00:00.000 0 0 I rcu : RCU dyntick-idle grace-period acceleration is enabled. 01-01 00:00:00.000 0 0 I rcu : RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=4. 01-01 00:00:00.000 0 0 I rcu : RCU priority boosting: priority 1 delay 500 ms. 01-01 00:00:00.000 0 0 I : Trampoline variant of Tasks RCU enabled. 01-01 00:00:00.000 0 0 I : Tracing variant of Tasks RCU enabled. 01-01 00:00:00.000 0 0 I rcu : RCU calculated value of scheduler-enlistment delay is 25 jiffies. 01-01 00:00:00.000 0 0 I rcu : Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 01-01 00:00:00.000 0 0 I NR_IRQS : 64, nr_irqs: 64, preallocated irqs: 0 01-01 00:00:00.000 0 0 I GICv3 : GIC: Using split EOI/Deactivate mode 01-01 00:00:00.000 0 0 I GICv3 : 160 SPIs implemented 01-01 00:00:00.000 0 0 I GICv3 : 0 Extended SPIs implemented 01-01 00:00:00.000 0 0 I GICv3 : Distributor has no Range Selector support 01-01 00:00:00.000 0 0 I : Root IRQ handler: gic_handle_irq.10d7cf410c142aff6d31b6303c3f9f87.cfi_jt 01-01 00:00:00.000 0 0 I GICv3 : 16 PPIs implemented 01-01 00:00:00.000 0 0 I GICv3 : CPU0: found redistributor 0 region 0:0x0000000038880000 01-01 00:00:00.000 0 0 W ITS : No ITS available, not enabling LPIs 01-01 00:00:00.000 0 0 I rcu : Offload RCU callbacks from CPUs: (none). 01-01 00:00:00.000 0 0 I kfence : initialized - using 524288 bytes for 63 objects at 0x(____ptrval____)-0x(____ptrval____) 01-01 00:00:00.000 0 0 I arch_timer: cp15 timer(s) running at 8.00MHz (phys). 01-01 00:00:00.000 0 0 I clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns 01-01 00:00:00.000 0 0 I sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns 01-01 00:00:00.009 0 0 I : Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) 01-01 00:00:00.019 0 0 I pid_max : default: 32768 minimum: 301 01-01 00:00:00.025 0 0 I LSM : Security Framework initializing 01-01 00:00:00.030 0 0 I SELinux : Initializing. 01-01 00:00:00.034 0 0 I : Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) 01-01 00:00:00.042 0 0 I : Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear) 01-01 00:00:00.053 1 1 I rcu : Hierarchical SRCU implementation. 01-01 00:00:00.057 1 1 I dyndbg : Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build 01-01 00:00:00.065 1 1 I : EFI services will not be available. 01-01 00:00:00.070 1 1 I smp : Bringing up secondary CPUs ... 01-01 00:00:00.076 0 0 I : Detected VIPT I-cache on CPU1 01-01 00:00:00.076 0 0 I GICv3 : CPU1: found redistributor 1 region 0:0x00000000388a0000 01-01 00:00:00.076 0 0 I CPU1 : Booted secondary processor 0x0000000001 [0x410fd034] 01-01 00:00:00.077 0 0 I : Detected VIPT I-cache on CPU2 01-01 00:00:00.077 0 0 I GICv3 : CPU2: found redistributor 2 region 0:0x00000000388c0000 01-01 00:00:00.077 0 0 I CPU2 : Booted secondary processor 0x0000000002 [0x410fd034] 01-01 00:00:00.078 0 0 I : Detected VIPT I-cache on CPU3 01-01 00:00:00.078 0 0 I GICv3 : CPU3: found redistributor 3 region 0:0x00000000388e0000 01-01 00:00:00.078 0 0 I CPU3 : Booted secondary processor 0x0000000003 [0x410fd034] 01-01 00:00:00.078 1 1 I smp : Brought up 1 node, 4 CPUs 01-01 00:00:00.139 1 1 I SMP : Total of 4 processors activated. 01-01 00:00:00.144 1 1 I CPU features: detected: 32-bit EL0 Support 01-01 00:00:00.150 1 1 I CPU features: detected: 32-bit EL1 Support 01-01 00:00:00.156 1 1 I CPU features: detected: CRC32 instructions 01-01 00:00:00.162 1 1 I CPU features: detected: Protected KVM 01-01 00:00:00.167 1 1 I CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching 01-01 00:00:00.187 1 1 I : CPU: All CPU(s) started at EL2 01-01 00:00:00.189 19 19 I alternatives: patching kernel code 01-01 00:00:00.210 1 1 I : Registered cp15_barrier emulation handler 01-01 00:00:00.213 1 1 I : Registered setend emulation handler 01-01 00:00:00.218 1 1 W : KASLR disabled due to lack of seed 01-01 00:00:00.223 1 1 I clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns 01-01 00:00:00.234 1 1 I : futex hash table entries: 1024 (order: 4, 65536 bytes, linear) 01-01 00:00:00.254 1 1 I pinctrl core: initialized pinctrl subsystem 01-01 00:00:00.259 1 1 I NET : Registered PF_NETLINK/PF_ROUTE protocol family 01-01 00:00:00.266 1 1 I DMA : preallocated 256 KiB GFP_KERNEL pool for atomic allocations 01-01 00:00:00.272 1 1 I DMA : preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations 01-01 00:00:00.280 1 1 I audit : initializing netlink subsys (disabled) 01-01 00:00:00.287 1 1 I thermal_sys: Registered thermal governor 'step_wise' 01-01 00:00:00.295 1 1 I thermal_sys: Registered thermal governor 'user_space' 01-01 00:00:00.302 1 1 I thermal_sys: Registered thermal governor 'power_allocator' 01-01 00:00:00.309 1 1 I cpuidle : using governor menu 01-01 00:00:00.321 1 1 I hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. 01-01 00:00:00.328 1 1 I : ASID allocator initialised with 65536 entries 01-01 00:00:00.334 1 1 I Serial : AMBA PL011 UART driver 01-01 00:00:00.339 1 1 I : imx rpmsg driver is registered. 01-01 00:00:00.348 1 1 I printk : console [ramoops-1] enabled 01-01 00:00:00.351 1 1 I pstore : Registered ramoops as persistent store backend 01-01 00:00:00.358 1 1 I ramoops : using 0x100000@0x94400000, ecc: 0 01-01 00:00:00.397 1 1 I platform 32fd8000.hdmi: Fixing up cyclic dependency with 32fc6000.lcd-controller 01-01 00:00:00.425 1 1 I iommu : Default domain type: Translated 01-01 00:00:00.427 1 1 I iommu : DMA domain TLB invalidation policy: strict mode 01-01 00:00:00.435 1 1 I : SCSI subsystem initialized 01-01 00:00:00.439 1 1 I usbcore : registered new interface driver usbfs 01-01 00:00:00.445 1 1 I usbcore : registered new interface driver hub 01-01 00:00:00.451 1 1 I usbcore : registered new device driver usb 01-01 00:00:00.457 1 1 I mc : Linux media interface: v0.10 01-01 00:00:00.462 1 1 I videodev: Linux video capture interface: v2.00 01-01 00:00:00.468 1 1 I pps_core: LinuxPPS API ver. 1 registered 01-01 00:00:00.474 1 1 I pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti 01-01 00:00:00.484 1 1 I : PTP clock support registered 01-01 00:00:00.488 1 1 I EDAC MC : Ver: 3.0.0 01-01 00:00:00.493 1 1 I : FPGA manager framework 01-01 00:00:00.496 1 1 I : Advanced Linux Sound Architecture Driver Initialized. 01-01 00:00:00.504 1 1 I Bluetooth: Core ver 2.22 01-01 00:00:00.507 1 1 I NET : Registered PF_BLUETOOTH protocol family 01-01 00:00:00.513 1 1 I Bluetooth: HCI device and connection manager initialized 01-01 00:00:00.520 1 1 I Bluetooth: HCI socket layer initialized 01-01 00:00:00.526 1 1 I Bluetooth: L2CAP socket layer initialized 01-01 00:00:00.532 1 1 I Bluetooth: SCO socket layer initialized 01-01 00:00:00.538 1 1 I nfc : nfc_init: NFC Core ver 0.1 01-01 00:00:00.542 1 1 I NET : Registered PF_NFC protocol family 01-01 00:00:00.548 1 1 I clocksource: Switched to clocksource arch_sys_counter 01-01 00:00:00.607 1 1 I VFS : Disk quotas dquot_6.6.0 01-01 00:00:00.609 1 1 I VFS : Dquot-cache hash table entries: 512 (order 0, 4096 bytes) 01-01 00:00:00.617 1 1 I NET : Registered PF_INET protocol family 01-01 00:00:00.622 1 1 I : IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear) 01-01 00:00:00.631 1 1 I : tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear) 01-01 00:00:00.639 1 1 I : Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) 01-01 00:00:00.648 1 1 I : TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear) 01-01 00:00:00.656 1 1 I : TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear) 01-01 00:00:00.665 1 1 I TCP : Hash tables configured (established 16384 bind 16384) 01-01 00:00:00.672 1 1 I : UDP hash table entries: 1024 (order: 3, 32768 bytes, linear) 01-01 00:00:00.679 1 1 I : UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear) 01-01 00:00:00.687 1 1 I NET : Registered PF_UNIX/PF_LOCAL protocol family 01-01 00:00:00.693 1 1 I NET : Registered PF_XDP protocol family 01-01 00:00:00.699 1 1 I PCI : CLS 0 bytes, default 64 01-01 00:00:00.704 8 8 I : Trying to unpack rootfs image as initramfs... 01-01 00:00:00.710 1 1 I hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available 01-01 00:00:00.720 1 1 I kvm [1] : IPA Size Limit: 40 bits 01-01 00:00:00.739 1 1 I kvm [1] : GICv3: no GICV resource entry 01-01 00:00:00.742 1 1 I kvm [1] : disabling GICv2 emulation 01-01 00:00:00.747 1 1 I kvm [1] : GIC system register CPU interface enabled 01-01 00:00:00.754 1 1 I kvm [1] : vgic interrupt IRQ9 01-01 00:00:00.758 1 1 I kvm [1] : Protected nVHE mode initialized successfully 01-01 00:00:00.767 1 1 I : Initialise system trusted keyrings 01-01 00:00:00.771 1 1 I workingset: timestamp_bits=46 max_order=19 bucket_order=0 01-01 00:00:00.788 1 1 I fuse : init (API version 7.36) 01-01 00:00:00.831 1 1 I : Key type asymmetric registered 01-01 00:00:00.833 1 1 I : Asymmetric key parser 'x509' registered 01-01 00:00:00.839 1 1 I : Block layer SCSI generic (bsg) driver version 0.4 loaded (major 237) 01-01 00:00:00.847 1 1 I : io scheduler mq-deadline registered 01-01 00:00:00.852 1 1 I : io scheduler kyber registered 01-01 00:00:00.857 1 1 I : io scheduler bfq registered 01-01 00:00:00.879 1 1 I brd : module loaded 01-01 00:00:00.893 1 1 I loop : module loaded 01-01 00:00:00.897 1 1 I wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. 01-01 00:00:00.903 1 1 I wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved. 01-01 00:00:00.914 1 1 I : MACsec IEEE 802.1AE 01-01 00:00:00.918 1 1 I tun : Universal TUN/TAP device driver, 1.6 01-01 00:00:00.923 1 1 I : PPP generic driver version 2.4.2 01-01 00:00:00.928 1 1 I : PPP BSD Compression module registered 01-01 00:00:00.933 1 1 I : PPP Deflate Compression module registered 01-01 00:00:00.939 1 1 I : PPP MPPE Compression module registered 01-01 00:00:00.945 1 1 I NET : Registered PF_PPPOX protocol family 01-01 00:00:00.950 1 1 I : PPTP driver version 0.8.5 01-01 00:00:00.955 1 1 I usbcore : registered new interface driver rtl8150 01-01 00:00:00.961 1 1 I usbcore : registered new interface driver r8152 01-01 00:00:00.967 1 1 I usbcore : registered new interface driver asix 01-01 00:00:00.974 1 1 I usbcore : registered new interface driver ax88179_178a 01-01 00:00:00.980 1 1 I usbcore : registered new interface driver cdc_ether 01-01 00:00:00.987 1 1 I usbcore : registered new interface driver cdc_eem 01-01 00:00:00.989 8 8 I : Freeing initrd memory: 22260K 01-01 00:00:00.993 1 1 I usbcore : registered new interface driver cdc_ncm 01-01 00:00:01.004 1 1 I usbcore : registered new interface driver aqc111 01-01 00:00:01.011 1 1 I usbcore : registered new interface driver r8153_ecm 01-01 00:00:01.019 1 1 I ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver 01-01 00:00:01.024 1 1 I ehci-pci: EHCI PCI platform driver 01-01 00:00:01.030 1 1 I ehci-platform: EHCI generic platform driver 01-01 00:00:01.036 1 1 I usbcore : registered new interface driver cdc_acm 01-01 00:00:01.042 1 1 I cdc_acm : USB Abstract Control Model driver for USB modems and ISDN adapters 01-01 00:00:01.051 1 1 I usbcore : registered new interface driver uas 01-01 00:00:01.057 1 1 I usbcore : registered new interface driver usb-storage 01-01 00:00:01.064 1 1 I usbcore : registered new interface driver xpad 01-01 00:00:01.070 1 1 I usbcore : registered new interface driver uvcvideo 01-01 00:00:01.076 1 1 I gspca_main: v2.14.0 registered 01-01 00:00:01.081 1 1 I device-mapper: uevent: version 1.0.3 01-01 00:00:01.086 1 1 I device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: [email protected] 01-01 00:00:01.096 1 1 I Bluetooth: HCI UART driver ver 2.3 01-01 00:00:01.101 1 1 I Bluetooth: HCI UART protocol H4 registered 01-01 00:00:01.106 1 1 I Bluetooth: HCI UART protocol LL registered 01-01 00:00:01.112 1 1 I Bluetooth: HCI UART protocol Broadcom registered 01-01 00:00:01.119 1 1 I Bluetooth: HCI UART protocol QCA registered 01-01 00:00:01.125 1 1 I sdhci : Secure Digital Host Controller Interface driver 01-01 00:00:01.132 1 1 I sdhci : Copyright(c) Pierre Ossman 01-01 00:00:01.137 1 1 I sdhci-pltfm: SDHCI platform and OF driver helper 01-01 00:00:01.143 1 1 I SMCCC : SOC_ID: ARCH_SOC_ID not implemented, skipping .... 01-01 00:00:01.150 1 1 I hid : raw HID events driver (C) Jiri Kosina 01-01 00:00:01.157 1 1 I usbcore : registered new interface driver usbhid 01-01 00:00:01.162 1 1 I usbhid : USB HID core driver 01-01 00:00:01.167 1 1 I ashmem : initialized 01-01 00:00:01.171 1 1 I gnss : GNSS driver registered with major 507 01-01 00:00:01.177 1 1 I usbcore : registered new interface driver snd-usb-audio 01-01 00:00:01.184 1 1 I : GACT probability NOT on 01-01 00:00:01.188 1 1 I : Mirror/redirect action on 01-01 00:00:01.192 1 1 I netem : version 1.3 01-01 00:00:01.196 1 1 I : u32 classifier 01-01 00:00:01.199 1 1 I : input device check on 01-01 00:00:01.204 1 1 I : Actions configured 01-01 00:00:01.209 1 1 I xt_time : kernel timezone is -0000 01-01 00:00:01.213 1 1 I ipip : IPv4 and MPLS over IPv4 tunneling driver 01-01 00:00:01.220 1 1 I gre : GRE over IPv4 demultiplexor driver 01-01 00:00:01.225 1 1 I ip_gre : GRE over IPv4 tunneling driver 01-01 00:00:01.231 1 1 I : IPv4 over IPsec tunneling driver 01-01 00:00:01.236 1 1 I : Initializing XFRM netlink socket 01-01 00:00:01.240 1 1 I : IPsec XFRM device driver 01-01 00:00:01.245 1 1 I NET : Registered PF_INET6 protocol family 01-01 00:00:01.252 1 1 I : Segment Routing with IPv6 01-01 00:00:01.255 1 1 I : In-situ OAM (IOAM) with IPv6 01-01 00:00:01.259 1 1 I mip6 : Mobile IPv6 01-01 00:00:01.264 1 1 I sit : IPv6, IPv4 and MPLS over IPv4 tunneling driver 01-01 00:00:01.270 1 1 I ip6_gre : GRE over IPv6 tunneling driver 01-01 00:00:01.276 1 1 I NET : Registered PF_PACKET protocol family 01-01 00:00:01.281 1 1 I NET : Registered PF_KEY protocol family 01-01 00:00:01.287 1 1 I can : controller area network core 01-01 00:00:01.292 1 1 I NET : Registered PF_CAN protocol family 01-01 00:00:01.298 1 1 I Bluetooth: RFCOMM TTY layer initialized 01-01 00:00:01.303 1 1 I Bluetooth: RFCOMM socket layer initialized 01-01 00:00:01.308 1 1 I Bluetooth: RFCOMM ver 1.11 01-01 00:00:01.313 1 1 I Bluetooth: HIDP (Human Interface Emulation) ver 1.2 01-01 00:00:01.320 1 1 I Bluetooth: HIDP socket layer initialized 01-01 00:00:01.325 1 1 I l2tp_core: L2TP core driver, V2.0 01-01 00:00:01.330 1 1 I l2tp_ppp: PPPoL2TP kernel driver, V2.0 01-01 00:00:01.336 1 1 I 8021q : 802.1Q VLAN Support v1.8 01-01 00:00:01.341 1 1 I tipc : Activated (version 2.0.0) 01-01 00:00:01.346 1 1 I NET : Registered PF_TIPC protocol family 01-01 00:00:01.351 1 1 I tipc : Started in single node mode 01-01 00:00:01.357 1 1 I NET : Registered PF_IEEE802154 protocol family 01-01 00:00:01.363 1 1 I NET : Registered PF_VSOCK protocol family 01-01 00:00:01.369 1 1 I : registered taskstats version 1 01-01 00:00:01.373 1 1 I : Loading compiled-in X.509 certificates 01-01 00:00:01.380 65 65 I : cryptomgr_probe (65) used greatest stack depth: 14032 bytes left 01-01 00:00:01.382 1 1 I : Loaded X.509 cert 'Build time autogenerated kernel key: 1fc11d5d4d75c3373e5cabcd3a650022fc1458b5' 01-01 00:00:01.399 1 1 I : page_owner is disabled 01-01 00:00:01.401 1 1 I : Key type ._fscrypt registered 01-01 00:00:01.406 1 1 I : Key type .fscrypt registered 01-01 00:00:01.410 1 1 I : Key type fscrypt-provisioning registered 01-01 00:00:01.416 1 1 I pstore : Using crash dump compression: deflate 01-01 00:00:01.426 1 1 I : ALSA device list: 01-01 00:00:01.426 1 1 I : No soundcards found. 01-01 00:00:01.431 1 1 E : Warning: unable to open an initial console. 01-01 00:00:01.437 1 1 I : Freeing unused kernel memory: 1408K 01-01 00:00:01.469 1 1 I : Run /init as init process 01-01 00:00:01.470 1 1 D with arguments: 01-01 00:00:01.470 1 1 D : /init 01-01 00:00:01.470 1 1 D with environment: 01-01 00:00:01.470 1 1 D : HOME=/ 01-01 00:00:01.470 1 1 D : TERM=linux 01-01 00:00:01.470 1 1 D : buildvariant=userdebug 01-01 00:00:01.474 1 1 I init : init first stage started! 01-01 00:00:01.477 1 1 E init : alias lines in modules.alias must have 3 entries, not 4 01-01 00:00:01.484 1 1 E init : alias lines in modules.alias must have 3 entries, not 4 01-01 00:00:01.493 1 1 E init : alias lines in modules.alias must have 3 entries, not 4 01-01 00:00:01.500 1 1 I init : Loading module /lib/modules/zsmalloc.ko with args '' 01-01 00:00:01.506 1 1 I zsmalloc: module verification failed: signature and/or required key missing - tainting kernel 01-01 00:00:01.518 1 1 I init : Loaded kernel module /lib/modules/zsmalloc.ko 01-01 00:00:01.523 1 1 I init : Loading module /lib/modules/zram.ko with args '' 01-01 00:00:01.532 1 1 I zram : Added device: zram0 01-01 00:00:01.534 1 1 I init : Loaded kernel module /lib/modules/zram.ko 01-01 00:00:01.540 1 1 I init : Loading module /lib/modules/soc-imx8m.ko with args '' 01-01 00:00:01.549 1 1 I SoC : i.MX8MP revision 1.1 01-01 00:00:01.552 1 1 I init : Loaded kernel module /lib/modules/soc-imx8m.ko 01-01 00:00:01.607 1 1 I : Bus freq driver module loaded 01-01 00:00:01.611 1 1 E : trusty trusty: failed to get version: -1 01-01 00:00:01.615 1 1 I : trusty trusty: selected api version: 0 (requested 5) 01-01 00:00:01.628 1 1 I imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver 01-01 00:00:01.645 1 1 I 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 37, base_baud = 1500000) is a IMX 01-01 00:00:01.645 1 1 I printk : console [ttymxc1] enabled 01-01 00:00:01.653 1 1 I printk : bootconsole [ec_imx6q0] disabled 01-01 00:00:01.670 1 1 I i2c-0 : IMX I2C adapter registered 01-01 00:00:01.676 1 1 I i2c-1 : IMX I2C adapter registered 01-01 00:00:01.683 1 1 I i2c 2-003c: Fixing up cyclic dependency with 32e40000.csi 01-01 00:00:01.690 1 1 I i2c-2 : IMX I2C adapter registered 01-01 00:00:01.713 1 1 I i2c-5 : IMX I2C adapter registered 01-01 00:00:01.720 1 1 I i2c_dev : i2c /dev entries driver 01-01 00:00:01.740 1 1 I nxp-pca9450 0-0025: pca9450bc probed. 01-01 00:00:01.750 1 1 W pwm-backlight lvds_backlight: supply power not found, using dummy regulator 01-01 00:00:01.769 8 8 I sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO 01-01 00:00:01.801 10 10 I mmc0 : SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA 01-01 00:00:01.801 55 55 I mmc2 : SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA 01-01 00:00:01.810 8 8 I mmc1 : SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA 01-01 00:00:01.840 1 1 W imx8mq-usb-phy 381f0040.usb-phy: supply vbus not found, using dummy regulator 01-01 00:00:01.849 1 1 W imx8mq-usb-phy 382f0040.usb-phy: supply vbus not found, using dummy regulator 01-01 00:00:01.862 1 1 E snvs_pwrkey 30370000.snvs: snvs-powerkey: snvs pwkey: trusty driver failed to probe! nr=0xb5000000 error=-1. Use normal mode. 01-01 00:00:01.876 1 1 I input : 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 01-01 00:00:01.878 66 66 I mmc2 : new HS400 Enhanced strobe MMC card at address 0001 01-01 00:00:01.897 66 66 I mmcblk2 : mmc2:0001 IX2932 29.1 GiB 01-01 00:00:01.907 43 43 I mmc0 : new ultra high speed SDR104 SDIO card at address 0001 01-01 00:00:01.907 66 66 W : Alternate GPT is invalid, using primary GPT. 01-01 00:00:01.920 66 66 I mmcblk2 : p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 01-01 00:00:01.930 66 66 I mmcblk2boot0: mmc2:0001 IX2932 4.00 MiB 01-01 00:00:01.938 66 66 I mmcblk2boot1: mmc2:0001 IX2932 4.00 MiB 01-01 00:00:01.945 66 66 I mmcblk2rpmb: mmc2:0001 IX2932 4.00 MiB, chardev (511:0) 01-01 00:00:01.960 1 1 I dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2) 01-01 00:00:01.972 1 1 I dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver 01-01 00:00:01.988 1 1 E imx-lcdifv3 32e80000.lcd-controller: lcdif: failed to get response of echo. Use normal mode. 01-01 00:00:02.007 1 1 I imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3_crtc_ops [imx_lcdifv3_crtc]) 01-01 00:00:02.018 1 1 I imx-drm display-subsystem: bound imx-lcdifv3-crtc.1 (ops lcdifv3_crtc_ops [imx_lcdifv3_crtc]) 01-01 00:00:02.028 1 1 I imx-drm display-subsystem: bound imx-lcdifv3-crtc.2 (ops lcdifv3_crtc_ops [imx_lcdifv3_crtc]) 01-01 00:00:02.039 1 1 I imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw_hdmi_imx_ops [dw_hdmi_imx]) 01-01 00:00:02.048 1 1 I : [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0 01-01 00:00:02.079 1 1 I xhci-hcd.0.auto: xHCI Host Controller 01-01 00:00:02.085 1 1 I xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 01-01 00:00:02.094 1 1 I xhci-hcd.0.auto: hcc params 0x0220fe6d hci version 0x110 quirks 0x0000002001010010 01-01 00:00:02.104 1 1 I xhci-hcd.0.auto: irq 247, io mem 0x38200000 01-01 00:00:02.111 1 1 I xhci-hcd.0.auto: xHCI Host Controller 01-01 00:00:02.117 1 1 I xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 01-01 00:00:02.126 1 1 I xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed 01-01 00:00:02.133 1 1 I usb1 : New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 01-01 00:00:02.142 1 1 I usb1 : New USB device strings: Mfr=3, Product=2, SerialNumber=1 01-01 00:00:02.150 1 1 I usb1 : Product: xHCI Host Controller 01-01 00:00:02.155 1 1 I usb1 : Manufacturer: Linux 5.15.74-gd14ab594eb48-dirty xhci-hcd 01-01 00:00:02.163 1 1 I usb1 : SerialNumber: xhci-hcd.0.auto 01-01 00:00:02.169 1 1 I hub 1-0 : 1.0: USB hub found 01-01 00:00:02.174 1 1 I hub 1-0 : 1.0: 1 port detected 01-01 00:00:02.179 1 1 I usb2 : We don't know the algorithms for LPM for this host, disabling LPM. 01-01 00:00:02.188 1 1 I usb2 : New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15 01-01 00:00:02.197 1 1 I usb2 : New USB device strings: Mfr=3, Product=2, SerialNumber=1 01-01 00:00:02.205 1 1 I usb2 : Product: xHCI Host Controller 01-01 00:00:02.210 1 1 I usb2 : Manufacturer: Linux 5.15.74-gd14ab594eb48-dirty xhci-hcd 01-01 00:00:02.218 1 1 I usb2 : SerialNumber: xhci-hcd.0.auto 01-01 00:00:02.225 1 1 I hub 2-0 : 1.0: USB hub found 01-01 00:00:02.230 1 1 I hub 2-0 : 1.0: 1 port detected 01-01 00:00:02.240 1 1 W __power_supply_register: Expected proper parent device for 'battery' 01-01 00:00:02.249 1 1 W __power_supply_register: Expected proper parent device for 'usb' 01-01 00:00:02.268 1 1 I : imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 5 mkt segment 0 supported-hw 0x20 0x1 01-01 00:00:02.285 1 1 W ov5640 2-003c: supply DOVDD not found, using dummy regulator 01-01 00:00:02.293 1 1 W ov5640 2-003c: supply AVDD not found, using dummy regulator 01-01 00:00:02.300 1 1 W ov5640 2-003c: supply DVDD not found, using dummy regulator 01-01 00:00:02.355 1 1 E ov5640 2-003c: ov5640_read_reg: error: reg=300a 01-01 00:00:02.361 1 1 E ov5640 2-003c: ov5640_check_chip_id: failed to read chip identifier 01-01 00:00:02.370 1 1 W imx8_isi_hw: module is from the staging directory, the quality is unknown, you have been warned. 01-01 00:00:02.383 1 1 W imx8_isi_mem2mem: module is from the staging directory, the quality is unknown, you have been warned. 01-01 00:00:02.396 1 1 W imx8_isi_capture: module is from the staging directory, the quality is unknown, you have been warned. 01-01 00:00:02.410 1 1 W imx8_capture: module is from the staging directory, the quality is unknown, you have been warned. 01-01 00:00:02.423 1 1 I isi-capture 32e00000.isi: cap_device: deferring 32e00000.isi:cap_device device registration 01-01 00:00:02.433 1 1 I isi-m2m 32e00000.isi: m2m_device: deferring 32e00000.isi:m2m_device device registration 01-01 00:00:02.443 74 74 I usb 1-1 : new high-speed USB device number 2 using xhci-hcd 01-01 00:00:02.450 1 1 I mxc-isi 32e00000.isi: mxc_isi.0 registered successfully 01-01 00:00:02.458 1 1 W imx8_mipi_csi2_sam: module is from the staging directory, the quality is unknown, you have been warned. 01-01 00:00:02.459 8 8 I isi-m2m 32e00000.isi: m2m_device: Register m2m success for ISI.0 01-01 00:00:02.478 1 1 W mxc-mipi-csi2-sam 32e40000.csi: supply mipi-phy not found, using dummy regulator 01-01 00:00:02.488 1 1 E : : mipi_csis_imx8mp_phy_reset, No remote pad found! 01-01 00:00:02.494 1 1 I mxc-mipi-csi2-sam 32e40000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 500000000 01-01 00:00:02.510 96 96 I imx-sdma 30bd0000.dma-controller: firmware found. 01-01 00:00:02.516 96 96 I imx-sdma 30bd0000.dma-controller: loaded firmware 4.6 01-01 00:00:02.518 8 8 I 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 36, base_baud = 5000000) is a IMX 01-01 00:00:02.534 8 8 I 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 35, base_baud = 5000000) is a IMX 01-01 00:00:02.535 32 32 I imx-sdma 30e10000.dma-controller: firmware found. 01-01 00:00:02.551 66 66 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.551 96 96 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.559 32 32 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.559 43 43 E : trusty trusty: locked_nop_work_func: SMC_SC_LOCKED_NOP failed -1 01-01 00:00:02.567 1 1 I : trusty trusty: trusty-log not supported on secure side. 01-01 00:00:02.593 1 1 E trusty-virtio trusty: trusty-virtio: trusty_load_device_descr: virtio get descr returned (-1) 01-01 00:00:02.603 1 1 E trusty-virtio trusty: trusty-virtio: failed (-19) to load device descr 01-01 00:00:02.611 1 1 E trusty-virtio trusty: trusty-virtio: Failed to add virtio devices 01-01 00:00:02.619 1 1 W basler_camera_driver_vvcam: loading out-of-tree module taints kernel. 01-01 00:00:02.631 74 74 I usb 1-1 : New USB device found, idVendor=1d5c, idProduct=5510, bcdDevice= 1.02 01-01 00:00:02.631 1 1 W imx8_media_dev: module is from the staging directory, the quality is unknown, you have been warned. 01-01 00:00:02.640 74 74 I usb 1-1 : New USB device strings: Mfr=1, Product=2, SerialNumber=0 01-01 00:00:02.658 74 74 I usb 1-1 : Product: Frescologic USB2.0 HUB 01-01 00:00:02.659 1 1 I mx8-img-md: Registered mxc_isi.0.capture as /dev/video1 01-01 00:00:02.664 74 74 I usb 1-1 : Manufacturer: Frescologic 01-01 00:00:02.671 1 1 I : unregister ISI channel: mxc_isi.0 01-01 00:00:02.683 1 1 I : enter viv_dwe_init_module 01-01 00:00:02.690 1 1 I : enter viv_isp_init_module 01-01 00:00:02.697 1 1 I : enter viv_video_init_module 01-01 00:00:02.710 74 74 I hub 1-1 : 1.0: USB hub found 01-01 00:00:02.715 74 74 I hub 1-1 : 1.0: 5 ports detected 01-01 00:00:02.731 1 1 I cfg80211: Loading compiled-in X.509 certificates for regulatory database 01-01 00:00:02.742 1 1 I cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' 01-01 00:00:02.773 88 88 I usb 2-1 : new SuperSpeed USB device number 2 using xhci-hcd 01-01 00:00:02.808 88 88 I usb 2-1 : New USB device found, idVendor=1d5c, idProduct=5500, bcdDevice= 1.02 01-01 00:00:02.812 100 100 I random : fsck.f2fs: uninitialized urandom read (40 bytes read) 01-01 00:00:02.817 88 88 I usb 2-1 : New USB device strings: Mfr=1, Product=2, SerialNumber=0 01-01 00:00:02.817 88 88 I usb 2-1 : Product: Frescologic USB3.1Gen2 HUB 01-01 00:00:02.817 88 88 I usb 2-1 : Manufacturer: Frescologic 01-01 00:00:02.845 88 88 I hub 2-1 : 1.0: USB hub found 01-01 00:00:02.846 1 1 I fsck.f2fs: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt" 01-01 00:00:02.850 88 88 I hub 2-1 : 1.0: 4 ports detected 01-01 00:00:02.851 100 100 I random : fsck.f2fs: uninitialized urandom read (40 bytes read) 01-01 00:00:02.851 100 100 I random : fsck.f2fs: uninitialized urandom read (4 bytes read) 01-01 00:00:02.861 1 1 I fsck.f2fs: WARNING: linker: Warning: failed to find generated linker configuration from "/linkerconfig/ld.config.txt" 01-01 00:00:02.892 100 100 I : fsck.f2fs (100) used greatest stack depth: 12528 bytes left 01-01 00:00:02.893 1 1 I fsck.f2fs: Info: Fix the reported corruption. 01-01 00:00:02.907 1 1 I fsck.f2fs: Info: not exist /proc/version! 01-01 00:00:02.912 1 1 I fsck.f2fs: Info: Segments per section = 1 01-01 00:00:02.918 1 1 I fsck.f2fs: Info: Sections per zone = 1 01-01 00:00:02.924 1 1 I fsck.f2fs: Info: sector size = 512 01-01 00:00:02.929 1 1 I fsck.f2fs: Info: total sectors = 131072 (64 MB) 01-01 00:00:02.935 1 1 I fsck.f2fs: Info: MKFS version 01-01 00:00:02.940 1 1 I fsck.f2fs: "5.15.74-gd14ab594eb48-dirty" 01-01 00:00:02.996 1 1 I F2FS-fs (mmcblk2p10): Mounted with checkpoint version = 3e52e044 01-01 00:00:03.058 1 1 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:03.071 1 1 I erofs : (device dm-5): mounted with root inode @ nid 59. 01-01 00:00:03.084 1 1 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:03.097 1 1 I erofs : (device dm-6): mounted with root inode @ nid 38. 01-01 00:00:03.108 1 1 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:03.120 1 1 I erofs : (device dm-7): mounted with root inode @ nid 42. 01-01 00:00:03.130 1 1 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:03.143 1 1 I erofs : (device dm-8): mounted with root inode @ nid 39. 01-01 00:00:03.152 1 1 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:03.165 1 1 I erofs : (device dm-9): mounted with root inode @ nid 39. 01-01 00:00:03.218 1 1 W printk : init: 14 output lines suppressed due to ratelimiting 01-01 00:00:03.225 1 1 W printk : init: 203 output lines suppressed due to ratelimiting 01-01 00:00:03.340 74 74 I usb 1-1.4: new full-speed USB device number 3 using xhci-hcd 01-01 00:00:03.388 1 1 I init : Opening SELinux policy 01-01 00:00:03.396 1 1 I init : Falling back to standard signature check. TODO implementent support for fsverity SEPolicy. 01-01 00:00:03.407 1 1 I init : Error: Apex SEPolicy failed signature check 01-01 00:00:03.414 1 1 I init : Loading APEX Sepolicy from /system/etc/selinux/apex/SEPolicy.zip 01-01 00:00:03.422 1 1 E init : Failed to open package /system/etc/selinux/apex/SEPolicy.zip: No such file or directory 01-01 00:00:03.444 1 1 I init : Loading SELinux policy 01-01 00:00:03.450 74 74 I usb 1-1.4: New USB device found, idVendor=0712, idProduct=0009, bcdDevice= 2.00 01-01 00:00:03.459 74 74 I usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 01-01 00:00:03.467 74 74 I usb 1-1.4: Product: WaveShare 01-01 00:00:03.472 74 74 I usb 1-1.4: Manufacturer: WaveShare 01-01 00:00:03.473 1 1 I SELinux : Permission bpf in class capability2 not defined in policy. 01-01 00:00:03.477 74 74 I usb 1-1.4: SerialNumber: 000000000089 01-01 00:00:03.485 1 1 I SELinux : Permission checkpoint_restore in class capability2 not defined in policy. 01-01 00:00:03.500 1 1 I SELinux : Permission bpf in class cap2_userns not defined in policy. 01-01 00:00:03.508 1 1 I SELinux : Permission checkpoint_restore in class cap2_userns not defined in policy. 01-01 00:00:03.518 1 1 I SELinux : Class mctp_socket not defined in policy. 01-01 00:00:03.524 1 1 I SELinux : the above unknown classes and permissions will be denied 01-01 00:00:03.539 1 1 I SELinux : policy capability network_peer_controls=1 01-01 00:00:03.546 1 1 I SELinux : policy capability open_perms=1 01-01 00:00:03.551 74 74 I input : WaveShare WaveShare as /devices/platform/soc@0/32f10108.usb/38200000.usb/xhci-hcd.0.auto/usb1/1-1/1-1.4/1-1.4:1.0/0003:0712:0009.0001/input/input1 01-01 00:00:03.552 1 1 I SELinux : policy capability extended_socket_class=1 01-01 00:00:03.567 74 74 I hid-multitouch 0003: 0712:0009.0001: input,hidraw0: USB HID v1.11 Device [WaveShare WaveShare] on usb-xhci-hcd.0.auto-1.4/input0 01-01 00:00:03.574 1 1 I SELinux : policy capability always_check_network=0 01-01 00:00:03.574 1 1 I SELinux : policy capability cgroup_seclabel=0 01-01 00:00:03.574 1 1 I SELinux : policy capability nnp_nosuid_transition=1 01-01 00:00:03.606 1 1 I SELinux : policy capability genfs_seclabel_symlinks=0 01-01 00:00:03.613 1 1 I SELinux : policy capability ioctl_skip_cloexec=0 01-01 00:00:03.878 1 1 I selinux : SELinux: Loaded file_contexts 01-01 00:00:03.883 1 1 I selinux : 01-01 00:00:03.904 1 1 I random : init: uninitialized urandom read (40 bytes read) 01-01 00:00:03.927 1 1 I random : init: uninitialized urandom read (40 bytes read) 01-01 00:00:03.934 1 1 I random : init: uninitialized urandom read (4 bytes read) 01-01 00:00:03.944 1 1 I init : init second stage started! 01-01 00:00:04.002 1 1 I init : Using Android DT directory /proc/device-tree/firmware/android/ 01-01 00:00:04.016 1 1 W init : Couldn't load property file '/system_dlkm/etc/build.prop': open() failed: No such file or directory: No such file or directory 01-01 00:00:04.029 1 1 W init : Couldn't load property file '/vendor/default.prop': open() failed: No such file or directory: No such file or directory 01-01 00:00:04.047 1 1 W init : Couldn't load property file '/odm_dlkm/etc/build.prop': open() failed: No such file or directory: No such file or directory 01-01 00:00:04.063 1 1 I init : Setting product property ro.product.brand to 'Android' (from ro.product.product.brand) 01-01 00:00:04.074 1 1 I init : Setting product property ro.product.device to 'lec_imx8mp' (from ro.product.product.device) 01-01 00:00:04.084 1 1 I init : Setting product property ro.product.manufacturer to 'nxp' (from ro.product.product.manufacturer) 01-01 00:00:04.095 1 1 I init : Setting product property ro.product.model to 'lec_imx8mp' (from ro.product.product.model) 01-01 00:00:04.106 1 1 I init : Setting product property ro.product.name to 'lec_imx8mp' (from ro.product.product.name) 01-01 00:00:04.349 126 126 E linkerconfig: Unable to access VNDK APEX at path: /apex/com.android.vndk.v33: No such file or directory 01-01 00:00:04.361 126 126 E linkerconfig: Unable to access VNDK APEX at path: /apex/com.android.vndk.v33: No such file or directory 01-01 00:00:04.376 126 126 I : linkerconfig (126) used greatest stack depth: 11120 bytes left 01-01 00:00:04.416 127 127 I ueventd : ueventd started! 01-01 00:00:04.425 127 127 I selinux : SELinux: Loaded file_contexts 01-01 00:00:04.430 127 127 I selinux : 01-01 00:00:04.435 127 127 I ueventd : Parsing file /system/etc/ueventd.rc... 01-01 00:00:04.442 127 127 I ueventd : Added '/vendor/etc/ueventd.rc' to import list 01-01 00:00:04.449 127 127 I ueventd : Added '/odm/etc/ueventd.rc' to import list 01-01 00:00:04.457 127 127 I ueventd : Parsing file /vendor/etc/ueventd.rc... 01-01 00:00:04.464 127 127 I ueventd : Parsing file /odm/etc/ueventd.rc... 01-01 00:00:04.470 127 127 I ueventd : Unable to read config file '/odm/etc/ueventd.rc': open() failed: No such file or directory 01-01 00:00:04.493 128 128 I apexd : Bootstrap subcommand detected 01-01 00:00:04.499 128 128 E cutils-trace: Error opening trace file: No such file or directory (2) 01-01 00:00:04.688 128 128 I apexd : wait for '/dev/loop-control' took 145ms 01-01 00:00:04.724 128 128 I apexd : Pre-allocated 16 loopback devices 01-01 00:00:04.730 128 128 I apexd : Scanning /system/apex for pre-installed ApexFiles 01-01 00:00:04.738 128 128 I apexd : Found pre-installed APEX /system/apex/com.android.adbd.capex 01-01 00:00:04.753 128 128 I apexd : Found pre-installed APEX /system/apex/com.android.adservices.capex 01-01 00:00:04.764 128 128 I apexd : Found pre-installed APEX /system/apex/com.android.apex.cts.shim.apex 01-01 00:00:04.773 128 128 I apexd : Found pre-installed APEX /system/apex/com.android.appsearch.apex 01-01 00:00:04.782 128 128 I apexd : Found pre-installed APEX /system/apex/com.android.art.capex 01-01 00:00:04.847 162 162 I loop0 : detected capacity change from 0 to 96704 01-01 00:00:04.855 161 161 I loop1 : detected capacity change from 0 to 16240 01-01 00:00:04.886 127 127 I ueventd : Coldboot took 0.403 seconds 01-01 00:00:04.936 161 161 I EXT4-fs (loop1): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:04.946 162 162 I EXT4-fs (loop0): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:04.955 161 161 I loop2 : detected capacity change from 0 to 74600 01-01 00:00:04.963 162 162 I loop3 : detected capacity change from 0 to 1728 01-01 00:00:05.024 161 161 I EXT4-fs (loop2): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:05.031 162 162 I EXT4-fs (loop3): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:05.057 128 128 W printk : apexd: 41 output lines suppressed due to ratelimiting 01-01 00:00:05.065 128 128 I : apexd (128) used greatest stack depth: 10736 bytes left 01-01 00:00:05.092 169 169 I random : linkerconfig: uninitialized urandom read (40 bytes read) 01-01 00:00:05.101 169 169 I random : linkerconfig: uninitialized urandom read (4 bytes read) 01-01 00:00:05.108 169 169 I random : linkerconfig: uninitialized urandom read (4 bytes read) 01-01 00:00:05.220 170 170 W : getrandom indicates that the entropy pool has not been initialized. Rather than continue with poor entropy, this process will block until entropy is available. 01-01 00:00:06.932 0 0 I [ C0] random: crng init done 01-01 00:00:06.936 0 0 I [ C0] random: 63 urandom warning(s) missed due to ratelimiting 01-01 00:00:07.173 174 174 W prng_seeder: Hanging forever because setup failed: hwrng.read_exact in new 01-01 00:00:07.184 174 174 W Caused by: 01-01 00:00:07.187 174 174 W : No such device (os error 19) 01-01 00:00:07.276 178 178 F wlan : Loading MWLAN driver 01-01 00:00:07.281 178 178 F wlan : Register to Bus Driver... 01-01 00:00:07.286 178 178 F wlan : Register to SDIO_MMC Bus Driver 01-01 00:00:07.292 178 178 F : vendor=0x02DF device=0x9141 class=0 function=1 01-01 00:00:07.298 178 178 F : Attach moal handle ops, card interface type: 0x104 01-01 00:00:07.305 178 178 F : rps set to 0 from module param 01-01 00:00:07.311 178 178 F SD8997 : init module param from usr cfg 01-01 00:00:07.317 178 178 F card_type: SD8997, config block: 0 01-01 00:00:07.322 178 178 F : cfg80211_wext=0xf 01-01 00:00:07.326 178 178 F : sta_name=wlan 01-01 00:00:07.329 178 178 F : uap_name=wlan 01-01 00:00:07.332 178 178 F : wfd_name=p2p 01-01 00:00:07.336 178 178 F : max_vir_bss=1 01-01 00:00:07.339 178 178 F : cal_data_cfg=none 01-01 00:00:07.342 178 178 F : ps_mode = 1 01-01 00:00:07.346 178 178 F : auto_ds = 1 01-01 00:00:07.349 178 178 F : host_mlme=enable 01-01 00:00:07.352 178 178 F : fw_name=nxp/sdsd8997_combo_v4.bin 01-01 00:00:07.358 178 178 F SDIO : max_segs=128 max_seg_size=65535 01-01 00:00:07.363 178 178 F : rx_work=1 cpu_num=4 01-01 00:00:07.367 178 178 W : Attach mlan adapter operations.card_type is 0x104. 01-01 00:00:07.379 178 178 W wlan : Enable TX SG mode 01-01 00:00:07.383 178 178 W wlan : Enable RX SG mode 01-01 00:00:07.394 178 178 F Request firmware: nxp/sdsd8997_combo_v4.bin 01-01 00:00:07.415 178 178 W : mlan_dnld_fw 01-01 00:00:07.423 178 178 W : Check if firmware is already running 01-01 00:00:07.429 178 178 W wlan_sdio_check_fw_status: Wait for firmware initialization event 01-01 00:00:07.486 1 1 E pstore : crypto_comp_decompress failed, ret = -22! 01-01 00:00:07.503 1 1 I : Registered swp emulation handler 01-01 00:00:07.610 186 186 I logd.auditd: start 01-01 00:00:07.613 193 193 I watchdogd: watchdogd started (interval 10, margin 20)! 01-01 00:00:07.644 186 186 I logd : Loaded bug_map file: /vendor/etc/selinux/selinux_denial_metadata 01-01 00:00:07.653 186 186 I logd : Loaded bug_map file: /system/etc/selinux/bug_map 01-01 00:00:07.809 1 1 I zram0 : detected capacity change from 0 to 1228800 01-01 00:00:07.842 1 1 I mkswap : Swapspace size: 614396k, UUID=610c7397-03f1-42a0-926f-30c0925d3fad 01-01 00:00:07.872 1 1 I : Adding 614396k swap on /dev/block/zram0. Priority:-2 extents:1 across:614396k SS 01-01 00:00:08.033 224 224 D vdc : Waited 0ms for vold 01-01 00:00:08.086 233 233 D vdc : Waited 0ms for vold 01-01 00:00:08.217 201 201 I fsck.f2fs: Info: Fix the reported corruption. 01-01 00:00:08.223 201 201 I fsck.f2fs: Info: not exist /proc/version! 01-01 00:00:08.229 201 201 I fsck.f2fs: Info: Segments per section = 1 01-01 00:00:08.235 201 201 I fsck.f2fs: Info: Sections per zone = 1 01-01 00:00:08.240 201 201 I fsck.f2fs: Info: sector size = 4096 01-01 00:00:08.246 201 201 I fsck.f2fs: Info: total sectors = 6197760 (24210 MB) 01-01 00:00:08.252 201 201 I fsck.f2fs: Info: MKFS version 01-01 00:00:08.257 201 201 I fsck.f2fs: "5.15.74-gd14ab594eb48-dirty" 01-01 00:00:08.263 201 201 I fsck.f2fs: Info: FSCK version 01-01 00:00:08.268 201 201 I fsck.f2fs: from "5.15.74-gd14ab594eb48-dirty" 01-01 00:00:08.358 201 201 I F2FS-fs (dm-38): Using encoding defined by superblock: utf8-12.1.0 with flags 0x0 01-01 00:00:08.453 201 201 I F2FS-fs (dm-38): recover_inode: ino = 317d, name = , inline = 21 01-01 00:00:08.462 201 201 I F2FS-fs (dm-38): recover_data: ino = 317d (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.472 201 201 I F2FS-fs (dm-38): recover_inode: ino = 1d1a, name = , inline = 21 01-01 00:00:08.480 201 201 I F2FS-fs (dm-38): recover_data: ino = 1d1a (i_size: recover) recovered = 0, err = 0 01-01 00:00:08.490 201 201 I F2FS-fs (dm-38): recover_inode: ino = 317e, name = , inline = 21 01-01 00:00:08.499 201 201 I F2FS-fs (dm-38): recover_dentry: ino = 317e, name = , dir = 177a, err = 0 01-01 00:00:08.509 201 201 I F2FS-fs (dm-38): recover_data: ino = 317e (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.518 201 201 I F2FS-fs (dm-38): recover_inode: ino = 3177, name = , inline = 21 01-01 00:00:08.527 201 201 I F2FS-fs (dm-38): recover_data: ino = 3177 (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.536 201 201 I F2FS-fs (dm-38): recover_inode: ino = 1d1a, name = , inline = 21 01-01 00:00:08.545 201 201 I F2FS-fs (dm-38): recover_data: ino = 1d1a (i_size: recover) recovered = 1, err = 0 01-01 00:00:08.561 201 201 I F2FS-fs (dm-38): checkpoint: version = 276aec00 01-01 00:00:08.568 201 201 I F2FS-fs (dm-38): Mounted with checkpoint version = 276aec00 01-01 00:00:08.569 178 178 W Wlan : FW download over, firmwarelen=623240 downloaded 623240 01-01 00:00:08.582 178 178 W wlan_sdio_check_fw_status: Wait for firmware initialization event 01-01 00:00:08.647 259 259 D vdc : Waited 0ms for vold 01-01 00:00:08.673 1 1 I fscrypt : AES-256-CTS-CBC using implementation "cts-cbc-aes-ce" 01-01 00:00:08.776 201 201 E vold : keystore2 Keystore earlyBootEnded returned service specific error: -68 01-01 00:00:08.836 199 199 I logd : logd reinit 01-01 00:00:08.843 199 199 E logd : FrameworkListener: read() failed (Connection reset by peer) 01-01 00:00:08.843 268 268 I apexd : Scanning /system/apex for pre-installed ApexFiles 01-01 00:00:08.859 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.adbd.capex 01-01 00:00:08.867 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.adservices.capex 01-01 00:00:08.877 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.apex.cts.shim.apex 01-01 00:00:08.886 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.appsearch.apex 01-01 00:00:08.895 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.art.capex 01-01 00:00:08.904 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.btservices.apex 01-01 00:00:08.913 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.car.framework.apex 01-01 00:00:08.922 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.cellbroadcast.capex 01-01 00:00:08.931 268 268 I apexd : Found pre-installed APEX /system/apex/com.android.conscrypt.capex 01-01 00:00:09.069 270 270 I loop4 : detected capacity change from 0 to 41784 01-01 00:00:09.077 271 271 I loop5 : detected capacity change from 0 to 6952 01-01 00:00:09.139 270 270 I EXT4-fs (loop4): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.140 271 271 I EXT4-fs (loop5): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.152 270 270 I loop6 : detected capacity change from 0 to 12952 01-01 00:00:09.165 271 271 I loop7 : detected capacity change from 0 to 536 01-01 00:00:09.219 270 270 I EXT4-fs (loop6): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.234 270 270 I loop8 : detected capacity change from 0 to 1728 01-01 00:00:09.237 271 271 I EXT4-fs (loop7): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.254 271 271 I loop9 : detected capacity change from 0 to 536 01-01 00:00:09.296 270 270 I EXT4-fs (loop8): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.307 270 270 I loop10 : detected capacity change from 0 to 74600 01-01 00:00:09.341 271 271 I EXT4-fs (loop9): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.352 271 271 I loop11 : detected capacity change from 0 to 96704 01-01 00:00:09.371 270 270 I EXT4-fs (loop10): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.383 270 270 I loop12 : detected capacity change from 0 to 3920 01-01 00:00:09.411 271 271 I EXT4-fs (loop11): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.420 178 178 F : WLAN FW is active 01-01 00:00:09.422 271 271 I loop13 : detected capacity change from 0 to 16240 01-01 00:00:09.425 178 178 F : on_time is 9252720625 01-01 00:00:09.442 270 270 I EXT4-fs (loop12): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.454 270 270 I loop14 : detected capacity change from 0 to 536 01-01 00:00:09.476 66 66 W : fw_cap_info=0x18fcffa3, dev_cap_mask=0xffffffff 01-01 00:00:09.483 66 66 W : max_p2p_conn = 8, max_sta_conn = 8 01-01 00:00:09.500 178 178 F : Register NXP 802.11 Adapter wlan0 01-01 00:00:09.506 178 178 F wlan : wlan%d set max_mtu 2000 01-01 00:00:09.511 271 271 I EXT4-fs (loop13): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.512 178 178 F : Register NXP 802.11 Adapter wlan1 01-01 00:00:09.522 271 271 I loop15 : detected capacity change from 0 to 1536 01-01 00:00:09.523 270 270 I EXT4-fs (loop14): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.531 178 178 F : Register NXP 802.11 Adapter p2p0 01-01 00:00:09.533 270 270 I loop16 : detected capacity change from 0 to 17256 01-01 00:00:09.542 178 178 F wlan : version = SD8997----16.68.1.p197-MM5X16368.p2-GPL-(FP92) 01-01 00:00:09.562 178 178 E WLAN : SDIO Driver Registration SUCCESS 01-01 00:00:09.568 178 178 F wlan : Register to Bus Driver Done 01-01 00:00:09.573 178 178 F wlan : Driver loaded successfully 01-01 00:00:09.584 178 178 F BT : Loading driver 01-01 00:00:09.597 178 178 F : BT FW is active(0) 01-01 00:00:09.601 270 270 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:09.601 178 178 F BT : FW already downloaded! 01-01 00:00:09.619 271 271 I EXT4-fs (loop15): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.630 271 271 I loop17 : detected capacity change from 0 to 40512 01-01 00:00:09.630 178 178 F BT : Create /dev/mbtchar0 01-01 00:00:09.640 270 270 I EXT4-fs (dm-36): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.653 270 270 I loop18 : detected capacity change from 0 to 17128 01-01 00:00:09.677 271 271 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:09.705 178 178 F BT : Create /dev/mdebugchar0 01-01 00:00:09.709 270 270 I device-mapper: verity: sha256 using implementation "sha256-ce" 01-01 00:00:09.728 271 271 I EXT4-fs (dm-35): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.732 270 270 I EXT4-fs (dm-34): mounted filesystem without journal. Opts: (null). Quota mode: none. 01-01 00:00:09.734 270 270 I loop19 : detected capacity change from 0 to 29504 01-01 00:00:09.744 178 178 F BT : Driver loaded successfully Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" hi,  Thank you so much for the reply.  I am working on Android 13 with kernel version 5.15.74 . i have ported the mbt8xxx driver from android 11 to android 13. It is working fine in my device, but after bluetooth connection the bluetooth is crashing after going through the dmesg i am getting the error as I mentioned above Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin" Hello @jeevanefx123  AW-CM276 have no SD-BT support. Your may use sd-uart firmware. Best Regards Shaun Re: 88w8997 Wifi driver IOCTL issue with firmware version "sdsd8997_combo_v4.bin"

PN7160 NFC bring up on Yocto Mickledore I am referring to AN13287 bring up guide and facing a crash in nfcDemoApp, please see nfcDemo.txt whic is the crash ,  due to some reason , i see CORE_RESET_NTF received, is that the reason for the crash ?? 1.. Nfc driver in the kernel is up, i can see /dev/nxpnfc root@nitrogen8mm:~# dmesg | grep nfc [ 2.744181] nfc_i2c_dev_init: Loading NXP NFC I2C driver [ 2.891526] nfc_i2c_dev_probe: enter [ 2.899770] nfc_parse_dt: irq 154 [ 2.910656] nfc_parse_dt: dwl_req gpio invalid -2 [ 2.920587] nfc_parse_dt: 154, 155, -2 [ 2.932796] nfc_i2c_dev_probe: unable to request nfc firm downl gpio [-2] [ 2.932942] nfc_i2c_dev_probe: requesting IRQ 179 [ 2.974174] nfc_i2c_dev_probe: probing nfc i2c successfully Re: PN7160 NFC bring up on Yocto Mickledore Hi @KaiLi ,  I am able to resolve the issue now ,  Tags are getting detected .. It seems like no one has actually tested this on Yocto Linux, i am on mickledore, I am surprised there is a compilation error as well Few notes :  Removed download PIN in device tree , no need of this  (please see nfc_i2c_dts.txt) Remove libpn7160_fw.so, we need not download the firmware 0002-Change-Default-Paths.patch is optional , we just change the default path 0003-Polling-Tech-Mask-not-read.patch  is the actual fix Re: PN7160 NFC bring up on Yocto Mickledore Hi Kelly,  Another thing , I am able to successfully read tags using the FactoryTestApp , so this confirms my kernel driver is working fine as such  https://github.com/NXPNFCLinux/linux_NfcFactoryTestApp Re: PN7160 NFC bring up on Yocto Mickledore This Log is with Skipping the firmware download ..  I set  the value in phNxpNciHal_fw_download_seq (gphNxpNciHal_fw_IoctlCtx.bSkipSeq) = false;   Re: PN7160 NFC bring up on Yocto Mickledore Hello @PavanNittala  Can you upload the complete log file?Thanks. Re: PN7160 NFC bring up on Yocto Mickledore Hi , Firmware download is attempted 3 times and failed, Is this an issue ??  The final issue i see is the "Chip Version Middleware Version mismatch!!!!" which returns a failure ,  I think others also facing this ,  please help !   root@nitrogen8mm:~# nfcDemoApp poll ######################################################################################### ## NFC demo ## ######################################################################################### ## Poll mode activated ## ######################################################################################### ... press enter to quit ... 2023:03:03-11:34:10.746 find found NXPLOG_TML_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 GetNxpNumValue: NXP Config Parameter : NXPLOG_TML_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 find found NXPLOG_FWDNLD_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 GetNxpNumValue: NXP Config Parameter : NXPLOG_FWDNLD_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 find found NXPLOG_NCIX_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 GetNxpNumValue: NXP Config Parameter : NXPLOG_NCIX_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 find found NXPLOG_NCIR_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 GetNxpNumValue: NXP Config Parameter : NXPLOG_NCIR_LOGLEVEL=(0xff) 2023:03:03-11:34:10.746 initializeGlobalDebugEnabledFlag: level=1 2023:03:03-11:34:10.746 initializeGlobalDebugEnabledFlag: level=1 2023:03:03-11:34:10.747 readConfig Opened base config /etc/libnfc-nci.conf 2023:03:03-11:34:10.748 NfcAdaptation::Initialize: Overriding NFA_EE_MAX_EE_SUPPORTED to use 1 2023:03:03-11:34:10.749 verify_stack_non_volatile_store 2023:03:03-11:34:10.749 crcChecksumVerifyIntegrity: filename=/nfaStorage.bin1 2023:03:03-11:34:10.749 crcChecksumVerifyIntegrity: filename=/nfaStorage.bin4 2023:03:03-11:34:10.749 crcChecksumVerifyIntegrity: filename=/nfaStorage.bin2 2023:03:03-11:34:10.749 crcChecksumVerifyIntegrity: filename=/nfaStorage.bin3 2023:03:03-11:34:10.749 crcChecksumVerifyIntegrity: filename=/nfaStorage.bin5 2023:03:03-11:34:10.749 Initialize: preserve stack NV store 2023:03:03-11:34:10.750 GKI_create_task func=0x0xffffa5ecc930 id=4 name=NFCA_TASK stack=0x(nil) stackSize=0 2023:03:03-11:34:10.750 GKI creating task 4, pCond/pMutex=(nil)/(nil) 2023:03:03-11:34:10.750 Leaving GKI_create_task 0xffffa5ecc930 4 ffffa50df180 NFCA_TASK (nil) 0 2023:03:03-11:34:10.750 GKI_create_task func=0x0xffffa5ecddd0 id=0 name=NFCA_THREAD stack=0x(nil) stackSize=0 2023:03:03-11:34:10.750 GKI creating task 0, pCond/pMutex=(nil)/(nil) 2023:03:03-11:34:10.750 gki_task_entry task_id=4, thread_id=ffffa50df180/ffffa50df180, pCond/pMutex=(nil)/(nil) 2023:03:03-11:34:10.750 NfcAdaptation::NFCA_TASK: enter 2023:03:03-11:34:10.750 GKI_run enter 2023:03:03-11:34:10.750 Start/Stop GKI_timer_update_registered! 2023:03:03-11:34:10.750 GKI_run, run_cond(0xffffa5f9a7c0)=1 2023:03:03-11:34:10.750 Leaving GKI_create_task 0xffffa5ecddd0 0 ffffa48cf180 NFCA_THREAD (nil) 0 2023:03:03-11:34:10.750 gki_task_entry task_id=0, thread_id=ffffa48cf180/ffffa48cf180, pCond/pMutex=(nil)/(nil) 2023:03:03-11:34:10.750 NfcAdaptation::Thread: enter 2023:03:03-11:34:10.750 GKI_create_task func=0x0xffffa5e8b1b4 id=3 name=NFC_TASK stack=0x(nil) stackSize=0 2023:03:03-11:34:10.750 GKI creating task 3, pCond/pMutex=0xffffa48ce7e8/0xffffa48ce7b8 2023:03:03-11:34:10.751 Leaving GKI_create_task 0xffffa5e8b1b4 3 ffff97fff180 NFC_TASK (nil) 0 2023:03:03-11:34:10.751 gki_task_entry task_id=3, thread_id=ffff97fff180/ffff97fff180, pCond/pMutex=0xffffa48ce7e8/0xffffa48ce7b8 2023:03:03-11:34:10.752 NFC_TASK started. 2023:03:03-11:34:10.752 GKI_wait task=3, pCond/pMutex = 0xffffa48ce7e8/0xffffa48ce7b8 2023:03:03-11:34:10.752 GKI_exit_task 0 done 2023:03:03-11:34:10.752 NfcAdaptation::Initialize: exit 2023:03:03-11:34:10.752 NfcAdaptation::Thread: exit 2023:03:03-11:34:10.752 gki_task task_id=0 terminating 2023:03:03-11:34:10.753 NFA_Init 2023:03:03-11:34:10.753 nfa_dm_init 2023:03:03-11:34:10.753 id=1, enable_cplt_mask=0x0 2023:03:03-11:34:10.753 nfa_p2p_init 2023:03:03-11:34:10.753 id=3, enable_cplt_mask=0x8 2023:03:03-11:34:10.753 Nfc: nfa_snep_init (): is_dta_mode=0 2023:03:03-11:34:10.753 Nfc: nfa[ 91.208401] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 0 _snep_default_init () 2023:03:03-11:34:10.753 id=4, enable_cplt_mask=0x18 2023:03:03-11:34:11.085 nfa_rw_init 2023:03:03-11:34:11.085 id=5, enable_cplt_mask=0x38 2023:03:03-11:34:11.085 nfa_ce_init 2023:03:03-11:34:11.085 id=6, enable_cplt_[ 91.234254] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 1 mask=0x78 2023:03:03-11:34:11.085 nfa_ee_init 2023:03:03-11:34:11.085 id=2, enable_cplt_mask=0x7c 2023:03:03-11:34:11.085 nfa_t4tnfcee_init 2023:03:03-11:34:11.085 find found NXP_T4T_NFCEE_ENABLE=(0x1) 2023:03:03-11:34:11.085 GetNxpNumValue: NXP Config Parameter : NXP_T4T_NFCEE_ENABLE=(0x1) 2023:03:03-11:34:11.085 id=9, enable_cplt_mask=0x27c 2023:03:03-11:34:11.099 llcp_init 2023:03:03-11:34:11.099 num_rx_buff = 9, rx_congest_start = 6, rx_congest_end = 4, max_num_ll_rx_buff = 2 2023:03:03-11:34:11.099 max_num_tx_buff = 21, max_num_ll_tx_buff = 6 2023:03:03-11:34:11.099 SAP:0x1, link_type:0x2, ServiceName: 2023:03:03-11:34:11.099 Registered SAP = 0x01 2023:03:03-11:34:11.099 NFA_Enable 2023:03:03-11:34:11.100 NFA got event 0x0100 2023:03:03-11:34:11.100 event: NFA_DM_API_ENABLE_EVT (0x00) 2023:03:03-11:34:11.100 nfa_dm_enable 2023:03:03-11:34:11.100 NFC_Enable 2023:03:03-11:34:11.100 nfc_set_state 0 (NONE)->1 (W4_HAL_OPEN) 2023:03:03-11:34:11.100 NfcAdaptation::HalOpen 2023:03:03-11:34:11.100 phNxpNci_MinOpen(): enter 2023:03:03-11:34:11.102 find found NXPLOG_GLOBAL_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_GLOBAL_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 find found NXPLOG_NCIHAL_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_NCIHAL_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 find found NXPLOG_EXTNS_LOGLEVEL=(0x3) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_EXTNS_LOGLEVEL=(0x3) 2023:03:03-11:34:11.102 find found NXPLOG_TML_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_TML_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 find found NXPLOG_FWDNLD_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_FWDNLD_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 find found NXPLOG_NCIX_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_NCIX_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 find found NXPLOG_NCIR_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 GetNxpNumValue: NXP Config Parameter : NXPLOG_NCIR_LOGLEVEL=(0xff) 2023:03:03-11:34:11.102 phNxpLog_InitializeLogLevel: global =255, Fwdnld =255, extns =3, hal =255, tml =255, ncir =255, ncix =255 2023:03:03-11:34:11.103 find found MIFARE_READER_ENABLE=(0x0) 2023:03:03-11:34:11.103 GetNxpNumValue: NXP Config Parameter : MIFARE_READER_ENABLE=(0x0) 2023:03:03-11:34:11.103 Entering phNxpNciHal_init_monitor 2023:03:03-11:34:11.103 Returning with SUCCESS 2023:03:03-11:34:11.103 find found NXP_NFC_DEV_NODE 2023:03:03-11:34:11.103 GetNxpStrValue: NXP Config Parameter : NXP_NFC_DEV_NODE 2023:03:03-11:34:11.103 NFC Chip Type: 0 2023:03:03-11:34:11.103 phTmlNfc_Init Entry...... 2023:03:03-11:34:11.103 getTransport Requested transportType: 4 2023:03:03-11:34:11.103 OpenAndConfigure Opening port=/dev/nxpnfc 2023:03:03-11:34:11.103 NfccReset, VEN eType 0 2023:03:03-11:34:11.129 NfccReset, VEN eType 1 2023:03:03-11:34:11.146 PN54X - Tml Reader Thread Started................ 2023:03:03-11:34:11.146 phTmlNfc_Init exit wInitStatus=0 2023:03:03-11:34:11.146 PN54X - Tml Writer Thread Started................ 2023:03:03-11:34:11.147 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.147 thread started 2023:03:03-11:34:11.147 PN54X - Read requested..... 2023:03:03-11:34:11.147 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.147 PN54X - Write requested..... 2023:03:03-11:34:11.147 PN54X - Invoking I2C Write..... 2023:03:03-11:34:11.148 len = 4 > 20000100 2023:03:03-11:34:11.148 PN54X - I2C Write successful..... 2023:03:03-11:34:11.148 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:11.148 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.148 write successful status = 0x0 2023:03:03-11:34:11.148 Response timer started 2023:03:03-11:34:11.148 Waiting after ext cmd sent 2023:03:03-11:34:11.152 PN54X - I2C Read successful..... 2023:03:03-11:34:11.152 len = 4 > 40000100 2023:03:03-11:34:11.152 PN54X - Posting read message..... 2023:03:03-11:34:11.152 read successful status = 0x0 2023:03:03-11:34:11.483 CORE_RESET_RSP NCI2.0 2023:03:03-11:34:11.483 Pavankn fw_maj_ver: 0, romVersion: 0 2023:03:03-11:34:11.483 PN54X - Read requested..... 2023:03:03-11:34:11.483 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.483 Response timer stopped 2023:03:03-11:34:11.483 Response timer started 2023:03:03-11:34:11.485 PN54X - I2C Read successful..... 2023:03:03-11:34:11.485 len = 12 > 600009020020040471125005 2023:03:03-11:34:11.485 PN54X - Posting read message..... 2023:03:03-11:34:11.485 read successful status = 0x0 2023:03:03-11:34:11.485 CORE_RESET_NTF NCI2.0 reason CORE_RESET_CMD received ! 2023:03:03-11:34:11.485 nci_version : 0x20 2023:03:03-11:34:11.485 getChipType HwVersion : 0x71 2023:03:03-11:34:11.485 getChipType Product : PN557 2023:03:03-11:34:11.485 phNxpNciHal_configFeatureList chipType = 9 2023:03:03-11:34:11.485 NxpNci> FW Version: 12.50.5 2023:03:03-11:34:11.485 Pavankn fw_maj_ver: 80, romVersion: 18 2023:03:03-11:34:11.485 PN54X - Read requested..... 2023:03:03-11:34:11.486 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.486 Response timer stopped 2023:03:03-11:34:11.486 Checking response 2023:03:03-11:34:11.486 PN54X - Write requested..... 2023:03:03-11:34:11.486 PN54X - Invoking I2C Write..... 2023:03:03-11:34:11.487 len = 5 > 2001020000 2023:03:03-11:34:11.487 PN54X - I2C Write successful..... 2023:03:03-11:34:11.487 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:11.487 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.487 write successful status = 0x0 2023:03:03-11:34:11.487 Response timer started 2023:03:03-11:34:11.487 Waiting after ext cmd sent 2023:03:03-11:34:11.491 PN54X - I2C Read successful..... 2023:03:03-11:34:11.491 len = 33 > 40011E001A7E060301D002FFFF01FF000800000100020003008000820083008400 2023:03:03-11:34:11.491 PN54X - Posting read message..... 2023:03:03-11:34:11.491 read successful status = 0x0 2023:03:03-11:34:11.491 CORE_INIT_RSP NCI2.0 received ! 2023:03:03-11:34:11.491 Pavankn fw_maj_ver: 80, romVersion: 18 2023:03:03-11:34:11.491 Response timer stopped 2023:03:03-11:34:11.491 Checking response 2023:03:03-11:34:11.491 PN54X - Read requested..... 2023:03:03-11:34:11.491 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.491 find found NXP_I2C_FRAGMENTATION_ENABLED=(0x0) 2023:03:03-11:34:11.491 GetNxpNumValue: NXP Config Parameter : NXP_I2C_FRAGMENTATION_ENABLED=(0x0) 2023:03:03-11:34:11.491 I2C status : 0 2023:03:03-11:34:11.492 PN54X - Write requested..... 2023:03:03-11:34:11.492 PN54X - Invoking I2C Write..... 2023:03:03-11:34:11.493 len = 6 > 20030301A005 2023:03:03-11:34:11.493 PN54X - I2C Write successful..... 2023:03:03-11:34:11.493 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:11.493 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.493 write successful status = 0x0 2023:03:03-11:34:11.493 Response timer started 2023:03:03-11:34:11.493 Waiting after ext cmd sent 2023:03:03-11:34:11.494 PN54X - I2C Read successful..... 2023:03:03-11:34:11.494 len = 9 > 4003060001A0050100 2023:03:03-11:34:11.495 PN54X - Posting read message..... 2023:03:03-11:34:11.495 read successful status = 0x0 2023:03:03-11:34:11.495 Pavankn fw_maj_ver: 80, romVersion: 18 2023:03:03-11:34:11.495 phNxpNciHal_print_res_status: response status =STATUS_OK 2023:03:03-11:34:11.495 PN54X - Read requested..... 2023:03:03-11:34:11.495 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.495 Response timer stopped 2023:03:03-11:34:11.495 Checking response 2023:03:03-11:34:11.495 Allocating Mem for Dnld Context.. 2023:03:03-11:34:11.495 find found NXP_FW_TYPE=(0x1) 2023:03:03-11:34:11.495 GetNxpNumValue: NXP Config Parameter : NXP_FW_TYPE=(0x1) 2023:03:03-11:34:11.495 firmware type from conf file: 1 2023:03:03-11:34:11.511 @@@//usr//lib//libpn7160_fw.so 2023:03:03-11:34:11.511 FW Image Length - ImageInfoLen 34542 2023:03:[ 91.959566] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 2 03-11:34:11.511 FW Image Info Pointer - pImageInfo 0xffffa4080010 2023:03:03-11:34:11.511 FW Major Version Num - 50 2023:03:03-11:34:11.511 FW Minor Version Num - 6 2023:03:03-11:34:11.844 FW Image Length - 34542 2023:03:03-11:34:11.844 FW Image Info Pointer - 0xffffa4080010 2023:03:03-11:34:11.844 FW version for FW file = 0x5006 2023:03:03-11:34:11.844 FW version from device = 0x125005 2023:03:03-11:34:11.844 PN54X - Write requested..... 2023:03:03-11:34:11.844 PN54X - Invoking I2C Write..... 2023:03:03-11:34:11.845 len = 6 > 20030301A008 2023:03:03-11:34:11.845 PN54X - I2C Write successful..... 2023:03:03-11:34:11.845 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:11.845 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.845 write successful status = 0x0 2023:03:03-11:34:11.845 Response timer started 2023:03:03-11:34:11.845 Waiting after ext cmd sent 2023:03:03-11:34:11.847 PN54X - I2C Read successful..... 2023:03:03-11:34:11.847 len = 10 > 4003070001A008020000 2023:03:03-11:34:11.847 PN54X - Posting read message..... 2023:03:03-11:34:11.847 read successful status = 0x0 2023:03:03-11:34:11.847 Pavankn fw_maj_ver: 80, romVersion: 18 2023:03:03-11:34:11.847 phNxpNciHal_print_res_status: response status =STATUS_OK 2023:03:03-11:34:11.847 phNxpNciHal_print_res_status: Storing GPIO Values... 2023:03:03-11:34:11.847 Response timer stopped 2023:03:03-11:34:11.847 Checking response 2023:03:03-11:34:11.847 PN54X - Read requested..... 2023:03:03-11:34:11.847 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.847 PN54X - Write requested..... 2023:03:03-11:34:11.847 PN54X - Invoking I2C Write..... 2023:03:03-11:34:11.852 len = 39 > 20022401A014200000000000000000000000000000000000000000000000000000000000000000 2023:03:03-11:34:11.852 PN54X - I2C Write successful..... 2023:03:03-11:34:11.852 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:11.852 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.852 write successful status = 0x0 2023:03:03-11:34:11.852 Response timer started 2023:03:03-11:34:11.852 Waiting after ext cmd sent 2023:03:03-11:34:11.853 PN54X - I2C Read successful..... 2023:03:03-11:34:11.854 len = 5 > 4002020000 2023:03:03-11:34:11.854 PN54X - Posting read message..... 2023:03:03-11:34:11.854 read successful status = 0x0 2023:03:03-11:34:11.854 Pavankn fw_maj_ver: 80, romVersion: 18 2023:03:03-11:34:11.854 phNxpNciHal_print_res_status: response status =STATUS_OK 2023:03:03-11:34:11.854 Response timer stopped 2023:03:03-11:34:11.854 Checking response 2023:03:03-11:34:11.854 Starting FW update 2023:03:03-11:34:11.854 PN54X - Read requested..... 2023:03:03-11:34:11.854 PN54X - Invoking I2C Read..... 2023:03:03-11:34:11.854 find found NXP_SYS_CLK_SRC_SEL=(0x1) 2023:03:03-11:34:11.854 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLK_SRC_SEL=(0x1) 2023:03:03-11:34:11.854 find found NXP_SYS_CLK_FREQ_SEL=(0x0) 2023:03:03-11:34:11.854 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLK_FREQ_SEL=(0x0) 2023:03:03-11:34:11.854 find found NXP_SYS_CLOCK_TO_CFG=(0x1) 2023:03:03-11:34:11.854 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLOCK_TO_CFG=(0x1) 2023:03:03-11:34:11.854 gphNxpNciHal_fw_IoctlCtx.bClkSrcVal = 0x1 2023:03:03-11:34:11.854 gphNxpNciHal_fw_IoctlCtx.bClkFreqVal = 0x0 2023:03:03-11:34:11.854 gphNxpNciHal_fw_IoctlCtx.bTimeout = 0x1 2023:03:03-11:34:11.854 NfccReset, VEN eType 2 2023:03:03-11:34:11.983 Calling Seq handler for FW Download 2023:03:03-11:34:11.983 find found NXP_FW_TYPE=(0x1) 2023:03:03-11:34:11.983 GetNxpNumValue: NXP Config Parameter : NXP_FW_TYPE=(0x1) 2023:03:03-11:34:11.983 firmware type from conf file: 1 2023:03:03-11:34:11.983 free library SUCCESS !! 2023:03:03-11:34:11.984 @@@//usr//lib//libpn7160_fw.so 2023:03:03-11:34:11.984 FW Image Length - ImageInfoLen 34542 2023:03:03-11:34:11.984 FW Image Info Pointer - pImageInfo 0xffffa4080010 2023:03:03-11:34:11.984 FW Major Version Num - 50 2023:03:03-11:34:11.984 FW Minor Version Num - 6 2023:03:03-11:34:11.984 FW Image Length - 34542 2023:03:03-11:34:11.984 FW Image Info Pointer - 0xffffa4080010 2023:03:03-11:34:11.984 phDnldNfc_InitImgInfo:SUCCESS 2023:03:03-11:34:11.984 Processing Normal Sequence.. 2023:03:03-11:34:11.984 Initializing Sequence.. 2023:03:03-11:34:11.984 Response Timer Created Successfully 2023:03:03-11:34:11.984 Inserting FrameId .. 2023:03:03-11:34:11.984 Frame created successfully 2023:03:03-11:34:11.984 GetSessionState Request submitted successfully 2023:03:03-11:34:11.984 PN54X - Write requested..... 2023:03:03-11:34:11.984 PN54X - Invoking I2C Write..... 2023:03:03-11:34:11.985 len = 8 > 0004F2000000F533 2023:03:03-11:34:11.986 PN54X - I2C Write successful..... 2023:03:03-11:34:11.986 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:11.986 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:11.986 Send Success 2023:03:03-11:34:11.986 Response timer started 2023:03:03-11:34:14.486 [ 94.591720] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 0 0 2023:03:03-11:34:14.486 phNxpNciHal_fw_dnld_get_sessn_state_cb - Request Failed, State:255, pInfo: 0x90001658 2023:03:03-11:34:14.486 phDnldNfc_GetSessionState cb failed 2023:03:03-11:34:14.486 phNxpNciHal_fw_seq_handler : FAILED 2023:03:0[ 94.619120] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 1 3-11:34:14.486 phNxpNciHal_fw_dnld_complete: Download Status = 0xff 2023:03:03-11:34:14.486 Fw Download Failed!! 2023:03:03-11:34:14.486 NfccReset, VEN eType 0 2023:03:03-11:34:14.514 NfccReset, VEN eType 1 2023:03:03-11:34:14.631 [ 94.736743] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 2 free library SUCCESS !! 2023:03:03-11:34:14.631 Freeing Mem for Dnld Context.. 2023:03:03-11:34:14.631 Retrying: FW download 2023:03:03-11:34:14.631 find found NXP_SYS_CLK_SRC_SEL=(0x1) 2023:03:03-11:34:14.631 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLK_SRC_SEL=(0x1) 2023:03:03-11:34:14.631 find found NXP_SYS_CLK_FREQ_SEL=(0x0) 2023:03:03-11:34:14.631 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLK_FREQ_SEL=(0x0) 2023:03:03-11:34:14.631 find found NXP_SYS_CLOCK_TO_CFG=(0x1) 2023:03:03-11:34:14.631 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLOCK_TO_CFG=(0x1) 2023:03:03-11:34:14.631 gphNxpNciHal_fw_IoctlCtx.bClkSrcVal = 0x1 2023:03:03-11:34:14.631 gphNxpNciHal_fw_IoctlCtx.bClkFreqVal = 0x0 2023:03:03-11:34:14.631 gphNxpNciHal_fw_IoctlCtx.bTimeout = 0x1 2023:03:03-11:34:14.632 NfccReset, VEN eType 2 2023:03:03-11:34:14.759 Allocating Mem for Dnld Context.. 2023:03:03-11:34:14.759 Calling Seq handler for FW Download 2023:03:03-11:34:14.759 find found NXP_FW_TYPE=(0x1) 2023:03:03-11:34:14.759 GetNxpNumValue: NXP Config Parameter : NXP_FW_TYPE=(0x1) 2023:03:03-11:34:14.759 firmware type from conf file: 1 2023:03:03-11:34:14.759 @@@//usr//lib//libpn7160_fw.so 2023:03:03-11:34:14.759 FW Image Length - ImageInfoLen 34542 2023:03:03-11:34:14.760 FW Image Info Pointer - pImageInfo 0xffffa4080010 2023:03:03-11:34:14.760 FW Major Version Num - 50 2023:03:03-11:34:14.760 FW Minor Version Num - 6 2023:03:03-11:34:14.760 FW Image Length - 34542 2023:03:03-11:34:14.760 FW Image Info Pointer - 0xffffa4080010 2023:03:03-11:34:14.760 phDnldNfc_InitImgInfo:SUCCESS 2023:03:03-11:34:14.760 Processing Normal Sequence.. 2023:03:03-11:34:14.760 Initializing Sequence.. 2023:03:03-11:34:14.760 Response Timer Created Successfully 2023:03:03-11:34:14.760 Inserting FrameId .. 2023:03:03-11:34:14.760 Frame created successfully 2023:03:03-11:34:14.760 GetSessionState Request submitted successfully 2023:03:03-11:34:14.760 PN54X - Write requested..... 2023:03:03-11:34:14.760 PN54X - Invoking I2C Write..... 2023:03:03-11:34:14.761 len = 8 > 0004F2000000F533 2023:03:03-11:34:14.761 PN54X - I2C Write successful..... 2023:03:03-11:34:14.761 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:14.761 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:14.761 Send Success 2023:03:03-11:34:14.762 Response timer started 2023:03:03-11:34:17.262 [ 97.367227] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 0 0 2023:03:03-11:34:17.262 phNxpNciHal_fw_dnld_get_sessn_state_cb - Request Failed, State:255, pInfo: 0x90001908 2023:03:03-11:34:17.262 phDnldNfc_GetSessionState cb failed 2023:03:03-11:34:17.262 phNxpNciHal_fw_seq_handler : FAILED 2023:03:0[ 97.394651] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 1 3-11:34:17.262 phNxpNciHal_fw_dnld_complete: Download Status = 0xff 2023:03:03-11:34:17.262 Fw Download Failed!! 2023:03:03-11:34:17.262 NfccReset, VEN eType 0 2023:03:03-11:34:17.289 NfccReset, VEN eType 1 2023:03:03-11:34:17.406 [ 97.512241] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 2 free library SUCCESS !! 2023:03:03-11:34:17.407 Freeing Mem for Dnld Context.. 2023:03:03-11:34:17.407 Retrying: FW download 2023:03:03-11:34:17.407 find found NXP_SYS_CLK_SRC_SEL=(0x1) 2023:03:03-11:34:17.407 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLK_SRC_SEL=(0x1) 2023:03:03-11:34:17.407 find found NXP_SYS_CLK_FREQ_SEL=(0x0) 2023:03:03-11:34:17.407 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLK_FREQ_SEL=(0x0) 2023:03:03-11:34:17.407 find found NXP_SYS_CLOCK_TO_CFG=(0x1) 2023:03:03-11:34:17.407 GetNxpNumValue: NXP Config Parameter : NXP_SYS_CLOCK_TO_CFG=(0x1) 2023:03:03-11:34:17.407 gphNxpNciHal_fw_IoctlCtx.bClkSrcVal = 0x1 2023:03:03-11:34:17.407 gphNxpNciHal_fw_IoctlCtx.bClkFreqVal = 0x0 2023:03:03-11:34:17.407 gphNxpNciHal_fw_IoctlCtx.bTimeout = 0x1 2023:03:03-11:34:17.407 NfccReset, VEN eType 2 2023:03:03-11:34:17.534 Allocating Mem for Dnld Context.. 2023:03:03-11:34:17.534 Calling Seq handler for FW Download 2023:03:03-11:34:17.534 find found NXP_FW_TYPE=(0x1) 2023:03:03-11:34:17.534 GetNxpNumValue: NXP Config Parameter : NXP_FW_TYPE=(0x1) 2023:03:03-11:34:17.534 firmware type from conf file: 1 2023:03:03-11:34:17.535 @@@//usr//lib//libpn7160_fw.so 2023:03:03-11:34:17.535 FW Image Length - ImageInfoLen 34542 2023:03:03-11:34:17.535 FW Image Info Pointer - pImageInfo 0xffffa4080010 2023:03:03-11:34:17.535 FW Major Version Num - 50 2023:03:03-11:34:17.535 FW Minor Version Num - 6 2023:03:03-11:34:17.535 FW Image Length - 34542 2023:03:03-11:34:17.535 FW Image Info Pointer - 0xffffa4080010 2023:03:03-11:34:17.535 phDnldNfc_InitImgInfo:SUCCESS 2023:03:03-11:34:17.535 Processing Normal Sequence.. 2023:03:03-11:34:17.535 Initializing Sequence.. 2023:03:03-11:34:17.535 Response Timer Created Successfully 2023:03:03-11:34:17.535 Inserting FrameId .. 2023:03:03-11:34:17.535 Frame created successfully 2023:03:03-11:34:17.535 GetSessionState Request submitted successfully 2023:03:03-11:34:17.535 PN54X - Write requested..... 2023:03:03-11:34:17.536 PN54X - Invoking I2C Write..... 2023:03:03-11:34:17.537 len = 8 > 0004F2000000F533 2023:03:03-11:34:17.537 PN54X - I2C Write successful..... 2023:03:03-11:34:17.537 PN54X - Posting Fresh Write message..... 2023:03:03-11:34:17.537 PN54X - Tml Writer Thread Running................ 2023:03:03-11:34:17.537 Send Success 2023:03:03-11:34:17.537 Response timer started [ 100.103038] [dhd] [wlan0] wl_run_escan : LEGACY_SCAN sync ID: 7, bssidx: 0 2023:03:03-11:34:20.037 [ 100.142796] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 0 0 2023:03:03-11:34:20.037 phNxpNciHal_fw_dnld_get_sessn_state_cb - Request Failed, State:255, pInfo: 0x90003f48 2023:03:03-11:34:20.037 phDnldNfc_GetSessionState cb failed 2023:03:03-11:34:20.037 phNxpNciHal_fw_seq_handler : FAILED 2023:03:0[ 100.170182] Inside nfc_dev_ioctl: cmd = 4008e901 arg = 1 3-11:34:20.037 phNxpNciHal_fw_dnld_complete: Download Status = 0xff 2023:03:03-11:34:20.038 Fw Download Failed!! 2023:03:03-11:34:20.038 NfccReset, VEN eType 0 2023:03:03-11:34:20.065 NfccReset, VEN eType 1 2023:03:03-11:34:20.182 free library SUCCESS !! 2023:03:03-11:34:20.182 Freeing Mem for Dnld Context.. 2023:03:03-11:34:20.182 Retrying: FW download 2023:03:03-11:34:20.182 Pavankn ChipType: 9, fw_maj_ver: 80, romVersion: 18 2023:03:03-11:34:20.182 Chip Version Middleware Version mismatch!!!! 2023:03:03-11:34:20.184 PN54X - Write request NOT enabled ^C[ 108.124521] i2c_read: err wakeup of wq Re: PN7160 NFC bring up on Yocto Mickledore Hello @PavanNittala  For your issue, I have forwarded a document to you, which is helpful for you, please check your email box.

event occured timing is varies in eMIOS MCB mode I use eMIOS UC23 as MCB mode. CORE Clock : 100MHz prescaler : all "1" UC23 A register : 5000 I am checking flag interrupts with an oscilloscope, but the timing of event occurrences varies. Please let me know if there are any possible causes for variation. #s32k Re: event occured timing is varies in eMIOS MCB mode There was a problem with the core clock. I reviewed the clock settings and the problem was resolved. Re: event occured timing is varies in eMIOS MCB mode Hi@Aren Could you provide your demo project and test details, we will take the time to help you check it. Re: event occured timing is varies in eMIOS MCB mode A note about variability I want an event to occur every 50us, but the events occur at completely different times, such as 10us, 20us, etc.

S32K344-Can DataFlash and CodeFlash be operated at the same time? Hello Is it possible to write or erase DataFlash and CodeFlash at the same time? BestRegards, Simon Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi @Senlent  Thank you for your response. Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi@Simoin-Liu This is a summary of some consultations between me and our AE colleagues. At the hardware level, it supports multi-core parallel access to different blocks. As for whether there is a conflict if multiple cores access the same register at the same time, this actually needs to be avoided by the fls driver. However, the fls driver we currently provide cannot provide multi-core parallel access to different blocks. Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi@Simon-Liu Please be patient. I need to confirm whether multiple cores can write to different blocks simultaneously. Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi @Senlent  I understand the first answer, "if the Core 0 application is performing a write process in block 0, then the Core 1 at the same time can read a data stored in the data flash block." Because if one block is read while another block is written, only one core will set the PGM and EHV bits of the C40 register MCR. So if two cores write to two blocks at the same time, how can the other core set the PGM and EHV bits again if one core has already set the PGM and EHV bits? Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi@Simon-Liu For single-core and interlocked cores, there is no such problem, because only one CPU core can work. For multi-core, it is possible, which has been explained in the first answer. Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi @Senlent  Is it possible to erase one block while erasing another block? Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi@Simon-Liu Simultaneous read and write operations on the same block are not supported. It is possible to perform read and write operations on different blocks separately. Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi @Senlent  Thanks for your answer. I know that simultaneous reading is possible and there is a "read while writing" function. What I want to confirm is whether simultaneous programming or simultaneous erasing is supported. BestRegards, Simon Re: S32K344-Can DataFlash and CodeFlash be operated at the same time? Hi@Simon-Liu It depends on the situation. For example, AN13388 describes it this way. The Flash memory can perform multiple reads between different blocks by a single, dual or quad read feature, where in a multi-core scenario, if there are multiple threads running in parallel (on different sections/blocks of memory) those threads can occur simultaneously by a dual or quad read, this feature is controlled internally and not by the user. It also has the “Read-While-Write” (RWW) feature to be able to perform a read and a write simultaneously (applies only when operations are in different blocks); for example, in the S32K324, if the Core 0 application is performing a write process in block 0, then the Core 1 at the same time can read a data stored in the data flash block.

How to build - Mcuxpresso command line build with build option I want use command line buld  1. windows  2. Ubuntu linux.  3. using build option; such as option [PREDEFINE_OPT 1], check below   Please explain the usage in case the sample project: (frdmkw38_ble_shell_freertos) Board Design Re: How to build - Mcuxpresso command line build with build option Hello, Hope you are doing well. I would recommend these posts: MCUXpresso IDE v11.8.1 - How to command line build project? - NXP Community mcuxpresso-ide command line and building with the .cproject file settings - NXP Community Command line build - NXP Community Hope this helps! Regards, Ricardo

LS1046Aの起動後、QSPI CSは常にLOW状態になります。 そのLS1046Aを実装したオリジナルボードを作成しました。Flash Programmer を CodeWarrior の JTAG と一緒に使用しようとしましたが、QSPI 信号が機能しません。 具体的には、ブート直後にQSPI_A_CS0信号がHighからLowに遷移しますが、Flash Programmerの起動後にCSが応答しません。 フラッシュ プログラマからの QSPI 消去とダンプは成功しますが、オシロスコープで波形を観察すると、QSPI 信号はアクティビティを示しません。RDBからtccファイルを変更しました。 追加情報:ボード上には、CFG_RCW_SRC[0:8]の値を設定できるDIPスイッチがあります。QSPIモードに設定すると、信号は正常に出力されますが、ハードコードされたRCWモードに設定すると問題が発生します。 Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 すごい！ 47ページの回路をたどってみて、JTAGのTRSTを入力すると、PORESET_Bだけが作動し、RCWが変更されていることが確認できました。 ご回答をよろしくお願い申し上げます。 Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 回路図 を確認するには、AN5252_QorIQ LS1046Aデザインチェックリスト(47ページ)を参照し、PORESET_B、HRESET_B、nRESET、TRSTを確認してください。 POR で書き込み可能にできたDCFG_CCSR_RCWSR13、JTAG が POR を制御するため、おそらく何らかの問題があるため、正しく書き込むことができませんでした。 Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 私はあなたのアドバイスに従ってリセット回路を見直しました。JTAGのTRSTが有効になっているとCPUのPORESET_BとTRST_Bがアクティブになるように修正しましたが、それでもRCW値は変わりません。 申し訳ございませんが、回路図は提供できません。 Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 リセット回路が原因として考えられますので、お客様ご自身で回路図をご確認いただくか、リセット部分とJTAG部分に関する回路図をこちらまでお送りください。 機密の場合は、次のパスで新しいケースを作成できます。 https://www.nxp.com/support/support:SUPPORTHOME 新しいケースに情報ケース#00686870を追加して、さらにサポートします。 ありがとうございます Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 ご返信ありがとうございます。 LS1046ARDBを使って確認してみました。 LS1046ARDBにRCWをセットすると、値が変わりました。 しかし、カスタムボードにRCWをセットしたところ、数値は変わりませんでした。 これが原因だと思います。RCW値が変わらない原因を知っていますか? Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 LS1046ARDBアプリケーションノート 、6.3.3 Hello World CodeWarriorプロジェクトの作成、DCFG_CCSR_RCWSR13値が0x20124000場合は確認の 「 CodeWarriorを使用したRAMブート 」に従ってください 。 ありがとうございます Re: LS1046A が起動した後、QSPI CS は常に LOW 状態になります。 変更してください。 ターゲット初期化ファイルの「USE_SAFE_RCW = False」 に 「USE_SAFE_RCW = 真」 そして、フラッシュプログラマでQSPIを再度フラッシュします。 ありがとうございます。

LS1046A启动后，QSPI CS始终处于低电平状态。 我已经创建了一个实现 LS1046A 的原始电路板。我正在尝试将 Flash 编程器与 CodeWarrior 的 JTAG 一起使用，但 QSPI 信号不起作用。 具体来说，QSPI_A_CS0 信号在启动后立即从高电平转换为低电平，但在 Flash 编程器启动后 CS 没有响应。 QSPI 从 Flash 编程器擦除和转储成功，但是当使用示波器观察波形时，QSPI 信号没有显示任何活动。我从 RDB 修改了 tcc 文件。 附加信息：电路板上有一个 DIP 开关，可以设置 CFG_RCW_SRC[0:8] 的值。当设置为QSPI模式时，信号输出正常，但当设置为硬编码RCW模式时，就会出现问题。 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 惊人的！ 按照47页的电路，我可以确认当JTAG的TRST输入时，只有PORESET_B被激活，并且RCW已经改变。 非常感谢！ 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 请参阅AN5252_QorIQ LS1046A 设计清单，第 47 页，检查 PORESET_B、HRESET_B、nRESET、TRST 以检查您的原理图。 DCFG_CCSR_RCWSR13 只能在 POR 中写入，由于 JTAG 控制 POR 可能存在一些问题，因此无法正确写入。 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 我按照您的建议检查了复位电路。我修改了一下，让JTAG的TRST使能时，CPU的PORESET_B和TRST_B变为有效，但是RCW值仍然没有变化。 抱歉，我无法提供电路图。 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 复位电路可能是原因，请自行检查原理图或将与复位和 JTAG 部分相关的原理图发送给我。 如果是保密的，您可以在以下路径中创建新案例： https://www.nxp.com/support/support:SUPPORTHOME 在新案例中添加信息案例#00686870，以便进一步支持。 谢谢！ 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 感谢你的回复。 我使用 LS1046ARDB 进行了检查。 当我在 LS1046ARDB 上设置 RCW 时，值发生了变化。 但是，当我在自定义板上设置 RCW 时，值并没有改变。 我相信这就是原因。您知道是什么原因导致 RCW 值不改变吗？ 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 请遵循使用 CodeWarrior 在 LS1046ARDB 上进行 RAM 启动的应用说明 , 6.3.3 创建Hello World CodeWarrior工程，检查DCFG_CCSR_RCWSR13的值是否为0x20124000。 谢谢！ 回复：LS1046A启动后，QSPI CS始终处于低电平状态。 请更改 目标初始化文件中的“USE_SAFE_RCW = False” 进入 “USE_SAFE_RCW = 真” 并再次通过闪存编程器刷新 QSPI。 谢谢。

After the LS1046A boots up, the QSPI CS is always in a LOW state. I have created an original board that implements the LS1046A. I am trying to use the Flash Programmer together with the JTAG of CodeWarrior, but the QSPI signals are not functioning. Specifically, the QSPI_A_CS0 signal transitions from High to Low immediately after boot, but the CS does not respond after the Flash Programmer is started. The QSPI erase and dump from the Flash Programmer are successful, but when observing the waveform with an oscilloscope, the QSPI signals do not show any activity. I modified the tcc file from the RDB. Additional information:On the board, there is a DIP switch that allows setting the value of CFG_RCW_SRC[0:8]. When set to QSPI mode, the signals are outputting normally, but when set to hard-coded RCW mode, the issue occurs. Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. Amazing! Following the circuit on page 47, I was able to confirm that when JTAG's TRST is input, only the PORESET_B is activated, and the RCW has been changed. Thank you! Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. Please refer to AN5252_QorIQ LS1046A Design Checklist, page 47, check PORESET_B, HRESET_B, nRESET, TRST to check your schematics. DCFG_CCSR_RCWSR13 only could be writeable in POR, it could not write correctly because the JTAG control the POR probably some issue. Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. I reviewed the reset circuit as per your advice. I modified it so that the CPU's PORESET_B and TRST_B become active when JTAG's TRST is enabled, but the RCW value still does not change. I'm sorry, but I cannot provide the circuit diagram. Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. The reset circuit would be the possible reason, please check the schematics by yourself or send your schematics related to the reset and JTAG part to me here. If it's confidential, you could create a new case in the path below: https://www.nxp.com/support/support:SUPPORTHOME Add information case#00686870 in the new case for the further support. Thanks Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. Thank you for your reply. I checked using the LS1046ARDB. When I set the RCW on the LS1046ARDB, the values changed. However, when I set the RCW on the custom board, the values did not change. I believe this is the cause. Do you know what might be causing the RCW values not to change? Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. Please follow RAM Boot using CodeWarrior on LS1046ARDB Application Note , 6.3.3 Create Hello World CodeWarrior project, check the DCFG_CCSR_RCWSR13 value if it is 0x20124000. Thanks Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. Thank you for your reply. However, as you suggested, I am running it with "USE_SAFE_RCW=True." In that case, the following code becomes effective, but the result does not change. if USE_SAFE_RCW: # Please make sure SERDES REF CLK is set to 100 MHz (SW4[1:2] = 00) # Set rcw_src to the hard-coded RCW option matching the board's DIP SW # regarding SYSCLK and differential/single-ended clock source # use this when SYSCLK = 66 MHz, single-ended clock source # TA.rcw.set_source(0x9A) # use this when SYSCLK = 66 MHz, differential clock source # TA.rcw.set_source(0x9B) # use this when SYSCLK = 100 MHz, single-ended clock source # TA.rcw.set_source(0x9E) # use this when SYSCLK = 100 MHz, differential clock source TA.rcw.set_source(0x9F) # Activate QSPI lines TA.rcw.set_data({13: 0x20124000})   # add here if you need to override other particular RCW values #TA.rcw.set_data({1: 0x40282830, 9: 0x00C12980, 10: 0x00002580}) TA.rcw.apply() Re: After the LS1046A boots up, the QSPI CS is always in a LOW state. Please kindly change the  "USE_SAFE_RCW = False" in the Target Initialization File into "USE_SAFE_RCW = True" And flash the QSPI by the flash programmer again. Thanks.

s32k3x4 -t172 debug error why i am getting this error  Re: s32k3x4-t172 debug error I change probe its working fine thank you Re: s32k3x4-t172 debug error I updated PEMicro software and S32DS Update 14 but still can't reproduce the problem you mentioned. Do you have other development boards? Also, do your colleagues encounter this problem? In addition, from the ssb.PNG, I can see that the S32K3 RTD you installed is version 3.0.0 P01 instead of the RTD 5.0.0 you mentioned before. Re: s32k3x4-t172 debug error i already have all software installed  still i am getting an error message but for Dio example it works after trying 4 to 5 time but not for pother peripheral Re: s32k3x4 -t172 debug error I don't have this problem, please compare my Installation Details Re: s32k3x4 -t172 debug error I am using only Onboard OPEN SDA debugger Re: s32k3x4 -t172 debug error version for s32DS is 3.5 and RTD 5.0.0 yes s32k3x4evb-T172 REV B2 I just check with open sda Re: s32k3x4 -t172 debug error Please tell me: Which version of Update did you install for S32DS v3.5? Which version of S32K3 RTD? Did you update PEMicro Software? Which S32K3 development board? S32K3X4EVB-T172 RevB or RevB2? I have not encountered this problem with the onboard OpenSDA, only when using the external PEMicro Multilink. Re: s32k3x4 -t172 debug error i am not using external debugger its on board debugger only  Re: s32k3x4 -t172 debug error how to configure and where to download Re: s32k3x4 -t172 debug error Hi It is recommended to use the onboard OpenSDA (J40) debugger. Are you using an external PEMicro Multilink debugger? If so, please note: "USB Multilink FX RevA and Universal Rev A and B are based on legacy UF32 USB devices, which are no longer actively supported/validated by PEmicro under the latest plugins/software packages. To get latest support user would need Multilink FX Rev C, Multilink Universal Rev C/D or Multilink ACP" Best Regards, Robin ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------