VR5510 收到待机请求后重启 大家好， 我使用vr5510和s32g2。 FS状态为NORMAL_FS，FLT_ERR_CNT为0，主状态机处于正常模式。 我将vr5510的STBY_TIMER_EN和TIMING_WINDOW_STDBY配置为零。vr5510的待机看门狗已关闭。I2C请求和STBY引脚请求的时间限制也已关闭。 然后我将STBY_REQ 配置为 1 并拉低 STBY 引脚。 100ms后，VR5510将拉低PGOOD、RESET_B和STBY_PGOOD。 这意味着vr5510不会进入待机模式，而是重新启动。 我该如何解决这个问题？

pfe slave test steps based on BSP41 Hi, Recently, I tested pfe master/slave feature, but it seems the test steps have changed, but I did not find related description documents in pfeng repo or the firmware docs. Would you please help to check the issue and give the steps how to test pfe master/slave feature and where I can get them? Thanks, Zhantao Re: pfe slave test steps based on BSP41 Hi, We apologize for the delay from our side. We have received the following update: " Customer could download the "PFE_S32G_A53_LNX_UserManual.pdf" from the page of S32G BSP download, for example: After download “PFE-DRV_S32G_A53_LNX_1.7.0_DOC.zip” and extract it, then you will get the  "PFE_S32G_A53_LNX_UserManual.pdf". " Please, let us know. Re: pfe slave test steps based on BSP41 Hi, Thanks for your feedback. It does seem to be that the latest user manual was published under v1.5.0. We will confirm with the related team the reason for this and if it is available at this moment. We apologize for any delay from our side. Please, let us know. Re: pfe slave test steps based on BSP41 Hi @Daniel-Aguirre, I used RDB3 v1.1 SOC for test, and I followed the steps in section "2.5.5 Runtime" of doc: "PFE_S32G_A53_LNX_UserManual.pdf", which is from the previous pfe branch, like v1.4.0, but now these .pdf files are all removed from the v1.7.0 branch. So I don't know where can get the new steps for pfe master/slave mode. Thanks, Zhantao Re: pfe slave test steps based on BSP41 Hi, Can you let us know which documents you have read? Also, which steps are you following? Can you let us know which S32G variant you are using? Please, let us know.

ld: -lcr_newlib_nohost が見つかりません i.MX 1170 EVKを使用していますが、MCUXpresso SDK v2.15およびv2.16のすべてのプロジェクトが次のエラーでビルドに失敗します。私はApple M1 MaxとVSCode 1.91.1を使用しています。 > ld: 見つからない -lcr_newlib_nohost: そのようなファイルまたはディレクトリはありません 私は以下のARM GCCツールチェーンを使用しています。 > arm-gnu-toolchain-13.2.Rel1-darwin-x86_64-arm-none-eabi MCUXpresso IDEを使用したとき、コンパイルに問題はありません。 リンク先がlibcrツールを見つけられないと思いますが、どこに配置すべきか、どのようにインストールするかを判断できません。 Re: ld: -lcr_newlib_nohost が見つかりません 数人の同僚と私は問題を再現しました。私の推測では、M1(IntelではなくARM)のMac OSインストールに関連していると思います。 VSCode プラグインに付属するツールチェーンが正しく動作しません。これは .mcuxpressotools/arm-gnu-toolchain にあります.....注は、Arm GNU Toolchain 13.2.rel1 と呼ばれています。 プロジェクトをコンパイルするには、'armgcc\debug\build.ninja' から '-lcr_newlib_nohost' フラグを削除します。 または、MCUXpresso IDE をインストールし、インストールするツールチェーンを選択することもできます。/Applications/MCUXpressoIDExxx/ide/tools にあります。2 つのツールチェーンの名前とバージョンは、バージョン 13.2.1 20231009まで同じであることに注意してください。しかし、彼らは非常に異なる動作をします。 回复: ld: cannot find -lcr_newlib_nohost @joscIDEの最新バージョンにはGCC 13.2が含まれており、リリースノートはこちらにある。 https://www.nxp.com/docs/en/release-note/MCUXpresso-RN.pdf  NXPは、ツールチェーンとライブラリの独自のビルドを行う可能性がありますか? お役に立てれば幸いです。 よろしくお願いします、デイブ

VR5510 stdbyリクエスト受信時に再起動 皆さん、こんにちは 私はvr5510とs32g2を使用しています。 FS ステータスは NORMAL_FS、FLT_ERR_CNT は 0、メイン ステート マシンは通常モードです。 vr5510のSTBY_TIMER_ENとTIMING_WINDOW_STDBYをゼロに設定しました。vr5510のスタンバイウォッチドッグが閉じています。I2CリクエストとSTBYピンリクエストの時間制限もクローズされます。 次に、 STBY_REQを1に構成し、STBYピンをローにプルダウンします。 100ms後、VR5510はPGOOD、RESET_B、およびSTBY_PGOODをプルダウンします。 これは、vr5510がスタンバイモードに入らず、再起動することを意味します。 この問題を解決するにはどうすればよいですか?

ld: 找不到 -lcr_newlib_nohost 我有一个 i.MX 1170 EVK，并且来自 MCUXpresso SDK v2.15 和 v2.16 的所有项目都无法构建，并出现以下错误。我正在使用 Apple M1 Max 和 VSCode 1.91.1。 > ld: 找不到 -lcr_newlib_nohost: 没有此文件或目录 我正在使用下面的 ARM GCC 工具链。 > arm-gnu-toolchain-13.2.Rel1-darwin-x86_64-arm-none-eabi 当我使用 MCUXpresso IDE 时，我没有遇到任何编译问题。 我认为链接找不到 libcr 工具，但我无法确定它应该位于何处或如何安装它。 回复：ld：找不到-lcr_newlib_nohost 我和几个同事重复了这个问题。我猜测它与 M1（ARM 而非英特尔）的 Mac OS 安装有关。 VSCode插件自带的工具链无法正常工作。它位于.mcuxpressotools/arm-gnu-toolchain.....注意它被称为 Arm GNU Toolchain 13.2.rel1。 您可以通过从“armgcc\debug\build.ninja”中删除“-lcr_newlib_nohost”标志来编译项目。 或者您可以安装 MCUXpresso IDE 并选择它安装的工具链。它位于 /Applications/MCUXpressoIDExxx/ide/tools 下。请注意，这两个工具链具有相同的名称和版本，直至版本 13.2.1 20231009。但他们的行为却截然不同。 回复： ld: 找不到-lcr_newlib_nohost @josc根据此处的发行说明，最新版本的 IDE 包含 GCC 13.2： https://www.nxp.com/docs/en/release-note/MCUXpresso-RN.pdf NXP 可能自己构建了工具链和库？？ 希望有帮助！ 谨致问候，戴夫

VR5510 restart when receive stdby request Hi all, I use vr5510 and s32g2. The FS status is NORMAL_FS, the FLT_ERR_CNT is 0, and the Main state machine is in normal mode. I config the STBY_TIMER_EN and TIMING_WINDOW_STDBY of vr5510 to zero. The standby watchdog of vr5510 is closed. The time limit of I2C request and STBY pin request is also closed. Then I config the STBY_REQ to 1 and pull low the STBY pin. After 100ms, VR5510 will pull down PGOOD, RESET_B and STBY_PGOOD. This means vr5510 does not enter standby mode, but restart. How should I solve this problem? Re: VR5510 restart when receive stdby request Hi Brian, Have you resolved your issue? Recently I am trying to set the VR5510 to standby mode by S32G399 too. I have the same configuration as yours and when i set the STBY_REQ high via I2C, PMIC reset happens.  Hope you can give me some advice. Looking forward to your reply, thanks. Yang Re: VR5510 restart when receive stdby request Hi Jozef, thanks for your kindly replay, I'll follow your suggestion and see the result. thanks again. Re: VR5510 restart when receive stdby request Hi Brian, please note, that entering Standby mode is not possible in Debug mode. Please make sure that you are not in Debug mode. Either by connecting the VDDOTP to GND or writing DBG_EXIT bit = 1. To disable the Stanby timer it is sufficient to set the STBY_TIMER_EN to 0. By setting the TIMER_STBY_WINDOW [3:0] to 0x0000, you have set it to 16ms. Please try to set there some different value to see if the restart will happen again in 100ms or after longer time value. Please try e.g. 0x0110. This will set the TIMER_STBY_WINDOW [3:0] to 8192ms=8.2s.  With Best Regards, Jozef

ld: cannot find -lcr_newlib_nohost I have an i.MX 1170 EVK and all the projects from the MCUXpresso SDK v2.15 and v2.16 fail to build with the following error. I'm using an Apple M1 Max and VSCode 1.91.1. > ld: cannot find -lcr_newlib_nohost: No such file or directory I'm using the ARM GCC tool chain below. > arm-gnu-toolchain-13.2.Rel1-darwin-x86_64-arm-none-eabi When I used the MCUXpresso IDE I don't have any issues compiling. I assume the linked can't find the libcr tool but I can't determine where it should be located or how to install it. Re: ld: cannot find -lcr_newlib_nohost A couple colleagues and I replicated the issue. My guess is it is related to the Mac OS installations for the M1 (ARM not intel). The tool chain that comes with the VSCode plug-in doesn't work properly. It's located in .mcuxpressotools/arm-gnu-toolchain..... Note is is called the Arm GNU Toolchain 13.2.rel1. You can get the project to compile by removing the `-lcr_newlib_nohost` flag from `armgcc\debug\build.ninja`. Or you can install the MCUXpresso IDE and select the toolchain that it installs. It's under /Applications/MCUXpressoIDExxx/ide/tools. Note the two toolchains have identical names and versions right down to the version 13.2.1 20231009. But they behave very differently. 回复： ld: cannot find -lcr_newlib_nohost @joscLatest version of IDE includes GCC 13.2, according to release notes here: https://www.nxp.com/docs/en/release-note/MCUXpresso-RN.pdf  NXP likely does their own build of the toolchain and libraries?? Hope that helps! Best Regards, Dave 回复： ld: cannot find -lcr_newlib_nohost Hi all, I also got the same error with the new ARM GNU Toolchain. It simply seems like that there is no libcr_newlib_nohost file. It is only available when I use the Toolchain which the MCUXpresso Installer provides. So, where does this file come from? How can I update to the newest version of the ARM GNU Toolchain? Because, as far as I know, the newest arm-none-eabi version provided by the MCUXpresso Installer is version 12.3 and not 13.3. Best Regards, Johannes 回复： ld: cannot find -lcr_newlib_nohost Hi @daniel_fudge , Thanks for your interest in NXP MIMXRT series! Have you ever compiled successfully with Vscode? Or never succeeded? Since we don't have a MAC test machine locally, we can't fully reproduce your problem. Just a guess, maybe your Mcuxpresso_for_Vscode development environment didn't get configured successfully. Normally, libcr_newlib_nohost.a should be under the folder where the compiler can find it. For my Windows test environment, it exists here: Best regards, Gavin

GUI for N-AFE could be used with other vendor's MCU? Hello, We're considering to apply NAFE13388 into I/O Module project. NXP offers GUI to configure N-AFE. I'd like to know if GUI for N-AFE works with only NXP MCU or If it could work with other vendor's MCU as well. Thank you. Best regards, Andy Re: GUI for N-AFE could be used with other vendor's MCU? Hi  Don't suggest to select other vendor for this GUI setup.

Interrupt on Receiving CAN FD S32k144 Hi, i would ask if there's any example for CAN FD Interrupt without SDK. I've configured IMASK1, is there anything else I must do? I tested it with canoe and send a CAN FD Message. But it says Tx Error (Bit Error and NAK Error) Hope anyone can help Sandra Re: Interrupt on Receiving CAN FD S32k144 Hi@Sandra1 I made a demo base on "S32K144_Project_CanFd" which is provided in S32 DS For Arm V2.2. 1.set MB4 interrupt mask in FLEXCAN0_init() CAN0->IMASK1 |= CAN_IMASK1_BUF31TO0M(1 << 4);/*Enable MB 4 interrupt mask*/ 2.Set NVIC and install  CAN0 IRQ Handler void NVIC_init_IRQs (void) { S32_NVIC->ICPR[2] = 1 << (CAN0_ORed_0_15_MB_IRQn % 32); S32_NVIC->ISER[2] = 1 << (CAN0_ORed_0_15_MB_IRQn % 32); S32_NVIC->IP[CAN0_ORed_0_15_MB_IRQn] = 0xA0; } void CAN0_ORed_0_15_MB_IRQHandler(void) { if ((CAN0->IFLAG1 >> 4) & 1) { /* If CAN 0 MB 4 flag is set (received msg), read MB4 */ FLEXCAN0_receive_msg(); /* Read message */ rx_msg_count++; /* Increment receive msg counter */ if (rx_msg_count == 10) { /* If 1000 messages have been received, */ PTD->PTOR |= 1<<16; /* toggle output port D16 (Green LED) */ rx_msg_count = 0; /* and reset message counter */ } FLEXCAN0_transmit_msg(); /* Transmit message using MB0 */ } }

88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Platform (Host CPU): i.mx8mm EVK OS: Tried Linux 6.1.22_2.0.0 and Linux 5.15.71_2.2.1 HW: i.mx8mm EVK + WiFi module: AW-CM276MA-PUR (M.2) BSP version: Linux 6.1.22_2.0.0 & 5.15.71_2.2.1 Driver version and Wi-Fi and Bluetooth/Bluetooth LE Firmware version: PCIE8997--16.92.21.p55.3-MM5X16366.p5-GPL-(FP92) and PCIE8997--16.92.21.p84.4-MM5X16391.p3-GPL-(FP92)    0. HW or SW/FW issue? should be FW or SW 1. Environment: In shielding room or open site? shielding  and also can check in open site. 2. Issue description: Do throughput iperf3 test with AX200 Notebook and AX210 desktop Check RX speed is too slow is around 300-400Mbps TX speed is ok >550Mbps. RX(i.mx8mm side: iperf3 -s; AX2x0 side: iperf3 -c [ip add.] ) 3. Setup: Bring up WiFi then do iperf3 test. 4. Steps to reproduce on NXP EVK: (attached config.zip) modprobe moal mod_para=nxp/wifi_mod_para.conf touch /var/lib/misc/udcpd.leases ifconfig uap0 192.168.1.2 netmask 255.255.255.0 up route add default gw 192.168.1.1 udhcpd /etc/udhcpd.conf hostapd /etc/hostapd-5g.conf -B iperf3 -s -i1 (RX) AX200 side: iperf3 -c 192.168.1.2 -w2M -P8 -fm -i1 -t60 round side test TX: iperf3 -c 192.168.1.2 -w2M -P8 -fm -i1 -t60 -R Note: Compared different test device. if use Samsung S23, there is no RX speed issue. both RX: >550Mbps, TX:>550Mbps. Please help to check if its compatibility issue and if its possible to solve on 88W8997 side. Thanks. 5. Observation: its only 4xx Mbps (Target: >550Mbps) i.mx8mm: iperf3 -s -i1 PC side (AX200): iperf3 -c 192.168.1.2 -w2M -P8 -fm -i1 -t60 6. Fail Rate: 100% 7. Additional dmesg/logcat/OTA sniffer logs, FW coredump, RF tester logs…: Please comment which logs needed, it can be easily reproduced. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi @Christine_Li  From customer's note: === This hostapd config file, when used in the shielding room for iperf3 testing, can achieve both Tx and Rx speeds up to 600Mbps. If there are any further issues, I will update you. ==== Thanks. for support. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi, @yao_feng  Do you get any chance to see whether have improvements with my provided hostapd.conf and test in shield room? Please let me know whether have anything I can do for you on this case. Best regards, Christine. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi, @yao_feng  Can you please help to try with attached hostapd.conf file to see whether have any improvement? The test result on my side, it has improvements with my attached hostapd.conf. Also, for you information, our data in the Release Note is tested in shield room. So please also test it in shield room to make sure we are on one page. Besides, you can also change country code US to CN, or change to different channel such as 36 to see whether have any difference. Best regards, Christine. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi, @yao_feng  Thanks for your reply. Now I can load 88W8997 driver successfully. I am preparing for start 88W8997 in AP mode. Will keep you posted. Best regards, Christine. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi Christine The issue only happened on uAP mode. please help to check uAP mode. thanks. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi, @yao_feng  I checked our Release Note (L6.6.23 official release), it mentioned that: So, for not only STA mode but also AP mode, 88W8997 could meet you requirement. I have also download our L6.6.23 prebuilt image on I.MX8MM-EVK, and prepare the test environment to start the test. 1.Before my test, may I ask which mode do you prefer 88W8997 work in? STA mode or AP mode? I checked your config files, it mentioned some configurations related to uap0, are you using 88W8997 in AP mode? 2. In default imx8mm-evk.dtb, it doesn't support M.2 interface. So I need to check the schematics and also modify the dts file to use M.2 88W8997 module. To save the porting time, would you mind share to me your dts file? So that I can directly follow your modifications to start my local test. Best regards, Christine. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi, @yao_feng  Thanks for verifying on our latest release. I will also do similar test locally to confirm. Once have any updates, I will let you know. Best regards, Christine. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 update  test on latest BSP and WiFi driver/FW got same result root@imx8mmevk:/lib/firmware/nxp# uname -a Linux imx8mmevk 6.6.23-lts-next-06236-gb586a521770e #1 SMP PREEMPT Fri Jun 7 13:15:57 UTC 2024 aarch64 GNU/Linux root@imx8mmevk:/lib/firmware/nxp# ./mlanutl uap0 version Version string received: PCIE8997--16.92.21.p119.3-MM6X16437.p21-GPL-(FP92) root@imx8mmevk:/lib/firmware/nxp# iperf3 -s -i1 [ ID] Interval Transfer Bitrate [ 5] 0.00-30.08 sec 190 MBytes 53.1 Mbits/sec receiver [ 8] 0.00-30.08 sec 190 MBytes 53.1 Mbits/sec receiver [ 10] 0.00-30.08 sec 189 MBytes 52.7 Mbits/sec receiver [ 12] 0.00-30.08 sec 189 MBytes 52.7 Mbits/sec receiver [ 14] 0.00-30.08 sec 190 MBytes 52.9 Mbits/sec receiver [ 16] 0.00-30.08 sec 190 MBytes 52.8 Mbits/sec receiver [ 18] 0.00-30.08 sec 190 MBytes 52.9 Mbits/sec receiver [ 20] 0.00-30.08 sec 189 MBytes 52.8 Mbits/sec receiver [SUM] 0.00-30.08 sec 1.48 GBytes 423 Mbits/sec receiver Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 Hi, @yao_feng  Thanks for creating case to us. I will check this issue and give you feedback ASAP. Best regards, Christine. Re: 88W8997PCIE module 11ac 80MHz slow Throughput around 300-400Mbps(RX) on i.mx8mm with AX200,210 updated: test latest BSP and driver/FW, got same result root@imx8mmevk:/lib/firmware/nxp# uname -a Linux imx8mmevk 6.6.23-lts-next-06236-gb586a521770e #1 SMP PREEMPT Fri Jun 7 13:15:57 UTC 2024 aarch64 GNU/Linux root@imx8mmevk:/lib/firmware/nxp# ./mlanutl uap0 version Version string received: PCIE8997--16.92.21.p119.3-MM6X16437.p21-GPL-(FP92) root@imx8mmevk:/lib/firmware/nxp# iperf3 -s -i1 [ ID] Interval Transfer Bitrate [ 5] 0.00-30.08 sec 190 MBytes 53.1 Mbits/sec receiver [ 8] 0.00-30.08 sec 190 MBytes 53.1 Mbits/sec receiver [ 10] 0.00-30.08 sec 189 MBytes 52.7 Mbits/sec receiver [ 12] 0.00-30.08 sec 189 MBytes 52.7 Mbits/sec receiver [ 14] 0.00-30.08 sec 190 MBytes 52.9 Mbits/sec receiver [ 16] 0.00-30.08 sec 190 MBytes 52.8 Mbits/sec receiver [ 18] 0.00-30.08 sec 190 MBytes 52.9 Mbits/sec receiver [ 20] 0.00-30.08 sec 189 MBytes 52.8 Mbits/sec receiver [SUM] 0.00-30.08 sec 1.48 GBytes 423 Mbits/sec receiver attached console log and dmesg.

potential bug in fsl_ocotp.c Hi, my micro is RT1175. in file fsl_ocotp.c there is OCOTP_ReadFuseShadowRegisterExt() at the beginning there is an assert to validate the `fuseWords` parameter. I tested that the assert is triggered for fuseWords >= 4 This is confirmed at line 71242 of MIMXRT1175_cm7.h the RT1175 can read 4 words at a time on OCOTP. Therefore, the `fuseWords` parameter should be written OCOTP_READ_CTRL[READ_FUSE_CNTR] in the source code, though, a field named READ_NUM is shown, which does not appear in any document or in any source related to RT1175. I think this is a bug. I tried a possible fix: this works best regards Max Re: potential bug in fsl_ocotp.c Hi @kerryzhou  do you have any news? a new version has been released, but the buggy code is still there. regards Max Re: potential bug in fsl_ocotp.c Hi @mastupristi ,    Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you. I think your report item is reasonable which also consider the Number of words to read. I report this SDK requirement to our SDK team, they will help to fix it in the new version. Thanks a lot for your contribution. If you find any issues of our SDK bug, welcome to report! If your question is solved, please help me to mark the correct answer, just to close this case, thanks. Best Regards, Kerry

[KW45] system assert （OSA_EventSet() at fsl_os_abstraction_free_rtos.c:760 0x14362 ） Hi，  KW45 system assert when i use BleApp_StartScan(); Core and Memory Re: [KW45] system assert （OSA_EventSet() at fsl_os_abstraction_free_rtos.c:760 0x14362 ） Hello,  By any chance, did you make any modification to the code? If you did, could you please help me with more details on what was modified in it  so we can try to reproduce it on our side? Regards, Re: [KW45] system assert （OSA_EventSet() at fsl_os_abstraction_free_rtos.c:760 0x14362 ） SDK Version:2.12.7 example:digital_key_car_anchor_freertos

S32K344 with HSE integration to FreeRTOS Hi all, I started to work with S32K344-EVB and use PEMicro.  Everything (build, flash and debug) works fine without HSE. And I'm trying to integrate HSE FW with FreeRTOS. I added HSE driver from S32 Design Studio IDE: I also downloaded the S32K344 HSE FW 0.2.40.0 SR Release and S32K3 MCUs for General Purpose HSE Demo Examples. I tried the HSE FW Install and Update from the baremetal examples and they worked fine too. HSE FW S32K3 Standard Software → Automotive SW - S32K3 - HSE Firmware → S32K344 HSE FW 0.2.40.0 SR Release HSE examples for PEMicro  S32K3 MCUs for General Purpose HSE Demo Examples  My questions are the followings: Is it possible to integrate HSE FW Install and Update with our FreeRTOS based project in the same software or should I create a separate FW Install/Update software? If the integration is possible what is the next step to integrate?  Do you have an example or a documentation about that? Can I integrate all other functions from Demo Examples into 1 project or should I handle the separately? The examples use files from ARM-software/CMSIS_4 repository, (e.g.: ARMCM7.h, ARMCM7_DP.h,.. ). Why are they important? Can I add these files from "Periferals view"  of S32 Design Studio IDE like a driver? Thanks in advance. Regards, Sandor   Re: S32K344 with HSE integration to FreeRTOS Thank You. Re: S32K344 with HSE integration to FreeRTOS Hi @sandor_b  Since the HSE firmware installation is typically done only once, I recommend creating a separate project. As for updating the HSE firmware, there should be no issues integrating it into your main application. For clarity, the S32K3 MCUs for General Purpose HSE Demo Examples are provided as separate applications for each use case, demonstrating how each works independently. Additionally, we provide AWS libraries and an MbedTLS package (with HSE) for the S32K3 product, which includes demo examples that integrate the RTD Driver, HSE Firmware, TCP/IP Stack, and RTOS. These resources might be useful for your application development. It can be downloaded from: S32K3 Reference Software > Automotive SW - S32K3 - AWS IoT or Automotive SW - S32K3 - mbedTLS. BR, VaneB

BLDC Sensorless Control with MPC5554 Hi, I am looking for demo of BLDC motor sensorless control with MPC5554.  I only find demo of BLDCM sensorless control with MPC5604B.  Could you please help me with application note on BLDCM sensorless control with MPC5554? Thank you very much! Best Regards, Emily Re: BLDC Sensorless Control with MPC5554 Thanks a lot, Peter! Re: BLDC Sensorless Control with MPC5554 Hello, Such demo is not available for this old micro. I can share with you general theory if you like to write one. https://www.nxp.com/docs/en/application-note/AN4548.pdf Best regards, Peter

RT1021-EVK BEE加密无法启动问题 测试背景：MCUBootUtility6.2 硬件背景：NXP RT1021-EVK 测试软件：iled_blinky 测试流程：移植image_enc2、上位机配置启动设备ISSI的Flash、板子改ISP启动模式、选择BEE加密方式、配置秘钥参数、选择hex、一键启动 烧录完成后将SW8配置成1010，LED没有闪烁，程序无法跑起来，重新改回ISP模式回读efuse，BEE_KEY0_SEL及XIP位数都已使能，SwGp2数值从0x000~ 变更到----- i.MXRT 102x Re: RT1021-EVK BEE加密无法启动问题 或许是我的加密区域过大或程序起始地址的问题，目前已经解决，感谢 Re: RT1021-EVK BEE加密无法启动问题 看起来操作没有问题，无法启动的时候，挂上JLINK， Halt内核看一下 PC 停在哪 回复： RT1021-EVK BEE加密无法启动问题 附未加密前的efuse值

MCUXpresso Secure Provisioning v10 BEE USER KEYS HI： After burning and writing my image through security tools in unsigned, the code can run normally.. No problem... But when using BEE user keys unsigned encryption, the code does not work properly. Isn't that where the problem lies?. The keys are all the same     Re: MCUXpresso Secure Provisioning v10 BEE USER KEYS This issue has been resolved because the XIP encryption enable pin in BOOT_CFG [1] was not connected to high Re: MCUXpresso Secure Provisioning v10 BEE USER KEYS Hi, I see you have two application "boot" and "app". Which of them does not work? What exactly means "the code does not work properly"? What exactly mean "The keys are all the same"? I can see you are using single key for BEE Engine 0. Are there any other keys?

RT1176 FlexRAM ECC enabled by default? Is the RT1176 FlexRAM ECC enabled by default, or does the user need to intentionally enable it with a set of preload configuration commands? We're using the MiMXRT1170 - EVKB. We observed this line of code, but unsure what exactly this means. Thanks in advance for any assistance. #define FSL_FEATURE_FLEXRAM_HAS_ECC (1) Re: RT1176 FlexRAM ECC enabled by default? Hi @Mike_Z , Thank you so much for your interest in our products and for using our community. Question: Is the RT1176 FlexRAM ECC enabled by default, or does the user need to intentionally enable it with a set of preload configuration commands? We're using the MiMXRT1170 - EVKB. Answer: The RT1176 FlexRAM ECC disabled by default, The user need to intentionally enable it. Please refer to MIMXRT1170RM chapter 38.7.1.16 OCRAM Pipeline And ECC Enable (PIPE_ECC_EN) I suggest you can refer to SDK demo "evkbmimxrt1170_mecc_single_error_cm7" Best Regards mayliu

S32K358 セキュアデバッグ NXP S32K358マイコンを使用したカスタムボードを設計しました。S32 Design Studio(S32DS)IDEを使用して最初のコードをアップロードしようとすると、次のエラーが発生します。 "このデバイスでは Secure Debug が有効になっている可能性があります。その場合は、再度接続を試みる前に、PEmicroスクリプトを使用してデバイスのロックを解除してください。 MCUのデバッグインターフェースがロックされているため、コードのアップロードやデバッグができていないと思われます。デバッグインターフェイスのロックを解除するためのステップバイステップガイドを提供していただけますか? 日時:S32K358セキュアデバッグ こんにちは@VaneB、 ご支援のほど、よろしくお願いいたします。問題が見つかりました。FS26のピンRST_Bローで、MCUをリセットしていたため、MCUのデバッグが制限されていました。RST_BをMCUピンから分離した後、MCUをデバッグできるようになりました。 日時:S32K358セキュアデバッグ こんにちは@VaneB、 FS26の電源レールは正常に動作しています。 FS26とMCUの両方の物理ピンの電圧を確認しました。 お申込みいたしました > VDD_HV_A & VDD_HV_B - (+5V) > Vcore - (+1.5V) >Vref - (+5V) V11とV25もチェックしましたが、これも問題ありません。以前のMCU(P32K358HVS 0P14E CTAB2335A)と同じボードを使用しており、問題なく動作していました。 現在のMCU品番は - S32K358GHMPCS 1P14E CTAG2428B 日時:S32K358セキュアデバッグ こんにちは @VaneB、 MCUのデバッグはまだできません。 私たちのサポートチケットは解決策なしに閉じられますので、フィードバックをお待ちしております。 BR、ナイーム

Running the flexcan example using two frdm-kw36 boards Hello. I am currently learning flexcan examples using two frdm-kw36 boards. The version of the kw36 SDK I am using is "SDK_2_2_12_FRDM-KW36", and the mcux version is "v11.8.1_1197". The flexcan example path is [frdmkw36 > driver_examples > flexcan > interrupt_transfer]. The hardware configuration is as shown in the photo below. I debugged the flexcan example and checked it with the Putty program, but after setting the node (A or B), even if I enter a string, no data is sent and nothing happens. As you can see in the picture, it only works up to that point and does not respond to any additional input after that. When I checked other examples or application notes, it said that 12V DC was needed for CAN communication, so I tried applying 12V DC, but the same phenomenon was repeated. After connecting 12V DC, the hardware configuration is as shown in the photo below. I've configured it this way, but why is there no action in the Putty program? Is there some process or content that I am not thinking about? I am waiting for answers from knowledgeable people. Re: Running the flexcan example using two frdm-kw36 boards Hi, I will give you a follow up from your last question. From the FlexCan example used, we define in the flexcan_interrupt_transfer.c located in the folder source; if it will use 2.0A or 2.0B from the line 206 and 239 using the typedef enum _flexcan_frame_format, were kFLEXCAN_FrameFormatStandard(will manage 2.0A) and kFLEXCAN_FrameFormatExtend (will manage 2.0B). To know more about the architecture for the CAN, you could look more information here. Answering the 2nd question, you should modify the FLEXCAN_ID_STD->FLEXCAN_ID_EXT as well the CAN_ID_STD_SHIFT->CAN_ID_EXT_SHIFT that are used in the flexcan_interrupt_transfer.c. This is how it's supposed to work using the values Tx/Rx of 4 digits. Regards, Itzel. Re: Running the flexcan example using two frdm-kw36 boards @Itzel_UV  Thank you for your kind reply. Additionally, I have a few more questions for you. Does that flexcan example use CAN 2.0A or CAN 2.0B? Also, even if you change the Tx/Rx ID from the current 3 digits (e.g. 0x123) to 4 digits (e.g. 0x5555), Putty can only display up to 3 digits (e.g. 0x555). Why is this like this? Please explain. thank you Re: Running the flexcan example using two frdm-kw36 boards Hello, I will be helping you with your question. You indeed have the connections correct (last picture on your own post). Could you confirm that you have pressed first the keyboard "B'' on one terminal followed after with the keyboard "A'' on the other terminal? The outcome from the flex CAN Interrupt Transfer example should look like this. Please keep me up to date if there's still trouble. Regards, Itzel.

S32K358 SECURE DEBUG We have designed a custom board using the NXP S32K358 microcontroller. While trying to upload the first code using the S32 Design Studio (S32DS) IDE, we are encountering the following error: "Secure Debug might be enabled on this device. If so, please unlock the device via PEmicro scripts before attempting to connect again." We suspect that the MCU’s debug interface is locked, preventing us from uploading code or debugging. Could you please provide a step-by-step guide to unlock the debug interface?? Re: S32K358 SECURE DEBUG Hi @VaneB , Thank you for your support. We have found the issue. RST_B pin of FS26 was low and it was resetting the MCU which restricted us from debugging the MCU. After isolating the the RST_B from MCU pin, we are now able to debug the MCU. Re: S32K358 SECURE DEBUG Hi @abunayeeem  I have consulted with the internal team regarding your situation. We need your assistance to verify a few details to determine whether the issue is related to the MCU or the software. Firstly, if possible, could you replace the MCU with the one that previously showed no issues? Does exhibit the same problem, or is it functioning properly? Also, the part number you initially used has custom firmware for VW. Were the PEMicro scripts you used also customized? Lastly, did your project include any modifications to the lifecycle?" Re: S32K358 SECURE DEBUG Hi @abunayeeem  I am checking the situation with the internal team and will let you know the response as soon as I have an update. Thank you for your patience. Re: S32K358 SECURE DEBUG Hi @VaneB , The FS26 power rails are working fine. We have checked the voltages of the physical pins of both FS26 and MCU. We have applied > VDD_HV_A & VDD_HV_B - (+5V) > Vcore - (+1.5V) >Vref - (+5V) We have also checked V11 and V25 which are also fine. We have used the same board with previous MCUs (P32K358HVS 0P14E CTAB2335A ) which was working just fine. Current MCU part number is - S32K358GHMPCS 1P14E CTAG2428B Re: S32K358 SECURE DEBUG Hi @abunayeeem  I have reviewed your previous cases and noticed that you are using an FS26. As mentioned earlier, this issue is typically related to communication problems. It is possible that the SBC is not powering correctly, which could prevent the MCU from being programmed. Please review the following thread, which contains information that could be useful. FS26 Re: S32K358 SECURE DEBUG Hi @VaneB , We are still unable to debug the MCU. Our support ticket is closed without any resolution and your feedback is appreciated. BR, Nayeem Re: S32K358 SECURE DEBUG Hi @VaneB , We have updated the PEmicro plugin and the chip is powered correctly. Please find attached the flash algorithm information. BR, Nayeem Re: S32K358 SECURE DEBUG Hi @abunayeeem  When programming the MCU for the first time, secure debug should be disabled, and this error message is usually related to communication issues. Please verify that the chip is powered correctly and that you are using the latest version of the PEMicro plugin. To update, go to Help > Install New Software, then select the PEMicro page. Additionally, could you provide information about your programming algorithm? BR, VaneB