Please help with some further confusion.
I have converted to using NetBeans (and the integrated call to dfu). Will the core-firmware.bin be “automatically” loaded by NetBeans???
I manuall get the V0.2.0 revisions.
Manually copy them into my exsiting directories, overwriting what is there.
Then clean, build and load.
Am I properly capturing all the needed core updates???
Am I capturing the cc3000 updates???
I don’t have NetBeans to verify with @LZHenry, but as long as you download and replace all three repositories, I think the process you described should work fine.
You are not capturing the CC3000 updates yet, because there are not yet finalized updates to share. Soon!
I have used the netbeans approach to loading firmware onto the spark core manually and all you need to do to get the latest firmware working is to replace the 3 old folders with the new and recompile and then flash.
Can you please fix the extern Timer Interrupt handler error on your web based IDE so that I could load via cloud.
…/…/core-common-lib/SPARK_Firmware_Driver/inc/config.h:12:2: warning: #warning “Defaulting to Release Build” [-Wcpp]
timer.cpp: In function ‘void TIM2_IRQHandler()’:
timer.cpp:32:14: error: previous declaration of ‘void TIM2_IRQHandler()’ with ‘C++’ linkage
timer.cpp:68:33: error: conflicts with new declaration with ‘C’ linkage
I know you guys are busy and this fix may not be on top of the priority todo list, but I need the feature.
Currently I am compiling locally from netbeans.
When the above is done, most of the time the socket connect call for cloud connection will block the user loop from running and will constantly lead to WLAN restart if internet is not present or blocked (WiFi is available)
I’ll create a github issue so can be debated over there if this is what the user experience should be i.e. run user application irrespective of cloud/internet connection.
@kennethlimcp when the cloud is disabled via includes through webIDE, the behaviour would be non-blocking in the current case so the user experience should be pretty smooth. So I bet on using the cloud disable includes in your case and use Spark.connect/disconnect judiciously when the internet is not present so as not block the user’s loop().