I’ve been keen to see if I could get the BrewPi spark-core to talk over wifi.
After the first round of digging it became clear that the SparkCloud had been disabled to free up flash space. (The loader gives you a nice error when you do overflow trying to make the main build without the right command line options).
But I was curious about how much of that memory issue was taken up by cloud specific items, and whether you could squeeze the wifi and a tcpserver into the firmware.
As it happens you can fire up the wifi without any problems, but trying to get the tcpserver going kicks the flash over the memory limit.
[Albeit without telling you like it did with the cloud enabled, i spent about 4hrs to work out why my code wasn’t updating - loader doesn’t complain, web upload of firmware works fine - device reboots but version doesn’t bump!
Eventually I switched to dfu for upload and it now seems to reliably complain about the last bytes not being writeable]
Main 2.10.0 = 104k
Main 2.10.0 + Wifi = 107k
Main 2.10.0 + Wifi + Tcp = > 108k
fixed-point(9/6/15) = ~96k
fixed-point(9/6/15) + blake temp space saver = 88k
Which brings me to the question - is there a better way to manage flash on the core to free up enough space to get this going?
I’m guessing the answer might be ‘not easily on the core wait for the photon, it has 1Mb of Flash’)