Multi Source Translation Content

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

Multi Source Translation Content

讨论

排序依据:
LLCE CAN 控制器不能在 LLCE_CAN_STARTED 中工作,但始终处于 LLCE_CAN_START_PENDING 状态 我正在使用 SW32G_RTD_4.4_4.0.2_P03 在 s32g274a 设备上集成 LLCE 1.0.8,但遇到了一个问题:固件加载并成功启动后,Can_43_LLCE_Init 运行正常,Can_43_LLCE_eDriverStatus 状态变为 CAN_43_LLCE_READY,当使用参数 CAN_CS_STARTED 调用 Can_43_LLCE_SetControllerMode 时,固件成功执行了命令 LLCE_CAN_CMD_GETCONTROLLERMODE,然后调用 Can_Llce_GetControllerMode 并返回 LLCE_FW_SUCCESS,但返回的控制器状态始终为 LLCE_CAN_START_PENDING,我不确定哪里出了问题,所以我想得到一些有用的解决方案 回复:LLCE CAN 控制器无法在 LLCE_CAN_STARTED 中工作,但始终处于 LLCE_CAN_START_PEND 状态 谢谢! 我使用的是自定义板卡和自定义应用程序,但是参考llce_sample_app_af示例配置了llce can,现在我已经解决了这个问题,这是由can超时参数引起的:(Can Timeout Method)和(Can Timeout Duration); 在我们的定制板上,如果没有连接 CAN 收发器,llce_can0 和 llce_can2 硬件通道就无法工作,但如果 TJA1403 正确启用,llce_can1 和 llce_can3 就可以正常工作; 在我们的自定义应用程序中,(Can Timeout Method)和(Can Timeout Duration)分别设置为OSIF_COUNTER_DUMMY和65,在第一次启用llce_can0时,应用程序一直循环调用Can_Llce_MainFunctionMode, 但在将(Can Timeout Method)和(Can Timeout Duration)设置为OSIF_COUNTER_DUMMY和0.1后,使能llce_can0至llce_can3正常,只有llce_can1和llce_can3启动成功。 参考集成手册的5.3外围硬件要求,要求llce CAN控制器必须连接到正确启用的CAN收发器才能获得CAN总线电压水平,对吗?
查看全文
Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox Dear NXP Team, I am using MIMXRT1064-EVK and first I have started with Getting Started with the MIMXRT1064-EVK Evaluation Board  to set up a development environment with the MCUXpresso IDE toolchain. I have also successfully run the 'hello world' and 'led blinky' examples. After that, I have installed the i.MXRT1xxx support package and MBDT for MATLAB and Simulink, and started with the getting started guide for NXP i.MXRT1xxx MBDT with Simulink as follows:  Getting started with NXP i.MX RT1xxx Simulink Toolbox I have followed all the steps and instructions carefully but still, I am getting the error enclosed in the "mytest2024a_20240416_120817.txt" file. Thank you very much for your support and reply. Here, I am seeking your guidance to solve my mistake.  Best regards, Bvin Re: Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox The file format (.Id) is not supported in the attachment. So, I have not enclosed in my last reply. Thank you and regards, Bvin Re: Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox Hello Stefan, Thank you for your fast reply.  You are right about the linker file. The error itself is with the default linker file defined inside MBDT which I have used to configure my Simulink model. I have solved the error and modified the default linker file with the right name for the included files.  The default linker file (MIMXRT1064xxxxA.Id) path for MIMXRT1064 is as follows: C:\Users\***\AppData\Roaming\MathWorks\MATLAB Add-Ons\Toolboxes\NXP_MBDToolbox_IMXRT1xxx\mbdtbx_imxrt\devices\MIMXRT1064\linker_files\default\flash 1. Open file: MIMXRT1064xxxxA.Id 2. Look for the below-mentioned text lines:  INCLUDE "evkmimxrt1064_bubble_peripheral_Debug_library.ld" INCLUDE "evkmimxrt1064_bubble_peripheral_Debug_memory.ld" 3. Replaced the text lines mentioned in Step-2 with the following lines: INCLUDE "mimxrt1064xxxxA_library.ld" INCLUDE "mimxrt1064xxxxA_memory.ld" 4. Save file: MIMXRT1064xxxxA.Id 5. Now, I have run the Simulink model again and there was no error.  Enclosed you can find both the Original and Modified versions of the default linker files of the MBDT for your better understanding.  Best regards, Bvin Re: Getting an error with NXP i.MXRT1xxx Simulink Model Based Design Toolbox Hello, @Bvin  Looking into the log file you have posted, it seems to me that your are trying to use a custom linker file that does not exist. If may I ask, did you provided another linker file to your model? How did you configured your model? Can you provide more information on how did you configured it? Regards! Stefan.
查看全文
硬故障处理程序异常 jumptouserapplication() 函数将进入 NXP Kinetis Bootloader 2.0.0 中的硬故障处理程序 尝试调试但无法解决。 请帮忙 Kinetis L系列MCU 回复:Hardfault 处理程序异常 在 MCU 设置中设置闪存中的应用程序起始地址,解决了该问题 回复:Hardfault 处理程序异常 您好,我叫帕维尔,我会支持您的案例,但我会关注您的 3 个案例,我会在您上传一些图像的内部继续此工作。 此致, 帕维尔
查看全文
quote characters got removed from defined symbols Hello user support, I have a strange SW build problem with MCUXpresso IDE v24.9 that the quote "" got removed Predefined symbols, this causes unexpected errors, please tell me how to fix it? I found a post with same problem Solved: v11.0.1 "Manage SDK Components" removes " from C++ Symbols - NXP Community But not sure where is the solution. I tried to change the double quote with <> but still not working and actually it's better to know the problem and solve it. SSS_CONFIG_FILE="fsl_sss_config_elemu.h" SSCP_CONFIG_FILE="fsl_sscp_config_elemu.h" macro expansion Error log: Thanks! Re: quote characters got removed from defined symbols Hi @BLEDev  Based on your  image and error message. You can try changing SSS_CONFIG_FILE="fsl_sss_config_elemu.h" SSCP_CONFIG_FILE="fsl_sscp_config_elemu.h" to SSS_CONFIG_FILE='"fsl_sss_config_elemu.h"' SSCP_CONFIG_FILE='"fsl_sscp_config_elemu.h"' BR Hang
查看全文
Delay between frames on LPSPI Hello, uC: MWCT2016S (S32K312) When using 32 bit data width for ExternalBuffer in SPI Channel configuration I've noticed that there is still a 6us delay between 4 bytes frames on SPI (see attachment). Interesting thing is that delay length is the same as frame length (6,23 us). I am using Spi_SyncTransmit API. How to get rid (if possible) of this delay ? Re: Delay between frames on LPSPI Yes, this was it, I was using default timings in Tresos SPI configuration because i thought they are not taken into consideration since I'm not using CS driven by SPI engine but the GPIO. Thanks a lot, have a nice day Re: Delay between frames on LPSPI Hi @Grzechu81 , you need to setup LPSPI CCR1 register - field PCSPCS - please find detailed description in S32K3 RM rev9, chapter 70.6.1.13 . Best regards, Pavel
查看全文
CAN1 issue using S32K344 - Error Frame (stuff error) Hello everyone, I have two codes using CAN0 and CAN1, the first code using RTD (S32K3_RTD_2_0_1_D2207_ASR_REL_4_4_REV_0000_20220707) both channels are working properly with this configuration on S32DS: When I configure the same baudrate on EB Tresos 29.0, only the CAN0 is working, the CAN1 is returning error on BUSMASTER tool: This is the configuration on Tresos for CAN0 and CAN1: This is the code that I`m using for test: When I select the instance 0, I can see the message reaching the BUSMASTER correctly: Note: The transceiver is being configured correctly and as I said, using the RTD code it is working properly, so the hardware is validated. Anyone can help me with this issue? Thanks, MVR Re: CAN1 issue using S32K344 - Error Frame (stuff error) Hello @PetrS, I found the issue. We have a mosfet in the hardware to control the terminator resistor. If the mosfet is activated, the terminator circuit will be working. The CAN0 doesn't have this mosfet. I didn't know about it... Also the registers are different, so these two things fooled me. Thank you. Re: CAN1 issue using S32K344 - Error Frame (stuff error) Note: I set manually the bitrate only to see if this is the problem, but the generated code for bitrate are different... Re: CAN1 issue using S32K344 - Error Frame (stuff error) Ops, I made a mistake. CBT registers are not different, they are the same: Sorry, I took a screenshot when I was changing the bitrate. But with the bitrate the same, CBT are the same. Re: CAN1 issue using S32K344 - Error Frame (stuff error) Hello @PetrS , The generated code are the same, using the RTD 2.0.1 and the last version of AUTOSAR HF02 (S32K3_RTD_4_0_0_HF02_D2407_ASR_REL_4_7_REV_0000_20240725), but looking the registers, they are different: Into the "FlexCAN_Ip_Vs_0_PBcfg.c" in both generated code we can see these values (this is one example about bitrate, but the other configuration are the same): But the registers we can see different values: How is it possible since the generated code is the same? Again, the CAN0 is working with the new version, but CAN1 is not working. Note: Left side is the RTD 2.0.1 for S32DS - SW32K3_RTD_4.4_2.0.1 (S32K3_RTD_2_0_1_D2207_ASR_REL_4_4_REV_0000_20220707) and in the right side is the new library version for Tresos - SW32K3_RTD_R21-11_4.0.0_HF_02 (S32K3_RTD_4_0_0_HF02_D2407_ASR_REL_4_7_REV_0000_20240725). Thank you, MVR Re: CAN1 issue using S32K344 - Error Frame (stuff error) Hi, try to share simplified project so can be tested on EVB. Maybe other try could be testing behavior on latest RTD. BR, Petr Re: CAN1 issue using S32K344 - Error Frame (stuff error) Anyone can help me? Re: CAN1 issue using S32K344 - Error Frame (stuff error) Hello @PetrS , I changed the clock but still the channel 1 is not working... Do you have another idea? Re: CAN1 issue using S32K344 - Error Frame (stuff error) I checked the registers and they are the same for bit timing setting, even with different values set in EB... I will test with the another clock that you recommended. Re: CAN1 issue using S32K344 - Error Frame (stuff error) Hi, try to use same bit timing setting, even that the one you use in EB would be correct too. Compare values actually written to bit timing registers. Finally, do not use FIRC as PE clock source, select FXOSC, or PLL running from FXOSC. BR, Petr
查看全文
Register access protection Hello, Regarding access protection registers (PCNS, PCNP, ICNS, and ICNP) for the MCX A microcontroller, they are mentioned in the user manual, but not described. Would it be available a description for these registers? Thanks! MCXA Re: Register access protection OK. Thanks! Re: Register access protection Hello JosG, Update: As TrustZone is not present on this device, these registers are not used. We will request to correct RM Thanks, Jun Zhang
查看全文
S32K144 Can·t go to sleep Hi:       When I was using the power management module to put the MCU into sleep, I found that when I turned on the ADC module, or used UART_SendDataBlockinig, the mcu can`t go to sleep. The attachment is my project, I hope to get your help。  IDE:S32DS SDK:RTM4.01 Re: S32K144 Can·t go to sleep Re: S32K144 Can·t go to sleep Hi@ChenPeng3 This is expected, you should disconnect the debugger before MCU into any low power mode. Re: S32K144 Can·t go to sleep Hi@Senlent:            Thank you for your reply, I tried again without debugging and found that the result was correct.but I couldn't get into STOP1 mode when I connected the emulator.This problem is still solved, thank you。 Re: S32K144 Can·t go to sleep Hi@Chenpeng3 You are right, the picture is the result of my attempt to use PTB13 wake-up test. In fact, I tested your demo and after entering STOP1 mode(connect PTB13 to ground, make sure the wake up pin is in a stable state), the LPUART module does not output anything. Re: S32K144 Can·t go to sleep Hi,@Senlent:     when call POWER_SYS_SetMode(STOP1, POWER_MANAGER_POLICY_AGREEMENT); mcu should stop in standby, but lpuart send "Core frequency" message.you can connect PB13 to VCC or GND, if mcu go to sleep, lpuart should`t have message. thank you Re: S32K144 Can·t go to sleep Hi@ChenPeng3 I have tested your project and it works fine on myside. (I have connect PTB13 to ground.)
查看全文
如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? 我是 NXP 主板的新手。 我安装了 MCUXpresso IDE,但现在我没有电路板。我安装了 SDK 并为主板创建了项目“hello world”。我建立了我的项目。如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? 我可以在 IDE 中创建一个简单的 C/C++ 项目,构建并运行它吗? 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 我还有一个问题。我是否可以使用 MIMXRT1060-EVKB 在 tflm_cifar10 中运行 Opencv(我想在 Opencv 中使用一些调整大小的方法)。如果可以,请帮我配置它。谢谢。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 更改内存映射后,错误不再发生。但模拟运行的时间更长,并没有输出任何东西。也许 Keil/MDK 中 MIMXRT-1060 EVKB 的模拟出了问题。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 我遵循了您的指南,但是在使用模拟器调试时,出现了与“写入”权限相关的错误,如下所示。 *** 警告:使用 ARM Cortex-M4 模拟器。ARM Cortex-M7 特定功能未建模! 运行时代码大小限制:32K 加载“ram_0x1400_release\\hello_world.out” *** 错误 65:0xFFFFFFF4 处访问冲突:没有“写入”权限 我创建了 .ini文件来修复它在 0xFFFFFFF4 处的访问冲突 - Keil 论坛 - 支持论坛 - Arm 社区,但它不起作用。 你对我有什么建议吗?谢谢。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 感谢您的快速回复。我将按照以下步骤检查它是否有效。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 谢谢。您是否有关于在 Keil uvision 模拟器中运行 SDK 示例的教程? 据我了解,首先我需要下载适用于 Keil/MDK 的 MCUXpresso SDK,然后在 Keil(模拟器)中以调试模式运行。是吗? 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 我可能是看了MIMXRT1060-EVK 的教程,里面提到了 SW7。它使用 SW7 来设置启动模式。MIMXRT1060 -EVK 入门 | 恩智浦半导体 当然,谢谢。对于 MIMXRT1060-EVKB,我们需要使用 SW4。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 感谢您提供详细信息。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @Alex_Wang 谢谢。我们正在购买 Mimrt1060。我不记得该董事会的具体名称。我看到 mimrt1060 有两个版本:evk 和 evkb。MIMXRT1060-EVK / EVKB 之间有什么区别? 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? @ErichStyger谢谢你的帮助。 @Alex_Wang谢谢。我还有一个问题。当我通过微型 USB 电缆将开发板连接到 PC 进行调试时(具体来说,我将运行 TF Lite 模型),我是否需要通过 DC IN 5V 为开发板供电?据我了解,调试时不需要通过 DC IN 5V 为电路板供电。它仅适用于电路板的独立工作。 回复:如何在不连接开发板的情况下在 IDE 中运行“hello world”应用程序演示? 是的,您可以这样做(但当然不能使用 NXP SDK,因为它适用于目标板/设备)。 您可以使用主机 GNU gcc 编译器/调试器(单独安装)并使用 IDE 构建和调试应用程序,就像任何其他 Eclipse 发行版一样。事实是,您不是在进行交叉开发,而是在进行原生开发。 对于“真正的嵌入式”开发,您需要一个开发板或模拟器,例如QUEMU( https://www.qemu.org/ )。
查看全文
ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? 私はNXPボードの初心者です。 MCUXpresso IDEをインストールしましたが、ボードがありません。SDKをインストールし、ボード用のプロジェクト「hello world」を作成しました。私は自分のプロジェクトを構築しました。ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? IDEで単純なC / C ++プロジェクトを作成し、ビルドして実行できますか? Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  もう一つ質問があります。MIMXRT1060-EVKBとtflm_cifar10でOpencvを実行できるかどうか(Opencvでいくつかのサイズ変更方法を使用したい)。もしそうなら、私がそれを設定するのを手伝ってください。ありがとうございます。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  メモリマップを変更した後、エラーは発生しなかった。しかし、シミュレーションの実行時間が長くなり、何も出力されませんでした。Keil/MDKのMIMXRT-1060 EVKBのシミュレーションに何か問題があったのかもしれません。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  私はあなたのガイドに従いましたが、シミュレータでデバッグすると、次のように「書き込み」権限に関連するエラーが発生しました。 警告: ARM Cortex-M4シミュレータを使用しています。ARM Cortex-M7固有の機能はモデル化されていません! コードサイズ制限付きでの実行: 32K "ram_0x1400_release\\hello_world.out"を読み込みます エラー 65: 0xFFFFFFF4 でのアクセス違反 : 'write' アクセス許可がありません .iniを作成しましたそれを修正するためのファイル - Keilフォーラム - サポートフォーラム - Armコミュニティでアクセス0xFFFFFFF4違反 - しかし、それは機能しません。 何かおすすめはありますか?感謝。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  迅速な対応ありがとうございました。これらの手順に従って、機能するかどうかを確認します。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  感謝。SDKからのサンプルをKeil uvisionでエミュレータとして実行するためのチュートリアルはありますか? 私の理解では、まずKeil / MDK用のMCUXpresso SDKをダウンロードしてから、Keil(エミュレータ)でデバッグモードで実行する必要があります。そうなんですか。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  MIMXRT1060-EVKのチュートリアルを見たかもしれませんが、このチュートリアルではSW7について言及しています。SW7 でブートモードの設定に使用します。MIMXRT1060-EVK入門 |NXPセミコンダクターズ  もちろん、よろしくお願いいたします。MIMXRT1060-EVKBの場合、SW4を使用する必要があります。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  詳細な情報をありがとうございます。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @Alex_Wang  感謝。Mimrt1060を購入しています。ボードの正確な名前は覚えていません。mimrt1060には、evkとevkbの2つのバージョンがあるようです。MIMXRT1060-EVK / EVKBの違いは何ですか? Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? @ErichStygerご協力いただきありがとうございます。 @Alex_Wang感謝。もう一つ質問があります。デバッグのためにマイクロUSBケーブルでボードをPCに接続する場合(具体的にはTF Liteモデルを実行します)、DC IN 5Vでボードに電力を供給する必要がありますか?私の理解では、デバッグのためにDC IN 5Vでボードに電力を供給する必要はありません。これは、ボードのスタンドアロン作業専用です。 Re:ボードに接続せずにIDEで「hello world」アプリのデモを実行するにはどうすればよいですか? はい、これを行うことができます(ただし、ターゲットボード/デバイスの場合と同様に、NXP SDKは使用しません)。 ホストの GNU gcc コンパイラ/デバッガ (別途インストール) を使用し、他の Eclipse ディストリビューションと同様に、IDE でアプリケーションをビルドおよびデバッグできます。問題は、クロス開発ではなく、ネイティブ開発を行っているということです。 「実際の組み込み」開発には、ボードまたはシミュレータが必要になります。QUEMU (https://www.qemu.org/).
查看全文
eMIOS PWM output disable(OPWMB MODE) hello experts: when (OPWMB mode)PWM dutycylce is 100%, it can not be output disabled by ODIS register. But if the dutycycle <100%,the (OPWMB mode) PWM can be disabled output by ODIS register.Such as the dutycle is 99% the PWM(OPWMB mode) can be disable by ODIS register. And if the PWM mode is OPWFMB,it can be disbled by ODIS when it's dutycle is 100%. why?And have any method to solve? Re: eMIOS PWM output disable(OPWMB MODE) thanks,it works。i knew how to do。 Re: eMIOS PWM output disable(OPWMB MODE)  I used the demo but not solved problem? I toggled gpio_34 pin and connect gpio_34 with PTB4(TRGMUX_in,1).when the pwm dutycle is 50%.it can be disabled by ODIS. when the pwm dutycle is 100%.it still can not be disable. Re: eMIOS PWM output disable(OPWMB MODE) Hi@FRIDAY618 This is a test demo i made before and please have a try.
查看全文
CAN rxフィルタの設定方法 KW38の使用 CAN RXフィルタを作りたい 例: 0x18FFB034 ~ 0x18FFB534 , 0x19FFB028 どうか私を導いてください。 ありがとうございます 日時:CAN rxフィルターの設定方法 [シェルフ解決済み] レジスタに向かって1ビットシフトが必要です。 ベース>RXFGMASK = 0x10FFB034<<1;
查看全文
usb wake-up Imx93 can't wake up after standby. What should I do to wake up with usb? Re: usb wake-up before enter suspend mode, use the command like echo enabled > /sys/class/tty/ttyLP0/power/wakeup
查看全文
CLOCK MHZ S32K312 IN CLOCKING OPTION (UNDER HARDWARE SETTINGS ) I AM HAVING 0 MHZ , BUT I HAVE CONFIGURED IT TO S32K312 BOARD  Re: CLOCK MHZ S32K312 Hi, @paul_ephraim_13, The problem you are facing seems to be caused by the non-compliant setting of the configuration project. In the Hardware tab you will find the link from the Configuration Template section, make sure it points to the correct configuration project. After you correctly set the path to the configuration project, the frequency of 120 Mhz should be displayed correctly. Let us know how the check went. Best regards, Dragos
查看全文
如何设置 CAN 接收过滤器 使用KW38 我想制作一个 CAN RX 过滤器 例如:0x18FFB034 ~ 0x18FFB534 , 0x19FFB028 请指导我。 谢谢! 回复:如何设置 CAN 接收过滤器 [货架已解决] 需要向寄存器移动 1 位。 基址->RXFGMASK = 0x10FFB034<<1;
查看全文
How to set CAN rx filter Using KW38 I want to make a CAN RX filter ex: 0x18FFB034 ~ 0x18FFB534 , 0x19FFB028 Please Guide me. Thanks Re: How to set CAN rx filter [Shelf Solved] need 1bit shift toward register. base->RXFGMASK = 0x10FFB034<<1; Re: How to set CAN rx filter Hello @JungkyuHan1 CAN controller affiliated with each node implements a filter that checks the arbitration ID of a broadcast message and either accepts messages when the arbitration ID is within a particular range, or ignores messages outside of that range. Matching to a range of IDs should be possible by using ID acceptance masks. FlexCAN supports individual masking per MB (IRMQ bit set) or global masking scheme (IRMQ cleared).  Although there may not be specific documentation for this scenario, I will recommend you checking the MCUXpresso SDK API Reference Manual_MKW38 included in KW38 SDK documentation > docs folder. Chapter 14 describes the peripheral driver for FlexCAN module; please refer to "Configuration" APIs. Just for reference, you can take a look at the Controller Area Network (CAN) standard - NXP Community. Regards, Eduardo.
查看全文
nxpimage: how to accept input file on command line instead of config entry Hi, .bd file has the following entry: sources { elfFile = extern(0); } doing this nxpimage expects the name of the input file on the command line. How can I achieve the same behavior using .yaml files? regards Max Re: nxpimage: how to accept input file on command line instead of config entry Hi @mastupristi , The nxpimage -> hab application supports both bd files and YAML configuration files. The bd file support is primarily intended as a backward compatibility solution for customers transitioning from elftosb to spsdk. I recommend using YAML configurations, as this is the standard format across all spsdk applications. Unfortunately, passing the input image via the command line when using YAML configuration is not currently supported. However, we are exploring the possibility of allowing users to override any configuration parameter across all spsdk applications. If implemented, this would enable you to specify the elfFile as a command line parameter when using a YAML file. Please note that this feature has not yet been developed. Let me know if you need any further adjustments!
查看全文
i.MX93 lcdif. XRGB8888 framebuffer to bus format RGB888 Hello, I observe some flickering and others glitches when trying to setup a parallel LCD with imx93. I attached a picture of the output of the fb-test command. In the yellow rectangles there are glitches around pixels set to print text "GREEN" and "RED". In the yellow circle there is a glitch, as if lines where pixels were set (for the text) were shifted left. fb-test outputfb-test output The framebuffer is configured as XRGB8888 (bpp 32), size 800x480. The bus format is configured as rgb888. The output of the fbset command is : mode "800x480-0" # 😧 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz geometry 800 480 800 480 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Device tree node for bus format (MEDIA_BUS_FMT_RGB888_1X24) : &parallel_disp_fmt { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_lcdif>; fsl,interface-pix-fmt = "rgb888"; status = "okay"; ports { port@1 { reg = <1>; display_out: endpoint { remote-endpoint = <&panel_in>; }; }; }; };   Panel configuration : panel { compatible = "panel-dpi"; power-supply = <&reg_vdd_3v3>; backlight = <&backlight>; panel-timing { clock-frequency = <33260000>; hactive = <800>; vactive = <480>; hfront-porch = <40>; hback-porch = <88>; hsync-len = <128>; vfront-porch = <35>; vback-porch = <8>; vsync-len = <2>; de-active = <1>; pixelclk-active = <1>; }; port { panel_in: endpoint { remote-endpoint = <&display_out>; }; }; }; &lcdif { status = "okay"; }; As far as I know I configured things the right way, but maybe I missed something. Could you please advise ? The driver used is lcdifv3, from linux 6.1.55. Re: i.MX93 lcdif. XRGB8888 framebuffer to bus format RGB888 Hello, I guess this issue is due to clock frequency check your clock. Regards
查看全文
LVDS not working as per datasheet timing-parameter with TechNexion EDM-G-IMX8MM and WB baseboard Hello to NXP Community,  i am trying to Bring-up  Digiwise's 13-070WMLBIAG1- C  7" display with TechNexion EDM-G-IMX8MM and WB baseboard  custom board.  The changes i did in .dts and panel-simple.c as per datasheet mentioned here. The source code is Android - 11 by https://github.com/technexion-android/. DTS file : ... / dts/freescale/overlays/imx8mm-edm-g-wb-sn65dsi84-vl10112880-overlay.dts fragment@1 { target = <&mipi_dsi>; __overlay__ { status = "okay"; #address-cells = <1>; #size-cells = <0>; panel@0 { reg = <0>; compatible = "tn,dsi2lvds-panel"; backlight = <&lvds_backlight>; power-supply = <&reg_lvds_pwr>; dsi,flags = <0x0007>; dsi,format = <2>; dsi,lanes = <4>; panel-width-mm = <152>; panel-height-mm = <91>; bus-format = <0x1009>; /* MEDIA_BUS_FMT_RGB666_1X18 */ bus-flags = <1>; refresh-rate = <60>; rotate = <0>; /* horz-flip; */ /* vert-flip; */ panel-timing { clock-frequency = <33300000>; hactive = <800>; vactive = <480>; hfront-porch = <204>; hsync-len = <6>; hback-porch = <46>; vfront-porch = <22>; vsync-len = <3>; vback-porch = <23>; /* flags = DISPLAY_FLAGS_HSYNC_HIGH | DISPLAY_FLAGS_VSYNC_HIGH */ vsync-active = <1>; hsync-active = <1>; }; }; }; };   And in .... / drivers/gpu/drm/panel/panel-simple.c static const struct display_timing dsi2lvds_panel_timing = { .pixelclock = { 26400000, 33300000, 46800000}, .hactive = { 800, 800, 800}, .hfront_porch = { 16, 204, 354 }, .hback_porch = { 46, 46, 46 }, .hsync_len = { 1, 6, 40 }, .vactive = { 480, 480, 480 }, .vfront_porch = { 7, 22, 147 }, .vback_porch = { 23, 23, 23 }, .vsync_len = { 1, 3, 20 }, .flags = DISPLAY_FLAGS_HSYNC_HIGH | DISPLAY_FLAGS_VSYNC_HIGH, }; /* * @modes: Pointer to array of fixed modes appropriate for this panel. If * only one mode then this can just be the address of this the mode. * NOTE: cannot be used with "timings" and also if this is specified * then you cannot override the mode in the device tree. * @num_modes: Number of elements in modes array. * @timings: Pointer to array of display timings. NOTE: cannot be used with * "modes" and also these will be used to validate a device tree * override if one is present. * @num_timings: Number of elements in timings array. * @bpc: Bits per color. * @size: Structure containing the physical size of this panel. * @delay: Structure containing various delay values for this panel. * @bus_format: See MEDIA_BUS_FMT_... defines. * @bus_flags: See DRM_BUS_FLAG_... defines. * @refresh_rate: Refresh rate, e.g. 60MHz * @rotate: Rotation, e.g. 0, 90, 180, 270 degrees * @hflip: Horizontal flip, e.g. flip horizontally * @vflip: Vertical flip, e.g. flip vertically */ static const struct panel_desc_dsi dsi2lvds_panel = { .desc = { .timings = &dsi2lvds_panel_timing, .num_timings = 1, .bpc = 6, .size = { .width = 152, .height = 91,}, .bus_flags = DRM_BUS_FLAG_DE_LOW, }, .flags = MIPI_DSI_MODE_VIDEO | MIPI_DSI_CLOCK_NON_CONTINUOUS, .format = MIPI_DSI_FMT_RGB666, .lanes = 4, }; in result adb shell  >> dmesg  edm_g_imx8mm:/ # dmesg | grep -i dsi [ 0.625461] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to get blk_ctl [ 0.625627] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200 [ 0.625913] imx_sec_dsim_drv 32e10000.mipi_dsi: Failed to attach bridge: 32e10000.mipi_dsi [ 0.634275] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to bind sec dsim bridge: -517 [ 0.916209] sn65dsi84 0-002d: Valid sn65dsi84 chip id [ 0.952430] sn65dsi84 0-002d: Soft reset to default [ 1.080725] imx_sec_dsim_drv 32e10000.mipi_dsi: failed to get blk_ctl [ 1.080853] imx_sec_dsim_drv 32e10000.mipi_dsi: version number is 0x1060200 [ 1.081031] panel-simple-dsi 32e10000.mipi_dsi.0: >>>>Initial DSI config: flags = 1025, format = 1, lanes = 4 [ 1.081040] panel-simple-dsi 32e10000.mipi_dsi.0: >>>>Final DSI config: flags = 7, format = 2, lanes = 4 [ 1.081045] panel-simple-dsi 32e10000.mipi_dsi.0: panel-desc-dsi setting overridden from dt [ 1.081057] panel-simple-dsi 32e10000.mipi_dsi.0: panel-desc setting overridden from dt [ 1.081187] panel-simple-dsi 32e10000.mipi_dsi.0: Found suitable override. [ 1.081251] imx-drm soc@0:bus@32c00000:display-subsystem: bound 32e10000.mipi_dsi (ops imx_sec_dsim_ops) [ 1.084469] imx_sec_dsim_drv 32e10000.mipi_dsi: >>>DSI format: 4105, DSI clock = 33300 [ 1.084479] imx_sec_dsim_drv 32e10000.mipi_dsi: Chirag ==> imx_sec_dsim_encoder_helper_atomic_check:144 display_info->bus_formats[i]: 4105 bus_format:4105 num_bus_formats: 1 [ 1.106707] imx_sec_dsim_drv 32e10000.mipi_dsi: >>>DSI format: 4105, DSI clock = 33300 [ 1.106713] imx_sec_dsim_drv 32e10000.mipi_dsi: Chirag ==> imx_sec_dsim_encoder_helper_atomic_check:144 display_info->bus_formats[i]: 4105 bus_format:4105 num_bus_formats: 1 [ 14.191421] imx_sec_dsim_drv 32e10000.mipi_dsi: >>>DSI format: 4105, DSI clock = 33300 [ 14.191432] imx_sec_dsim_drv 32e10000.mipi_dsi: Chirag ==> imx_sec_dsim_encoder_helper_atomic_check:144 display_info->bus_formats[i]: 4105 bus_format:4105 num_bus_formats: 1 [ 15.078433] imx_sec_dsim_drv 32e10000.mipi_dsi: >>>DSI format: 4105, DSI clock = 33300 [ 15.078442] imx_sec_dsim_drv 32e10000.mipi_dsi: Chirag ==> imx_sec_dsim_encoder_helper_atomic_check:144 display_info->bus_formats[i]: 4105 bus_format:4105 num_bus_formats: 1 [ 15.528918] imx_sec_dsim_drv 32e10000.mipi_dsi: >>>DSI format: 4105, DSI clock = 33300 [ 15.528927] imx_sec_dsim_drv 32e10000.mipi_dsi: Chirag ==> imx_sec_dsim_encoder_helper_atomic_check:144 display_info->bus_formats[i]: 4105 bus_format:4105 num_bus_formats: 1 and here is screenshot :  * >>> However below mentioned changes in  panel-simple.c  :  static const struct panel_desc_dsi dsi2lvds_panel = { .desc = { .timings = &dsi2lvds_panel_timing, .num_timings = 1, .bpc = 8, .size = { .width = 165, .height = 105, .width = 152, .height = 91, }, .bus_flags = DRM_BUS_FLAG_DE_LOW, }, static const struct panel_desc_dsi dsi2lvds_panel = { .format = MIPI_DSI_FMT_RGB888, .lanes = 4, }; i got this result :  Despite this, I am facing issues with display initialization, and the panel does not seem to power up as expected. Could someone please assist me in reviewing the device tree configuration or suggest any required changes in the driver code (panel-simple.c) or other areas to help resolve this issue?  Additionally, any insights on changes that may be required in the SN65DSI84 bridge configuration or the DRM driver (panel-simple.c) would be appreciated. Thank you for your support! Best regards,  Ajaysinh.  Android Graphics & Display HW-Open-Source i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Linux Re: LVDS not working as per datasheet timing-parameter with TechNexion EDM-G-IMX8MM and WB baseboard The display issue was resolved by configuring the pixel format to RGB888 and setting the SN65DSI84 bridge register at 0x18 to a value of 0x72. This setup aligned the display's colour depth and timing parameters correctly, providing stable and accurate display output. thanks to @ Chavira for look at this ticket.  Re: LVDS not working as per datasheet timing-parameter with TechNexion EDM-G-IMX8MM and WB baseboard Hi @ajaysinh9484! Thank you for contacting NXP Support! For this case I recommend to contacting Technexion support they should have a patch or device tree using that display. Best Regards! Alejandro
查看全文
PN7160 devkit power(?) issue I'm working with a PN7160 devkit, the OM27160A1HN (I2C version), connected to a Karo QS93 which features an i.mx93 processor. The issue I'm encountering has to do with the two voltage inputs of the devkit (screenshot from the devkit user manual): It can be seen that both VDD(PAD) and VDD(UP)/VBAT are supposed to work with a 3.3V input. But the issue I'm running into, is that the devkit can't detect a tag, when using this 3.3V input voltage. ONLY when providing VDD(UP)/VBAT with 5V from the Karo QS93, the devkit will actually detect the tag and can successfully read its data. When providing this pin with 3.3V the tag CAN NOT be detected. Regarding the software: I use the libnfc-nci library and the provided nfcDemoApp to verify the devkit. Link to the library: https://github.com/NXPNFCLinux/linux_libnfc-nci I run the demoApp with the 'poll' argument, and the tag is only detected and read out successfully, when using 5v for VDD(UP)/VBAT. With 3.3V, nothing happens, whatever I try. The demoAPP is just stuck on "waiting for tag" in that case. I've read through all the related documentation and have not been able to find any remarks that address this issue. So for now I'm a bit stuck on this, any help would be greatly appreciated! Re: PN7160 devkit power(?) issue Disabling the TXLDO check indeed resolved the issue. Thanks alot! Re: PN7160 devkit power(?) issue Hi @kowalski_analysis  There is a very similar issue described in AN13892.   It could happen that PN7160 can not generate an RF field due to bad power supply on VUP/TVDD or a bad power configuration.  Typically happens once 3.3V as the VUP has been used.  https://www.nxp.com/docs/en/application-note/AN13892.pdf -> 9 TXLDO check   Can you try to disable the TXLDO check?  Regards Daniel
查看全文