WICED currently has support for sflash from the following manufacturers.

1. MACRONIX
2. MICRON
3. SST
4. EON
5. ISSI
6. WINBOND
7. CYPRESS

You can get a list of all the supported sflash in CYW43907 with External SFLASH in WICED . If you want to add support for any other part number from the existing supported flash manufacturers in WICED SDK, you can follow the steps mentioned below. In this example, I have added support for N25Q128A flash from MICRON.

For ST based platforms:

• Please add the SFLASH_ID from the part number datasheet in 43xxx_Wi-Fi/libraries/drivers/spi_flash/spi_flash_internal.h
  

    #define SFLASH_ID_MX25L8006E           ( (uint32_t) 0xC22014 )

    #define SFLASH_ID_MX25L1606E           ( (uint32_t) 0xC22015 )

    #define SFLASH_ID_MX25L6433F           ( (uint32_t) 0xC22017 )

    #define SFLASH_ID_MX25L12835F          ( (uint32_t) 0xC22018 )

    #define SFLASH_ID_MX25L25635F          ( (uint32_t) 0xC22019 )

    #define SFLASH_ID_MX25U1635F           ( (uint32_t) 0xC22535 )

    #define SFLASH_ID_MX66U51235F          ( (uint32_t) 0xC2253A )

    #define SFLASH_ID_SST25VF080B          ( (uint32_t) 0xBF258E )

    #define SFLASH_ID_EN25QH16             ( (uint32_t) 0x1C3015 )

    #define SFLASH_ID_ISSI25CQ032          ( (uint32_t) 0x7F9D46 )

    #define SFLASH_ID_N25Q512A             ( (uint32_t) 0x20BB20 )

    #define SFLASH_ID_ISSI25LP064          ( (uint32_t) 0x9D6017 )

    #define SFLASH_ID_N25Q064A             ( (uint32_t) 0x20BA17 )

    #define SFLASH_ID_W25Q64FV             ( (uint32_t) 0xEF4017 )

    #define SFLASH_ID_CY15B104Q            ( (uint32_t) 0x7F7F7F )

    +#define SFLASH_ID_N25Q128A             ( (uint32_t) 0x20BA18 )

    #define SFLASH_ID_DEFAULT              ( (uint32_t) 0x000000 )

• Then try adding the size of the new part number in 43xxx_Wi-Fi/libraries/drivers/spi_flash/spi_flash_internal.h

   #define SFLASH_SIZE_1MByte                0x100000

   #define SFLASH_SIZE_2MByte                0x200000

   #define SLFASH_SIZE_32MByte               0x2000000

   #define SFLASH_SIZE_64MByte               0x4000000

   #define SFLASH_SIZE_512KByte              0x80000

   #define SFLASH_SIZE_16MByte               0x1000000

• Add the device name in the sflash_device_id_size structure in the following manner

         device_id_to_flash_size_t sflash_device_id_size [SFLASH_ID_MAX_PARTS] =

         {

                { SFLASH_ID_MX25L8006E,  SFLASH_SIZE_1MByte   },

                { SFLASH_ID_MX25L1606E,  SFLASH_SIZE_2MByte   },

                { SFLASH_ID_MX25L25635F, SLFASH_SIZE_32MByte  },

                { SFLASH_ID_MX25U1635F,  SFLASH_SIZE_2MByte   },

                { SFLASH_ID_SST25VF080B, SFLASH_SIZE_1MByte   },

                { SFLASH_ID_EN25QH16,    SFLASH_SIZE_2MByte   },

                { SFLASH_ID_N25Q512A,    SFLASH_SIZE_64MByte  },

                { SFLASH_ID_CY15B104Q,   SFLASH_SIZE_512KByte },

                { SFLASH_ID_N25Q128A,    SFLASH_SIZE_16MByte  }

         };

• If you are using WINBOND, ISSI, CYPRESS flash, you have to add SFLASH_SUPPORT_WINBOND_PARTS in 43xxx_Wi-Fi/libraries/drivers/spi_flash/spi_flash.mk or as a part of GLOBAL_DEFINES in your <platform>.mk file

For 4390x based platform

To add a new part with the already supported sflash chips for 4390x platform, you have to make the necessary modifications in 43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/spi_flash.

• Just like ST based platforms, you need to add the SFLASH_ID in 43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/spi_flash/spi_flash.h

      #define SFLASH_ID_MX25L8006E           SFLASHID( 0xC2, 0x20, 0x14 )

      #define SFLASH_ID_MX25L1606E           SFLASHID( 0xC2, 0x20, 0x15 )

      #define SFLASH_ID_MX25L6433F           SFLASHID( 0xC2, 0x20, 0x17 )

      #define SFLASH_ID_MX25L12835F          SFLASHID( 0xC2, 0x20, 0x18 )

      #define SFLASH_ID_MX25L25635F          SFLASHID( 0xC2, 0x20, 0x19 )

      #define SFLASH_ID_MX25U1635F           SFLASHID( 0xC2, 0x25, 0x35 )

      #define SFLASH_ID_MX66U51235F          SFLASHID( 0xC2, 0x25, 0x3A )

      #define SFLASH_ID_SST25VF080B          SFLASHID( 0xBF, 0x25, 0x8E )

      #define SFLASH_ID_EN25QH16             SFLASHID( 0x1C, 0x30, 0x15 )

      #define SFLASH_ID_ISSI25CQ032          SFLASHID( 0x7F, 0x9D, 0x46 )

      #define SFLASH_ID_N25Q512A             SFLASHID( 0x20, 0xBB, 0x20 )

      #define SFLASH_ID_ISSI25LP064          SFLASHID( 0x9D, 0x60, 0x17 )

      #define SFLASH_ID_N25Q064A             SFLASHID( 0x20, 0xBA, 0x17 )

      #define SFLASH_ID_W25Q64FV             SFLASHID( 0xEF, 0x40, 0x17 )

      #define SFLASH_ID_S25FL064L            SFLASHID( 0x01, 0x60, 0x17 )

      #define SFLASH_ID_S25FL128L            SFLASHID( 0x01, 0x60, 0x18 )

      #define SFLASH_ID_S25FL256L            SFLASHID( 0x01, 0x60, 0x19 )

      #define SFLASH_ID_N25Q128A             SFLASHID( 0x20, 0xBA, 0x18 )

      #define SFLASH_ID_DEFAULT              SFLASHID( 0x00, 0x00, 0x00 )

• In 43xxx_Wi-Fi/WICED/platform/MCU/BCM4390x/peripherals/spi_flash/spi_flash.c, you have to add the part number information in sflash_capabilities_tables structure.

       #ifdef SFLASH_SUPPORT_MICRON_PARTS

              { SFLASH_ID_N25Q064A,       { 8*MBYTE,    256,  .action = &micron_action,   .speed_advance = &micron_speed_config } },

              { SFLASH_ID_N25Q128A,       { 16*MBYTE,   256,  .action = &micron_action,   .speed_advance = &micron_speed_config } },

      #endif

•      If you are using any flash other than macronix flash, you have to add support in <platform_name>.mk file in the following manner.

             GLOBAL_DEFINES += SFLASH_SUPPORT_MICRON_PARTS

Debugging Notes:

• Please check for DEBUG_PRINT macro in 43xxx_Wi-Fi/apps/waf/sflash_write/sflash_write.c. Once you enable this macro, you should be able to see debug prints in the UART terminal where you should look for SFLASH ID and SFLASH size. If the support is correctly added, these two fields will show you the correct SFLASH ID and the size that you have added following the above mentioned steps.

          SFLASH Device ID ( 0x20ba18)
     SFLASH Size      ( 0x1000000)

• The micron flash (N25Q128A) I have added in this example needed a 100k pull up resistor in the RESET pin as specified by the datasheet. Please check similar things in the datasheet of the flash you plan to add.
• This blog post does not cover the porting effort of flash from a different manufacturer, in which case, you have to add the read, write, erase source code in the spi_flash.c for which you can refer to the already existing implementations.

The BCM2073x chip (SoC) has 40 logical GPIOs (P0-P39).

The GPIOs themselves are broken out into three separate ports (meaningful when you start programming):

• P0 through P15 on port0

• P16 through P31 on port1

• P32 through P39 on port2

The 32 pin package (i.e. the SoC - BCM20736 and BCM20737 *without* the S) only brings out 14 of the 40 logical GPIOs. The System in Package/SIP (the BCM20736S and BCM20737S modules) follows the SoC closely with regards to which pins are brought out (but there is a slight difference) and these are what you see in the SIP module datasheets.

Since the 32 pin package (SoC) and the modules are pin-limited, some of the logical GPIOs within the SoC are multi-bonded before bringing them out on the balls on the chip.

For the 32 pin package, the following pins are bonded in this manner:

• P8 and P33 (only one of two is available)
• P11 and P27 (only one of two is available)
• P12 and P26 (only one of two is available)
• P13 and P28 (only one of two is available)
• P14 and P38 (only one of two is available)

Very Important Note: The SOC packaged part described above is not used for the SIP module. The SIP uses the raw die and wirebonds it differently than the DFN part, so the IOs described above for the SoC are not bonded together from the die - they are bonded together on the DFN wirebond package.

Always refer to the BCM20737S Bluetooth Low Energy SiP Module Technical Reference for the bonding/alternate function information relevant to the SIP modules, not the BCM20737 SOC Data Sheet.

When leveraging the WICED™ Smart Hardware Interfaces for your development, you will run across several GPIO mapping tables in the document that look like this one:

Note here that you can use only one of the GPIOs (noted in black) from each of the vertical rows above.  This is what is referenced in the WICED™ Smart Hardware Interfaces as a "group" (all signals must be selected from the same group, which is essentially the table).

All options may not be available in the package used within the SIP module (shown in red). Combinations shown in red text are also not generally available on the BCM20732 TAG. Additional options may be unavailable if they are being used for the peripheral UART interface.

All GPIOs support programmable pull-up and pull-down resistors, along with a 2 mA drive strength except P26, P27, and P28, which provide a 16 mA drive strength at 3.3V supply (this will change as the supply drops and the GPIO pins will sink less current).

The GPIOs are all capable of waking the device from sleep or deep sleep and the application can configure interrupts (both/either edges, level), pull-up/pull-down High-Z, etc.

The following GPIOs are available on the BCM2073XS based SIP Modules (remember, only 14 are brought out on the SIP module):

• P8/P33 (Dual bonded, only one of two is available)
  Change per information received on 4/28/15: our packaging facility confirmed that P8 and P33 are both available and that on the SIP they are not dual-bonded
• P13/P28 (Dual bonded, only one of two is available)
• P14/P38 (Dual bonded, only one of two is available)
• P12/P26 (Dual bonded, only one of two is available)
  Change per information received on 4/28/15: our packaging facility confirmed that P12 and P26 are both available and that on the SIP they are not dual-bonded
  - P12 if not used as P26 or external 32KHz LPO; If used as 32KHz LPO, then P12 and P26 are unavailable
  - If external 32KHz OSC is used then P12 is not available, but P26 is available
• P11/P27 (Dual bonded, only one of two is available)
  -P11 if not used as P27 or external 32KHz LPO; If used as 32KHz LPO, then P11 and P27 are unavailable
  - If external 32KHz OSC is used then P11 is not available, but P27 is available

For unused dual bonded pins, the unused GPIO should be input/output disabled (especially when it is an input).

From the perspective of writing software against the GPIO mappings defined above, it's important to keep in mind that the GPIO is physically mapped to a BCM2073XS device within the platform.h file which is custom to the TAG development board by default.

However, this mapping in platform.h can be reconfigured for a custom design.

The values in platform.h then map to definitions and function prototypes in bleprofile.h

Note that the specific values in the bleprofile.h bitmasks themselves are not intended to be exposed as the code beneath these bitmasks is proprietary and cannot be released for reasons outside the scope of this discussion.

In addition to reconfiguring the mappings of your custom board within the bleprofile.h, GPIO can also be assigned within BLE_PROFILE_GPIO_CFG within the .c file for each application. This is also where you allocate/initialize the GPIO within your application.  The bleprofile_xxx() routines are then how you use/access what you have configured above.

With this said, I realize there is some ambiguity in this message as we have documents like WICED™ Smart Hardware Interfaces which clearly states that the BCM2073X (note that this guide was written for the SoC, then modified slightly for the SIP module) includes two sets of APIs that are available for the application: the low-level driver API and the high-level profile API.

So yes, the Low Level API is there and in some cases ok to use, but we are not consistent in exposing everything a developer needs to actually use it effectively on a consistent basis.

Hopefully you guys find this helpful.  I know many of you have tidbits to add, so feel free to comment (please stay on topic). I would love to see some examples and code snippets showing usage of the bleprofile_xxx() routines.

The attached app shows sample usage of the ADC hardware built into the 36/37/s chips.

To use the app, load it onto a Tag board that has a push button on P0. Run traces on the board. You'll initially see ~0V, and when you press the button you'll see the applied voltage on the voltage rail (~3300mV).

There are three necessary steps to get the ADC running, as seen in the app:

     Import:

     #include "adc.h"

     Instantiate in create function:

     adc_config();

     And poll the ADC using the function:

          adc_readVoltage(adc_convertGPIOtoADCInput(gpio_number));

*Calibration occurs within the initialization function. However, it may be useful to your application to calibrate the ADC to an external voltage for added assurance, or to do so periodically throughout the run-time of your application. To do so, call the function below: parameter one is the known voltage of the reference source in mV, and parameter two is the location of the reference voltage. The location can be configured to many different buses and all GPIOs (for external sources). Control click the second parameter within the source code to see a complete list of the locations that can be utilized as a reference voltage.

     adc_adcCalibrate(2000, ADC_INPUT_VDDIO);

The output of the polling function is in mV.

jakewtorres

More info on the ADC:

     BCM20732S ADC Configuration

     BCM20737S - ADC Noise-free resolution

     Questions related to the ADC implementation on the BCM2073XS...

     BCM20737 ADC DMA or Interrupt Service Routine

                                   

• Code Overview
  
  • iBeacon and SDK 2.1 Code Overview
  • WICED Smart BCM2073X Coding Tips from user maxsong...
  • WICED Smart Training videos, compliments of Macnica North America...
  • BCM92073X BLE Profile Configuration

• General Questions
  
  • BCM20732 questions
  • How to get started (coming from arduino)
  • What is difference between being connected versus paired?
  • Wiced Smart Software Runtime -- Lots of Questions
  • About BCM20737S
  • BCM20737s: NFC Reader or only TAG?

• Hardware Design between 2073X and External MCU

• Reference Design/Schematics
  
  • New iBeacon BCM20737 Reference Design
  • Experts Interview Video: Michael L. - IBCN BCM20737 Schematic Review
  • BCM20737TAG Board - Gerbers and Schematics

• Layout
  
  • BCM20732 layout options
  • BCM20737S input capacitors and placement
  • BCM20732S layout
  • Are pullup resistors always needed on 20732 SCL and SCA pins?
  • Exact Location of internal PIFA Antenna on BCM20737S
  • 20732S XTAL (32KHz)

• General
  
  • WICED Smart Video BLOG: SDK 2.1 Smart Designer Tool Walk-Thru
  • WICED Smart BCM92073X GATT DB Operation
  • Lots of questions.. L2CAP/GATT/GAP, etc
  • Multiple Notifications in an App...?
  • Support for very large characteristics

• Other
  • How to change the GATT database after init (bleapp_set_cfg) ?
  • Is pairing/encryption mandatory to allow a peer to write in GATT

• Advertising
  
  • Customizing Advertising on WICED Smart
  • Best way to rewrite advertisement data
  • Connectable vs. nonconnectable Advertisements.
  • How to change advertisement interval after init?
  • Advertising during connection
  • bleprofile_notifyAdvPacketTransmissions doesn't work.

• Callback to modify single advertisments?
• About the bleprofile_GenerateScanRspData function?
• How to register callback for ADV events ?

• Scanning
  
  • Scan sometimes stops working
  • Scheduling of scan window and connection window

• Additional master/slave questions on BCM20736/7 family
• Re: How best to implement bulk data transport
• smp_bond_result 04
• Connection Event Callback API
• Connection Event Callback API (follow-on)
• Connection Interval and Connection Slave Latency
• When does bleprofile_sendNotification() actually send?
• Check if bleprofile_sendNotification() was successful
• Slow reconnection
• Sometimes connection not bonding

• Adding and removing master nodes to a whitelist running on a peripheral device

• General
  
  • BCM2073XS GPIO Basics
  • Can someone tutor me on GPIO usage?
  • GPIO Headers
  • BCM20732S PIN information
  • BCM2073xS (BCM20737S) GPIO bonding

• Interrupts
  • Access_tag_interrupt_handler
  • How to identify GPIO interrupt source pin?
  • Buttons in hello_sensor.c
  • How can I wake BCM20737S up by using GPIO interrupt?
  • How to disable interrupt?
  • GPIO in high impedance mode
  • Wake up on GPIO interrupt

• General
  
  • Information: Debug the BCM20732 Tag over HCI-UART using a COM port via USB on the PC
  • How to debug the board step by step?
  • Information: BCM20732S debug/trace capabilities through the HCI UART port
  • How do I interpret the extra tracing data ?
  • Testing Master and Slave Roles
  • How can I use ble_trace() for application debug?
  • How to get debug traces ?
  • WICED Sense debug with UART
  • How to disable 20737S SDK trace, BLE_TRACE_DISABLE?

• J-Link
  • WICED Smart J-Link Debugger
  • WICED Smart - Debugging Support Using a J-Link Probe Application Note

• BCM92073X TAG Power Supply Configurations
• Power level granularity in blecm_setTxPowerInConnection() and blecm_setTxPowerInADV()
• Current Draw and Advertising Timing on the WICED Sense (BCM20737S)
• how to reduce the power consumption when use puart ?
• BCM20737S Current Consumption Voltage Condition and more...
• [BC20636S] Power consumption advantages when using external oscillator

• BLE RF Testing Specification Introduction
• BLE RF Testing Setup Procedures

• General
  
  • WICED Smart Video BLOG: Experts Interview - Sleep Deep_Sleep and Advertising
  • Sleep Deep_Sleep Explanation and Techniques
  • WICED Smart Sleep/Deep-Sleep Explanation and Techniques Design Guide
  • BCM20736S Sleep Example Firmware
  • Questions sleep and deep sleep modes on BCM20737
  • GPIO Interrupt State after Deep Sleep

• Entering Sleep
  
  • How to enter HIDOFF?  How to detect if the request is not honored?
  • Putting '20732S into sleep or deep sleep mode
  • BCM20736S HIDOFF problem
  • Problem with sleep mode
  • Sleep Mode on 20736S

• Waking From Sleep
  • Boot Time of WICED Smart Tag Board (BCM20737)
  • GPIO state in deep sleep
  • For wake on GPIO interrupts, please look under GPIO->Interrupt
    

• WICED™ Smart Hardware Interfaces
• BCM20736S I2C, PUART and SPI comms
• SPI1 access or send command to flash in application level.

• Memory:
  • BCM20732 Memory Map Architecture
  • BCM92073X TAG Memory and Programming Configurations
  • WICED Smart BCM92073X I2C EEPROM Emulation Porting Guide
  • WICED Smart BCM92073X EEPROM and SFLASH Layout
  • WICED Smart BCM92073X NVRAM Access
  • Memory size limits on 20732?
  • BCM20732S NVRAM Size
  • nvram: number of locations to write to
  • BCM20736S I2C, PUART and SPI comms
  • It seems that I can not read the data is stored in NVRAM before the last power off.
  • Layout of VS1 in the EEPROM
  • Re: Accessing the 512 kb (64 kB) EEPROM in the 20737S module

• PWM:
  • LED with PWM
  • Different Frequencies for PWM
  • How many PWM channels available in BCM20732S ?
  • BCM92073x periodic interrupt rate
  • How to turn on LED

• ADC:
  • BCM20732S ADC Configuration
  • Questions related to the ADC implementation on the BCM2073XS...
  • ADC on BCM20732

• UART:
  • Information: Programming your BCM20732S-based board from an onboard UART header
  • UART does not receive
  • UART Routines
  • BCM20732S based boards sometimes develop UART failure
  • Spec for uploading firmware to the BCM20732S via HCI UART?
  • puart_write() crashing on BCM20736?
  • Peripheral UART missing bytes
  • Problem with UART watermarks
  • PUART RTS/CTS Hardware Flow Control
  • What are the PUART FIFO Rx interrupt threshold settings?
  • Need clarification on PUART RTS/CTS flow control support

• I2C:
  • I2C Discussion
  • BCM20736S recovery problem - SDA high does not enter recovery mode
  • How can I use i2c in BCM20737S?

• SPI:
  • SPI on BCM920732TAG
  • Spi Debug
  • SPI flow control

• Timer in 2073x
• BCM20737S Timer Module

• Software/Usage
  
  • appFineTimer
  • FineTimer
  • What is the best way to set an application timer to fire?
  • how to config RTC use external 32.768?
  • Re: How to use real time tick clock?
  • rtc_sample bricks our BCM20736S-based board
  • Turning off the timers in BCM20736S
  • Hello_client/blecen Timer Callback Questions

• Watchdog Timer
  • How can I get bcm20732s reset reason?
  • Increasing/Disabling the watchdog timer

• Crystal
  • Explanation of Crystal Warmup Issue
  • Crystal warm-up work-around video...
  • 32kHz Crystal Spec?
  • Internal vs. External Oscillator

• RTC
  • rtc_RtcTime2Sec() returns wrong seconds when RtcTime.year is 2016
  • How to use real time tick clock?
  • rtc_sample bricks our BCM20736S-based board
  • how to config RTC use external 32.768?

• Watchdog Timer
  • Increasing/Disabling the watchdog timer
  • How can I get bcm20732s reset reason?

• Hardware Timer
  • How to use 100us interval timer?
  • Hardware Timer (hw_timer.h) usage
  • HW Timer in 2073x
  • Timer in 2073x
  • Wiced Sense hardware timer example
  • Wiced Sense hardware timer example (part 2)

• WICED Smart BCM92073X OTA Firmware Upgrade (1)
• WICED Smart BCM92073X OTA Firmware Upgrade (2)
• How to do OTA: Step by Step with PDF
• SOTAFU for Android and iOS
• Why error occur when I open WsOtaUpgrade.exe?
• Why error occur when I open WsOtaUpgrade.exe? (continued)
• Issue with using Windows OTA upgrade app

• How to recover BCM20736S on custom board?

Security:

• Encryption API
• How to operate RSA in BCM20737S & BCM20737S document
• Update on RSA and/or app note for BCM20737?
• BCM20736S and RSA
• RSA Document
• BCM20737S: LE security mode1 level3/4 supported?

• Programming manufacturing data during production
• Do I need to register separately with the Bluetooth SIG to use the Bluetooth logo in my product?

• BD_ADDR - how do you get one?
• BD_ADDR: Changing BCM20737 Board Address for Production
• Changing BD_ADDR from the application
• Video Link : 1216

• Programming the TAG2/TAG3 Board using command line tools
• BCM20732S refuses to program
• cgs.exe and ChipLoad.exe

• WICED Smart BCM92073X Generate Your Own UUID

• Broadcom BCM20732S/BCM20736S/BCM20737S Regulatory Approvals
• Certification from Bluetooth SIG
• 20732S regulatory certification
• More questions regarding FCC certification on the BCM2073XS Product
• FCC Certification Flow for Broadcom module products
• FCC approval for BCM20736S

The WICED host CPU's ADC port can be setup to read ADC data and send it to a remote host or client.

The App_temp_control application (temp_control) located in .../apps/demo/temp_control demonstrates  ADC setup and reading. This application sends temperature data (ADC data) to remote host (www.xively.com). The same data is served by the http server running on the WICED module and sent to http clients.  This is a comprehensive sample application with many rich features.

The attached sample application sets up the ADC using only WICED APIs and reads the ADC data then prints the read ADC value on the serial terminal.

The new adc_setup_read  snip application is located in …/apps/snip/adc_setup_read. Patch file updates the …/apps/snip/ directory with adc_setup_read application files.

In order to run this snip application on the BCM43341WCD1 platform platform.c and platform.h files needs to be updated. Attached patch file contains the needed changes.

Use the following Make Target commands to build the ADCSetupReadApp application.

For BCM943362WCD4 platform:

     snip.adc_setup_read-BCM943362WCD4 download run

For BCM943341WCD1 platform:

     snip.adc_setup_read-BCM943341WCD1 download run

The ADC values are printed on the serial terminal.