MCUXpressoリンカファイルおよび外部メモリに使用 皆さん、こんにちは。 私は iMXRT パーツで MCUXpresso を使用しており、アプリケーションには常に RT のパーツの内部 RAM メモリを使用していました。ただし、1 つのプロジェクトで RAM がさらに必要になるため、外部 SDRAM デバイスをアタッチしました。そうは言っても、RT の内部 RAM の使用を維持しながら、外部 SDRAM をアプリケーションで使用できるようにするために、リンカ ファイルにどのような変更を加える必要があるかはわかりません。次に、リンカ ファイルが変更された後、作成された変数が外部 SDRAM に格納されるようにするには、アプリケーション コード内で何をする必要がありますか。歴史的に、私は古いCodeWarriorソフトウェアでプラグマを使用してこれを行っていましたが、MCUExpressoでこれを行う方法がわかりません。そうは言っても、私は上記の最善の方法について、ここの専門家に尋ねようと思いました。 よろしくお願いいたします！ 乾杯 Re:MCUXpressoリンカファイルと外部メモリへの使用 皆さん、こんにちは。 私の元の質問の更新です。MCUXpressoユーザーズガイド-セクション18には、MCUXに変数などをメモリの他の部分に配置するように指示する方法についての優れた説明があります...18.13は私が必要なものを見つけた場所です。 それでは。 Sam 回复: MCUXpresso リンカファイルおよび外部メモリに使用 こんにちはギャビン、 すべてが私の側にうまくいっており、あなたも同じであることを願っています! あなたの投稿とリンクをありがとう!レビューし、さらに質問がある場合は再度投稿します。 改めて感謝します! 乾杯、サム

フラッシュからsja1110を起動する方法は?チュートリアル資料はありますか? 画像ファイルを生成する方法とそれをフラッシュにロードする方法、詳細なチュートリアルはありますか?

Dynamically Record Video Hi, I’m displaying a video from v4l2src in a waylandsink and while I’m doing that I want to dynamically record the video to an mp4. I want to allow a user provided input to determine when to start recording to an mp4 and when to stop the recording. The recording pipeline I’m currently using is: gst-launch-1.0 v4l2src ! vpuenc_h264 ! h264parse ! mp4mux ! filesink location=sample.mp4 -e I tried connecting the recording pipeline to a tee and then deleting it when I’m done recording and I was able to get video to record but that approach causes problems after starting and stopping recording multiple times. Does anyone know a way I can approach this, preferably by just pausing the recording section of the pipeline?   i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: Dynamically Record Video Thanks for the response, I got good results using the appsink approach. Re: Dynamically Record Video Hi @itaigolan, I would implement a gstreamer Tee that sinks in an Appsink. After that, every time a new recording event occurs, I will start a recording pipeline using Appsrc. This would be my best bet. You might alternatively look at Ridgerun Interpipe that can do similar stuff: https://developer.ridgerun.com/wiki/index.php/GstInterpipe_-_GstInterpipe_Overview  Using pause or start/stop does not work well with MP4 because MP4 needs a proper file header that contains all key frame positions of the stream. A more robust file format for this is Mpeg-TS. H.264 elementary stream embeds very well in *.ts files and TS muxer are available in stock Gstreamer. Re: Dynamically Record Video The processor is imx8mp and we are running Mickledore. My question is how do I set up a system where I can dynamically start and stop video recording while constantly displaying the video on a waylandsink. Re: Dynamically Record Video what processor and bsp version do you use？ and what kind of problem do you have? 

MCUXpresso 链接器文件及其用于外部存储器 大家好， 我一直将 MCUXpresso 与我的 iMXRT 部件一起使用，并且始终将 RT 的部件内部 RAM 内存用于我的应用程序。但是，我有一个项目需要更多的 RAM，因此我连接了一个外部 SDRAM 设备。也就是说，我不确定需要对链接器文件进行哪些更改，以允许外部 SDRAM 可用于我的应用程序，同时仍然保持使用 RT 的内部 RAM。其次，一旦链接器文件发生更改，需要在应用程序代码中做什么来确保创建的任何变量都存储在外部 SDRAM 中。以前我曾经使用旧 CodeWarrior 软件的编译指令来执行此操作，但我不确定如何使用 MCUExpresso 来执行此操作。话虽如此，我想向这里的专家请教如何最好地实施上述目标。 提前感谢！ 干杯 回复：MCUXpresso 链接器文件及其用于外部存储器 大家好， 这只是对我的原始问题的更新。MCUXpresso 用户指南第 18 节中对如何指示 MCUX 将变量等放置在内存的其他部分进行了很好的描述...18.13 就是我找到我需要的东西的地方。 干杯， Sam 回复： MCUXpresso 链接器文件和用于外部存储器 你好，加文， 我这边一切都好，希望你也一样！ 感谢您的帖子和链接！我会进行审查，如果有更多问题我会再次发帖。 再次感谢！ 干杯，萨姆

Pre-build steps not executing I have a python script to aggregative GIT info like commit and branch name, in the root directory of my project. I want the script to execute as a pre-build step. I go to Properties -> Settings -> Build Steps ... and enter the command to run the script with the `Release_FLASH` config" cd.. python sample.py However, the python script does not execute. I tried creating a .bat file with the same execution instructions, but still no luck. What am I missing here? Is there a flag I need to set somewhere?  Re: Pre-build steps not executing Hi @Farnam, Thank you for the workaround as well! Best regards, Julián Re: Pre-build steps not executing Hi @Julián_AragónM , Thank you!! This may well have worked, so I'll mark it as the accepted answer. However, I ended up doing the following work-around. Go to Properties → Builders Create a new builder, click "New..." Double click program Name the new builder Enter the location of the script Enter the working directory of the script Under refresh Select "Refresh resources upon completion." Then select "The selected resource" Select "After a "Clean"" (Optional) Select "During manual builds" (Optional) Then click "OK" Now click on the new builder and press the "Up" key until it is at the top of the list Re: Pre-build steps not executing Hi @Farnam, If the file (.py or .bat) is not included inside the project and by project properties, try with the whole path to the file so it can be recognized, as such: python "C:\User\user\Downloads\hello_world.py" I did a simple test with a hello world and it printed before finishing building: If this still does not work, try to add cmd.exe in front of your command line, so it launches the windows shell/command prompt. Best regards, Julián

ビルド前のステップが実行されない 私は、プロジェクトのルートディレクトリにコミットやブランチ名などのGIT情報を集約するPythonスクリプトを持っています。 スクリプトをビルド前のステップとして実行したいと思います。 [プロパティ] - > 設定 - > ビルド ステップ] に移動します。そして、コマンドを入力して、「Release_FLASH」構成でスクリプトを実行します。 Pythonの sample.py ただし、Pythonスクリプトは実行されません。 .batを作成してみました同じ実行命令でファイルを作成しますが、それでも運が悪いです。 ここで何が足りないのでしょうか?どこかにフラグを設定する必要がありますか?

预构建步骤未执行 我有一个 python 脚本，用于在项目的根目录中聚合 GIT 信息，例如提交和分支名称。 我希望脚本作为预构建步骤执行。 我转到“属性”->“设置”->“构建步骤...”，然后输入使用“Release_FLASH”配置运行脚本的命令” cd..python 示例.py 但是，python脚本没有执行。 我尝试创建一个 .bat文件具有相同的执行指令，但仍然没有运气。 我在这里遗漏了什么？我需要在某处设置标志吗？

Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi Team, We are using the NXP S32K388EVB-Q289 evaluation board. We have configured the CLOCK_RUN frequency to be 20 MHz and it is sourced by PLL PHI0 (which is 160MHz). All the peripheral clocks are enabled in the MCU driver and the MCU is set to RUN mode. We have configured the GPIO Pin PTD14's GPIO mode as SYSTEM_CLKOUT_RUN_OUT. The expectation is to see the clock frequency on the GPIO PTD14 to be 20 MHz while measuring through any of the logic analyzer. However, when we measured using Saleae logic analyzer (connected to available GPIO mux pad on the Eval board), the GPIO value is always 0. Noise is observed in the analog channel.  But the clock frequency value read from the API Mcu_GetClockFrequency(CLKOUT_RUN_CLK) is returning the value as expected 20 MHz. We also checked the MCU MUX 6 and the GPIO110 register and looks like the values are expected ones. Could you please check and let us know what could be the reason for the observed issue? #S32K388 #S32K3 #CLKOUT_RUN #GPIO Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi Peter, We could identify the connection where the PTD14 is routed and we could measure the configured frequency value from this pin.   Thank you for the support. Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi, Do you mean that the pins PTD14, PTD10 & PTB5 (which can be configured as the CLKOUT_RUN) are not connected to IO matrix by default? We have this document S32K388EVB-Q289_EVB_HWPack_RevA0_Schematic 1 with us. We could see the pin PTD14 is connected to the Ardunio header J702 pin 11. But again we didn't see the frequency value on this pin as well. Could you please let us know how can we identify if the pin is connected to the IO matrix or headers and also the location on the EVB where we can measure this signal as we don't have the layout information with us? Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi, please note no pins mentioned are connected by default to Arduino headers or IOmatrix. Those go to SABRE connector or QSPI memory. So please check board schematic to find right place to measure signal. BR, Petr Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi Peter, I am attaching the example what we are using. The RTD package we are using is SW32K3_S32M27x_RTD_4.4_4.0.0_P20. Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi, let me check with a board. BTW what kind of driver is used, or can you share simplified example you have? BR, Petr Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi Peter, We checked all the below possibilities. 1. Confirmed the connected pin for measurement is PTD14. 2. Analyzer was set to highest available sample rate and also tried with the scope. In both cases, the result is same. 3. Tried with lower CLKOUT_RUN frequency and enabling the drive strength as well, still the same result. 4. Tried with both PTB5 & PTD14 which can be configured as CLKOUT_RUN and the result is same in all the pins. Couldn't test PTD10 since there is no GPIO tap out available to test it. Note: PTD14 & PTB5 - GPIO Standard Plus (Switching up to 50 MHz and the CLKOUT_RUN is configured as 20MHz), PTD10 - GPIO Fast (Switching up to 120 MHz). Also as per the requirement, we have used PTD14 as the CLKOUT_RUN mode. We have an LED blinking code and it is working as per the timings we have configured it to toggle. Basically what I have observed till now is, the expected clock frequency is generated but the same is not reflecting in the PTD14 pin whose GPIO mode is configured as CLKOUT_RUN. Is there any other configuration which should be done other the above configurations? Can you please try to simulate and verify on S32K388 EVB just to make sure it is not the issue of the EVB? This is the blocker point for us right now. Regards, Punith Chandra. Re: Expected CLKOUT_RUN frequency not observed in the mapped GPIO Hi, register setting for selecting CLKOUT looks fine. I can recommend to try/check below - be sure you are on right pin on EVB - be sure analyzer is using fast sample rate, or use scope - use even higher divider to have lower freq on CLKOUT - set drive strength for PTD14 - you can try different pins, ideally fast type BR, Petr

gpio-sim as a GPIO Interrupt for PMIC driver Hi everyone, I'm currently working on getting a custom i.MX93 board up and running, and I'm facing an issue with the PMIC (the NXP PCA9451A). The problem is that the PMIC requires a GPIO interrupt to load its driver, but our board does not have any free GPIOs available. To solve this, we came up with the idea of using a "fake" GPIO through gpio-sim or gpio-mockup, so that we can get the PMIC up and running for now. In a future revision of the board, we plan to replace this mockup GPIO with a real one. However, I'm struggling to get the PMIC driver to load, regardless of how I configure the gpio-sim node. I've seen a linux patch from 2022 "[PATCH v2 0/3] allow gpio simulator be used as interrupt controller ", which seems to be attempting the same thing I'm trying to do. We're currently using Linux version 6.6.28-lf-6.6.y-lf-6.6.y-g81ea508ca4b7-dirty. I've also made sure to add the necessary kernel configuration options, including: CONFIG_GPIO_SIM=y CONFIG_GPIOLIB=y CONFIG_IRQ_SIM=y Despite this, the PMIC driver does not load. Below is how I'd like the PMIC node to look in the device tree, using gpio-sim as the interrupt parent: &lpi2c1 { #address-cells = <1>; #size-cells = <0>; clock-frequency = <400000>; pinctrl-names = "default", "sleep"; pinctrl-0 = <&pinctrl_lpi2c1>; pinctrl-1 = <&pinctrl_lpi2c1>; status = "okay"; pmic@25 { compatible = "nxp,pca9451a"; reg = <0x25>; interrupt-parent = <&gpio_sim>; interrupts = <0 IRQ_TYPE_EDGE_FALLING>; Has anyone successfully used gpio-sim in a similar scenario, or can anyone suggest how the gpio-sim node should be configured to make this work? Any help would be greatly appreciated! Best regards, Elia   Re: gpio-sim as a GPIO Interrupt for PMIC driver To anyone having the same question I got it to work: / { gpio_sim { compatible = "gpio-simulator"; bank0: bank0 { gpio-controller; #gpio-cells = <1>; ngpios = <1>; interrupt-controller; #interrupt-cells = <1>; }; }; };

There was an error during the import process of the S32K396 PWM example routine into EB I am getting an error message when attempting to import the S32K396 PWM example into EB. Could you please assist me in troubleshooting this issue? Re: There was an error during the import process of the S32K396 PWM example routine into EB Hi@qingwang_a This is a problem with your RTD version. For the new version, please read the “readme.text” in the DEMO project. You need to make some modifications. Re: There was an error during the import process of the S32K396 PWM example routine into EB I have already installed the latest eTPU library, but the installed version is ETPU_TS_T40D34M10I0R0, and the so-called ETPU_TS_T40D34M40I0R0 does not exist. I'm not sure if this is a bug in the ETPU library. @Senlent  Re: There was an error during the import process of the S32K396 PWM example routine into EB Hi@qingwang_a According to the error message, you need to install the eTPU library You can find eTPU library in the path below. https://nxp.flexnetoperations.com/control/frse/product?plneID=830607

如何测试MIFARE Ultralight的VCSL命令？ 我在测试 MIFARE Ultralight 的 VCSL 命令时遇到了一些问题。如何在 VCSL 命令中填写 IID 和 PCDCAPS 的值？我尝试多次测试VCSL命令并收到卡返回的NAK。 有人能帮我吗？ 回复：如何测试MIFARE Ultralight的VCSL命令？ 谢谢你的回答。我现在可以测试它。谢谢你！

How to test the VCSL command of MIFARE Ultralight? I encountered some problems while testing the VCSL command for MIFARE Ultralight.How do I fill in the values of IID and PCDCAPS in the VCSL command? I tried to test the VCSL command several times and received the NAK returned by the card. Can someone help me? Re: How to test the VCSL command of MIFARE Ultralight? Thank you for your answer. I can test it now. Thank you! Re: How to test the VCSL command of MIFARE Ultralight? Hello @wangj1201  The below log for your reference.

MIFARE UltralightのVCSLコマンドをテストする方法は? MIFARE Ultralight の VCSL コマンドのテスト中に問題が発生しました。VCSL コマンドの IID および PCDCAPS の値はどのように入力すればよいですか。VCSLコマンドを何度かテストしようとしましたが、カードからNAKが返されました。 どなたか助けてもらえますか? Re:MIFARE UltralightのVCSLコマンドをテストする方法は? ご回答ありがとうございます。今ならテストできます。ありがとうございます！

MFRC630 Write FIFO Error Hi, We have designed a circuit with the MFRC63003HN component to detect NFC cards. In some circuits it works perfectly. However, in other circuits I am unable to perform detection. I have been able to verify that an error appears in the IRQ0 register. Reading 0Ah register, I could see that It is "NoDataErr" error. Testing I have been able to see how, after writing in the FIFO, there is no information in the FIFO. That is, after sending a "mfrc630_write_fifo(data, len)" command, if I read the length of the FIFO ("mfrc630_fifo_length()"), it returns 0. As I say, this happens only in some circuits. The only solution I have currently found is to change the MFRC603 component with another of the same model. Is it possible that the component was damaged in the assembly and soldering process? Best regards. Thank you. Re: MFRC630 Write FIFO Error Hello @Carlos_APERTON Hope you are doing well. Could you please confirm that you have read the instructions from the following guides to design your antenna? CLRC663 Antenna Design Guide; this document describes NFC and RFID antenna design rules, different requirements and antenna design for CLRC663 in detail to get an optimum performance. Measurement and tuning of a NFC and Reader IC antenna with a MiniVNA; this Application Note gives a guideline on how to measure and tune/match an NFC and Reader IC antenna with a MiniVNA network analyzer. Additionally, please refer to the NFC Antenna Design training, an online training series that could help you with key aspects for the antenna, optimizing and debugging, and testing to get the best-matched antenna for your product, in addition to the NFC Antenna Tool. Also, please consider using the NFC Reader Library, which is a complete software support library for NFC Frontend ICs designed to provide a faster and simpler way to develop your project. This library also provides an API that facilitates the most common operations required in NFC applications such as reading or writing data. Regards, Eduardo.

使用 LinkServer/CMSIS-DAP 在 MIMXRT1060-EVKB 上调试大于 128 KB 的程序 我正在使用 MCUXpresso 进行 VSCode 并尝试在 MIMXRT1060-EVKB 板上调试应用程序。 一切运行正常，直到我的程序大小似乎超过了 128 KB 的大小标记。 我已将链接器映射设置为使用 0x00000000 处的整个 512 KB 作为 ITCM，因此它应该适合。 但是，我收到一个错误消息对话框，其中显示： 无法开始调试。命令“-interpreter-exec console“load””的 GDB 输出意外。加载失败 在深入研究调试控制台日志之后，我看到了以下内容： [Warning] 1: (6334) STDERR: Wc: ============= SCRIPT: RT1060_connect.scp ============= [Warning] 1: (6334) STDERR: Wc: RT1060 Connect Script [Warning] 1: (6334) STDERR: Wc: DpID = 0BD11477 [Warning] 1: (6334) STDERR: Wc: APID = 0x04770041 [Warning] 1: (6334) STDERR: Wc: Disabling MPU [Warning] 1: (6334) STDERR: Wc: Configure FlexRAM for 768KB OC RAM, 128KB I-TCM, 128KB D-TCM [Warning] 1: (6334) STDERR: Wc: Finished [Warning] 1: (6334) STDERR: Wc: ============= END SCRIPT ============================= LinkServer 文件夹中的这个 RT1060_connect.scp 脚本似乎明确配置了 ITCM 上 RAM 的 128 KB 限制。 脚本本身的这一部分如下所示： 360 REM ====== Configure FlexRAM ====== 370 print "Configure FlexRAM for 768KB OC RAM, 128KB I-TCM, 128KB D-TCM" 380 REM TCM CTRL Poke 0x400B0000 - to force RAM clocking and set wait states = b100 390 Poke32 this 0x400B0000 0x4 400 REM IOMUXC_GPR17 0x400AC044 - this sets bitfield allocation of FlexRAM 32KB banks to OC 256KB b01, I 128KB b11, D 128KB b10 410 Poke32 this 0x400AC044 0x5555FFAA 420 REM IOMUXC_GPR16 0x400AC040 - this sets enables for I and DTCM and the source of the TCM config = 0x200007 430 Poke32 this 0x400AC040 0x200007 440 print "Finished" 450 REM =============================== 在哪里可以找到有关如何覆盖/定制此 FlexRAM 设置以匹配我的链接器文件内容（或其他配置）的信息？   提前感谢！ 回复： 使用 LinkServer/CMSIS-DAP 在 MIMXRT1060-EVKB 上调试大于 128 KB 的程序 我确认此方法在 VSCode 中有效。 谢谢@Gavin_Jia ！

ISELED - ボード回路図 こんにちは、皆さん、こんにちは!! ISELEDボード回路図を探していますが、それやBOMを取得するチャンスはありますか? ありがとうございました。

ISELED - Board Schematic Hello Guys, good day!! I'm looking for the ISELED Board Schematic, is it any chance to get it or the BOM? Thanks!! Re: ISELED - Board Schematic Hi Do you mean the ISELED power adaptor board and 16-LED bar?  According to the information on this webpage ADK - Application & Development Kit, the MANUFACTURER is Inova&Various, and I can only find this block diagram. If you need schematic diagram, I'm afraid you have to consult INOVA SEMICONDUCTORS. Inova ISELED ADK User Manual Best Regards, Robin ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------

LinkServer/CMSIS-DAP を使用した MIMXRT1060-EVKB 上の 128 KB を超えるプログラムのデバッグ VSCodeにMCUXpressoを使用しており、MIMXRT1060-EVKBボード上のアプリケーションをデバッグしようとしています。 私のプログラムサイズが128 KBのサイズマークを超えているように見えるまで、すべてが正常に機能します。 リンカマップは、0x00000000で512 KB全体をITCMとして使用するように設定されているので、収まるはずです。 ただし、次のようなエラーメッセージダイアログウィンドウが表示されます。 デバッグを開始できません。コマンド "-interpreter-exec console "load"" からの予期しない GDB 出力。ロードに失敗しました デバッグコンソールのログを少し掘り下げると、次のように表示されます。 [Warning] 1: (6334) STDERR: Wc: ============= SCRIPT: RT1060_connect.scp ============= [Warning] 1: (6334) STDERR: Wc: RT1060 Connect Script [Warning] 1: (6334) STDERR: Wc: DpID = 0BD11477 [Warning] 1: (6334) STDERR: Wc: APID = 0x04770041 [Warning] 1: (6334) STDERR: Wc: Disabling MPU [Warning] 1: (6334) STDERR: Wc: Configure FlexRAM for 768KB OC RAM, 128KB I-TCM, 128KB D-TCM [Warning] 1: (6334) STDERR: Wc: Finished [Warning] 1: (6334) STDERR: Wc: ============= END SCRIPT ============================= LinkServer フォルダにあるこの RT1060_connect.scp スクリプトは、ITCM に 128 KB の制限を設けて RAM を明示的に構成しているようです。 スクリプト自体のこの部分は、次のようになります。 360 REM ====== Configure FlexRAM ====== 370 print "Configure FlexRAM for 768KB OC RAM, 128KB I-TCM, 128KB D-TCM" 380 REM TCM CTRL Poke 0x400B0000 - to force RAM clocking and set wait states = b100 390 Poke32 this 0x400B0000 0x4 400 REM IOMUXC_GPR17 0x400AC044 - this sets bitfield allocation of FlexRAM 32KB banks to OC 256KB b01, I 128KB b11, D 128KB b10 410 Poke32 this 0x400AC044 0x5555FFAA 420 REM IOMUXC_GPR16 0x400AC040 - this sets enables for I and DTCM and the source of the TCM config = 0x200007 430 Poke32 this 0x400AC040 0x200007 440 print "Finished" 450 REM =============================== この FlexRAM 設定をオーバーライド/カスタマイズして、リンカー ファイルの内容 (またはその他の構成) と一致させる方法に関する情報はどこで入手できますか。   よろしくお願いいたします！ 回复: LinkServer/CMSIS-DAP を使用した MIMXRT1060-EVKB 上の 128 KB を超えるプログラムのデバッグ この方法がVSCodeで動作することを確認します。 ありがとうございました@Gavin_Jia

ISELED - 电路板示意图 大家好，祝您有美好的一天！ 我正在寻找 ISELED 板原理图，有机会获得它或 BOM 吗？ 谢谢！！

mpc5744 facing a memmove function bug Hi NXP experts, Recently we are using mpc5744 with S32 Design Studio for Power Architecture Version 2017.R1 to compile the project. Now we are facing a memmove function problem. The project in the attachment is modified based on "hello world" and can reproduce the issue we encountered. We defined a 40-byte array of type U8 as the data source, used 0x4001268e as the data destination, called the memmove function to copy data, but found that the last 6 bytes of the destination data were not copied correctly. Upon analyzing the standard C code, we discovered that the issue might be related to the macro replacement of deref_auto_inc in __copy_long_mem.c. The memmove.o included in libc99.a should have enabled #define deref_auto_inc(p) *++(p), but it was incorrectly enabled as #define deref_auto_inc(p) *(p)++. We want to confirm if this issue is caused by a bug in the default lib library provided by s32DS or an default method we have usd. Thanks! Re: mpc5744 facing a memmove function bug Hi,  right click on project name -> Properties -> C/C++ Build -> Settings: Re: mpc5744 facing a memmove function bug Hi, Can you tell me how can I switch STD C library from EWL C to NewLIB in project properties? Can you show me the process? Maybe some screenshots can be showed. Re: mpc5744 facing a memmove function bug Hi,  I can reproduce the issue and can confirm that it is a bug in EWL C standard C library. Thanks for report!  Unfortunately S32DS for PA v2017.R1 is no more maintained and the bug will not be fixed for this S32DS version.  This bug is already fixed in S32DS for PA v2.1 and you can use this S32DS version.   If you need to use S32DS PA v2017 - you have couple options. You can Switch STD C library from EWL C to NewLIB in project properties.  Other possibility is use memcpy instead of memmove, memcpy works as expected.   Re: mpc5744 facing a memmove function bug Hi,  I'm looking at you project right now, I'll be back later today with more info.  Re: mpc5744 facing a memmove function bug Can someone test this project? We would like to know if the issue is due to our incorrect usage or if memmove function itself has a bug in S32DS? We are eagerly awaiting your response. Re: mpc5744 facing a memmove function bug Can someone reply my problem?  It's really urgent. Re: mpc5744 facing a memmove function bug We also found in the map file that the memmove function is not compiled from the C source code but rather uses library functions from libc99.a. This means that we cannot solve this problem by modifying the C source code, is that correct? How should we go about resolving this issue then? We are in urgent need of your help. Thanks!!!  Re: mpc5744 facing a memmove function bug Project is attached, the problem is very urgent, please reply soon.