S32K146费用问题 大家好，团队。我目前正在开发一个使用 S32K146 的项目。我在使用 EB tresos 配置 FEE 模块时遇到了一些问题。您能否提供一些答案或建议？ 如图所示， Fee Block Size和F ee Virtual Page Size之间是什么关系？ 当我将费用虚拟页面大小配置为 8 或 32 时，只有当费用块大小小于或等于 32 时，我才能通过 Fee_Read() 函数检索所需的数据。例如，如果我将Fee Block Size设置为 64（大于 32 的值）并将Fee Virtual Page Size设置为 32，则我无法将数据写入 D-flash，因此也无法读取数据。如果我想将费用块大小设置为 200，我该怎么做？ 感谢您的回复。感谢您的帮助。 回复：S32K146费用问题 嗨，Lukas。现在我可以实现 FEE 功能了，因为我可以直接读出来而不需要等待它写完。你的建议很有帮助。谢谢！ 回复：S32K146费用问题 你好，卢卡斯！谢谢你的回复， 我复制了官方例子提供的读写函数到我的项目中使用，如你的截图所示。S32K146中一个扇区的大小为0x1000。我可以这样理解吗：“Fee Block Size”是用户定义的块大小，其最大值应小于0x1000？这是我的函数调用截图：

RT1052のFlexspiインターフェースの使用 こんにちは、先生 RT1052チップのFlexspiインターフェースの使用方法を確認したいのですが。 1.Flexspiインターフェイスを使用して、NORフラッシュとFPGAの2つのデバイスと通信する必要があり、これらはそれぞれFlexspiAインターフェイスとFlexspiBインターフェイスに対応し、どちらも4線式通信モードを使用します。 2.システムの電源が入った後、2つのデバイスに同時にアクセスする必要があります。これは許可されていますか?具体的には、FLASHで作業しているとき、FPgasの読み書きは許可されていますか? 3.in 特に、FPGAとの通信は通常の2ms通信ですが、FLASHの動作には時間がかかりますが、FPGAとの通信周期に影響はありますか? 4.お勧めのより良いプランはありますか? ありがとうございます！ ブートROM|ブート|フラッシュ 通信&制御(I3C |I2Cの |SPIの |フレックスキャン |イーサネット |FlexIOの) Re:RT1052のFlexspiインターフェースの使用 こんにちは、ハリー RT1052にはFlexSPIコントローラーが2つあるということですか? NORフラッシュの動作中にハードウェアが占有されていることをどのように理解しますか?FPGAへのアクセスが遅れていますか?私が使用すると、FlexSPI_Aインターフェースの信号がFLASHに接続され、FlexSPI_B FPGAデバイスに接続されます。 2つのFlexSPIコントローラを使用して、2つのFlexSPIインターフェースを完全に独立して制御することで、FlexSPI_AとFlexSPI_Bを行うということですか?2 つの FlexSPI インターフェイスを完全に独立して制御する設定の例はどこで入手できますか。 感謝！ ジアシン

この FreeRTOS のヒープ使用量の表示は破損を示唆していますか? 奇妙な質問ですが、デバッガーの FreeRTOS の [ヒープ使用量] タブの添付されたスナップショットは、データの破損を示唆していますか? 通常、実行中のファームウェアで使用されているものを表す緑色の領域と、空いている/割り当てられていない白い領域が表示されていると思います。私の画像では、白であると思っていた大きな領域が、代わりに薄緑色になっていることがわかります。 ばかげているように聞こえることはわかっていますが、過去にオーバーフロー/データ破損中にデバッガータブが奇妙に報告されるのを見たことがあります。あそこにはライトグリーンの色は見たことがありません。それは単に、ヒープが不足に近づいていることを示していますか? Re: この FreeRTOS ヒープ使用量の表示は破損を示唆していますか? こんにちは いいえ、色はデータの破損を示唆するものではなく、IDEビューのバグのようです。 このビューには、ヒープ上の使用済みスペースと使用可能なスペースのみが表示されます。 よろしくお願いいたします オマル

How to explain the MC33665 TPL2 Message I‘m learning the MC33665 datasheet .in "5.2.3"TPL2 protocol , the message lenght is 48bit,however the second 16bit data is larger than 16bit.how can i understund it  i mean MS =1bit, RADD=7bit, MADD=1bit,CADD=3bit,DADD=6bit, total is 18bit,that is larger than 16bit ? Re: How to explain the MC33665 TPL2 Message Hi, The AN13281 is classified as a secure file requiring an NDA. You can download it directly from: https://www.nxp.com/webapp/sd/collateral/1644500428545720962128?version=0.1 or from: https://www.nxp.com/mynxp/secure-files In case of any problems with your secure access rights, please contact support. BRs, Tomas Re: How to explain the MC33665 TPL2 Message where can i get AN13281.my security access goes wrong. it‘s not working after i got the MC33665A-datasheet Re: How to explain the MC33665 TPL2 Message Hi, Please have a look at our AN13281 - that describes the TPL2 message frame in detail and provides other useful information. BRs, Tomas

IMX8Mplus LPDDR4 EVKでCSI2-MIPIインターフェースを使用したい IMX8Mplus LPDDR4 EVKを使用しており、IMXLXYOCTOUG v.LF6.1.55_2.2.0BSPバージョンをビルドしています。 CSI2-MIPI interface.it の使用方法が検出されません。どのような設定が必要ですか? ov5640カメラを使用していますが、このカメラをCSI1-MIPIインターフェースに接続すると、カメラが機能します。 CSI2-MIPI インターフェイスに接続していると、機能していません。その理由は何ですか?どなたかご存知の方がいらっしゃいましたら、助けてください。 ありがとう&よろしく スリニヴァス Re: imx8mplus lpddr4 evk で csi2-mipi インターフェイスを使用したい 0v5640カメラセンサーをCSI2-MIPIインターフェースに接続しています Re: imx8mplus lpddr4 evk で csi2-mipi インターフェイスを使用したい 私のfdtfile = imx8mp-evk.dtb 「FATLS MMC 1:1」実行後 それはたくさんのDTBファイルを提供します。「imx8mp-evk-basler-ov5640.dtb」または「imx8mp-evk-os08a20-ov5640.dtb」のどちらであるか説明していただけますか?ファイルが読み取られるかどうか。ubootファイルでfdtfile=imx8mp-evk-basler-ov5640.dtbを変更する必要がありますか。 Re: imx8mplus lpddr4 evk で csi2-mipi インターフェイスを使用したい DTBファイルの意味を設定し、変数fdtfileをfdtfile=imx8mp-evk.dtbに指定したファイル名に変更します。それは正しいですか?ubootファイルを添付しました。 ありがとうとよろしくお願いします スリニバス Re: imx8mplus lpddr4 evk で csi2-mipi インターフェイスを使用したい こんにちはスリニヴァス、 最初に、デバイス・ツリーの CSI2-MIPI ノードを確認できます。 ov5640 カメラに CSI2-MIPI 用のノードがあり、状態が [ok] に設定されているかどうかを確認します。 ov5640 カメラの CSI2-MAPI にノードがない場合は、CSI1-MAPI のノードに基づいてノードを作成してみてください。 よろしくお願いします。 キンバリー・カルバハル 組み込みソフトウェアエンジニア - RidgeRun お問い合わせ:support@ridgerun.com 開発者 Wiki: https://developer.ridgerun.com ウェブサイト: www.ridgerun.com

S32k311 Flash programmer Hello everyone, I am using S32 Design Studio for S32 Platform Version: 3.5 and I am trying to flash a program through S32 Flash programmer icon but it is not enabled. I only Flash a program using a debug icon. If anyone knows how to enable the S32 Flash Programmer, I appreciate it. Regards, Alvaro  S32 SDK for Power Architecture® S32 SDK for S32K1 S32 SDK for S32V Re: S32k311 Flash programmer Hi Alvaro, S32K is not in the list of Supported target devices. Please read S32_Flash_Tool_Release_Notes.pdf or S32_Flash_Tool_User_Guide.pdf (C:\NXP\S32DS.3.5\S32DS\tools\S32FlashTool\doc) 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. -------------------------------------------------------------------------------

Does this FreeRTOS Heap Usage display suggest corruption? It's an odd question, but does the attached snapshot of the debugger's FreeRTOS' Heap Usage tab suggest data corruption?  I think it normally shows green areas representing those that are being used by the running firmware, and white areas that are free/unallocated.  In my image, you can see the big area that I would expect to be white is instead light green. I know it sounds silly, but I've seen the debugger tabs report oddly in the past during an overflow/data corruption.  I've never seen a light green color there before.  Is it merely and indication that I'm closer to running out of heap? Re: Does this FreeRTOS Heap Usage display suggest corruption? Hello No, the color does not suggest data corruption, it seems like a bug on the IDE view.  This view only shows used and available space on heap.  Best regards, Omar

i.MX93 TMU errata ERR052243 I've found this patch on linux-imx GitHub repository, containing an iMX93 TMU workaround for ERR052243 However I cannot find the ERR052243 itself on NXP site, does anybody knows where to find it or has any additional reference on this errata? Kind Regards, Andrea Re: i.MX93 TMU errata ERR052243 Hello, Has this errata ever been documented? Thanks, Frank Re: i.MX93 TMU errata ERR052243 Hi, @andreascian! I don't have an expected day but our team is working on the document to release it as soon as possible. Best Regards! Chavira Re: i.MX93 TMU errata ERR052243 @Chavira thanks for the confirm do you have any expected publication date for this new errata document? Re: i.MX93 TMU errata ERR052243 Hi, @andreascian! Thank you for contacting NXP Support! The ERR052243 should be added to the next version of the errata document. Sorry for the mistake! Best Regards! Chavira

i.MX6 CAAM - keyblob decryption fails after kernel upgrade Hi, We are currently upgrading a custom board from Kernel 4.1 to 5.15. We are using NXP's CAAM driver to securely store a keyblob. After updating on a security-enabled device, decryption fails. Adding some debug prints in sm_store.c yields that the job returns with JRSTA_CCBERR_ERRID_ICVCHKL If I print the status instead of just returning -EBADMSG, I get the following output:  [ 30.153764] caam_jr 2101000.jr: 2000081a: CCB: desc idx 8: AES: ICV check failed. [ 30.161259] caam_jr 2101000.jr: 2000081a: CCB: desc idx 8: AES: ICV check failed. The raw return value is 0x2000 081A, in case there is more information there.  nbsp;w Any help is highly welcome. I can of course provide more information if needed. Thanks in advance and best regards Niklas Reisser Re: i.MX6 CAAM - keyblob decryption fails after kernel upgrade Hi, thanks for the replies. We were able to find the solution in the updated kernel module which extracts the key. Kind regards, Niklas Re: i.MX6 CAAM - keyblob decryption fails after kernel upgrade The transition between kernels can introduce subtle changes in cryptographic APIs or hardware interactions that aren’t immediately apparent but have far-reaching implications, like in this case with keyblob handling and AES operations. Debugging such issues not only requires a deep understanding of the kernel internals but also a meticulous review of descriptor handling and parameter consistency. It’s impressive to see how tightly coupled cryptographic integrity checks are to kernel upgrades—almost like a puzzle where one misplaced piece can disrupt the entire system. Re: i.MX6 CAAM - keyblob decryption fails after kernel upgrade Hi, Did you use caam_keygen to generate the keyblob in bsp5.15? If not, it is recommended to use caam_keygen. Regards Harvey

Bytes to Float not working Hello all. I am trying to convert some bytes that I receive from CAN to a float variable. However, the result is not correctly. I tried to change from little endian to big endian, not works. For example, I am receiving the data 0x40333333, it`s suposed to be 2.8, but the result is totally different. The images below will help to explain the situation (the variable that I am focusing in this example is cellParams.underVoltage😞 - variable initialiazion cellParams.underVoltage = 2.80; - initialization confirmation: So after the initialization, I will send a CAN command to change the value (I will send the same value) The new value is in the image below, from buffer position 3 until 6 When I receive the buffer, I try to do the following: int dummyInt = DeserializeInt32(&cmdMsg->data[3]); //cellParams.underVoltage = atof(&cmdMsg->data[3]); (same problem...) cellParams.underVoltage = (float)(dummyInt); static uint32_t DeserializeUint32(const uint8_t *buffer) {     int value = 0;       value += (int)buffer[3] << 24U;     value += (int)buffer[2] << 16U;     value += (int)buffer[1] << 8U;     value += (int)buffer[0];     return value; }   the returned value to dummyInt is OK: The float value, before cellParams.underVoltage = (float)(dummyInt), is: And after cellParams.underVoltage = (float)(dummyInt), is: but if I check the variable (not in memory monitor), the hex value looks fine, but the float value lookw incorrect: PS.: I tried atof, memcpy, not success. Could someone help me? Thanks in advance! Re: Bytes to Float not working Hello, thank you so much for the answer. Memcpy not worked for me, but I found another solution (thats similar to memcpy, but that`s the onlyone that worked...) static float DeserializeFloat(const uint8_t *buffer) { uint32_t value = 0;   value |= buffer[3] << 24U; value |= buffer[2] << 16U; value |= buffer[1] << 8U; value |= buffer[0]; float f = *((float*)&value); return f; }   Anyway, thank you very much for your time. Re: Bytes to Float not working Hi,  I tried it on my side and only working method for me is memcpy - like this:  unsigned int counter = 0x40333333; float f=0.0; memcpy(&f,&counter,4); 

i want to use csi2-mipi interface in imx8mplus lpddr4 evk i am using imx8mplus lpddr4 evk, i build the IMXLXYOCTOUG v.LF6.1.55_2.2.0  bsp version. how to use the CSI2-MIPI interface.it is not detecting. what are the configurations I have to do? I am using the ov5640 camera, when I connect this camera to the CSI1-MIPI interface, the camera works. suppose I connect to the CSI2-MIPI  interface, it is not working. what is the reason? if anyone knows please help me out. Thanks &Regards Srinivas Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk i am connecting 0v5640 camera sensor to CSI2-MIPI interface Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk my fdtfile =imx8mp-evk.dtb after running "fatls mmc 1:1" it gives lots of dtb files . can you explain whether "imx8mp-evk-basler-ov5640.dtb" or "imx8mp-evk-os08a20-ov5640.dtb" files are read or not . is it required to change fdtfile=imx8mp-evk-basler-ov5640.dtb in uboot file Hit any key to stop autoboot: 0 u-boot=> u-boot=> fatls mmc 1:1 32856576 Image 58151 imx8mp-ab2.dtb 87685 imx8mp-evk-8mic-swpdm.dtb 87100 imx8mp-evk-basler-ov2775.dtb 86771 imx8mp-evk-basler-ov5640.dtb 85910 imx8mp-evk-basler.dtb 86823 imx8mp-evk-dpdk.dtb 66170 imx8mp-evk-dsp.dtb 86745 imx8mp-evk-dual-basler.dtb 86682 imx8mp-evk-dual-os08a20.dtb 86858 imx8mp-evk-dual-ov2775.dtb 86748 imx8mp-evk-ecspi-slave.dtb 86911 imx8mp-evk-flexcan2.dtb 88590 imx8mp-evk-hifiberry-dacplus.dtb 3059 imx8mp-evk-inmate.dtb 88089 imx8mp-evk-iqaudio-dacplus.dtb 88089 imx8mp-evk-iqaudio-dacpro.dtb 86963 imx8mp-evk-it6263-lvds-dual-channel.dtb 86786 imx8mp-evk-jdi-wuxga-lvds-panel.dtb 86991 imx8mp-evk-ndm.dtb 87119 imx8mp-evk-os08a20-ov5640.dtb 85973 imx8mp-evk-os08a20.dtb 87265 imx8mp-evk-ov2775-ov5640.dtb 87380 imx8mp-evk-ov2775.dtb 86911 imx8mp-evk-pcie-ep.dtb 89118 imx8mp-evk-revA3-8mic-revE.dtb 87446 imx8mp-evk-rm67191.dtb 87419 imx8mp-evk-rm67199.dtb 87895 imx8mp-evk-root.dtb 66874 imx8mp-evk-rpmsg-lpv.dtb 66898 imx8mp-evk-rpmsg.dtb 66247 imx8mp-evk-sof-pdm.dtb 66580 imx8mp-evk-sof-wm8960.dtb 86163 imx8mp-evk-spdif-lb.dtb 88743 imx8mp-evk-usdhc1-m2.dtb 86805 imx8mp-evk.dtb 8528 imx8mp_m7_TCM_hello_world.bin 139272 imx8mp_m7_TCM_low_power_wakeword.bin 20704 imx8mp_m7_TCM_rpmsg_lite_pingpong_rtos_linux_remote.bin 20096 imx8mp_m7_TCM_rpmsg_lite_str_echo_rtos.bin 56556 imx8mp_m7_TCM_sai_low_power_audio.bin 574328 tee.bin System Volume Information/ 56 .dropbox.device 43 file(s), 1 dir(s) Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk my fdtfile =imx8mp-evk.dtb after running "fatls mmc 1:1" it gives lots of dtb files . can you explain whether "imx8mp-evk-basler-ov5640.dtb" or "imx8mp-evk-os08a20-ov5640.dtb" files are read or not . is it required to change fdtfile=imx8mp-evk-basler-ov5640.dtb in uboot file . Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk Hi @srinivas_123! Yes, that is correct.   You can check the device trees saved on the memory using the next commands: "fatls mmc 1:1" for SD card boot "fatls mmc 2:1" for MMC boot Best Regards! Chavira                         Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk set the dtb file means , change  variable fdtfile with file name  you given   fdtfile=imx8mp-evk.dtb .is it correct ?. i attached the uboot file . thanks and Regards srinivas Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk Hi @srinivas_123! Thank you for contacting NXP Support!   For iMX8MP you should set the device tree called "imx8mp-evk-basler-ov5640.dtb" or "imx8mp-evk-os08a20-ov5640.dtb" https://www.nxp.com/docs/en/release-note/IMX_LINUX_RELEASE_NOTES.pdf Best Regards! Chavira Re: i want to use csi2-mipi interface in imx8mplus lpddr4 evk Hi Srinivas, You could first check the CSI2-MIPI node in the device-tree. Check if there is a node for the ov5640 camera for the CSI2-MIPI and the state is set to "okay". If the ov5640 camera does not have a node in the CSI2-MIPI you can try create it based on the node for the CSI1-MIPI. Regards, Kimberly Carvajal Embedded SW Engineer at RidgeRun Contact us: support@ridgerun.com Developers wiki: https://developer.ridgerun.com Website: www.ridgerun.com

我想在 imx8mplus lpddr4 evk 中使用 csi2-mipi 接口 我正在使用 imx8mplus lpddr4 evk，我构建了 IMXLXYOCTOUG v.LF6.1.55_2.2.0 bsp 版本。 如何使用CSI2-MIPI接口。它没有检测。我必须做哪些配置？ 我正在使用ov5640相机，当我将此相机连接到CSI1-MIPI接口时，相机就可以工作了。 假设我连接到CSI2-MIPI接口，它不起作用。原因是什么？如果有人知道，请帮助我。 谢谢与问候 斯里尼瓦斯 回复：我想在 imx8mplus lpddr4 evk 中使用 csi2-mipi 接口 我正在将 0v5640 摄像头传感器连接到 CSI2-MIPI 接口 回复：我想在 imx8mplus lpddr4 evk 中使用 csi2-mipi 接口 我的 fdtfile =imx8mp-evk.dtb 运行“fatls mmc 1:1”后 它提供了许多 dtb 文件。你能解释一下“imx8mp-evk-basler-ov5640.dtb”还是“imx8mp-evk-os08a20-ov5640.dtb”吗？文件是否被读取。是否需要在 uboot 文件中更改 fdtfile=imx8mp-evk-basler-ov5640.dtb 。 回复：我想在 imx8mplus lpddr4 evk 中使用 csi2-mipi 接口 设置 dtb 文件意味着，用给定的文件名fdtfile=imx8mp-evk.dtb更改变量fdtfile 。对吗？我附加了 uboot 文件。 谢谢并问候 斯里尼瓦斯 回复：我想在 imx8mplus lpddr4 evk 中使用 csi2-mipi 接口 你好， Srinivas， 您可以先检查设备树中的 CSI2-MIPI 节点。检查 CSI2-MIPI 对应的 ov5640 摄像头节点是否存在，并且状态是否设置为“okay”。 如果 ov5640 摄像头在 CSI2-MIPI 中没有节点，您可以尝试基于 CSI1-MIPI 的节点创建它。 此致， 金伯利·卡瓦哈尔 RidgeRun 嵌入式软件工程师 联系我们：support@ridgerun.com 开发者维基： https://developer.ridgerun.com 网站: www.ridgerun.com

Write operation for internal flash in mcxa153 is not working Hi, i want to use internal flash memory on mcxa-153 frdm development board, i went through the sdk example of flashiap in mcuxpresso ide , to know how to write or read from flash, but those API functions provided in example only works for read operation, any attempt to write to flash throws an bus fault. below functions didnt work for me :- FLASH_API->flash_erase_sector(&s_flashDriver, destAdrss, pflashSectorSize, kFLASH_ApiEraseKey); FLASH_API->flash_program_page(&s_flashDriver, destAdrss, (uint8_t *)s_buffer, sizeof(s_buffer)); but any functions that attempts only to read flash is working fine like example:- flash_verify_erase_sector(&s_flashDriver, destAdrss, pflashSectorSize); FLASH_API->flash_verify_program(&s_flashDriver, destAdrss, sizeof(s_buffer), (const uint8_t *)s_buffer, &failedAddress, &failedData); FLASH_API->flash_get_property(&s_flashDriver, kFLASH_PropertyPflashSectorSize, &pflashSectorSize); destAdrss given here is last second sector address and block base address is 0x00 :- #define SECTOR_INDEX_FROM_END 2U destAdrss = pflashBlockBase + (pflashTotalSize - (SECTOR_INDEX_FROM_END * pflashSectorSize)); Can i please know if am missing something or using these functions wrongly?. Thank You Boot ROM|Booting | Flash MCXA Re: Write operation for internal flash in mcxa153 is not working Thanks for the solution, It solved the issue. Re: Write operation for internal flash in mcxa153 is not working Hello @Gurunath  Sorry above code is for new version SDK v2.16.0. For SDK v2.14.0, please test below code: __attribute__ ((weak)) void SystemInit (void) {   SCB->CPACR |= ((3UL << 0*2) | (3UL << 1*2)); /* set CP0, CP1 Full Access in Secure mode (enable PowerQuad) */ #if defined (__ARM_FEATURE_CMSE) && (__ARM_FEATURE_CMSE == 3U) SCB_NS->CPACR |= ((3UL << 0*2) | (3UL << 1*2)); /* set CP0, CP1 Full Access in Normal mode (enable PowerQuad) */ #endif /* (__ARM_FEATURE_CMSE) && (__ARM_FEATURE_CMSE == 3U) */   SCB->NSACR |= ((3UL << 0) | (3UL << 10)); /* enable CP0, CP1, CP10, CP11 Non-secure Access */   #if defined(__MCUXPRESSO) extern void(*const g_pfnVectors[]) (void); SCB->VTOR = (uint32_t) &g_pfnVectors; #else extern void *__Vectors; SCB->VTOR = (uint32_t) &__Vectors; #endif /* Enable the LPCAC */ SYSCON->LPCAC_CTRL |= SYSCON_LPCAC_CTRL_LPCAC_MEM_REQ_MASK; SYSCON->LPCAC_CTRL &= ~SYSCON_LPCAC_CTRL_DIS_LPCAC_MASK;   /* Enable flash RWX when FLASH_ACL in IFR0 is invalid */ if ((*((volatile const uint32_t *)(0x1000000)) == 0xFFFFFFFFU) || ((*((volatile const uint32_t *)(0x1000000)) == 0x59630000U) && (*((volatile const uint32_t *)(0x1000040)) == 0xFFFFFFFFU) && (*((volatile const uint32_t *)(0x1000044)) == 0xFFFFFFFFU))) { /* Enable MBC register written with GLIKEY index15 */ GLIKEY0->CTRL_0 = 0x00060000U; GLIKEY0->CTRL_0 = 0x0002000FU; GLIKEY0->CTRL_0 = 0x0001000FU; GLIKEY0->CTRL_1 = 0x00290000U; GLIKEY0->CTRL_0 = 0x0002000FU; GLIKEY0->CTRL_1 = 0x00280000U; GLIKEY0->CTRL_0 = 0x0000000FU;   /* Enable RWX for GLBAC0 */ MBC0->MBC0_MEMN_GLBAC[0] = 0x7700U;   /* Use GLBAC0 for all flash block */ // for (uint8_t i = 0; i < 2U; i++) // { // MBC0->MBC_INDEX[0].MBC_DOM0_MEM0_BLK_CFG_W[i] = 0x00000000U; // } MBC0->MBC_DOM0[0].MBC0_DOM_MEM0_BLK_CFG_W0 = 0x00000000U; MBC0->MBC_DOM0[0].MBC0_DOM_MEM0_BLK_CFG_W1 = 0x00000000U; /* Disable MBC register written */ GLIKEY0->CTRL_0 = 0x0002000FU; } SystemInitHook(); }       BR Alice Re: Write operation for internal flash in mcxa153 is not working Hi Alice, Thanks for clearing my doubt, i tried modifying system_init(), as you said but am getiing an error as mentioned below: /device/system_MCXA153.c:98:17: error: 'MBC_Type' has no member named 'MBC_INDEX' 98 | MBC0->MBC_INDEX[0].MBC_MEMN_GLBAC[0] = 0x7700U; | ^~ ../device/system_MCXA153.c:103:21: error: 'MBC_Type' has no member named 'MBC_INDEX' 103 | MBC0->MBC_INDEX[0].MBC_DOM0_MEM0_BLK_CFG_W[i] = 0x00000000U; can you please help me with this? Thank you Re: Write operation for internal flash in mcxa153 is not working Hello @Gurunath  This is because in the default state after booting, the flash is protected by the ROM using the MBC and no erase/write operations are allowed. There are two ways to solve this: Modify the CMPA to configure the default MBC setting as mentioned in the example's readme. Configure the MBC in the application code, please refer to below code, this has been integrated in new SDK and will be released in next version. __attribute__ ((weak)) void SystemInit (void) { SCB->CPACR |= ((3UL << 0*2) | (3UL << 1*2)); /* set CP0, CP1 Full Access in Secure mode (enable PowerQuad) */ #if defined (__ARM_FEATURE_CMSE) && (__ARM_FEATURE_CMSE == 3U) SCB_NS->CPACR |= ((3UL << 0*2) | (3UL << 1*2)); /* set CP0, CP1 Full Access in Normal mode (enable PowerQuad) */ #endif /* (__ARM_FEATURE_CMSE) && (__ARM_FEATURE_CMSE == 3U) */ SCB->NSACR |= ((3UL << 0) | (3UL << 10)); /* enable CP0, CP1, CP10, CP11 Non-secure Access */ #if defined(__MCUXPRESSO) extern void(*const g_pfnVectors[]) (void); SCB->VTOR = (uint32_t) &g_pfnVectors; #else extern void *__Vectors; SCB->VTOR = (uint32_t) &__Vectors; #endif /* Enable the LPCAC */ SYSCON->LPCAC_CTRL |= SYSCON_LPCAC_CTRL_LPCAC_MEM_REQ_MASK; SYSCON->LPCAC_CTRL &= ~SYSCON_LPCAC_CTRL_DIS_LPCAC_MASK; /* Enable flash RWX when FLASH_ACL in IFR0 is invalid */ if ((*((volatile const uint32_t *)(0x1000000)) == 0xFFFFFFFFU) || ((*((volatile const uint32_t *)(0x1000000)) == 0x59630000U) && (*((volatile const uint32_t *)(0x1000040)) == 0xFFFFFFFFU) && (*((volatile const uint32_t *)(0x1000044)) == 0xFFFFFFFFU))) { /* Enable MBC register written with GLIKEY index15 */ GLIKEY0->CTRL_0 = 0x00060000U; GLIKEY0->CTRL_0 = 0x0002000FU; GLIKEY0->CTRL_0 = 0x0001000FU; GLIKEY0->CTRL_1 = 0x00290000U; GLIKEY0->CTRL_0 = 0x0002000FU; GLIKEY0->CTRL_1 = 0x00280000U; GLIKEY0->CTRL_0 = 0x0000000FU; /* Enable RWX for GLBAC0 */ MBC0->MBC_INDEX[0].MBC_MEMN_GLBAC[0] = 0x7700U; /* Use GLBAC0 for all flash block */ for (uint8_t i = 0; i < 2U; i++) { MBC0->MBC_INDEX[0].MBC_DOM0_MEM0_BLK_CFG_W[i] = 0x00000000U; } /* Disable MBC register written */ GLIKEY0->CTRL_0 = 0x0002000FU; } SystemInitHook(); } BR Alice Re: Write operation for internal flash in mcxa153 is not working Hi, i tried to run the example as it is without modification, but it didnt work, it gave an hard fault(bus error). this error occurs only when functions like erase_sector or program_page were called(mostly those that performs write to flash). Since in example, erase sector is being called first, execution doesnt return from function call due to this error, so the error message was not print based on return value. i have got these active faults when run, Active faults Bus Fault (BFSR) BFARVALID (7) BusFault Address Register (BFAR) valid flag PRECISERR (1) Precise data bus error Hard Fault (HFSR) FORCED (30) Indicates a forced hard fault, generated by escalation of a fault with configurable priority that cannot be handled, either because of priority or because it is disabled Re: Write operation for internal flash in mcxa153 is not working Hello @Gurunath  1) "below functions didn't work for me :" ->> Please describe more detail about how it didn't work. What the return status of "flash_program_page "? 2) Does the flashiap work well on your side? Please run it first. BR Alice

MIMXRT1060 - ENET statistics not working Hello, Question refers to: MIMXRT1060-EVKB, example: evkbmimxrt1060_lwip_ping_freertos Ethernet connection was established. I can ping the device. I see lwip statistics which are incremented. I would like to see MAC's stats but it looks like statistics are not build. Values of statistics registers are always 0. I am looking at ENET_BASE (0x402D8000u): I suppose somewhere in MAC registers there is BIT for enablin/disabling statistisc. Unfortunetally, I didn't found such an option in Reference Manual. Could you pleas help with that? Why ENET statistics not working?  Re: MIMXRT1060 - ENET statistics not working Hi @timmek , Thanks for your interest in NXP MIMXRT series! And sincerely apologize for the late reply. The issue you mentioned is the same as this one:https://community.nxp.com/t5/i-MX-RT/i-MX-RT-serires-How-to-read-out-the-register-value-from-Rx/m-p/982764 Please try this solution.  Best regards, Gavin Re: MIMXRT1060 - ENET statistics not working Does anyone work with ENET and can tell me why the interface statistics are not working? I appreciate any help.

GUIDER编译时出现这种错误 error: invalid storage class for function 'scrSetting1_btnClose_event_handler'是怎么回事？ GUI_GUIDER编译时出现以下错误，请问是什么原因造成的？ "Compiling C:/NXP/GUI-Guider-Projects/TSVWI_V1.7.2_240517/lvgl-simulator/../generated/events_init.c" C:/NXP/GUI-Guider-Projects/TSVWI_V1.7.2_240517/lvgl-simulator/../generated/events_init.c: In function 'scrSetting1_btnDigiENT_event_handler': C:/NXP/GUI-Guider-Projects/TSVWI_V1.7.2_240517/lvgl-simulator/../generated/events_init.c:6352:13: error: invalid storage class for function 'scrSetting1_btnClose_event_handler' 6352 | static void scrSetting1_btnClose_event_handler (lv_event_t *e) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ C:/NXP/GUI-Guider-Projects/TSVWI_V1.7.2_240517/lvgl-simulator/../generated/events_init.c:8067:1: error: expected declaration or statement at end of input 8067 | } | ^ Makefile:102: recipe for target 'build/object/generated/events_init.o' failed mingw32-make: *** [build/object/generated/events_init.o] Error 1 mingw32-make: *** Waiting for unfinished jobs.... 回复： GUIDER编译时出现这种错误 error: invalid storage class for function 'scrSetting1_btnClose_event_handler'是怎 原因找到了，有个事件函数里缺少了一个括号“}”。

S32G-PROCEVB3-S board Hello,  In S32G-PROCEVB3-S board – REV A Schematics.pdf p. 17 U140 and U143 Multiplexer both have SD_MUX_TXN signals to A0_P. Q1: SD_MUX_TXN is a signal input to Multiplexer, is that correct? Q2: what is SD_MUX_TXN? where is it from S32G? I cannot find it in other pages. Thanks Re: S32G-PROCEVB3-S board "connecting the output of U140 to the input of U143" Thanks Daniel, it is clear. Re: S32G-PROCEVB3-S board Hi, As told before, the signal is a point-to-point connection between U140 and U143. There is no purpose other than connecting the output of U140 to the input of U143. As of who provides it, the specific signal of SD_MUX_TXN, it is being provided by the output of the multiplexer/demultiplexer U140. Depending on the setting of the multiplexer, can be either being routed to B0 or C0 of U140. More information on regards of U140, we can recommend opening a ticket under the NXP online services, since this community is related to S32G rather than multiplexer/demultiplexer technology. We do apologize. Please, let us know. Re: S32G-PROCEVB3-S board Hello Daniel, What is the purpose of this signal? Where/who provide it? Thanks Re: S32G-PROCEVB3-S board Hi, For the information provided under the schematic, since the signals are the transmission lines (TX), and the signals shown at the right side of the image go to the physical connector, we can say that the signals are seen as an output from U140. Please, let us know. Re: S32G-PROCEVB3-S board Hello Daniel, Thanks for the update. What is the purpose of this signal? From U140 perspective, is it a input signal? Thanks Re: S32G-PROCEVB3-S board Hi, We might be misunderstanding the overall inquiry, if so we apologize. The signal you are referring to is a point-to-point connection between U140 and U143, as shown under the schematic: These are not directly connected to the S32G. Please, let us know.

Nitrogen8M fails to detect Wi-Fi module Hi, I am working on a project using the Nitrogen8M Plus SMARC and the M2-JODY-W3 Wi-Fi 6 module. I am experiencing difficulty in getting the Nitrogen8M board to recognize the Wi-Fi module. I have successfully loaded the NXP drivers (moal and mlan, available at http://github.com/nxp-imx/mwifiex.git) for the module based on the NXP 88W9098 chipset. Additionally, I have used the 88W9098 firmware from https://github.com/NXP/imx-firmware.   After running the command "modprobe moal mod_para=nxp/wifi_mod_para.conf," the drivers were successfully installed into the kernel. However, the mlan0 interface remains down. The configuration file wifi_mod_para.conf is set with the following parameters:   PCIE9098_0 = { cfg80211_wext=0xf wfd_name=p2p max_vir_bss=1 cal_data_cfg=none drv_mode=7 ps_mode=2 auto_ds=2 mac_addr=00:50:43:20:12:34 fw_name=nxp/pcieuart9098_combo_v0.bin }   PCIE9098_1 = { cfg80211_wext=0xf wfd_name=p2p max_vir_bss=1 cal_data_cfg=none drv_mode=7 ps_mode=2 auto_ds=2 mac_addr=00:50:43:20:52:56 fw_name=nxp/pcieuart9098_combo_v0.bin }   I would appreciate any assistance you can provide in resolving this issue.   Best regards Re: Nitrogen8M fails to detect Wi-Fi module Hi, @SimaoLeite  Thanks for your reply and congratulations for your great job! Such a good news to hear. Have a nice day. Best regards, Christine. Re: Nitrogen8M fails to detect Wi-Fi module Hi, @Christine_Li I have solved my issue by updating my Linux Kernel to version 6.1.22. It appears that Linux Kernel version 5.15.71 does not support the new generation of PCIe. Thank you for all your replies. Best regards, Simão Leite Re: Nitrogen8M fails to detect Wi-Fi module Hi, @Christine_Li The default device tree source file I am using is imx8mp-nitrogen_smarc.dts. I have also tested another DTS file, particularly imx8mp-nitrogen8mp.dts, and encountered the same issue. While I observed some differences between these two files, none seemed significant. Attached are all the relevant DTS files and the dmesg logs from the imx8mp-nitrogen8mp.dts file (The logs previously provided are the result of using the imx8mp-nitrogen_smarc.dts file). Concerning my host platform, I am also confused by the "imx6q" output. However, I can ensure that I am working with the Nitrogen8M board. The Linux Kernel repository I am using is available at "https://github.com/boundarydevices/linux/tree/boundary-imx_5.15.y" Thanks, Simão Re: Nitrogen8M fails to detect Wi-Fi module Hi, @SimaoLeite  From your given logs, I saw some PCIE error logs. It seems that your PCIE driver has problem, then Wi-Fi driver can not be loaded successfully. ====== [ 2.564136] pcie phy pipe clk is not ready [ 2.568247] phy phy-32f00000.pcie-phy.4: phy init failed --> -110 [ 2.568255] imx6q-pcie 33800000.pcie: Waiting for PHY PLL ready timeout! [ 2.588773] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout [ 2.602304] Console: switching to colour frame buffer device 100x37 [ 2.629670] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.631690] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [ 2.637264] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound [ 2.664168] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges: [ 2.668723] pps pps0: new PPS source ptp0 [ 2.671429] imx6q-pcie 33800000.pcie: No bus range found for /soc@0/pcie@33800000, using [bus 00-ff] [ 2.684784] imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000 [ 2.692998] imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000 [ 2.701303] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.706815] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound ========== Please check your dts, especially PCIE part. Also, I am confused with this print: "imx6q", it is not matched with your host platform: "Nitrogen8M" Can you please help to double confirm your host platform? And also please share to me your device tree file, so that I can check it further. Best regards, Christine. Re: Nitrogen8M fails to detect Wi-Fi module Hi, @Christine_Li First of all, thanks for the reply. I am using the Linux Kernel 5.15.71, and my full dmesg log is shown below root@nitrogen8mp:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 5.15.71-2.2.0+yocto+gaaf028b285b7+p0 (oe-user@oe-host) (aarch64-agl-linux-gcc (GCC) 11.4.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Tue Feb 27 02:13:20 UTC 2024 [ 0.000000] Machine model: Boundary i.MX8MPlus nitrogen8mp smarc board [ 0.000000] efi: UEFI not found. [ 0.000000] Reserved memory: created CMA memory pool at 0x00000000e0000000, size 512 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] Reserved memory: created DMA memory pool at 0x0000000094300000, size 1 MiB [ 0.000000] OF: reserved mem: initialized node vdev0buffer@94300000, compatible id shared-dma-pool [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000040000000-0x00000000ffffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal [mem 0x0000000100000000-0x000000023fffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000040000000-0x0000000055ffffff] [ 0.000000] node 0: [mem 0x0000000058000000-0x00000000923fffff] [ 0.000000] node 0: [mem 0x0000000092400000-0x00000000a43fffff] [ 0.000000] node 0: [mem 0x00000000a4400000-0x000000023fffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000023fffffff] [ 0.000000] On node 0, zone DMA: 8192 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 28 pages/cpu s74200 r8192 d32296 u114688 [ 0.000000] pcpu-alloc: s74200 r8192 d32296 u114688 alloc=28*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 2056192 [ 0.000000] Kernel command line: console=ttymxc1,115200 vmalloc=400M consoleblank=0 rootwait fixrtc cpu=8MP[8] board=nitrogen_smarc uboot_release=2022.04-63881-g325116286aa root=/dev/mmcblk0p2 snd.slots=,snd-soc-imx-hdmi [ 0.000000] Unknown kernel command line parameters "fixrtc vmalloc=400M cpu=8MP[8] board=nitrogen_smarc uboot_release=2022.04-63881-g325116286aa", will be passed to user space. [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) [ 0.000000] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [ 0.000000] software IO TLB: mapped [mem 0x00000000dc000000-0x00000000e0000000] (64MB) [ 0.000000] Memory: 7279232K/8355840K available (17664K kernel code, 2470K rwdata, 6004K rodata, 4224K init, 433K bss, 552320K reserved, 524288K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 160 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] GICv3: Distributor has no Range Selector support [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: 16 PPIs implemented [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000 [ 0.000000] ITS: No ITS available, not enabling LPIs [ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns [ 0.000001] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [ 0.000589] Console: colour dummy device 80x25 [ 0.000632] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [ 0.000645] pid_max: default: 32768 minimum: 301 [ 0.000728] LSM: Security Framework initializing [ 0.000753] Yama: becoming mindful. [ 0.000816] AppArmor: AppArmor initialized [ 0.000906] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.000934] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 0.002359] rcu: Hierarchical SRCU implementation. [ 0.004624] EFI services will not be available. [ 0.004934] smp: Bringing up secondary CPUs ... [ 0.005458] Detected VIPT I-cache on CPU1 [ 0.005485] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000 [ 0.005522] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.006028] Detected VIPT I-cache on CPU2 [ 0.006048] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000 [ 0.006066] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.006565] Detected VIPT I-cache on CPU3 [ 0.006585] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000 [ 0.006603] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.006670] smp: Brought up 1 node, 4 CPUs [ 0.006697] SMP: Total of 4 processors activated. [ 0.006703] CPU features: detected: 32-bit EL0 Support [ 0.006707] CPU features: detected: 32-bit EL1 Support [ 0.006717] CPU features: detected: CRC32 instructions [ 0.014192] CPU: All CPU(s) started at EL2 [ 0.014233] alternatives: patching kernel code [ 0.015945] devtmpfs: initialized [ 0.029223] Registered cp15_barrier emulation handler [ 0.029248] Registered setend emulation handler [ 0.029258] KASLR disabled due to lack of seed [ 0.029390] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.029407] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.043291] pinctrl core: initialized pinctrl subsystem [ 0.043801] DMI not present or invalid. [ 0.044376] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.045719] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations [ 0.045983] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.046323] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.046369] audit: initializing netlink subsys (disabled) [ 0.046486] audit: type=2000 audit(0.044:1): state=initialized audit_enabled=0 res=1 [ 0.046898] thermal_sys: Registered thermal governor 'step_wise' [ 0.047186] cpuidle: using governor menu [ 0.047402] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.047488] ASID allocator initialised with 65536 entries [ 0.048793] imx mu driver is registered. [ 0.048812] imx rpmsg driver is registered. [ 0.061977] imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver [ 0.081372] platform 32fd8000.hdmi: Fixing up cyclic dependency with 32fc6000.lcd-controller [ 0.098882] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.098900] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [ 0.098907] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.098914] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [ 0.100858] cryptd: max_cpu_qlen set to 1000 [ 0.104879] imx_dev_clk_hw_pll14xx: audio_pll2 en:1, sel:2, mf:30000, mr:2 [ 0.104907] imx_dev_clk_hw_pll14xx: video_pll1 en:1, sel:2, mf:30000, mr:5 [ 0.116449] ACPI: Interpreter disabled. [ 0.120011] debugfs: Directory 'vref-3v3' with parent 'regulator' already present! [ 0.120671] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 35, base_baud = 5000000) is a IMX [ 0.120787] serial serial0: tty port ttymxc0 registered [ 0.121268] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 36, base_baud = 5000000) is a IMX [ 0.121738] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 37, base_baud = 1500000) is a IMX [ 0.865923] printk: console [ttymxc1] enabled [ 0.870787] 30a60000.serial: ttymxc3 at MMIO 0x30a60000 (irq = 45, base_baud = 5000000) is a IMX [ 0.880470] iommu: Default domain type: Translated [ 0.885362] iommu: DMA domain TLB invalidation policy: strict mode [ 0.891647] max77958:max77958_i2c_init [ 0.895633] SCSI subsystem initialized [ 0.899562] libata version 3.00 loaded. [ 0.899759] usbcore: registered new interface driver usbfs [ 0.905288] usbcore: registered new interface driver hub [ 0.910634] usbcore: registered new device driver usb [ 0.916493] imx-i2c 30a20000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.923176] i2c i2c-0: IMX I2C adapter registered [ 0.928238] imx-i2c 30a30000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.935079] i2c i2c-1: IMX I2C adapter registered [ 0.940497] imx-i2c 30a40000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.947137] i2c i2c-2: IMX I2C adapter registered [ 0.952142] imx-i2c 30a50000.i2c: stop-delay=0, inter-byte-delay=0 [ 0.958508] i2c i2c-3: IMX I2C adapter registered [ 0.963379] imx-i2c 30ae0000.i2c: stop-delay=0, inter-byte-delay=0 [ 1.031272] i2c i2c-5: IMX I2C adapter registered [ 1.036754] mc: Linux media interface: v0.10 [ 1.041061] videodev: Linux video capture interface: v2.00 [ 1.046711] pps_core: LinuxPPS API ver. 1 registered [ 1.051684] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [ 1.060853] PTP clock support registered [ 1.065570] Advanced Linux Sound Architecture Driver Initialized. [ 1.072266] Bluetooth: Core ver 2.22 [ 1.075874] NET: Registered PF_BLUETOOTH protocol family [ 1.081194] Bluetooth: HCI device and connection manager initialized [ 1.087556] Bluetooth: HCI socket layer initialized [ 1.092442] Bluetooth: L2CAP socket layer initialized [ 1.097509] Bluetooth: SCO socket layer initialized [ 1.102403] NetLabel: Initializing [ 1.105803] NetLabel: domain hash size = 128 [ 1.110165] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 1.115891] NetLabel: unlabeled traffic allowed by default [ 1.122277] clocksource: Switched to clocksource arch_sys_counter [ 1.157189] VFS: Disk quotas dquot_6.6.0 [ 1.161190] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 1.168497] AppArmor: AppArmor Filesystem Enabled [ 1.173269] pnp: PnP ACPI: disabled [ 1.183027] NET: Registered PF_INET protocol family [ 1.188160] IP idents hash table entries: 131072 (order: 8, 1048576 bytes, linear) [ 1.198534] tcp_listen_portaddr_hash hash table entries: 4096 (order: 4, 65536 bytes, linear) [ 1.207142] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 1.214900] TCP established hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 1.223244] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear) [ 1.231541] TCP: Hash tables configured (established 65536 bind 65536) [ 1.238228] UDP hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 1.245170] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes, linear) [ 1.252673] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 1.258739] RPC: Registered named UNIX socket transport module. [ 1.264691] RPC: Registered udp transport module. [ 1.269404] RPC: Registered tcp transport module. [ 1.274115] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.280568] PCI: CLS 0 bytes, default 64 [ 1.285143] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available [ 1.294172] kvm [1]: IPA Size Limit: 40 bits [ 1.299841] kvm [1]: GICv3: no GICV resource entry [ 1.304645] kvm [1]: disabling GICv2 emulation [ 1.309109] kvm [1]: GIC system register CPU interface enabled [ 1.315039] kvm [1]: vgic interrupt IRQ9 [ 1.319111] kvm [1]: Hyp mode initialized successfully [ 1.327889] Initialise system trusted keyrings [ 1.332405] Key type blacklist registered [ 1.336551] workingset: timestamp_bits=46 max_order=21 bucket_order=0 [ 1.348632] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 1.355396] NFS: Registering the id_resolver key type [ 1.360500] Key type id_resolver registered [ 1.364695] Key type id_legacy registered [ 1.368773] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.375481] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 1.382894] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 1.389343] 9p: Installing v9fs 9p2000 file system support [ 1.395151] integrity: Platform Keyring initialized [ 1.436171] Key type asymmetric registered [ 1.440282] Asymmetric key parser 'x509' registered [ 1.445216] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) [ 1.452724] io scheduler mq-deadline registered [ 1.457268] io scheduler kyber registered [ 1.474178] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator [ 1.482288] imx6_pcie_probe: reset gp 117 [ 1.486364] imx6q-pcie 33800000.pcie: pcie_ext_src clk src missing or invalid [ 1.488156] imx-sdma 30bd0000.dma-controller: firmware found. [ 1.493552] imx6q-pcie 33800000.pcie: Failed to get PCIEPHY perst control [ 1.499436] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5 [ 1.515489] mxs-dma 33000000.dma-apbh: initialized [ 1.521635] SoC: i.MX8MP revision 1.1 [ 1.525331] imx-sdma 30e10000.dma-controller: firmware found. [ 1.526928] Bus freq driver module loaded [ 1.545196] nxp-pca9450 0-0025: pca9450bc probed. [ 1.553867] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 1.573451] brd: module loaded [ 1.581095] loop: module loaded [ 1.586456] imx ahci driver is registered. [ 1.591357] slram: not enough parameters. [ 1.599305] tun: Universal TUN/TAP device driver, 1.6 [ 1.604540] CAN device driver interface [ 1.610903] e1000e: Intel(R) PRO/1000 Network Driver [ 1.615880] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 1.621841] igb: Intel(R) Gigabit Ethernet Network Driver [ 1.627248] igb: Copyright (c) 2007-2014 Intel Corporation. [ 1.632858] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 1.639134] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 1.645091] sky2: driver version 1.30 [ 1.651210] platform 38100000.usb: Fixing up cyclic dependency with connector [ 1.660551] dwc3 38200000.usb: vbus regulator failed -19 [ 1.668507] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.675089] ehci-pci: EHCI PCI platform driver [ 1.679573] ehci-platform: EHCI generic platform driver [ 1.685063] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 1.691258] ohci-pci: OHCI PCI platform driver [ 1.695739] ohci-platform: OHCI generic platform driver [ 1.701923] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.707435] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 [ 1.715447] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe6d hci version 0x110 quirks 0x0000002001010010 [ 1.724889] xhci-hcd xhci-hcd.0.auto: irq 247, io mem 0x38200000 [ 1.731026] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.736526] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 [ 1.744200] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 1.751245] hub 1-0:1.0: USB hub found [ 1.755030] hub 1-0:1.0: 1 port detected [ 1.759270] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.767774] hub 2-0:1.0: USB hub found [ 1.771554] hub 2-0:1.0: 1 port detected [ 1.775822] usbcore: registered new interface driver usb-storage [ 1.781877] usbcore: registered new interface driver usb_ehset_test [ 1.790437] init [ 1.790973] input: 30370000.snvs:snvs-powerkey as /devices/platform/soc@0/30000000.bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0 [ 1.806127] i2c_dev: i2c /dev entries driver [ 1.813353] i2c i2c-1: Added multiplexed i2c bus 6 [ 1.818509] i2c 7-0060: Fixing up cyclic dependency with 38100000.usb [ 1.825010] i2c 7-0060: Fixing up cyclic dependency with connector [ 1.832816] i2c i2c-1: Added multiplexed i2c bus 7 [ 1.838163] i2c i2c-1: Added multiplexed i2c bus 8 [ 1.843153] i2c i2c-1: Added multiplexed i2c bus 9 [ 1.847971] pca954x 1-0073: registered 4 multiplexed busses for I2C switch pca9546 [ 1.857012] i2c i2c-2: Added multiplexed i2c bus 10 [ 1.862092] i2c i2c-2: Added multiplexed i2c bus 11 [ 1.867192] i2c i2c-2: Added multiplexed i2c bus 12 [ 1.872255] i2c i2c-2: Added multiplexed i2c bus 13 [ 1.877155] pca954x 2-0073: registered 4 multiplexed busses for I2C switch pca9546 [ 1.886241] i2c 14-0010: Fixing up cyclic dependency with 32e40000.csi [ 1.892998] i2c i2c-5: Added multiplexed i2c bus 14 [ 1.898171] i2c 15-0010: Fixing up cyclic dependency with 32e50000.csi [ 1.904932] i2c i2c-5: Added multiplexed i2c bus 15 [ 1.910005] i2c i2c-5: Added multiplexed i2c bus 16 [ 1.915073] i2c i2c-5: Added multiplexed i2c bus 17 [ 1.919971] pca954x 5-0070: registered 4 multiplexed busses for I2C switch pca9546 [ 1.942520] rtc-rv3028 6-0052: registered as rtc0 [ 1.949106] rtc-rv3028 6-0052: setting system clock to 2024-05-20T08:47:55 UTC (1716194875) [ 1.959740] check_alarm_past: alarm in the past [ 1.964416] snvs_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc1 [ 1.975161] sdhci: Secure Digital Host Controller Interface driver [ 1.981368] sdhci: Copyright(c) Pierre Ossman [ 1.985845] Synopsys Designware Multimedia Card Interface Driver [ 1.992091] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.999312] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO [ 2.005050] ledtrig-cpu: registered to indicate activity on CPUs [ 2.011803] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 2.018619] usb 1-1: new high-speed USB device number 2 using xhci-hcd [ 2.019481] caam 30900000.crypto: device ID = 0x0a16040100000100 (Era 9) [ 2.031882] caam 30900000.crypto: job rings = 1, qi = 0 [ 2.036255] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA [ 2.038237] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA [ 2.048221] caam algorithms registered in /proc/crypto [ 2.057474] caam 30900000.crypto: caam pkc algorithms registered in /proc/crypto [ 2.065013] caam 30900000.crypto: rng crypto API alg registered prng-caam [ 2.071831] caam 30900000.crypto: registering rng-caam [ 2.077470] random: crng init done [ 2.078653] Device caam-keygen registered [ 2.085338] caam-snvs 30370000.caam-snvs: violation handlers armed - non-secure state [ 2.093525] hid: raw HID events driver (C) Jiri Kosina [ 2.099158] usbcore: registered new interface driver usbhid [ 2.104758] usbhid: USB HID core driver [ 2.109464] mxc-mipi-csi2-sam 32e40000.csi: supply mipi-phy not found, using dummy regulator [ 2.118351] : mipi_csis_imx8mp_phy_reset, No remote pad found! [ 2.119708] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA [ 2.124291] mipi_csis_subdev_init: mxc-mipi-csi2.0 [ 2.136123] mxc-mipi-csi2-sam 32e40000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 500000000 [ 2.146013] mipi_csis_probe: success ffff0000c0a7b810 [ 2.151457] mxc-mipi-csi2-sam 32e50000.csi: supply mipi-phy not found, using dummy regulator [ 2.160373] : mipi_csis_imx8mp_phy_reset, No remote pad found! [ 2.166295] mipi_csis_subdev_init: mxc-mipi-csi2.1 [ 2.171108] mxc-mipi-csi2-sam 32e50000.csi: lanes: 2, hs_settle: 13, clk_settle: 2, wclk: 1, freq: 266000000 [ 2.180980] mipi_csis_probe: success ffff0000c0a7cc10 [ 2.187595] deferring isp device registration [ 2.193071] mmc0: new HS400 Enhanced strobe MMC card at address 0001 [ 2.195408] optee: probing for conduit method. [ 2.200619] mmcblk0: mmc0:0001 TB2916 14.6 GiB [ 2.203939] optee: revision 3.17 (98499642) [ 2.209969] mmcblk0: p1 p2 [ 2.209982] optee: dynamic shared memory is enabled [ 2.215361] mmcblk0boot0: mmc0:0001 TB2916 4.00 MiB [ 2.217327] optee: initialized driver [ 2.223491] mmcblk0boot1: mmc0:0001 TB2916 4.00 MiB [ 2.228816] hantrodec 0 : module inserted. Major = 238 [ 2.232674] mmcblk0rpmb: mmc0:0001 TB2916 4.00 MiB, chardev (240:0) [ 2.235771] hub 1-1:1.0: USB hub found [ 2.236065] hantrodec 1 : module inserted. Major = 238 [ 2.237333] hantroenc: HW at base <0000000038320000> with ID <0x80006200> [ 2.237457] hx280enc: module inserted. Major <237> [ 2.245177] wm8962 8-001a: customer id 0 revision F [ 2.250771] hub 1-1:1.0: 4 ports detected [ 2.292637] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517) [ 2.299556] NET: Registered PF_LLC protocol family [ 2.304833] NET: Registered PF_INET6 protocol family [ 2.311900] Segment Routing with IPv6 [ 2.315605] In-situ OAM (IOAM) with IPv6 [ 2.319584] NET: Registered PF_PACKET protocol family [ 2.324655] can: controller area network core [ 2.329069] NET: Registered PF_CAN protocol family [ 2.333899] can: raw protocol [ 2.336934] can: broadcast manager protocol [ 2.341162] can: netlink gateway - max_hops=1 [ 2.341451] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd [ 2.346290] Bluetooth: RFCOMM TTY layer initialized [ 2.357004] Bluetooth: RFCOMM socket layer initialized [ 2.362191] Bluetooth: RFCOMM ver 1.11 [ 2.365972] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.371308] Bluetooth: BNEP filters: protocol multicast [ 2.376570] Bluetooth: BNEP socket layer initialized [ 2.381562] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.387557] Bluetooth: HIDP socket layer initialized [ 2.393067] 9pnet: Installing 9P2000 support [ 2.397408] Key type dns_resolver registered [ 2.402453] Loading compiled-in X.509 certificates [ 2.411045] Key type encrypted registered [ 2.415101] AppArmor: AppArmor sha1 policy hashing enabled [ 2.438983] hub 2-1:1.0: USB hub found [ 2.442834] hub 2-1:1.0: 4 ports detected [ 2.445759] imx6q-pcie 33800000.pcie: supply epdev_on not found, using dummy regulator [ 2.446377] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung_dw_hdmi_phy2) [ 2.447342] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.454965] imx6_pcie_probe: reset gp 117 [ 2.465832] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops 0xffff80000926d968) [ 2.471790] imx6q-pcie 33800000.pcie: pcie_ext_src clk src missing or invalid [ 2.475871] imx-drm display-subsystem: bound 32fd8000.hdmi (ops 0xffff80000925ad78) [ 2.484019] imx6q-pcie 33800000.pcie: EXT REF_CLK is used!. [ 2.491298] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 0 [ 2.499236] imx6q-pcie 33800000.pcie: PCIe PHY PLL clock is locked. [ 2.522909] mmc2: new ultra high speed SDR104 SDIO card at address 0001 [ 2.564136] pcie phy pipe clk is not ready [ 2.568247] phy phy-32f00000.pcie-phy.4: phy init failed --> -110 [ 2.568255] imx6q-pcie 33800000.pcie: Waiting for PHY PLL ready timeout! [ 2.588773] imx6q-pcie 33800000.pcie: PCIe PLL lock timeout [ 2.602304] Console: switching to colour frame buffer device 100x37 [ 2.629670] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.631690] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [ 2.637264] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound [ 2.664168] imx6q-pcie 33800000.pcie: host bridge /soc@0/pcie@33800000 ranges: [ 2.668723] pps pps0: new PPS source ptp0 [ 2.671429] imx6q-pcie 33800000.pcie: No bus range found for /soc@0/pcie@33800000, using [bus 00-ff] [ 2.684784] imx6q-pcie 33800000.pcie: IO 0x001ff80000..0x001ff8ffff -> 0x0000000000 [ 2.692998] imx6q-pcie 33800000.pcie: MEM 0x0018000000..0x001fefffff -> 0x0018000000 [ 2.701303] imx6q-pcie 33800000.pcie: iATU unroll: enabled [ 2.706815] imx6q-pcie 33800000.pcie: Detected iATU regions: 4 outbound, 4 inbound [ 2.710697] fec 30be0000.ethernet eth0: registered PHC device 0 [ 2.721079] imx-dwmac 30bf0000.ethernet: IRQ eth_lpi not found [ 2.727493] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51 [ 2.734311] imx-dwmac 30bf0000.ethernet: DWMAC4/5 [ 2.739111] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported [ 2.746255] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported [ 2.753395] imx-dwmac 30bf0000.ethernet: TX Checksum insertion supported [ 2.760102] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported [ 2.766246] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 2.773919] imx-dwmac 30bf0000.ethernet: Enabled L3L4 Flow TC (entries=8) [ 2.780714] imx-dwmac 30bf0000.ethernet: Enabled RFS Flow TC (entries=8) [ 2.787431] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max_off=256) [ 2.795007] imx-dwmac 30bf0000.ethernet: Using 34 bits DMA width [ 2.813131] hd3ss3220 7-0060: probed revision=0x0 [ 2.818382] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 5 mkt segment 0 supported-hw 0x20 0x1 [ 2.828737] deferring isp device registration [ 2.834193] input: WM8962 Beep Generator as /devices/platform/soc@0/30800000.bus/30a30000.i2c/i2c-1/i2c-8/8-001a/input/input1 [ 2.890014] input: audio-hdmi HDMI Jack as /devices/platform/sound-hdmi/sound/card1/input2 [ 2.899789] deferring isp device registration [ 2.904985] deferring isp device registration [ 2.919052] input: gpio-keys-batt as /devices/platform/gpio-keys-batt/input/input3 [ 2.929838] input: gpio-keys as /devices/platform/gpio-keys/input/input4 [ 2.929876] deferring isp device registration [ 2.941477] deferring isp device registration [ 2.967396] input: gpio-keys-can as /devices/platform/gpio-keys-can/input/input5 [ 2.977245] deferring isp device registration [ 2.998910] ALSA device list: [ 3.001897] #0: wm8962-audio [ 3.004975] #1: audio-hdmi [ 3.714073] imx6q-pcie 33800000.pcie: Phy link never came up [ 3.719833] imx6q-pcie: probe of 33800000.pcie failed with error -110 [ 3.749845] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none. [ 3.759665] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 3.766798] devtmpfs: mounted [ 3.770547] Freeing unused kernel memory: 4224K [ 3.782625] Run /sbin/init as init process [ 3.786736] with arguments: [ 3.786740] /sbin/init [ 3.786743] fixrtc [ 3.786746] with environment: [ 3.786748] HOME=/ [ 3.786751] TERM=linux [ 3.786754] vmalloc=400M [ 3.786756] cpu=8MP[8] [ 3.786759] board=nitrogen_smarc [ 3.786761] uboot_release=2022.04-63881-g325116286aa [ 3.925864] systemd[1]: systemd 250.5+ running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA -SMACK +SECCOMP -GCRYPT -GNUTLS -OPENSSL +ACL +BLKID -CURL -ELFUTILS -FIDO2 -IDN2 -IDN +IPTC +KMOD -LIBCRYPTSETUP +LIBFDISK -PCRE2 -PWQUALITY -P11KIT -QRENCODE -BZIP2 -LZ4 -XZ -ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=hybrid) [ 3.957720] systemd[1]: Detected architecture arm64. [ 4.041150] systemd[1]: Hostname set to . [ 4.050406] systemd[1]: Initializing machine ID from random generator. [ 4.057418] systemd[1]: Installed transient /etc/machine-id file. [ 4.307371] systemd[1]: Queued start job for default target Multi-User System. [ 4.346939] systemd[1]: Created slice Slice /system/getty. [ 4.360661] systemd[1]: Created slice Slice /system/modprobe. [ 4.384346] systemd[1]: Created slice Slice /system/serial-getty. [ 4.408230] systemd[1]: Created slice User and Session Slice. [ 4.430768] systemd[1]: Started Dispatch Password Requests to Console Directory Watch. [ 4.454689] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 4.478685] systemd[1]: Reached target Host and Network Name Lookups. [ 4.502774] systemd[1]: Reached target Path Units. [ 4.522396] systemd[1]: Reached target Remote File Systems. [ 4.547046] systemd[1]: Reached target Slice Units. [ 4.566725] systemd[1]: Reached target Swaps. [ 4.603618] systemd[1]: Listening on Process Core Dump Socket. [ 4.626697] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 4.651229] systemd[1]: Listening on Journal Audit Socket. [ 4.675016] systemd[1]: Listening on Journal Socket (/dev/log). [ 4.699008] systemd[1]: Listening on Journal Socket. [ 4.723237] systemd[1]: Listening on Network Service Netlink Socket. [ 4.763771] systemd[1]: Listening on udev Control Socket. [ 4.787260] systemd[1]: Listening on udev Kernel Socket. [ 4.811311] systemd[1]: Listening on User Database Manager Socket. [ 4.838633] systemd[1]: Mounting Huge Pages File System... [ 4.862215] systemd[1]: Mounting POSIX Message Queue File System... [ 4.885706] systemd[1]: Mounting Kernel Debug File System... [ 4.910376] systemd[1]: Mounting Kernel Trace File System... [ 4.949532] systemd[1]: Mounting Temporary Directory /tmp... [ 4.969956] systemd[1]: Starting Create List of Static Device Nodes... [ 4.998679] systemd[1]: Starting Load Kernel Module configfs... [ 5.022049] systemd[1]: Starting Load Kernel Module drm... [ 5.046628] systemd[1]: Starting Load Kernel Module fuse... [ 5.060733] fuse: init (API version 7.34) [ 5.069228] systemd[1]: Starting SELinux autorelabel service loading... [ 5.093365] systemd[1]: Starting SELinux init for /dev service loading... [ 5.117985] systemd[1]: Starting File System Check on Root Device... [ 5.138975] systemd[1]: systemd-journald.service: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. [ 5.151925] systemd[1]: (This warning is only shown for the first unit using IP firewalling.) [ 5.164135] systemd[1]: Starting Journal Service... [ 5.173957] systemd[1]: Starting Load Kernel Modules... [ 5.182570] systemd[1]: Starting Generate network units from Kernel command line... [ 5.195804] galcore: loading out-of-tree module taints kernel. [ 5.208525] deferring isp device registration [ 5.209918] Galcore version 6.4.3.p4.398061 [ 5.233254] systemd[1]: Starting Coldplug All udev Devices... [ 5.260955] systemd[1]: Mounted Huge Pages File System. [ 5.273059] systemd[1]: Mounted POSIX Message Queue File System. [ 5.289459] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 1 [ 5.298186] deferring isp device registration [ 5.306947] systemd[1]: Started Journal Service. [ 5.327047] audit: type=1130 audit(1716194878.876:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.410803] audit: type=1130 audit(1716194878.960:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=kmod-static-nodes comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.447294] audit: type=1130 audit(1716194878.996:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.467589] audit: type=1131 audit(1716194878.996:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@configfs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.506790] audit: type=1130 audit(1716194879.056:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.526651] audit: type=1131 audit(1716194879.056:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@drm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.563394] audit: type=1130 audit(1716194879.112:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.583344] audit: type=1131 audit(1716194879.112:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=modprobe@fuse comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.622812] audit: type=1130 audit(1716194879.172:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-autorelabel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.643364] audit: type=1131 audit(1716194879.172:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-autorelabel comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.683411] audit: type=1130 audit(1716194879.232:12): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-labeldev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.703717] audit: type=1131 audit(1716194879.232:13): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=selinux-labeldev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 5.852994] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null). Quota mode: none. [ 5.961069] systemd-journald[283]: Received client request to flush runtime journal. [ 6.722763] Bluetooth: HCI UART driver ver 2.3 [ 6.736344] Bluetooth: HCI UART protocol H4 registered [ 6.738933] deferring isp device registration [ 6.744181] Bluetooth: HCI UART protocol BCSP registered [ 6.759654] Bluetooth: HCI UART protocol ATH3K registered [ 6.772226] hci_uart_bcm serial0-0: supply vbat not found, using dummy regulator [ 6.781824] hci_uart_bcm serial0-0: supply vddio not found, using dummy regulator [ 6.795486] Bluetooth: HCI UART protocol Broadcom registered [ 6.855725] imx219 14-0010: supply VANA not found, using dummy regulator [ 6.864576] Bluetooth: HCI UART protocol QCA registered [ 7.025046] imx219 14-0010: supply VDIG not found, using dummy regulator [ 7.032328] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 7.073636] imx219 14-0010: supply VDDL not found, using dummy regulator [ 7.082134] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 7.083381] deferring isp device registration [ 7.091599] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 7.104535] cfg80211: failed to load regulatory.db [ 7.186202] imx219 14-0010: failed to read chip id 219 [ 7.212100] Bluetooth: hci0: BCM: chip id 135 [ 7.217062] Bluetooth: hci0: BCM: features 0x0f [ 7.223020] Bluetooth: hci0: BCM4373A0 [ 7.227012] Bluetooth: hci0: BCM4373A0 (001.001.025) build 0000 [ 7.233073] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 7.239745] Bluetooth: hci0: BCM: 'brcm/BCM4373A0.hcd' [ 7.244989] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' [ 7.273105] imx219: probe of 14-0010 failed with error -5 [ 7.280748] deferring isp device registration [ 7.284090] brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac4373-sdio for chip BCM4373/0 [ 7.290602] imx219 15-0010: supply VANA not found, using dummy regulator [ 7.293925] brcmfmac mmc2:0001:1: Direct firmware load for cypress/cyfmac4373-sdio.boundary,imx8mp-nitrogen-smarc.bin failed with error -2 [ 7.316486] deferring isp device registration [ 7.317794] brcmfmac mmc2:0001:1: Direct firmware load for cypress/cyfmac4373-sdio.bin failed with error -2 [ 7.350563] imx219 15-0010: supply VDIG not found, using dummy regulator [ 7.358179] imx219 15-0010: supply VDDL not found, using dummy regulator [ 7.378851] imx219 15-0010: failed to read chip id 219 [ 7.384971] imx219: probe of 15-0010 failed with error -5 [ 8.338351] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 8.443600] IPv6: ADDRCONF(NETDEV_CHANGE): can1: link becomes ready [ 8.450954] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 8.682664] Micrel KSZ9031 Gigabit PHY 30be0000.ethernet-1:07: attached PHY driver (mii_bus:phy_addr=30be0000.ethernet-1:07, irq=93) [ 8.789444] imx-dwmac 30bf0000.ethernet eth1: PHY [stmmac-0:07] driver [Micrel KSZ9031 Gigabit PHY] (irq=89) [ 8.808085] imx-dwmac 30bf0000.ethernet eth1: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 8.822348] imx-dwmac 30bf0000.ethernet eth1: No Safety Features support found [ 8.829658] imx-dwmac 30bf0000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported [ 8.843207] imx-dwmac 30bf0000.ethernet eth1: registered PTP clock [ 8.862347] imx-dwmac 30bf0000.ethernet eth1: FPE workqueue start [ 8.868515] imx-dwmac 30bf0000.ethernet eth1: configuring for phy/rgmii-id link mode [ 13.200889] fec 30be0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 13.208941] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 13.230843] 8021q: 802.1Q VLAN Support v1.8 [ 13.236988] 8021q: adding VLAN 0 to HW filter on device eth1 [ 34.126325] vref-1v8: disabling [ 293.030168] wlan: Loading MWLAN driver [ 293.034357] wlan: Register to Bus Driver... [ 293.038657] wlan: Register to Bus Driver Done [ 293.043044] wlan: Driver loaded successfully Thanks. Simão Re: Nitrogen8M fails to detect Wi-Fi module Hi, @SimaoLeite  Can you please let  me know your kernel version? Are you using Linux kernel 6.6.3? And also, please share me your full dmesg logs so that I can check what happened on your side. Thanks. Christine.

s32k312 spi2 clock wire ouput extra pulse at begining. Hi Nxp,     i am using s32k312 spi2 to send  data. and found spi2 clk line always output extra one pulse  as  pic below(blue waveform is clock line),  how's that happen. it not happened in spi1. attached is a sample project. 回复： s32k312 spi2 clock wire ouput extra pulse at begining. 1. sck pull-up resistor cause this problem. 2. spi-sd need send data with CS high, so manually control cs instead of lpspi2_pcs0. 回复： s32k312 spi2 clock wire ouput extra pulse at begining. I tested your attached project and did not see the waveform mentioned in your screenshot(I don't see any SPI data at all). Please re-upload the test project. In addition, why do you use PTE11 as GPIO(PCS) instead of configuring PTE11 as lpspi2_pcs0? Also, why call IP_LPSPI_2->TCR |= speed << 27; instead of using the S32 Configuration Tool to configure SpiBaudrate? It is recommended to refer to the Lpspi_Flexio_Ip_Transfer_S32K344, Lpspi_Ip_HalfDuplexTransfer_S32K344 projects in S32K3 RTD 4.0.0 or Example S32K312 SPI Transmit & Receive Using DMA DS3.5 RTD300 回复： s32k312 spi2 clock wire ouput extra pulse at begining. attached files Re: s32k312 spi2 clock wire ouput extra pulse at begining. Hello, The extra clock pulse on the SPI2 clock line is definitely interesting, especially since it doesn’t happen on SPI1. This could be caused by a configuration mismatch in SPI2 settings, such as clock polarity, phase, or transfer mode. It’s also worth checking if SPI2 handles idle states differently or if there’s a subtle difference in how the driver or SDK is managing it. Hardware issues like signal integrity could also play a role, though it’s less likely.

S32K3 MCAL CANFDマスク設定のバグ 皆さん、こんにちは EDFビット、標準CANFDはビット14である必要がありますが、現在は30です。バグですか?そして、それはまだRTD5.0.0に存在します。 MCALコードでは、CANFDフレームを送信する場合、着信パラメータのCANFDメッセージIDのFDFバイトを1にする必要があります。つまり、CANFD標準フレームのBit14は1です。バグがあります。CANFD フレーム形式に従ってCAN_43_FLEXCAN_FD_FRAME_U32ビット 14 をマスクする必要があります。現在はビット 30 に設定されています。 BRs、 仙龍 Re:S32K3 MCAL CANFDマスク設定のバグ Hi@武仙龍 こちらの記事を参考にしてください。 https://community.nxp.com/t5/S32K/Use-S32K358-flexcan-to-sent-extended-ID/td-p/1993198https://nxp.lightning.force.com/lightning/r/Case/500KA0000039pXzYAI/view Re:S32K3 MCAL CANFDマスク設定のバグ こんにちは すみません、よく見てしまいました。これはバグではなく、ソフトウェア設計です。CANFD_ID伝送パラメータでは、ユーザーは最大2ビットの32Uを埋める必要があります。 /** * @{ ※@brief Can_IdType * @detailsはL-PDUの識別子を表します。最上位 2 ビットは、フレーム タイプを指定します。 * -00 標準 CAN ID の CAN メッセージ * -01 標準CAN ID付きCAN FDフレーム * -10 CANメッセージ(拡張CAN ID付き) * -11 CAN FDフレーム(拡張CAN ID付き) ※@implements Can_IdType_type */ /* Can_CreatePduInfo(id |CAN Can_IdType_type、swPduハンドル、長さ、sdu) */ Can_PduInfo = Can_CreatePduInfo(0U |CAN_43_FLEXCAN_FD_FRAME_U32、0U、16U、Can_au8Sdu8bytes);

RW612 zigbee サポート こんにちは RW612システムにZigBeeサポートを追加する予定はありますか?コーディネーターの役割です。最大64ノードまでの小さなネットワークでこのタスクを行うには十分強力だと思います 日時:RW612 zigbeeサポート それを見つけました。 感謝 日時:RW612 zigbeeサポート 申し訳ありませんが、このファイルとフォルダが見つかりません。 このファイルをRW612用にダウンロードする方法を教えてください。 日時:RW612 zigbeeサポート ありがとうございます！ 確認してみます