Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
约克托·斯卡斯加普 您好,您计划很快发布Yocto Scarthgap imx-manifest吗? 如果是的话,那会是什么时候? 提前致谢!
View full article
where can I get PN7160_PN81T_DPC_Config_Template_CAS_v1.0.xls Hi, From AN13224, where can I get PN7160_PN81T_DPC_Config_Template_CAS_v1.0.xls? Thanks Re: where can I get PN7160_PN81T_DPC_Config_Template_CAS_v1.0.xls Hello jiafangguo,  Just download the document and check for the attachments as shown below:  BR Tomas 
View full article
evkmimxrt1060_wifi_cli demo problem I use i.MX RT1060 Evaluation Kit plug AW-AM510uSD to connect wifi. When I use evkmimxrt1060_wifi_cli from sdk to build and debug was no problem, but type "help" at terminal only show 3 commands can be used. So I cannot use the command like "ping" and so on, can anyone share me some advices? Product: WiFi IW6XX Re: evkmimxrt1060_wifi_cli demo problem Sor, I didn't mention that I used rt1060 evkb, and then based on Technician's advice, SDK should use another(https://mcuxpresso.nxp.com/en/builder?hw=MIMXRT1060-EVKB). Besides, I changed VIO on AM510. Now, it works perfectly!
View full article
Any MCU from NXP can support separated address and data pins for external bus? Hello,  I selected MCX Micro as a location for my question. But this question is not for specific MCU family from NXP. My question is, is there any MCUs from NXP that can support separated address and data pins for external bus? In my understanding, NXP's MCU that support the external bus interface  have multiplexed address/data pins. Regards, Norihiro Michigami AVNET Package and IO|GPIO Re: Any MCU from NXP can support separated address and data pins for external bus? Hello Jun,  Thank you for your comment. I understood your point. BTW, customer may have questions that are not classified to specific MCU like this question.  If there is a forum for general questions, it may be good for customers. Regards, Norihiro Michigami AVNET Re: Any MCU from NXP can support separated address and data pins for external bus? Hi norihiromichiga , Thanks. I was considering MCX because this is MCX space.  Considering other MCUs,  LPC17xx/18xx, LPC40xx integrates EMC module which has saperated data and address external bus. But these LPCs are legacy product which is not recommended for new design. RT1060 RT1170 also support EMC. I would suggest you consider as well. Hope this helps, Jun Zhang Re: Any MCU from NXP can support separated address and data pins for external bus? Hello Jun,  Thank you for your answer. But as I posted in my first post, my quesiton is not limited to MCX series. Does NXP have any series of MCU that can suppor seperated address and data bus of external bus interface? Regards, Norihiro Michigami AVNET Re: Any MCU from NXP can support separated address and data pins for external bus? Hi norihiromichiga, MCX N only supports external memory over FlexSPI interface or SPI  Hope this will help you, Jun Zhang
View full article
MBDT S32k358 が S32k 設定ツールに構成がありません こんにちは、私は現在、BMUがコントローラーとしてs32k358を持っている800V BMSを使用しています。ハードウェアボード設定をS32k358-Q172としてhvbmu2_read_s32ctの例をフラッシュしようとしたとき、外部構成ツール(S32k構成ツール)のBCC MCC33775Aに関連する構成が欠落していることがわかりました。具体的には、「trascation descriptor」がありません。しかし、ハードウェアボードの設定がS32k358-Q172というbcc_775a構成を見つけることができました。 このような構成ブロックを毎年追加しようとしましたが、成功しませんでした 問題は、s32k358 に外部 BCC モジュールに関連する設定がないのはなぜですか。また、サポートされていない場合は、S32k設定ツールを使用してs32k358に手動で追加するにはどうすればよいですか?または、どうすればBCC_775aとコミュニケーションをとることができますか? ありがとうございます。 サンプル・モデル Re:MBDT S32k358がS32k構成ツールに構成がありません こんにちは、提案された解決策をありがとう。BMSのMBDTをダウンロードしていないことに気づきました。 しかし、私はBMSツールボックスからブロックで版を作るのに苦労しています。外部構成ツールを開くのに失敗し、次に印刷されるエラー メッセージが matlab コンソールに出力されます。S32k358 ボード設定のトランザクション記述子コンフィギュレーションがまだありません。 "open_config_tool(0行目)の失敗:インデックスが配列要素の数を超えています。インデックスは 0 を超えてはなりません。 両方のツールボックスをインストールして再インストールしようとしましたが、役に立ちませんでした。なぜそれが起こっているのかわかりません。このエラーにつながる何かがあるのでしょうか?感謝。
View full article
i.MX 8QuadXPlus 上の Android Auto 13 (AAUG) 用の Dockerfile みなさん 私は i.MX 8QuadXPlusでAndroid 13のビルドを作成する必要があります 私はこのMEKが利用可能です: https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-development-boards/i-mx-8quadxplus-multisensory-enablement-kit-mek:MCIMX8QXP-CPU ここから: https://www.nxp.com/design/design-center/software/embedded-software/i-mx-software/android-automotive-os-for-i-mx-applications-processors:ANDROID-AUTO 「imx-automotive-13.0.0_2.3.0.tar.bz2」というファイルをダウンロードしました 私はドキュメントに記載されている手順に従っています。 https://www.nxp.com/docs/en/user-guide/Android_Auto_User's_Guide.pdf これは 2024 年 1 月 4 日に更新されます。 これらすべてを行うために、私はgl要素を含むDockerfile(ubuntu 18.04から)を作成しました。 https://source.android.com/docs/setup/start/requirements Dockerfileには、「Android_Auto_User's_Guide.pdf」で示されている次のようなパッケージも追加しました。 uuid uuid-dev \ zlib1g-dev liblz-dev \ liblzo2-2 liblzo2-dev \ lzop \ git curl \ u-boot-tools \ mtd-utils \ android-sdk-libsparse-utils \ デバイスツリーコンパイラ \ gdisk \ m4 \ バイソン\ フレックス メイク \ libssl-dev \ gcc-multilib \ libghc-gnutls-dev \ スウィグ \ liblz4-tool \ libdw-dev \ ドワーフ\ bc cpio tar lz4 rsync \ rsync ユーティリティ \ 忍者ビルドクラン \ ビルドエッセンシャル \ libncurses5 "Android_Auto_User's_Guide.pdf"の3/63ページ参照 ただし、次の2つのアイテムを削除する必要がありました - LZ4 -効用 「dockerbuild」コマンドでエラーが発生していたため、これらを削除しました。 誰かが同じ問題を抱えていますか? 日時:i.MX 8QuadXPlus上のAndroid Auto 13(AAUG)用のDockerfile 問題を解決しました 「LZ4」パッケージは既にliblz4-toolに含まれていますが、「ユーティリティ」パッケージは削除しました。ビルドは終了し、イメージはボード上に正しくプログラムされました。 日時:i.MX 8QuadXPlus上のAndroid Auto 13(AAUG)用のDockerfile ありがとう、 しかし、lz4をインストールしようとすると、次のことがわかります。 sudo apt-get lz4をインストールする [sudo] compandroidパスワード: パッケージリストを読み取っています...完成です 依存関係ツリーの生成 ステータス情報を読み込んでいます...完成です パッケージ lz4 には利用可能なバージョンはありませんが、別のバージョンによって名前が付けられています パッケージ。これは、パッケージが見つからないか、古くなっていることを示している可能性があります または、別のソース内でのみ利用可能です E: パッケージ "lz4" にはインストールする候補がありません。 LZ4パッケージは利用できません
View full article
i.MX 8M Plus EVK で M7 の QSPI を使用する方法 皆さん、こんにちは i.MX 8M Plus EVKをQSPI NORで使い始めるのに苦労しています。 「uuu -b qspi firmware.bin」を使用して8M Miniをフラッシュする方法の説明を見つけました。しかし、これはうまくいかないようです 私のEVKには、NORフラッシュにロードされたブートイメージが付属しているようです。 u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> sf read $loadaddr 0 0x100 device 0 offset 0x0, size 0x100 SF: 256 bytes @ 0x0 Read: OK u-boot=> md $loadaddr 40400000: 412000d1 007e1000 0005fc00 00000000 .. A..~......... 40400010: 007e0fe0 007e0fc0 0080b7c0 00000000 ..~...~......... 40400020: 007e0bc0 0002cc00 00000000 00000000 ..~............. 40400030: 00000000 00000000 00000000 00000000 ................ 40400040: 1400000a d503201f 40200000 00000000 ..... .... @.... QSPIのコードを使用してM7をフラッシュして起動する方法に関するアプリノートはありますか? Re:i.MX 8M Plus EVKでM7のQSPIを使用する方法 オフセット0にflash_debug/hello_world.binでフラッシュをプログラムしました。 u-boot=> load mmc 1 $loadaddr hello_world.bin 18664 bytes read in 4 ms (4.4 MiB/s) u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> sf erase 0 0x5000 SF: 20480 bytes @ 0x0 Erased: OK u-boot=> sf write $loadaddr 0 $filesize device 0 offset 0x0, size 0x48e8 SF: 18664 bytes @ 0x0 Written: OK Re:i.MX 8M Plus EVKでM7のQSPIを使用する方法 私はそれを理解しました... .binのプログラミング後ファイルをフラッシュに送り、U-Boot で次のコマンドを発行すると、M7 hello_world アプリを実行できます。 u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> bootaux 0x08000000 ## No elf image at address 0x08000000 ## Starting auxiliary core stack = 0x20020000, pc = 0x0800048D... そして、UART4 (/dev/ttyUSB3) に "hello world." と表示されます。
View full article
MBDT S32k358 在 S32k 配置工具中缺少配置 您好,我目前正在使用 800V BMS,其中 BMU 以 s32k358 作为控制器。当我尝试将硬件板设置为 S32k358-Q172 来刷新 hvbmu2_read_s32ct 示例时,我发现外部配置工具(S32k 配置工具)中缺少与 BCC MCC33775A 相关的配置。具体来说,它缺少“交易描述符”。但是,我能够找到硬件板设置为 S32k358-Q172 的 bcc_775a 配置。 我尝试手动添加这样的配置块,但没有成功 问题是,为什么s32k358缺少与外部BCC模块相关的配置?如果不支持,如何使用 S32k 配置工具手动将其添加到 s32k358?或者我如何与 BCC_775a 通信? 谢谢。 示例模型 回复:MBDT S32k358 在 S32k 配置工具中缺少配置 您好,感谢您提出的解决方案。我意识到我还没有下载 BMS 的 MBDT。 但是,我在从 BMS 工具箱制作版本时遇到了麻烦。外部配置工具打开失败,如下所示的错误消息打印到 matlab 控制台。S32k358 板设置仍缺少事务描述符配置。 “open_config_tool(第 0 行)失败:索引超出了数组元素的数量。索引不得超过 0。” 我尝试安装并重新安装这两个工具箱,但没有帮助。我不确定为什么会发生这种情况。有什么原因会导致这个错误吗?谢谢。
View full article
How to use QSPI for M7 on i.MX 8M Plus EVK Hi all, I'm having trouble getting started using the i.MX 8M Plus EVK with QSPI NOR. I've found instructions on how to flash the 8M Mini using "uuu -b qspi firmware.bin", but this doesn't appear to work on  My EVK seems to have come with a boot image loaded into the NOR flash: u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> sf read $loadaddr 0 0x100 device 0 offset 0x0, size 0x100 SF: 256 bytes @ 0x0 Read: OK u-boot=> md $loadaddr 40400000: 412000d1 007e1000 0005fc00 00000000 .. A..~......... 40400010: 007e0fe0 007e0fc0 0080b7c0 00000000 ..~...~......... 40400020: 007e0bc0 0002cc00 00000000 00000000 ..~............. 40400030: 00000000 00000000 00000000 00000000 ................ 40400040: 1400000a d503201f 40200000 00000000 ..... .... @.... Is there an app note regarding how to flash and start the M7 with code in QSPI? Re: How to use QSPI for M7 on i.MX 8M Plus EVK I programmed the flash with flash_debug/hello_world.bin at offset 0. u-boot=> load mmc 1 $loadaddr hello_world.bin 18664 bytes read in 4 ms (4.4 MiB/s) u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> sf erase 0 0x5000 SF: 20480 bytes @ 0x0 Erased: OK u-boot=> sf write $loadaddr 0 $filesize device 0 offset 0x0, size 0x48e8 SF: 18664 bytes @ 0x0 Written: OK Re: How to use QSPI for M7 on i.MX 8M Plus EVK I figured it out... After programming the .bin file to the flash, issuing these commands in U-Boot allow the M7 hello_world app to run: u-boot=> sf probe SF: Detected n25q256ax1 with page size 256 Bytes, erase size 4 KiB, total 32 MiB u-boot=> bootaux 0x08000000 ## No elf image at address 0x08000000 ## Starting auxiliary core stack = 0x20020000, pc = 0x0800048D... And I see "hello world." on UART4 (/dev/ttyUSB3).
View full article
Debugging app deployed to nor flash Hello  I'm using 1189EVK and loaded freertos hello world cm33 app to vscode.  I want to build, deploy and debug that app. But when deploying vscode shows an error  "Error: ENOENT: no such file or directory, open 'C:\NXP\MCUX_Provi_v9\bin\deviceInfo.json'" and indeed that file is not in that directory (provisioning tool version is 9.0.1). Is that vscode doen't support debugging on flash? Thanks Re: Debugging app deployed to nor flash Hi, Indeed you can have this problem if no rights, the issue is logged and will be addressed soon. In the mean time, please find attached the deviceInfo file. Remove the txt extension, copy it in the location and let me know if the problem is fixed. Regards, Melania.
View full article
Can't install S32K3xx Development Package and FreeMASTER Serial Communication Driver version 1.3.0 I have received the S32K3X4EVB-T172.  Question 1: When I tried install the S32DS 3.5.9, I could't  install the S32K3xx Development Package by SW32_S32DS_3.5.9_D2312.zip only showed S32 Design Studio Platform Package and S32 Design Studio Platform Tools Package.  2. Get Software: 2.2 Install the S32K3xx Development Package  Open About S32 Design Studio for S32 Platforms dialog (menu → Help → About S32 Design Studio for S32 Platforms) shows the following as: S32 Design Studio for S32 Platform Version: 3.5 Build id: 231219 (Update 9) Question 2: I have already installed the FreeMASTER 1.3.0 RTM (FMASTERSW32.exe) in Step "2.4 Get the Run-Time Debugging Tool", but I can't install "FreeMASTER Serial Communication Driver version 1.3.0" on S32DS Extensions and Updates dialog (menu → Help → S32DS Extensions and Updates).  The error message shows as following as: Operation details Software being installed: com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400 Missing requirement: com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400 requires 'org.eclipse.equinox.p2.iu; com.nxp.s32ds.s32k3.dev.feature.feature.group 1.0.0' but it could not be found. The installation Details: Package: GDB Client for Arm Embedded Processors 12.1 Build 1702; Version: 1702; Build id: 202309251304 Package: S32 Design Studio Platform package; Version: 3.5.9; Build id: 202312191958 Package: S32K3 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202303311831 Package: S32K3.P01 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202304031555 Package: GNU ARM PEMicro Interface Debugging Support; Version: 5.1.7; Build id: 202112141853 Package: S32 Design Studio Platform Tools package; Version: 3.5.9; Build id: 202312191958 Package: NXP GCC for Arm Embedded Processors Build 1620; Version: 1620; Build id: 202005201521 Package: S32 Design Studio Debugger Core; Version: 3.5.9; Build id: 202312191723 Re: Can't install S32K3xx Development Package and FreeMASTER Serial Communication Driver version 1.3 I have install the FreeMASTER 1.3.0 RTM (FMASTERSW32.exe) after that i had installed the S32K3xx Development Package from SW32K3xx_S32DS_3.5.0_D2303.zip (Upload from previous version S32DS 3.5.3).
View full article
部署到 Nor Flash 的调试应用程序 你好 我正在使用 1189EVK 并将 freertos hello world cm33 应用程序加载到 vscode。 我想构建、部署和调试该应用程序。但是部署vscode时显示错误 “错误:ENOENT:没有此文件或目录,打开‘C:\NXP\MCUX_Provi_v9\bin\deviceInfo.json’”,但该文件确实不在该目录中(配置工具版本为 9.0.1)。vscode 不支持在 flash 上调试吗? 谢谢!
View full article
无法安装S32K3xx开发包和FreeMASTER串行通信驱动程序版本1.3.0 我已经收到了S32K3X4EVB-T172。 问题 1 :当我尝试安装 S32DS 3.5.9 时,我无法通过SW32_S32DS_3.5.9_D2312.zip安装S32K3xx 开发包,仅显示S32 Design Studio 平台包和S32 Design Studio 平台工具包。 2.获取软件:2.2 安装S32K3xx开发包 打开关于 S32 平台的 S32 设计工作室对话框(菜单 → 帮助 → 关于 S32 平台的 S32 设计工作室)显示以下内容: 面向 S32 平台的 S32 设计工作室 版本:3.5 版本号:231219(更新 9) 问题 2 :我已经在步骤“2.4获取运行时调试工具”,但我无法在S32DS 扩展和更新对话框(菜单 → 帮助 → S32DS 扩展和更新)上安装“FreeMASTER 串行通信驱动程序版本 1.3.0”。 错误信息如下: 操作详情 正在安装的软件:com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400缺少要求:com.nxp.s32ds.s32k3.sdk.freemaster.feature.feature.group 1.3.0.202312191400 需要“org.eclipse.equinox.p2.iu;com.nxp.s32ds.s32k3.dev.feature.feature.group 1.0.0”但找不到。 安装详情: 软件包:适用于 Arm 嵌入式处理器 12.1 Build 1702 的 GDB 客户端;版本:1702;构建 ID:202309251304 软件包:S32 Design Studio 平台软件包;版本:3.5.9;版本号:202312191958 软件包:S32K3 RTD AUTOSAR R21-11 版本 3.0.0;版本:3.0.0;版本号:202303311831 软件包:S32K3.P01 RTD AUTOSAR R21-11 版本 3.0.0;版本:3.0.0;版本号:202304031555 软件包:GNU ARM PEMicro 接口调试支持;版本:5.1.7;版本号:202112141853 软件包:S32 Design Studio 平台工具包;版本:3.5.9;版本号:202312191958 软件包:NXP GCC for Arm Embedded Processors Build 1620;版本:1620;版本号:202005201521 软件包:S32 Design Studio Debugger Core;版本:3.5.9;版本号:202312191723 回复:无法安装S32K3xx开发包和FreeMASTER串行通信驱动程序版本1.3 我已经安装了FreeMASTER 1.3.0 RTM (FMASTERSW32.exe),之后我从 SW32K3xx_S32DS_3.5.0_D2303.zip 安装了 S32K3xx 开发包(从以前的版本 S32DS 3.5.3 上传)。
View full article
Another imx8mp 4GB LPDDR uboot question Hello, We have board based on the imx8mp evk that has 4GB LPDDR4 instead of 6G, and I'm trying to understand the correct settings for PHYS_SDRAM_SIZE and the memory devicetree node. The memory module (MT53E1G32D2FW) datasheet lists 32Gb/package, 16Gb dual-channel die. Listed are 2 die, 2 channels per die, and 8 banks per channel. Density: 8Gb per channel, 16Gb per die. I ran the DDR tool and got the timings for the board to boot. Now I need to do the uboot configuration. It seems I have 2 primary options for uboot configuration 3GB/1GB or 2GB/2GB splits. 3GB/1GB split Board header: #define PHYS_SDRAM_SIZE 0xc0000000 /* 3 GB */ #define PHYS_SDRAM_2_SIZE 0x40000000 /* 1 GB */ Device tree: reg = <0x0 0x40000000 0 0xc0000000>, <0x1 0x00000000 0 0x40000000>; or 2GB/2GB split Board header: #define PHYS_SDRAM_SIZE 0x80000000 /* 2 GB */ #define PHYS_SDRAM_2_SIZE 0x80000000 /* 2 GB */ Device tree: reg = <0x0 0x40000000 0 0x80000000>, <0x1 0x00000000 0 0x80000000>; They both seem to boot ok, but I'm not sure which is correct (if any). In this post, there was this was the suggestion: #define PHYS_SDRAM_SIZE 0xC0000000 /* 3 GB */ //This value is the size that you will need for your first die on your memory. In this case 3GB. Since the density of each die on this DDR is 16Gb (2GB), that would indicate that I should use a 2G/2G split. However, in this post, the suggestion was: .xlsx seems as correct. For imx8mp_evk.h suggest to leave "PHYS_SDRAM_SIZE" in default value, This suggestion would indicate that I should use the 3GB/1GB split. Here is another post where the person tried both ways, although their issue was not running the DDR tool first. I've seen both approaches in various board headers in the uboot source tree, which only adds confusion. So my question is whether PHYS_SDRAM_SIZE should be based on the die density (16Gb) value or set  to the size of the imx8mp's first DDR memory map region (3GB)? In other words, is the 3GB/1GB split or 2GB/2GB split correct? i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Another imx8mp 4GB LPDDR uboot question I haven't found anyone yet, but do you have this tool? https://www.nxp.com/design/design-center/development-boards-and-designs/i-mx-evaluation-and-development-boards/config-tools-for-i-mx-applications-processors:CONFIG-TOOLS-IMX I'm pretty sure all we did was generate the initial file by filling in the device info on the DDR screen. After you choose the part number when creating a new project, you go to the DDR screen using the menu at the top. It will load a table that you fill in the module info. This will update the tabs on the right with the .ds and the timing.c files. You can see the tabs I'm talking about in the second screenshot on the tool's main page (see below). I believe these are the settings from the datasheet that go in the table. 8 2 2 32 16 10 3 8 32 2000 0.5 200 5 50 20 Without the pins to run the tool, though, you won't be able to tune the settings or run the validation tests. From experience, you may end up with some very tricky bugs down the road without doing those steps. Re: Another imx8mp 4GB LPDDR uboot question Thanks for your quick response.  Well in theory, the ddr tool can communicate with a board that doesn't have OTG as long as the circuit is configured as USB-Device. The issue is we don't have all the USB pins exposed on our board to make it work like that. That's why I'm searching for the file lpddr4_timing.c obtained for the RAM MT53E1G32D2FW. Re: Another imx8mp 4GB LPDDR uboot question Hi rcossdev, One of our hardware guys was able to generate the details for the config tool by filling in the device info table in the DDR configuration spreadsheet. He used the one from here. From what I remember, we copied the data from the last tab to the config tool to actually generate the c code. Requirements changed and we actually moved over to the mx8mq. I had to clear that workspace to make room due to the size of yocto, so I'll have to see if anyone still has a copy. The caveat is that we never got that board to actually pass all of the config tool's DDR validation tests before switching boards. I know the docs say that OTG is required, but I used the config tool on the board we were working on and the hardware guys later assured me that it did not have OTG. I do remember having to connect both the USB cable and separate usb-serial adapter without any SD cards to get the tools to communicate with the board and load the validation code. I'm not sure why that worked, but it did pass the lower frequency tests for what it's worth. Re: Another imx8mp 4GB LPDDR uboot question Hello jmp, Did you manage to generate the lpddr4_timing.c file? We designed a board based also on the imx8mp using the same RAM (MT53E1G32D2FW) But since we didn't include the OTG circuitry we're unable to run the ddr tool and we're struggling to do the bring-up of the board. I'd really appreciate if you could share your timing file. Thanks! Re: Another imx8mp 4GB LPDDR uboot question Perfect, thank you for the clarification. Re: Another imx8mp 4GB LPDDR uboot question yes, we suggest customer to use 3G+1G, you also can find the definition for DDR4(4G) in the uboot https://github.com/varigit/uboot-imx/blob/imx_v2020.04_5.4.70_2.3.2_var01/include/configs/imx8mp_evk.h but I think if you use 2G should be fine, if 3G+1G works for you why do you struggle with this? just use this, it's fine, you can find imx8mp memory map from reference manual
View full article
nor flash にデプロイされたアプリのデバッグ こんにちは 私は1189EVKを使用しており、freertos hello world cm33アプリをvscodeにロードしました。 そのアプリをビルド、デプロイ、デバッグしたいと思います。しかし、vscodeをデプロイするとエラーが表示されます 「エラー:ENOENT:そのようなファイルまたはディレクトリはありません。'C:\NXP\MCUX_Provi_v9\bin\deviceInfo.json'を開いてください」と、実際にはそのファイルがそのディレクトリにありません(プロビジョニングツールのバージョンは9.0.1です)。それはvscodeがフラッシュでのデバッグをサポートしていないのですか? ありがとうございます
View full article
S32K3 RTD5.0.0 lpi2c hello! Recently, I updated RTD4.0.0 to 5.0.0, then got problem. In Lpi2c configure page, "I2C Clock Source" don't contains any value.(in RTD4.0.0 it works ok) the RTD error is : Source clock is not enabled in Clock component is that a bug ? or something I didn't configure? 回复: S32K3 RTD5.0.0 lpi2c Hi@Vandarkholme Please add"Clock_Ip_ReferencePoints" and then try again. 回复: S32K3 RTD5.0.0 lpi2c oh, I add clockReference then it worked! In RTD5.0.0 clockReference is key component? RTD4.0.0 not need to configure that component
View full article
Difference between EIM and FCCU NCFF Hello, I'm currently learning on how to work with some safety concepts on the S32K344-Q257EVB, namely the FCCU, and i wanted to test it and see how it reacts to faults (in terms of changing states in the Finite State Machine (FSM) and checking the FCCU1/FCCU2 signals with an oscilloscope to see if they get asserted or not). My question is, how should i do that? On the reference manual i have read that the FCCU has some Non-Critical Fault Fake (NCFF) that could be used to achieve that, but there is also an Error Injection Module (EIM) and that is where my confusion begins. What is the difference between both? In which cases should i use one and/instead of the other? Thanks in advance! Best regards, JRodrigues Re: Difference between EIM and FCCU NCFF Hello Peter, Thanks for the clarification. Have a good rest of your day! Best Regards, JRodrigues Re: Difference between EIM and FCCU NCFF Hello, the NCFF referring to "All SRAM ECC uncorrectable error ERM_SRAM or ECC cache memory error.." can act as a fault that "happened in the memory and was then reported to the FCCU"? NCFF will inject the fault only to FCCU fail state machine (FSM). So you can verify the reaction of device in case such fault will come to FCCU. But NCFF will not inject the ECC error physically to ECC mechanism nor to the memory. For such purpose you will you EIM. So if you want to verify the reaction of ECC and reaction path on error in ECC mechanism to FCCU NCFSx, you will need to use EIM. Best regards, Peter Re: Difference between EIM and FCCU NCFF Hi Peter, So, in the S32K3xx_fault_map excel file that comes with the reference manual, the NCFF referring to "All SRAM ECC uncorrectable error ERM_SRAM or ECC cache memory error.." can act as a fault that "happened in the memory and was then reported to the FCCU"? Best Regards, JRodrigues Re: Difference between EIM and FCCU NCFF Hello, You can use for EOUT tests NCFF which can inject the faults to the FCCU. Usually you use it when you want to verify the FCCU reaction on incoming fault. It however cant physically inject fault to peripherals/ memories. In some cases there is inejction dirrectly on tested peripheral or FCCU can inject fault only to the status register like STCU_ERR and not in the test itself. However EIM: The Error Injection Module (EIM) is mainly used for diagnostic purposes. It provides a method for diagnostic coverage of internal memories (for example, system RAM, cache RAMs, and peripheral memories). EIM enables you to induce artificial errors on error-checking mechanisms of a system, such as ECC for RAM read data and parity bits. So EIM will create a physical fault on memory and memory then reports fault to FCCU. This way you can test for example if your ECC mechanism is working correctly, etc... Best regards, Peter
View full article
i.MX7 Solo LCD信号とピン配置 ご列席の皆様、 私はここのような同様の問題を抱えています: https://community.nxp.com/t5/i-MX-Processors/i-MX7-LCD-Pinout/m-p/1599101 しかし、私の質問は24ビット幅のLCDインターフェースです。 データシート ( IMX7SCEC Rev. 7, 09/2023 ) にもリファレンス マニュアル ( IMX7SRM Rev. 0.1, 08/2016 ) にも、どのピンが信号 R[0], R[1] に属しているかがわかりません。G[0]、G[1]、....B[0]、...[7]。 この情報は、HW回路を設計するために不可欠です。 ここでは、信号は次のようになります。 LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7] ? つまり、LCD_DATA[00] = B0, LCD_DATA[01]= B1, ....そしてLCD_DATA[22]=R6、LCD_DATA23=R7、それぞれです。私は正しいですか? これらの信号とそのピン配置の具体的な宣言は、ドキュメントのどこで確認できますか。   日時:i.MX7ソロLCD信号とピン配置 こんにちは はい、その通りです。 LCD_DATA[00-07] = B[0-7] LCD_DATA[08-15]=G[0-7] LCD_DATA[16-23]=R[0-7]  これについては、i.MX7D Sabreの回路図を参照してください。 よろしくお願いします/サルドス、 アルド。
View full article
EB:如何在EB中设置优先级分组? 当我在平台模块中使能Isr的时候,发现最大优先级只能到15,如果优先级设置的大于15的话,EB就会报优先级超出范围的错误。我怎样才能将优先级设置为大于 15?我想知道是否可以在EB中设置优先级组。 这里我使用s32k344和RTD 4.0.0.0
View full article
EB 生成コード: modules.h の Marco use_Gpt_moduleSTD_ONに変更することはできません EBにGPT、basenxp、platform、resource、その他のモジュールを追加し、コードを生成した後、Marcoがmodules.hをuse_Gpt_moduleしていることがわかりました。STD_ONに変更することはできません。このマルコをSTD_ONに変更する方法は? 回复: EB 生成コード: Marco use_Gpt_module of modules.hSTD_ONに変更することはできません ここではs32k344を使用しています。
View full article