Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
如何为 KSDK 和 PEx 项目的新 MQX RTOS 添加 MFS 和 Shell 支持 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 大家好, 基于如何使用 KDS 和 KSDK 将 RTCS 添加到处理器专家项目,您可以在下面找到使用 KSDK1.2 和处理器专家将 MFS 和 Shell 包含到 KDS3.0 项目的步骤。 感谢Carlos_Musich提供的出色文档以及本文档的草稿。 此致, 艾萨克·阿维拉 文件系统 回复:如何为 KSDK 和 PEx 项目的新 MQX RTOS 添加 MFS 和 Shell 支持 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 感谢 Isaac 的演讲。 我使用 Shell 和适用于 K60D100M micro 的 shell 创建了 KDS3.0 项目。KSDK 1.2.0。 我遇到的唯一问题是构建变量。 在 Properties\C/C++ Build\Build Variables 中缺少 KSDK_PATH(参见插入的图像)。 我创建了几个任务并在调试器下运行应用程序。调试器下没有 TAD 信息。 我知道,只需查看 TAD 信息,调试器就应该在运行后在任务内部的某个地方停止。 也许你已经解决了这个问题。 谢谢! 列昂尼德·博尔夏克。
View full article
Example S32K312 PIT BTCU parallel ADC FIFO DMA DS3.5 RTD300 This example for S32K312 is based on this, example on S32K344 :-- https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K344-PIT-BTCU-parallel-ADC-FIFO-DMA-DS3-5-RTD300/ta-p/1732444 *******************************************************************************  The purpose of this demo application is to present a usage of the  ADC_SAR and BCTU IP Driver for the S32K3xx MCU.  The example uses the PIT0 trigger to trigger BCTU conversion list to  perform parallel conversions on ADC0/ADC1. Three ADC channels  are selected to be converted on each ADC:  ADC0: S8 , P0, S8  ADC1: S10, S13, S17  Converted results from BCTU FIFO are moved by DMA into result array.  ADC channel S10 is connected to board's potentiometer.  ------------------------------------------------------------------------------ * Test HW: S32K3X4EVB-Q172 * MCU: S32K312 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE Micro * Target: internal_FLASH ******************************************************************************** Set PIT Freeze Enable :--- BCTU will be do the parallel conversion for channel mentioned in BCTU list :--   "NEW DATA DMA enable mask" :-- controls These bit field in MCR register "ADC target mask" :-- It controls "ADC_SEL " bit field in "Trigger Configuration (TRGCFG_0 - TRGCFG_71)" for single conversions you can enable only one instance so the possible values for target mask: 1 (0b001) ADC0 2 (0b010) ADC1 3 (0b100) ADC2| for list of conversions we can enable also parallel con version for example 3 (0b011) parallel conversion of ADC0 and ADC1 The trigger is configured as a list of parallel conversions ADC0, ADC1 in “Adc Target Mask”. List of ADC channels is defined in “BCTU List Items” while order is given by the “Adc Target Mask”: BctuListItems_0 is ADC0, BctuListItems_1 is ADC1 etc. Result :-- I connected VDD from board on adc_0_p0 (PTD1 : J412-1)  and adc_1_p2 (PTE0 J412-13). Also POT value on S10 of ADC-1 & ADC-0-VREFH value coming correct & STABLE. =========================Using  FIFO-2 ================= FIFO-2 Trigger & LIST Index :-- ADC channel conversion :--
View full article
S32K Examples S32K1xx S32K144 Example S32K144 CMP Round-robin S32DS2.0  Example S32K144 Verify Backdoor Access Key S32DS1.3  Example S32K144 FlexCAN0 RXFIFO DMA nonSDK S32DS13  Example S32K144 PDB ADC trigger DMA ISR S32DS  Example S32K144 Flash RW simple S32DS  Example S32K144 DMA memory copy test S32DS  Example S32K144 EEEPROM usage Example S32K144 EEEPROM usage - No SDK  Example S32K144 RTC VLPS  Example S32K144 WDOG RCM interrupt  Example S32K144 SRAM ECC Injection  Example S32K144 RAM Retention S32DS.R1 Example S32K144 I2C Master MPL3115A2 S32DSR1_v3  Example S32K144 FlexCAN RXFIFO DMA S32DS.ARM.2018.R1  Example S32K144_printf_implementation - S32DS_1.0  Example S32k144 UART printf/scanf under FreeRTOS - S32DS Example S32K144 SDK Function call on configurable period using LPIT timer.  Example S32K144 .noinit section usage Example S32K144 PDB ADC DMA S32DS.ARM.2018.R1   Example S32K144 RAM selftest simple S32DS 2018.R1  Example S32K144 Position Independent Code  Example S32K144 FlexCAN Pretended Networking STOP mode test S32DS.ARM.2.2  Example S32K144 LPIT DMA LPSPI  Example S32K144 FlexCAN TX/RX/Error ISR test S32DS2.2  Example S32K144 FlexIO Idle Detection S32DS2.2 S32K142 Example_S32K142_LMEN_Cache_v1_0_S32DS3.6_RTD300  Lauterbach_Script_For_MDM_AP_Mass_erase_S32K142  S32K146 Example S32K146 Set_whole_FlexRAM-as_RAM S32DS.ARM.2.2 S32K148 Example S32K148 PDB0-PDB1 ring S32DS3.4 RTM4.0.3  Example S32K148 PDB0-PDB1 ring DMA S32DS3.4 RTM4.0.3  Example S32K148 GPIO Interrupt   S32K116 Example S32K116 WDOG Fast Test  Example S32K116 LPUART LIN Slave TXRX ISR S32DS.ARM.2.2  Example S32K116 FlexCAN PN STOP S32DS.ARM.2.2 Example S32K116 FlexCAN VLPR test S32DS.ARM.2.2 S32K118 Example S32K118-SRAM-keep_data_over_SW_reset v0_1 S32DS.ARM.2.2 S32K3xx S32K312 Example S32K312 ADC_IP Continuous Scan DMA S32DS36 RTD600    S32K344 Example S32K344 PIT BTCU ADC DMA DS3.4 RTD100   Example S32K344 FlexCAN_Ip TX/RX/EnhanceRXFIFO test S32DS3.4 RTD200     Example_C40_Ip_ECC_Fault_Skip_S32K312_DS34_RTD2211_v1     Example Siul2_Port_Ip_Example_S32K344_ITCM_DTCM S32DS3.4 RTD300   Example S32K344 LPUART RX/TX ISR FreeRTOS S32DS36 RTD600    Example_S32K344_MCAL_MCU_ClockMonitor_v1_0_S32DS36_RTD600    Example_S32K314_DTCM1_Backdoor_RTD201_DS34_v3    Example_Reg_Prot_Flash_Controller_S32K344   Example_S32K344_EIM_ERM_DTCM_SRAM_Baremetal_v3_0_S32DS36    Example S32K344 PIT SWtrig ADC ANAMUX S32DS 3.6.0 RTD 6.0.0   Example S32K344 EMAC lwIP FreeRTOS miniEVB S32DS 3.6.1 RTD 6.0.0   Example S32K344 EMAC lwIP FreeRTOS MRCANHUB S32DS 3.6.1 RTD600   Example_S32K344_BIST_eMCEM_SPD106_v2_0_S32DS365_RTD700  Example S32K344EVB_T172 UART_ETH_Gateway HLD S32DS368 RTD701   Example_S32K344_CMU_FM_POR_WDG_v1_0_S32DS369_RTD701    Example_S32K344_FLS_Integrity_Margin_Check_v1_0_S32DS36_RTD701    Example S32K344 LPSPI LCD-PAR-S035 FRDM S32DS 3.6.6 RTD 7.0.1   Example FRDM-A-S32K344 FlexCAN TX_RX FreeRTOS S32DS36 RTD600    Example_S32K344_INFLS_ECC_EDC_eMCEM_SPD106_v1_0_S32DS365_RTD700    Example S32K344 EMAC lwIP FreeRTOS S32K3-T-BOX S32DS 3.6.6 RTD7.0.1   Demo EthernetAnalyzer FRDM-A-S32K344 RTD 7.0.1   Example FRDM-A-S32K344 PIT ADC BTCU_ControlMode FIFO DMA HLD S32DS35 RTD300    Example S32K344EVB_T172 LPUART_EMAC_Gateway IP S32DS368 RTD701    S32K358   S32K358 Multicore Start CM7_2 from CM7_0    Example S32K358 FlexCAN TXRX ISR S32DS35 RTD400/500   Example S32K358 GMAC 100M lwIP FreeRTOS S32DS 3.6.1 RTD600   Example S32K358 GMAC 1G lwIP FreeRTOS S32DS 3.6.1 RTD600   Example S32K358 GMAC lwIP FreeRTOS RDBESS S32DS 3.6.1 RTD600   Example_S32K358_XRDC_SEMA42_Multicore_v1_0_S32DS369_RTD701    S32K388 Example S32K388 GMAC0 lwIP FreeRTOS S32DS 3.6.1 RTD600   S32K389 Example S32K389 GMAC0 lwIP FreeRTOS S32DS 3.6.1 RTD 6.0.0   Example S32K389 GMAC1 SABRE lwIP FreeRTOS S32DS 3.6.1 RTD600  
View full article
示例 S32K118-SRAM-keep_data_over_SW_reset v0_1 S32DS.ARM.2.2 ******************************************************************************** * Detailed Description: * The purpose of this example is show how to keep data in SRAM memory over SW * reset. SW reset is triggered by pressing the SW3 button on the S32K118EVB. * Reset is delayed for 514 LPO cycles. In the RCM interrupt, SRAMU_RETEN is * cleared allowing to retain SRAM data during the reset. After SW reset, * SRAMU_RETEN is set to allow accesses to SRAM. * File startup_S32K116.S in modified to skip ECC RAM initialization for SW reset * source. To check whether stored data stayed unmodified in the SRAM, specified * address is read and the LED lights up. * ------------------------------------------------------------------------------ * Test HW: S32K118EVB-Q064 * MCU: S32K118 LAMLH 0N97V QTZE1802B * Fsys: fsys = 48MHz * Debugger: Lauterbach Trace32 * Target: Debug * Terminal: 19200-8-no parity-1 stop bit-no flow control * EVB connection: default ******************************************************************************** Revision History: Ver Date Author Description of Changes 0.0 May-17-2023 David Tosenovjan Initial version *******************************************************************************/
View full article
Example S32K344 UART Transmit & Receive Using DMA DS3.5 RTD300 *******************************************************************************  The purpose of this demo application is to present a usage of the  UART IP Driver for the S32K3xx MCU.  The example uses LPUART6 for transmit & receive five bytes using the DMA.  ------------------------------------------------------------------------------ * Test HW: S32K3X4EVB-T172 * MCU: S32K344 * Compiler: S32DS3.5 * SDK release: RTD 3.0.0 * Debugger: PE micro * Target: internal_FLASH ******************************************************************************** Putty output :-- Re: Example S32K344 UART Transmit & Receive Using DMA DS3.5 RTD300 Hi @Dinesh_Guleria , Can we use DMA without Autosar (RM CDD)?  Re: Example S32K344 UART Transmit & Receive Using DMA DS3.5 RTD300 @Dinesh_Guleria  do you have an example of DMA UART in RTD 4.0.0?
View full article
Ara2 Windows factory-test/runtime package unavailable I’m working with an Ara2 PCIe Accelerator on Windows. The hardware is detected correctly, PCIe/DMA initialization succeeds, and the AraProxyService is running. However, device initialization fails with the following error: Unsupported firmware version on device: 0 please update firmware. Current environment: Firmware: 14.34.0.0 Proxy: 1.1.0.0 SysAPI: 1.1.56.0 The Windows ARA2 User Guide references the factory-test-package-windows.zip file and the Qwen Windows demo package, but those attachments are not available to me through the article. Could someone from NXP please provide access to the current Windows factory-test package and the matching runtime/firmware package for the Ara2? This is currently blocking validation of the accelerator in an active Windows deployment.
View full article
Create a new configuration project using the S32CT 1 Table of Contents • Introduction • Prerequisites • Launch the S32 Configuration Tool • Create a New Configuration Project • Configure the Peripherals • Generate the Configuration Code • Link the Configuration to the Simulink Model • Debugging and Validation • References • Conclusion 2 Introduction The S32 Configuration Tool (S32CT) is NXP’s graphical configuration environment used to set up low-level MCU features such as pin muxing, clock trees, peripherals, and interrupts. When working with the NXP Model-Based Design Toolbox (MBDT), the configuration produced by S32CT is what allows the Simulink-generated code to correctly access peripherals like GPIO, ADC, CAN, LIN, SPI, or PWM on the target device. This article walks through the process of creating a new S32CT configuration project from scratch, linking it to a Simulink model, and preparing it for use in a Model-Based Design workflow on NXP S32K devices. 3 Prerequisites Before creating a new S32CT configuration project, make sure the following tools and components are available and properly installed: MATLAB & Simulink NXP Model-Based Design Toolbox (MBDT) S32 Design Studio (S32DS) with the S32 Configuration Tool component installed NXP RTD (Real-Time Drivers) package matching the target device Target hardware (e.g. S32K344-Q172, S32K358-Q289) USB / JTAG debugger (e.g. PEMicro Multilink) It is important that the S32CT version, the RTD package, and the MBDT release are mutually compatible. Version mismatches between these components are one of the most common causes of missing peripheral drivers, unresolved symbols during code generation, or configuration files that cannot be opened. The compatibility matrix is provided in the release notes shipped with each MBDT installation and should be consulted before starting a new project. It is also recommended to keep the S32CT project inside the same folder as the associated Simulink model. This makes the workflow easier to maintain, ensures relative paths remain valid when the project is shared or moved to another machine, and simplifies version control. 4 Launch the S32 Configuration Tool Step 1: Open S32CT from S32 Design Studio Launch S32 Design Studio From the top menu, select S32 Configuration Tools → Open S32 Configuration Tool Step 2: Open S32CT from Simulink (recommended for MBDT) Open your Simulink model Open Model Settings ( Ctrl + E ) Go to Hardware Implementation In the Configuration Project Template section, click the Open button next to the selected template When launched from Simulink, S32CT is automatically opened in the context of the currently selected hardware board. This ensures that the device family, part number, and package options are already aligned with the target you configured in the model, reducing the risk of manual selection errors. 5 Create a New Configuration Project Step 3: Start a new project In S32CT, select File → New → S32 Configuration Project Enter a meaningful project name, e.g. s32k344_led_blink_cfg Choose the project location — ideally the same folder as your Simulink model Step 4: Select the target device Choose the correct device family (e.g. S32K3) Select the exact part number (e.g. S32K344) Choose the correct package variant (e.g. 172 MAPBGA) Select the SDK / RTD version matching your MBDT installation The device, package, and SDK selection defines the set of peripherals, pins, and clock sources that will be available in the configuration views. Choosing a device that does not match the target hardware will lead to invalid pin assignments and code that will not run correctly on the board. Step 5: Confirm project creation Click Finish to create the project S32CT generates a .mex file that stores the full configuration The project opens automatically in the S32CT perspective 6 Configure the Peripherals S32CT provides several dedicated views, each responsible for a different aspect of the MCU configuration. For a basic LED blink example, the following are the most relevant: Step 6: Configure the Pins view Open the Pins tool Select the pin connected to the on-board LED (refer to the board schematic) Assign the pin to the SIUL2 / GPIO functionality Set the direction to Output Assign a meaningful label, e.g. DioLed0 Step 7: Configure the Clocks view Open the Clocks tool Select the desired clock source (FIRC, SIRC, FXOSC, PLL) Configure the system clock frequency (e.g. 160 MHz for S32K344) Verify that peripheral clock gates are enabled for the modules you use Step 8: Configure the Peripherals view Open the Peripherals tool Enable the Dio driver and add a Dio channel corresponding to the pin configured earlier Match the channel name (e.g. DioLed0 ) with the one that will be used in the Simulink Dio block Enable additional drivers (Port, Mcu, Platform) as required by the RTD stack The channel names, driver instances, and symbolic identifiers defined here are exactly the ones that will appear in the drop-down menus of the MBDT Simulink blocks. Keeping the naming consistent between S32CT and the Simulink model is essential for a clean, maintainable project. 7 Generate the Configuration Code Step 9: Update the code Click the Update Code button in the S32CT toolbar Review the list of files that will be created or modified Confirm the update to generate the C source and header files S32CT generates a set of static configuration files that describe the pin muxing, clock tree, and driver instances. These files are consumed at build time by the MBDT-generated code, which invokes the driver initialization functions ( Port_Init , Mcu_Init , Dio_Init , etc.) during system startup. Any change made in S32CT must be followed by a code update; otherwise the newly configured peripherals will not be visible to the Simulink model. Step 10: Save the project Save the .mex file ( Ctrl + S ) Verify that the generated files are located under the project folder Commit both the .mex file and the generated code to version control 8 Link the Configuration to the Simulink Model Step 11: Point Simulink to the S32CT project Open the Simulink model Open Model Settings ( Ctrl + E ) → Hardware Implementation In the Configuration Project Template section, browse to the newly created .mex file Apply and close the dialog Once linked, the Simulink model uses the S32CT project as its single source of truth for MCU configuration. Peripheral blocks from the MBDT library (Dio, Adc, Pwm, Can, Uart, …) automatically populate their parameter dialogs with the instances, channels, and signals defined in the .mex file. Step 12: Validate the link Add a Dio block from the MBDT library Open the block dialog and verify that DioLed0 appears in the Channel drop-down If the channel is missing, re-run Update Code in S32CT and refresh the block dialog 9 Debugging and Validation After the S32CT project is created and linked to Simulink, you can validate the configuration in several ways: Build the Simulink model ( Ctrl + B ) and confirm that no configuration-related errors are reported Inspect the generated files under the model build folder for the expected driver initialization calls Use the S32DS debugger to step through the startup sequence and verify that Port_Init , Mcu_Init , and Dio_Init execute correctly Use FreeMASTER or a UART console to confirm that the peripherals behave as configured on the target 10 References Quick Start Guide for S32K3X4EVB Board Model-Based Design Toolbox (MBDT) – How To S32 Configuration Tool User Guide RTD Reference Manual for the target device family 11 Conclusion Correctly using S32CT guarantees that the low-level MCU configuration and the high-level Simulink model remain aligned throughout the development cycle. This is a key enabler for a robust Model-Based Design flow on NXP S32 devices, especially in automotive projects that need to comply with AUTOSAR and functional safety requirements.
View full article
How to Enable Super Overdrive (SOD) Mode (2.0 GHz) on i.MX95 Some customer wants to know how to enable the SOD for MIMX9596DVZXQAC, commercial qualification in 19mm. They want to test the SOD mode which is A55 running at 2.0GHz, there is no any documentation in our NXP side explaining how to do that. Here this article give the describe and enable the Super Overdrive mode on the i.MX95. 1\Introduction the i.MX95 Voltage Operating Modes The i.MX power architecture is designed with the expectation that a dedicated PMIC supplies all required power rails, ensuring compliance with stringent power-up and power-down sequencing requirements. Majority of the digital logic is supplied with two supplies: VDD_ARM and VDD_SOC. VDD_ARM is for the CORTEXAMIX. VDD_SOC is for the rest of the modules in SoC. The VDD_SOC has following modes: Overdrive mode Nominal mode Underdrive mode Suspend mode The VDD_ARM has following modes: Super Overdrive mode Overdrive mode Nominal mode Underdrive mode Suspend mode The i.MX95 power management architecture is based on multiple performance setpoints controlled by the System Manager (SM). These setpoints control: Cortex-A55 operating frequency VDD_ARM voltage Power consumption Thermal dissipation The available performance modes are:PRK,LOW,NOM,ODV,SOD Where SOD (Super Overdrive) is available only on qualified 2.0 GHz capable devices such as MIMX9596DVZXQAC. In our datasheet we can see that for the part number only MIMX9596DVZXQAC A core support the 2.0 GHz. Details in the naming rules: For the operating ranges in our datasheet can see the details: Only the Cortex-A55 support the super overdrive mode, and for the typical voltage is 1.0V. In our reference design the VDD_ARM and VDD_SOC from different PMIC. And for the frequency of modules can also see in the datasheet, for the default setting is 1.8GHz, the maximum is 2004MHz. 2\ Enable Super Overdrive (SOD) Mode (2.0 GHz) on MIMX9596DVZXQAC Understanding about SOD mode:  The default NXP BSP SM (System Manager) code will automatically detect if the iMX 95 device it is running on is a 2.0 GHz capable device, and then the code will enable operation at 2.0 GHz with Super Overdrive voltage mode.  Linux on the iMX 95 only needs to request 2.0 GHz from the System Manager to enable it. Default BSP support code: In the download source code path : /imx95BSP/tmp/work/imx95_19x19_lpddr5_evk-poky-linux/imx-system-manager/2025q4/git/devices/MIMX95/sm/dev_sm_perf.c Or in our github source can see the code: imx-sm/devices/MIMX95/sm/dev_sm_perf.c at master · nxp-imx/imx-sm · GitHub The NXP BSP already contains logic to detect whether the device supports 2.0 GHz operation /* Check for 2+GHz device */ if (speedGrade >= 2000000000U) { /* 2+GHz devices support PRK, LOW, NOM, ODV, SOD setpoints */ s_perfNumLevels[PS_VDD_ARM] = DEV_SM_NUM_PERF_LVL_ARM; }  When the System Manager reads: speedGrade >= 2000000000 the BSP automatically: Enables the SOD performance level Enables 2.0 GHz OPP Manages required ARM voltage transitions The above code will enable the SOD without changing anything. Then in Linux you can use performance to run at 2.0GHz. Using the following command: echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor Then we can check the frequency and voltage of the VDD_ARM.  3\ Enabling SOD on a Non-2.0 GHz EVK (Evaluation Only) For evaluation on the EVK with the 1.8 GHz i.MX95, the process to enable 2.0 GHz and Super Overdrive voltage mode is to modify a single line of SM (System Manager) code so that 2 GHz is enabled even if the iMX 95 does not report 2 GHz operation is possible. Change this file: /MIMX95/sm/dev_sm_perf.c else { /* All other devices support PRK, LOW, NOM, ODV setpoints */ s_perfNumLevels[PS_VDD_ARM] = DEV_SM_NUM_PERF_LVL_ARM - 1U; }// This the the default running code for the 1.8GHz for the i.MX95 FROM: s_perfNumLevels[PS_VDD_ARM] = DEV_SM_NUM_PERF_LVL_ARM - 1U; TO: s_perfNumLevels[PS_VDD_ARM] = DEV_SM_NUM_PERF_LVL_ARM;//Force to work on the SOD mode.  Then rebuild the imx-system-manager and generate a new image. Write the images to the i.MX95 19x19 lpddr5 EVK board. Run the board and boot up. root@imx95-19x19-lpddr5-evk:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies 500000 900000 1404000 1800000 2004000 root@imx95-19x19-lpddr5-evk:~# cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq 2004000 BCU tool show that VDD_ARM is 1.0v when "running" at 2.0GHz and VDD_ARM is 0.9v when running at 1.8GHz, so the SOD is working. I did the the above change and tested on NXP imx95 1.8GHz 19x19 lpddr5 EVK board and the SOD worked 4\Summary So For the MIMX9596DVZXQAC the BSP is expected to automatically detect 2.0 GHz capability and enable SOD mode without source code modifications. EVK Modification The forced SM modification described above: DEV_SM_NUM_PERF_LVL_ARM is intended only for evaluation and debug purposes. It bypasses the normal speed-grade detection mechanism and should not be considered a production configuration for non-qualified devices. For the customer's MIMX9596DVZXQAC device: No BSP modification should be required. System Manager automatically checks the speed grade. If the device reports 2.0 GHz capability, SOD is enabled automatically. Linux only needs to request the highest CPU frequency. SOD operation can be verified by: Availability of 2004000 kHz CPU running at 2.0 GHz VDD_ARM increasing from ~0.9 V to ~1.0 V This confirms successful operation in Super Overdrive (SOD) Mode. IMX95EVK
View full article
MCXA153:LPSPI 数据突发传输。 你好, 参考手册 MCXA153 包含了对 TDBRn 和 RDBRn LPSPI 寄存器的描述: “TDBRn 和 RDBRn 寄存器支持向发送 FIFO 发送数据进行突发传输,以便与 DMA 控制器一起使用”。 请问有人可以分享一下使用这些寄存器进行突发传输的示例代码吗? 此致 博格丹 通信与控制(I3C | I2C | SPI | FlexCAN | 以太网 | FlexIO) MCXA Re: MCXA153: LPSPI data burst transfer. 嗨@bogdan_u 抱歉,目前没有相关示例。 我找到的最接近的 MCXA153 示例使用 LPSPI_MasterTransferEDMALite() 和 eDMA,但驱动程序通过 LPSPI_GetTxRegisterAddress() / LPSPI_GetRxRegisterAddress() 来定位 TDR/RDR,而不是突发别名窗口。 但我认为你可以尝试使用。 typedef struct { uint32_t cmd; uint32_t data[128]; } lpspi_burst_tx_t; static inline uint32_t LPSPI_TCBR_Address(LPSPI_Type *base) { return ((uint32_t)base + LPSPI_TCBR_OFFSET); } static inline uint32_t LPSPI_TDBR0_Address(LPSPI_Type *base) { return ((uint32_t)base + LPSPI_TDBR0_OFFSET); } static inline uint32_t LPSPI_RDBR0_Address(LPSPI_Type *base) { return ((uint32_t)base + LPSPI_RDBR0_OFFSET); } void LPSPI_StartTxBurstDMA(LPSPI_Type *base, edma_handle_t *txDmaHandle, uint32_t *cmd_plus_data, uint32_t nwords) { edma_transfer_config_t cfg = {0}; cfg.srcAddr = (uint32_t)&cmd_plus_data[0]; cfg.destAddr = LPSPI_TCBR_Address(base); cfg.srcOffset = 4; cfg.destOffset = 4; cfg.srcTransferSize = kEDMA_TransferSize4Bytes; cfg.destTransferSize = kEDMA_TransferSize4Bytes; cfg.minorLoopBytes = 4; cfg.majorLoopCounts = nwords + 1u; EDMA_ResetChannel(txDmaHandle->base, txDmaHandle->channel); EDMA_SetTransferConfig(txDmaHandle->base, txDmaHandle->channel, &cfg, NULL); EDMA_StartTransfer(txDmaHandle); LPSPI_EnableDMA(base, kLPSPI_TxDmaEnable); } void LPSPI_StartRxBurstDMA(LPSPI_Type *base, edma_handle_t *rxDmaHandle, uint32_t *rx_words, uint32_t nwords) { edma_transfer_config_t cfg = {0}; cfg.srcAddr = LPSPI_RDBR0_Address(base); cfg.destAddr = (uint32_t)&rx_words[0]; cfg.srcOffset = 4; cfg.destOffset = 4; cfg.srcTransferSize = kEDMA_TransferSize4Bytes; cfg.destTransferSize = kEDMA_TransferSize4Bytes; cfg.minorLoopBytes = 4; cfg.majorLoopCounts = nwords; EDMA_ResetChannel(rxDmaHandle->base, rxDmaHandle->channel); EDMA_SetTransferConfig(rxDmaHandle->base, rxDmaHandle->channel, &cfg, NULL); EDMA_StartTransfer(rxDmaHandle); LPSPI_EnableDMA(base, kLPSPI_RxDmaEnable); } BR 哈里
View full article
How to Recover Your Lost Bitcoin Without Falling Victim to Another Scam I never imagined I would become a victim of a cryptocurrency investment scam. Like many others, I was promised high returns and convinced that my investment was safe. What started as a promising cryptocurrency investment quickly turned into one of the most painful experiences I have ever faced. Like many people searching for financial growth and security, I trusted what appeared to be a legitimate investment platform. The website looked professional, the representatives were convincing, and genuine. Over time, I invested a total of €210,000 in Bitcoin, believing I was building a better future for myself and my family. Then, without warning, everything changed. When I tried to withdraw my funds, I encountered delays, excuses, and requests for additional payments. Soon after, communication stopped completely. It became painfully clear that I had fallen victim to a sophisticated scam. The emotional impact was overwhelming. I felt betrayed, embarrassed, and devastated. The money I had worked so hard to earn was gone, and with it went my confidence and peace of mind, countless moments of self-blame, and a growing fear that I would never recover from such a significant loss. During this difficult period, I regularly spoke with my therapist about what had happened. She saw how much the loss was affecting my mental health and overall well-being. she suggested that I reach out to Digital Light Solution Website https://digitallightsolution.com/, ; From my first interaction with their team, I felt something I had not felt in a long time—hope. They treated my case with professionalism, patience, and understanding. Most importantly, they listened. During one of the darkest periods of my life, Digital Light Solution their guidance and support helped me regain confidence and take positive steps forward. Today, I share my story not only to express my gratitude but also to warn others. Cryptocurrency scams are becoming more sophisticated every day. Fake investment platforms, romance scams, and online job scams are destroying lives and draining the savings of innocent people around the world. If there is one lesson I learned from this experience, it is this: always do thorough research before investing, never trust promises of guaranteed returns, and remain vigilant online. Losing your hard-earned money can be devastating, but awareness and caution can help protect others from experiencing the same heartbreak. Email:[email protected] WhatsApp +19548568045, https://wa.link/989vlf Re: How to Recover Your Lost Bitcoin Without Falling Victim to Another Scam A group of cryptocurrency investors reportedly suffered a combined loss of approximately $2.3 million after becoming victims of a fraudulent Decentralized Autonomous Organization (DAO). The project was presented as a revolutionary investment opportunity, supported by professional-looking websites, promotional material, and testimonials designed to create an appearance of legitimacy. After investors deposited their cryptocurrency into the project’s smart contract, the fraudsters allegedly exploited a hidden backdoor within the contract and transferred the deposited assets to other wallet addresses. The sudden loss left the victims searching for answers and trying to determine whether their funds could be traced. TECHY FORCE CYBER RETRIEVAL (TFCR) was brought in to assist with the investigation. The process began with collecting transaction hashes, wallet addresses, smart-contract information, screenshots, communications, and other available evidence relating to the investment. TFCR then used blockchain-analysis techniques to examine the transactions and follow the movement of the cryptocurrency between wallets. Investigators can analyze transaction patterns, identify intermediary addresses, and document transfers that may help establish how the stolen assets moved through the blockchain. The investigation highlights an important characteristic of cryptocurrency: although transactions are generally irreversible, many blockchains maintain publicly accessible transaction records. These records can provide investigators with valuable information when reconstructing the movement of digital assets. For victims of fraudulent DAO schemes, preserving transaction information and reporting the incident promptly can be important. Blockchain tracing does not guarantee that stolen cryptocurrency will be recovered, but it can help establish an evidence trail that may support further investigation, exchange intervention, legal proceedings, or law-enforcement action. REACH OUT TO TECHY FORCE CYBER RETRIEVAL  (@)TECHCYBERFORC     Website  https://techyforcecyberretrievals.com Re: How to Recover Your Lost Bitcoin Without Falling Victim to Another Scam The Hidden Impact of a Crypto Scam: The Shame, the Silence and the Struggle to Move Forward People often talk about the financial loss that comes with falling victim to a cryptocurrency scam. They talk about the money, the transactions, the warning signs that may have been missed and the difficulty of recovering what was lost. But there is another side to these experiences that rarely receives the attention it deserves. It is the emotional toll. And sometimes, that can be far more difficult to live with than the financial loss itself. Being scammed does not simply mean losing money. It can mean losing confidence in yourself, questioning your own judgement and struggling to understand how something like this could happen to you. You may find yourself replaying conversations, revisiting decisions and wondering how you did not see what now seems so obvious. Then comes the shame. You start searching online for answers, hoping to find someone who understands what you are going through. Instead, you come across blog posts, articles and comment sections filled with cruel remarks. People calling victims stupid, careless, greedy or foolish. People asking how anyone could possibly fall for such an obvious scam. And suddenly, the pain becomes even harder to carry. You already know you made a decision that cost you dearly. You do not need strangers on the internet reminding you of it. What many people fail to understand is that scams are designed to deceive. The people behind them often invest considerable time and effort into building trust, creating convincing stories and manipulating emotions. They know how to make their schemes appear legitimate. Being deceived does not make someone stupid. It makes them human. The self doubt can be overwhelming. You may become suspicious of everyone, even those who genuinely want to help. You might feel embarrassed speaking to friends or family, afraid of being judged or hearing the dreaded words, "How could you let that happen?" Some people withdraw completely, carrying the experience in silence because explaining it feels almost as painful as living through it. But you do not have to go through that process alone. Sometimes, the most meaningful support comes from people who have walked a similar path. People who understand the sleepless nights, the regret, the anger, the embarrassment and the feeling of having your trust taken advantage of. People who do not need a lengthy explanation to understand why you are hurting. That is why 4victimsbyvictims community exists. It is a community established by victims, with the intention of creating a space where people affected by scams can connect with others who understand first hand what the experience feels like. It offers an opportunity to speak openly, share experiences and find reassurance among people who know that the impact of a scam goes far beyond a bank balance. If you have been affected by a cryptocurrency scam or any other type of fraud, consider visiting 4victimsbyvictims . org. You can also reach out by email at support @ 4victimsbyvictims .org. You do not have to pretend that you are fine. You do not have to hide what happened or allow the judgement of others to define you. And you certainly do not have to accept the idea that being scammed makes you less intelligent, less capable or less deserving of respect. What happened to you matters. Your feelings matter. And so does your recovery. There is life beyond the scam, even if it takes time to see it. The first step towards moving forward may simply be finding someone who understands and realising that you are not alone.
View full article
kw47 lpuart 您好: 根据官方例程 kw47loc_wireless_uart_freertos 修改并验证串行通信。仅修改 Uart_RxCallBack 和波特率。修改内容如下: 为了方便测试,目前每次通过串口发送 20 字节。测试发现,当波特率低于 256000 时,接收和发送均无问题。当波特率设置为 460800 或更高时,kw47 发送正常,但在接收过程中会发生丢包。 请问您能否帮我检查一下我的使用方法是否正确,并给我一些指导? 另外,为什么 sdk_26_03_00 中没有 kw47loc_freertos_lpuart_cm33_core0 例程? 谢谢!
View full article
MCUXpressoで「転送送信」が有効になっている場合に、無効なeDMAコードが生成される(MCXN547) こんにちは、 MCUXpresso Config Tools v26.xをMCXN547プロジェクトで使用し、eDMAペリフェラルコンポーネントを使ってADC -> eDMA転送を設定しています。 構成: eDMAチャネルAPIモード:トランザクション(転送設定) eDMAリクエスト: ADC1 FIFO Aリクエスト 送金送信:有効 自動停止リクエスト:有効 周辺要求:有効 peripherals.cで生成されたコード には以下が含まれます: status = EDMA_SubmitTransfer(&DMA0_CH0_Handle, DMA0_CH0_Transfers_config, 1U); assert(status == kStatus_Success); しかし、ステータスの宣言は生成されません。その結果、プロジェクトはコンパイルに失敗します。 error: 'status' undeclared (first use in this function) 生成されるコードは以下のいずれかになります。 status_t status; status = EDMA_SubmitTransfer(...); または: assert(kStatus_Success == EDMA_SubmitTransfer(...)); この問題に遭遇したことがある方はいらっしゃいますか? これはConfig Toolsにおける既知のコード生成バグでしょうか、それとも「転送を送信」を使用する際に必要な追加の設定オプションがあるのでしょうか? 必要に応じて生成されたペリフェラル.cと.mexの設定も提供できます。 ありがとうございます。 ボード設計 MCX N Re: MCUXpresso generates invalid eDMA code when "Submit transfer" is enabled (MCXN547 ) ハイ 迅速なご対応ありがとうございます。 はい、ツールのバージョン26.03を持っています。 プロセッサー: MCXN547(2020年3月26日) - MCX MCXN MCUXpresso SDK バージョン 25.13.00 パッケージ:mcuxsdk-core バージョン:2.0.0 DMA0転送構成の「すべての転送をループ」に、このコードをDMA0_init()に追加します。 /* DMA0 ループ転送送信 */ status = EDMA_SubmitLoopTransfer(&DMA0_CH0_Handle, DMA0_CH0_Transfers_config, 1U); assert(status == kStatus_Success); 「ステータス」がどこにも宣言されていない場合。 Re: MCUXpresso generates invalid eDMA code when "Submit transfer" is enabled (MCXN547 ) こんにちは、 @tjo_dkさん。 投稿ありがとうございます! どのMCXN547パッケージを使っているのか教えていただけますか? 使用しているConfig Toolsのバージョンは何ですか?26.03でしょうか? どのSDKバージョンをインストールしていますか? 私の環境で同様の設定を行うために、この情報を共有してください。 Re: MCUXpresso generates invalid eDMA code when "Submit transfer" is enabled (MCXN547 ) こんにちは、 @tjo_dk さん。 あなたと同じ構成で、同様の問題を再現しようと試みました。しかし、私の環境では、コードプレビューにはすでにDMA0_init関数内でステータス変数の宣言が含まれています。
View full article
IMX93 SAI - シンプルオーディオカードデバイスツリー設定 こんにちは、simple-audio-cardのデバイスツリー設定を探しています: -imx93 はマスターです -オーディオコーデックはスレーブTDM 16スロット/32ビット そして、以下のタイミングが守られる必要があります。 どんなヒントでもありがたいです Linux Re: imx93 sai - simple-audio-card devicetree settings こんにちは、 残念ながら、i.MX93のTDMでSAIポートをスレーブとして構成するためのデバイスツリーの例は提供しておりません。 参考文献としては以下の投稿を参考にしてください: https://community.nxp.com/t5/i-MX-Processors/How-should-I-write-a-dts-file-to-use-16ch-TDM-with-quot-simple/mp/1625768#M203519 よろしくお願いいたします。
View full article
关于 RDBESS774A3EVB 的咨询 - 由于连接器(J1_1 和 J1_3)互换导致的板损坏 您好, 我目前正在评估RDBESS774A3EVB电池监控单元 (CMU) 板(采用 MC33774A 电池单元控制器),该板连接到 50 节电池组设置。 最近,我们在测试过程中发生了一起意外的连接错误。我们错误地将J1_1 (上部)和J1_3 (下部)之间的电池连接器组互换了。 事件发生期间观察到以下行为: 初始事件:连接器互换后,第 36 单元立即发生严重短路,导致外部电线/线路烧毁断裂。 后续措施:发现错误后,我们使用正确的连接器位置将电池组重新连接到同一块电路板上。 次要行为:一旦建立了正确的连接,板上的多个平衡电阻器(R_balance)就开始过热并烧毁。 基于以上情况,我们非常希望您能就以下问题提供工程方面的见解: Q1:在第一次事件中,J1_1 和 J1_3 之间的初始连接器互换是否对 MC33774A IC 或相关电路造成了灾难性的内部损坏? Q2:假设在第二次(正确的)连接期间多个平衡电阻烧毁是由于第一次事故造成的 MC33774A IC 内部损坏(例如,内部 FET 击穿或栅极驱动器卡在导通状态)的直接结果,这种假设是否正确? Q3:如果我们更换损坏的MC33774A IC和所有烧毁的平衡电阻,RDBESS774A3EVB板能否恢复到完全功能和安全的工作状态?除了主集成电路之外,是否还有其他重要的配套组件(例如静电放电/齐纳保护二极管或隔离电路元件)需要检查或更换? Re: Inquiry regarding RDBESS774A3EVB - Board Damage due to Swapped Connectors (J1_1 and J1_3) 嗨@guoweisun , 我们没有将整个 50 节电池组连接到一个连接器上。相反,我们的 50 单元系统分为三个独立的部分,并配有三个不同的单元连接器。 1 Initial Event ERROR: CONNECTOR SWAP1 Initial Event ERROR: CONNECTOR SWAP1 Initial Event ERROR: CONNECTOR SWAP1 Initial Event ERROR: CONNECTOR SWAP1 Initial Event ERROR: CONNECTOR SWAP1 初始事件错误:连接器交换 2 Subsequent Action: NORMAL CONNECTION2 Subsequent Action: NORMAL CONNECTION2 Subsequent Action: NORMAL CONNECTION2 Subsequent Action: NORMAL CONNECTION2 Subsequent Action: NORMAL CONNECTION2 后续操作:正常连接 Re: Inquiry regarding RDBESS774A3EVB - Board Damage due to Swapped Connectors (J1_1 and J1_3) 你是说你把50*3.6V加错了吗?MC33774 第一部分中 C17 到地之间的电压是多少? Re: Inquiry regarding RDBESS774A3EVB - Board Damage due to Swapped Connectors (J1_1 and J1_3) 嗨@guoweisun , 为了确保硬件的功能安全并防止任何潜在的接线问题,我们设计了一个中间“CSU 桥接板” ,将我们的 50S 电池组连接到 RDBESS774A3EVB(采用菊花链连接三个 MC33774A AFE)。 请您查看我们附上的原理图( CSUBridge_Connector.png和CSUBridge_Block Diagram.png ),并确认我们的引脚映射和连接方式是否正确?   Re: Inquiry regarding RDBESS774A3EVB - Board Damage due to Swapped Connectors (J1_1 and J1_3) 似乎没有发现其他问题,但请注意 GDN1 GND2 GND3 的位置。 Re: Inquiry regarding RDBESS774A3EVB - Board Damage due to Swapped Connectors (J1_1 and J1_3) 感谢您一直以来的支持。首先,我们想澄清一下我们实际硬件配置中的 AFE 堆叠顺序,以确保我们保持一致: AFE1 (J1_1)指定用于高压级(单元 37–50)。 AFE3 (J1_3)指定用于低电压级(单元 1–18)。 我们附上了一张图片,其中记录了我们最近的发现以及我们目前面临的关键问题。 我们希望您能就之前提出的关于第一次事件的问题,以及新董事会提出的新问题,给出明确的答复: 【第一部分:对第一次板的回顾性问题】 Q1:在第一次事件中,J1_1 和 J1_3 之间的初始连接器互换是否对 MC33774A IC 或相关电路造成了灾难性的内部损坏? Q2:假设在第二次(更正后的)连接过程中多个平衡电阻烧毁是由于第一次事故造成的 MC33774A IC 内部损坏(例如,内部 FET 击穿或栅极驱动器卡在导通状态)的直接结果,这种假设是否正确? Q3:如果我们更换损坏的MC33774A IC和所有烧毁的平衡电阻,RDBESS774A3EVB板能否恢复到完全功能和安全的工作状态?除了主集成电路之外,是否还有其他重要的配套组件(例如静电放电/齐纳保护二极管或隔离电路元件)需要检查或更换? 【第二部分:新董事会带来的新问题】 按照上述正确的堆叠顺序(高压端接 AFE1/J1_1,低压端接 AFE3/J1_3),我们尝试使用全新的 RDBESS774A3EVB 板来测试我们的系统。 然而,一接上电源,就立即冒烟,高压段(37-50 节电池/AFE1)上的平衡 IC(MC33774A)再次损坏。 鉴于连接映射完全按照预期进行(高对高,低对低),请问您能否帮助我们分析一下为什么新板在 AFE1 阶段立即失效? Re: Inquiry regarding RDBESS774A3EVB - Board Damage due to Swapped Connectors (J1_1 and J1_3) 嗨@guoweisun , 我们目前遇到一个严重的问题,即在多个电池组依次连接时,均衡IC会损坏。 根据当地 NXP 技术建议,对于我们第 1 组部分(监控 14 个电池单元)上未使用的通道,我们已将未使用的引脚直接连接到平衡 IC 输入端,具体如下: CB15-18 与 CB14 短路 CT15-18 与 CT14 连接短路 以下是我们的测试流程详情及相应结果: 测试 1:单组连接(仅限组 1) 步骤:我们只连接了第 1 组,该组对应于最高电位段:电池 37 至电池 50(共 14 个电池,总电压约为 100 伏)。50V)。 结果:板运行正常。我们能够准确读取所有电池的电压。VBAT_1 相对于 GND_1 的测量电压稳定在约 50V。未发现异常情况。 测试 2:完整的 3 组连接(顺序上电) 步骤:我们将所有 3 个细胞组同时连接起来,但严格按照从下到上的插入顺序,从第 3 组(底部细胞)开始,一直到第 1 组(顶部细胞)。 结果:连接完成后,电阻 R1_1(10 欧姆)附近出现烟雾和可见的烧焦痕迹。我们立即切断电源以防止进一步损坏,并检查了电路板。 事后分析及损害分析: VBAT_1 至 GND_1 短路:电气测试显示 VBAT_1 和 GND_1 之间存在短路。由于这条电源线直接连接到平衡集成电路,我们怀疑是内部硅芯片故障。 电阻器 R1_1:发现 10 欧姆电阻器已烧毁开路(开路)。 CT 和 CB 引脚:检查了 CT 和 CB 引脚;未发现这些引脚有任何物理或电气损坏。 平衡电阻:检查了所有外部电池平衡电阻;所有电阻均完好无损。 IC 根本原因验证:我们从 PCB 上拆焊了平衡 IC,以隔离问题。对未安装的集成电路进行测试,证实 VBAT 和 GND 引脚之间存在永久性内部短路。 向恩智浦技术支持提出的问题: 鉴于单独给第 1 组供电时配置工作完美,当所有三组依次(从下到上)插入时,什么会触发平衡 IC 内部的 VBAT 到 GND 故障? 将未使用的引脚短接(CB15-18 到 CB14,以及 CT15-18 到 CT14)的终端方法是否会在多芯片菊花链热插拔过程中引起意外的瞬态或闩锁情况? 为了缓解这种故障模式,我们需要实施哪些具体的热插拔保护、TVS 调整或上电顺序限制? 请帮助我们分析并提出解决此问题的建议。
View full article
树莓派摄像头 V1.0i.MX93 CSI-2 接口无法正常工作 大家好, 我们使用的是NXP i.MX93板。NXP MIPI CSI-2(2 通道)摄像头工作正常。 我们还尝试连接了 Raspberry Pi Camera Module V1.0,它使用 CSI-2 2 通道接口。Linux 系统中已安装了相应的相机驱动程序,但相机无法工作,也无法访问。 请问您能否帮我们找出根本原因?要在 i.MX93 上支持 Raspberry Pi 摄像头,是否需要额外的设备树配置、驱动程序修改或 MIPI CSI-2 兼容性要求? 如有需要,请与我们联系是否需要任何日志或调试信息。 谢谢。 Re: Raspberry Pi Camera V1.0 Not Working on i.MX93 CSI-2 Interface 你应该检查哪些内容(实用调试清单) 步骤 1:验证 I2C 基本通信 i2cdetect -y dmesg | grep imx219 / ov5647 关键问题: 检测到问题但探测失败 → 时钟/RESET问题 未检测到 → 硬件/引脚/电源问题 步骤 2:检查时钟输出 确认: CLK引脚实际上输出波形 频率校正(24/25 MHz) 步骤 3:验证 RESET/掉电 GPIO 确保DTS包含以下内容: RESET GPIOS = <...>; pwdn-gpios = <...>; 测试: 手动切换(调试打印或 GPIO sysfs) 步骤 4:与 NXP 摄像机 DTS 进行比较 使用: 来自电路板支持包的 OV5640 或 AP1302 DTS 比较: 端点 端口 车道配置 步骤五:检查媒体图表 media-ctl -p 确认管道已完成。 步骤 6:确认车道配置 不匹配示例: 数据通道 = <1 2>; 时钟通道 = <0>; 配置错误 → 无流 推荐: 方案A(项目推荐方案): 使用NXP 认证的摄像头模块→ 可节省数周的启动时间 方案 B(如果必须使用树莓派摄像头): 你需要: 完全端口传感器驱动器调校: 时钟频率 链路频率 MIPI 时序 仔细对齐: 电源序列 复位时序 调整 DTS + 管道 预计需要付出相当大的努力。
View full article
s32k142 LPUART0 单线模式无法发送数据 我正在将 LPUART0 设置为多路复用 UART 模式,并使用一个外部 10K 电阻将其上拉至 3.3V。将其配置为单线UART后,我无法发送数据。请帮我排查一下这个问题。 void LPUART0_init(void) {     PCC->PCCn[PCC_LPUART0_INDEX]&= ~PCC_PCCn_CGC_MASK;        PCC->PCCn[PCC_LPUART0_INDEX] |= PCC_PCCn_PCS(0b010) | PCC_PCCn_CGC_MASK;       LPUART0 ->BAUD = LPUART_BAUD_OSR(15) | LPUART_BAUD_SBR(52);     uint32_t ctrl_value = 0;     ctrl_value |= LPUART_CTRL_LOOPS_MASK; // LOOPS = 1     ctrl_value |= LPUART_CTRL_RSRC_MASK; // Rsrc=1     ctrl_value |= LPUART_CTRL_TE_MASK; // TE = 1     ctrl_value |= LPUART_CTRL_RE_MASK; // RE = 1     ctrl_value |= LPUART_CTRL_RIE_MASK; // RIE = 1(如需)   LPUART0->CTRL = ctrl_value; // 一次性赋值   }   PB1的配置为: PORTB ->PCR[1] = PORT_PCR_MUX(2);   发送时,先将TXDIR置为高电平,发送完成后再将其复位: LPUART0->CTRL |= LPUART_CTRL_TXDIR_MASK; 发送数据 LPUART0->CTRL&= ~LPUART_CTRL_TXDIR_MASK; Re: s32k142 LPUART0 singleWire mode cannot send data 捕获 I2C 总线波形并将上拉电阻修改为 4.7K 也可能会有所帮助 Re: s32k142 LPUART0 singleWire mode cannot send data 你好@sssPPP  根据您分享的代码,LOOPS 和 RSRC 位的配置是正确的: LPUART0->CTRL |= LPUART_CTRL_LOOPS_MASK; /* Enable loop/single-wire mode */ LPUART0->CTRL |= LPUART_CTRL_RSRC_MASK; /* Select single-wire mode */ 但是,在修改这些位之前,务必确保发射器和接收机均处于禁用状态: LPUART0->CTRL &= ~(LPUART_CTRL_TE_MASK | LPUART_CTRL_RE_MASK); 然后,在开始传输之前,应设置传输方向并启用发射器: LPUART0->CTRL |= LPUART_CTRL_TXDIR_MASK; /* Set transmit direction */ LPUART0->CTRL |= LPUART_CTRL_TE_MASK; /* Enable transmitter */ 最后,在将数据写入 DATA 寄存器后,请务必等待“传输完成”标志 (TC) 触发,而不仅仅是“发送数据寄存器清空”标志 (TDRE),然后再将引脚切换回接收模式。这是为了防止 LPUART 在字节完全传输之前释放单线线。 在主题“S32K344 单线 UART 模式”中也讨论过这一点,其中 TXDIR 信号的正确时序对于确保传输正常至关重要。 BR、VaneB
View full article
I tried running Zephyr HTTP Server on FRDM-MCXN947 (Japanese blog) 0. What is this article about? When using network functionality with embedded microcontrollers, traditionally, you had to start by figuring out "how to make it work." You'd have to find the SDK and sample code provided by the vendor of the microcontroller you wanted to use, and then write code according to its API. Since the API changes with each different microcontroller, you often end up having to research everything from scratch every time you want to do something similar. With network functionality, there's a lot to learn, such as initializing the TCP stack and using the socket API, and I'm sure many people have experienced running out of steam before they could even write their own application. Zephyr OS can be one solution to these problems. Zephyr provides a standard API as an RTOS, and a major advantage is that once you learn how to use it, the same code will run on different boards. Among the abundant sample code available, there is also the HTTP server sample that we will be discussing, and it was surprisingly easy to get running. This article provides a step-by-step guide on how to run the HTTP server sample on the NXP FRDM-MCXN947 evaluation board. Once the sample is running, you will be able to access the FRDM-MCXN947 from your PC's web browser and turn the LEDs on the board ON/OFF using buttons on the page. goal: Access the HTTP server on the FRDM-MCXN947 from your browser and control the LEDs using the "LED on" and "LED off" buttons on the page. Before reading this article This assumes that the Zephyr build environment is already installed and that you are familiar with the basic operations of west build and west flash . If you're starting from setting up the environment, you can refer to the " Getting Started Guide " on the Zephyr official website, or the guide video that allows you to easily set it up using MCUXpresso for VSC. Let's get started! See "MCUXpresso with VS Code and Zephyr OS". table of contents 0. What is this article about? 1. What you will need 1.1 Hardware 1.2 Software (must be installed) 2. Preparation: Activate environment variables 3. Configuring prj.conf (specifying the IP address) 3.1 When using a static IP address 3.2 Using DHCP (Automatically obtaining an IP address) 3.3 When connecting the PC and the board directly on a one-to-one basis 4. Build 4.1 In the case of a static IP address 4.2 When using DHCP 5. Writing to the board 6. Operation check 6.1 Check the IP address using the serial terminal 6.2 Accessing from a browser Reference materials 1. What you will need 1.1 Hardware Product name remarks FRDM-MCXN947 Evaluation Board Zephyr Documentation USB cable (included with the FRDM board mentioned above) This connects the board's J17 connector to the PC. LAN cable This connects the board's Ethernet connector to the network. 1.2 Software (must be installed) Latest Zephyr development environment (west, Zephyr SDK)   2. Preparation: Activate environment variables This time, we'll proceed using commands from the macOS Terminal screen. Once you open the terminal, first execute the following two commands. First, activate the Python execution environment: source ~/zephyrproject/.venv/bin/activate If installed using MCUXpresso for VSC The location of bin/activate is different from the standard. On macOS, it's located in ~/.mcuxpressotools/.venv_3_14/ . On Windows, it was located in C:\Users\<ユーザ名>\.mcuxpressotools\.venv_3_12\Scripts . *When using Windows PowerShell, the commands and filenames used will differ from those on Linux and macOS, so please refer to the " Getting Started Guide " before proceeding. Next, we'll set the environment variables required to build Zephyr. This command will allow you to build Zephyr from any folder: source ~/zephyrproject/zephyr/zephyr-env.sh Next, navigate to the sample folder: cd ~/zephyrproject/zephyr/samples/net/sockets/http_server   3. Configuring prj.conf (specifying the IP address) The prj.conf file in this folder contains network settings. Please choose from the following three methods according to your connection type. section Connection type IP setting method Section 3.1 Connect to the LAN via a router Manually configure a static IP address. Section 3.2 Connect to the LAN via a router Automatic acquisition via DHCP (easy) Section 3.3 Connect the PC and the board directly with a single LAN cable. Set a static IP address for both the PC and the board. Reference: IP Address: Static and CHCP 3.1 Using a static IP address (via a router) This method involves connecting to the LAN via a router and assigning a fixed IP address to the board. Open prj.conf in a text editor and rewrite the following two lines to match your network environment. Before change (default): CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1" CONFIG_NET_CONFIG_MY_IPV4_GW="192.0.2.2" After the change (example): CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.168.1.100" CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.1.1" Setting items meaning CONFIG_NET_CONFIG_MY_IPV4_ADDR The IP address to assign to the board (specify an address within the router's subnet that does not overlap with other devices). CONFIG_NET_CONFIG_MY_IPV4_GW The IP address of the gateway (router). This is not strictly necessary if you are only accessing it from a PC within the same LAN. The subnet mask is not specified here, but in the environment I tested, it was set to 255.255.255.0 . This article uses "192.168.1.100" as an example. Please change it to match your network environment. 3.2 Using DHCP (Automatically obtaining an IP address) When connecting the FRDM-MCXN947 to a router (wireless router), it can automatically obtain an IP address from the router. To do this, make the following changes to prj.conf : CONFIG_NET_DHCPV4=y # 追加 CONFIG_NET_CONFIG_MY_IPV4_ADDR="" # 空文字列に変更 Alternatively, you can choose not to edit prj.conf and instead specify the configuration file using the build command described later (see Section 4.2 ). 3.3 When connecting the PC and the board directly on a one-to-one basis It can also be operated by directly connecting the PC and the FRDM-MCXN947 with a single LAN cable, without using a router. In this case, since there is no DHCP server, you will need to manually set a static IP address on both the PC and the board. The key points are the following two: Assign different IP addresses to the PC and the board within the same subnet . Since it will not connect to the internet, gateway settings are not required (or any value is acceptable). Here is an example of the settings: subject IP address Subnet mask PC (wired LAN adapter) 192.168.100.1 255.255.255.0 FRDM-MCXN947 192.168.100.2 255.255.255.0 (Automatic setting) On the board side, edit prj.conf in the same way as in Section 3.1. Example settings when using the values from the table above: CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.168.100.2" CONFIG_NET_CONFIG_MY_IPV4_GW="192.168.100.1" The IP address of the wired LAN adapter on the PC side is set manually from the OS settings screen: macOS: Go to "System Preferences" → "Network" → Select your wired LAN adapter → Change "IP Settings" to "Manual" and enter the address 192.168.100.1 and subnet mask 255.255.255.0 Windows: Go to "Control Panel" → "Network and Sharing Center" → "Change adapter settings" → Right-click on the wired LAN adapter → "Properties" → "Internet Protocol Version 4 (TCP/IPv4)" → Select "Use the following IP address" and enter the same information. If DHCP is available , the standard configuration of connecting to a router (Section 3.2) is easier as it does not require changing the PC's IP settings. Direct connection is useful for testing in locations without a router or when you don't want to change the PC's network settings. 4. Build Once the setup is complete, proceed with the build (compilation and linking). The working directory is "~/zephyrproject/zephyr/samples/net/sockets/http_server". 4.1 If you have a static IP address, or if you have configured the system to use DHCP in prj.conf Build it with the following command. west build -p auto -b frdm_mcxn947/mcxn947/cpu0 4.2 When using DHCP prj.conf To enable DHCP without editing the file, run the following command: west build -p auto -b frdm_mcxn947/mcxn947/cpu0 -- -DEXTRA_CONF_FILE="overlay-dhcpv4.conf" -DEXTRA_CONF_FILE="overlay-dhcpv4.conf" This will result in the configuration file for enabling DHCP being added to prj.conf during the build process. In this configuration, if the DHCP server is not enabled, the static IP address written in prj.conf will be set by default.   5. Writing to the board Once the build is complete, write it to the board. Connect the board's J17 (USB) connector (to the left of the Ethernet connector) to your PC using a USB cable, and connect a LAN cable to the Ethernet connector . Run the following command: west flash Once the writing process is complete, the board will start operating.   6. Operation check 6.1 Check the IP address using the serial terminal Open a serial terminal (such as Tera Term, PuTTY, or VS Code's Serial Monitor), select the FRDM-MCXN947 port, and set the baud rate to 115200 . There are several types of serial terminals available, and you can use whichever you prefer. Please refer to separate articles for information on their installation and usage. uart:~$ When you see the prompt, enter the following command: net iface A list of network settings will be displayed. If you specified a static IP address, that value will be displayed; if you used DHCP, the IP address assigned by the router will be displayed, so please check that address. If you miss the startup log, you can restart the board by pressing the SW1 (RESET) button on the board. You can also check the IP address in the output immediately after restarting. 6.2 Accessing from a browser Enter the confirmed IP address into your browser's address bar and access it (in this example, http://192.168.1.100 ). If it is working correctly, a page containing " LED on " and " LED off " buttons will be displayed. Pressing these buttons will turn the green LED on/off on the FRDM-MCXN947. Reference materials [Zephyr ® Series] Part 1: What kind of OS is the recently popular Zephyr OS? (Japanese Blog) [Zephyr ® Series] Part 2: First Build and Testing (Japanese Blog) Zephyr Project Getting Started Guide Let's get started! Zephyr OS with MCUXpresso and VS Code (Guided Video) Trying out UI: GUI Guider sample code on Zephyr OS (Japanese blog) Change history: 2026-06-16: First Edition ========================= We are currently unable to respond to comments left in the "Comment" section of this post. We apologize for the inconvenience, but please refer to "Technical Questions to NXP - How to Contact Us (Japanese Blog)" when making an inquiry. (If you are already an NXP distributor or have a business relationship with NXP, you may ask your representative directly.) This guide provides a step-by-step explanation of how to run the Zephyr HTTP server sample on the FRDM-MCXN947 and turn the LEDs on the board ON/OFF from a PC browser. It supports both fixed IP/DHCP connections via a router and direct connections between the PC and the board using a single LAN cable. If the Zephyr build environment is already installed, you can verify operation from editing the configuration file to building and flashing with just a few commands. (Estimated time: 15 minutes *Assuming Zephyr development environment is installed and you are familiar with PC networking) Ethernet Introduction MCX Japanese Blog
View full article
如何使用 S32K 的编译脚本? 各位恩智浦专家:   目前,我使用 IDE("S32 Design Studio for S32 Platform 3.4" )手动编译项目。 我能否通过脚本在项目中执行清理、刷新、构建和切换链接文件等操作? 这样一来,我就能实现部分自动编译,而无需打开 IDE 进行操作。 Re: How to use the compilation script for S32K? 谢谢你,petervlna!  我试试看,非常感谢! Re: How to use the compilation script for S32K? 你好 是的,你可以在不打开 IDE GUI 的情况下自动版本 S32 Design Studio。S32 设计工作室基于 Eclipse,你可以利用 Eclipse 无头编译机制进行命令行编译。 您可以在以下链接中找到教程: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/S32DS-list-of-HOWTOs/ta-p/1113475 对于命令行界面: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/HOWTO-S32-Design-Studio-Command-Line-Interface/ta-p/1112410 顺祝商祺! Peter
View full article
S32K311チップはPIT(割り込み処理)を介して割り込みソフトウェア環境に入ることができません。(S32DS 3.6.0)RTD 6.0.0 プログラムは実行中に割り込みを発生させず、pit_notifaction も呼び出しませんでした。 ソフトウェア環境:S32DS 3.6.0RTD 6.0.0 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 テストのために関数内にブレークポイントを設定しましたが、関数が呼び出されませんでした。考えられる原因は何でしょうか?カウンターは正常にカウントしていますが、割り込みが発生していません。 ソフトウェアのバージョンが異なると、何か影響はありますか? Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 こんにちは、 @Finnc 現在、私はS32K311ボードにアクセスできません。しかし、同じ構成とコードをFRDM-A-S32K312でテストしたところ、PitNotificationが呼び出され、カウンタが期待どおりに増加することを確認しました。 通知関数が呼び出されているかどうかを確認するために、通知関数内にブレークポイントを設定していただけますか? BR、VaneB Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 全速で走行している場合、pit_notifactionは入力されず、PitCountの値は0のままです。一時停止時のレジスタのパラメータを図に示します。 クロック設定に関係していますか?設定は以下のとおりです。 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 こんにちは、 @Finnc あなたのコードで確認できる通り、カウンターはPitNotificationが呼び出されたときにのみ増加します。これは、PIT割り込みが正しくトリガーされていることを示しています。 よりシンプルで分かりやすいテストを行うには、PitNotification 関数内で printf を使用してカウンター値を出力することができます。表示された値を確認できれば、割り込みが想定どおりに実行されていることがさらに確認できます。 例えば、私は以下のように実装しました。 また、printfの設定方法についてサポートが必要な場合は、 「S32DS 3.5でprintf関数を使用する方法」というスレッドを参照してください。 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 こんにちは、 @Finnc S32K311EVBを使って私の環境であなたのコードをテストしたところ、すべて期待どおりに動作しました。 カスタムハードウェアに関連する問題を排除するために、クロックソースをFIRCに切り替えて、動作に変化があるかどうか試していただけますでしょうか? Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 内部クロックを使用している場合、pit_notifaction 状態に入ることができません。さらに、通信割り込みやその他の割り込みも正しく機能しません。同じプログラムと設定を S32K312 でテストしたところ、正常に動作しました。 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 こんにちは、 @Finnc 問題はソフトウェアに関係ない可能性が高いようです。代わりにカスタムボードに関連付けられている場合もあります。同じテストを比較するために、S32K311デバイス付きの別の基板にアクセスできますか? Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 現在、S32K311を搭載した他のボードは存在せず、同じボードのいくつかで同様の問題が発生しています。S32K312チップのみ、同じプログラムと構成で正常に動作します。K311の不具合の原因は特定されていません。 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 こんにちは、 @Finnc 私の側ではFRDM-A-S32K312とS32K31XEVB-Q100の両方でコードが正常に動作し、あなたの側もS32K312を使っているので、問題はソフトウェアに関係ない可能性があります。 あなたが説明した挙動からすると、これはハードウェアに関係している可能性があります。しかし、さらなる分析なしに正確な根本原因を特定することは困難である。S32K31XEVB-Q100の回路図やS32K3xx マイクロコントローラのハードウェア設計ガイドラインファイル(S32K3汎用ハードウェア設計パッケージに含まれる)を見て、カスタムボードを推奨設計方法と比較すると良いでしょう。 もし問題がMCU自体に関連している可能性があると思われる場合は、NXPの担当者または部品を購入した代理店にご連絡ください。 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 こんにちは、 @Finnc 別のデバッガーを使ってみましたか?また、最初に共有していただいたコードはまだ使用していますか? Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 テスト中に、`Pit_notifaction`関数にLEDの切り替え機能を追加したところ、プログラムのダウンロードが完了した後、LEDが点滅して割り込みが発生したことを示すには、ボードの電源を再度オンにする必要があることがわかりました。しかし、プログラムを正常に実行するには、ダウンロードのたびに電源を入れ直す必要があり、デバッグモードに入ることができませんでした。 Re: S32K311 芯片 pit无法进入中断 软件环境 S32DS 3.6.0  RTD 6.0.0 元のプログラムを使用し、割り込みにLEDの点滅を追加しました。問題は解決しました。原因は、J-LinkプログラマのリセットピンがNTRSTに接続されていたことでした。これをSRSTに置き換えたところ、問題が解決し、プログラムは正常に実行されました。この2つのピンの違いは何ですか?SRSTに接続する必要があるのでしょうか?すべてのチップでこのピン接続が必要なのでしょうか?
View full article
能否提供 etpuc_pwmm.c 文件?如何重建 PWMM eTPU 功能集? eTPU 报告显示,PWMM 函数是根据 etpuc_pwmm.c 编译的。 报告还列出了以下内部职能: - PWMM_CalcEdgeTimes - PWMM_CalcEdgeTimesAtCenter - PWMM_SchedulePhaseMatchesAtCenter - PWMM_UpdateDutyCycles 我需要修改 PWMM 边沿放置算法,以便为 AZSPWM/NSPWM 实现与相位相关的载波极性。 能否提供 etpuc_pwmm.c 文件?如何重建 PWMM eTPU 功能集? Re: Could you provide the etpuc_pwmm.c source file or advise how to rebuild the PWMM eTPU function s 你好 电机控制 eTPU 库中的 PWMM 功能作为预编译 eTPU 功能集的一部分提供。原始源文件(例如 etpuc_pwmm.c)不包含在标准版本包中。 因此,所提供的库不支持内部修改(如更改边缘计算算法)。 如果需要自定义行为,建议使用 eTPU C 工具链实现自定义 eTPU 功能。 此外,您也可以通过恩智浦网络支持页面申请源代码访问权限,但可用性有限,且通常受特定协议的限制。 顺祝商祺! Peter
View full article