Multi Source Translation Content

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

Multi Source Translation Content

讨论

排序依据:
A2T27S020NR1 S パラメータ こんにちは、私はA2T27S020NR1 LDMOSトランジスタを使用しています。どなたかこのデバイスのSパラメータデータを共有していただけますか?2.4GHzで動作するパワーアンプを設計するために必要です。                      
查看全文
S32K312 スリープウェイクアップ 背景情報 現在、S32k312を使用してスリープおよびウェイクアップ機能を開発しています。以下の点についてご質問があります。ご助言をお願いいたします。 1. 高速スタンバイではなく通常ウェイクアップを使用しています。通常ウェイクアップモードでは、ウェイクアップソースをスタンバイRAMに保存できますか?現在、WISRレジスタから有効なウェイクアップソースを読み出すことができません。 2. オシロスコープで観察したところ、スリープ状態でウェイクアップソースを受信すると、K3はまずリセットしてからICU割り込みに入ることが分かりました。ウェイクアップはまずリセットされてからICU割り込みに入るのか、それともICU割り込みに入ってからリセットされるのかを知りたいです。 3. スリープ解除後、レベルエッジ割り込みによるウェイクアップを1回だけトリガーしました。ウェイクアップ後、WISRレジスタの値を見ると、ICUウェイクアップ機能で設定されたすべての割り込みが1回トリガーされたことがわかります。そのため、ウェイクアップソースA〜Bが2つ存在するのではないかと疑っています。方法AでMCUをウェイクアップすると、WISRはA〜Bの両方のウェイクアップイベントを同時に記録します。この問題の解決方法をご教示ください。 Re: S32K312 スリープウェイクアップ はい、おっしゃる通り、私のプログラムも同じように設計しています。例えば、同じウェイクアップソースとしてCANウェイクアップを使用しています。ウェイクアップメッセージを1回だけ送信すると、プログラムはウェイクアップしてからスリープ状態に戻ります。しかし、ウェイクアップメッセージを2回または3回送信すると、ソフトウェアは有効なウェイクアップソースを認識し、ウェイクアップ状態を維持できます。なぜでしょうか?ありがとうございます。 Re: S32K312 スリープウェイクアップ 1. 私のソフトウェアは有効なウェイクアップソースを検出すると、ウェイクアップ状態を維持します。この場合、MCUがスリープ状態になった後にウェイクアップイベントを1回だけトリガーすると、MCUはウェイクアップした後すぐに再びスリープ状態になります。これは、有効なウェイクアップソースが認識されていないためと考えられます。MCUがスリープ状態になった後に2回または3回トリガーされれば、有効なウェイクアップソースを認識し、ウェイクアップ状態を維持できます。したがって、K3プラットフォームでは、ウェイクアップイベントを1回だけトリガーすると、MCUをウェイクアップしてリセットすることしかできないと考えられます。2回目または3回目のウェイクアップイベントがない場合、MCUはリセット後すぐに再びスリープ状態になります。私の結論は正しいでしょうか?ありがとうございます。
查看全文
FXLS8967AF Datasheet error: SENS_CONFIG1 default value descriptions The current datasheet listed on the website is Rev 1.5 of Mar 11, 2022: https://www.nxp.com/products/sensors/accelerometers/2g-4g-8g-16g-low-power-12-bit-digital-accelerometer:FXLS8967AF Table 47 shows that the SENS_CONFIG1 register default value depends on the BT_MODE pin: This affects the FSR and ACTIVE fields. The Table 48 descriptions fail to mention this, and use inconsistent options for the 2 fields: The description of FSR uses the BT_MODE=VDD default value, 01; The description of ACTIVE uses the BT_MODE=GND default value, 0 Re: FXLS8967AF Datasheet error: SENS_CONFIG1 default value descriptions Hello andrewneil, I hope all is great with you. Thank you for using the NXP communities. Correct, I also think that Table 48 doesn't mention this. It is not clear. I just wanted to let you know that I have already shared your feedback with the corresponding team. Thank you very much for your comments. Regards, David
查看全文
What difference between Connectivty_test and HCI black box FW? Hi NXP,    We are testing SRRC for kw45 bluetooth boards and it designed by us.    When we test RF test, is accour different result by using different FW, connectivity_test and HCI black box.     like below:    When test Frenquency range, signal send by LE_transmitter_cmd is lower than connectivty test cmd send by LE_transmitter_cmd:01 1E 20 03 00 25 00, result=-36.953dBm/MHz: send by connectivty test cmd:"Mode TX, Rate BLE 1Mbps, Whiten Fixed, Channel 42, Power 31, Payload 37, XtalTrim 26> Mod PN", result=-39.23dBm/MHz:      It is higher 2dB in connectivity test.  Why and how it can occured? and we use the same sounding only different FW.     Here is we use:      SDK example: KW45B14ZEVK 2.12.7      FW: connectivity test / HCI black box from, which only I change is Xtaltrim=26.      MXUXpresso IDE: V11.8.0_1165    If you have any ideas about the commands and how to pass certification, please let us know, thanks.    Best Regards,    Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  For the spec mentioned by you, we also have test result please see below pic: And would you mind to speak Chinese for better understanding each other? 您是要测带外杂散信号吗? 可以将您的问题详细描述一下发到我的邮箱:[email protected] 我把您原始的邮件转发给我们的内部专家团队帮忙看看,避免因translate引起误解。 Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? hey Christine,        We are not talking the same thing.We are testing Freq Range not Emission in Band. It is not a good solution for us.        The specification files we are refering is as attach. I am sure the limit is 30dBm/KHz as below SRRC limit .       It meas When we are sending signal in 2402MHz or 2480Mhz, It request power in 2400MHz&2483.5MHz need to less than -80dBm/Hz. And we need to calculate, Power dBm= -80dBm/hz+10*log(100000)= -80+50= -30dBm/KHz, So its limit should be -30dBm/KHz, it is talking clearly in ETSI EN 300 328 V1.7.1 (2006-10).pdf and SRRC number 129. Our SA setting when we are testing Freq Range in 2400 Center Freq=2400MHz Span=10MHz RBW=100KHz VBW=100KHz Sweep time =60s offset=cable loss+Antenna Gain Detector=RMS Max hold You can try and talk to me. Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Do you have any chance to read my previous comment? Please let me know whether you have any other queries. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Our internal team's test result is similar with you. Please see below: But after checked the AN13228, we found the BT limit is -20dBm, not -30dBm. It means, according to the AN13228's BT limit, we can pass for sure. Can you please help to confirm SRRC certification limit requirement? If you have any specification files, can also share us to check together. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  I found our test result, it seems different with yours. There is no these 2 little peak in our test results as shown in the below screen shot. For details, you can also refer to our test report on KW45-EVK. AN13228-KW45B41Z-EVK RF System Evaluation Report for Bluetooth Low Energy Applications I have request our AE team help to test again, and at the same time, please share me your detailed test steps, so that we can compare and find whether have any different steps during test. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li,     I have tried your suggestion. But the signal is not what we want. it behaves like umodulation signal. Continuous Modulated Transmission 1's:  Continuous Modulated Transmission 0's:   Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  It's my pleasure!  You are welcome anytime. I receive our internal team's suggestion, can you please have a try and let me know your result? Could you please try the transmitter test command with the pattern of all 0 bits or 1 bits? Thank you. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li,      We got the 2M-Freq Range from KW45- EVK. It also behaves less margin in 2400MHz, Like below pictrue, and its power is about 9.8dBm in 2402MHz: The test Way we get from ETSI EN 300 328 V1.7.1 (2006-10) as the attach file. Now we have tunned a matching and the result in 2M-Freq Range is similiar to KW45-EVK. If you have better ideas about the test Way or how to get more margin, please talk to us. Thank you very much. Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your reply. Sure, please take your time. And also I have created an internal case to our expertise team. Hope we can resolve this issue ASAP. If I need any other info from your side, I will leave message to you. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your reply and your efforts on this issue. Sorry, I am not good at this Power related to certification,. I need to check with our internal team. But as you know, we will have a public holiday from May 1st to May 5th in China, totally 5 days, and I will be back to office 6th of May. I could not reply you in time during this period. I sincerely apologize for the inconvenience. Have a nice holiday~   Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for creating case to us and hope you are doing well. I will check it and reply to you once have any updates. Have a nice weekend. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  These two is built for different examples. For the details inside of these two FWs, I need to confirm with our internal team. But before that, may I ask what kind of issue do you meet during your certification? Which FW can pass the certification? and what is the standard of the certification? Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine,     Thanks for your reply.     Now we are going to get pass the China Ble standard named SRRC. And the issue I meet in certification is 2M-Frequency range fail.     When I use Connetivity_test FW, I get the 2M-Frequency range result as below, it is so close to the limit.The Frenquency of Power 30dBm/100Khz is 2.40000GHz=2.4GHz. We do not have enough value to pass the certification: cmd:  Mode TX, Rate      BLE 2Mbps, Whiten Fixed, Channel 42, Power 31, Payload 37, XtalTrim 26> Mod PN When I use HCI black box FW, I get the result as below, Power 30dBm/100Khz is 2.40065GHz>2.4GHz, Pass : cmd: 01 34 20 04 00 25 00 02 And also, The 2M-suprious emission of 2390-2400 is so close to the limit as below Picture: For connectivity test FW, Power in 2.4GHZ is -30.68dBm, we have no more margin to pass: cmd: Mode TX, Rate      BLE 2Mbps, Whiten Fixed, Channel 42, Power 31, Payload 37, XtalTrim 26> Mod PN For HCI black box FW, Power in 2.4GHZ is -33.750dBm, we still have 3dB margin to pass: cmd: 01 34 20 04 00 25 00 02 Our Surrounding: SDK: KW45 V2.12.7 IDE: V11.8.0_1165 FW: connectivity_test &HCI black box      thanks      Best Regards,      Annie Re: What difference between Connectivty_test and HCI black box FW? And, This Afternoon, I try to change Connectivity test cmd and it can get a better result. Cmd- Burst Transmission using random-payload packets: Mode RX, Rate BLE 2Mbps, Whiten Fixed, Channel 42, Power 31, Payload 37, XtalTrim 26> Packet Mode PRBS started. Press [SPACE] to stop test and 2M-Frenquency Range result as below, there is 70KHz margin: and 2M-Suprous Emisson in 2390-2400Mhz result as below, there is 6dBm margin: And if we can use Burst Transmission using random-payload packets cmd to test certification? What different in Burst Transmission using random-payload packets cmd and Continuous Modulated Transmission pseudo-random cmd and HCI_LE cmd?  connectivity test FW cmd as below: If you have any ideas about it, please let us know. Thanks. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  I found this guide in our SDK: Generic FSK Link Layer Quick Start Guide.pdf  which is located in SDK_2_12_7_KW45B41Z-EVK\docs\wireless\GENFSK\ path. Please see section:  4.3.1 Continuous tests  So I think we just provide some examples and different modes to customer to choose according customer's preference. About SRRC certification, I think you can choose any modes from them.  Do you know SSRC has any special rules to limit the test modes? If there is no such kind of limitations, then you can pass it with Cmd- Burst Transmission using random-payload packets. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine,    SRRC may request the duty cycle, but I did not get the specific limit about it. Duty cycle of an old SRRC report in 2008 is demanded more than 10%.    I try to send cmd-Burst Transmission using random-payload packets to DUT, it pass. But its duty cycle is less than 10%.    So if you have better Ideas about below: 1. HCI black box can support HCIExt_ModemTestTxCmd & HCIExt_EnhancedModemTestTxCmd HCIExt_ModemTestTxCmd: 1Mbps 2402MHz UNMoudulation: Send->01 08 FC 02 01 00 recieve>>04 FF 05 08 04 00 08 FC HCIExt_EnhancedModemTestTxCmd: 1Mbps 2402MHz UNMoudulation: Send->01 27 FC 03 01 00 00 >>04 FF 05 27 04 00 27 FC those cmd we got From other chip platform, if you have similar solution about unmodulation signal in KW45? 2. How to get 2M-Phy Frenquency Range in 2400 lower down? We really need your help, if you have any ideas, please share us, Thank you so much. Best regards, annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your reply. 1.For the unmodulated signal in KW45, can you please help to try with mode [6]? 2. How to get 2M-Phy Frenquency Range in 2400 lower down? ==>Sorry, can you give me more details for better understanding? I didn't get your point. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  I haven't received your feedback in 5 days, do my above comments help you? Please let me know whether still need our support on this thread. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine,     Sorry, I'm late for your reponse.     What I talk may not so clear. 1. I hope to use HCI black box image to send unmodulation signal, not connectivity test image to send. 2.For sencond question, you can know taht 2M-Frenquency range of KW45 fail in China SRRC test. Like below picture, I send 2M signal in 2402Mhz by connectivity test, and its Frenquency Range is more than 30dBm in 2400Mhz. SRRC request in 2400Mhz, power need less than 30dBm. But HCI black box image to test 2M Freq Range, it is easily to pass this SRRC item. But it can not sopport Ummodulation signal. We need a image which can pass SRRC and send unmodulation signal&modulatuion signal. And if you have better idea? And sorry for late again and Thank you so much for your reply. Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Sorry for my late reply. Do you have our KW45-EVK? Have you tested with our KW45-EVK? I am suspect whether it is a hardware issue. I am not so familiar with hardware, if you have our KW45-EVK, please help to test with it and let me know the result. At the same time, I will create an internal ticket to our expertise team to ask help. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li,     We have KW45-EVK, and I will use KW45-EVK to test its 2M Freq Range with Connectivity test image this afternoon or tomorrow and give a feedback for you.      Thanks for your help and reply. Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li,      KW45-EVK 2M-Freq Range test result is as below: There is also less margin to the limit(-30dBm) in 2400Mhz. And test way I got from ETSI EN 300 328 V1.7.1 (2006-10) as attach. We have tunned a RF matching and got similiar result as KW45-EVK in SRRC 2M Freq Range. If you have better ideas about the test way or how to get better one, please talk to us, Thank you very much. Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your results. I have forwarded the test result on both your board and our KW45-EVK to our expertise team. Once receive any feedback, I will share with you. I apologize again for my poor RF knowledge. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li,     Thanks you so much. You take much of you time to help us.     You can check the test way of Freq Range and if you have any ideas about the 2M Freq Range, you can share with us.     And if you have any updates, you can send mail to me or leave massege in this post. My Email is [email protected]. Best Regards, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Did you get any chance to test with our internal team's suggestion? Please let me know whether it works for you. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your reply. I have forwarded your result to our internal team. Hope we can get more suggestions to support you. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your patience. I received our internal team's reply as below: ========  Yes, the HCI commands can not generate the pure continuous wave. The frequency of transmitting 1 or 0 has a positive or negative deviation than the pure continuous wave. We can consider it as an unmodulated signal while ignoring the frequency. ========= Please let me know anything else I can do for you. If you still have any other concerns, please do not hesitate to reply me. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Anything else I can do for you on this case? Or do you have any other questions or queries? Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li,     Thanks for your attention in this post!     But the report that you posted the picture, the power it set is 0 dBm and it is uppper bandege which signal is 2480MHz not 2400MHz. And I do not know the reason it set the minium power. But when we go to do the SRRC certification, we need set the max power 10 dBm. And SA setting is different from SRRC requested. SRRC request       Now we found to decrease the power to 9dBm-9.5dBm, we can pass 2M Freq Range in the certification, But there is a little margin, it is stiil dangerous for us.      Thank you again. Best Regards, Annie             Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your reply, and you are welcome, it is my job to support you. I have forwarded your feedback to our internal team, our expertise will test today, hope they can share some good news or ideas to us. Once have any updates, I will let you know. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Do you have any chance to read my previous comment? Please let me know whether you have any other queries. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  The test result of TX power in band is normal. And it complies with the BLE specification.  Please let me know whether you have any other concerns on this case. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for your reply. Sure, I will forward your feedback to our internal team and request to continue to support this case. Any updates I will let you know. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Regarding the first question, I would like to add: Are you measuring the radiation mode? Or the maximum equivalent isotropic radiated power? Is it a conducted test? For the second question, let me add one more thing. As shown in the figure below, are you testing the out-of-band emission band or the spurious emission band? Because we see that you are testing: The spurious domain is outside 2.5 times the channel bandwidth And what you tested is: 2M PHY: 2390-2400MHz. Combined with the figure below, it looks like it is in the out-of-band emission domain rather than the spurious domain? So please confirm. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi Christine_Li, Let me give you a brief reply here. The problem we encountered when testing the KW45 SRRC report was that the Ble 2M PHY-2400MHZ sideband power was too close to the limit. There are two limit requirements related to 2M PHY-2400MHz 2400 in SRRC No. 129: 1. The defined operating frequency range is 2400-2483.5MHz, and the equivalent isotropic radiated power at the upper and lower limits of the operating frequency is specified to be no greater than -80dBm/Hz. This test can also be understood as a frequency edge test. The conversion formula is: -80dBm/hz+10*log(100000)= -80+50= -30dBm/KHz. 2. Special frequency band spurious test 2M PHY-2390-2400MHz, the limit requirement is also -30dBm. The test specifications and methods we refer to are as follows: Frequency range test requirements, reference document: ETSI EN 300 328 V1.7.1 (2006-10) Frequency range test requirements and test methods, refer to the document: Bluetooth RF indicators and detection methods The results of our board test are as follows: The firmware is kw45b41zevk_connectivity_test_bm, SDK: 2.12.7 测试时,频谱仪需补的Offset应为cable loss+Antenna Gain 1. 2M PHY 2400MHz 频率边带测试 The KW45 test result of 2M PHY frequency edge 2400MHz is: -30.446dBm<-30dBm, the margin is only 0.446dBm The KW45 test result of 2M PHY frequency edge 2400MHz is: -30.383dBm<-30dBm, the margin is only 0.383dBm At present, the sideband of our 2M PHY 2400MHz is very close to the Limit -30dBm. The KW45 EVK test also has similar results. You can test it according to the method I posted in the post. At present, it is found that adjusting the RF matching cannot solve the problem well. Only by reducing the power can a better effect be achieved. I uploaded the documents used to Attach. Best Regads, Annie Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he Sorry for not replying to you for so long. We just received a reply from our internal team. We still have some questions about your test: You mainly test two parameters, one is the out-of-band transmission power, which is the maximum equivalent isotropic radiated power tested. This should not be a conducted test, right? The spurious signal of the second test should be outside 2.5 times the channel bandwidth of the center frequency, that is, 2.4G+-50M? SRRC Certification: Standards and specific requirements for Bluetooth and WI-FI product model approval testing! _Sichuan Chengdu Third-Party Testing and Certification Agency (wanttest.com) SRRC certification: standards and specific requirements for Bluetooth and WI-FI product model approval testing! SRRC certification: Standards and specific requirements for model approval testing of Bluetooth and WI-FI products! "Radio Transmitter Equipment Model Approval Certificate", the model approval code must be indicated on the label of the factory equipment. Your test document also mentions that you need to test in the spurious domain. Please help answer the above questions, thank you. Best regards, Christine. Re: What difference between Connectivty_test and HCI black box FW? Hi, @Annie_he  Thanks for the detailed information. Our internal AE team colleagues have been a bit busy recently and haven't replied to me yet. I will continue to follow up and inform you as soon as there is any progress. Best regards, Christine.
查看全文
Problem with CDC-ACM driver crashing when closing ttyACM port We are having an issue with a USB-to-Serial converter device using the cdc-acm driver. More specifically, the port can be opened and communicated with correctly, but closing the port results in a crash. The problem occurs with a USB 2.0 device connected to the USB1 interface of our i.MX8M-Mini (USB1 configured as host). The board is our own design based on the X-8MMINILPD4-EV evaluation board. The device is a USB-to-Serial converter which is also our own design. We are using linux-imx kernel version imx_4.14.98_2.2.0. We have enabled the cdc-acm driver in our DEFCONFIG file (CONFIG_USB_ACM=y) and the device appears as expected under /dev/ttyACM0. I can open the port and communicate normally with the device. However, a crash occurs as soon as the port gets closed. The error message refers to a NULL pointer dereference. I have tried different ways of talking to the device (with minicom, with a simple echo command, with some C code) and the crash occurs in every scenario. The full crash log is below. The same USB device can be opened and closed normally when it is connected to a Ubuntu computer, therefore the problem appears to be on the iMX8MM side and not with the USB device. I've searched on the internet and found some references to known issues related to cdc-acm driver and NULL pointer dereference, but it looks like fixes have been released years ago so I wouldn't expect to encounter them today. I wonder if a newer kernel might solve the problem and I've been trying to upgrade, but I'm facing lots of issues with the migration. I don't know if a newer kernel would be more stable but in any case this is not the preferred solution. Can anyone advise on potential solutions to solve this with kernel 4.14.98_2.2.0? Thanks. >>> [ 52.482669] Unable to handle kernel NULL pointer dereference at virtual address 00000010 [ 52.490833] Mem abort info: [ 52.493627] Exception class = DABT (current EL), IL = 32 bits [ 52.499545] SET = 0, FnV = 0 [ 52.502598] EA = 0, S1PTW = 0 [ 52.505737] Data abort info: [ 52.508617] ISV = 0, ISS = 0x00000004 [ 52.512451] CM = 0, WnR = 0 [ 52.515420] user pgtable: 4k pages, 48-bit VAs, pgd = ffff8000e4c32000 [ 52.521945] [0000000000000010] *pgd=0000000000000000 [ 52.526912] Internal error: Oops: 96000004 [#1] PREEMPT SMP [ 52.532484] Modules linked in:NOR | Minicom 2.7.1 | VT102 | Offline | tyACM0 [ 52.535543] CPU: 0 PID: 4046 Comm: minicom Tainted: G W 4.14.98-06466-g5910884f0fa2-dirty #1 [ 52.545107] Hardware name: FSL i.MX8MM EVK board (DT) [ 52.550157] task: ffff8000e5249b00 task.stack: ffff00001a288000 [ 52.556084] PC is at start_unlink_async.part.36+0x34/0x88 [ 52.561483] LR is at ehci_urb_dequeue+0xcc/0xe0 [ 52.566012] pc : [ ] lr : [ ] pstate: a00001c5 [ 52.573405] sp : ffff00001a28bb70 [ 52.576718] x29: ffff00001a28bb70 x28: ffff8000e5249b00 [ 52.582031] x27: ffff000008d61000 x26: 0000000000000039 [ 52.587344] x25: 0000000000000124 x24: ffff8000f2ca5928 [ 52.592658] x23: 0000000000000140 x22: ffff8000f392d100 [ 52.597971] x21: ffff8000f93cb30c x20: 0000000000000000 [ 52.603284] x19: ffff8000f93cb000 x18: 0000000000000000 [ 52.608597] x17: 0000ffff8907d6b8 x16: ffff000008211298 [ 52.613910] x15: 16170f12001a1311 x14: 071c71c71c71c71c [ 52.619223] x13: 0000000000000000 x12: 0000000c1b110c39 [ 52.624536] x11: 00000000000004a2 x10: 0000000000000980 [ 52.629849] x9 : ffff00001a28bba0 x8 : ffff8000e524a4e0 [ 52.635162] x7 : 00000000000005ec x6 : 0000000002abbc65 [ 52.640475] x5 : 0000000000000000 x4 : ffff8000f93cb330 [ 52.645788] x3 : 0000000000000000 x2 : 0000000000000000 [ 52.651101] x1 : ffff8000f2d42600 x0 : ffff8000f93cb238 [ 52.656415] Process minicom (pid: 4046, stack limit = 0xffff00001a288000) [ 52.663201] Call trace: [ 52.665647] Exception stack(0xffff00001a28ba30 to 0xffff00001a28bb70) [ 52.672088] ba20: ffff8000f93cb238 ffff8000f2d42600 [ 52.679917] ba40: 0000000000000000 0000000000000000 ffff8000f93cb330 0000000000000000 [ 52.687747] ba60: 0000000002abbc65 00000000000005ec ffff8000e524a4e0 ffff00001a28bba0 [ 52.695576] ba80: 0000000000000980 00000000000004a2 0000000c1b110c39 0000000000000000 [ 52.703406] baa0: 071c71c71c71c71c 16170f12001a1311 ffff000008211298 0000ffff8907d6b8 [ 52.711236] bac0: 0000000000000000 ffff8000f93cb000 0000000000000000 ffff8000f93cb30c [ 52.719066] bae0: ffff8000f392d100 0000000000000140 ffff8000f2ca5928 0000000000000124 [ 52.726895] bb00: 0000000000000039 ffff000008d61000 ffff8000e5249b00 ffff00001a28bb70 [ 52.734725] bb20: ffff0000088d739c ffff00001a28bb70 ffff0000088d31a4 00000000a00001c5 [ 52.742555] bb40: ffff8000fff6b000 ffff000009488000 0000ffffffffffff ffff8000e5249b00 [ 52.750383] bb60: ffff00001a28bb70 ffff0000088d31a4 [ 52.755263] [ ] start_unlink_async.part.36+0x34/0x88 [ 52.761703] [ ] ehci_urb_dequeue+0xcc/0xe0 [ 52.767277] [ ] unlink1+0x28/0x130 [ 52.772156] [ ] usb_hcd_unlink_urb+0x98/0xc8 [ 52.777903] [ ] usb_kill_urb.part.4+0x30/0xb0 [ 52.783736] [ ] usb_kill_urb+0x20/0x30 [ 52.788963] [ ] acm_kill_urbs+0x54/0x70 [ 52.794276] [ ] acm_port_shutdown+0x7c/0x90 [ 52.799937] [ ] tty_port_shutdown+0x94/0xb0 [ 52.805597] [ ] tty_port_close+0x4c/0x88 [ 52.810996] [ ] acm_tty_close+0x1c/0x28 [ 52.816310] [ ] tty_release+0x10c/0x490 [ 52.821625] [ ] __fput+0x88/0x1d0 [ 52.826417] [ ] ____fput+0xc/0x18 [ 52.831210] [ ] task_work_run+0x9c/0xc0 [ 52.836525] [ ] do_notify_resume+0xfc/0x108 [ 52.842183] Exception stack(0xffff00001a28bec0 to 0xffff00001a28c000) [ 52.848624] bec0: 0000000000000000 0000ffff891a8f10 0000000000000000 0000000000003c71 [ 52.856454] bee0: 0000aaaaddce0100 0000000000000004 0000aaaad1c764b8 0000ffff891af6d0 [ 52.864283] bf00: 0000000000000039 0000000000000000 0000000000000016 0000000000000000 [ 52.872113] bf20: 00000a3b00001cb2 0000000000000005 00010004157f1c03 16170f12001a1311 [ 52.879943] bf40: 0000aaaad1c70b58 0000ffff8907d6b8 0000000000000000 0000000000000003 [ 52.887773] bf60: 0000ffff891a9710 0000ffffc1e7d828 0000aaaad1c7f2e8 0000aaaad1c70000 [ 52.895602] bf80: 0000aaaad1c57000 0000aaaad1c70000 0000aaaad1c77a40 0000aaaad1c76e08 [ 52.903433] bfa0: 0000aaaad1c71000 0000ffffc1e7d230 0000aaaad1c3bd58 0000ffffc1e7d230 [ 52.911262] bfc0: 0000ffff8907d6e4 0000000000000000 0000000000000003 0000000000000039 [ 52.919092] bfe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 52.926922] [ ] work_pending+0x8/0x10 [ 52.932062] Code: f9000043 f9407403 14000002 aa0203e3 (f9400862) [ 52.938156] ---[ end trace 12c9a1d9f603ec7e ]--- [ 63.059546] mmc1: Timeout waiting for hardware interrupt. [ 63.064955] mmc1: sdhci: ============ SDHCI REGISTER DUMP =========== [ 63.071398] mmc1: sdhci: Sys addr: 0x00000008 | Version: 0x00000002 [ 63.077837] mmc1: sdhci: Blk size: 0x00000200 | Blk cnt: 0x00000000 [ 63.084277] mmc1: sdhci: Argument: 0x00068788 | Trn mode: 0x0000002b [ 63.090717] mmc1: sdhci: Present: 0x01f88008 | Host ctl: 0x00000013 [ 63.097157] mmc1: sdhci: Power: 0x00000002 | Blk gap: 0x00000080 [ 63.103596] mmc1: sdhci: Wake-up: 0x00000008 | Clock: 0x0000000f [ 63.110036] mmc1: sdhci: Timeout: 0x0000008f | Int stat: 0x00000003 [ 63.116475] mmc1: sdhci: Int enab: 0x107f100b | Sig enab: 0x107f100b [ 63.122915] mmc1: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000502 [ 63.129354] mmc1: sdhci: Caps: 0x07eb0000 | Caps_1: 0x8000b407 [ 63.135794] mmc1: sdhci: Cmd: 0x0000193a | Max curr: 0x00ffffff [ 63.142233] mmc1: sdhci: Resp[0]: 0x00000900 | Resp[1]: 0x00eddf7f [ 63.148673] mmc1: sdhci: Resp[2]: 0x325b5900 | Resp[3]: 0x00000900 [ 63.155112] mmc1: sdhci: Host ctl2: 0x00000088 [ 63.159555] mmc1: sdhci: ADMA Err: 0x00000000 | ADMA Ptr: 0x7804f208 [ 63.165994] mmc1: sdhci: ============================================ i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Problem with CDC-ACM driver crashing when closing ttyACM port We have identified the root of the problem. Our USB device had an error with one of its endpoint descriptors. The direction for the interrupt endpoint of the serial device was wrong. That endpoint is not used so we don't understand why this was causing a problem with the CDC-ACM driver in the NXP environment. There is no more crash after changing the direction of the interrupt. Re: Problem with CDC-ACM driver crashing when closing ttyACM port Hi Aldo, thank you for your answer. We have set CONFIG_USB_ACM=y because we need the driver to be active on boot and detect/map our USB device right away. We had first tried with the default configuration (CONFIG_USB_ACM=m) but then the device doesn't appear as /dev/ttyACM0 when we plug it in. Besides, we have been able to confirm that the cdc-acm driver is working correctly in our iMX8M-Mini platform with another USB device from a different manufacturer. It would seem there are differences between our device and that other device which are causing a crash inside the linux-imx environment, but are working seamlessly in a Ubuntu workstation.  We are currently trying to figure out the differences in the USB descriptors between the two devices. Thanks. Yannick. Re: Problem with CDC-ACM driver crashing when closing ttyACM port Hello, I'm looking into the issue, I cannot find reports of this so I will need to check what is actually causing this. As a side note I see that in our Config we have this enabled as a module, while you have set it as built-in, could you try to set it as module? Best regards/Saludos, Aldo. Re: Problem with CDC-ACM driver crashing when closing ttyACM port Update: I have replicated the problem on the i.MX8MM EVK (LPDDR4) with linux-imx kernel 4.14.98_2.0.0ga, and also with the latest version from the repo which is lf-6.6.3-1.0.0. I can see that the cdc-acm driver has evolved between the two versions, therefore I assume that any pending bug fix should be included in there. Yet, I see the same crash when closing the ttyACM0 port with the latest version of the kernel. The USB-serial device works correctly on my DELL Optiplex computer with Ubuntu 20.04 and kernel 5.15.0-105. So it seems there is something specific to the i.MX8MM environment that causes problems. Has anyone had success using a USB-serial converter with cdc-acm driver on iMX8M-Mini? Thanks.
查看全文
S32K312 sleep wakeup Background information I am currently using S32k312 to develop sleep and wake-up functions. I have the following questions. Please ask for advice; 1. I use Normal Wakeup instead of Fast Standby. Can I store the wakeup source in StandbyRam in Normal wakeup mode? I cannot read the valid wakeup source from the WISR register at present. 2. I observed through an oscilloscope that after receiving the wake-up source in the sleep state, K3 first resets and then enters the Icu interrupt. I want to know whether the wake-up is reset first and then enters the Icu interrupt or first enters the Icu interrupt and then reset; 3. I only triggered the level edge interrupt wake-up once after sleep. After waking up, the value in the WISR register shows that all my interrupts configured with the Icu wake-up function were triggered once. Therefore, I doubt whether there are two wake-up sources AB. After waking up the MCU through method A, WISR will record both wake-up events AB at the same time. Please help me solve this problem. Re: S32K312 sleep wakeup Yes, as you said, my program is also designed in this way. For the same wake-up source, for example, I use CAN wake-up. If I only send a wake-up message once, my program will wake up and then go back to sleep. However, when I send two or three wake-up messages, the software can recognize the valid wake-up source and maintain wake-up. Why is this? Thank you. Re: S32K312 sleep wakeup 1. If my software detects a valid wake-up source, it will maintain a wake-up state. In this case, if I only trigger a wake-up event once after the MCU goes to sleep, the MCU will only wake up and then quickly go to sleep again. It is believed that the valid wake-up source is not recognized. If the MCU is triggered two or three times after sleep, it can recognize the valid wake-up source and maintain wake-up. Therefore, I think that on the K3 platform, only triggering a wake-up event once can only wake up and reset the MCU. If there is no second or third wake-up event, the MCU will immediately go to sleep again after resetting. Is my conclusion correct? Thank you
查看全文
S32K312 休眠唤醒 背景信息我目前正在使用S32k312进行休眠唤醒的功能开发,我有以下问题请请教咨询一下; 1、我使用的是Normal Wakeup而非Fast Standby,请问在Normal唤醒模式下可以实现唤醒源在StandbyRam的存储吗,我目前无法从WISR寄存器中读到有效唤醒源; 2、我通过示波器观察发现K3在休眠状态下收到唤醒源后是先走复位然后才进入的Icu中断,我想知道唤醒到底是先复位再进Icu中断还是先进Icu中断再复位; 3、我在休眠后只触发一次电平沿边中断唤醒,唤醒后从WISR寄存器中的值来看我所有配置了Icu唤醒功能的中断都触发了一次,因此我怀疑是否存在AB两种唤醒源,通过A方式唤醒MCU后WISR会同时记录AB两个唤醒事件,麻烦帮我解答一下; Re: S32K312 休眠唤醒 Hi@Gaulle 自己去排查,可能是的程序根本就没有成功进入standby模式,亦或者你的唤醒源一直存在 Re: S32K312 休眠唤醒 对的,如你所说,我的程序也是这样设计的,同样的唤醒源,例如我是CAN唤醒,如果我只发一次唤醒报文,那么我的程序会唤醒然后又休眠,而我发两三帧唤醒报文的时候,软件就能识别到有效唤醒源且维持唤醒,这是为什么呢,谢谢 Re: S32K312 休眠唤醒 Hi@Gaulle 不正确,除非你的程序在唤醒后又进入了休眠,不存在几次唤醒的问题 Re: S32K312 休眠唤醒 1、我的软件内部如果检测到有效唤醒源会进行一个唤醒状态的维持,在这种情况下,我在MCU休眠后如果只触发一次唤醒事件,MCU只会唤醒然后很快再次休眠下去,愿意是未识别到有效唤醒源,而在休眠后如果触发二到三次MCU就可以识别到有效唤醒源且维持唤醒,因此我认为在K3平台上只触发一次唤醒事件只能唤醒且复位MCU,如果没有第二三次唤醒事件,则MCU在复位起来后会立马又休眠下去,请问我的结论正确吗?谢谢 Re: S32K312 休眠唤醒 Hi@Gaulle Q.请问在Normal唤醒模式下可以实现唤醒源在StandbyRam的存储吗 可以,外部唤醒源唤醒后读取WISR,再将其存储在StandbyRam中没有问题 Q.我通过示波器观察发现K3在休眠状态下收到唤醒源后是先走复位然后才进入的Icu中断,我想知道唤醒到底是先复位再进Icu中断还是先进Icu中断再复位; 唤醒的中断标志位在唤醒后依然存在,如果当前使能了中断,那么会在唤醒后进入唤醒中断处理。 Since the wakeup flag register is retained after waking up, the wakeup ISR can be entered once the NVIC->ISER of Wakeup Unit is enabled by code. All the 64 wakeup sources share one interrupt vector. Q.唤醒后从WISR寄存器中的值来看我所有配置了Icu唤醒功能的中断都触发了一次 所有的64个唤醒源共用一个中断向量,ICU唤醒功能的中断都触发了一次是可能的,但是相应的唤醒WISR是独立的,所有你自己去排查是否响应的唤醒口是否触发了唤醒操作。 Read the WKPU->WISR & WKPU->WISR_64 (Wakeup/Interrupt Status Flag Register). They are cleared by writing 1.
查看全文
A2T27S020NR1 S 参数 大家好,我正在使用 A2T27S020NR1 LDMOS 晶体管。有人可以分享这个设备的 S 参数数据吗?我需要它来设计一个工作在 2.4 GHz 的功率放大器。                      
查看全文
A2T27S020NR1 S -parameter Hi all, I'm working with the A2T27S020NR1 LDMOS transistor. Can anyone please share the S-parameter data for this device? I need it to design a power amplifier operating at 2.4 GHz.                       Re: A2T27S020NR1 S -parameter Hello I've sent the S-parameters.  Re: A2T27S020NR1 S -parameter Dear NXP consultant ! Is there any update on this. I need S-parameter or model for my research project ASAP. Best regards, Tung   Re: A2T27S020NR1 S -parameter case 00661231 Re: A2T27S020NR1 S -parameter I've opened support ticket . Re: A2T27S020NR1 S -parameter Hello, Could you please open a support ticket? https://www.nxp.com/support/support:SUPPORTHOME I can not attach the Files here.
查看全文
Is there a driver for S32K312's SPI and SD card reading and writing? I have been working on a project about S32K312mcu to read and write SD card using SPI, but what has always confused me is that after configuring SPI for STM32's cubemx, it will automatically generate the initialization and enable of the SPI pins, while S32DS needs to configure it again. I wanted to try to transplant it using the STM32 driver code, but it always failed. So I would like to ask if anyone has SPI and SD card drivers for the S32K312 or S32K3 series. Re: 是否有S32K312的SPI与SD卡的读写驱动程序 As mentioned in case #00660962: We have no drivers for SD card in SPI mode for S32K3 devices. I guess that the libraries mentioned on the community are for Kinetis devices. So, you can take a look at the Kinetis SDK: https://www.nxp.com/design/design-center/development-boards-and-designs/software-development-kit-for-kinetis-mcus:KINETIS-SDK It's mentioned in the Features: "SDMMC, a software component supporting SD Cards and eMMC" Or you can take a look at following resources: https://www.nxp.com/docs/en/application-note/AN10406.pdf https://community.nxp.com/docs/DOC-330958
查看全文
是否有S32K312的SPI与SD卡的读写驱动程序 我最近一直在做一个关于S32K312mcu的关于SPI去读写SD卡的项目,但一直困惑我的是,stm32的cubemx配置SPI后会自动生成关于SPI引脚的初始化和使能,而S32DS却需要自己再次配置,我本想试着用STM32的驱动代码移植,可一直失败,所以想请问大家是否有S32K312或S32K3系列的SPI与SD卡的驱动。
查看全文
请求 UUU 工具的源代码。 尊敬的专家们, 您能否提供UUU工具的最新源代码链接? 此外,我还非常感激有关如何定制 UUU 工具的任何指导。 谢谢和问候, 拉维库马尔
查看全文
S32K312 の SPI および SD カードの読み取りと書き込み用のドライバーはありますか? S32K312mcuを使ってSPI経由でSDカードの読み書きを行うプロジェクトに取り組んでいますが、いつも困惑しています。STM32のcubemxではSPIを設定すると自動的にSPIピンの初期化と有効化が行われるのに対し、S32DSでは再度設定が必要なのです。STM32のドライバコードを使って移植しようとしたのですが、いつも失敗してしまいます。そこで、S32K312またはS32K3シリーズ用のSPIおよびSDカードドライバをお持ちの方がいらっしゃいましたら、ぜひ教えてください。
查看全文
LCD distortion sometimes after reboot on imx6 custom board I have a custom imx6 board and using MI0350B4T_5CL LCD (240*320).  My problem is sometimes after reboot the LCD doesnt work properly. If I store the fb0 as a PNG I can see the picture is true but that picture is not shown correctly on the screen. There is a distortion on the screen, most pixels are white with some black lines. It doesnt work anymore unless I reboot the system again. And it could happen again after reboot. I should say most of the times after reboot it works. This my device tree: mxcfb1: fb@0 { compatible = "fsl,mxc_sdc_fb"; disp_dev = "lcd"; interface_pix_fmt = "RGB24"; mode_str = "ILI9341-1"; default_bpp = <32>; int_clk = <0>; late_init = <0>; status = "okay"; };   lcd@0 { compatible = "fsl,lcd"; ipu_id = <0>; disp_id = <0>; default_ifmt = "RGB24"; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_ipu1>; status = "okay"; };   pinctrl_ipu1: ipu1grp { fsl,pins = < MX6QDL_PAD_DI0_DISP_CLK__IPU1_DI0_DISP_CLK 0x10 MX6QDL_PAD_DI0_PIN15__IPU1_DI0_PIN15 0x10 MX6QDL_PAD_DI0_PIN2__IPU1_DI0_PIN02 0x10 MX6QDL_PAD_DI0_PIN3__IPU1_DI0_PIN03 0x10 MX6QDL_PAD_DI0_PIN4__IPU1_DI0_PIN04 0x80000000 MX6QDL_PAD_DISP0_DAT0__IPU1_DISP0_DATA00 0x10 MX6QDL_PAD_DISP0_DAT1__IPU1_DISP0_DATA01 0x10 MX6QDL_PAD_DISP0_DAT2__IPU1_DISP0_DATA02 0x10 MX6QDL_PAD_DISP0_DAT3__IPU1_DISP0_DATA03 0x10 MX6QDL_PAD_DISP0_DAT4__IPU1_DISP0_DATA04 0x10 MX6QDL_PAD_DISP0_DAT5__IPU1_DISP0_DATA05 0x10 MX6QDL_PAD_DISP0_DAT6__IPU1_DISP0_DATA06 0x10 MX6QDL_PAD_DISP0_DAT7__IPU1_DISP0_DATA07 0x10 MX6QDL_PAD_DISP0_DAT8__IPU1_DISP0_DATA08 0x10 MX6QDL_PAD_DISP0_DAT9__IPU1_DISP0_DATA09 0x10 MX6QDL_PAD_DISP0_DAT10__IPU1_DISP0_DATA10 0x10 MX6QDL_PAD_DISP0_DAT11__IPU1_DISP0_DATA11 0x10 MX6QDL_PAD_DISP0_DAT12__IPU1_DISP0_DATA12 0x10 MX6QDL_PAD_DISP0_DAT13__IPU1_DISP0_DATA13 0x10 MX6QDL_PAD_DISP0_DAT14__IPU1_DISP0_DATA14 0x10 MX6QDL_PAD_DISP0_DAT15__IPU1_DISP0_DATA15 0x10 MX6QDL_PAD_DISP0_DAT16__IPU1_DISP0_DATA16 0x10 MX6QDL_PAD_DISP0_DAT17__IPU1_DISP0_DATA17 0x10 MX6QDL_PAD_DISP0_DAT18__IPU1_DISP0_DATA18 0x10 MX6QDL_PAD_DISP0_DAT19__IPU1_DISP0_DATA19 0x10 MX6QDL_PAD_DISP0_DAT20__IPU1_DISP0_DATA20 0x10 MX6QDL_PAD_DISP0_DAT21__IPU1_DISP0_DATA21 0x10 MX6QDL_PAD_DISP0_DAT22__IPU1_DISP0_DATA22 0x10 MX6QDL_PAD_DISP0_DAT23__IPU1_DISP0_DATA23 0x10 >; }; Also I added this to `mxc_lcdif.c`: +   /* 240x320 @ 65 Hz, pixel clk @ 6.0MHz */ +   "ILI9341-1", 65, 240, 320, 166667, //167515 +   .left_margin = 20, .right_margin = 10, +   .upper_margin = 2, .lower_margin = 4, +   .hsync_len = 10, .vsync_len = 2, +   .sync = 0, +   .vmode = FB_VMODE_NONINTERLACED, +   .flag = 0,},     Kernel logs: # dmesg | grep mxc [ 0.000000] Kernel command line: noinitrd consoleblank=0 console=ttymxc1,115200 root=/dev/mmcblk3p2 rootwait rw quiet panic=5 [ 0.000020] clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns [ 0.331436] 2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 25, base_baud = 5000000) is a IMX [ 0.332127] 21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 66, base_baud = 5000000) is a IMX [ 0.332169] console [ttymxc1] enabled [ 0.332647] 21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 67, base_baud = 5000000) is a IMX [ 0.333227] 21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 68, base_baud = 5000000) is a IMX [ 0.392363] clocksource: Switched to clocksource mxc_timer1 [ 0.421910] mxc_sdc_fb fb@0: registered mxc display driver lcd [ 0.484577] mxc_sdc_fb fb@0: 240x320 h_sync,r,l: 10,38,10 v_sync,l,u: 4,8,4 pixclock=6007000 Hz [ 0.923060] mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed [ 2.796337] mxc_sdc_fb fb@0: 240x320 h_sync,r,l: 10,38,10 v_sync,l,u: 4,8,4 pixclock=6007000 Hz Any idea? could it be a hardware issue? is there any way to reset LCD by application, driver or ...? Re: LCD distortion sometimes after reboot on imx6 custom board Okay, I updated the lcd initialization in the uboot and its fixed now. Thanks. Re: LCD distortion sometimes after reboot on imx6 custom board Thank you for your quick reply, but sorry I couldn’t understand what your suggestion was. Would you mind please clarify more. Regards Re: LCD distortion sometimes after reboot on imx6 custom board Hello, I think this is a software issue, try to export you current LCD to displa and change the dtb setting regard resolution. regards
查看全文
MPC8250ACZUMHBC IBIS model Hi Team, I need IBIS model for microprocessor MPC8250ACZUMHBC. Please share me at the earliest. Re: MPC8250ACZUMHBC IBIS model Thanks for your help. 789Bet Re: MPC8250ACZUMHBC IBIS model Hello @Santhosh_9056  Hope this email finds you well, I would like to inform you that in order to keep the information as clear as possible, and avoid any kind of confusion, I will provide you with the IBIS Model on the technical support case # 00661197. We will continue the communication on such case. Have a great day. BR, Hector Villarruel Re: MPC8250ACZUMHBC IBIS model OK Hector, Thank you! Hope I will get an IBIS model as requested at the earliest. Re: MPC8250ACZUMHBC IBIS model Hello @Santhosh_9056  Hope this post finds you well, This post is to inform you that we have looking for it. I will inform you as soon as we get an update. Have a great day. BR, Hector Villarruel
查看全文
Request to the source code for the UUU Tool. Dear Experts, Could you please provide the latest source code link for the UUU tool? Additionally, I'd appreciate any guidance on how to customize the UUU tool. Thanks & Regards,  Ravikumar  Re: Request to the source code for the UUU Tool. Hi, All source code for uuu tool can be found from mfgtools/releases  About customization, hope that the mfgtools/wiki be helpful for you. Regards Harvey
查看全文
UUUツールのソースコードへのリクエストです。 親愛なる専門家の皆様、 UUUツールの 最新のソースコードリンク を提供していただけますか? さらに、UUUツールをカスタマイズする方法についてのガイダンスをいただければ幸いです。 ありがとう&よろしく、 ラビクマール
查看全文
MPC8250ACZUMHBC IBISモデル こんにちはチーム、 マイクロプロセッサMPC8250ACZUMHBC用のIBISモデルが必要です。できるだけ早く教えてください。 日時:MPC8250ACZUMHBC IBISモデル ご協力いただきありがとうございます。 789ベット 日時:MPC8250ACZUMHBC IBISモデル OKヘクター、ありがとう! できるだけ早くご要望通りのIBISモデルが手に入ることを願っています。
查看全文
MPC8250ACZUMHBC IBIS模型 大家好, 我需要微处理器 MPC8250ACZUMHBC 的 IBIS 模型。请尽快与我分享。 回复:MPC8250ACZUMHBC IBIS模型 感谢您的帮助。 789Bet 回复:MPC8250ACZUMHBC IBIS模型 好的,赫克托,谢谢你! 希望能够尽快得到所要求的IBIS模型。
查看全文
EmiosCommon Settings Greyed out Hello, I'm trying to use PWM to control the intensity of the red LED on the S32K358, so I try to follow section 4 of this tutorial: https://community.nxp.com/t5/NXP-Model-Based-Design-Tools/Controlling-LED-intensity-with-ADC-and-PWM/ta-p/1747898 Like the tutorial 4.3, I set the Emios to enable  via Mcu -> McuModuleConfiguraion ->McuModeSettingConf - >McuPeripheral But my EmoisCommon settings are greyed out: I'm not sure what to do now. Without the EmoisCommon config, it's giving me the error on PwmemiosBufsRef Can anyone help me out? Thanks. Re: EmiosCommon Settings Greyed out Hi @Vast-Horizon  For being able to configure Emios settings inside Mcl, you should have the following check enabled inside the Mcl General Configuration tab, as illustrated below. Hope this helps, Irina
查看全文