Multi Source Translation Content

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Multi Source Translation Content

讨论

排序依据:
Is NVCC_SD2 power domain necessary? Hello, I'm using iMX93 and I don't need the microSD interface, can I leave the NVCC_SD supply pin disconnected? Best regards, Roberto Re: Is NVCC_SD2 power domain necessary? Hello, If entire NVCC_SD2 bank is not used, you can tie to ground through 10K resistor. Best regards.
查看全文
S32K344-How to convert the actual time to the RTCVAL value of the RTC Hello I used S32K344 to test the RTC wake-up function. When setting the RTC timing time, I referred to the conversion method in the sample program as shown below: However, the time was deviated during the actual test. What is the reason? BestRegards, Simon Re: S32K344-How to convert the actual time to the RTCVAL value of the RTC Hello Simon, The internal SIRC is not precise: To get precise RTC, use the external SXOSC with 32.768Khz crystal. Regards, Daniel
查看全文
USB Bluetooth driver not added to kernel on Android Auto 13 Hi, Currently I'm working on imx8qm MEK with Android Auto 13, linux kernel version is v6.1.25. I am trying to enable bluetooth function on the board by connecting a bluetooth USB dongle rtl8761bu. To recognize the device and bring out the driver, btusb.ko and btrtl.ko are both necessary for this. Here is my setting: arch/arm64/configs/gki_defconfig CONFIG_BT=m CONFIG_BT_RTL=m CONFIG_BT_HCIUART=m CONFIG_BT_HCIBTUSB=m CONFIG_BT_HCIBTUSB_RTL=y drivers/bluetooth/Makefile -obj-$(CONFIG_BT_HCIBTUSB) += btusb.o +obj-m += btusb.o -obj-$(CONFIG_BT_RTL) += btrtl.o +obj-m += btrtl.o After compile the kernel, both kernel modules are missing in the driver folder, why? Android i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Linux Re: USB Bluetooth driver not added to kernel on Android Auto 13 Hi You need add your .ko files into /device/nxp/imx8q/mek_8q/SharedBoardConfig.mk, then the drivers will be copied into Android rootfs. Best Regards Zhiming
查看全文
Motorola SHQ1917H I'm looking for Motorola SHQ1917H. Is this product still manufactured by NXP? Re: Motorola SHQ1917H Thank you for your response. Re: Motorola SHQ1917H SHQ1917H does not exist in NXP database. Seems this part never became NXP.
查看全文
NFC Hi NXP team, Hello, I would like to ask, can the PCA943X connected to a coil directly obtain energy from the phone's NFC, or is another chip needed? Thank you! Re: NFC Hello ZHELI1,  You have to tuned the NFC antenna  using CP and CS to approx 13.56 MHz. For that, the Vector Network analyzer has to be used.  Cp defines the resonance frequency and Cs the system Q factor. The 0-resistors are just for disconecting the rectifier. This might be good for the development phase.  BR Tomas  Re: NFC Hello Tomas, Yes, I am using a mobile phone for reading. Hello, I would like to ask, in this diagram, is Cp used for resonance? Then what is Cs used for (energy storage?)? And is this 0-ohm resistor used for a jumper? I tested this device yesterday. After the antenna and capacitor resonated and matched, I aligned the mobile phone NFC with the coil, and then connected the output to a small LED light. This small light intermittently lights up, and the brightness is not high, not even as high as the energy provided by the NFC chip (10mW). Thank you Re: NFC Hello sir, Unfortunately, the use of PCA943x requires rectifier diodes as shared by Tomas (06-25-24). Additionally for the communication, the matching circuit needs the NTAG or a CRN120. Please request access to AN12641 for further hardware guidelines. Unfortunately, these are restricted to secure files, to get access to them, please follow this guide: https://www.nxp.com/docs/en/user-guide/nxp-secure-files-user-guide.pdf I hope this information may have been useful. Re: NFC Hello Fabian, I have already purchased the PCA943x through official channels, but I don't know which two pins connect to the coil and which two pins connect to the output. Is the usage similar to the NTG5 and NTH2111? Thank you Re: NFC Hello sir, Unfortunately, we don't have any other device that is able to deliver this amount of power besides the PCA943x. Regarding the I2C interface, please keep in mind that this is a slave device. On the other hand, CRN120 is also a T2T that can be read by the Smartphone. My apologies sir but, I believe there isn't a single solution device that will fill your needs. Re: NFC Hello ZHELI1 , I was just referring to your last post :  "Hello Tomas, I haven't heard from you for a long time. I hope you are well.I am not using NFC for communication, only for power supply, to power a rotating platform that requires 3V and 25mA of current. Thank you" For that scenario, you should be OK with the energy harvester I provided last time.  About NFC chips supporting build-in energy harvesting. We offer NTAG I2C (energy harvesting up to 10mW) and NTAG5 (energy harvesting up to 30mW).  But if your design requires NFC communication, you can extend the energy-harvesting circuit with the NTAG I2C as shown below:  BTW. what should be your reader? Do you plan to use a mobile phone?  BR Tomas  Re: NFC Hello Fabian Thank you very much for your response. Here is my requirement: I need an NFC chip that can be connected to a coil I made to form a resonant circuit and use a mobile phone for both power transmission and data communication. It should be capable of outputting a current and voltage sufficient to drive a rotating disc (requires 3V voltage and 25mA current). It needs to support a sensor system (including an MCU and an accelerometer) to collect the acceleration information of the rotating disc. The collected acceleration data should be transmitted directly to a mobile phone via an I2C interface, meaning the NFC chip should support wireless reading. Therefore, I need an NFC chip with high power output. but other products currently have a maximum output of only 30mW(NTAG5 AND NT3H2111). Thank you! Re: NFC Hello sir, This is Fabian from customer support. Could you please help us by explaining a little more your application since we are a little confused about it?  From what we understand you are looking for a power harvesting application that is able to output around 80mW. Is it possible to decrease this output? Now regarding the data transfer you mentioned, over which interface are you looking to transfer data, a wired or through RF? Thank you very much for the clarification, please remember that the more information we have, the better our recommendation will be. Re: NFC Hello Tomas, This means I don't need to purchase any NFC chips, right? If I still need a little bit of data transfer, does it mean there are no suitable NFC chips available at the moment? Thank you Re: NFC Hello ZHELI1,  For your application, You can consider the following structure (see the attachment).  For the rectifier diodes, I would recommend PMEG3005AEA.  BR Tomas  Re: NFC Hello Tomas, I haven't heard from you for a long time. I hope you are well.I am not using NFC for communication, only for power supply, to power a rotating platform that requires 3V and 25mA of current. Thank you Re: NFC Hello ZHELI1 , NTAG5 can provide up to 30mW.  But do you need any NFC communication or only pure energy harvesting?  BR Tomas  Re: NFC Hello Tomas, Previously, I used the NT3H2111, which could provide around 10mW. However, for my scenario, I need about 80mW. Can the NTAG5 provide such a high power output? Thank you Re: NFC Hello ZHELI1,  Good question!  The PCA943X is mainly used in ecosystems including an MCU + NFC Tag. For your application, the NTAG5 (Link or Switch) might be used. The NTAG5 has a very nice capability of energy harvesting.  What is your power requirement?  BR Tomas 
查看全文
[LX2160ARDB-Rev C] 25G port compatibility Hi, Can I use 25G port in LX2160ARDB Rev.C with 10G SFP+ module as 10G port? Regards, J.Hwan Kim Re: [LX2160ARDB-Rev C] 25G port compatibility Yes, you can. Please refer to the following document. https://community.nxp.com/t5/Layerscape-Knowledge-Base/Modify-LX2160ARDB-SFPs-from-25G-to-10G/ta-p/1737068
查看全文
Installing new SDK causes automation project migration I have S32 DS 3.5 and S32K344 micro. It was originally set with SDK/RTD V2.0.0 It became necessary to add SDK 4.0.0, so that one project would migrate to 4.0.0 and another project stays at 2.0.0 SDK 4.0.0 gets installed properly and both SDKs appear under project settings. I was expecting that by attaching/detaching SDK I can control which SDK current project would use. However those "attached/detached" check-boxes seems to have no effect. Regardless of that all projects would use 4.0.0 and it is was not possible to keep one project with 2.0.0 Is there a way to avoid that? Re: Installing new SDK causes automation project migration That works, thank you Re: Installing new SDK causes automation project migration Hi @sstelmak  S32DS 3.5 can keep one RTD version only (plus additional extensions packages/stacks). The solution is to install more S32DS instances. Just use different folder name of S32DS like: c:\NXP\S32DS.3.5_RTD_200\ c:\NXP\S32DS.3.5_RTD_400\ And install corresponding RTD package to those instances. Regards, Lukas
查看全文
MPC5746C模式进入帮助 问候! 我正在尝试按照 TRM 中的步骤使用模式进入模块正确初始化我的控制器。我在 main.c 中编写了一些模式进入模块代码,我认为它与手册中的说明非常相似,但是当我的程序尝试执行对 MC_ME_MCTL 寄存器的第二次写入时,它就挂起了。此外,根据 MC_ME_GS 寄存器,控制器似乎启动了模式转换,但从未完成。 您能看一下我的项目(附件)并帮我找出问题所在吗? 我的最终目标是让 ADC1 模块运行:配置 ADC 寄存器,然后从 ADC 读取。您会注意到我没有为其他外围设备启用任何时钟,这就是原因。 感谢您的时间! 保罗 回复:MPC5746C模式进入帮助 @petervlna感谢您的回复。 我正在查看示例MPC5746C PIT ISR GHS614并尝试模仿其中的模式进入步骤。我仍然遇到同样的问题,但我会继续尝试。 问:我可以使用 Processor Expert 中的 clock_manager 组件来帮我完成模式进入工作吗?它可以独立工作吗?还是我仍需要用代码补充 clock_manager 组件才能使一切正常工作? 保罗
查看全文
channel id error for dio Hello nxp team, we are trying to enable the PTD17 pin high with dio peripheral port name: PTD_H Dio port Id: 7 Dio channel Id: 1 how to check the channel id i set is correct or not? right now this pin is not getting high. HotFix Re: channel id error for dio Hi @Vijay98  For achieving a correct configuration of PTD17 inside the Dio component, could you please check the following article (link)? It provides a complete description of the mapping between the Port Id, Channel Id and the pin that should be configured. The article also presents a demo application, showcasing how certain values can be written to the pins, or how the pins values can be read, using the APIs exposed by the MBDT Dio Simulink block. Hope this helps, Irina
查看全文
MPC5746Cモード入力ヘルプ あいさつ! TRMの手順に従って、モードエントリーモジュールでコントローラーを適切に初期化しようとしています。main.cに書かれたモードエントリーモジュールコードがいくつかありますが、これはマニュアルの指示によく似ていると思いますが、プログラムがMC_ME_MCTLレジスタへの2回目の書き込みを実行しようとすると、ハングするだけです。また、MC_ME_GS レジスタによると、コントローラーはモード遷移を開始したように見えますが、完了することはありません。 私のプロジェクト(添付)を見て、問題が何であるかを特定するのを手伝ってもらえますか? 私の最終目標は、ADC1モジュールを動作させることです。ADCレジスタを構成してから、ADCから読み出します。他の周辺機器のクロックを有効にしていないことに気付くでしょうが、それが理由です。 お時間をいただきありがとうございました! ポール Re:MPC5746Cモードエントリヘルプ @petervlna お返事ありがとうございます。 PIT ISR GHS614の例を見てMPC5746Cそこからモードエントリーの手順を模倣しようとしています。私はまだ同じ問題を抱えていますが、私は試み続けます。 質問: Processor Expert 内の clock_manager コンポーネントを使用して、モード入力の作業を行うことはできますか?それはスタンドアロンで動作しますか、それともすべてを正しく機能させるためにclock_managerコンポーネントにコードを追加する必要がありますか? ポール
查看全文
新しい SDK をインストールすると、プロジェクトの移行が自動化されます 私はS32 DS 3.5とS32K344 microを持っています。 もともとは SDK/RTD V2.0.0 で設定されていました SDK 4.0.0の追加が必要になりましたが、これにより、1 つのプロジェクトが 4.0.0 に移行され、別のプロジェクトが 2.0.0 のままになります SDK 4.0.0 は正しくインストールされ、両方の SDK がプロジェクト設定の下に表示されます。 SDKをアタッチ/デタッチすることで、現在のプロジェクトで使用するSDKを制御できると思っていました。 ただし、これらの「取り付け/取り外し」チェックボックスは効果がないようです。 それにもかかわらず、すべてのプロジェクトが 4.0.0 を使用し、1 つのプロジェクトを 2.0.0 で保持することはできませんでした それを避ける方法はありますか? Re:新しいSDKをインストールすると、プロジェクトの移行が自動化されます それはうまくいきます、ありがとう
查看全文
How can i use bluetooth in imx8mm evk board? Hi. I would like to use bluetooth in imx8mm evk board. But There is not the uart device file, I think ttymxc0 is connected to bluetooth module. ---------- root@imx8mmevk:~# hciattach /dev/ttymxc0 any 115200 flow Can't open serial port: No such file or directory Can't initialize device: No such file or directory root@imx8mmevk:~# ls /dev/ttymxc* /dev/ttymxc1 /dev/ttymxc2 ---------- ■ Question 1. What image should i use?     Now, I use imx-image-multimedia-imx8mmevk.wic. 2. What dtb should i use?     Now, I use imx8mm-evk.dtb. ---------- u-boot=> printenv fdtfile fdtfile=imx8mm-evk.dtb ---------- ■ additional explaination 1. Image and dtb is installed from https://www.nxp.jp/webapp/Download?colCode=L6.6.3_1.0.0_MX8MM&appType=license Re: How can i use bluetooth in imx8mm evk board? I resolved this problem. I didn't need to execute command [hciattach /dev/ttymxc0 any 115200 flow]. I execute only following command.  ------------------- modprobe moal mod_para=nxp/wifi_mod_para.conf modprobe btnxpuart hciconfig hci0 up ------------------- I refered https://community.nxp.com/t5/i-MX-Processors-Knowle\dge-Base/Bluetooth-NXP-UART-Driver-Linux-BSP-6-1-22-btnxpuart/ta-p/1708588. Thanks for a lot!! Re: How can i use bluetooth in imx8mm evk board? Why does it use Linux Open Source UART driver? [6 Bring-up of Bluetooth] section is described as follows. • Bring up using NXP Bluetooth UART driver on the i.MX Linux BSP version L6.1.22 and later. • Bring up using Linux Open Source UART driver on i.MX Linux BSP version earlier than L6.1.22. I downloaded image from following url. I maybe use version 6.6.3. So I guess that I should refer 6.1 Bring-up using NXP Bluetooth UART driver. https://www.nxp.jp/webapp/Download?colCode=L6.6.3_1.0.0_MX8MM&appType=license Re: How can i use bluetooth in imx8mm evk board? pls refer to the chapter 6.2 Bring-up using Linux open source UART driver of enclosed file Re: How can i use bluetooth in imx8mm evk board? Maybe, It's AW-CM358SM (NXP 88W8987). evk board is not expanding. Re: How can i use bluetooth in imx8mm evk board? what BT module do you test on your board? Re: How can i use bluetooth in imx8mm evk board? did you use nxp imx8mm lpddr4 evk board? pls try the command as below before running BT: modprobe moal mod_para = wifi_mod_para.conf
查看全文
S32K142W FTM0 PWM Modulation Hello, My team is attempting to apply spread spectrum to a 3-phase BLDC motor via PWM outputs, which are driven through the FTM0 peripheral. We are investigating the PWM modulation option to achieve this as mentioned in the reference manual: It is still unclear to us the exact affect the modulation will have on the PWM output. Ideally, we are looking for something that will sweep(oscillate) the PWM frequency between a low limit (say 20KHz), and a high limit (say 22KHz). We would look into dithering as another option, but unfortunately we need to used FTM0 for our layout, and dithering is not supported on FTM0. Can someone please explain how the PWM would behave if we applied a modulation of 2Khz on FTM0? Would it jump from 20KHz to 22KHz every few period cycles? Or will it randomly run at a frequency in between that range? Any clarification would be appreciated. We have attempted to model this ourselves, but the instructions for setting up modulation are a bit unclear. I enabled the SIM->FTMOPT1 register to apply modulation on each of the 3 output channels I also set up FTM1 channel 1 to output a PWM at 50% duty cycle at a frequency of 22KHz (2KHz higher than the FTM0 pwms). I applied a 10 tick deadtime and 1/16 deadtime pre-scale to match the FTM0 driver. This is the results I am getting (Yellow is the PWM output on FTM0, blue is the FTM1 output): Here are the configurations for each FTM module: FTM0 /* Fault configuration structure for FTM0 */ ftm_pwm_fault_param_t flexTimer_pwm0_FaultConfig = { false, /* Output pin state on fault */ false, /* PWM fault interrupt state */ 20U, /* Fault filter value */ FTM_FAULT_CONTROL_MAN_ALL, /* Fault mode */ { { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Channel output state on fault */ }, { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Channel output state on fault */ }, { true, /* Fault channel state (Enabled/Disabled) */ true, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Channel output state on fault */ }, { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Channel output state on fault */ }, } }; /* Independent channels configuration structure for flexTimer_pwm0 */ ftm_independent_ch_param_t flexTimer_pwm0_IndependentChannelsConfig[3] = { { 0U, /* hwChannelId */ FTM_POLARITY_HIGH, /* Edge mode */ 0U, /* Duty cycle percent 0-0x8000 */ false, /* External Trigger */ FTM_LOW_STATE, /* The selection of the channel (n) mode */ true, /* Enabled/disabled the channel (n+1) output */ FTM_MAIN_INVERTED, /* Select channel (n+1) output relative to channel (n) */ true, /* Dead time enabled/disabled */ }, { 2U, /* hwChannelId */ FTM_POLARITY_HIGH, /* Edge mode */ 0U, /* Duty cycle percent 0-0x8000 */ false, /* External Trigger */ FTM_LOW_STATE, /* The selection of the channel (n) mode */ true, /* Enabled/disabled the channel (n+1) output */ FTM_MAIN_INVERTED, /* Select channel (n+1) output relative to channel (n) */ true, /* Dead time enabled/disabled */ }, { 4U, /* hwChannelId */ FTM_POLARITY_HIGH, /* Edge mode */ 0U, /* Duty cycle percent 0-0x8000 */ false, /* External Trigger */ FTM_LOW_STATE, /* The selection of the channel (n) mode */ true, /* Enabled/disabled the channel (n+1) output */ FTM_MAIN_INVERTED, /* Select channel (n+1) output relative to channel (n) */ true, /* Dead time enabled/disabled */ }, }; /* PWM configuration for flexTimer_pwm0 */ ftm_pwm_param_t flexTimer_pwm0_PwmConfig = { 3U, /* Number of independent PWM channels */ 0U, /* Number of combined PWM channels */ FTM_MODE_CEN_ALIGNED_PWM, /* PWM mode */ 10U, /* Dead time value */ FTM_DEADTIME_DIVID_BY_16, /* Dead time prescaler */ 20000U, /* PWM frequency */ flexTimer_pwm0_IndependentChannelsConfig, /* Independent PWM channels configuration structure */ NULL, /* Combined PWM channels configuration structure */ &flexTimer_pwm0_FaultConfig /* PWM fault configuration structure */ }; /* Global configuration of flexTimer_pwm0 */ ftm_user_config_t flexTimer_pwm0_InitConfig = { { true, /* Software trigger state */ false, /* Hardware trigger 1 state */ false, /* Hardware trigger 2 state */ false, /* Hardware trigger 3 state */ false, /* Max loading point state */ true, /* Min loading point state */ FTM_PWM_SYNC, /* Update mode for INVCTRL register */ FTM_PWM_SYNC, /* Update mode for SWOCTRL register */ FTM_PWM_SYNC, /* Update mode for OUTMASK register */ FTM_PWM_SYNC, /* Update mode for CNTIN register */ true, /* Automatic clear of the trigger*/ FTM_WAIT_LOADING_POINTS, /* Synchronization point */ }, FTM_MODE_CEN_ALIGNED_PWM, /* Mode of operation for FTM */ FTM_CLOCK_DIVID_BY_1, /* FTM clock prescaler */ FTM_CLOCK_SOURCE_SYSTEMCLK, /* FTM clock source */ FTM_BDM_MODE_00, /* FTM debug mode */ false, /* Interrupt state */ false /* Initialization trigger */ }; FTM1 /* Global configuration of flexTimer_pwm_1 InitConfig */ ftm_user_config_t flexTimer_pwm_MOD_InitConfig = { { true, /* Software trigger state */ false, /* Hardware trigger 1 state */ false, /* Hardware trigger 2 state */ false, /* Hardware trigger 3 state */ false, /* Max loading point state */ true, /* Min loading point state */ FTM_PWM_SYNC, /* Update mode for INVCTRL register */ FTM_PWM_SYNC, /* Update mode for SWOCTRL register */ FTM_PWM_SYNC, /* Update mode for OUTMASK register */ FTM_PWM_SYNC, /* Update mode for CNTIN register */ true, /* Automatic clear of the trigger*/ FTM_WAIT_LOADING_POINTS, /* Synchronization point */ }, FTM_MODE_CEN_ALIGNED_PWM, /* Mode of operation for FTM */ FTM_CLOCK_DIVID_BY_1, /* FTM clock prescaler */ FTM_CLOCK_SOURCE_SYSTEMCLK, /* FTM clock source */ FTM_BDM_MODE_00, /* FTM debug mode */ false, /* Interrupt state */ false /* Initialization trigger */ }; /* Fault configuration structure for flexTimer_pwm_1*/ ftm_pwm_fault_param_t flexTimer_pwm_MOD_FaultConfig = { false, /* Output pin state on fault */ false, /* PWM fault interrupt state */ 0U, /* Fault filter value */ FTM_FAULT_CONTROL_DISABLED, /* Fault mode */ { { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Fault channel state (Enabled/Disabled) */ }, { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Fault channel state (Enabled/Disabled) */ }, { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Fault channel state (Enabled/Disabled) */ }, { false, /* Fault channel state (Enabled/Disabled) */ false, /* Fault channel filter state (Enabled/Disabled) */ FTM_POLARITY_LOW, /* Fault channel state (Enabled/Disabled) */ }, } }; /* The independent channels configuration structure for flexTimer_pwm_1_IndependentChannelsConfig */ ftm_independent_ch_param_t flexTimer_pwm_MOD_IndependentChannelsConfig[1] = { { 1, /* Hardware channel Id */ FTM_POLARITY_HIGH, /* Polarity of the PWM signal */ 16384U, /* Duty cycle percent 0-0x8000 */ false, /* External Trigger */ FTM_LOW_STATE, /* Safe state of the PWM channel when faults are detected */ false, /* Enabled/disabled the channel (n+1) output */ FTM_MAIN_INVERTED, /* Select channel (n+1) output relative to channel (n) */ true, /* Dead time enabled/disabled */ } }; /* PWM configuration for flexTimer_pwm_1 */ ftm_pwm_param_t flexTimer_pwm_MOD_PwmConfig = { 1U, /* Number of independent PWM channels */ 0U, /* Number of combined PWM channels */ FTM_MODE_CEN_ALIGNED_PWM, /* PWM mode */ 10U, /* Dead time value */ FTM_DEADTIME_DIVID_BY_16, /* Dead time prescale */ 22000U, /* PWM frequency */ flexTimer_pwm_MOD_IndependentChannelsConfig, /* The independent PWM channels configuration structure */ NULL, /* Combined PWM channels configuration structure */ &flexTimer_pwm_MOD_FaultConfig /* PWM fault configuration structure */ }; I set the FTMOPT1 register before initializing the FTM peripherals using the following lines of code: SIM_Type * simeBase = SIM_BASE_PTRS; simeBase->FTMOPT1 |= SIM_FTMOPT1_FTM0_OUTSEL(0x2A); /* 0b101010 channels 1, 3, and 5 */ Is there something I am initializing incorrectly? This behavior does not seem correct. I would expect a consistent duty cycle each period with alternating frequencies in the range of 20kHz-22kHz. To clarify, I am using an S32K142W MCU with the SDK RTM v4.0.3. Thanks. Re: S32K142W FTM0 PWM Modulation Hi, Thank you so much for your interest in our products and for using our community. The FTM Modulation Implementation for PWM mode using FTM0_OUTSEL register looks like this. Without modulation: Modulation with FTM1_CH1: At the moment I only have on hand a S32K144-Q100 to test but it should be equal for the S32K142W. I attach the project using S32 Design Studio for S32 Platform v.3.5 and RTD for S32K1 and S32M24x version 2.0.0 including patch P01. Another way to perform modulation is using FAULT input signals, for more detail please refer to the following community posts: https://community.nxp.com/t5/S32K/Modulated-PWM-waveform-Generation/m-p/656233 https://community.nxp.com/t5/S32K/FTM2-Output-Modulation/m-p/1056029 Hope it helps you. Have a nice day!
查看全文
摩托罗拉 SHQ1917H 我正在寻找摩托罗拉 SHQ1917H。 该产品仍由 NXP 生产吗? 回复:摩托罗拉 SHQ1917H 谢谢您的回复。 回复:摩托罗拉 SHQ1917H SHQ1917H在 NXP 数据库中不存在。看来这部分从未成为 NXP。
查看全文
dio 的频道 ID 错误 你好,NXP团队, 我们正在尝试使用 dio 外设启用PTD17引脚高电平 端口名称: PTD_H Dio 端口 ID: 7 Dio 频道 ID:1 如何检查我设置的频道ID是否正确? 现在这个引脚还没有变高。 热修复
查看全文
MPC5746C Mode Entry Help Greetings! I am trying to follow the steps in the TRM to properly initialize my controller with the Mode Entry module. I have some Mode Entry module code written in main.c that I believe closely resembles the instructions from the manual, but when my program tries to execute the second write to the MC_ME_MCTL register, it just hangs. Also, according to the MC_ME_GS register, the controller appears to start a mode transition but it never completes.  Can you please take a look at my project (attached) and help me identify what the problem is? My end goal is to get the ADC1 module operational: configure the ADC registers and then read from the ADC. You will notice that I haven't enabled any clocks for other peripherals, and that is the reason. Thank you for your time! Paul Re: MPC5746C Mode Entry Help Thanks Peter. The issue was incorrectly configured clocks, as you suggested. Once I got that right I ended up just using the clock_manager inside Processor Expert to configure everything and initialized by calling the two functions below, which I learned about through some of the examples in the S32 SDK (the functions are in clock_MPC57xx.c). Just using the CLOCK_DRV_Init processor expert function was not enough. Re: MPC5746C Mode Entry Help Hello, there is a clock configuration guide: https://www.nxp.com/products/processors-and-microcontrollers/power-architecture/mpc5xxx-microcontrollers/ultra-reliable-mpc57xx-mcus/ultra-reliable-mpc574xb-c-g-mcus-for-automotive-and-industrial-control-and-gateway:MPC574xB-C-G Such will ease your work with clocks and their configuration. https://www.nxp.com/docs/en/application-note/AN5392.pdf best regards, Peter Re: MPC5746C Mode Entry Help @petervlna  Thanks for your reply. I am looking at example MPC5746C PIT ISR GHS614 and trying to mimic Mode Entry steps from that. I am still having same issue but I will keep trying. Question: Can I alternatively use the clock_manager component inside Processor Expert to do the Mode Entry work for me? Will it work standalone or do I still need supplement the clock_manager component with code to get everything working just right? Paul Re: MPC5746C Mode Entry Help Hello, but when my program tries to execute the second write to the MC_ME_MCTL register, it just hangs. not sure what prevents you from transition, there could be following reasons: 1. You have incorrectly configured clocks 2. you have peripherals which clock is still active. For example CAN module, PWM module, etc.. is still running from clock source which will be changed in target mode. I suggest to have a look at very basic examples either community ones or S32DS ones: https://community.nxp.com/t5/MPC5xxx-Knowledge-Base/MPC5-software-example-list/ta-p/1102445#MPC5746C Best regards, Peter
查看全文
モトローラSHQ1917H モトローラのSHQ1917Hを探しています。 この製品はまだNXPによって製造されていますか? 日時:モトローラSHQ1917H 返信ありがとうございます。 日時:モトローラSHQ1917H SHQ1917H NXP データベースに存在しません。この部分はNXPにはならなかったようです。
查看全文
iMXRT117x: Linking errors during build smart_lock app for SLN-VIZN3D-IOTDG board Hi, We have a customer is trying to build the smart-lock application for SLN-VIZN3D-IOTDG board. They followed the instructions in the reference manual:  SLN-VIZN3D-IOT SW Developer Guide (nxp.com) When building the smart_lock main application, they get the following errors: What is the resolutions for the above errors, Here are some old tickets related to same issue: How to solve gcc linker error (.ARM.exidx+0x0): relocation truncated to fit: R_ARM_PREL31: followup - NXP Community Re: RT1064: How to solve gcc linker error (.ARM.exidx+0x0): relocation truncated to fit: R_ARM_PREL31 - NXP Community Thanks. Ayman Sydhom Re: iMXRT117x: Linking errors during build smart_lock app for SLN-VIZN3D-IOTDG board Hi Kerry, The customer confirmed that the app builds fine after downgraded the MCUXpresso. Thanks. Ayman Re: iMXRT117x: Linking errors during build smart_lock app for SLN-VIZN3D-IOTDG board Hi @asydhom ,   You are welcome!   I already test both two IDE versions, so, I am sure of this solution.    Yes, after your end customer also make it works, please help me to mark the correct answer, just to close this case, thanks. Any new issues, welcome to create the new case. Best Regards, kerry Re: iMXRT117x: Linking errors during build smart_lock app for SLN-VIZN3D-IOTDG board Thanks Kerry. Will communicate the resolution to our customer and let you know if this solved the issue or not. Regards. Ayman Re: iMXRT117x: Linking errors during build smart_lock app for SLN-VIZN3D-IOTDG board Hi @asydhom ,   Thank you for your interest in the NXP MIMXRT product, I would like to provide service for you. I know your failed issues reason, your used IDE version is high, as I also test it on my side, my MCUXpresso IDE is the v11.9.0, then same build result to you.   So, I download the older MCUXPresso IDE Version to : V11.4.1, as the get start also mentioned: You can download it from this linker: https://www.nxp.com/design/design-center/software/development-software/mcuxpresso-software-and-tools-/mcuxpresso-integrated-development-environment-ide:MCUXpresso-IDE Download the previous version: Then, you need to download the SLN-VIZN3D-IOT SDK https://mcuxpresso.nxp.com/en/builder?hw=SLN-VIZN3D-IOT You need to add it to the MCUXPresso IDE  Now, build your project again, you will find it is OK to use: Please try my method on your side. If you still have question about it, please kindly let me know. If your question is solved, please help me to mark the correct answer, just to close this case, thanks. Any new issues, welcome to create the new case. Best Regards, Kerry
查看全文
Doubt regarding configuration Hello everyone!!! I am using MK22FN512VLL12 Controller in my project i have configured all the pins and peripherals according to my requirement and generated code successfully.  But, I have found something fishy that in project explorer window next to my project name there is   please find the attached....... May I know the reason that why it is showing like that. and will it cause any effect to my project?? and how can i remove it. Thank you!!! regards, ANIL. Please checkPlease check Freedom Development Platform Kinetis K Series MCUs Re: Doubt regarding configuration Hi @yoursanil3 , The message next to the project name is related to the building of the project, the default building in MCUXpresso is Debug but, you can change this in the arrow next to the hammer of building This will not cause any effect to your project. If you want to know more about this, you can see section 3.1 A note about Launch Configuration files of the MCUXpresso IDE - User Guide Hope it helps you!
查看全文
安装新的 SDK 会导致自动化项目迁移 我有 S32 DS 3.5 和 S32K344 micro。 原本是用SDK/RTD V2.0.0设置的 有必要添加 SDK 4.0.0,这样,一个项目将迁移到 4.0.0,而另一个项目仍保留在 2.0.0 SDK 4.0.0 已正确安装,并且两个 SDK 都出现在项目设置下。 我希望通过附加/分离 SDK,我可以控制当前项目将使用哪个 SDK。 然而那些“附加/分离”复选框似乎没有效果。 尽管如此,所有项目都会使用 4.0.0,并且不可能让一个项目继续使用 2.0.0 有没有什么办法可以避免这种情况? 回复:安装新的 SDK 会导致自动化项目迁移 有效,谢谢
查看全文