Skip to content

Conversation

JojoS62
Copy link
Contributor

@JojoS62 JojoS62 commented Feb 7, 2017

Description

A few sentences describing the overall goals of the pull request's commits.
Issue #3711

Status

READY

Migrations

NO

Todos

  • Tests
  • Documentation

Steps to test or reproduce

Outline the steps to test or reproduce the PR here.
mbed compile -t GCC_CR

@sg-
Copy link
Contributor

sg- commented Feb 7, 2017

@JojoS62 What version of LPCXpresso are you using? Is it repackaging GNU ARM Embedded? If so I'd like to get rid of this as an option.

@theotherjimmy
Copy link
Contributor

Would it make more sense to make the LPCXpresso exporter use GCC_ARM and completely remove GCC_CR?

@JojoS62
Copy link
Contributor Author

JojoS62 commented Feb 7, 2017

I'm using the actual 8.2.2 version. The differences between GCC_ARM and GCC_CR that I know are only some different libraries. Also the startup code and the linker script are slightly different. But the tools and compiler flags are the same.
I don't know about the future of LPCXpresso, but NXP is creating a new IDE for LPC and Kinetis MCUs. So I guess for longer term support it is better to move to MCUXpresso when it is available, aren't any NXP people here with some more information?
Now I'm still using LPCXpresso, it was the easiest way to export from the online IDE and import to LPCX for debugging.
@theotherjimmy : as mentionend, what toolchain will MCUXpresso use? I hope it is easier to create exports for this and then drop the GCC_CR. I don't want to spend lots of time in creating a new LPCX exporter and then NXP is dropping this...
Edit:
the LPCX setup includes this toolchain:

c:\nxp\LPCXpresso_8.2.2_650\lpcxpresso\tools\bin>arm-none-eabi-gcc.exe --version
arm-none-eabi-gcc.exe (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release) [ARM/embedded
37715]

@JojoS62
Copy link
Contributor Author

JojoS62 commented Feb 7, 2017

ok, I have tried again to use th eclipse_gcc_arm exporter for LPCX and it works in general. There are few error messages but that can be ignored/fixed. The biggest change is that the makefile is used instead of the settings via dialogs and there is only one launch-configuration, no seperate ones for debug/release. Debugging works too, I've tested first only my 'poor' target LPC824 which is a little too small (8k RAM) for mbed-os, mbed-classic would fit better for this device. I'll keep trying.

@sg-
Copy link
Contributor

sg- commented Feb 13, 2017

Yeah - lets start a process of toolchain support removal for GCC_CR. I started this last year but got interrupted and never completed.

@sg-
Copy link
Contributor

sg- commented Feb 13, 2017

/morph export-build

@mbed-bot
Copy link

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph export-build

@bridadan
Copy link
Contributor

Sorry for all the testing spam, had to restart the machines.

/morph export-build

@mbed-bot
Copy link

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph export-build

Output

mbed Build Number: 129

All exports and builds passed!

@sg- sg- merged commit 69de788 into ARMmbed:master Feb 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants