Differences

This shows you the differences between two versions of the page.

--- playground:mission-log-template1 [2014/11/04 10:13] – [Local Spark-Cloud Server Dataflow] chrono
+++ playground:mission-log-template1 [2015/07/07 12:01] – [Test-Setup] chrono
@@ Line 1: / Line 1: @@
-====== HOWTO: Set up and use a local Spark-Core Cloud ======
+====== Review: Managed Low-Power Switch DGS-1100-8 ======
-It took quite a bit of tinkering and a couple of clarifying sessions on IRC (Thanks to lbt and aholler for their input and support), to deploy the local Spark-Cloud test setup and interpret/abstract the scattered docs into one whole system view model. But why go through all this hassle, when you can just comfortably use the "official" spark.io cloud service to develop & manage your cores instantly?
+In a past Mission-Log, we've [[mission:log:2012:01:13:dlink-green-ethernet-switch-review|reviewed the power consumption of "green" Ethernet Switches]] (consumer-grade/unmanaged) that could be used in off-grid environments and they performed really well. Compliant with IEEE 802.3az Energy Efficient Ethernet, these switches consume less energy by cutting down on power consumption when the traffic volume is low and automatically measure the length of the connected cables to adjust power usage, when cables are shorter than 20 meters. In addition, they monitor the link status of every port and drastically reduce power consumption when a port has no link. With more technology and infrastructure, the need increased for more Ethernet features like VLANs, trunks and many other features, usually  offered only by expensive, loud and very power hungry managed/enterprise switches.
-Well, the IoT (Internet of Things) is a hip buzzword these days and the [[mission:log:2014:09:06:reminder-gotta-get-more-spark-cores|Spark-Cores]] definitely can be categorized as the first generation of open, relatively cheap and hackable wireless IoT devices.
+Luckily this situation has changed and we could test and already deploy a new pair of managed but very low power and fanless (silent) switches: The [[http://us.dlink.com/products/business-solutions/easysmart-8-port-gigabit-switch/|D-Link DGS-1100 Family]], which also come in a sturdy metal case and with the benefit of a (limited - due to legal issues on a per country basis) lifetime warranty.
-For all we know, it is at least save to assume, that we actually have no way of knowing how far this technology branch is going to develop and spread in a couple of years, just like the Internet itself 20 years ago. We should look at the privacy aspects before it's actually too late to do so. In the end, it boils down to this question:
+====== ======
-//Do we really want to give out our complete sensory data (sys/env/biometrics) over all time and possibly full remote control over all the actors, built into everything, at all time, at the place we like to call our home?//
+===== Power Consumption Analysis =====
-In the year 2014, in a post [[http://spectrum.ieee.org/telecom/security/the-real-story-of-stuxnet|Stuxnet]], [[http://www.heise.de/extras/timeline/|Snowden]] & [[http://www.zdnet.com/unsealed-docs-show-what-really-happened-with-lavabit-7000021489/|Lavabit]] era, we have no other choice but to come out of our state of denial and simply accept the fact, that every commercial entity can be compromised through multiple legal, administrative, monetary, social/personal or technological levers. Access- and Cloud-Provider are no exception. All of them can be tricked, coerced or forced to "assist" in one way or another. No matter what anyone promises, from this point on, they all have to be considered compromised.
+For better comparison all measurement results have been put together. A couple of people have been a bit unhappy, that we've only documented power consumption on the DC side in the past review (which is all we care about for off-grid usage). As a result, this time we've documented DC and Wall-Power consumption (with the original D-Link AC/DC plug).
-The current software implementation (firmware- and server-side) has no concept of mesh/p2p or direct networking/communication. All Spark-Cores need a centralized spark-server for Control & Communication. Also, the Spark.connect() routine unfortunately has no timeout (yet?), the Core might hang indefinitely, which could be a big problem, even if your particular code doesn't require to connect to the cloud because after you call Spark.connect(), **your loop will not be called again until the Core finishes connecting to the Cloud**. This might happen if your WiFI or internet access is offline.
+==== Test-Setup ====
-==== Remote Spark-Cloud (AWS) Dataflow ====
+Wall-Power was measured using [[http://www.elv.de/elv-energy-master-profi-energiekosten-messgeraet-1.html|this device]], DC consumption was measured with our [[http://www.amazon.de/dp/B00LZ07BG0|Portapow USB Powermeter]], which also has a connection kit for barrel connectors. For better comparison, we've tested the same set of scenarios as in the first test to keep results as comparable as possible.
-{{:mission:log:2014:10:remote-spark-core-cloud-overview.png|}}
-In this picture the blue lines represent the data flow of the Cores, the clients and the central server. All points marked with a red C show where the current implementation/infrastructure is to be considered compromised and the yellow P marks potential security risks (since the firmware isn't compiled locally), theoretically anything can be injected into the firmware, either in the AWS cloud or even in-stream. Tests showed that the API webservers don't offer perfect forward secrecy, the cores itself use only 128-CBC without DH support, which offers no forward secrecy at all. Not having reliable crypto and passing everything through compromised infrastructure can't be the way to go.
-==== Local Spark-Cloud Server Dataflow ====
-{{:mission:log:2014:10:local-spark-core-cloud-overview.png}}
-When you follow this howto and secure your network access with a strong VPN you'll end up with something that looks like this image, where we effectively mitigate all these issues and take back control of our privacy & autonomy.
+==== Results ====
-==== Key Features/Aspect Comparison ====
+| ||  DGS-1008D G2  ||  DGS-1008D G3  || DGS-1100-8 Rev A1 |||
+| || {{:blog:2012-02-10:d-link-dgs-1008d.jpg?235|}}||{{:blog:2012-02-10:dlink-ds1008v2.jpg?235|}}||{{:blog:2012-02-10:dlink-ds1008v2.jpg?235|}}|||
+| Clients |Mode| 5V DC Current | 5V DC Power | 5V DC Current | 5V DC Power | 5V DC Current | 5V DC Power| 230V AC Power |
+| 0 | Switch only | 66-93mA | 0.33-0.46W | 67-111mA | 0.33-0.55W | 105mA | 0.52W | 0.8W |
+| 1 | Client Stdby | 100-160mA | 0.5-0.8W | 109-124mA | 0.54-0.62W | 131mA | 0.65W | 1W |
+| 2 | Client Stdby | 141-194mA | 0.70-0.97W | 153-161mA | 0.76-0.80W | 154mA | 0.77W | 1.1W |
+| 2 | Client Idle | 160-200mA | 0.8-1W | 170mA | 0.85W | 212mA | 1.06W | 1.5W |
+| 3 | Client SCP | 250mA | 1.25W | 210-220mA | 1.07W | 238mA | 1.2W | 1.7W |
+| 4 | Client SCP | 250mA | 1.25W | 210-220mA | 1.07W | 264mA | 1.32W | 1.9W |
-|:::^ Remote Spark-Cloud (AWS) ^ Local Spark-Cloud Server^
-^ Easy start with WebIDE | Yes | Manual setup required |
-^ Offline Development with Atom and git | No (Use WebIDE) | Yes |
-^ Number of exposable functions | 4 | unlimited((Since source code is open, this can be changed to whatever we like.)) |
-^ Number of exposable variables | 10 | unlimited((Since source code is open, this can be changed to whatever we like.)) |
-^ Local Cross-Compiler Toolchain needed | No | Yes |
-^ Cores still work when Internet is offline | No((Remember: The Core stops in the connect() routine until connected to the cloud. Not one line of your code will be exceuted until that happens.)) | **Yes** |
-^ Perfect Privacy/Forward Secrecy | No((See about weak SHA1 and cipher selection on [[https://www.ssllabs.com/ssltest/analyze.html?d=api.spark.io&hideResults=on|SSL Check for api.spark.io]])) | **Yes**((Depending how you set up your VPN.)) |
-^ Core Firmware can be trusted | Potentially Not | **Yes** |
-^ OTA Update capability | Yes (But potentially insecure) | **Yes** |
-^ Minimum Avg. Non-US Network Latency | >100ms | <10ms (LAN/WiFI) |
-===== =====
+===== Reliability & Performance =====
-===== Installation =====
+The DGS-1100-8 test candidates have been up and running 24x7 for more than 365 days now without any glitch or the necessity to power cycle.
-==== Dependencies ====
+<WRAP round tip>
+When you make changes to the configuration in the web-interface, make sure to click the **"Save Configuration"** button in the top left menu to actually save your changes to non-volatile RAM. Otherwise the next power cycle will wipe your config changes :)
+</WRAP>
-=== dfu-util ===
+===== Conclusion =====
-To claim, configure and flash our Cores locally we'll need dfu-util >= 0.7.0
+Grid powered devices still have the luxury to be able to consume more power than absolutely necessary, since the limiting factor is money and not power itself. Off-Grid scenarios change that point of view on costs, as the value is no longer money, but the painfully finite element of power itself.
-<code>
+There are still a lot of devices out there with a standby-consumption of well above 10W, the DGS-1008D G3 connects 4 clients, actively transfers a lot of data and consumes about 1W. D-link obviously did a good job with this, although there is a little curiosity in StandBy: The G2 consumes a little less power in StandBy, when no clients are connected but the G3 saves considerably more power when active so overall the G3 is a very good evolutionary step in low-power consumption Gigabit-Ethernet technology.
-$ emerge -av dfu-util
-</code>
-In this guide I've used the 9999 gentoo ebuild, which pulls and builds
-the current git master, on other distros your mileage may vary.
-=== Node.js ===
+The only drawback of these switches is their un-managed nature. Hopefully, in the future even managed switches can operate with this kind of power consumption profile.
-<code>
+Other manufacturers, who also build similar products, may always send us their products for hardcore real live evaluation as well :)
-$ emerge -av nodejs
-</code>
-Make sure the npm USE flag is set to get the node package manager as well
+{{tag>ethernet switch review hardware test energy}}
-==== Cross Compiler Toolchain ====
-At this time is wasn't possible yet to use a gentoo crossdev toolchain to compile
-the firmware since it seems to require newlib-nano instead of the plain newlib gentoo
-would like to merge. Aholler
-There wasn't enough time to hunt down this particular bug further so the
-[[https://launchpad.net/gcc-arm-embedded/+download|official toolchain]] was used instead.
-<code>
-$ mkdir spark-core
-$ cd spark-core
-</code>
-<code>
-$ wget https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q2-update/+download/gcc-arm-none-eabi-4_8-2014q2-20140609-linux.tar.bz2
-$ tar xvjpf gcc-arm-none-eabi-4_8-2014q2-20140609-linux.tar.bz2
-</code>
-Tell your system to pick it up automatically:
-<code>$ export PATH=$PATH:$HOME/src/spark-core/gcc-arm-none-eabi-4_8-2014q2/bin</code>
-==== Core/Firmware ====
-<code>
-$ git clone https://github.com/spark/core-firmware.git
-$ git clone https://github.com/spark/core-common-lib.git
-$ git clone https://github.com/spark/core-communication-lib.git
-</code>
-Make sure you checkout the three core repos into the same folder, otherwise it won't build.
-==== Spark Server ====
-<code>
-$ git clone https://github.com/spark/spark-server.git
-</code>
-==== Spark CLI ====
-<code>
-$ npm install -g spark-cli (need either root or sudo)
-</code>
-===== Configuration & Usage =====
-==== Local Spark cloud server ====
-<code>
-$ cd spark-server/js
-$ npm install
-$ node main.js
--------
-No users exist, you should create some users!
--------
-connect.multipart() will be removed in connect 3.0
-visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
-connect.limit() will be removed in connect 3.0
-Starting server, listening on 8080
-static class init!
-core keys directory didn't exist, creating... /home/chrono/src/spark-core/spark-server/js/core_keys
-Creating NEW server key
-Loading server key from default_key.pem
-set server key
-server public key is:
------BEGIN PUBLIC KEY-----
-MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2UuRHTMfftLH/w814i9x
-H3dFElK4J4Zp3SkF3Ere3pS/DVBJUG1MAirv6jfGP3knmWORR9hWEdjqJNGwAms
-SESv5Ztt6zxlB4vbmzkK914bj/d8UuBjEFczfOh5YX65lQUdKm5arxjGza9I8tN+
-i+mdy/bNg3go9V1NflWNm0LQswwtBeVP0kdo/YOh8GJS7VZXyPIgDB/SrmgXfdvE
-crAaE/0LiaI6/sOrMn7INirGJaHfkzSNs1yBZ0ZTci9HbFH0A/prwG5H5qmUVARa
-eQ2T/Zk8I+QuBzjaqTqNLn+rOmbTDWT0pQCdIHJMURcKRDE54ChZeAMw3Sft5jO
-nQIDAQAB
------END PUBLIC KEY-----
-Your server IP address is: 192.168.1.100
-server started { host: 'localhost', port: 5683 }
-</code>
-==== Spark-CLI Configuration ====
-Spark-CLI usually wants to connect to the official Spark cloud, so we need
-to tell it where to connect instead. Since our spark-server told us it is
-listening on **192.168.1.100** we just say:
-<code>
-$ spark config local api-url http://192.168.1.100:8080
-$ spark config local
-</code>
-This will create/update the spark-cli configuration found in ~/.spark/ reflecting
-our wish to use the local cloud instance running on **192.168.1.100** instead of the public one.
-At the point of writing these features are not yet documented but this
-[[https://github.com/spark/spark-cli/commit/26bbf530fe835943399b10c49e3e9194f482a3b1|commit]]
-worked here.
-==== Prepare a new Spark-Core ====
-Let's leave the server running in this shell and open another terminal
-to configure the core. Now it's also a good time to connect your Micro-USB cable to the Spark-Core.
-=== Update factory firmware & CC3000 code ===
-If this is a new Spark-Core, we want to run a special firmware program (deep-update), that will update the firmware running inside the CC3000 WiFi module. Put your Spark-Core in DFU-Mode by simultaneously pressing the MODE and RESET buttons, then releasing RESET while continuing to hold MODE for at least 3 seconds until the LED starts blinking (3-4Hz) yellow (red+green).
-<code>$ spark flash --usb deep_update_2014_06</code>
-<code>
-FOUND DFU DEVICE 1d50:607f
-checking file  /usr/lib64/node_modules/spark-cli/binaries/deep_update_2014_06.bin
-spawning dfu-util -d 1d50:607f -a 0 -i 0 -s 0x08005000:leave -D /usr/lib64/node_modules/spark-cli/binaries/deep_update_2014_06.bin
-dfu-util 0.7
-[...]
-Filter on vendor = 0x1d50 product = 0x607f
-Opening DFU capable USB device... ID 1d50:607f
-Run-time device DFU version 011a
-Found DFU: [1d50:607f] devnum=0, cfg=1, intf=0, alt=0, name="@Internal Flash  /0x08000000/20*001Ka,108*001Kg"
-Claiming USB DFU Interface...
-Setting Alternate Setting #0 ...
-Determining device status: state = dfuERROR, status = 10
-dfuERROR, clearing status
-Determining device status: state = dfuIDLE, status = 0
-dfuIDLE, continuing
-DFU mode device DFU version 011a
-Device returned transfer size 1024
-No valid DFU suffix signature
-Warning: File has no DFU suffix
-DfuSe interface name: "Internal Flash  "
-Downloading to address = 0x08005000, size = 93636
-............................................................................................
-File downloaded successfully
-Transitioning to dfuMANIFEST state
-Error during download get_status
-Flashed!
-</code>
-Don't worry about the "Error during download get_status", apparently this is "normal" and doesn't mean the flash process failed. When the LED is blinking (3-4Hz) green, put it into DFU-Mode again and flash a regular firmware like Tinker to get connected and developing again.
-<code>$ spark flash --usb tinker</code>
-=== ID your Core ===
-Put your Spark-Core into Listening-Mode by pressing and holding the MODE button until the LED is blinking (2Hz) blue. Now run the following command to get your Core's ID:
-<code>$ spark identify</code>
-<code>Your core id is: 1234567890abcdef</code>
-Note/copy this ID, you'll need it soon again.
-=== Upload local Spark-Cloud's pub-key to Spark-Core ===
-Now that we've got the Spark-CLI ready, we can supply our Spark-Core with the public key
-of our freshly deployed spark-server. This actually is a good practice against DNS hijacking or other
-man-in-the-middle type attacks because our Spark-Cores can now determine that they are
-communicating with our server and not someone else's. It would be good to have some of the more stack/sec oriented people looking deeper into the [[https://github.com/spark/spark-protocol/blob/master/js/lib/ICrypto.js|code]].
-<code>
-$ cd spark-core/spark-server/js
-$ ls -al default*
-</code>
-<code>
--rw-r--r-- 1 chrono users 1679 Sep 25 11:27 default_key.pem
--rw-r--r-- 1 chrono users  451 Sep 25 11:27 default_key.pub.pem
-</code>
-Put the Spark-Core into DFU mode again and then execute:
-<code>$ spark keys server default_key.pub.pem 192.168.1.100</code>
-<code>
-Creating DER format file
-running openssl rsa -in  default_key.pub.pem -pubin -pubout -outform DER -out default_key.pub.der
-checking file  default_key.pub192_168_1_100.der
-spawning dfu-util -d 1d50:607f -a 1 -i 0 -s 0x00001000 -D default_key.pub192_168_1_100.der
-dfu-util 0.7
-[...]
-Filter on vendor = 0x1d50 product = 0x607f
-Opening DFU capable USB device... ID 1d50:607f
-Run-time device DFU version 011a
-Found DFU: [1d50:607f] devnum=0, cfg=1, intf=0, alt=1, name="@SPI Flash : SST25x/0x00000000/512*04Kg"
-Claiming USB DFU Interface...
-Setting Alternate Setting #1 ...
-Determining device status: state = dfuERROR, status = 10
-dfuERROR, clearing status
-Determining device status: state = dfuIDLE, status = 0
-dfuIDLE, continuing
-DFU mode device DFU version 011a
-Device returned transfer size 1024
-No valid DFU suffix signature
-Warning: File has no DFU suffix
-DfuSe interface name: "SPI Flash : SST25x"
-Downloading to address = 0x00001000, size = 1024
-.
-File downloaded successfully
-Okay!  New keys in place, your core will not restart.
-</code>
-=== Create new keys for your core ===
-Put the Spark-Core into DFU mode again and then execute:
-<code>
-$ mkdir core_keys
-$ cd core_keys
-$ spark keys doctor 1234567890abcdef
-</code>
-<code>
-FOUND DFU DEVICE 1d50:607f
-running openssl genrsa -out 1234567890abcdef_new.pem 1024
-running openssl rsa -in 1234567890abcdef_new.pem -pubout -out 1234567890abcdef_new.pub.pem
-running openssl rsa -in 1234567890abcdef_new.pem -outform DER -out 1234567890abcdef_new.der
-New Key Created!
-FOUND DFU DEVICE 1d50:607f
-FOUND DFU DEVICE 1d50:607f
-running dfu-util -d 1d50:607f -a 1 -s 0x00002000:1024 -U pre_1234567890abcdef_new.der
-running openssl rsa -in pre_1234567890abcdef_new.der -inform DER -pubout -out pre_1234567890abcdef_new.pub.pem
-Saved!
-checking file  1234567890abcdef_new.der
-spawning dfu-util -d 1d50:607f -a 1 -i 0 -s 0x00002000:leave -D 1234567890abcdef_new.der
-dfu-util 0.7
-Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
-Copyright 2010-2012 Tormod Volden and Stefan Schmidt
-This program is Free Software and has ABSOLUTELY NO WARRANTY
-Please report bugs to dfu-util@lists.gnumonks.org
-Filter on vendor = 0x1d50 product = 0x607f
-Opening DFU capable USB device... ID 1d50:607f
-Run-time device DFU version 011a
-Found DFU: [1d50:607f] devnum=0, cfg=1, intf=0, alt=1, name="@SPI Flash : SST25x/0x00000000/512*04Kg"
-Claiming USB DFU Interface...
-Setting Alternate Setting #1 ...
-Determining device status: state = dfuUPLOAD-IDLE, status = 0
-aborting previous incomplete transfer
-Determining device status: state = dfuIDLE, status = 0
-dfuIDLE, continuing
-DFU mode device DFU version 011a
-Device returned transfer size 1024
-No valid DFU suffix signature
-Warning: File has no DFU suffix
-DfuSe interface name: "SPI Flash : SST25x"
-Downloading to address = 0x00002000, size = 610
-.
-File downloaded successfully
-Transitioning to dfuMANIFEST state
-Error during download get_status
-Saved!
-attempting to add a new public key for core 1234567890abcdef
-submitting public key succeeded!
-Okay!  New keys in place, your core should restart.
-</code>
-==== Claim the Spark-Core ====
-Press RESET on the core and/or hold the MODE button until the
-core goes back to listening mode (blinking blue). In order to
-create a new user and claim your first core we simply run:
-<code>$ spark setup</code>
-<code>
-If you run this the first time, you'll have to create an
-account in your local cloud first:
-========================================
-Setup your account
-Could I please have an email address?  myemail@domain.net
-and a password?  *******
-Trying to login...
-Login failed, Lets create a new account!
-confirm password  *******
-creating user:  myemail@domain.net
-user creation succeeded!
-Got an access token! 7yxc7yxc7yxc7yxc7yxc7yxc7yxc7yxc7yxc
-Logged in!  Saving access token: 7yxc7yxc7yxc7yxc7yxc7yxc7yxc7yxc7yxc
-Using the setting "access_token" instead
-Now that we have created a user and are logged in (got an access token)
-we can claim our core:
-----------------------
-Finding your core id
-Your core id is: 1234567890abcdef
-========================================
-Setup your wifi
-SSID: mySSID
-Security 0=unsecured, 1=WEP, 2=WPA, 3=WPA2: 3
-Wifi Password: myWifiPSK
-Attempting to configure wifi on /dev/ttyACM0
-I said: w
-Serial said: SSID:
-I said: mySSID
-Serial said: mySSID
-Security 0=unsecured, 1=WEP, 2=WPA, 3=WPA2:
-I said: 3
-Serial said: 3
-Password:
-I said: myWifiPSK
-Serial said: myWifiPSK
-Thanks! Wait about 7 seconds while I save those credentials...
-Awesome. Now we'll connect!
-If you see a pulsing cyan light, your Spark Core
-has connected to the Cloud and is ready to go!
-If your LED flashes red or you encounter any other problems,
-visit https://www.spark.io/support to debug.
-    Spark <3 you!
-Done!  Your core should now restart.
-Please wait until your core is breathing cyan and then press ENTER
-</code>
-The Led should now slowly pulsate in cyan (blue+green) and your
-spark-server should show something in the console like:
-<code>
- Connection from: 192.168.1.123, connId: 1
-on ready { coreID: '123456789abcdef',
-  ip: '192.168.1.123',
-  product_id: 0,
-  firmware_version: 10,
-  cache_key: '_0' }
-Core online!
-</code>
-=== Check/List cores ===
-<code>
-$ spark list
-</code>
-<code>
-Checking with the cloud...
-Retrieving cores... (this might take a few seconds)
-tinkertest (123456789abcdef) is online
-  Functions:
-    int digitalread(String args)
-    int digitalwrite(String args)
-    int analogread(String args)
-    int analogwrite(String args)
-</code>
-==== Compile firmware ====
-<code>
-$ cd core-firmware/build
-</code>
-<code>
-$ make clean all
-</code>
-<code>
-Building core-common-lib
-make[1]: Nothing to be done for `all'.
-Building core-communication-lib
-make[1]: Nothing to be done for `all'.
-Building target: core-firmware.elf
-Invoking: ARM GCC C++ Linker
-mkdir -p ./
-arm-none-eabi-g++ -g3 -gdwarf-2 -Os -mcpu=cortex-m3 -mthumb  -I../inc -I../libraries/Serial2 -I../../core-common-lib/CMSIS/Include -I../../core-common-lib/CMSIS/Device/ST/STM32F10x/Include -I../../core-common-lib/STM32F10x_StdPeriph_Driver/inc -I../../core-common-lib/STM32_USB-FS-Device_Driver/inc -I../../core-common-lib/CC3000_Host_Driver -I../../core-common-lib/SPARK_Firmware_Driver/inc -I../../core-common-lib/SPARK_Services/inc -I../../core-communication-lib/lib/tropicssl/include -I../../core-communication-lib/src -I. -ffunction-sections -Wall -fmessage-length=0 -Werror=deprecated-declarations -MD -MP -MF core-firmware.elf.d -DUSE_STDPERIPH_DRIVER -DSTM32F10X_MD -DDFU_BUILD_ENABLE -DSPARK=1 -DRELEASE_BUILD  ./obj/src/spark_wiring_random.o ./obj/src/spark_wiring_tcpserver.o ./obj/src/application.o ./obj/src/spark_wiring_i2c.o ./obj/src/spark_wiring_usartserial.o ./obj/src/spark_wiring_interrupts.o ./obj/src/spark_wiring_usbserial.o ./obj/src/spark_wiring_ipaddress.o ./obj/src/usb_endp.o ./obj/src/usb_prop.o ./obj/src/spark_wiring_stream.o ./obj/src/spark_wiring.o ./obj/src/spark_wiring_print.o ./obj/src/stm32_it.o ./obj/src/spark_wiring_string.o ./obj/src/main.o ./obj/src/spark_wiring_wifi.o ./obj/src/spark_wiring_eeprom.o ./obj/src/spark_wiring_tone.o ./obj/src/usb_desc.o ./obj/src/newlib_stubs.o ./obj/src/wifi_credentials_reader.o ./obj/src/spark_wiring_udp.o ./obj/src/spark_wiring_time.o ./obj/src/spark_utilities.o ./obj/src/spark_wiring_tcpclient.o ./obj/src/spark_wlan.o ./obj/src/usb_istr.o ./obj/src/spark_wiring_spi.o ./obj/src/spark_wiring_servo.o ./obj/src/startup/startup_stm32f10x_md.o --output core-firmware.elf -T../linker/linker_stm32f10x_md_dfu.ld -nostartfiles -Xlinker --gc-sections  -L../../core-common-lib/build -lcore-common-lib -L../../core-communication-lib/build -lcore-communication-lib -Wl,-Map,core-firmware.map --specs=nano.specs -lc -lnosys -u _printf_float
-Invoking: ARM GNU Create Flash Image
-arm-none-eabi-objcopy -O binary core-firmware.elf core-firmware.bin
-Invoking: ARM GNU Create Flash Image
-arm-none-eabi-objcopy -O ihex core-firmware.elf core-firmware.hex
-Invoking: ARM GNU Print Size
-arm-none-eabi-size --format=berkeley core-firmware.elf
-   text	   data	    bss	    dec	    hex	filename
-	   1224	  11864	  91760	  16670	core-firmware.elf
-</code>
-==== OTA firmware update ====
-<code>
-$ spark flash 1234567890abcdef tinker
-</code>
-<code>
-Including:
-/usr/lib64/node_modules/spark-cli/binaries/spark_tinker.bin
-attempting to flash firmware to your core 1234567890abcdef
-flash core said  {"id":"1234567890abcdef","status":"Update started"}
-</code>
-<code>
-set_core_attributes { coreID: '1234567890abcdef',
-  userID: '1a2b3c4d5e6f7A8B9C0D' }
-FlashCore { coreID: '1234567890abcdef',
-  userID: '1a2b3c4d5e6f7A8B9C0D+QQyn' }
-flash core started! - sending api event { coreID: '1234567890abcdef' }
-.168.1.100 - - [Sun, 05 Oct 2014 09:34:18 GMT] "PUT /v1/devices/1234567890abcdef?access_token=060085e419be45ea4c4c1b7f09a443c2806a7fb3 HTTP/1.1" 200 68 "-" "-"
-on response, no chunk, transfer done!
-releasing flash ownership  { coreID: '1234567890abcdef' }
-flash core finished! - sending api event { coreID: '1234567890abcdef' }
-Connection from: 192.168.1.123, connId: 185
-on ready { coreID: '1234567890abcdef',
-  ip: '192.168.1.123',
-  product_id: 0,
-  firmware_version: 10,
-  cache_key: '_184' }
-Core online!
-</code>
-==== Caveats ====
-  * Compiling through the local cloud is on the road map but doesn't work yet
-{{tag>tag1 tag2 }}
-{{keywords>Apollo-NG apollo next generation hackerspace hacker space research development makerspace fablab diy community open-resource open resource mobile hackbus tag1 tag2}}
 ~~DISCUSSION~~
-When you are done with your draft, enter the following URL schema, create the page (with current date and your title) and copy the content into it:
-https://apollo.open-resource.org/mission:log:2013:09:24:title-of-mission-log

User Tools

Site Tools

Differences

Page Tools