About entering IVOR1_Handler when using FlexCAN When I used multiple CAN channels of MPC5748G in FreeRTOS, in the execution FLEXCAN_DRV_RxFifo(INST_CANCOM2,&recvBuff); Or FLEXCAN_DRV_Receive(INST_CANCOM2,RX_MAILBOX2,&recvBuff); Until we have this problem: Enter into IVOR1_Vector: e_b IVOR1_Handler Part of the program is as follows: #if CAN1_EN FLEXCAN_DRV_Init(INST_CANCOM1, &canCom1_State, &canCom1_InitConfig0); //CAN0 FLEXCAN_DRV_ConfigRxMb(INST_CANCOM1, RX_MAILBOX, &RXdataInfo1, RX_MSG_ID); FLEXCAN_DRV_ConfigTxMb(INST_CANCOM1, TX_MAILBOX, &TXdataInfo1, TX_MSG_ID); if(! canCom1_InitConfig0.fd_enable) { FLEXCAN_DRV_ConfigRxFifo(INST_CANCOM1,FLEXCAN_RX_FIFO_ID_FORMAT_A,&RX_id_table1); } FLEXCAN_DRV_InstallEventCallback(INST_CANCOM1,CAN_CallBackHandle,NULL); if(canCom1_InitConfig0.fd_enable) { FLEXCAN_DRV_Receive(INST_CANCOM1,RX_MAILBOX,&recvBuff); } else { FLEXCAN_DRV_RxFifo(INST_CANCOM1,&recvBuff); } #endif #if CAN2_EN FLEXCAN_DRV_Init(INST_CANCOM2, &canCom2_State, &canCom2_InitConfig0); //CAN1 FLEXCAN_DRV_ConfigRxMb(INST_CANCOM2, RX_MAILBOX2, &RXdataInfo2, RX_MSG_ID); FLEXCAN_DRV_ConfigTxMb(INST_CANCOM2, TX_MAILBOX, &TXdataInfo2, TX_MSG_ID); if(! canCom2_InitConfig0.fd_enable) { FLEXCAN_DRV_ConfigRxFifo(INST_CANCOM2,FLEXCAN_RX_FIFO_ID_FORMAT_A,&RX_id_table2); } FLEXCAN_DRV_InstallEventCallback(INST_CANCOM2,CAN_CallBackHandle,NULL); if(canCom2_InitConfig0.fd_enable) { FLEXCAN_DRV_Receive(INST_CANCOM2,RX_MAILBOX2,&recvBuff); } else { FLEXCAN_DRV_RxFifo(INST_CANCOM2,&recvBuff); } MPC5748G-GW-RDB  回复： About entering IVOR1_Handler when using FlexCAN I have solved this problem by increasing the FreeRTOS heap size. This is done by increasing the size of configTOTAL_HEAP_SIZE in FreeRTOSConfig.h Re: About entering IVOR1_Handler when using FlexCAN Sure. Thank you very much for taking the time to help me troubleshooting the problem. My project is a collection of ENET and CAN project based on the sample program, if you want to execute to send the wrong place, may require you to complete the TCP connection. My test project looks like this: Re: About entering IVOR1_Handler when using FlexCAN Hi, can you share full simplified project, so it can be tested? BR, Petr

S32DS for S32 Platform3.5如何安装OpenExplorer插件 S32DS无法直接打开工程的文件夹目录，在S32DS for ARM以及S32DS for Power里面，都可以将OpenExplorer.jar插件复制到S32DS的安装目录下面的eclipse\plugins目录下面，就可以启用这个插件，直接在S32DS里面就可以打开文件浏览器。 下图是S32DS for ARM安装插件的效果： 但是S32DS for Platform 3.5，按照同样的方式复制jar文件，却没有出现这个插件，请问如何可以安装？ 回复: S32DS for S32 Platform3.5如何安装OpenExplorer插件 回复: S32DS for S32 Platform3.5如何安装OpenExplorer插件 S32DS v3.5基于不同的Eclipse版本。请下载适用于 Eclipse v4.20 的插件

S32k312 CANFD 通过FlexCAN_Ip_ConfigRxMb()设置问题 你好： 在使用S32k312 配置CANFD功能时发现， FlexCAN_Ip_ConfigRxMb(INST_FLEXCAN_0, RX_MB_IDX, &rx_info, MSG_ID); FlexCAN_Ip_Receive(INST_FLEXCAN_0, RX_MB_IDX, &rxData, false); rx_info.data_length = 8u; rx_info.fd_enable = FALSE; 1. Data的length和FD_enable 设置为8U,和FALSE时，当发送端发送16个字节CANFD帧时，S32K312 端还是能接收到16个byte的数据，请问这是问什么？代码如下： Flexcan_Ip_DataInfoType rx_info； IntCtrl_Ip_EnableIrq(FlexCAN0_1_IRQn); IntCtrl_Ip_InstallHandler(FlexCAN0_1_IRQn, CAN0_ORED_0_31_MB_IRQHandler, NULL_PTR); FlexCAN_Ip_Init(INST_FLEXCAN_0, &FlexCAN_State0, &FlexCAN_Config0); FlexCAN_Ip_SetRxMaskType_Privileged(INST_FLEXCAN_0,FLEXCAN_RX_MASK_INDIVIDUAL); FlexCAN_Ip_SetRxIndividualMask_Privileged(INST_FLEXCAN_0,RX_MB_IDX,0x0<<18); FlexCAN_Ip_SetStartMode(INST_FLEXCAN_0); //setupCanXCVR_TJA1153(); tx_info.is_polling = FALSE; tx_info.msg_id_type = FLEXCAN_MSG_ID_STD; tx_info.data_length=64; tx_info.fd_enable = TRUE; tx_info.enable_brs = TRUE; rx_info.msg_id_type = FLEXCAN_MSG_ID_STD; rx_info.data_length = 8u; rx_info.fd_enable = FALSE; rx_info.fd_padding = FALSE; rx_info.enable_brs = FALSE; rx_info.is_polling = FALSE; rx_info.is_remote = FALSE; FlexCAN_Ip_ConfigRxMb(INST_FLEXCAN_0, RX_MB_IDX, &rx_info, MSG_ID); FlexCAN_Ip_Receive(INST_FLEXCAN_0, RX_MB_IDX, &rxData, false); FlexCAN_Ip_Send(INST_FLEXCAN_0, TX_MB_IDX, &tx_info, MSG_ID, (uint8 *)&dummyData); 此图为s32k312接收到数据，再发送出来： Re: S32k312 CANFD 通过FlexCAN_Ip_ConfigRxMb()设置问题 Hi@Bert2023 不错的问题，之前没细心留意过。 我测试之后发现确实是这样，当调用过FlexCAN_Ip_Init之后，每个MB的大小是已经确定了，你的工程是设置为64byte的数据长度，所以只要rx_info.data_length在64byte之内，你能收到所有的数据。 但是你可以查看rxData.dataLen来查看当前收到的Frame的数据长度，这样你就直到你实际需要接收多少个字节的数据。 “ FlexCAN_Ip_Receive(INST_FLEXCAN_0, RX_MB_IDX, &rxData, false); for(int i=0;i dataLen;i++) {      dummyData[i]=rxData.data[i]; } ” Re: S32k312 CANFD 通过FlexCAN_Ip_ConfigRxMb()设置问题 好的，多谢！工程文件如附件，环境DS3.4 +S32K3 RTD2.0.0   ，FD code参考Example S32K358 FlexCAN TXRX ISR S32DS35 RTD400 - NXP Community例程。 Re: S32k312 CANFD 通过FlexCAN_Ip_ConfigRxMb()设置问题 Hi@Bert2023 工程发过来，我帮你测试检查下

デプロイ前にコンソールへのセミホスティング 'printf'を無効にするために特に何かをする必要がありますか? MCUXpressoのドキュメントで、「セミホスティングライブラリとリンクすると、アプリケーションはスタンドアロンで動作しなくなります。デバッガーに接続されている場合にのみ機能します」と読みました。 フォーラムの他の場所では、「セミホスティングは、デバイスへのアクティブなデバッグ接続がある場合にのみ機能します。」 - これは、アクティブなデバッグセッションにないときにはコンソール出力を提供しないため、デプロイ時にコードに残しても問題ないように聞こえます。 私はLPC845ベースのシステムを持っており、コンソールをPRINTFに使用しており、コードの開発に非常に便利です。マルチリンクから切断すると完全に機能するように見え、「スタンドアロン」として機能するため、#MCUXpresso ドキュメントステートメントに混乱しています だから、私はこれについて決定的な答えを求めています: セミホスティングの使用に関して、デバッグから製品リリースに適切に移行するために、コードまたはIDE設定に対して何を行う必要がありますか?PRINTF ステートメントを削除または使用不可にする必要がありますか?デバッグセッションに接続されていないときに自動的に「削除」されるので、そのままにしておくことはできますか? 乾杯！ Re:デプロイ前にコンソールへのセミホスティング 'printf'を無効にするために特に何かをする必要がありますか? これはまさに完璧な情報です。改めて、ありがとう、ありがとう、エーリッヒ!

i.MX8M Mini internal IO pullup/pulldown ERR050080 "continuously driven" Hello, According to ERR050080 in Errata IMX8MM_0N87W, "There is a degradation of the internal IO pullup/pulldown capability when the IO pads are continuously driven in the opposite logic level," What is the meaning of continuously? more than 1 millisecond, 1 minute, or 1 hour??? On my design, The IO pad could be driven in the opposite logic level of internal Pullup /pullodwn resistor during software boots.  After, the  software disable the internal pullup/pulldown. It's not continously, but it could be more than several tens of seconds. Do you think it could be be a problem? Remark: the operating temperature is -20/+70°C. Best Regards. Sylvain Re: i.MX8M Mini internal IO pullup/pulldown ERR050080 "continuously driven" Hello @Sylvain_B  If pull-up/Pull-down resistors are not required (internal or external), it should works well, there is not related known issue, but anyway is recommended to disable the the Pull resistors by software as you are doing. Best regards, Salas.  Re: i.MX8M Mini internal IO pullup/pulldown ERR050080 "continuously driven" => So, can you confirm that if the IO pad is driven at the logic level opposite to the internal pullup/pullodwn resistor during software startup and then the software disables the internal pullup/pulldown after several tens of seconds, there won't be a problem? Alternatively , In the first version of the erratasheet (Rev 0) 01/2019, it is mentioned that the impedance pad is downgraded (20k -> 92k). Could you please confirm that only the resistor value is affected  on theand that the IO will still be functional (without the internal PU/PD resistor. Best Regards Re: i.MX8M Mini internal IO pullup/pulldown ERR050080 "continuously driven" Hello @Sylvain_B  There is not documented exact "time" to describe continuously. The errata ERR050080 impact to the operations like a communication protocol that use changes in the line to the opposite state of the pull at 3.3v, that means continuously. As the workaround of this Errata, is recommended to use external pulls and disable from software. Best regards, Salas.

i.MX8MP MPUとMCU間のSPI通信 こんにちは、マイコンを使用してセンサデータを読み取る予定であり、このデータをi.MX8MPを搭載したカスタムボードで活用する予定です。データはSPIを介してMCUから i.MX に転送されます。私の質問は、i.MX のM7コアを使用してデータを受信し、カスタムディストリビューションのユーザーアプリケーション内で処理する必要があるか、それともAコアと直接SPI通信を処理する必要があるかということです。統合が簡単で、レイテンシを短縮する方法はどれですか? Re:i.MX8MP MPUとMCU間のSPI通信 rpmsg を使用してレイテンシが発生し、m7 は共有メモリにデータを書き込み (必要な時間)、次に MU を使用して A コア (必要な時間) に通知し、次に A コアが共有メモリからデータを読み出します (必要な時間)。では、低レイテンシが必要なため、AコアSPIから直接データを受信してみてはいかがでしょうか Re:i.MX8MP MPUとMCU間のSPI通信 ユーザー空間で使用する受信データを解析するドライバーを作成する必要があります。この目的に関する提案はありますか、または制限はありますか?また、m7コアを使用し、rpmsgを介してユーザー空間のセンサーデータを使用することが悪い考えであるのはなぜですか? ありがとうございます！

Build failed on BSP40 with enabling secboot feature. Hi Sir I enable secboot feature like this. DISTRO_FEATURES:append = " pfe hse secboot" I encountered a build error. Could you help me check it? Re: Build failed on BSP40 with enabling secboot feature. Hello, thanks for the reply. If you do not want to remove corresponding 3 files mentioned from previous post, the following method may also be useful, add the following line to conf/local.conf, then rebuild: PREFERRED_VERSION_arm-trusted-firmware-tools-native = "2.5"   Hope it helps. Best Regards Chenyin Re: Build failed on BSP40 with enabling secboot feature. Hi Sir, Can TF-A 2.10 be disregarded without being deleted? Re: Build failed on BSP40 with enabling secboot feature. Hello, Thanks for the question To enable SECBoot Support, update the conf/local.conf file in the Yocto build directory with these lines: DISTRO_FEATURES:append = " secboot" NXP_FIRMWARE_LOCAL_DIR = "/path/to/firmware/folder" Enabling HSE Secure Boot in the conf/local.conf file will automatically enable PKCS11 Support & HSE Linux Driver as well. You may not need to add additional “hse” here. For the building error, since only TF-A 2.5 is used in BSP40, you may temporally remove the TF-A 2.10 related files under sources/meta-alb/recipes-bsp/arm-trusted-firmware/ as a workaround. Hope it helps. Best Regards Chenyin

Can't use PEmicro debugger with S32K3X4EVB-T172 I have a problem about the PEmicro in Step 4.3 Upload Software and Debug.  Getting Started with the S32K3X4EVB-T172 Evaluation Board for Automotive General Purpose  Error in services launch sequence PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power. Verify that the launch settings in the Debug Configuration are accurate. This Can't use PEmicro debugger with S32K118EVB2-Q048 showed Kinetis_Recovery_Utility.zip how  to make sure that the PEmoicro is work, but the figure of my computer shows that PEmicro is still not work. This blew figure shows my installed softwares and drivers. In additional, why is the LED RST_OSDA always high not blink. Re: Can't use PEmicro debugger with S32K3X4EVB-T172 After Plugging in the Power Supply with a transfer with supported 12 V, the User LED is blinking. Remember that the EVM must support it with a external voltage.

rte_kni.ko not found within the DPDK on Ubuntu 20.04 PC I am testing dpdk application in PC with PCI-E Dual-RJ45 gigabit NIC card to develop a network based application. I have started my project with dpdk 21.08 and Codewarrior IDE. PC details : uname -a Linux mglocadmin-ThinkCentre-M73 5.15.0-105-generic #115~20.04.1-Ubuntu SMP Mon Apr 15 17:33:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux The following steps to install DPDK (Data Plane Development Kit) on Ubuntu 20.04: sudo apt update sudo apt install build-essential meson python3-pyelftools libnuma-dev pkgconf wget https://fast.dpdk.org/rel/dpdk-21.08.tar.xz tar -xf dpdk-21.08.tar.xz meson build ninja -C build meson -Dexamples=all build sudo ninja install sudo ldconfig Setup hugepage in PC: mkdir -p /dev/hugepages mountpoint -q /dev/hugepages || mount -t hugetlbfs nodev /dev/hugepages echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages Log "dpdk-devbind.py -s": Network devices using DPDK-compatible driver 0000:02:00.0 '82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) 105e' drv=uio_pci_generic unused=e1000e,vfio-pci 0000:02:00.1 '82571EB/82571GB Gigabit Ethernet Controller D0/D1 (copper applications) 105e' drv=uio_pci_generic unused=e1000e,vfio-pci Network devices using kernel driver 0000:03:00.0 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller 8168' if=enp3s0 drv=r8169 unused=vfio-pci,uio_pci_generic *Active* I follow the steps to load DPDK KNI Kernel Module below the link https://doc.dpdk.org/guides-21.08/prog_guide/kernel_nic_interface.html#kni-default-carrier-state Testing KNI application in PC $ sudo ./dpdk-kni -l 0-1 -n 4 -- -P -p 0x3 --config="(0,0,0),(1,1,1)" ERROR log: EAL: Detected 4 lcore(s) EAL: Detected 1 NUMA nodes EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'PA' EAL: No available 1048576 kB hugepages reported EAL: VFIO support initialized EAL: Probe PCI driver: net_e1000_em (8086:105e) device: 0000:02:00.0 (socket 0) EAL: Probe PCI driver: net_e1000_em (8086:105e) device: 0000:02:00.1 (socket 0) TELEMETRY: No legacy callbacks, legacy socket not created KNI: Can not open /dev/kni APP: Initialising port 0 ... KNI: KNI subsystem has not been initialized. Invoke rte_kni_init() first EAL: Error - exiting with code: 1 Cause: Fail to create kni for port: 0 Try to find rte_kni.ko kernal module file in DPDK directory : $ sudo find / -name rte_kni.ko rte_kni.ko: No such file or directory NOTE: Dpdk-l2fwd and Dpdk-L2fwd-crypto working in PC kindly help us to resolve this issue. Re: rte_kni.ko not found within the DPDK on Ubuntu 20.04 PC Thank you for your Reply @yipingwang  . I am using meson to configuration and ninja to build DPDK application and also i find the solution on my own Here the solution(using Meson): 1.Need to edit the /home/mglocadmin/NIC/dpdk-21.08/meson_options.txt file and make sure that you enable the boolean as a true to get rte_kni.ko       option('enable_kmods', type: 'boolean', value: true, description:'build kernel modules') 2.Build and test KNI       meson -Dexamples=all build       ninja –C build Log: make: Entering directory '/usr/src/linux-headers-5.15.0-105-generic' CC [M] /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/kni_net.o CC [M] /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/kni_misc.o LD [M] /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/rte_kni.o MODPOST /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/Module.symvers CC [M] /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/rte_kni.mod.o LD [M] /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/rte_kni.ko BTF [M] /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/rte_kni.ko 3.Load KNI module sudo insmod /home/mglocadmin/NIC/dpdk-21.08/build/kernel/linux/kni/rte_kni.ko kthread_mode=multiple Re: rte_kni.ko not found within the DPDK on Ubuntu 20.04 PC To cross-compile DPDK, including the kernel modules, the kernel source tree needs to be specified by setting RTE_KERNELDIR: make -j CROSS=aarch64-linux-gnu- RTE_KERNELDIR= CROSS_COMPILE=aarch64-linux-gnu-

SPI Comm Between i.MX8MP MPU and MCU Hello, we are planning to read sensor data using an MCU and intend to utilize this data on our custom board equipped with an i.MX8MP. The data will be transferred from the MCU to the i.MX via SPI. My question is: should we use the M7 core on the i.MX to receive the data and then process it within our user application on our custom distro, or should we handle the SPI communication directly with the A core? Which method would be easier to integrate and result in lower latency? Re: SPI Comm Between i.MX8MP MPU and MCU Hello, Do you have any examples of this type of communication? For both sides, an MCU and an MPU? Thanks! Re: SPI Comm Between i.MX8MP MPU and MCU There is latency using rpmsg, the m7 write data to shared memory(need time), then use MU to notify A core(need time), then A core read data from shared memory(need time). So why not receive data from A core SPI directly as you need lower latency Re: SPI Comm Between i.MX8MP MPU and MCU We'll have to write a driver to parse the incoming data to use in the userspace. Any suggestions for this purpose or do you see any limitations? Also Why using m7 core and using the sensor data on the user space via rpmsg is a bad idea? Thanks! Re: SPI Comm Between i.MX8MP MPU and MCU Hi @Wobaffet   Which method would be easier to integrate and result in lower latency? --> I think use it in A core is better for you.

i.MX8MP MPU 和 MCU 之间的 SPI 通信 您好，我们计划使用 MCU 读取传感器数据，并打算在配备 i.MX8MP 的定制板上使用这些数据。数据将通过 SPI 从 MCU 传输到 i.MX。我的问题是：我们应该使用 i.MX 上的 M7 核心接收数据，然后在我们自定义发行版的用户应用程序中处理它，还是应该直接用 A 核心处理 SPI 通信？哪种方法更容易集成并降低延迟？ 回复：i.MX8MP MPU 和 MCU 之间的 SPI 通信 使用 rpmsg 存在延迟，m7 将数据写入共享内存（需要时间），然后使用 MU 通知 A 核（需要时间），然后 A 核从共享内存读取数据（需要时间）。既然需要更低的延迟，为什么不直接从 A 核 SPI 接收数据呢？ 回复：i.MX8MP MPU 和 MCU 之间的 SPI 通信 我们必须编写一个驱动程序来解析传入的数据以供在用户空间中使用。对于此目的您有什么建议吗？或者您认为有什么限制吗？另外为什么使用 m7 核心并通过 rpmsg 在用户空间使用传感器数据是一个坏主意？ 谢谢！

new recommendation for EOL of TDA8026ET Hi Teams, for EOL of TDA8026ET, do you have any new product to recommend to customer in use. thanks . RF Re: new recommendation for EOL of TDA8026ET Hello @joe7  TDA8026 has 6 Analog interfaces. I'd like to know how many of these interfaces do you use? If you only use one or none, then the TDA8035 is recommended for you. BR Kelly

TDA8026ET 停产新建议 大家好， 对于TDA8026ET的EOL，您有什么新产品可以推荐给正在使用的客户吗？ 谢谢 。 射频

S32K3 Cyclic wake-up current is abnormal Hi,all I need to implement a function: the S32K3 cycle wakes up, and then scans the GPIO input to see if the MCU really needs to wake up, otherwise it continues to enter low-power mode. After testing, I found that the description in the data manual of the chip may be wrong.The manual I use is S32K3xx Data Sheet Rev.9.The manual describes the average current as 159uA,My test results show that the average current is 2700uA. The chip can't do that, and the cycle time of the RUN is only 0.2ms. The chip takes 14 ms to enter the main from the wake-up event, which is tested in the NXP manual< Power Management for S32K3XX>. My test results show that the average current is 2700uA. The result is much larger than that described in the manual and most of the current is consumed in the startup.s operation. How is the data in the data manual tested? Can you provide a way to implement it? it is best to have a Demo to provide. BRs, xianlong Re: S32K3 Cyclic wake-up current is abnormal Hi xianlong, Please refer to the S32K344_RTI_Cycl_Wkup_S32DS_3_4_RTD_LLD_2_0 example in https://community.nxp.com/t5/S32K-Knowledge-Base/S32K3-Low-Power-Management-AN-and-demos/ta-p/1527724 It is recommended to use Fast wakeup and check the IO status in Wkup_FastWkupBootAddress and then return to standby. Do not call __asm("bl Reset_Handler"); which initialize the MCU and then enter main function. Otherwise, whether it is Fast wakeup or Normal wakeup, it will take 14ms to finally enter the main function. Best Regards, Robin ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------

s32k344：如何写入内部闪存？算法/步骤/代码示例/解释是什么？ s32k344：如何写入内部闪存？ 算法/步骤/代码示例/解释是什么？ 您能提供没有 autosar 的代码示例吗？ 回复：s32k344：如何写入内部闪存？算法/步骤/代码示例/解释是什么？ 编译之前 - 我打开 *.mex 文件并“更新代码”。修复缺失的 PIN SDK 文件。 我发现“Siul2_Port_Ip_Defines.h”被遗漏了。 从另一个项目复制此文件后 - 它可以运行。

TDA8026ETのEOLに関する新しい推奨事項 こんにちはチーム、 TDA8026ETのEOLについて、使用中のお客様にお勧めする新製品はありますか? 感謝。 RF

i.MX7d uSDHC CMD53读取错误 当通过 SDR50 将 Silex SX-SDMAC 连接到 i.MX7d uSDHC2 并运行时，读取 CMD53 时有时会出现错误，我们正在调查原因。 调校过程没有采用自动调校，而是设置uSDHC2_TUNING_CTRL寄存器中的STD_TUNING_EN，设置uSDHC2_AUTOCMD12_ERR_STATUS寄存器中的EXECUTE_TUNING，发出40次CMD19后等待调校完成，但是下面社区有帖子说自动调校时启用默认CMD和DATA[0]到DATA[3]时，Delay cell无法正常调整，读取CMD53时可能会出错。 即使不进行自动调整，我是否只需要将 CMD 和 DATA[0] 设置为调整时的目标并进行调整？ uSDHC 自动调优和可能的 SDIO 故障 - NXP 社区 i.MX7 双核 回复：i.MX7d uSDHC CMD53 读取错误 感谢您的回复。 回复：i.MX7d uSDHC CMD53 读取错误 在 i.MX 7Dual 应用处理器参考手册的 10.3.8.13 中断状态 (uSDHCx_INT_STATUS) 中，第 15 位是保留位（此只读字段保留，且始终为 0）。您的回答与此不符，因此我希望您修改参考手册或提供勘误表。此外，似乎发生错误时会设置第 15 位，但如何清除已设置的第 15 位？ >-->或者您可以尝试清除这些位来检查是否可以解决此问题。 >uSDHCx_AUTOCMD12_ERR_STATUS[SMP_CLK_SEL] >uSDHCx_MIX_CTRL[FBCLK_SEL] >uSDHCx_MIX_CTRL[自动调谐] 我应该什么时候清除这些位？ 这是在 uSDHC2_AUTOCMD12_ERR_STATUS 寄存器中设置 EXECUTE_TUNING 之前吗？ 回复：i.MX7d uSDHC CMD53 读取错误 我理解在 uSDHC2 调优过程中，即使不使用自动调优，也只需设置 CMD 和 DATA[0]。在设置 uSDHC2_AUTOCMD12_ERR_STATUS 寄存器中的 EXECUTE_TUNING 之前，是否可以立即将 uSDHC2_VEND_SPEC2 寄存器设置为仅针对 CMD 和 DATA[0]？或者是否存在任何限制，要求在设置任何其他寄存器之前设置它？顺便提一下，这次发生 CMD53 读取错误时，uSDHC2_INT_STATUS 寄存器的第 15 位（保留）被设置为 1。手册上说读取的值始终为 0，请问您能解释一下这个位的含义吗？ 回复：i.MX7d uSDHC CMD53 读取错误 我了解在 uSDHC2 调整过程中，即使不使用自动调整，也只需设置 CMD 和 DATA[0]。 在 uSDHC2_AUTOCMD12_ERR_STATUS 寄存器中设置 EXECUTE_TUNING 之前，是否可以将 uSDHC2_VEND_SPEC2 寄存器设置为仅针对 CMD 和 DATA[0]？ 或者是否存在任何限制，要求在任何其他寄存器设置之前进行设置？ 顺便说一下，这次发生 CMD53 读取错误时，uSDHC2_INT_STATUS 寄存器的第 15 位（保留）被设置为 1。手册上说总是读出 0，但你能告诉我这位是什么意思吗？ 回复：i.MX7d uSDHC CMD53 读取错误 您的帖子已被更改，因为在邮件正文中发现无效的 HTML。无效的 HTML 已被删除。请检查该消息，满意后提交该消息。

S32K312-172HDQFP 的 V11 引脚布局 问候， 在“S32K3xx - 硬件设计指南”文档中，表6显示“所有v11引脚必须短路并通过外部连接到PCB上的公共参考”。我认为这个评论是针对 K388 版本的。 由于V11是S32K312内部产生的核心逻辑电压电源，因此对于S32K312来说，似乎没有必要将所有V11引脚外部连接在一起？这个理解对吗？ 回复：S32K312-172HDQFP的V11引脚布局 明白了，Pavell，感谢您的快速回复。 回复：S32K312-172HDQFP的V11引脚布局 你好@Edward_Y ， 是的，将所有 V11 引脚连接在一起是绝对必要的。因为评论连续：“每个电源引脚可以使用一个去耦电容器，并且仅为 V11 域使用一个本地大容量/旁路电容器，以增加 MCU 的电压参考的稳健性和去耦效果。” 供给建议不容小觑。 顺祝商祺！ 帕维尔

S32K312-172HDQFPのV11ピンレイアウト あいさつ 「S32K3xx - ハードウェア設計ガイドライン」の資料の表 6 には、「すべての v11 ピンを短絡し、PCB 上の共通のリファレンスに外部から接続する必要がある」と記載されています。このコメントはK388バージョン用だと思います。 V11はS32K312用の内部生成コアロジック電圧供給であるため、すべてのV11ピンを外部に接続する必要はないように思われますかS32K312この理解は正しいですか? 日時:S32K312-172HDQFPのV11ピンレイアウト わかった、Pavell、迅速な対応に感謝します。 日時:S32K312-172HDQFPのV11ピンレイアウト こんにちは@Edward_Y、 はい、すべてのV11ピンを一緒に接続することが絶対に必要です。「MCUのこの電圧リファレンスの堅牢性とデカップリング効果を高めるために、各電源ピンごとにデカップリングコンデンサを使用し、V11ドメイン専用のローカルバルク/バイパスコンデンサを使用できます」というコメントが連続しているからです。 供給の推奨事項を過小評価してはなりません。 よろしくお願いいたします。 パベル

KEA128 UART Bootloader 你好，我在KEA128单片机开发遇到一个问题，这个问题通过Jlink烧写程序调试是完全没有问题的，但是当我通过bootloader下载该程序，出现主程序死机的情况。 当我使用以下该程序（设置占空比）时，通过bootloader下载之后，程序出现死机现象。当我把该函数的内容注释掉，则一切正常。这种情况Jlink烧写是完全没有问题的，这个问题让我无从下手，希望能得到帮助，告诉我应该往那个方向寻找答案。 void heater_output(uint32 duty) { if(heater_switch==on) { ftm_pwm_duty(ftm0,ftm_ch0,duty);//设置占空比 } else { heater_pwm_duty=0; ftm_pwm_duty(ftm0,ftm_ch0,0); } } 这是我的跳转程序 void bootup_application(uint32_t appEntry, uint32_t appStack) { static void (*jump_to_application)(void); static uint32_t stack_pointer; //shutdown_drivers(); jump_to_application = (void (*)(void))appEntry;//跳转APP入口地址 stack_pointer = appStack; //堆栈指针 // SCB->VTOR = appEntry; __set_MSP(appStack); //设置主程序堆栈指针 __set_PSP(appStack); //设置进程堆栈指针 jump_to_application(); //跳转 } Re: KEA128 UART Bootloader Hi, 建议您考虑S32K系列， 它是车规级芯片。 https://www.nxp.com/products/processors-and-microcontrollers/s32-automotive-platform/s32k-auto-general-purpose-mcus:S32K-MCUS 如果你老师进入hardFault, 请看看stack是否分配小了。 BR XiangJun Rong Re: KEA128 UART Bootloader 你好，谢谢您的回复，我通过不下载仿真调试发现总是进入HardFault_Handler函数，我觉得可能是调用层次比较深，然后再主循环里直接调用设置占空比的函数，结果没有出现卡死情况。请问这种情况在这款芯片常见吗，我的APP程序大概33K左右，从0x8000开始，如果我想在项目中选择性能更好的性价比的车规级芯片，能运行更多算法，我应该如何选择。 Re: KEA128 UART Bootloader Hi, 那你把appEntry加上1. BR XiangJun Rong Re: KEA128 UART Bootloader 你好，当我把这行代码放进去，出现一个错误，（jump_to_application =jump_to_application +1；）使用的是IAR软件编译器，报错信息为，Error[Pe852]: expression must be a pointer to a complete object type 。这个该如何解决呀？ Re: KEA128 UART Bootloader Hi, 请使用下列代码： //shutdown_drivers(); jump_to_application = (void (*)(void))appEntry;//跳转APP入口地址 jump_to_application =jump_to_application +1； stack_pointer = appStack; //堆栈指针 // SCB->VTOR = appEntry; __set_MSP(appStack); //设置主程序堆栈指针 __set_PSP(appStack); //设置进程堆栈指针 jump_to_application(); //跳转 因为是thumb指令集， 请试一下，看行不行 BR XiangJunRong