WICED Smart SDK version 2.0.1 is now available

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

Note: SDK 2.0.1 requires the WICED SMART BCM92073X_LE_KIT small form factor development board and cannot be used with older BCM920732_LE_KIT development boards.


WICED™ SMART Software Development Kit (version 2.0.1) is now available online here:WICED Smart Documentation


The WICED™ SMART SDK includes the tools and software needed to create BT and networking applications for a wide range of products.


The SDK is available as a standalone zipfile or as a separate installer bundled with the WICED™ Integrated Development Environment.

0 Likes
10 Replies
MichaelF_56
Moderator
Moderator
Moderator
250 sign-ins 25 comments on blog 10 comments on blog

Note that support for OSX and Linux has been added  the SDK 2.0 release as well.

0 Likes
Anonymous
Not applicable

Does SDK 2.0.1 support '20732-based designs ?

I am not talking about BCM920732_LE_KIT which I know it does not support but any custom design based on '20732.

Thanks

Lukas

0 Likes
Anonymous
Not applicable

Hi Lukas,

Where did you find the information stating that SDK 2.0.1 does not support the BCM920732_LE_KIT.

I need this for reference.

Thanks,

Mike

0 Likes

This has been posted in numerous places throughout the forum, including the first post in this thread.

I am confirming again that SDK 2.0.1 does not support the BCM920732_LE_KIT (firmware differences).

0 Likes

The MAC OSX Version of SDK 2.0.1 was just added to the community: WICED-Smart-SDK-2.0.1-IDE-Installer.pkg

0 Likes
SuLe_1710756
Level 5
Level 5
10 likes received First like received First like given

I have a question about SDK 2.0.1.

When I build the example application of "cycling_speed_cadence" in SDK 1.1.0, Total RAM footprint is as follows,

--------------------------------------------------------------------------------

Patches start at 0x00205918 (RAM address)

Patches end at 0x00208B1C (RAM address)

Application starts at 0x00208A08 (RAM address)

Application ends at 0x00209730 (RAM address)

Patch size (including reused RAM)      12804 bytes

Patch size 12528 bytes

Application size 3368 bytes

------

  Total RAM footprint 15896 bytes (15.5kiB)

However, when I build same application in SDK 2.0.1, Total RAM footprint is as follows.

I think this is the reason that patch may be migrated into ROM.

--------------------------------------------------------------------------------

Patches start at 0x00204568 (RAM address)

Patches end at 0x00204AFC (RAM address)

Application starts at 0x00204974 (RAM address)

Application ends at 0x00205714 (RAM address)

Patch size (including reused RAM)       1428 bytes

Patch size 1036 bytes

Application size 3488 bytes

------

Total RAM footprint 4524 bytes (4.4kiB)

  --------------------------------------------------------------------------------

Our major customer would like to use more RAM space for user application, so is it possible to use SDK2.0 with BCM20732?

I know SDK 2.0 is running in BCM92083X_LE_KIT, but I am not sure that SDK 2.0 is also running in BCM20732 or BCM20732S module.

Thanks,

SM

0 Likes
Anonymous
Not applicable

Unfortunately SDK 2.0.1 does not support 20732.

Please take a look at this discussion:

Does SDK 2.0.1 support '20732-based designs ?

0 Likes

Patches have been optimized within SDK 2.0.1 such that more RAM is free for user applications.  As mentioned, SDK 2.0.1 requires the new BCM20737-based  BCM92073X_LE_KIT development environment and will not work with the existing 20732-based TAG board.

The new board is discussed/shown on the 1-pager here: WICED SMART 1-Page Overview

wowu_1723141
Level 2
Level 2
Welcome!

Hi, All,

I got an issue in SDK2.0.1, seems the compiler ignored head file changes. For example, in hello_sensor, I compiled this project before, and then I modified the hello_sensor.h, and re-compile the project, you could see there is no compile procedure and linker works directly.

B. Regds

Wolfman

0 Likes

It looks like the dependency is not properly recognized by the makefiles. We will fix this in the next release of the SDK. Please clean and then build your app as a workaround for now.

0 Likes