It looks like the Windows and Mac version of 2.2 have been pulled. When will they be available again?
I am republishing these now. The Mac and .z files are updated, but the Windows installer is taking some time (500MB).
Can you provide any more detailed summary on particular bugs that are fixed in 2.2?
I tried it quickly but I am wondering if it is worth doing a new round of power testing before using it in a production build.
Unfortunately we do not have access to the low level details for the bugs that were fixed.
I can tell you that firmware tweaks were made which allowed the part to perform more inline with the power numbers posted in the datasheet and pass regulatory.
I recommend moving to SDK 2.2 if you can.
The first thing I noticed was the boot time increased 3x - consuming 34 mAS of energy vs about 10 previously, which had me worried that there might be other changes.
However perhaps the other changes reduce the power elsewhere in the application.
Does SDK 2.1.1 sometimes not pass regulatory for the 20736? We haven't had our design tested yet.
How did you measure the boot time? Could you tell me the exact boot time?
I roughly measured the boot time, which is around 2 seconds (is it too large?), but I don't know the accurate time.
I did not measure it carefully. I just observed the length of time from
when the board is powered or comes out of reset, to when the application
If you look at the current draw over time you will see a long period of
high draw when it is loading the firmware image out of eeprom, this where
the delay comes from
On May 29, 2015 6:14 PM, "noalac" <firstname.lastname@example.org>
Thanks for your reply.
I just posted a new question about this issue. Here is the link
I described how I measured the boot time in this question. I can see the current draw when the board is booting, but I try to measure the time correctly.
I don't whether it is related with the SDK version or not, but I can try different versions.
WICED smart SDK couldn't install in windows 10.
Unfortunately, Windows 10 did not exist when we released this version of the SDK, so I'm assuming that we did not test on this platform.
I will talk to the SVT team about testing on Windows 10 for the next release of the SDK.
You might want to take a look at this post on Stack Overflow as well: http://stackoverflow.com/questions/31729714/just-installed-windows-10-and-eclipse-no-more-starts
Apparently this is an issue with Windows 10/Eclipse?