无法在 S32 Design Studio Ver 2018.R1 中安装 IAR 插件 我在 Casco Auto 工作，使用适用于 Win64 的 S32 DS IDE 版本 2018.R1。 每当我尝试安装 IAR 插件时，都会显示错误“无法读取存储库” 我按照IAR Embedded Workbench for Eclipse中指定的说明进行操作 回复：无法在 S32 Design Studio Ver 2018.R1 中安装 IAR 插件 最终能够使用ARM v2.2 安装 IAR 插件。不确定为什么 2018.R1 无法实现，是否存在兼容性问题？不过，我对ARM v2.2 版本还满意。 感谢您的帮助，非常感谢！！ 回复：无法在 S32 Design Studio Ver 2018.R1 中安装 IAR 插件 感谢您的反馈。 我尝试手动安装，但最终出现错误“无法执行操作”。由于我使用的是 IAR-EW 8.22.1，因此我使用了 IAR-8.22 的 update-site 选项 回复：无法在 S32 Design Studio Ver 2018.R1 中安装 IAR 插件 附加错误

S12ZVLA128用の統合ブートローダー NXPコミュニティの皆さん、こんにちは。 私は現在、S12ZVLA128マイクロコントローラーを含むプロジェクトに取り組んでいますが、Unified Bootloader、特にフラッシュローダーの部分についての詳細を探しています。 私の理解では、ブートローダーはUDS(Unified Diagnostic Services)を介してフラッシュローダーを受け取ります。ただし、UDS経由で受信するのではなく、フラッシュメモリに直接ロードされるフラッシュローダーを使用できるようにする構成またはオプションがあるかどうかを知りたいです。 このシナリオでブートローダーを設定する方法について、ガイダンスやドキュメントを提供していただけますか?構成例や参照があれば幸いです。 ご協力いただきありがとうございます!

unable to install IAR plugins in S32 Design Studio Ver 2018.R1 I work in Casco Auto, using S32 DS IDE version 2018.R1 for win 64. Whenever I am trying to install IAR plugins, its showing error "unable to read repository" Im following instructions specified in IAR Embedded Workbench for Eclipse Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Finally able to install IAR plugin with ARM v2.2. Not sure why its not possible with 2018.R1, will be there any compatibility issues? However, I'm ok with ver  ARM v2.2. Appreciate your help, thanks a lot!! Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Hi@AdarshRajendran This is strange, because I tried to install several versions and I didn't encounter any problems. According to your error message, it keeps showing that some dependent packages cannot be installed. This is could be likely related to your network. My suggestion: 1. Reinstall S32 Design Studio for ARM 2018 2. Try some new networks and then try to install the IAR plug-in agian If it still doesn't work, you can try to install S32 Design Studio for ARM v2.2, and then try to install the IAR plug-in Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 @Senlent  I tried to install EMF 2.13 as you suggested, still I have same trouble. Its showing operation can't be completed due to some missing requirement. details are given below snapshot. Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Hi@AdarshRajendran Please try to install EMF 2.13 than try again, seem it also useful on myside. https://community.nxp.com/t5/S32-Design-Studio/problem-while-install-IAR-plugin-into-S32DS-ARM/td-p/1191185 Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Attaching the error message: Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Thank you for your feedback. I tried manual installation, however ended up with error "cannot perform operation". I used update-site option for IAR-8.22 since I'm using the IAR-EW 8.22.1 Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Hi@AdarshRajendran In the link you provided, you can see such description. Manual installation using the "Install New Software..." dialog The plugins can also be installed directly using the Install New Software... dialog, without using the plugin manager. To do this, you need to first lookup the update site to use which is compatible with your version of IAR Embedded Workbench version. When you have the correct update site, proceed with the normal Eclipse plugin installation procedure. Please refer to Eclipse documentation for additional information. Re: unable to install IAR plugins in S32 Design Studio Ver 2018.R1 Attaching the error 

S32 Design Studio Ver 2018.R1にIARプラグインをインストールできません 私はCasco Autoで、S32 DS IDEバージョン2018.R1をWin64に使用しています。 IARプラグインをインストールしようとすると、「リポジトリを読み取れません」というエラーが表示されます IAR Embedded Workbench for Eclipseで指定されている指示に従っています。 Re:S32 Design Studio Ver 2018.R1にIARプラグインをインストールできません ついにARM v2.2でIARプラグインをインストールできるようになりました。2018.R1で不可能な理由がわかりませんが、互換性の問題はありますか?しかし、私はver ARM v2.2で大丈夫です。 あなたの助けに感謝します、どうもありがとう!! Re:S32 Design Studio Ver 2018.R1にIARプラグインをインストールできません ご意見ありがとうございました。 手動インストールを試みましたが、「操作を実行できません」というエラーが表示されました。IAR-EW 8.22.1を使用しているため、IAR-8.22のupdate-siteオプションを使用しました Re:S32 Design Studio Ver 2018.R1にIARプラグインをインストールできません エラーの添付

RT1051 FreeRTOS plus TCP Is there any reason that the FreeRTOS plus TCP SDK component is not available for RT1051 devices? The manifest file has a dependency on RT1052, making it a nuisance to use the SDK version in projects. SDK version 2.16 Re: RT1051 FreeRTOS plus TCP Hi @otsl  Thank you for your reply and patience.  I manage to reproduce the issue, I already reported this to the SDK team. I do not have specific dates about when will the fix will be made. However the change is minimum, so I expect this to be ready on a minor release, or at least next major release. I appreciate your efforts reporting this. Diego Re: RT1051 FreeRTOS plus TCP It was downloaded from the web and added to MCUXpresso IDE. I also have the 1052 SDK and EVKB-IMXRT1050 SDK installed. All are very near the same. However, when I start a new project in MCUXPresso using the RT1051 I have the problem. Selecting the 1051 processor only gives me the option for the 1051 SDK (not the EVK SDK): If I select the 1052 processor, I have the ability to choose the EVK to use (and everything works fine using the 1052): Re: RT1051 FreeRTOS plus TCP Hi @otsl  I agree with you, thank you for your report! I already escalated this issue internally.  Edit: @otsl  Are you using a plug-in  SDK downloaded from the IDE or from  https://mcuxpresso.nxp.com/en ?  I noticed that I can import the middleware on my side, see below details.  \ Imported midleware files using Manage SDK components look like this. I downloaded the SDK from https://mcuxpresso.nxp.com/en  I acknowledge that your report is correct and you need to be able to import this middleware as I did.  Therefore, I want to check with you any troubles with the SDK generation. All the best,  Diego Re: RT1051 FreeRTOS plus TCP The software is included in the SDK, but the MCUXpresso "new project tool" (and any subsequent attempt to "Manage SDK Components" from the GUI) do not show FreeRTOS+TCP as an import option: (MCUXpresso v11.10.0, and NXP Config Tools Framework 16.0.0.202407020751) I don't know exactly how the tools "decide" to show options, but it's very likely because of the content of the manifest file: All SDK components that are selectable in the GUI have an entry for the 1051, but freertos-plus-tcp does not. This oversight means I can't easily use the tools to manage SDK components. I can manually add the component from the zip of the SDK, but then in the future if I'm updating SDK components (to new versions for example), I have to remember to manually update the FreeRTOS+TCP. As previously mentioned, It's a nuisance, and there doesn't seem to be any reason for it to be this way (other than possibly an oversight). Re: RT1051 FreeRTOS plus TCP  Hi @otsl  Thank you for reaching out!  The midleware is only available for RT1051 with sillicon revision B SDK. Below a referecen picture.  I would like to dig further on your issue, it seems that you are getting troubles with the manifest, could you detail how it limitates you, as well your procedure to  import the midleware files? Thank you! Diego

S12ZVLA128 的统一引导加载程序 大家好，恩智浦社区， 我目前正在从事一个涉及 S12ZVLA128 微控制器的项目，我正在寻找有关统一引导加载程序的更多详细信息，特别是有关闪存加载程序部分。 据我了解，引导加载程序通过 UDS（统一诊断服务）接收闪存加载程序。但是，我想知道是否有任何配置或选项允许我使用直接加载到闪存中的闪存加载程序，而不是通过 UDS 接收它。 您能否提供一些有关如何针对此场景配置引导加载程序的指导或文档？任何示例配置或参考都将不胜感激。 谢谢您的帮助！

Unified Bootloader for S12ZVLA128 Hello NXP Community, I am currently working on a project involving the S12ZVLA128 microcontroller, and I am looking for more details about the Unified Bootloader, specifically regarding the flash loader part. From my understanding, the bootloader receives the flash loader through UDS (Unified Diagnostic Services). However, I would like to know if there are any configurations or options that would allow me to use a flash loader that is directly loaded into the flash memory, rather than receiving it via UDS. Could you please provide some guidance or documentation on how to configure the bootloader for this scenario? Any example configurations or references would be greatly appreciated. Thank you for your assistance! Re: Unified Bootloader for S12ZVLA128 Hello @MassimilianoPegaso, I’m sorry to say that Unified bootloader shared on the community is a demo only provided AS IS with no guarantees and no support. Currently we do not have resources to support this demo. We apologize for the inconvenience. https://community.nxp.com/t5/S32K-Knowledge-Base/Unified-bootloader-Demo/ta-p/1423099 BR, Daniel

imx8 bitbake 可扩展 SDK 错误 大家好 我需要可扩展的 SDK。 我可以通过命令构建 SDK bitbake imx图像full-c populate_sdk， 但无法通过命令构建可扩展的 SDK bitbake imx 图像完整-c populate_sdk_ext。 我尝试了 cleanall imx-image-full 和 changong python 版本 2 和 3。 但都不起作用？ 有人可以给我建议吗？谢谢。 错误信息如下： 加载缓存：100% |############################################# ##| Time: 0:00:00 Loaded 4640 entries from dependency cache. Parsing recipes: 100% |## ########################################| 时间：0:00:00 3218 .bb 的解析文件已完成（3217 个已缓存，1 个已解析）。4641 个目标，464 个被跳过，1 个被屏蔽，0 个错误。 注意：解决任何缺失的任务队列依赖关系 构建配置： BB_VERSION = "1.44.0" BUILD_SYS =“x86_64-linux” NATIVELSBSTRING =“ubuntu-20.04” TARGET_SYS =“aarch64-poky-linux” 机器 = “imx8mqevk” 发行版 = “fsl-imx-wayland” 发行版本 = "5.4-zeus" TUNE_FEATURES = “aarch64 cortexa53 crc 加密” 目标FPU = "" 元 元狭小 =“头：d88d62c20d7d8da85f02edb170dae0280624ad7e” 元 元多媒体 meta-python =“HEAD：2b5dd1eb81cd08bc065bc76125f2856e9383e98b” 元飞思卡尔=“HEAD：14f1a630a47375432f93c556927b879b51d84c4e” meta-freescale-3rdparty =“HEAD:dbcc686f52c3c84db8cb86aa8973a4e373651b98” meta-freescale-distro =“HEAD:ca27d12e4964d1336e662bcc60184bbff526c857” 元bsp 元 SDK meta-ml =“HEAD：7f0abf664d65ab9f03f85a1d16ab54e0d1134a9b” meta-nxp-demo-experience =“HEAD:03904c493469907a2829cf29df7ab060f9c664a6” 元浏览器 =“HEAD：ee3be3b5986a4aa0e73df2204a625ae1fe5df37e” meta-rust =“HEAD：53bfa324891966a2daf5d36dc13d4a43725aebed” meta-clang =“HEAD：711e593d5984aad3bf35c51b7ac4482982bc16c7” 元侏儒 元网络 元文件系统 = “HEAD:2b5dd1eb81cd08bc065bc76125f2856e9383e98b” meta-qt5 =“HEAD：21ce4c124d9a972d9122f87c64ac2773bf04c284” meta-python2 =“HEAD：4400f9155ec193d028208cf0c66aeed2ba2b00ab” 警告：/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb:do_compile 因强制运行而受到污染 警告：/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb:do_deploy 因强制运行而受到污染 警告：/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2020.04.bb:do_compile 因强制运行而受到污染 警告：/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2020.04.bb:do_deploy 因强制运行而受到污染 初始化任务：100% |##########################################| 时间：0:00:02 状态摘要：求购 0 找到 0 错过 0 当前 4036（0% 匹配，100% 完成） 注意：执行任务 注：场景任务已完成 错误：imx-image-full-1.0-r0do_sdk_depends: 在 exec_python_func() 自动生成中执行 python 函数时出错： 导致此异常/失败的 python 调用的堆栈跟踪是： 文件：'exec_python_func() 自动生成'，行号：2，功能： 0001： *** 0002：扩展配方_系统根目录（d） 0003： 文件：'/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/poky/meta/classes/staging.bbclass'，lineno：551，功能：extend_recipe_sysroot 0547：目标=新清单[l] 0548：如果 l.endswith(“/”)： 0549：staging_copydir（l，targetdir，dest，seedirs） 0550：继续 *** 0551：staging_copyfile（l，targetdir，dest，postinsts，seedirs） 0552： 0553: bb.note("已安装到 sysroot：%s" % str(msg_adding)) 0554: bb.note("跳过，因为 sysroot 中已经存在：%s" % str(msg_exists)) 0555： 文件：'/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/poky/meta/classes/staging.bbclass'，lineno：144，功能：staging_copyfile 0140: 如果 os.path.islink(c): 0141: linkto = os.readlink(c) 0142：如果 os.path.lexists（dest）： 0143：如果不是 os.path.islink（dest）： *** 0144: 引发 OSError(errno.EEXIST, "链接 %s 已作为文件存在" % dest, dest) 0145：如果 os.readlink（dest）==linkto： 0146：返回目的地 0147: raise OSError(errno.EEXIST, "链接 %s 已经存在于不同的位置？（％s 与 ％s）” % (dest, os.readlink(dest), linkto), dest) 0148：os.symlink（链接到，目标） 异常：FileExistsError：[Errno 17] 链接 /home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/recipe-sysroot/lib 已作为文件存在：'/home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/recipe-sysroot/lib' 错误：故障日志文件存储在：/home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/temp/log.do_sdk_depends.835827 错误：任务（/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/imx-image-full.bb:do_sdk_depends）失败，退出代码为“1” 注意：任务摘要：尝试了 10496 个任务，其中 10495 个不需要重新运行，1 个失败。 摘要：1 个任务失败： /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/imx-image-full.bb:do_sdk_depends 摘要：显示了 5 条警告消息。 摘要：显示 1 条错误消息，返回非零退出代码。

imx8 bitbake extensible SDK エラー こんにちは、皆さん 拡張可能なSDKが必要です。 コマンドでSDKをビルドできる bitbake imx-image-full -c populate_sdk、 ただし、拡張可能なSDK をコマンドでビルドすることはできません bitbake imx-image-full -c populate_sdk_ext. 私はcleanall imx-image-fullとchangong pythonバージョン2と3を試しました。 しかし、どちらもうまくいきませんか? どなたかアドバイスをいただけますか?ありがとうございます。 エラーメッセージは次のとおりです。 OADキャッシュ:100% |############################################| Time: 0:00:00 Loaded 4640 entries from dependency cache. Parsing recipes: 100% |##########################################|時間: 0:00:00 3218 .bbの解析ファイルが完了しました (3217 キャッシュ、1 解析)。4641 ターゲット、464 スキップ、1 マスク、0 エラー。 注: 欠落しているタスクキューの依存関係の解決 ビルド構成: BB_VERSION = "1.44.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "ubuntu-20.04" TARGET_SYS = "aarch64-poky-linux" マシン = "imx8mqevk" DISTRO = "fsl-imx-wayland" DISTRO_VERSION = "5.4-ゼウス" TUNE_FEATURES = "aarch64 cortexa53 crc crypto" TARGET_FPU = "" メタ meta-poky = "ヘッド:d88d62c20d7d8da85f02edb170dae0280624ad7e" メタOE メタマルチメディア メタpython = "HEAD:2b5dd1eb81cd08bc065bc76125f2856e9383e98b" meta-freescale = "ヘッド:14f1a630a47375432f93c556927b879b51d84c4e" meta-freescale-3rdparty = "HEAD:dbcc686f52c3c84db8cb86aa8973a4e373651b98" meta-freescale-distro = "HEAD:ca27d12e4964d1336e662bcc60184bbff526c857" メタBSP メタSDK meta-ml = "ヘッド:7f0abf664d65ab9f03f85a1d16ab54e0d1134a9b" meta-nxp-demo-experience = "HEAD:03904c493469907a2829cf29df7ab060f9c664a6" メタブラウザ = "HEAD:ee3be3b5986a4aa0e73df2204a625ae1fe5df37e" meta-rust = "ヘッド:53bfa324891966a2daf5d36dc13d4a43725aebed" meta-clang = "ヘッド:711e593d5984aad3bf35c51b7ac4482982bc16c7" メタノーム メタネットワーキング meta-filesystems = "HEAD:2b5dd1eb81cd08bc065bc76125f2856e9383e98b" メタ qt5 = "ヘッド:21ce4c124d9a972d9122f87c64ac2773bf04c284" メタpython2 = "ヘッド:4400f9155ec193d028208cf0c66aeed2ba2b00ab" 警告: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb:do_compile は強制実行によって汚染されています 警告: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb:do_deploy は強制実行によって汚染されています 警告: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2020.04.bb:do_compile強制実行により汚染されています 警告: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2020.04.bb:do_deploy強制実行により汚染されています タスクの初期化: 100% |#######################################|時間: 0:00:02 状態の概要: 募集 0 発見 0 見逃し 0 現在 4036 (一致率 0、完了率 100%) メモ: タスクの実行 注:セットシーンタスクが完了しました エラー: imx-image-full-1.0-r0do_sdk_depends:自動生成されたexec_python_func()でPython関数を実行するとエラーが発生しました。 この例外/失敗の原因となったPython呼び出しのスタックトレースは次のとおりです。 ファイル: 'exec_python_func() 自動生成', lineno: 2, 関数: 0001: 0002:extend_recipe_sysroot(d) 0003: ファイル: '/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/poky/meta/classes/staging.bbclass', lineno: 551, 関数: extend_recipe_sysroot 0547: dest = newmanifest[l] 0548: L.EndsWith("/") の場合: 0549: staging_copydir(l, targetdir, dest, seendirs) 0550: 続行 0551: staging_copyfile(l, targetdir, dest, postinsts, seendirs) 0552: 0553: bb.note("sysroot にインストールされました: %s" % str(msg_adding)) 0554: bb.note("sysroot にすでに存在するためスキップします: %s" % str(msg_exists)) 0555: ファイル: '/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/poky/meta/classes/staging.bbclass', lineno: 144, function: staging_copyfile 0140: os.path.islink(c) の場合: 0141: linkto = os.readlink(c) 0142: os.path.lexists(dest) の場合: 0143: os.path.islink(dest) でない場合: 0144: OSError(errno.EEXIST, "リンク %s はすでにファイルとして存在します" % dest, dest) 0145: os.readlink(dest) == linktoの場合: 0146: 帰還地 0147: OSError(errno.EEXIST, "リンク %s はすでに別の場所に存在しますか?(%s vs %s)" % (dest, os.readlink(dest), linkto), dest) 0148: os.symlink(linkto, dest) 例外:FileExistsError:[エラー番号17]リンク/home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/recipe-sysroot/libはすでにファイルとして存在します:'/home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/recipe-sysroot/lib' エラー:障害のログファイルが/home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/temp/log.do_sdk_depends.835827に保存されています。 エラー:タスク（/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/imx-image-full.bb）do_sdk_depends)が終了コード「1」で失敗しました 注: タスクの概要: 10496 個のタスクを試行しましたが、そのうち 10495 個は再実行する必要がなく、1 個が失敗しました。 概要: 1 つのタスクが失敗しました: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/imx-image-full.bb:do_sdk_depends 概要:5つの警告メッセージが表示されました。 概要: 1 つの ERROR メッセージが表示され、0 以外の終了コードが返されました。

imx8 bitbake extensible SDK error Hi all I have a need for extensible SDK.  I can build SDK by command bitbake imx-image-full -c populate_sdk, but can't build extensible SDK by command bitbake imx-image-full -c populate_sdk_ext. I'vd tried cleanall imx-image-full and changong python version 2 and 3. but neither works? Could anyone please give me advice?Thank you. The error message is as follows: oading cache: 100% |############################################| Time: 0:00:00 Loaded 4640 entries from dependency cache. Parsing recipes: 100% |##########################################| Time: 0:00:00 Parsing of 3218 .bb files complete (3217 cached, 1 parsed). 4641 targets, 464 skipped, 1 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.44.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "ubuntu-20.04" TARGET_SYS = "aarch64-poky-linux" MACHINE = "imx8mqevk" DISTRO = "fsl-imx-wayland" DISTRO_VERSION = "5.4-zeus" TUNE_FEATURES = "aarch64 cortexa53 crc crypto" TARGET_FPU = "" meta meta-poky = "HEAD:d88d62c20d7d8da85f02edb170dae0280624ad7e" meta-oe meta-multimedia meta-python = "HEAD:2b5dd1eb81cd08bc065bc76125f2856e9383e98b" meta-freescale = "HEAD:14f1a630a47375432f93c556927b879b51d84c4e" meta-freescale-3rdparty = "HEAD:dbcc686f52c3c84db8cb86aa8973a4e373651b98" meta-freescale-distro = "HEAD:ca27d12e4964d1336e662bcc60184bbff526c857" meta-bsp meta-sdk meta-ml = "HEAD:7f0abf664d65ab9f03f85a1d16ab54e0d1134a9b" meta-nxp-demo-experience = "HEAD:03904c493469907a2829cf29df7ab060f9c664a6" meta-browser = "HEAD:ee3be3b5986a4aa0e73df2204a625ae1fe5df37e" meta-rust = "HEAD:53bfa324891966a2daf5d36dc13d4a43725aebed" meta-clang = "HEAD:711e593d5984aad3bf35c51b7ac4482982bc16c7" meta-gnome meta-networking meta-filesystems = "HEAD:2b5dd1eb81cd08bc065bc76125f2856e9383e98b" meta-qt5 = "HEAD:21ce4c124d9a972d9122f87c64ac2773bf04c284" meta-python2 = "HEAD:4400f9155ec193d028208cf0c66aeed2ba2b00ab" WARNING: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb:do_compile is tainted from a forced run WARNING: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-kernel/linux/linux-imx_5.4.bb:do_deploy is tainted from a forced run WARNING: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2020.04.bb:do_compile is tainted from a forced run WARNING: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx_2020.04.bb:do_deploy is tainted from a forced run Initialising tasks: 100% |#######################################| Time: 0:00:02 Sstate summary: Wanted 0 Found 0 Missed 0 Current 4036 (0% match, 100% complete) NOTE: Executing Tasks NOTE: Setscene tasks completed ERROR: imx-image-full-1.0-r0 do_sdk_depends: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: 0001: *** 0002:extend_recipe_sysroot(d) 0003: File: '/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/poky/meta/classes/staging.bbclass', lineno: 551, function: extend_recipe_sysroot 0547: dest = newmanifest[l] 0548: if l.endswith("/"): 0549: staging_copydir(l, targetdir, dest, seendirs) 0550: continue *** 0551: staging_copyfile(l, targetdir, dest, postinsts, seendirs) 0552: 0553: bb.note("Installed into sysroot: %s" % str(msg_adding)) 0554: bb.note("Skipping as already exists in sysroot: %s" % str(msg_exists)) 0555: File: '/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/poky/meta/classes/staging.bbclass', lineno: 144, function: staging_copyfile 0140: if os.path.islink(c): 0141: linkto = os.readlink(c) 0142: if os.path.lexists(dest): 0143: if not os.path.islink(dest): *** 0144: raise OSError(errno.EEXIST, "Link %s already exists as a file" % dest, dest) 0145: if os.readlink(dest) == linkto: 0146: return dest 0147: raise OSError(errno.EEXIST, "Link %s already exists to a different location? (%s vs %s)" % (dest, os.readlink(dest), linkto), dest) 0148: os.symlink(linkto, dest) Exception: FileExistsError: [Errno 17] Link /home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/recipe-sysroot/lib already exists as a file: '/home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/recipe-sysroot/lib' ERROR: Logfile of failure stored in: /home/sysgration/imx8_5_4/imx8-yocto-bsp/build-wayland/tmp/work/imx8mqevk-poky-linux/imx-image-full/1.0-r0/temp/log.do_sdk_depends.835827 ERROR: Task (/home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/imx-image-full.bb:do_sdk_depends) failed with exit code '1' NOTE: Tasks Summary: Attempted 10496 tasks of which 10495 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/sysgration/imx8_5_4/imx8-yocto-bsp/sources/meta-imx/meta-sdk/dynamic-layers/qt5-layer/recipes-fsl/images/imx-image-full.bb:do_sdk_depends Summary: There were 5 WARNING messages shown. Summary: There was 1 ERROR message shown, returning a non-zero exit code. Re: imx8 bitbake extensible SDK error There is update at imx8-image-full but not need machine learning function features. - NXP Community Regards Harvey Re: imx8 bitbake extensible SDK error Hi @Harvey021  Because there is a problem by use imx-image-full -c populate_sdk_ext , so I need add QT5 then use imx-image-multimedia -c populate_sdk_ext. Thanks for your reply. Re: imx8 bitbake extensible SDK error Hi, What about the multimedia image burn and flash into board? As full image includes QT, sorry. I haven't got that experience for adding QT to multimedia. Regards Harvey Re: imx8 bitbake extensible SDK error Hi @Harvey021  I can build the multimedia version esdk (bitbake imx-image-multimedia -c populate_sdk_ext). Do you know how to add QT on multimedia esdk?Thanks.  Re: imx8 bitbake extensible SDK error Hi, esdk will include debug, which makes it larger. This makes it uncertain whether our wic format is sufficient. If debugging is needed, it is recommended to target a specific package instead of the entire toolchain. Regards Harvey

T2081 SD card boot Hi,   We have a custom board using T2081. We are trying to bring up the board using SD card. As given in document, we prepared the SD card with RCW, uboot-spl and u-boot. We are unable to progress because what we think SD card is not responding. We see activity on CMD line but not much beyond that. In order to debug this we plan to run uboot-spl in SRAM and the full u-boot from SD card. Can you let us know how to do this especially u-boot-spl from SRAM. We searched various forums and documents, but we did not get enough information. Re: T2081 SD card boot If configuring the target board to fetch RCW from SD card first, then run CodeWarrior SRAM project successfully(without using JTAG configuration file overriding RCW function), it means there is no problem to fetch RCW from SD card now. Probably you need to use CodeWarrior to debug SD u-boot, please refer to the following application note. https://community.nxp.com/t5/CodeWarrior-Development-Tools/CodeWarrior-U-Boot-Debugging/ta-p/1121398 Re: T2081 SD card boot Hii Yipingwang, below attached image  is of schematics, connecting buffer to SD card . Re: T2081 SD card boot Hii Yipingwang, I’m currently working on configuring my target board to fetch the RCW from an SD card. I’ve successfully created a SRAM project in CodeWarrior, and it runs without issues. However, I’m having trouble when attempting to boot from the SD card. after buffer we placed a pullup resistor on sd_clk with 10k(resistor value) Observations: I inserted the SD card into the board and monitored the sd_clk line before and after the buffer, as well as the sd_data0 line. Here are the details of the buffer I’m using: Part Number: MAX13035EETE+T. for your reference below i am attaching images is there any modifications needed please suggest. Re: T2081 SD card boot First, please configure the target board fetching RCW from SD card. Then use CodeWarrior to create a SRAM project and check whether this CodeWarrior SRAM project can run successfully. Use this method, you can verify whether RCW deployed in SD card is correct.

GPIO Clock Gating on S32K118 Hello, I am checking the clock configuration of S32K118 and noticed that there's a PLATCGC register under System Integration module:  "CGCGPIO - Controls the clock gating to the GPIO"  This CGCGPIO bit is not mentioned any other place in the reference manual document. What is the function of this bit? Should we enable the gating before using GPIOs?  Re: GPIO Clock Gating on S32K118 Hello, Thanks for the reply. Yes, it's only mentioned in SIM module section, but I think it would be beneficial to do the same in GPIO section. Overlooking this could lead to losing some time on configuration of GPIOs. By the way It seems that there's a duplication error there so it should be "GPIO Clock Gating Control". Regards. Re: GPIO Clock Gating on S32K118 Hi@zubizeratta Yes, this bit must be enabled before using the GPIO In fact you can find some description in the data sheet

Hardfault handler exception The jumptouserapplication() function is going to hardfault handler in NXP Kinetis Bootloader 2.0.0 Tried debugging but couldnt resolve. Kindly help Kinetis L Series MCUs Re: Hardfault handler exception Set the application start address in flash in MCU settings which resolved the issue Re: Hardfault handler exception Hello, my name is Pavel, and I will be supporting your case, but I´m following your 3 cases, I will continue this in the internal where you upload some images. Best regards, Pavel

LLCE CAN Controller can not be working in LLCE_CAN_STARTED but is always in LLCE_CAN_START_PENDING I am integrating LLCE  1.0.8 on s32g274a device with SW32G_RTD_4.4_4.0.2_P03，but have encountered a problem：after firmware was loaded and started successfully, then Can_43_LLCE_Init was  running ok and the state Can_43_LLCE_eDriverStatus  came to be CAN_43_LLCE_READY,  when Can_43_LLCE_SetControllerMode was called with parameter CAN_CS_STARTED, the firmware executed the cmd LLCE_CAN_CMD_GETCONTROLLERMODE successfully, then Can_Llce_GetControllerMode was called and firmware returned LLCE_FW_SUCCESS, but the returned controller state was always LLCE_CAN_START_PENDING,  I'm not sure what was wrong, so I want to get some useful solutions Re: LLCE CAN Controller can not be working in LLCE_CAN_STARTED but is always in LLCE_CAN_START_PEND Hi, Thanks for your feedback. As for the questions: it's required that the llce can controller have to be connected to the can tranceiver which was be enabled correctly in order to get the CAN bus voltage levels,  is that right ? That is correct. This is a HW requirement by the CAN standard itself, the following is shown under the Integration Manual for LLCE-CAN: "The CAN physical interface should be connected to the CAN-LLCE module pins in order to get the CAN bus voltage levels. There has to be at least another CAN node present on the CAN bus in order to get the CAN bus synchronized." Please, let us know. Re: LLCE CAN Controller can not be working in LLCE_CAN_STARTED but is always in LLCE_CAN_START_PEND Thanks, I'm using a custom board and our custom application, but configures the llce can by referring to the llce_sample_app_af examples, now I have resolved this problem, it was caused by the can timeout parameters: (Can Timeout Method) and (Can Timeout Duration)； On our custom board, the llce_can0 and llce_can2 hardware channel doesn't work without can transceiver attached, but llce_can1 and llce_can3 is working normally with TJA1403 being enabled correctly; In our costom application, (Can Timeout Method) and (Can Timeout Duration)  was set with OSIF_COUNTER_DUMMY and 65，during firstly enabling llce_can0 ,application was always looping with calling Can_Llce_MainFunctionMode, but after (Can Timeout Method) and (Can Timeout Duration)  was set with OSIF_COUNTER_DUMMY and 0.1, enabling llce_can0 to llce_can3  was normal, and only llce_can1 and llce_can3 were started successfully. Referring to  5.3 Peripheral Hardware Requirements  of the Integration Manual, it's required that the llce can controller have to be connected to the can tranceiver which was be enabled correctly in order to get the CAN bus voltage levels,  is that right ? Re: LLCE CAN Controller can not be working in LLCE_CAN_STARTED but is always in LLCE_CAN_START_PEND Hi, Is this a custom board? Or is this with an NXP reference board? Also, are you using any NXP examples? Or is this a custom application? We are not able to see the behavior you are describing. Can you share images of the behavior you are seeing? Please, let us know.

LLCE CANコントローラーはLLCE_CAN_STARTEDでは動作できませんが、常に動作していますLLCE_CAN_START_PENDING s32g274aデバイス上のLLCE1.0.8をSW32G_RTD_4.4_4.0.2_P03と統合していますが、問題が発生しました:ファームウェアがロードされて正常に起動した後、Can_43_LLCE_Initは問題なく実行され、Can_43_LLCE_SetControllerModeがパラメータCAN_CS_STARTEDで呼び出されたときに状態Can_43_LLCE_eDriverStatusがCAN_43_LLCE_READYになりました。 ファームウェアはcmd LLCE_CAN_CMD_GETCONTROLLERMODEを正常に実行し、次にCan_Llce_GetControllerModeが呼び出され、ファームウェアがLLCE_FW_SUCCESS返されましたが、返されたコントローラーの状態は常にLLCE_CAN_START_PENDINGでした、何が間違っていたのかわからないので、いくつかの有用な解決策を得たいです Re:LLCE CANコントローラーはLLCE_CAN_STARTEDでは動作できませんが、常に動作していますLLCE_CAN_START_PEND ありがとうございます 私はカスタムボードと私たちのカスタムアプリケーションを使用していますが、llce_sample_app_af例を参照してllce缶を構成し、今、私はこの問題を解決しました、それは缶のタイムアウトパラメータによって引き起こされました:(缶タイムアウト方式)および(缶タイムアウト期間)。 このカスタムボードでは、llce_can0とllce_can2のハードウェアチャンネルはCANトランシーバーが接続されていないと機能しませんが、TJA1403が正しく有効になっているllce_can1とllce_can3は正常に動作しています。 私たちのクライアントアプリケーションでは、(Can Timeout Method)と(Can Timeout Duration)がOSIF_COUNTER_DUMMYと65で設定されていましたが、最初にllce_can0を有効にすると、アプリケーションは常に呼び出しCan_Llce_MainFunctionModeでループしていました。 しかし、(Can Timeout Method)と(Can Timeout Duration)をOSIF_COUNTER_DUMMYと0.1に設定すると、llce_can0 llce_can3が可能になるのは正常であり、llce_can1とllce_can3のみが正常に開始されました。 インテグレーションマニュアルの5.3 Peripheral Hardware Requirementsを参照すると、CANバスの電圧レベルを取得するには、llce canコントローラーが正しく有効になっているcanトランシーバーに接続する必要がありますが、正しいですか?

ハードフォールト ハンドラーの例外 jumptouserapplication() 関数は、NXP Kinetis ブートローダ 2.0.0 のハードフォールトハンドラになります。 デバッグを試みましたが、解決できませんでした。 親切に助けてください Kinetis Lシリーズ・マイクロコントローラ Re:ハードフォールトハンドラの例外 マイコンの設定でアプリケーションの起動アドレスをフラッシュで設定し、問題を解決しました Re:ハードフォールトハンドラの例外 こんにちは、私の名前はPavelです、そして私はあなたのケースをサポートしますが、私はあなたの3つのケースをフォローしています、私はあなたがいくつかの画像をアップロードする内部でこれを続けます。 よろしくお願いいたします パベル

LLCE CAN 控制器不能在 LLCE_CAN_STARTED 中工作，但始终处于 LLCE_CAN_START_PENDING 状态 我正在使用 SW32G_RTD_4.4_4.0.2_P03 在 s32g274a 设备上集成 LLCE 1.0.8，但遇到了一个问题：固件加载并成功启动后，Can_43_LLCE_Init 运行正常，Can_43_LLCE_eDriverStatus 状态变为 CAN_43_LLCE_READY，当使用参数 CAN_CS_STARTED 调用 Can_43_LLCE_SetControllerMode 时，固件成功执行了命令 LLCE_CAN_CMD_GETCONTROLLERMODE，然后调用 Can_Llce_GetControllerMode 并返回 LLCE_FW_SUCCESS，但返回的控制器状态始终为 LLCE_CAN_START_PENDING，我不确定哪里出了问题，所以我想得到一些有用的解决方案 回复：LLCE CAN 控制器无法在 LLCE_CAN_STARTED 中工作，但始终处于 LLCE_CAN_START_PEND 状态 谢谢！ 我使用的是自定义板卡和自定义应用程序，但是参考llce_sample_app_af示例配置了llce can，现在我已经解决了这个问题，这是由can超时参数引起的：（Can Timeout Method）和（Can Timeout Duration）； 在我们的定制板上，如果没有连接 CAN 收发器，llce_can0 和 llce_can2 硬件通道就无法工作，但如果 TJA1403 正确启用，llce_can1 和 llce_can3 就可以正常工作； 在我们的自定义应用程序中，（Can Timeout Method）和（Can Timeout Duration）分别设置为OSIF_COUNTER_DUMMY和65，在第一次启用llce_can0时，应用程序一直循环调用Can_Llce_MainFunctionMode， 但在将(Can Timeout Method)和(Can Timeout Duration)设置为OSIF_COUNTER_DUMMY和0.1后，使能llce_can0至llce_can3正常，只有llce_can1和llce_can3启动成功。 参考集成手册的5.3外围硬件要求，要求llce CAN控制器必须连接到正确启用的CAN收发器才能获得CAN总线电压水平，对吗？

Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox Dear NXP Team, I am using MIMXRT1064-EVK and first I have started with Getting Started with the MIMXRT1064-EVK Evaluation Board  to set up a development environment with the MCUXpresso IDE toolchain. I have also successfully run the 'hello world' and 'led blinky' examples. After that, I have installed the i.MXRT1xxx support package and MBDT for MATLAB and Simulink, and started with the getting started guide for NXP i.MXRT1xxx MBDT with Simulink as follows:  Getting started with NXP i.MX RT1xxx Simulink Toolbox I have followed all the steps and instructions carefully but still, I am getting the error enclosed in the "mytest2024a_20240416_120817.txt" file. Thank you very much for your support and reply. Here, I am seeking your guidance to solve my mistake.  Best regards, Bvin Re: Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox The file format (.Id) is not supported in the attachment. So, I have not enclosed in my last reply. Thank you and regards, Bvin Re: Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox Hello Stefan, Thank you for your fast reply.  You are right about the linker file. The error itself is with the default linker file defined inside MBDT which I have used to configure my Simulink model. I have solved the error and modified the default linker file with the right name for the included files.  The default linker file (MIMXRT1064xxxxA.Id) path for MIMXRT1064 is as follows: C:\Users\***\AppData\Roaming\MathWorks\MATLAB Add-Ons\Toolboxes\NXP_MBDToolbox_IMXRT1xxx\mbdtbx_imxrt\devices\MIMXRT1064\linker_files\default\flash 1. Open file: MIMXRT1064xxxxA.Id 2. Look for the below-mentioned text lines:  INCLUDE "evkmimxrt1064_bubble_peripheral_Debug_library.ld" INCLUDE "evkmimxrt1064_bubble_peripheral_Debug_memory.ld" 3. Replaced the text lines mentioned in Step-2 with the following lines: INCLUDE "mimxrt1064xxxxA_library.ld" INCLUDE "mimxrt1064xxxxA_memory.ld" 4. Save file: MIMXRT1064xxxxA.Id 5. Now, I have run the Simulink model again and there was no error.  Enclosed you can find both the Original and Modified versions of the default linker files of the MBDT for your better understanding.  Best regards, Bvin Re: Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox Hello, @Bvin  Looking into the log file you have posted, it seems to me that your are trying to use a custom linker file that does not exist. If may I ask, did you provided another linker file to your model? How did you configured your model? Can you provide more information on how did you configured it? Regards! Stefan.

硬故障处理程序异常 jumptouserapplication() 函数将进入 NXP Kinetis Bootloader 2.0.0 中的硬故障处理程序 尝试调试但无法解决。 请帮忙 Kinetis L系列MCU 回复：Hardfault 处理程序异常 在 MCU 设置中设置闪存中的应用程序起始地址，解决了该问题 回复：Hardfault 处理程序异常 您好，我叫帕维尔，我会支持您的案例，但我会关注您的 3 个案例，我会在您上传一些图像的内部继续此工作。 此致， 帕维尔

quote characters got removed from defined symbols Hello user support, I have a strange SW build problem with MCUXpresso IDE v24.9 that the quote "" got removed Predefined symbols, this causes unexpected errors, please tell me how to fix it? I found a post with same problem Solved: v11.0.1 "Manage SDK Components" removes " from C++ Symbols - NXP Community But not sure where is the solution. I tried to change the double quote with <> but still not working and actually it's better to know the problem and solve it. SSS_CONFIG_FILE="fsl_sss_config_elemu.h" SSCP_CONFIG_FILE="fsl_sscp_config_elemu.h" macro expansion Error log: Thanks! Re: quote characters got removed from defined symbols Hi @BLEDev  Based on your  image and error message. You can try changing SSS_CONFIG_FILE="fsl_sss_config_elemu.h" SSCP_CONFIG_FILE="fsl_sscp_config_elemu.h" to SSS_CONFIG_FILE='"fsl_sss_config_elemu.h"' SSCP_CONFIG_FILE='"fsl_sscp_config_elemu.h"' BR Hang