Local building for Core+Photon

rei_vilo · October 4, 2015, 12:46pm

Thank you for the two answers.

Here the tests I've conducted so far.

Configuration

Tool-chain and SDK located at
/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2 /Users/ReiVilo/Library/embedXcode/Particle-new with firmware-latest branch

Projects are located at
/Users/ReiVilo/Desktop/particle-1 /Users/ReiVilo/Desktop/particle-2 /Users/ReiVilo/Desktop/particle-3

Test 1

The particle-1 folder contains
/Users/ReiVilo/Desktop/particle-1/LocalLibrary.cpp /Users/ReiVilo/Desktop/particle-1/LocalLibrary.h /Users/ReiVilo/Desktop/particle-1/main.cpp

Test 1a

Launch cd ~/Library/embedXcode/Particle-new/firmware/modules
Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-1 TARGET_DIR=/Users/ReiVilo/Desktop/particle-1/Builds TARGET_FILE=embeddedcomputing clean all program-dfu > ~/Desktop/particle-1/1a.txt
Result: OK.

Test 1b

Change the number of blinks, e.g. blink(myLED, 1, 333); for blink(myLED, 2, 333);

Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-1 TARGET_DIR=/Users/ReiVilo/Desktop/particle-1/Builds TARGET_FILE=embeddedcomputing program-dfu > ~/Desktop/particle-1/1b.txt
Result: NOK

Omitting clean all fails: old code is kept, new code not taken into account. The LED still blinks once, not twice.

Test 1c

Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-1 TARGET_DIR=/Users/ReiVilo/Desktop/particle-1/Builds TARGET_FILE=embeddedcomputing clean all program-dfu > ~/Desktop/particle-1/1c.txt
Result: OK.

Question 1

Is clean all compulsory? Why to build the whole framework each time? Why to upload 3 packages each time, when only the latest one changes?
Downloading to address = 0x08020000, size = 249148 Downloading to address = 0x08060000, size = 169036 Downloading to address = 0x080a0000, size = 2272

Question 2

How to get rid of those messages?
fatal: Not a git repository (or any of the parent directories): .git

Question 3

What is the meaning of COMPILE_LTO=n, which is not documented at https://github.com/spark/firmware/blob/develop/docs/build.md?

Test 2

The particle-2 folder contains
/Users/ReiVilo/Desktop/particle-2/blink.ino /Users/ReiVilo/Desktop/particle-2/LocalLibrary.cpp /Users/ReiVilo/Desktop/particle-2/LocalLibrary.h /Users/ReiVilo/Desktop/particle-2/main.cpp

Test 2a

Sketch uses an .ino extension. main.cpp mentions #include "blink.ino"

Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-2 TARGET_DIR=/Users/ReiVilo/Desktop/particle-2/Builds TARGET_FILE=embeddedcomputing clean all program-dfu > ~/Desktop/particle-2/2a.txt

Result: OK.

Question 1, Question 2, Question 3

Same as per Test 1.

Test 2b

Change the number of blinks, e.g. blink(myLED, 1, 333); for blink(myLED, 2, 333);

Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-2 TARGET_DIR=/Users/ReiVilo/Desktop/particle-2/Builds TARGET_FILE=embeddedcomputing program-dfu > ~/Desktop/particle-2/2b.txt

Result: NOK.

Test 2c

Separating building and linking from uploading. Uploading done through USB or OTA.

Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-2 TARGET_DIR=/Users/ReiVilo/Desktop/particle-2/Builds TARGET_FILE=embeddedcomputing clean all > ~/Desktop/particle-2/2c.txt
Launch particle flash ABCDEFGHIJKLMNOPQRSTUVWX /Users/ReiVilo/Desktop/particle-2/Builds/embeddedcomputing.bin

Result: Success rate = 60%.

Connection fails although the LED pulses cyan and the board is listed as online. Error message is

Flash device failed
[object Object]

Launch particle flash --usb /Users/ReiVilo/Desktop/particle-2/Builds/embeddedcomputing.bin

Result: OK.

Question 4

How to upload the program OTA with success rate = 100%?

Test 3

The particle-3 folder contains
/Users/ReiVilo/Desktop/particle-3/blink.ino /Users/ReiVilo/Desktop/particle-3/LocalLibrary.cpp /Users/ReiVilo/Desktop/particle-3/LocalLibrary.h /Users/ReiVilo/Desktop/particle-3/main.cpp /Users/ReiVilo/Desktop/particle-3/Particle_fast.mk

Particle_fast.mk include a variable definition MY_IDE, which is tested on main.cpp and blink.ino
CPPFLAGS += -DMY_IDE=310 CFLAGS += -DMY_IDE=310

Launch make v=1 GCC_ARM_PATH=/Users/ReiVilo/Library/embedXcode/gcc-arm-none-eabi-4_9-2015q2/bin/ COMPILE_LTO=n PLATFORM_ID=6 APPDIR=/Users/ReiVilo/Desktop/particle-3 TARGET_DIR=/Users/ReiVilo/Desktop/particle-3/Builds TARGET_FILE=embeddedcomputing USER_MAKEFILE=Particle_fast.mk clean all program-dfu > ~/Desktop/particle-3/3a.txt

Result: NOK.

Question 5

How to specify variables in the makefile?

Thank you!

rei_vilo · October 4, 2015, 1:06pm

One more question: Why are you using /stuff/sparkcore/firmware/main while the recommended folder is /stuff/sparkcore/firmware/modules?

Thank you!

rei_vilo · October 5, 2015, 7:31pm

For Question 5, see specific thread Local Build: How to Specify Variables in the Makefile?.

dmh · October 21, 2015, 8:02pm

@BDub does the monolithic build work on the latest branch?

rei_vilo · November 8, 2015, 2:00pm

@BDub

No answer to my comprehensive post?

mdma · January 14, 2016, 9:22am

Thank you for bringing this issues. I tried all the failed test cases against release 0.4.6 (Oct 2 2015) and all the tests passed. Could it be you were using an older release?

The make target given is just program-dfu - which flashes latest built code to the device. To build the code first and flash it to the device you need all program-dfu as a target, as documented at https://github.com/spark/firmware/blob/develop/docs/build.md#targets

all: the default target - builds the artefact for the project

clean: deletes all artefacts so the next build runs from a clean state
all program-dfu: (not bootloader) - builds and flashes the executable to a device via dfu
all st-flash: flashes the executable to a device via the st-link st-flash utility

A clean build isn't necessary each time, only when switching branches.

Q2

How to get rid of those messages?
fatal: Not a git repository (or any of the parent directories): .git

I don't see these messages. What make command do you run that produces this?

Q3

COMPILE_LTO is an internal flag that the build system sets itself for different platforms. You do not need to provide this flag.

Test 2b, same cause as 1b - missing all target.

Test 2c, Q4 - this issue has been resolved in the meantime.

Test 3, Q5: This worked for me, in a test application I had

#if MY_IDE!=310
#error variable not defined as 310
#endif

I got the test to fail by excluding the user makefile (since the variable wasn't defined) and the tests passed when the makefile was used.

Please retry these tests with the latest branch or develop. They should work for you, but if not we can investigate further.

rei_vilo · January 14, 2016, 9:48am

Thank you for your answer.

Unfortunately, the initial tests were performed and reported three months ago, in Oct '15, so I’m not sure I’ve kept the protocol.

In the meantime, almost everything has changed: new release of Mac OS X, new release of Xcode and thus make and obviously new release of the tools for Core and Photon local build.

I’ve found another solution with the MediaTek LinkIt One, which brings WiFi, Bluetooth + BLE, GSM + GPRS, GPS in one single board, plus full Wiring / Arduino implementation and compatibility.

Sorry.

rei_vilo · February 4, 2016, 4:49pm

The RedBear Duo board leverages Particle for the IoT infrastructure, and manages to compile with Arduino. Incidentally, this makes the board supported by embedXcode.

When does Particle plan to release the same feature for the Core and Photon?

rei_vilo · April 27, 2016, 7:56pm

Any update on this major feature?

nrobinson2000 · June 1, 2016, 4:43pm

Hi. @sej7278

I have recently been developing a script for installing and using the Particle Toolchain on Ubuntu-based Distros and OSX. I have done lots of testing and it is now very stable. Read more at po-util.com, or download it instantly with:

curl -fsSL bit.ly/po-util13 | bash

rei_vilo · April 10, 2021, 4:33pm

I had the opportunity to test the offline Particle Workbench for this Remote e-Paper Messages Panel project and I really liked it. It leverages the features of Visual Studio Code and offers cloud and local build. This is what I had in mind for an offline IDE many years ago…

Topic		Replies	Views
Trying to build with the develop branch locally Firmware	8	3160	June 22, 2015
LOCAL TOOLCHAIN: Working with HAL General	2	1339	September 13, 2015
Problem compiling locally for Core Firmware	2	1111	July 5, 2016
Building spark/firmware "locally" on a cloud development server Firmware	5	1623	July 22, 2016
Building locally: git pull angst General	4	1232	March 31, 2015