Multi Source Translation Content

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

Multi Source Translation Content

讨论

排序依据:
RT1170EV 呼び出し: MCU C++ リンカー arm-none-eabi-c++ -nostartfiles -nodefaultlibs -nostdlib -mcpu=cortex-m7 -mfpu=fpv5-d16 -mfloat-abi=hard -mthumb -T evkbmimxrt1170_freertos_generic_cm7_Debug.ld -o "evkbmimxrt1170_freertos_generic_cm7.axf"./xip/dcd.o./xip/evkbmimxrt1170_flexspi_nor_config.o ./xip/fsl_flexspi_nor_boot.o ./xip/xmcd.o ./utilities/str/fsl_str.o ./utilities/debug_console_lite/fsl_debug_console.o ./utilities/fsl_assert.o ./utilities/fsl_memcpy.o ./startup/boot_multicore_slave.o ./startup/startup_mimxrt1176_cm7.o ./source/freertos_generic.o ./source/semihost_hardfault.o ./freertos/freertos-kernel/ポータブル/MemMang/heap_4.o ./freertos/freertos-kernel/ポータブル/GCC/ARM_CM4F/port.o ./freertos/freertos-kernel/croutine.o ./freertos/freertos-kernel/event_groups.o ./freertos/freertos-kernel/list.o ./freertos/freertos-kernel/queue.o ./freertos/freertos-kernel/stream_buffer.o ./freertos/freertos-kernel/tasks.o ./freertos/freertos-kernel/timers.o ./freertos/FreeRTOSAddons/cpp/Source/ccondition_variable.o ./freertos/FreeRTOSAddons/cpp/Source/cevent_groups.o ./freertos/FreeRTOSAddons/cpp/Source/cmem_pool.o ./freertos/FreeRTOSAddons/cpp/Source/cmutex.o ./freertos/FreeRTOSAddons/cpp/Source/cqueue.o ./freertos/FreeRTOSAddons/cpp/Source/cread_write_lock.o ./freertos/FreeRTOSAddons/cpp/Source/csemaphore.o ./freertos/FreeRTOSAddons/cpp/Source/ctasklet.o ./freertos/FreeRTOSAddons/cpp/Source/cthread.o ./freertos/FreeRTOSAddons/cpp/Source/ctickhook.o ./freertos/FreeRTOSAddons/cpp/Source/ctimer.o ./freertos/FreeRTOSAddons/cpp/Source/cworkqueue.o ./freertos/FreeRTOSAddons/c/Source/dlist.o ./freertos/FreeRTOSAddons/c/Source/mem_pool.o ./freertos/FreeRTOSAddons/c/Source/queue_simple.o ./freertos/FreeRTOSAddons/c/Source/read_write_lock.o ./freertos/FreeRTOSAddons/c/Source/slist.o ./freertos/FreeRTOSAddons/c/Source/stack_simple.o ./freertos/FreeRTOSAddons/c/Source/workqueue.o ./freertos/FreeRTOSAddons/c/Source/zero_copy_queue.o ./ドライバ/fsl_anatop_ai.o ./ドライバ/fsl_cache.o ./ドライバ/fsl_clock.o ./ドライバ/fsl_common.o ./ドライバ/fsl_common_arm.o ./ドライバ/fsl_dcdc.o ./ドライバ/fsl_gpc.o ./ドライバ/fsl_gpio.o ./ドライバ/fsl_lpuart.o ./ドライバ/fsl_mu.o ./ドライバ/fsl_pgmc.o ./ドライバ/fsl_pmu.o ./ドライバ/fsl_soc_src.o ./device/system_MIMXRT1176_cm7.o ./component/uart/fsl_adapter_lpuart.o ./board/board.o ./board/clock_config.o ./board/hardware_init.o ./board/pin_mux.o D:/nxp/MCUXpressoIDE_25.6.136/ide/plugins/com.nxp.mcuxpresso.tools.win32_25.6.0.202501151204/tools/bin/../lib/gcc/Arm-none-eabi/14.2.1/../../../../Arm-none-eabi/bin/ld.exe: 警告: evkbmimxrt1170_freertos_generic_cm7.axf には RWX 権限を持つ LOAD セグメントがあります D:/nxp/MCUXpressoIDE_25.6.136/ide/plugins/com.nxp.mcuxpresso.tools.win32_25.6.0.202501151204/tools/bin/../lib/gcc/Arm-none-eabi/14.2.1/../../../../Arm-none-eabi/bin/ld.exe: ./xip/fsl_flexspi_nor_boot.o:(.boot_hdr.ivt+0x10):undefined reference to `__boot_hdr_boot_data_loadaddr__' D:/nxp/MCUXpressoIDE_25.6.136/ide/plugins/com.nxp.mcuxpresso.tools.win32_25.6.0.202501151204/tools/bin/../lib/gcc/Arm-none-eabi/14.2.1/../../../../Arm-none-eabi/bin/ld.exe: ./xip/fsl_flexspi_nor_boot.o:(.boot_hdr.ivt+0x14): `__boot_hdr_ivt_loadaddr__' への未定義の参照 collect2.exe:エラー: ld は 1 の終了ステータスを返しました メイク[1]: *** [メイクファイル:82: evkbmimxrt1170_freertos_generic_cm7.axf]エラー1 make: *** [makefile:73: all] エラー 2 「make -r -j8 all」は終了コード 2 で終了しました。ビルドが不完全である可能性があります。 ===================================================== 「アプリケーションを RAM にリンク」を選択すると、上記のエラーが発生します。選択されていない場合はエラーは報告されません Re: RT1170EV こんにちは@yanpingzhuさん 追加情報をありがとうございます。これは、C ファイルと CPP ファイルを管理するための IDEs のリンク スクリプトの違いによるものと思われます。次の 2 つのマクロ定義は手動で変更する必要があります。これはコンパイルされて成功します。 よろしくお願いします、 ギャビン Re: RT1170EV ご回答ありがとうございます Cコンパイラを使用して「アプリケーションをRAMにリンク」を選択した場合にはエラーは発生しません。C++コンパイラを使用して「アプリケーションをRAMにリンク」を選択した場合にのみエラーが発生します。 Re: RT1170EV こんにちは@yanpingzhuさん NXP MIMXRTシリーズにご興味をお持ちいただきありがとうございます。 提供されたエラー メッセージから、問題はリンク スクリプト内の `__boot_hdr_ivt_loadaddr __' and `__ boot_hdr_boot_data_loadaddr__' によって発生しているようです。 ただし、Link-to-RAM は XIP イメージを生成しないため、IDEs の車載生成スクリプトは異なり、boot_hdr セクションが含まれません。したがって、「リンカー スクリプトの管理」がチェックされていることを確認し、クリーンアップしてから再度コンパイルしてください。
查看全文
[S32K388] BIST Prerequisite Details Clarifications Hi Team, Customer is looking for some clarifications about information updated in latest version of the SAF/SPD Bist User Manual: Looking into the newer version SAF BIST documentation, this is now the wording mentioned: 1) Is this an incorrect statement for the S32K388 device. Reading this as stated, it seems to imply that for the S32K388 it is recommended to run the BIST on CM7_0 core. This seems to be in stark contrast with what your device safety manual is suggesting that all safety checks should be running on the master safety core (AOU_SW_SAFETY_CORE_USAGE), and the master safety core is defined as CM7_2 core on the S32K388. 2) Can you address the below questions for clarification: Is it mandatory that the cores that the BIST is NOT executing on are "disabled", or just a recommendation?  Does "disabled" here mean the cores are literally halted in hardware and are not at all executing, or if they are simply in a software wait loop with all interrupts disabled and waiting for the BIST to be completed good enough?  If it really needs to be halted in hardware, does this effectively exclude the option for me to enable those cores to start automatically through the IVT boot configuration word, and instead have to keep those cores off until after the BIST has executed (and I'd have to develop a software strategy for manually starting the other cores)? Thanks, Daniel V. Safety_SW Re: [S32K388] BIST Prerequisite Details Clarifications Hello Daniel, customer is right about what is master safety core on K388, it will be fixed in BIST UM. As per Safety architects, it doesn't necessarily mean it must be CM7_2, if customer wants to run ASIL_D on CM7_0, and has K388_LS chip variant it is possible to consider CM7_0 as master safety core and run SAF from that core. Second question is HW related, but simple answer is to keep the other cores in reset, which should be default state. Typically which cores are enabled is set in startup in Boot Configuration Word as customer mentioned, so yes to run online BIST on K3 requires to run the other cores after BIST within customer SW - I think using MCU driver via Mcu_SetMode(). It's a good question whether it should be enough to put the other cores into SleepMode or some loop where it will do nothing, but this use case is not validated - HW team need to confirm. My understanding is that BIST is accessing some HW and Memories which can be used by other cores (check RM e.g. for instruction and data cache blocks covered be MBIST) if there would be some app running so it would corrupt correct BIST execution. Kind Regards, Radoslav
查看全文
sBoot NCF 测试 - 反应配置 您好, 在目前的配置中,eMcem 模块中的 R1 反应配置了少数 FCCU 故障。 在 sBoot 中配置 FCCU 测试时,无法使用 R1 配置。只有 R1_R2 可用。 为 R1_R2 配置时,预计将启用 NMI,这将导致当前应用程序的 RESET。 如何仅为 sBoot FCCU NCF 测试配置 R1? SAF 版本:SW32G_SAF_2.0.2_QLP01_D2410 Re: sBoot NCF test - Reaction configurations 你好,@Irshad2225 谢谢你的帖子。 我刚刚检查了 sBoot 的代码。 没有只定义 R1 反应,因此不能将其设置为 R1 对您的不便,我深表歉意。 BR 切宁  
查看全文
S32k3の外部GPIO割り込みの例 こんにちは、 S32K3X4EVB-Q172のプッシュボタンSW5を使用して、単純な外部GPIO割り込みを実行しようとしています。 私はhttps://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/SIUL2-external-interrupt-example-project-using-S32K3-RTD-without/ta-p/1552335に従っています。 これはメインファイルです しかし、「 SIUL2_ICU_IP_INSTANCE」が宣言されていないというエラーが発生し、他のエラーも発生します SIUL2 INSTANCEは0に設定されていますが、該当するファイルでは更新されていません 設定で何かが足りないのでしょうか? S32K3X4EVB-Q172ボードでプッシュボタンとLEDトグルを使用したGPIO割り込みについて、これまたは利用可能な例を誰か助けてくれませんか? プロジェクト フォルダーは下記に添付されています。RTD 5.0.0 を使用しています。 Re: External GPIO interrupt example in S32k3 こんにちは@AntoZ この HOWTO は RTD バージョン 2.0.0 を使用して実装され、その後のリリースでいくつかの変更が導入されました。その結果、新しいバージョンの手順に従うと、いくつかの矛盾が生じる可能性があります。 予期される構成パラメータの不一致により、Siul2_Icu_Ip_Init() 関数のエラー メッセージが表示されます。関数に渡されたパラメータは予期された名前では存在しません。別の識別子で生成されました。 たとえば、 Siul2_Icu_Ip_0_Config_PB_BOARD_InitPeripheralsを使用する代わりに。以下を使用する必要があります: Siul2_Icu_Ip_0_Config_PB 。この正しい設定はSiul2_Icu_Ip_SA_PBcfg.hにあります。ファイル。 より良い参考のために、Siul2_Icu_Ip_BlinkLed_S32K344 の例を確認することをお勧めします。これは、HOWTO で説明されているものと同じアプリケーションを実装します。この例はRTDパッケージに含まれており、例から新しいプロジェクトを作成するときに簡単にアクセスできます。 BR、ヴェインB
查看全文
FRDM-MCXA156: FlexPWM not working as intended Hello, I'm trying to use the FlexPWM peripheral of the MCXA156 SoC in a FRDM_MCXA156 devboard using Zephyr but I can't get it to fully work. Whatever I try, the pulse and period seen in the associated output pins do not correspond with the values I am assigning it. I have found a way to reproduce the issue using the blinky_pwm example. Using the reproduction steps below I only get a small pulse of less than 1ms in pin P3_6 (where channel 0 of flexpwm0_pwm0 is linked) whenever the PWM is reconfigured, but nothing in between. AFAIK the example should be setting a 50% duty cycle signal and that is not what I am seeing. It is not a regression; I've tried the same thing on a semi-recent commit 0d46a93 and commit 9f6fdae (Where PWM was implemented for the FRDM_MCXA156 board) and the issue still happens. Steps to reproduce: west init repro cd repro && west update Copy the following overlay file to samples/basic/blinky_pwm/boards/frdm_mcxa156.overlay: #include / { pwmleds { compatible = "pwm-leds"; pwm_led_0: pwm_led_0 { pwms = <&flexpwm0_pwm0 0 PWM_MSEC(1) PWM_POLARITY_NORMAL>; label = "PWM LED 0"; }; }; aliases { pwm-led0 = &pwm_led_0; pwm-0 = &flexpwm0_pwm0; }; }; Then: cd zephyr && west build -b frdm_mcxa156 samples/basic/blinky_pwm west flash See incorrect behavior when probing P3_6. Logs don't show much: [00:00:00.000,069] <dbg> pwm_mcux: pwm_mcux_init: Set prescaler 128, reload mode 2 *** Booting Zephyr OS build v4.2.0-2444-g0d46a934171a *** PWM-based blinky Calibrating for channel 0... [00:00:00.017,179] <err> pwm_mcux: Too long period (750000), adjust pwm prescaler! [00:00:00.025,412] <err> pwm_mcux: Too long period (375000), adjust pwm prescaler! [00:00:00.033,645] <err> pwm_mcux: Too long period (187500), adjust pwm prescaler! [00:00:00.041,879] <err> pwm_mcux: Too long period (93750), adjust pwm prescaler! Done calibrating; maximum/minimum periods 62500000/7812500 nsec Using period 62500000 Using period 31250000 Using period 15625000 Using period 7812500 Using period 15625000 Using period 31250000 ... Attached is the (compressed) ELF final binary I got doing these steps. I hope this is just a mistake on my side. Appreciate any feedback on this matter! Thanks in advance Re: FRDM-MCXA156: FlexPWM not working as intended Hi @aperea-cc, Thanks for the suggestions of documenting this somewhere on the Zephyr driver. I will pass it on to the Zephyr team for their consideration. Re: FRDM-MCXA156: FlexPWM not working as intended Hello, Thank you very much for your response and support. Yesterday I did the same thing (Comparing with the example from the official NXP SDK) and ended up noticing that the FlexPWM peripheral only works if the CPU is active. That would explain why in Zephyr doesn't work, since it sleeps for 4 seconds after every PWM configuration. I don't think there's any elegant solution for this problem in Zephyr, since we'd need the CPU busy if we want the PWM to work, so I'm figuring out if the same behaviour I want can be reproduced using FlexIO instead. From reading the reference manual it seems that FlexPWM is the only non-CPU-related peripheral that exhibits this behavior. It's in the same power management category as the watchdog, cache controller or CPU itself. Maybe this could be documented in the Zephyr driver somewhere; I think it'd save a lot of time to newcomers to the SoC. Re: FRDM-MCXA156: FlexPWM not working as intended Hi @aperea-cc, I imported the blinky_pwm example code from the Zephyr repository and added the overlay that you shared. Indeed, the P3_6 pin outputs small pulses instead of actual PWM signals. After this test, I imported the normal pwm example (without Zephyr) and it worked properly with P3_6. This proves that the issue is not hardware, but rather software related. I will continue investigating whether the issue is on application level or on driver level on the Zephyr example. If you have any further developments, let me know. BR, Edwin.
查看全文
External GPIO interrupt example in S32k3 Hi there, I'm trying to execute simple external GPIO interrupt in S32K3X4EVB-Q172 using push button SW5 I'm followed the https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/SIUL2-external-interrupt-example-project-using-S32K3-RTD-without/ta-p/1552335 This is main file But i'm getting an error as "SIUL2_ICU_IP_INSTANCE" not declared and other errors too SIUL2 INSTANCE is configured as 0 but its not updated in respected file Am I missing something in configuration, Can anyone help this or any example available for GPIO interrupt with push button and led toggle with S32K3X4EVB-Q172 board The project folder is attached bellow , I'm using RTD 5.0.0. Re: External GPIO interrupt example in S32k3 Hi @AntoZ  This HOWTO was implemented using RTD version 2.0.0, and several changes have been introduced in subsequent releases. As a result, some discrepancies may appear when following the instructions with newer versions. The Siul2_Icu_Ip_Init() function error message is displayed due to a mismatch in the expected configuration parameter. The parameter passed to the function does not exist under the expected name—it was generated with a different identifier. For example, instead of using: Siul2_Icu_Ip_0_Config_PB_BOARD_InitPeripherals. You should use: Siul2_Icu_Ip_0_Config_PB. This correct configuration can be found in the Siul2_Icu_Ip_SA_PBcfg.h file. For better reference, I recommend reviewing the Siul2_Icu_Ip_BlinkLed_S32K344 example. It implements the same application as described in the HOWTO. This example is included with the RTD package and can be easily accessed when creating a new project from an example BR, VaneB
查看全文
External GPIO interrupt example in S32k3 Hi there, I'm trying to execute simple external GPIO interrupt in S32K3X4EVB-Q172 using push button SW5 I'm followed the https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/SIUL2-external-interrupt-example-project-using-S32K3-RTD-without/ta-p/1552335 This is main file But i'm getting an error as "SIUL2_ICU_IP_INSTANCE" not declared and other errors too SIUL2 INSTANCE is configured as 0 but its not updated in respected file Am I missing something in configuration, Can anyone help this or any example available for GPIO interrupt with push button and led toggle with S32K3X4EVB-Q172 board The project folder is attached bellow , I'm using RTD 5.0.0. Re: External GPIO interrupt example in S32k3 Hi @AntoZ  This HOWTO was implemented using RTD version 2.0.0, and several changes have been introduced in subsequent releases. As a result, some discrepancies may appear when following the instructions with newer versions. The Siul2_Icu_Ip_Init() function error message is displayed due to a mismatch in the expected configuration parameter. The parameter passed to the function does not exist under the expected name—it was generated with a different identifier. For example, instead of using: Siul2_Icu_Ip_0_Config_PB_BOARD_InitPeripherals. You should use: Siul2_Icu_Ip_0_Config_PB. This correct configuration can be found in the Siul2_Icu_Ip_SA_PBcfg.h file. For better reference, I recommend reviewing the Siul2_Icu_Ip_BlinkLed_S32K344 example. It implements the same application as described in the HOWTO. This example is included with the RTD package and can be easily accessed when creating a new project from an example BR, VaneB
查看全文
链接服务器错误:没有可用端口 我们有一个 MIMXRT798S 板,我们正在尝试使用 McuLink。我们从 NXP 网站下载了 Linux 版 Linkserver 25.7.33。当我们运行它时,会收到一条错误信息 /usr/local/LinkServer/LinkServer gdbserver MIMXRT798S:EDNA INFO: Exact match for MIMXRT798S:EDNA found INFO: Selected device MIMXRT798S:EDNA CRITICAL: Critical error ERRMSG: launcher.core.utils.NoFreePortError: No available port in range 11111:11211 for host 您能帮助我们解决这个问题吗?谢谢。 开发板 Re: LinkServer error: No available port 你好@TaliB i.MX RT700 仍在试生产中,因此,我只想提醒您,您的主要支持渠道是您的直接恩智浦代表。 你是本机运行 Linux 还是在虚拟机中运行?另外,你在使用哪个发行版? 我看到您正在运行 GDB 服务器命令。我不知道您的操作系统是否存在这个问题。我们可以通过测试其他链接服务器命令来缩小问题范围。您可以尝试使用 LinkFlash 图形用户界面轻松测试其他命令。 谢谢、 迪亚戈
查看全文
RT I.MX 1172 Secure RM and application note can not be found Hello all currently ,we are developing the project based on I.MX RT 1172. When we want refer tohe Secure Reference manual, we didn't find the source in the RT1172 page. and the secure debug application note and other application is also not found in anywhere. Cloud someone can tell me how to get the latest RT1172 Secure RM and RT1172 related application note? Re: RT I.MX 1172 Secure RM and application note can not be found Thanks for your updated information, Have you tried applying for additional permissions? Best Regards Re: RT I.MX 1172 Secure RM and application note can not be found I  think I should have the right to access the secure file. Because we have signed the NDA. the RT is also checked and granted from the secure file page.(refer to the below image.) Therefore, I don't how to download the this file.(We also contact the NXP FAE, he is also can not find and get this SRM of RT1172, cloud you please check it how to get the SRM of the RT1172? ) Re: RT I.MX 1172 Secure RM and application note can not be found Hi @Yiming2 , Thank you so much for your interest in our products and for using our community. I think you have no secure access rights, please check the following link. https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS Wish it helps you. If you still have question about it, please kindly let me know. Wish you a nice day! Best Regards MayLiu Re: RT I.MX 1172 Secure RM and application note can not be found this is the page which I try to find the SRM. But there is empty. https://www.nxp.com/products/i.MX-RT1170
查看全文
RT I.MX 1172 Secure RM and application note can not be found Hello all currently ,we are developing the project based on I.MX RT 1172. When we want refer tohe Secure Reference manual, we didn't find the source in the RT1172 page. and the secure debug application note and other application is also not found in anywhere. Cloud someone can tell me how to get the latest RT1172 Secure RM and RT1172 related application note? Re: RT I.MX 1172 Secure RM and application note can not be found Thanks for your updated information, Have you tried applying for additional permissions? Best Regards Re: RT I.MX 1172 Secure RM and application note can not be found I  think I should have the right to access the secure file. Because we have signed the NDA. the RT is also checked and granted from the secure file page.(refer to the below image.) Therefore, I don't how to download the this file.(We also contact the NXP FAE, he is also can not find and get this SRM of RT1172, cloud you please check it how to get the SRM of the RT1172? ) Re: RT I.MX 1172 Secure RM and application note can not be found Hi @Yiming2 , Thank you so much for your interest in our products and for using our community. I think you have no secure access rights, please check the following link. https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS Wish it helps you. If you still have question about it, please kindly let me know. Wish you a nice day! Best Regards MayLiu Re: RT I.MX 1172 Secure RM and application note can not be found this is the page which I try to find the SRM. But there is empty. https://www.nxp.com/products/i.MX-RT1170
查看全文
这是否能用于重写 OFDMA TF 文件? 我有三个 TF 文件(TF_Config_20MHz.txt、TF_Config_40MHz.txt、TF_Config_80MHz.txt)。 是否可以重写 TF 文件的内容或添加新的 TF 文件? 20 MHz 和 40 MHz 带宽以全音输出, ,但 80 MHz 带宽似乎以 106 音输出。 我还需要将费率调整为最差费率。 在此先表示感谢。 Re: Is this able to OFDMA TF-Files of Rewrite? 你好,Christine_Li 非常感谢你的回复。 我会考虑的。 Re: Is this able to OFDMA TF-Files of Rewrite? 你好,@kazus 我在我们的 LABTOOL_SDK-2.0.0.39.0 中查看了最新版本,是的,您说得没错,默认的20MHz 和 40MHz 带宽输出的是全音。 对于 20MHz:TrigUserInfoField=5;0;61;1;0;0;0;80,根据图 14。UM11749 中20 MHz 带宽的 RU 索引值,此处为 61表示使用全音调。 对于 40MHz:TrigUserInfoField=5;0;65;1;0;0;0;80,根据图 15。UM11749 中40 MHz 带宽的 RU 索引值,此处 65 表示使用全音。 但在默认情况下,80 兆赫的输出有 26 个音调 对于 80MHz:TrigUserInfoField=5;0;0;1;0;0;0;80,根据图 16。UM11749 中 80 MHz 频率的 RU 指数值,红色 0 表示使用 26 个音调。 如果您想改为使用全音调,请将该段从 0 改为67. 要调整速率,可以编辑 TrigUserInfoField 中的第五段。我认为默认 .txt20MHz、40MHz 和 80MHz 的文件,我们已经在使用最差的文件:MCS0。 如果要更改为其他 MCS 数据速率,如 MCS 7 数据速率,可将第五段改为 7,如下所示: TrigUserInfoField=5;0;3;1;7;0;0;80//RU 设置为 3, MCS 设置为 7 以上红色字体为 RU 指数(用于音调),蓝色字体为 MCS 数据速率。 希望我的解释能让你明白。 顺祝商祺! Christine。 Re: Is this able to OFDMA TF-Files of Rewrite? 你好,@kazus 请允许我向电台的同事确认一下。 一旦确认,我会通知你们。 顺祝商祺! Christine。 Re: Is this able to OFDMA TF-Files of Rewrite? 嗨, Christine_Li 20MHz 和 40MHz 带宽以全音输出,但 80MHz 带宽似乎以 106 音输出。 此外,我还需要将费率调整为最差费率。 我该如何重写下面的文件? 另外,请介绍一下 40MHz 和 80MHz。 =========================================== OFDMA_20MHz.txt FRAME_CTRL_TYPE=1\\ IEEE_TYPE_CTRL_TYPE=2\\ TRIGGER \\配置持续时间字段 \ 最大持续时间 FRAME_DURATION=5484\0x156C \\ 配置触发器帧的公共信息字段\\ HE_Trigger_Frame.triggerField.triggerType = BASIC_TRIGGER; \\ HE_Trigger_Frame.triggerField.ULLEN = 1000;\\ Max\ He_Trigger_Frame.triggerField.csRequired = 1000;\\ Max\ He_trigger_Frame.triggerField.csRequired = 1000; \\ Max \ He_trigger_Frame._frame.trigcommonfield.ULBW = TB_BW_20MHZ;\\ HE_Trigger_Frame.trigcommonfield.LTFTYPE = LTF_1_GI_1_6US;\\ HE_Trigger_Frame.trigcommonfield.LTFSYMBOL = 0;\\ HE_Trigger_Frame.trigcommonfield.LTFSYMBOL = 0;\\ HE_Trigger_Frame.trigcommonfield. trigger_frame.trigcommonfield.ulstBC = FALSE; \\ HE_Trigger_frame.trigcommonfield.ldpcess = TRIGGER_FRAME.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigcommonfield.aptxpwr = 0\\ HE_\ he_trigger_frame.trigcommonfield.spatialReuse = 65535; \\ HE_Trigger_Frame.trigcommonfield.doppler = FALSE;\\ He_trigger_frame.trigger_frame.trigger_frame.trigcommonfiel TrigCommonField=0;1000;0;0;0;1;0;0;0;1;0;1;0;65535;0;511 \\ 配置触发帧的用户信息字段\\ he_trigger_Frame.triguserInfoeld.aid12 = (5 & 0xFFF); \\ He_trigger_frame.triguserInfoeld.ruallocreg = 0;\\ He_trigger_Frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_frame.trigger_framfield.ulcodingType = CODING_TYPE_LDPC; \\ HE_Trigger_Frame.triguserInfoeld.ulmcs = 0;\\ HE_Trigger_Frame.trigserInfoild.uldCM = FRAME; \\ HE_Trigger_Frame.triger_frame.triger_frame.triger_frame.triger_frame.triger_frame.triger_frame.trigser UltargetRSSI = 80; TrigUserInfoField=5;0;61;1;0;0;0;80 \\ 配置触发器相关用户信息字段\\ HE_Trigger_Frame.basicTriguserinfo.mpdu_mu_sf = MPDU_SPACING_MULT_1; \\ He_trigger_Frame.basicTrigger_Frame.basicTrigger_Frame.basicTrigger_Frame.basicTrigger_Frame.basicTrigger_Frame.basicTrigger_Frame.basicTrigger_Frame.basicTrigger_Frinfo.pref_ac = TB_AC_VO;basicTriguserInfo=0;0;0;0;0 Re: Is this able to OFDMA TF-Files of Rewrite? 你好,@kazus 您在使用我们的 IW611 吗? 您可以参考本节内容编辑配置文件: 13.3 编辑 UM11749中的配置文件。 顺祝商祺! Christine。
查看全文
リンカーはリファレンスマニュアルに書かれているようにVLE関数間のギャップを圧縮しません。 「CodeWarrior Development Studio for Power Architecture ®プロセッサ ビルド ツール リファレンス」には次のように記載されています。 -func_align   実行可能コード内の関数の配置を指定します。   構文 -func_align 4 | 8 | 16 | 32 | 64 | 128   備考 デフォルトの配置は 4 です。ただし、最適化レベル 4 では、アライメントは 16 に変わります。-func_align 4 (またはなし) を使用しており、VLE 用にコンパイルしている場合、リンカーは VLE 関数間のギャップを圧縮します。 • これらの関数がClassic PPC関数によって呼び出されない場合 • 関数のアライメントは 4 より大きい。 注:ギャップの圧縮は、CodeWarrior コンパイラによってコンパイルされたファイルでのみ行われます。 ------------------------ 質問: 1.ここに矛盾はありませんか、それともこれをどのように理解すべきでしょうか? 「-func_align 4 (またはなし) を使用しており、VLE 用にコンパイルしている場合、リンカーは VLE 関数間のギャップを圧縮します。」   「• 関数のアライメントは 4 より大きいです。」 2. 「クラシックPPC機能」とは何ですか? 3. 関数間にまだギャップ「00 00」があるのはなぜですか。VLE コードをコンパイルし、Codewarrior プロジェクト設定の「関数のアライメント」(コード生成 -> EPPC プロセッサ) が「4 バイト」に設定されています (添付ファイルを確認してください)。     Re: Linker does not compress gaps between VLE functions like Reference Manual say FORCEFILES { "module.o"} 何らかの理由で、リンク元に約束を忘れる権利が与えられます。同じ問題が発生する場合は、モジュール名を削除してください。 Re: Linker does not compress gaps between VLE functions like Reference Manual say UPD1: 空のプロジェクトを作成し、サンプル関数を入力しましたが、このプロジェクトでは関数間にギャップは生成されません。私はこれで遊んでいます Re: Linker does not compress gaps between VLE functions like Reference Manual say ...添付ファイル...
查看全文
LX2080 LX2080のセキュアブートモードをハードウェアとソフトウェアで無効にする方法 Re: LX2080 LX2080C A 72232B の場合、 LX2160 のデータシート で「A」の「SEC 無効、SEC セキュアブートを含む」 と確認できます 。セキュアブートが有効になっているかどうかは、どのようにして確認するのですか?   よろしくお願いします。   Re: LX2080 LX2080CA72232B よろしくお願いします。 Re: LX2080 LX2080 の部品番号をお知らせください。 よろしくお願いします。
查看全文
PCAL 6534 Power sequence Is there any power that needs to be turn on first, VDD(P) or VDD(I2C_BUS)? Does it need a power sequence for PCAL6534? Re: PCAL 6534 Power sequence Hi, There is no exact timing sequence specified. If VDD_I2C is powered first in your design, ensure that VDD_P ramps up promptly and reaches the POR threshold before any I²C communication is attempted. Note that the POR reset delay time is approximately 1 µs after VDD_P crosses the threshold. So to ensure reliable operation, allow a short delay (e.g. a few microseconds) after VDD_P is stable before initiating I²C transactions. BRs, Tomas Re: PCAL 6534 Power sequence Is there exact power sequence that contains timing? Actually, VDD_I2C is powered first than VDD_P in design. Re: PCAL 6534 Power sequence Hi, VDD(P) should be powered first or at least not later than VDD(I2C_BUS). This ensures the internal circuits and registers are properly initialized before communication begins. BRs, Tomas
查看全文
How to disable JTAG on IMX95 and reuse JTAG as GPIO HelloI would like to use these GPIOs for JTAG to control other devices, but I found that these GPIOs cannot be controlled with JTAG.How can I disable JTAG and repurpose it as GPIO? Linux Re: How to disable JTAG on IMX95 and reuse JTAG as GPIO Hello, 1. I couldn't find the download link for the manual. Could you please send me the download link? 2. Is there any other way to disable this function besides using fuses? 3. I haven't modified the jtag configuration yet. The/sys/class/gpio pins in the system cannot be controlled because they are reused as jtag by default? Re: How to disable JTAG on IMX95 and reuse JTAG as GPIO Hello, To disable JTAG I suggest you take a look in security reference manual, there is a section where describes the fuse to disable this function in the processor. Once you disabled the JTAG you need to change the IOMUX registers (in device tree for example) to configure JTAG pins as GPIO functions. Best regards.
查看全文
HDMI Interface is not working in I.MX8QM Evaluation Board. Hi, HDMI Interface is not working in I.MX8QM Evaluation Board and all other interfaces are working Previously HDMI interface worked properly, and we are using same previous SD card and Board booting through SD card. Now Issue Showing as "cdns-mhdp-imx 56268000.hdmi: Falling back to sysfs fallback for hdmitxfw.bin". Please help us to resolve this Issue. Re: HDMI Interface is not working in I.MX8QM Evaluation Board. The i.MX8 QM provides an HDMI transmitter capable of supporting an HDMI2.0 compatible output, a Display Port 1.3 compatible output, or an embedded Display Port 1.4 compatible output.  Here which version BSP are you using? Are you using the demo images or the images you build youself?  The firmware file hdmitxfw.bin should be present in /lib/firmware/.   On yur board, run: ls /lib/firmware/hdmitxfw.bin If the file is missing, that’s the root cause.  
查看全文
KW45 based BLE dongle Dear Team, I look over the NXP product lineup and say many MCU have a BLE dongle which best suits some application for Testing and development. I want to know if any such device exists for KW45 MCU? I am in real need for KW45 based dongle. If it does not exist -  1. Do we have any other dongle which I can use to receive data over BLE which I can program the same code made for KW45 MCU ? 2. I know point 1 is difficult, but if we can migrate code from KW45 to other MCU and do this? Example - KW40 can use same code by migrating KW45 code and doing some changes. If 2 is possible, can you provide MCU details and Migration guide if available? BR, Tomaru USB-KW38 USB-KW41Z BLE-NFC KW45B41Z-EVK KW45  Kinetis K Series MCUs Re: KW45 based BLE dongle Hi, @tomaru  Anything else I can do for you on this case? If no other concerns, would you mind to mark my answer as a solution for this case so that we can close this thread? Please feel free to create new case to us if you meet any other issue during using our products. Best regards, Christine. Re: KW45 based BLE dongle Hi, @tomaru  I am so sorry for the inconvenience because we do not have a USB-Dongle based on KW45 BLE chip. 1. Do we have any other dongle which I can use to receive data over BLE which I can program the same code made for KW45 MCU ? ==>Sorry, we do not have. 2. I know point 1 is difficult, but if we can migrate code from KW45 to other MCU and do this? ==>Sorry, I worry it is not possible.  You might think about our other USB-Dongles such as USB-KW38, USB-KW40, USB-KW41. I know it is not convenient for you, but currently, we do not have such kind of dongle for KW45 and also not possible to migrate code from KW45 to other USB-Dongles. Best regards, Christine.
查看全文
TJA1028T/5V0/20/1JとTJA1028T/5V0/20/1の違い こんにちは、 部品番号の違いがわかる人はいますか? TJA1028T/5V0/20/1 Jと TJA1028T/5V0/20/1 ですか? よろしくお願いします。
查看全文
Code Warrior for MCU v10.6 with S08/RS08 microcontrollers Hi, I have installed CodeWarrior Development Studio, CodeWarrior for MCU v10.6, and I'm trying to work with a HCS08 (S08/RS08) microcontroller. During the installation, I was unable to access the Freescale website to download the software package for this microcontroller. After the installation, when I try to install additional software, the problem persists. Please, could anybody send me the installation package for this microcontroller or help me resolve the issue? Re: Code Warrior for MCU v10.6 with S08/RS08 microcontrollers Hi. I found the soltion to my problem. I´ll post it here for anybody's help. You just have to open the available the software sites and change the 'freescale.com' site with 'cache.nxp.com'. In my case: FSL MCU Eclipse Update Site - http://cache.nxp.com/lgfiles/updates/Eclipse/MCU10_6/com.freescale.mcu.updatesite Hope it helps! For me, one day lost...
查看全文
Quectel_SG560D(CPU QCM6490) Android 12 PN7160 移植ガイド Andriod 12用のPN7160移植ガイドはありますか? 弊社のハードウェア プラットフォームは Quectel_SG560D (CPU QCM6490) です。 NFCコントローラーソリューション Re: Quectel_SG560D(cpu QCM6490) Android 12 PN7160 porting guide こんにちは@SunYuxiang 添付ファイルをご確認ください。 ただし、Android 13 から始めることをお勧めします。
查看全文