Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
S32K3_HSE_ASB_postboot_passflag Hi, NXP I am now ready to use HSE's ASB to verify my BOOT and APP. I use Preboot SMR to verify my BOOT and release the M7 kernel when the verification passes. Then I used postboot to verify my APP in parallel. The problem now is how to confirm that my APP verification was successful. (I can't find the status sign of postboot pass) The current idea is to wait for the HSE initialization to complete before jumping to the APP, and then confirm whether the verification is successful by checking whether the SMR KEYs are valid. Can this method be implemented? is there a better way? Best Regards, xianlong Re: S32K3_HSE_ASB_postboot_passflag Thank you very much for your help. I ignored the API documentation before and did not find the information. Re: S32K3_HSE_ASB_postboot_passflag Hi Yes, the end of post boot phase can be monitored by HSE_STATUS_INIT_OK: You can read the status directly. See struct hseAttrSmrCoreStatus_t in HSE Service API reference manual: You can find an example for Get Attribute service in HSE DemoExamples: https://www.nxp.com/webapp/Download?colCode=S32K3_HSE_DemoExamples This is from c:\NXP\S32K3_HSE_DemoExamples_1_0_0\S32K3_HSE_DemoExamples\Secure_Boot\S32K344_Advanced_SecureBoot: /* Get status of the Secure Memory Region and Core Reset Entry installation */ HseResponse = Get_Attr( HSE_SMR_CORE_BOOT_STATUS_ATTR_ID, sizeof(hseAttrSmrCoreStatus_t), (void *)(&smrCoreStatus)); ASSERT(HSE_SRV_RSP_OK == HseResponse); Regards, Lukas
記事全体を表示
Difference between different HSE subsystems Hello everyone, I was wondering what the difference is between the HSE subsystems HSE_H, HSE_M and HSE_B? Is the difference just in which board they run on, or are there functional differences as well? Thank you! Re: Difference between different HSE subsystems Hi @joma  The main differences between each version lie in the host system images required to operate on Flash-less devices or devices with embedded Flash. The HSE-H&M runs on a Cortex-M7 core, while the HSE-B runs on a Cortex-M0+ core. All versions provide the following services, divided into the following classes: Administration services: installation, configuration, and testing of the HSE. Key management services: management of different key sets handled by the HSE, for example, through cryptographic services. Cryptographic services: providing the application with cryptographic primitives used by high-level security stacks in the application. Random number services: generating random streams that can be used in various security protocols. Memory verification services: allowing the application to verify different memory areas during startup (after reset) and runtime. Monotonic counter services: providing the application with a set of monotonic counters that can only be read and incremented. The difference between versions lies in the feature support. Re: Difference between different HSE subsystems Hi @VaneB thank you for your quick response. Unfortunately, this only answers the first part of my question. However, I am also interested in whether there are functional differences or whether the functionality is identical. I don't expect a detailed answer here, but I think you are allowed to answer yes or no 🙂 Since you also mentioned Base, Medium and High, can I assume that this refers to the security rating? In other words, if I have a project with a high security level, then I can't use an S32K3XX, but have to use an S32G2, for example? Kind regards joma Re: Difference between different HSE subsystems Hi @joma  The HSE subsystem exists in three variants, depending on the device in which it integrates: - HSE_H (High) is available on Flash-less S32x product variants (such as S32G2, S32G3, S32ZE, and S32R45). - HSE_M (Medium) is available on Flash-less S32x product variants (such as S32R41, SAF85XX, and SAF86XX). - HSE_B (Base) is available in S32x product variants with embedded Flash (such as S32K3XX, S32M27X, and MWCT2XX3A). Unfortunately, due to security restrictions related to working with automotive components, I am unable to share further details. The HSE reference manuals are accessible only through secure files. If you have not previously accessed secure files, please follow the guide below to request safety documentation: How to request safety documentation: Support Information BR, VaneB
記事全体を表示
不同HSE子系统之间的差异 大家好, 我想知道 HSE 子系统 HSE_H、HSE_M 和 HSE_B 之间有什么区别? 区别仅在于它们在哪个主板上运行,还是在功能上也有区别? 非常感谢! 回复:不同 HSE 子系统之间的差异 你好@VaneB 感谢您的快速回复。 不幸的是,这只回答了我的问题的第一部分。 但是,我也对是否存在功能差异或功能是否相同感兴趣。我不期望这里有详细的答案,但我认为你可以回答是或否 🙂 既然您还提到了基础、中和高,我可以假设这是指安全等级吗? 换句话说,如果我有一个安全级别很高的项目,那么我就不能使用 S32K3XX,而必须使用 S32G2,例如? 亲切的问候 乔马
記事全体を表示
imx8 Quad Max uboot 保险丝程序错误 我正在尝试烧掉 Quad Max 的保险丝。 保险丝程序-y 0 722 0x........ 将 Bank 0 字 0x000002d2 编程为 0x........ 错误 => 保险丝读取 0 722 读取组 0: 字 0x000002d2: 00000000 我已经为 AHAB 创建了 uboot 设置,并且 uboot 的“安全版本”正在运行(我还没有烧毁任何保险丝,这是第一次尝试) U-Boot 2020.04 是否需要改变 SCFW 才能允许保险丝烧断? i.MX 8 系列 | i.MX 8QuadMax (8QM) | 8QuadPlus 回复:imx8 Quad Max uboot 保险丝程序错误 通过将 SECO 固件更新至 3.8.5 解决了该问题。 $ wget https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/imx-seco-3.8.5.bin 回复:imx8 Quad Max uboot 保险丝程序错误 uboot最终调用/uboot/drivers/misc/imx8/fuse.ccall_imx_sip() 烧录 fusw=e,调用 smc_call()。 smc_call 调用哪个模块,sc_firmware 还是 seco? smc_call 所属的任何一方均失败。   如何确定/修复? 喜欢    
記事全体を表示
Yocto 构建失败(vulkan-validation-layers) 运行 bitbake imx-image-multimedia,全部通过,但 vulkan-validation-layers 一直失败。不确定如何继续。 尝试使用 bitbake vulkan-validation-layers -c clean,但仍然出现同样的错误 错误:任务(/opt/yocto/imx-6.6.52-2.2.0-build/sources/poky/meta/recipes-graphics/vulkan/vulkan-validation-layers_1.3.275.0.bb:do_compile)失败,退出代码为“1” 注意:任务摘要:尝试了 1669 项任务,其中 1668 项无需重新运行,1 项失败。 附加日志文件。 回复:Yocto 构建失败(vulkan-validation-layers) 谢谢。 在配备 16GB 内存的 6 核 12 线程英特尔处理器上运行。 通过将其添加到 local.conf 中,设法使其工作 BB_NUMBER_THREADS = "2" PARALLEL_MAKE = "-j2"
記事全体を表示
[S32K312 External Mode Issue] Monitor & Tune Fails to Connect Hello, I am working with an S32K312 Evaluation Board and the NXP Model-Based Design Toolbox for MATLAB/Simulink. I can successfully build and deploy my application to the board—my code runs as expected, and I can see the results. However, when I try to use external mode example project and click the “Monitor & Tune” button, I consistently receive an error stating that Simulink cannot connect to the target.  I have already checked the following: The correct COM port is selected under Model Configuration Parameters > Hardware Implementation > Target Hardware Resources > External Mode. The correct configuration project template is selected under Model Configuration Parameters > Hardware Implementation > Target Hardware Resources > Hardware Drivers for OpenSDA/PEmicro appear to be installed correctly (no errors in Device Manager). The board is powered. Could anyone suggest additional steps, configuration details, or known workarounds for getting External Mode to function on the S32K312? Any guidance would be appreciated. Thank you. Re: [S32K312 External Mode Issue] Monitor & Tune Fails to Connect Hi @Berke_E , I have tried to replicate the steps in s32k3xx_extmode_ebt_example_readme.html, please follow along: 1. Open the s32k3xx_extmode_ebt model and go to Hardware Settings -> Target hardware resources -> Select Configuration Project Template to be S32K312-Q172 EB Tresos:  2. Then this Warning Dialog will appear on screen and click OK:   3. Then go to External Mode and select the Serial port of your board, press Refresh: 4. The serial com port must match the K312 boards OpenSDA as in Device Manager, in my case is COM12: 5. Click on Apply and OK, to close Configuration Parameters. 6. Press Monitor & Tune in Simulink, wait 1-2 minutes, then the Blue LED will toggle on the K312 board. 7. Open the Scope output and see the sinusoidal shape:   These steps are from the s32k3xx_extmode_ebt_example_readme.html , that my colleague @Irina_Costachescu  mentioned above, Hope this helps, Stefan V. Re: [S32K312 External Mode Issue] Monitor & Tune Fails to Connect Hi @Berke_E  All the steps required to run External Mode are described in the readme file associated to the model, under the Prepare the Demo section. For being able to provide more guidance, could you please share with us the hardware setup that you are using? For External Mode you need to enable a Serial Connection via the USB port specified in the application model help file. Based on your point 1. I understand that this connection is established already. Also, based on point 2. I understand that your model is already configured to address an S32K312 processor? Thanks, Irina
記事全体を表示
imx8 Quad Max uboot ヒューズ プログラム エラー Quad Maxのヒューズを燃やしようとしています。 ヒューズ prog -y 0 722 0x........ プログラミング バンク 0 ワード 0x000002d2 から 0x........ エラー => ヒューズ読み取り 0 722 読み取りバンク0: ワード0x000002d2: 00000000 AHABのubootセットアップを作成し、ubootの「セキュアバージョン」を実行しました(まだヒューズを燃やしておらず、これが最初の試みです) Uブート 2020.04 ヒューズの燃焼を可能にするためにSCFWの変更が必要ですか? i.MX 8ファミリ | i.MX 8QuadMax (8QM) | 8QuadPlus Re: imx8 Quad Max uboot ヒューズ プログラムエラー この問題は、SECOファームウェアを3.8.5にアップデートすることで解決されます。 $ wgetの https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/imx-seco-3.8.5.bin Re: imx8 Quad Max uboot ヒューズ プログラムエラー Uboot は最終的に /uboot/drivers/misc/imx8/fuse.c を呼び出します。call_imx_sip() を使用して fusw=e を焼き、smc_call() を呼び出します。 smc_callはどのモジュール、sc_firmware、またはセコに呼び出していますか? smc_callが誰に属しているにせよ、失敗しているのです。   決定/修正する方法は? という感じで    
記事全体を表示
Error installing S32_Design_Studio_for_S32_Platform_3.6.0 I cant install S32 Design Studio for S32 Platform 3.6.0  on Windows 10 Pro. There is a error entry in the installation log: S32 Design Studio for S32 Platform 3.6.0(Install All Uninstaller Components) Status: ERROR Additional Notes: ERROR - Error writing LaunchAnywhere components (Access Denied) There is some prolem with my activation code.  It doesn't matter whether I use online or offline registration, the result is always the same: the installation process stops and ends when verifying the license. Is there a solution for this? Thanks, Richard Re: Error installing S32_Design_Studio_for_S32_Platform_3.6.0   In the end, it turned out that the problem was either with Windows or the installation software used, InstallAnywhere. My main disk C in Windows had only about 11GB of free space, so I planned to install the software on disk D, which had enough capacity. However, S32 Design Studio requires about 12.5GB of space for temporary files during installation. When I launched the installer S32DS_3.6.0_win32.x86_64.exe, an error message appeared (the screenshot in Czech is attached): "There is not enough space for the complete installation. Please select a temporary folder to place the installer." So, I selected a folder on disk D, but the installation always ended with the error described above. In the end, freeing up space on disk C helped – after I freed up a total of 13GB on disk C, the installation went as expected. Problem solved. Thanks, Richard Re: Error installing S32_Design_Studio_for_S32_Platform_3.6.0 Hello @rick1964. Similar situations have been discussed in the community before. Please take a look at the below community thread and let me know if the solution provided there was helpful to you. Installation of S32DS V3.6 fails on Windows 11. - RomanVR. Re: Error installing S32_Design_Studio_for_S32_Platform_3.6.0 Thanks, but I've tried this several times. I delete the license using licfix, then run the installation and copy the activation code directly from the email to avoid any transcription errors. The result is always the same (see attachment). What's strange is that I successfully installed Studio on another older computer (running Windows 7) using the same code without any issues. On the computer where the installation fails, I already have S32 Design Studio for Arm installed, as well as other software (MUXpresso, FreeMaster)." Best regards, Richard Re: Error installing S32_Design_Studio_for_S32_Platform_3.6.0 Hello @rick1964  Please try running the S32DS installer with administrator rights and ensure that the activation code has no typos. This error is generally caused by user rights restrictions. Please let me know if this is helpful. - RomanVR.
記事全体を表示
imx8 Quad Max uboot fuse prog ERROR I am trying to burn the fuses for the Quad Max. fuse prog -y 0 722 0x........ Programming bank 0 word 0x000002d2 to 0x........ ERROR => fuse read 0 722 Reading bank 0: Word 0x000002d2: 00000000 I have created the uboot setup for AHAB, and the "secure version" of uboot runs (I have not burned any fuses yet, this is the first attempt) U-Boot 2020.04 Is there a SCFW change needed to allow fuse burning? i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Re: imx8 Quad Max uboot fuse prog ERROR The issue is solved by updating SECO firmware to 3.8.5. $ wget https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/imx-seco-3.8.5.bin Re: imx8 Quad Max uboot fuse prog ERROR Uboot ultimately calls calls /uboot/drivers/misc/imx8/fuse.c call_imx_sip() to burn the fusw=e, which calls smc_call(). Which module is the smc_call calling into, sc_firmware, or seco? Whomever smc_call belongs to is failing.   How to determine/fix? Like     Re: imx8 Quad Max uboot fuse prog ERROR I followed all/any of the AHAB directions from Variscite and NXP, and a few other companies that support imx8 Quad Max processors. Most did not have the steps required for auth_cntr part that needed to be in the config, but auth_os runs without error. Uboot seems fine otherwise, just no fuse burn... using: ATF 2.6 imx-seco-3.75 imx-sc-firmware-1.11.0 Linux 5.10.71 U-Boot 2020.04 Re: imx8 Quad Max uboot fuse prog ERROR Hi, Thank you for your interest in NXP Semiconductor products, Could you confirm that you have followed the steps correctly until this point? Also, what is the SECO FW version used? This causes OTPs to not be flashed. Regards
記事全体を表示
Yocto ビルドの失敗 (vulkan-validation-layers) bitbake imx-image-multimedia を実行すると、vulkan-validation-layers 以外のすべてのパスが失敗し続けます。どのように進めればよいかわかりません。 vulkan-validation-layers -c cleanをビットベイクしようとしましたが、それでも同じエラーが発生します エラー:タスク(/ opt / yocto / imx-6.6.52-2.2.0-build / sources / poky / meta / recipes-graphics / vulkan / vulkan-validation-layers_1.3.275.0.bb:do_compile)が終了コード「1」で失敗しました 注: タスクの概要: 1669 個のタスクを試行し、そのうち 1668 個を再実行する必要がなく、1 個が失敗しました。 ログファイルを添付。 Re:Yoctoビルドの失敗(vulkan-validation-layers) 感謝。 16GBのRAMを搭載した6コア12スレッドIntelで実行。 これをlocal.confに追加することで、なんとか動作させることができました BB_NUMBER_THREADS = "2" PARALLEL_MAKE = "-j2"
記事全体を表示
S32_Design_Studio_for_S32_Platform_3.6.0 のインストール中にエラーが発生しました S32 Design Studio for S32 Platform 3.6.0 をインストールできませんWindows 10 Proで。 インストールログにエラーエントリがあります。 S32 Design Studio for S32 Platform 3.6.0(インストールすべてのアンインストーラコンポーネント) ステータス: ERROR 追記事項: ERROR - Error writing LaunchAnywhere components (Access Denied) 私のアクティベーションコードにはいくつかのプロレムがあります。 オンライン登録とオフライン登録のどちらを使用するかは関係なく、結果は常に同じです:ライセンスを確認すると、インストールプロセスが停止および終了します。 これに対する解決策はありますか? ありがとうございます リチャード 日時:S32_Design_Studio_for_S32_Platform_3.6.0のインストール中にエラーが発生しました   結局、問題はWindowsまたは使用されたインストールソフトウェアであるInstallAnywhereのいずれかにあることが判明しました。WindowsのメインディスクCには約11GBの空き容量しかなかったため、十分な容量があるディスクDにソフトウェアをインストールすることを計画しました。ただし、S32 Design Studioは、インストール中に一時ファイル用に約12.5GBのスペースを必要とします。インストーラー S32DS_3.6.0_win32.x86_64.exeを起動してみたところ、エラーメッセージが表示されました(チェコ語のスクリーンショットが添付されています)。 「完全な設置には十分なスペースがありません。インストーラーを配置する一時フォルダを選択してください。 そこで、ディスクD上のフォルダを選択しましたが、インストールは常に上記のエラーで終了しました。結局、ディスクCのスペースを空けたおかげで、ディスクCのスペースを合計13GB空けた後、インストールは予想通りに進みました。 問題は解決しました。 感謝 リチャード 日時:S32_Design_Studio_for_S32_Platform_3.6.0のインストール中にエラーが発生しました こんにちは、@rick1964。 同様の状況は、以前にコミュニティで議論されました。以下のコミュニティスレッドを見て、そこで提供された解決策が役に立ったかどうか教えてください。 Windows 11 で S32DS V3.6 のインストールが失敗します。 - RomanVR。 日時:S32_Design_Studio_for_S32_Platform_3.6.0のインストール中にエラーが発生しました ありがとう、でも 私はこれを何度か試しました。licfixを使用してライセンスを削除してから、インストールを実行し、転記エラーを避けるために電子メールから直接アクティベーションコードをコピーします。結果は常に同じです (添付資料を参照)。奇妙なことに、同じコードを使用して、別の古いコンピューター(Windows 7を実行)にStudioを問題なく正常にインストールしました。インストールに失敗したコンピュータには、すでにS32 Design Studio for Armと他のソフトウェア(MUXpresso、FreeMaster)がインストールされています。 よろしくお願いいたします。 リチャード 日時:S32_Design_Studio_for_S32_Platform_3.6.0のインストール中にエラーが発生しました こんにちは@rick1964  管理者権限でS32DSインストーラーを実行し、アクティベーションコードにタイプミスがないことを確認してください。このエラーは、通常、ユーザー権限の制限が原因です。 これがお役に立てるかどうか教えてください。 - RomanVR。
記事全体を表示
異なるHSEサブシステム間の違い みなさん HSEサブシステムのHSE_H、HSE_M、HSE_Bの違いは何ですか? 違いは彼らがどのボードで動作するかだけですか、それとも機能的な違いもありますか? ご回答をよろしくお願い申し上げます。 Re:異なるHSEサブシステム間の違い こんにちは@VaneB 迅速な対応をしていただきありがとうございました。 残念ながら、これは私の質問の最初の部分にしか答えていません。 しかし、機能的な違いがあるのか、それとも機能が同一なのかということにも興味があります。ここで詳細な答えを期待しているわけではありませんが、はいまたはいいえで答えることは許されていると思います 🙂 Base、Medium、Highともおっしゃっていましたが、これはセキュリティ評価を指していると考えてよいですか? 言い換えれば、セキュリティレベルの高いプロジェクトがある場合、S32K3XXは使用できず、たとえばS32G2を使用する必要がありますか? 敬具 ジョマ
記事全体を表示
安装 S32_Design_Studio_for_S32_Platform_3.6.0 时出错 我无法为S32平台3.6.0安装S32设计工作室在 Windows 10 Pro 上。 安装日志中有一个错误条目: S32 Design Studio for S32 Platform 3.6.0(安装所有卸载程序组件) 状态:错误 附加说明:错误 - 写入 LaunchAnywhere 组件时出错(访问被拒绝) 我的激活码有问题。 无论我使用在线还是离线注册,结果总是一样的:安装过程在验证许可证时停止并结束。 有解决办法吗? 谢谢! 理查德 回复:安装 S32_Design_Studio_for_S32_Platform_3.6.0 时出错   最后发现问题要么出在 Windows 上,要么出在所使用的安装软件 InstallAnywhere 上。我的Windows主盘C盘只有大约11GB的可用空间,所以我计划将软件安装在容量足够的D盘上。但是,S32 Design Studio 在安装过程中需要大约 12.5GB 的空间来存储临时文件。当我启动安装程序S32DS_3.6.0_win32.x86_64.exe时,出现错误信息(附捷克语截图): “没有足够的空间来完成整个安装。请选择一个临时文件夹来放置安装程序。” 于是,我选择了D盘上的一个文件夹,但是安装总是以上面描述的错误结束。最后,释放 C 盘空间有所帮助——在我释放了 C 盘上总共 13GB 的空间后,安装按预期进行。 问题解决了。 谢谢, 理查德 回复:安装 S32_Design_Studio_for_S32_Platform_3.6.0 时出错 你好@rick1964 。 类似的情况之前在社区里也讨论过。请查看下面的社区主题,并让我知道其中提供的解决方案是否对您有帮助。 S32DS V3.6 在 Windows 11 上安装失败。 -RomanVR。 回复:安装 S32_Design_Studio_for_S32_Platform_3.6.0 时出错 谢谢,但是 我已经尝试过几次了。我使用 licfix 删除许可证,然后运行安装并直接从电子邮件中复制激活码,以避免任何转录错误。结果总是一样的(见附件)。奇怪的是,我使用相同的代码在另一台旧计算机(运行 Windows 7)上成功安装了 Studio,没有任何问题。在安装失败的电脑上,我已经安装了 S32 Design Studio for Arm,以及其他软件(MUXpresso、FreeMaster)。” 顺祝商祺! 理查德 回复:安装 S32_Design_Studio_for_S32_Platform_3.6.0 时出错 你好@rick1964 请尝试以管理员权限运行 S32DS 安装程序,并确保激活码没有拼写错误。这个错误一般是由于用户权限限制导致的。 如果这有帮助,请告诉我。 -RomanVR。
記事全体を表示
LINFlexd in UART mode with eDMA Hi, I configured LinFlexD to UART mode and set up DMA channel 0 for transmission, but it triggered a Destination Bus Error. I'm not sure how to resolve this issue. The code as follow. is something i missed?       LINFLEX_3.LINCR1.B.INIT    = 1;            LINFLEX_3.LINCR1.B.SLEEP   = 0;            LINFLEX_3.LINCR1.B.BF      = 0;           LINFLEX_3.UARTCR.B.UART    = 1;            LINFLEX_3.UARTCR.B.RXEN    = 1;            LINFLEX_3.UARTCR.B.TXEN    = 1;            LINFLEX_3.UARTCR.B.WL0     = 1;            LINFLEX_3.UARTCR.B.PC0     = 1;            LINFLEX_3.UARTCR.B.PCE     = 0;            LINFLEX_3.UARTCR.B.TFBM    = 1;             // LINFLEX_3.UARTCR.B.RFBM    = 1;              LINFLEX_3.LINIBRR.B.DIV_M  = 20 * 10000 / 96 / 16;     // 250k // Baud Rate = 9600, In Case fperi1 = 80 MHz     LINFLEX_3.LINFBRR.B.DIV_F  = 0;      // 7 // Baud Rate = 9600, In Case fperi1 = 80 MHz     LINFLEX_3.LINIER.B.DRIE    = 1;            LINFLEX_3.UARTSR.B.DRFRFE  = 1;       // Clear Data Reception Completed Flag     LINFLEX_3.UARTSR.B.DTFTFF  = 1;       // Clear Data Transmission Completed Flag     LINFLEX_3.LINCR1.B.INIT    = 0;       // Normal Mode     LINFLEX_3.DMATXE.B.DTE0 = 1;     // LINFLEX_3.DMARXE.B.DRE0 = 1;       DMAMUX_0.CHCONFIG[0].R = 0xA5;     // DMAMUX_0.CHCONFIG[1].B.ENBL = 1;    // channel 1 uart rx     // DMAMUX_0.CHCONFIG[1].B.TRIG = 0;     // DMAMUX_0.CHCONFIG[1].B.SOURCE = 0x26;     EDMA_0.TCD[0].CITER = 0x8;     EDMA_0.TCD[0].BITER = 0x8;     EDMA_0.TCD[0].NBYTES = 0x1;     EDMA_0.TCD[0].SADDR = (uint32)&lin3_tx_buffer[0];     EDMA_0.TCD[0].SOFF = 0x1;     EDMA_0.TCD[0].SSIZE = 0;     EDMA_0.TCD[0].SLAST = 0xFFFFFFFFFFFFFFF8;     EDMA_0.TCD[0].DADDR =  (uint32)(&LINFLEX_3.BDRL) + 3;     EDMA_0.TCD[0].DOFF = 0;     EDMA_0.TCD[0].DSIZE = 0;     EDMA_0.TCD[0].D_REQ = 1;     EDMA_0.TCD[0].INT_MAJ = 1;     EDMA_0.DMAERQL.B.ERQ00 = 1;   There are a few more questions. 1. If I want to periodically send 30 bytes of data in a 20ms task, how do I control the sending and stopping of DMA? Can I enable it during the 20ms task by EDMA_0.DMAERQL.B.ERQ00 = 1; and disable it during the DMA completion interrupt by EDMA_0.DMAERQL.B.ERQ00 = 0?  In another words, how should i restart the DMA periodically in 20ms task or i dont have to do that manually?    2. When LINFlexD is in UART FIFO mode (TFBM = 1),how many bytes are there in BDR? The manual says there is only one byte, is it true? if it is, why call it a FIFO? should't it be 4 bytes.   3. When there is a Destination Bus Error, you can see that the Citer has been decreasing. Why is this? Shouldn't it stop the DMA transmission? I'm sure no signal is coming out of the serial port, so who gives the DMA request?   thanks Re: LINFlexd in UART mode with eDMA   1) Setup certain timer for 20ms and after its expiration set START bit of particular DMA TCD. 2) You haven't specified used device. MPC5643L has is as follows, other may have it differently.   3) Yes, bus error stops transmission. If triggered again, it apparently continues.
記事全体を表示
FRDM-MCXN947 无法使用配置工具修改 led_blinky 示例项目中使用的 LED。 我正在尝试遵循本教程,其中解释了如何使用 VSCode 的配置工具。( https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con... ) 以下是快速重现我所遇到的问题的方法: 1. 安装 VS Code、MCUXpresso 扩展和 MCXN947 板的 SDK。(我在英特尔 iMac 上运行它。) 2. 导入、构建并运行 led_blinky 示例项目。这很好用。 3. 在 VSCode 中,右键单击 led_blinky 并开始使用配置工具。 4. 配置工具一打开就报告时钟和引脚中存在许多错误。(大约 20 个错误)。我是 NXP、MCUXpresso 和 VSCode 的新手,所以我不知道如何继续。 我在网上搜索了我遇到的错误,但没有找到任何有用的信息。 感谢您的帮助! 此外,MCUXpresso VS Code 扩展也给我留下了深刻的印象。你们太棒了!而且我很确定,一旦我更好地了解配置工具,我也会说同样的话。 回复:FRDM-MCXN947 无法使用配置工具修改 led_blinky 示例项目中使用的 LED。 嗯,这次成功了。您将看到上面的屏幕截图。 我确实看到您的配置概述没有显示我收到的错误。我希望我的概览屏幕看起来像你的一样! 我不知道如何确认配置工具是否安装成功。据我所知,它似乎正在发挥作用。我确实得到了一个与您的类似的配置工具概览屏幕,但仍然存在很多差异。我希望当您看到配置工具概览屏幕之间的差异时,它将帮助您确定出了什么问题。同时,我将卸载我的配置工具程序并从您的网站重新安装它。 回复:FRDM-MCXN947 无法使用配置工具修改 led_blinky 示例项目中使用的 LED。 我添加了几个屏幕截图。我在每个屏幕截图上标记了与错误相关的各个区域。 显示两种类型的错误。 1.设备配置错误似乎表明配置工具不支持 MCNX947 上使用的处理器。我想我误解了这个错误的含义。 2. 缺少驱动程序错误。我在我的 SDK 仓库中找不到这些驱动程序。也许这些文件名(COMMON、PORTR、CLOCK 等)是通用名称而不是实际文件名。如果是这样的话,我不知道如何找到实际的文件名,也不清楚如何使用 VS Code 或配置工具将驱动程序添加到项目中。
記事全体を表示
BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. Hello,  I am trying to run program in RAM section . I build simple sieve code using S32 design studio with build setting as Debug_RAM. when I debug using PEmicro debugger it works fine , there are no errors. but If I use same elf and program it using Lauterbach script  "s32k344cvd-q257_sieve_sram.cmm" it throws bus error "bus error at EST:0x2043000--0x204310CF".  note: with example elf file provided by Lauterbach, script "s32k344cvd-q257_sieve_sram.cmm" works perfectly fine. What setting I am missing in S32_studio ? Are any changes need to do in linker manually? S32K344-WB  Thanks in advance!! Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. Hi, @davidtosenovjan  Initializing whole RAM in init_ram.cmm script resolved my issue.  Thank you so much. Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. The script 'init_sram.cmm' initialized address range 0x20400000-0x20427FFF i.e. 160kB i.e. only half of SRAM memory of S32K344.init_sram.cmm That's the reason probably Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. Hi, attached Lauterbach scripts I am using. Re: BUS error while programming S32K344 using Lauterbach debugger utrace in RAM section. This is rather question to Lauterbach. Could you share mentioned script?
記事全体を表示
FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. I am attempting to follow this tutorial which explains how to use the Config tool with VSCode. . (https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con...)  Here' is how to quickly reproduce the problem I am having: 1. Install VS Code, the MCUXpresso extension, and the SDK for the MCXN947 board. (I'm running it on an intel iMac.)  2. Import, built, and run the led_blinky example project. This works fine.  3. From VSCode, right click on led_blinky and start using the config tool. 4. As soon as it opens, the Config tool is reporting many errors in Clocks and Pins. (around 20 errors). I'm new with NXP, MCUXpresso, and VSCode so I don't know how to proceed.  I've searched the web for the errors I'm getting and haven't found anything useful. Thank you for your help! Also, I am very impressed with the MCUXpresso VS Code extension. You guys rock! And I'm pretty sure I will say the same thing about the Config tool once I learn it better.  Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  Congratulations! The repo you advised me to obtain does not show any Config errors! Thank you for spending as much time as you did to help me with this problem!  Is it always best to obtain archives from the SDK builder rather than Github? I'm pretty sure the IDE recommended Github. Perhaps it should recommend the SDK builder.  Now I've got a lot to learn about how to use the Config tool. Right now It's pretty confusing to me. I've no doubt I'll figure it out pretty quickly now that you've solved this problem.. Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Hello @ClarkS , Thanks for your information. I have tried the Config Tools v24.12. The problem you mentioned still hasn't occurred. However, I've found that the SDKs we're using are indeed different. You're using the one from GitHub, while mine is from a local repository. I tried using the one from GitHub, but I keep failing to import it. So, I'm wondering if you could try the method of local import to see if it works. 1. Download the 24.12 SDK from Select Board | MCUXpresso SDK Builder 2. After the download is completed, place the SDK in the created directory C:\MCUXpresso_for_vscode.  3. Select the "LOCAL ARCHIVE" method to import the repository.   Choose "Import Repository" -> "LOCAL ARCHIVE" -> "Archive" -> "Browse", then locate the SDK folder downloaded from the SDK Builder. Select the built "SDK_24_12_00_FRDM - MCXN947".  4. Create a new empty folder and name it "MCXN947". Click "Destination" -> "Browse" and select the newly created "MCXN947" folder. Then click "Import", and the SDK will be automatically imported. 5. Click "Import Example from Repository" to import the project "led_blinky" and create a new project.   Hope it can help you. BRs, Celeste Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  We have different versions of Config Tools.  I have 24.12. You have 16.1.  I got mine from here: https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-config-tools-pins-clocks-and-peripherals:MCUXpresso-Config-Tools  Would you be able to test with the later version?  My SDK is 24.12.10. You have both SDK: 24_12_00 and SDK_2_16_100. When I import my repo for the MCXN947 board I see these two choices. What's the difference between the two.? Which one should I select? I'm pretty sure I picked the 2nd one.  Here is another view of my configuration.  Thank you for your help! Clark Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Hello ClarkS, On my end, there was indeed a version warning, but after I closed it, I didn't encounter any problems. Let me list the versions of my tests: Config Tools: v16.1 SDK: 24_12_00, SDK_2_16_100 I've tried the led_blinky in both versions of the SDK, and there were no issues. BRs, Celeste Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  I deleted my Config Tools app, downloaded a new copy from your web site, deleted my led_blinky example, re-imported it from my repo, and relaunched the new copy of Config Tools. It still shows the errors.  I did notice that the errors do not appear until I acknowledge a warning message complaining about the version of the configuration. I will attach two screen shots, the first one showing the warning message, and the second showing the next screen shot. Do you get the version warning? If not, what would explain that? Are we using different led_blinky versions? Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Well, this time it worked. You will see the screenshots above.  I do see that your Configuration Overview does not show the errors that I am getting. I wish my Overview screen looked like yours does! I don't know how to confirm Config tools is successfully installed. As far as I can tell, it appears to be working. I do get a Config Tools Overview screen which is similar to yours, but there are still a lot of difference. I hope when you see the differences between the Config Tools Overview screens, it will help you determine what is going wrong. In the mean time, I will uninstall my Config Tools program and reinstall it from your web site.  Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. @Celeste_Liu  I'm having trouble adding the screen shots. Whenever I do I get an error message below the CAPTCHA that says that verification failed.  Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. Hello @ClarkS , Thank you for your interest in our products. I have tried it on my end, but I haven't reproduced your problem. The configuration tools can be opened normally. I have checked the Quick Start Guide of the MCUXpresso configuration tools and found that it supports iMac. Could you please confirm whether you have successfully installed the MCUXpresso configuration tools on your Intel iMac? You can also send me a screenshot of the error message that appears when you try to open it. BRs, Celeste Re: FRDM-MCXN947 Can't use Config tool to modify LED used in led_blinky example project. I've added a couple screen shots. I've marked the various error related areas on each screen shot.  Two types of errors are shown. 1. The Device Configuration error which seems to say the Config tool does not support the processor used on the MCNX947. I think I misunderstand the meaning of this error. 2. Missing driver errors.  I cannot find those drivers in my SDK repo. Maybe those file names (COMMON, PORTR, CLOCK, etc) are generic names and not actual file names. If that is the case, I have no idea how to find the actual file name, nor is it clear to me how to add drivers to the project using VS Code or the Config tool.  
記事全体を表示
FRDM-MCXN947 Config ツールを使用して、サンプル プロジェクトで使用されている LED を変更できませんled_blinky VSCodeでConfigツールを使用する方法を説明するこのチュートリアルに従うことを試みています。.(https://community.nxp.com/t5/MCUXpresso-Training-Hub/MCUXpresso-for-VS-Code-Getting-started-with-Con...) ここで'私が抱えている問題を迅速に再現する方法は次のとおりです。 1. VS Code、MCUXpresso 拡張機能、および MCXN947 ボードの SDK をインストールします。(私はそれをIntel iMacで実行しています。 2. led_blinky サンプル プロジェクトをインポートし、ビルドして実行します。これは正常に動作します。 3. VSCodeから、led_blinkyを右クリックして、構成ツールの使用を開始します。 4. Configツールが開くとすぐに、クロックとピンに多くのエラーが報告されます。(約20エラー)。私はNXP、MCUXpresso、およびVSCodeを初めて使用するので、どのように進めればよいかわかりません。 私は私が得ているエラーのためにウェブを検索しましたが、有用なものは何も見つかりませんでした。 ご協力いただきありがとうございます! また、MCUXpresso VS Code拡張機能にも非常に感銘を受けました。あなたたちは最高です!そして、Configツールについてもっとよく学んだら、同じことを言うと確信しています。 Re: FRDM-MCXN947 Config ツールを使用して、サンプル プロジェクトで使用されている LED を変更できませんled_blinky さて、今回はうまくいきました。上のスクリーンショットが表示されます。 構成の概要には、発生しているエラーが表示されていないことがわかります。私の概要画面があなたの画面のように見えたらいいのにと思います! Configツールが正常にインストールされたことを確認する方法がわかりません。私が知る限り、それは機能しているようです。あなたのものと同様の構成ツールの概要画面が表示されますが、それでも多くの違いがあります。Config Tools Overview画面の違いを確認すると、何が問題になっているのかを判断するのに役立つことを願っています。それまでの間、私は私のConfigToolsプログラムをアンインストールし、あなたのWebサイトから再インストールします。 Re: FRDM-MCXN947 Config ツールを使用して、サンプル プロジェクトで使用されている LED を変更できませんled_blinky スクリーンショットをいくつか追加しました。各スクリーンショットでさまざまなエラー関連領域をマークしました。 2 種類のエラーが表示されます。 1.デバイス構成エラーは、構成ツールがMCNX947で使用されているプロセッサをサポートしていないことを示しているようです。私はこのエラーの意味を誤解していると思います。 2.ドライバーのエラーがありません。SDK リポジトリでこれらのドライバーが見つかりません。もしかしたら、これらのファイル名 (COMMON、PORTR、CLOCK など) は一般的な名前であり、実際のファイル名ではないかもしれません。その場合、実際のファイル名を見つける方法がわからず、VSCodeまたはConfigツールを使用してプロジェクトにドライバーを追加する方法も明確ではありません。
記事全体を表示
UJA1164 SBC芯片/Can收发器配置 我对 UJA1164 SBC 芯片有疑问。我正在通过 SPI 与 SBC 通信。我正在尝试设置一些具有特定值的寄存器,但这些值并未写入寄存器中。配置收发器是否应遵循特定的程序?有这个的演示代码吗? 回复:UJA1164 SBC芯片/CAN收发器配置 在案例 # 00655722 中进行了内部答复。  
記事全体を表示
Is it possible to write any data to UTest area in SystemInit for S32K312 Hi I want to write any data to UTest Area(for example : 0x1b000060) in SystemInit. is it possible? Re: Is it possible to write any data to UTest area in SystemInit for S32K312 This issue is resolved. Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hello, Security (HSE) topics are not discussed on public community. Please submit a ticket at NXP.com for support on such theme. Best regards, Peter Re: Is it possible to write any data to UTest area in SystemInit for S32K312 The attached file is the firmware to install hse firmware Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hi. I make SHERPA_HSE_INSTALL_S32K312.sre file to install hse binary(s32k3x2_hse_fw_0.13.0_2.6.0_pb221129.bin.pink). and Power off and on runs after I download this file. But HSE Enable flag does not written to 0x1b000000. Could you please let me know what is problem? Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hello, Is it possible to write the attached file to 0x1b000000 using MCU Programming Tool like FR-Cube There is no restriction o n programming UTEST. It is just a normal flash which is set as OTP in NXP factory. Follow the procedure described in reference manual for UTEST programming. chapter 21.3 UTest NVM sector MCU Programming Tool like FR-Cube without running code for hse enable? Unfortunate I do not know your FR-Cube tool. Please consult such with your tool vendor. Best regards, Peter Re: Is it possible to write any data to UTest area in SystemInit for S32K312 In additional,  Is it possible to write the attached file to 0x1b000000 using MCU Programming Tool like FR-Cube without running code for hse enable? BRs. Hyunung Park  Re: Is it possible to write any data to UTest area in SystemInit for S32K312 Hello, In these areas you can store you information. make sure in case you are using UTEST DCF Start or Records, to store your data after 0xFFFF_FFFF_FFFF_FFFF space from your DCf data. Also be aware that storing data after stop record will leave you will no possibility to add additional DCF records. So leave enough space. Best regards, Peter
記事全体を表示