[exporter] LPCXpresso exporter broken #2448

toyowata · 2016-08-15T11:51:56Z

Exported project for LPCXpresso broken from mbed library Rev.122 and onward.

Step to reproduce:

Create blinky project for LPC1768 (or other LPC) target
Set mbed library Rev. 122 or 123
Export to LPCXpresso
Open the project by LPCXpresso IDE (I used LPCXpresso v8.1.4)
Build the project file

Building target: mbed_blinky.axf
Invoking: MCU C++ Linker
arm-none-eabi-c++ -nostdlib -L"/Users/toyowata/Documents/LPCXpresso_8.1.4/workspace/mbed_blinky" -L"/Users/toyowata/Documents/LPCXpresso_8.1.4/workspace/mbed_blinky/mbed" -L"/Users/toyowata/Documents/LPCXpresso_8.1.4/workspace/mbed_blinky/mbed/TARGET_LPC1768" -L"/Users/toyowata/Documents/LPCXpresso_8.1.4/workspace/mbed_blinky/mbed/TARGET_LPC1768/TARGET_NXP" -L"/Users/toyowata/Documents/LPCXpresso_8.1.4/workspace/mbed_blinky/mbed/TARGET_LPC1768/TARGET_NXP/TARGET_LPC176X" -L"/Users/toyowata/Documents/LPCXpresso_8.1.4/workspace/mbed_blinky/mbed/TARGET_LPC1768/TARGET_NXP/TARGET_LPC176X/TARGET_MBED_LPC1768" -Xlinker -Map="mbed_blinky.map" -Xlinker --gc-sections -mcpu=cortex-m3 -mthumb -T "" -o "mbed_blinky.axf"  ./main.o   
/Applications/lpcxpresso_8.1.4_606/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/5.2.1/../../../../arm-none-eabi/bin/ld: read in flex scanner failed
collect2: error: ld returned 1 exit status
make: *** [mbed_blinky.axf] Error 1

When I use Rev. 121 mbed library, it worked fine (I could build a project by LPCXpresso). The exporter doesn't seem to generate pre-build object files for target. See below:

mbed library Rev.122 and onward

mbed library Rev.121 and upward

I also tried to export other target such as LPC1114FN28 anr LPCXpresso11U68, they are same result.

The text was updated successfully, but these errors were encountered:

0xc0170 · 2016-08-15T15:26:15Z

Can you test the latest master here with project.py to find out if its a problem of scripts here in this code base or in the online IDE?

toyowata · 2016-08-19T05:59:55Z

@0xc0170

tools\project.py -m LPC1768 -i lpcxpresso -p 0 generates correct project file for the LPCXpresso IDE. I got link errors, and fixed by other PR (see later - Other issues).

tools\project.py -m LPC1768 -i lpcxpresso -p 0 -b it seems generate incorrect files in the project zip. I got compile errors below:

make -r all 
Building file: ../zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -D__NEWLIB__ -D__CODE_RED -DCPP_USE_HEAP -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\env" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\rtos" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\rtos\rtos" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\rtos\rtx" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\rtos\rtx\TARGET_CORTEX_M" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\rtos\rtx\TARGET_CORTEX_M\TARGET_M3" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\emblocks\LPC1768\temp\rtos\rtx\TARGET_CORTEX_M\TARGET_M3\TOOLCHAIN_GCC" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\env" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\api" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\common" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\hal" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\hal\storage_abstraction" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\cmsis" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\cmsis\TARGET_NXP" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\cmsis\TARGET_NXP\TARGET_LPC176X" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\cmsis\TARGET_NXP\TARGET_LPC176X\TOOLCHAIN_GCC_CR" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\hal" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\hal\TARGET_NXP" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\hal\TARGET_NXP\TARGET_LPC176X" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\hal\targets\hal\TARGET_NXP\TARGET_LPC176X\TARGET_MBED_LPC1768" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\mbed" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\mbed\TARGET_LPC1768" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\mbed\TARGET_LPC1768\TARGET_NXP" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\mbed\TARGET_LPC1768\TARGET_NXP\TARGET_LPC176X" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\mbed\TARGET_LPC1768\TARGET_NXP\TARGET_LPC176X\TARGET_MBED_LPC1768" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\mbed\TARGET_LPC1768\TOOLCHAIN_GCC_CR" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp\env" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp\rtos" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp\rtos\rtos" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp\rtos\rtx" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp\rtos\rtx\TARGET_CORTEX_M" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1\zip\LPC1768\temp\rtos\rtx\TARGET_CORTEX_M\TARGET_M3" -I"C:\Users\toywat01\Documents\LPCXpresso_8.0.0_526\workspace\MBED_A1" -O0 -g3 -Wall -c -std=gnu99 -DTARGET_MBED_LPC1768 -DDEVICE_ERROR_PATTERN=1 -D__MBED__=1 -DDEVICE_I2CSLAVE=1 -DTARGET_LIKE_MBED -DTARGET_NXP -DTARGET_LPC176X -DDEVICE_PORTIN=1 -DDEVICE_RTC=1 -DTOOLCHAIN_object -D__CMSIS_RTOS -DMBED_BUILD_TIMESTAMP=1471585027.01 -DTOOLCHAIN_GCC -DDEVICE_CAN=1 -DTARGET_LIKE_CORTEX_M3 -DTARGET_CORTEX_M -DARM_MATH_CM3 -DDEVICE_ANALOGOUT=1 -DTARGET_UVISOR_UNSUPPORTED -DTARGET_M3 -DDEVICE_PWMOUT=1 -DDEVICE_INTERRUPTIN=1 -DDEVICE_I2C=1 -DDEVICE_PORTOUT=1 -D__CORTEX_M3 -DDEVICE_STDIO_MESSAGES=1 -DTARGET_LPC1768 -DTOOLCHAIN_GCC_CR -DDEVICE_PORTINOUT=1 -DDEVICE_SERIAL_FC=1 -DTARGET_RELEASE -D__MBED_CMSIS_RTOS_CM -DDEVICE_SLEEP=1 -DDEVICE_SPI=1 -DDEVICE_ETHERNET=1 -DDEVICE_SPISLAVE=1 -DDEVICE_ANALOGIN=1 -DDEVICE_SERIAL=1 -DDEVICE_SEMIHOST=1 -DDEVICE_DEBUG_AWARENESS=1 -DDEVICE_LOCALFILESYSTEM=1 -include mbed_config.h -c -Wall -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -fmessage-length=0 -fno-exceptions -fno-builtin -ffunction-sections -fdata-sections -funsigned-char -MMD -fno-delete-null-pointer-checks -fomit-frame-pointer -mcpu=cortex-m3 -mthumb -Os -mcpu=cortex-m3 -mthumb -D__NEWLIB__ -MMD -MP -MF"zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.d" -MT"zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.o" -MT"zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.d" -o "zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.o" "../zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.c"
../zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.c:50:7: error: expected '(' before 'void'
 __asm void rt_set_PSP (U32 stack) {
       ^
../zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.c:72:20: error: stray '#' in program
         LSLS    R0,#31
                    ^
../zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.c:73:20: error: stray '#' in program
         MOVNE   R0,#0x02                ; Privileged Thread mode, use PSP
                    ^
(snip)

../zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.c:229:20: error: stray '#' in program
         MVN     LR,#:NOT:0xFFFFFFFD     ; set EXC_RETURN value
                    ^
make: *** [zip/LPC1768/temp/rtos/rtx/TARGET_CORTEX_M/TARGET_M3/TOOLCHAIN_ARM/HAL_CM3.o] Error 1

It wrongly uses the TOOLCHAIN_ARM rather than TOOLCHAIN_GCC_CR

Other issue

During this test, I got multiple definition errors in the build, but this fixes the issue. #2498

I still got errors by automated test by singletest.py below:

Test summary:
+---------+---------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| Result  | Target  | Toolchain | Test ID     | Test Description                      | Elapsed Time (sec) | Timeout (sec) | Loops |
+---------+---------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
| TIMEOUT | LPC1768 | GCC_CR    | DTCT_1      | Simple detect test                    |       20.07        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | EXAMPLE_1   | /dev/null                             |       20.07        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_10     | Hello World                           |       20.07        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_11     | Ticker Int                            |       40.33        |       20      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_12     | C++                                   |       20.08        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_16     | RTC                                   |       30.25        |       15      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_2      | stdio                                 |       40.34        |       20      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_22     | Semihost                              |       20.14        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_23     | Ticker Int us                         |       30.25        |       15      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_24     | Timeout Int us                        |       30.25        |       15      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_25     | Time us                               |       30.23        |       15      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_26     | Integer constant division             |       20.08        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_34     | Ticker Two callbacks                  |       30.22        |       15      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_37     | Serial NC RX                          |        20.1        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_38     | Serial NC TX                          |       20.12        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_A1     | Basic                                 |       20.07        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_A18    | Interrupt vector relocation           |       20.09        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_A2     | Semihost file system                  |       20.12        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_A21    | Call function before main (mbed_main) |       20.13        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_A9     | Serial Echo at 115200                 |       20.09        |       10      |  0/1  |
| TIMEOUT | LPC1768 | GCC_CR    | MBED_BUSOUT | BusOut                                |       30.21        |       15      |  0/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_1      | Basic thread                          |       12.69        |       15      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_2      | Mutex resource lock                   |       12.84        |       20      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_3      | Semaphore resource lock               |        9.81        |       20      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_4      | Signals messaging                     |        7.78        |       20      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_5      | Queue messaging                       |        3.7         |       20      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_6      | Mail messaging                        |        3.71        |       20      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_7      | Timer                                 |       12.62        |       15      |  1/1  |
| OK      | LPC1768 | GCC_CR    | RTOS_8      | ISR (Queue)                           |        7.81        |       20      |  1/1  |
+---------+---------+-----------+-------------+---------------------------------------+--------------------+---------------+-------+
Result: 8 OK / 21 TIMEOUT

Completed in 732.83 sec

It failed all non-RTOS test cases. This is because the software_init_hook is always enabled even if non-RTOS build here.
https://github.com/ARMmbed/mbed-os/blob/master/hal/targets/cmsis/TARGET_NXP/TARGET_LPC176X/TOOLCHAIN_GCC_CR/startup_LPC17xx.cpp#L154
I will find out this issue.

ciarmcom · 2016-08-25T23:51:04Z

ARM Internal Ref: IOTMORF-439

toyowata · 2016-08-30T07:05:58Z

I have created other ticket for automated test fail issue here : #2581

sg- · 2016-09-19T16:17:36Z

@toyowata Is this resolved with the latest exporter updates?

toyowata · 2016-09-20T00:23:24Z

@sg- Actually, it is getting worse. I got an error dialog below when I exported to the LPCXpresso.

Step to reproduce

Create new blinky program for NXP LPC target such as LPC1768
Export the project to LPCXpresso

theotherjimmy · 2016-09-20T14:56:28Z

reproduced. I have the error message at hand. Could you try exporting from the command line tools?

that is:

mbed import mbed-os-blinky
mbed export -i lpcxpresso -m lpc1768

then import the project into lpcxpresso

This would help, as the error you are seeing is only related to how the online export system works. If that's the only issue, then exporting from the command line should work.

toyowata · 2016-09-21T04:56:10Z

@theotherjimmy

The mbed export command generates LPCXpresso project without error. However, I got following error when I build the project by LPCXpresso IDE.

**** Build of configuration Debug for project Unnamed_Project ****

Nothing to build for project Unnamed_Project

The project windows doesn't seem to have source code and libraries.

JojoS62 · 2016-09-21T12:50:35Z

I've tried also the mbed-cli with the blinky example. The export stops after scanning FEATURE_STORAGE and the exported project file is not generated.

D:\Projects\Sn\ARM\LPCXpresso1769\mbed-os-example-blinky>pip install mbed-cli --upgrade
Requirement already up-to-date: mbed-cli in c:\python27\lib\site-packages\mbed_cli-0.9.5-py2.7.egg

D:\Projects\Sn\ARM\LPCXpresso1769\mbed-os-example-blinky>mbed export -i lpcxpresso -m lpc1768 -vv
[mbed] Working path "D:\Projects\Sn\ARM\LPCXpresso1769\mbed-os-example-blinky" (program)
[mbed] Exec "python -u D:\Projects\Sn\ARM\LPCXpresso1769\mbed-os-example-blinky\mbed-os\tools\project.py -i lpcxpresso -
m lpc1768 --source ." in D:\Projects\Sn\ARM\LPCXpresso1769\mbed-os-example-blinky
Build Options: debug-info
Scan: .
Scan: FEATURE_BLE
Scan: FEATURE_CLIENT
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_UVISOR
Scan: FEATURE_IPV4
Scan: FEATURE_IPV6
Scan: FEATURE_STORAGE

D:\Projects\Sn\ARM\LPCXpresso1769\mbed-os-example-blinky>

I can compile the the project with GCC_ARM. With GCC_CR, the .bin is created also but there is an error when the size should be prompted:
Link: mbed-os-example-blinky Elf2Bin: mbed-os-example-blinky Unknown toolchain for memory statistics GCC_CR Image: .\.build\lpc1768\gcc_cr\mbed-os-example-blinky.bin

JojoS62 · 2016-09-21T14:17:37Z

Update: I was looking for an archive file in .build, but a .project and .cproject for the eclipse ide is built in the root of my blinky-example project. These files look ok, but when I import from the root of my project, the import pulls in all the unwanted stuff like the complete mbed-os dir with all tools etc.
Uploading mbed-os-example-blinky.zip…

theotherjimmy · 2016-09-21T16:48:31Z

@toyowata what version of mbed-os are you using?

@JojoS62 Comment 1: That error is likely related to memap.py, could you open a new issue for that link error so that we can track it separately?

@JojoS62 Comment 2: The .project and .cproject file in the root is expected; zip files are only created for mbed 2 tests. The source of mbed-os (*.c, *.cpp) should be pulled in to the project, but the tools should not be in the project workspace. Further, I can't seem to download the zip file you posted.

toyowata · 2016-09-23T14:07:14Z

@theotherjimmy I used mbed-os-5.1.4 for this test and rev.126 for this.

I also found some reports from community questions below:
https://developer.mbed.org/questions/74489/Exprt-error-LPCxpresso/
https://developer.mbed.org/questions/74741/Exporting-EA-LPC11U35-Quickstart-board-t/

Carl-M · 2016-10-03T18:38:48Z

I have this issue too, started new mbed project, choose blinky and export from online compiler. Import into lpcxpresso v8.2.2 [Build 650] and get the same -t error.
If I switch to revision 121 and repeat it builds fine in LPCxpresso

theotherjimmy · 2016-10-03T18:49:12Z

@Carl-M I'm sorry, but I don't know what you are talking about when you refer to the "-t error"

Carl-M · 2016-10-03T18:52:50Z

Sorry this is the error
arm-none-eabi-c++ -nostdlib -L"\LPCXpresso_8.2.2_650\workspace\mbed_blinky" -L"\LPCXpresso_8.2.2_650\workspace\mbed_blinky\mbed" -L"\LPCXpresso_8.2.2_650\workspace\mbed_blinky\mbed\TARGET_LPC1768" -L"\LPCXpresso_8.2.2_650\workspace\mbed_blinky\mbed\TARGET_LPC1768\TARGET_NXP" -L"\LPCXpresso_8.2.2_650\workspace\mbed_blinky\mbed\TARGET_LPC1768\TARGET_NXP\TARGET_LPC176X" -L"\LPCXpresso_8.2.2_650\workspace\mbed_blinky\mbed\TARGET_LPC1768\TARGET_NXP\TARGET_LPC176X\TARGET_MBED_LPC1768" -Xlinker -Map="mbed_blinky.map" -Xlinker --gc-sections -mcpu=cortex-m3 -mthumb -T "" -o "mbed_blinky.axf" ./main.o e:/dev/nxp/lpcxpresso_8.2.2_650/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: unrecognized option '-T' e:/dev/nxp/lpcxpresso_8.2.2_650/lpcxpresso/tools/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: use the --help option for usage information

theotherjimmy · 2016-10-03T18:53:55Z

You don't have a linker script. It should be between the "s after the -T

theotherjimmy · 2016-10-03T18:54:07Z

What target did you try?

Carl-M · 2016-10-03T18:54:21Z

Mbed LPC1768

theotherjimmy · 2016-10-03T18:57:23Z

Do you mean 1768?

JojoS62 · 2016-10-03T18:57:57Z

The -t is a linker option that is wrong. I experienced also that options are defined double, once in project settings and also in additional misc settings.

Am 03.10.2016 um 20:54 schrieb Jimmy Brisson notifications@github.com:

What target did you try?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

theotherjimmy · 2016-10-03T19:04:44Z

@JojoS62 @Carl-M I appreciate you enthusiasm for this exporter.

The exporter in question is called codered in the tools (file here) In the current master, once issue #2892 Is fixed, you may use the eclipse_gcc_arm or similar exporter to have an equivalent export. That is the way we have planned forward.

OTOH, if you would like to dive into the tools code yourself, I can help you with that.

JojoS62 · 2016-10-03T19:22:10Z

Thanks, eclipse exporter is what I appreciate also. Lpcxpresso uses the GCC toolchain, do no need for a different handling. I see only differences in the linker script that is generated by lpcxpresso. Using the gcc_arm scripts work, but switching to lpcxpresso managed scripts makes trouble.
I'm wiling to investigate this further, a compatible solution would be great.

Am 03.10.2016 um 21:04 schrieb Jimmy Brisson notifications@github.com:

@JojoS62 @Carl-M I appreciate you enthusiasm for this exporter.

The exporter in question is called codered in the tools (file here) In the current master, once issue #2892 Is fixed, you may use the eclipse_gcc_arm or similar exporter to have an equivalent export. That is the way we have planned forward.

OTOH, if you would like to dive into the tools code yourself, I can help you with that.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

theotherjimmy · 2016-10-03T20:07:31Z

Using the gcc_arm scripts work, but switching to lpcxpresso managed scripts makes trouble.

Perfect! Is there any special handling that LPCXpresso needs? (Special flashing tools, Code analysis tools, etc?)

If not, I can change LPCXpresso to be an alias to EclipseGccArm

fjvva · 2016-10-05T09:58:55Z

In order to allow code to compile, a quick fix is ->Project->Properties->Settings->Tool Settings->MCU C++ linker->Managed Linker Script
And then just check the box "Manage Linker Script"

This worked for me

theotherjimmy · 2016-10-20T19:47:06Z

@JojoS62 It's been a few weeks! If you could get back to me on this:

Is there any special handling that LPCXpresso needs? (Special flashing tools, Code analysis tools, etc?)

Then I can get on making the LPCXpresso exporter more robust.

JojoS62 · 2016-10-21T07:25:16Z

thanks for asking. I'm still struggling with the exporters in general. I use the mbed-os master branch and I execute the following:

D:\Projects\Sn\LocalGit\mbed-os\tools>python project.py -n MBED_BLINKY -i lpcxpresso
Scan: blinky
Scan: env
Scan: hal

D:\Projects\Sn\LocalGit\mbed-os\tools>

That gives me an output in mbed-os\export where still a lot is missing and the dir structure is messed up, even a mbed.h. I have attached the complete folder 'MBED_BLINKY_lpcxpresso_LPC1768 '
MBED_BLINKY_lpcxpresso_LPC1768.zip
So, am I doing something wrong here or does the export work now only with mbed-cli?

For the lpcxpresso most things worked before the directory structure change. The other issue was double output of flags and missing/wrong settings in the .cproject file. I had opened an issue for that but accidently closed it. I can reopen it and I will post my fix for the exporter there.

theotherjimmy · 2016-10-21T17:03:20Z

That gives me an output in mbed-os\export where still a lot is missing and the dir structure is messed up, even a mbed.h.

That's the intended directory structure.

So, am I doing something wrong here or does the export work now only with mbed-cli?

Normal projects (not tests) should be exported through mbed-cli (mbed export ...)

I can reopen it and I will post my fix for the exporter there.

Please do!

JojoS62 · 2016-10-21T18:00:15Z

I will try this soon. I followed the instructions in docs/building.md, but that is outdated: URL to mbed, no more setup.py, instructions for export...

theotherjimmy · 2017-04-25T16:54:28Z

@toyowata This exporter has not received the love that it should have. I don't have time right now to fix the issues with the LPCXpresso exporter, but if you do I have some guidance. I would start by trying the gnuarmeclipse exporter in place of lpcxpresso. If that is satisfactory, then you can just change the lpcxpresso key in tools/export/__init__.py to point to the same thing as the gnuarmeclipse in the EXPORTERS dict. If the replacement does not look satisfactory, then we can discuss extending the class.

JojoS62 · 2018-02-16T09:54:26Z

I suggest to close this issue, LPCXpresso has been superseeded by MCUXpresso and projects can be exported to MCUX.

toyowata added the type: bug label Aug 15, 2016

sg- added the tracking label Aug 25, 2016

ciarmcom added the mirrored label Aug 25, 2016

sg- added the devices: nxp label Sep 19, 2016

JojoS62 mentioned this issue Oct 21, 2016

LPC824: export to LPCXpresso, settings for release build gives compiler errors #2883

Closed

sg- added the component: export label Jan 16, 2017

0xc0170 closed this as completed Feb 16, 2018

ciarmcom added the closed_in_jira label Feb 16, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[exporter] LPCXpresso exporter broken #2448

[exporter] LPCXpresso exporter broken #2448

toyowata commented Aug 15, 2016 •

edited

Loading

0xc0170 commented Aug 15, 2016

toyowata commented Aug 19, 2016 •

edited

Loading

ciarmcom commented Aug 25, 2016

toyowata commented Aug 30, 2016

sg- commented Sep 19, 2016

toyowata commented Sep 20, 2016

theotherjimmy commented Sep 20, 2016

toyowata commented Sep 21, 2016

JojoS62 commented Sep 21, 2016

JojoS62 commented Sep 21, 2016

theotherjimmy commented Sep 21, 2016

toyowata commented Sep 23, 2016

Carl-M commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

Carl-M commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

Carl-M commented Oct 3, 2016 •

edited

Loading

theotherjimmy commented Oct 3, 2016

JojoS62 commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

JojoS62 commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016 •

edited

Loading

fjvva commented Oct 5, 2016

theotherjimmy commented Oct 20, 2016

JojoS62 commented Oct 21, 2016

theotherjimmy commented Oct 21, 2016

JojoS62 commented Oct 21, 2016

theotherjimmy commented Apr 25, 2017

JojoS62 commented Feb 16, 2018

[exporter] LPCXpresso exporter broken #2448

[exporter] LPCXpresso exporter broken #2448

Comments

toyowata commented Aug 15, 2016 • edited Loading

Step to reproduce:

mbed library Rev.122 and onward

mbed library Rev.121 and upward

0xc0170 commented Aug 15, 2016

toyowata commented Aug 19, 2016 • edited Loading

Other issue

ciarmcom commented Aug 25, 2016

toyowata commented Aug 30, 2016

sg- commented Sep 19, 2016

toyowata commented Sep 20, 2016

Step to reproduce

theotherjimmy commented Sep 20, 2016

toyowata commented Sep 21, 2016

JojoS62 commented Sep 21, 2016

JojoS62 commented Sep 21, 2016

theotherjimmy commented Sep 21, 2016

toyowata commented Sep 23, 2016

Carl-M commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

Carl-M commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

Carl-M commented Oct 3, 2016 • edited Loading

theotherjimmy commented Oct 3, 2016

JojoS62 commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016

JojoS62 commented Oct 3, 2016

theotherjimmy commented Oct 3, 2016 • edited Loading

fjvva commented Oct 5, 2016

theotherjimmy commented Oct 20, 2016

JojoS62 commented Oct 21, 2016

theotherjimmy commented Oct 21, 2016

JojoS62 commented Oct 21, 2016

theotherjimmy commented Apr 25, 2017

JojoS62 commented Feb 16, 2018

toyowata commented Aug 15, 2016 •

edited

Loading

toyowata commented Aug 19, 2016 •

edited

Loading

Carl-M commented Oct 3, 2016 •

edited

Loading

theotherjimmy commented Oct 3, 2016 •

edited

Loading