This article has been updated 6/29/2023 for 6th Beta Release:
Your system should now be ready to begin developing with NXP. Please review included Walkthrough OR "Online Documentation" for further assistance.
Please provide feedback on these instructions below.
HI,
I have just installed the Toolchain and try to run a the provided Hello World Programm on a IMXRT1050-EVKB Board. I can compile the programm but when connecting to the Board to Debug the result, I get an GDB Error Message saying that the connection can not be established. Is there anything that I still need to set up in order for the debug process to run ?
If the i.MX RT1050-EVKB board shows up in your Windows (assumed) explorer as a USB device, then the debug settings require a latency setting. This is being added to the extension release next week.
YOu can manually see if this fixes the issue where debug data is not reliable due to GDB server latency/timeouts.
Open the launch.json file for the project.
Paste the following command as shown in the image below:
"setupCommands": [{"text":"set remotetimeout 60000"}],
Note 1: you should also verify that you installed the LInkserver Debug Probe software in the installer. The Linkserver software is used with the probe on the board. HOwever, not having this software installed usually reports an error of missing software.
Note 2: you should also verify that the board has core power. Without the board showing up as a USB storage device indicates it is using J-Link or LPCLink debug firmware. This can require 2 usb cables to provide power to the board if an external power supply is not connected to the barrel connector. The USB cables should connect to the Debug USB port and the USB Device port. Refer to the RT1050-EVK getting started page to verify you have power.
Note 3: You may also verify that it connects with MCUXpresso IDE to eliminate VS Code as the issue.
Please let us know if this helped with your issue.
Hi and thank you for your response. I was able to get the i.MX RT1050-EVKB Board running and am also now able to compile and Debug SW for the Board. I had to select one of the following confiugrations : flexspi_nor_sdram_debug / flexspi_nor_sdram_release
This takes care of the hello world application. May next challenge is to get a EcosPro OS compiled and running on the board. This would require me to include the OS into the build system and also encorperate the ecc file, that configured the ecos itself.
Is this something that you guys have done before or can help me with ?
Regarding my question of using the eCos OS in combination with MCUXPresso. Is there any help that you can offer ? I think I am running into an issue with trying to use a board specific ecos with the board specific configuration in MCUXpresso provided in the hello world examples. For instance when trying to import the compiled ecos librarys I am running into an memory allocation error.
If anyone has some experience in this topic, help would be greatly appreciated. Otherwise I need to contact the ecos guys.
Thank you
Hi @ThBer,
Could you please post this question on MCUXpresso SDK community: https://community.nxp.com/t5/MCUXpresso-SDK/bd-p/mcuxpresso-sdk? Maybe they will be able to help you with the eCos OS issue.
Best regards,
Dragos.
MCUXpresso Installer cannot download correct AArch64(Arm64) packages on MacOS. It will download amd64 or x86_64 package. Maybe it's because that there was no arm64 version before.
Hello @FengChendian,
You are right, MCUXpresso Installer doesn't yet support arm64 packages on macOS. We plan to add arm64 support in a future release, we estimate that it will be available in the last quarter of the year.
Best regards,
Lorena
Is there a vscode development path using WSL ?
Hello @vae,
Could you please help us with more information?
You can send us the log file -> in the top right corner of the menu, please select "open log folder" and send us the files to better understand what is happening on your setup.
Regards,
Lorena Lazar (lorenaionela.lazar@nxp.com)