Sloeber not working for Duo


#1

Wondering if anyone has the Duo working from Sloeber V4.x?

I have tried to get things going several ways, but when I try to build the Blink example, I get something like

tions/EclipseOxy.app/Contents/Eclipse/arduinoPlugin/packages/RedBear/hardware/STM32F2/0.3.1/variants/RedBear_Duo" -MMD -MP -MF"Blink.d" -MT"Blink.o" -D__IN_ECLIPSE__=1 -x c++ "../Blink.ino"   "Blink.o"
arm-none-eabi-gcc: error: Blink.o: No such file or directory
make: *** [Blink.o] Error 1

(this was generated using the makefile in the workspace/Blink/Release directory)

I know that the Redbear Duo json is okay as everything works fine in the Arduino IDE. And, yes, the path to arm-non-eabi-gcc is fine and works.

Thanks,

steven


#2

I have the same problem.
Someone can help us?
Thank you.


#3

SLOEBER FOR REDBEAR DUO

Arduino C++ Compiler
Command line pattern:
${A.RECIPE.CPP.O.PATTERN.1} ${OUTPUT} ${INPUTS} ${A.RECIPE.CPP.O.PATTERN.2} ${A.RECIPE.CPP.O.PATTERN.3} ${JANTJE.EXTRA.COMPILE} ${JANTJE.EXTRA.CPP.COMPILE} ${JANTJE.EXTRA.ALL}

Arduino C Compiler
Command line pattern:
${A.RECIPE.C.O.PATTERN.1} ${OUTPUT} ${INPUTS} ${FLAGS} ${A.RECIPE.C.O.PATTERN.2} ${A.RECIPE.C.O.PATTERN.3} ${JANTJE.EXTRA.COMPILE} ${JANTJE.EXTRA.C.COMPILE} ${JANTJE.EXTRA.ALL}

Archive Compiler (remove ${A.ARCHIVE_FILE_PATH})
Command line pattern:
${A.RECIPE.AR.PATTERN.1} ${INPUTS} ${A.RECIPE.AR.PATTERN.2} ${A.RECIPE.AR.PATTERN.3} ${JANTJE.EXTRA.ARCHIVE} ${JANTJE.EXTRA.ALL}

Archive Linker (remove ${A.ARCHIVE_FILE_PATH})
Command line pattern:
${A.JANTJE.PRE.LINK}${A.RECIPE.C.COMBINE.PATTERN.1} ${FLAGS} ${INPUTS} ${A.RECIPE.C.COMBINE.PATTERN.2} ${A.RECIPE.C.COMBINE.PATTERN.3} ${JANTJE.EXTRA.ALL} ${JANTJE.EXTRA.LINK}${A.JANTJE.POST.LINK}

EDIT ENVIRMENTS VARIABLES

A.TOOLS.ARM_NONE_EABI_GCC.CPP.DEFINES

Add escape to DLOG_MODULE_CATEGORY, results:

-DBOOTLOADER_SDK_3_3_0_PARTICLE -DDFU_BUILD_ENABLE -DINCLUDE_PLATFORM=1 -DLOG_INCLUDE_SOURCE_INFO=1 -DLOG_MODULE_CATEGORY="“app”" -DMODULAR_FIRMWARE=1 -DMODULE_DEPENDENCY2=0,0,0 -DMODULE_DEPENDENCY=4,2,10 -DMODULE_FUNCTION=5 -DMODULE_INDEX=1 -DMODULE_VERSION=10 -DPARTICLE=1 -DPARTICLE_DCT_COMPATIBILITY -DPARTICLE_USER_MODULE -DPLATFORM_ID=88 -DPLATFORM_NAME=duo -DPLATFORM_THREADING=1 -DPRODUCT_FIRMWARE_VERSION=65535 -DPRODUCT_ID=88 -DRELEASE_BUILD -DRESET_AVRDUDE_FLASHER_SERIAL_SPEED=1200 -DSPARK=1 -DSPARK_PLATFORM -DSPARK_PLATFORM_NET=BCM43438A1 -DSTART_AVRDUDE_FLASHER_SERIAL_SPEED=19200 -DSTART_DFU_FLASHER_SERIAL_SPEED=14400 -DSTART_YMODEM_FLASHER_SERIAL_SPEED=28800 -DSTM32F2XX -DSTM32_DEVICE -DSYSTEM_VERSION_STRING=0.3.1 -DUSBD_PID_CDC=0xC058 -DUSBD_PID_DFU=0xD058 -DUSBD_VID_SPARK=0x2B04 -DUSER_FIRMWARE_IMAGE_LOCATION=0x80C0000 -DUSER_FIRMWARE_IMAGE_SIZE=0x40000 -DUSE_STDPERIPH_DRIVER -DUSE_SWD -D_GNU_SOURCE -D_WINSOCK_H

Add a POST-BUILDING STEP
“${A.RUNTIME.PLATFORM.PATH}/tools/crc32/linux/sh” “${A.RUNTIME.PLATFORM.PATH}/tools/crc32/linux/crc32.sh” “${A.BUILD.PATH}/${A.BUILD.PROJECT_NAME}.bin” “${A.RUNTIME.PLATFORM.PATH}/tools/crc32/linux” “${A.TOOLS.ARM_NONE_EABI_GCC.PATH}”

CREATE ENVIRMENTS VARIABLES
A.TOOLS.FW_LOADER.PROGRAM.PATTERN value: ${A.TOOLS.AVRDUDE.UPLOAD.PATTERN}

CREATE ENVIRMENTS VARIABLES
A.TOOLS.AVRDUDE.UPLOAD.VERBOSE value: ${A.TOOLS.AVRDUDE.UPLOAD.PARAMS.VERBOSE}