How do I add a new "toolchain" to Eclipse? [message #1834702] |
Mon, 16 November 2020 09:57  |
Eclipse User |
|
|
|
We use NXP's MCUXpresso on Windows 10 for embedded C++ development (Arm Cortex-M targets). MCUXpresso is Eclipse+CDT+Arm cross-compile+other tools for embedded development and debugging. Works great.
We use host (PC) builds for testing our software (including simulation or mocks for hardware-specific components). Historically we've used a separate IDE (another Eclipse install or Visual Studio).
Because the host builds are of the same software, using the same git repository, we would like to make these host builds part of the MCUXpresso Eclipse workset. If I understand correctly, this requires adding a 'toolchain' to Eclipse to support managed builds. Is there...
a recommended way to do this?
a recommended GCC toolchain for Windows (MinGW? other?)?
Thanks!
Best Regards, Dave
PS: In case you're not clear on why one would do this, you might enjoy this video:
Butterfly Windows simulator
|
|
|
Re: How do I add a new "toolchain" to Eclipse? [message #1834953 is a reply to message #1834702] |
Sat, 21 November 2020 19:00  |
Eclipse User |
|
|
|
Here's the solution:
1) Install your favorite GCC. I used a 32-bit MinGW from http://winlibs.com/
2) In MCUXpresso, create a new C/C++ project, either managed build or un-managed. On next panel, give a name, uncheck "show project types and toolchains only of they are supported on the platform", then select toolchain MinGW.
3) After the project is created, set debug+release properties:
• C/C++ Build, Environment, MINGW_HOME environment variable to c:\MinGW32.
• Launching gdb inside Eclipse will die if there are DLLs required and not on the path.
Either modify the path in the local Eclipse shell (how?), or use linker option -static.
Otherwise on starting gdb Eclipse gives the error:
Failed to execute MI command: -run
Error message from debugger back end:
During startup program exited with code 0xc0000135.
A project created this way can be built and debugged within MCUXpresso.
In my case I also added GUI framework wxWidgets to help with our test frameworks.
Enjoy,
Best Regards, Dave
|
|
|
Powered by
FUDForum. Page generated in 0.03724 seconds