The procedure for the issuing of LOA for the CYW20732/6/7 has changed.

Essentially, we have recertified the 20732/6/7S modules to have a Cypress FCC ID assigned and we now provide the LOA signed by Manager of the regulatory team,

Please complete the following template (Cypress Authorization Letter Template (LOA)) and create a new discussion which includes the filled out template here in the WICED Smart Bluetooth Forums

Hi for a EMEA customer design - we need a ref design with WLCSP package - ideally putting every component within 7x7 space- Can we support that??

Question: While using WICED Smart on a CYW20736 project, one notices that there doesn’t appear to be a management callback event for a CONNECTION PARAMETER UPDATE request on the slave side. Is there a way for an application to determine if the Master is requesting a Connection Parameter Update within WICED Smart SDK 2.2.3's hello_sensor project?

Answer: To register an update request handler, use the API: bleprofile_regAppEvtHandler_leConnUpdateComplete

You may also find this discussion helpful: Connection Parameter Update Requests

• The application runs in its own thread and the entire application framework is event driven

• The main entry point of the application is APPLICATION_INIT() where the app has to register its GATT database, configurations and the application create function

• No other operations are allowed at this point

• Once this is done, the rest of the firmware and the BLE stack will be initialized - and once these are ready- the application create function will be invoked

• This is equivalent to C’s main()

• Once you return from this function, everything is event driven

• Callbacks for connection up/down/end of ADV interval/write to GATT handle, interrupts, timer expiry etc. are all events for the application to handle

• So, there is effectively no need for a main() function

I wanted to let everyone know that there will be a Bay Area Meetup for Anaren Atmosphere/Roadmap Updates, including live product demos.

Date: Tuesday, June 14, 2016

Time: 5:30 PM

Location:

Broadcom Corp

190 Mathilda Pl

Sunnyvale, CA

It’s been a while since Anaren's last meetup, so they have some new products on the roadmap that I’m sure you guys will find interesting.

Their cloud-based drag-and-drop development platform, Atmosphere, is now in release version 1.5 with some great new features, and version 2.0 is nearing completion.

They are also on the cusp of releasing thier new Wi-Fi module and the all new Stratosphere Cloud Hosting platform. These tools form an ecosphere that allows hardware or software developers to quickly prototype embedded wireless designs – often without writing a stitch of code or knowing little about hardware implementation when you use their multi-sensor development kit to get started.

The Anaren HW platform is also supported by the Broadcom WICED SDK and Adobe PhoneGap, so you can carry your design momentum forward, straight into your target market.

If this sounds interesting to you, make sure you RSVP here: http://www.meetup.com/Atmosphere-IoT-Development-Platform/events/231575147/?rv=ea1

Changes for WICED-Smart-SDK-2.2.3

• Upgrading to this SDK is highly recommended
• Improved RF performance - fixed spectrum ch37 spectrum growth
• Updated several Linux download tools
• Included optional patch to fix potential NVRAM corruption
• Minor updates to Bluetooth Designer
• Added new sample apps: long_char_big_btu and puart_control_big_mtu

Windows Downloads:

• WICED-Smart-SDK-2.2.3-IDE-Installer (Windows)
• WICED-Smart-SDK-2.2.3 (.7z Archive)

Linux and OSX versions to follow

victorz jamesle1  jakewtorres  boont  arvinds​ jaeyoung​ nsankar​ santol​ andrew997​

jakewtorres​ just published a series of detailed and well written blogs designed to help new users familiarize themselves with the new WICED Smart SDK and development tools:

   Basic Features of the WICED Smart Kernel

• Project 1: How to Send I2C Sensor Data over BLE
  • How to Transmit BLE Notifications
  • How to Initialize and Read From an I2C Sensor
  • Putting It All Together, Project 1

• Project 2: Push a Button, Light an LED
  • How to Toggle a GPIO
  • How to Register for an Interrupt, Project 2 Wrap-Up

santol​ cgariss​ david_armour​ nsankar​ boont​ andrew997​ peter_fenn​

As described in the document here: Broadcom BCM20732S/BCM20736S/BCM20737S Regulatory Approvals

Note that the email address to use for regulatory submissions has changed: bcm2073xs-regulatory-list.pdl@broadcom.com

Broadcom WICED/IoT: Images from CES 2016...

Those who have been playing long enough with the Wiced Sense should have been facing a similar issue as mine, briefly there are two ways to power up the module

1. Coin battery

2. USB cable

With the first method, you need a new battery every once in a while (that while was as short as a few days for me), also if your code has a bug, you will have to take out the battery in occasions. With the second method, there is a complicated way of running a code without battery (put the battery in, reset, connect to USB, remove the battery), then when you change the FW, you need to do that again.

The problem is that without battery, when the module is connected through USB, the bootloader loop runs waiting for the commands to write FLASH, ... (BTW is there any documentation for the bootloader ?), and it never goes out of that loop. But I also noticed that ChipLoad executes the FW right after programming, monitoring the USB activity, I found a way to do this without ChipLoad, you basically need to send the following bytes to the USB port connected to the module

01 2E FC 00 01 4E FC 04 00 00 00 00

I guess the last four bytes are the address that the boot loader jumps to. Doing that the FW is executed. Attached you can find a simple script to do this in windows, there is even a simpler way to do it in Unix.

Now, briefly here is what I do

To run the FW

1. Take out the battery, I will never need it anymore

2. Connect the module to the USB

3. Run rst COMx (x is the COM port number in windows)

4. FW runs

To program the FW

1. Disconnect and reconnect the module to the USB

2. Run make from the SDK

3. FW runs at the end of ChipLoad execution

I hope it is useful for others as much as it has been for me.