By default the LwIP standard debug prints are disabled to save memory and re-use the same for other parts of application threads. But in-case, you need to enable the standard debug prints in LwIP stack, which is done by LWIP_DEBUGF, you need to follow the steps mentioned below.

lwipopts for WICED SDK can be found in 43xxx_Wi-Fi/WICED/network/LwIP/WWD/FreeRTOS/lwipopts.h. If you are on a DEBUG build (specified by -debug in the make target), WICED_LWIP_DEBUG macro will be enabled, but the prints are still disabled by default.

A standard snip example is considered to demonstrate the how-to operation for a DEBUG build.

1. Make Target: snip.tcp_client-<platform_name>-FreeRTOS-LwIP-debug download

    2. Switch the LWIP_DBG_TYPES_ON to LWIP_DBG_ON

    3. To enable specific debug messages in LWIP, just set the specific define value for the *_DEBUG value to " LWIP_DBG_ON". A comprehensive list of debug                          defines that can be enabled usually found in the 43xxx_Wi-Fi/WICED/network/LwIP/ver2.0.3/src/include/lwip/opt.h file. You need to copy the defines          for the  debug messages you want to enable into the lwipopts.h file and enable them there. As an example, I have switched the following on in my lwipopts.h file

#define TCP_DEBUG                       LWIP_DBG_ON
#define ETHARP_DEBUG                    LWIP_DBG_ON
#define PBUF_DEBUG                      LWIP_DBG_ON
#define IP_DEBUG                        LWIP_DBG_ON
#define TCPIP_DEBUG                     LWIP_DBG_ON
#define DHCP_DEBUG                      LWIP_DBG_ON
#define UDP_DEBUG                       LWIP_DBG_ON

Attached is the modified lwipopts.h file and and the uart terminal print. Please note that enabling debug prints can add extra size (approximately 20 kB for the mentioned settings) to the code. It will also slow down performance of the LwIP code due to required run-time checks and output. It's is recommended to enable debug support only if there is no chance of attaching an external debugger to the target platform and step through the code.

• SUMMARY:

  We divide the SDK code into different module or library for specific function, and Hierarchical software design also is useful for the code maintenance. This blog is to show the log setting for different module.  Please see below architecture from SDK release document. Our aim is to print useful logs when issue happens,  upload one module picture from SDK release .

• HOW TO Print LOGS：

1. To use “printf” directly, this is very convenient for the debug, but not easy to make a good management for the logs added. Some basic knowledge of print is in this link：

https://fresh2refresh.com/c-programming/c-printf-and-scanf/

     #include <stdio.h>

     int main()

     {

        char ch = 'A';

        char str[20] = "fresh2refresh.com";

        float flt = 10.234;

        int no = 150;

        double dbl = 20.123456;                         

        printf("Character is %c \n", ch);

        printf("String is %s \n" , str);

        printf("Float value is %f \n", flt);

        printf("Integer value is %d\n" , no);

        printf("Double value is %lf \n", dbl);

        printf("Octal value is %o \n", no);

        printf("Hexadecimal value is %x \n", no);

        return 0;

     }

·    %d got replaced by value of an integer variable  (no),

·       %c got replaced by value of a character variable  (ch),

·       %f got replaced by value of a float variable  (flt),

·       %lf got replaced by value of a double variable  (dbl),

·       %s got replaced by value of a string variable  (str),

·       %o got replaced by a octal value corresponding to integer variable  (no),

·       %x got replaced by a hexadecimal value corresponding to integer variable

·       \n got replaced by a newline.

2.     In wwd_debug.h, wwd_debug.c , wiced_defaults.h

We defined Macros to control the log output for different MODULE.

Modules are Application, library, Webserver , Network, RTOS,

Security , WPS, Supplicant, Wiced , WWD(Wiced wi-fi Driver) .

We have good instructions and warnings for the log setting:

* ** WARNING for PRINTING **

*  If printing is enabled, the stack of each thread that uses printing

* must be increased to at least 4 kBytes since the printf function uses

*  a lot of memory (including dynamic memory)

/* Select which group of functions are allowed to print */

/* WPRINT_ENABLE_<MODULE>_ERROR - Enable print messages in the respective <MODULE> that are present

* as WPRINT_<MODULE>_ERROR.

* For instance, if WPRINT_ENABLE_WWD_ERROR is enabled, then trace messages that are under

* WPRINT_WWD_ERROR will be printed. This directive shall also result in an ASSERT if the target is built in DEBUG                                 mode.

* WPRINT_ENABLE_<MODULE>_DEBUG - Enable print messages in the respective module that are present as

* WPRINT_<MODULE>_DEBUG.

* For instance, if WPRINT_ENABLE_WWD_DEBUG is enabled, then trace messages that are under

* WPRINT_WWD_DEBUG will be printed.

* WPRINT_ENABLE_<MODULE>_INFO - Enable print messages in the respective module that are present as

* WPRINT_<MODULE>_INFO.

* For instance, if WPRINT_ENABLE_WWD_INFO is enabled, then trace messages that are under

* WPRINT_WWD_INFO will be printed.

If you disable all the logs, there will have a compiled error, so please keep this one at least:

#define WPRINT_ENABLE_APP_INFO           /* Application prints */

So general debug sequence for log enable:

• Enable WPRINT_ENABLE_MODULE_INFO to track the process.
• If found an error was printed out, check which module , then enable DEBUG and ERROR mode also. Be noted, Debug compile will go to an assert if enable ERROR layer .
• Find the bug position , add more debug info by using the same level log print.

I think if you want to manage the log clearly , you can define one MACRO to just add your debug info ,like           #define WPRINT_ENABLE_BUG_DEBUG_INFO , after issue is fixed you can disable it .Another log print mode :

3.     Wiced_log_setting, it is often used on application area.

If you want to close the log , please change the log to WICED_LOG_OFF, the logs added in      the application will be disabled. And strongly suggest to use this debug info in application debug stage.

Log initialize at application_start and enum structure.

         wiced_log_init(WICED_LOG_INFO, render_log_output, wiced_time_get_time);

         wiced_log_msg(WLF_DEF, WICED_LOG_NOTICE, "wiced logging system is initialized\n");

typedef enum

{

    WICED_LOG_OFF = 0,

    WICED_LOG_ERR,

    WICED_LOG_WARNING,

    WICED_LOG_NOTICE,

    WICED_LOG_INFO,

    WICED_LOG_DEBUG0,

    WICED_LOG_DEBUG1,

    WICED_LOG_DEBUG2,

    WICED_LOG_DEBUG3,

    WICED_LOG_DEBUG4,

    WICED_LOG_PRINTF, /* Identifies log messages generated by wiced_log_printf calls */

    WICED_LOG_MAX

} WICED_LOG_LEVEL_T;

b: How to write to STDOUT .

use this function:

Enable time output with log together.

Summary:

     The difference between Signal mode and Direct mode is: we only need to connect the EVB with the test AP created by AP, then AP will have a menu to test TX and RX related. Its aim is to figure out if the actual running power is matching what you want, RX path has no RF de-sense in a normal running mode.   If signal mode passed all the RF standard, we can have a confidence that current RF path include TX and RX, current RF configuration like NVRAM have no critical issues.  We can move the product into next long-run function tests.

• Which EVB is for the tests?

I choose 43340 because it has 2.4G and 5G together.

• How to set 8860C before test.

       1. Set the static IP address

    2.  configuration .

Which means creating a AP at 153 channel with 6M rate and power is -15dbm.

After AP created we use command to join the AP, then we can do the test .

• Which application is needed for the tests?

I used the command console for the test because we can use a lot of embedded commands to join a specific AP and do some command input. 

And we are using the normal firmware for the test, please see the command output.

         test.console-BCM943340WCD1 download run

• Which commands are needed before the tests?

After connection established “scan_suppress 1” , “roam_disable ” are preferred .

PM = 0 is good to be set also.

In command console:

Usage: scan_disable <1 = disable scan|0 = enable scan>

> scan_disable 1

If you didn’t have this command, please add it according another blog.

• How to change country for a test ?

Please input “set country ”, then get channel , choose one channel to do connection with the AP created by instrument.

     > get_country

         Country is US (US/0)

     > set_country CN/0

     > get_country

         Country is CN (CN/0)

     > get_channels

          1  2  3 4  5  6  7  8 9  10  11 12  13  149 153  157  161 165  >

• TX test results

This blog post shows how to use macros in WICED to debug TLS (Transport Layer Security) data. The mbedTLS library provides debug macros MBEDTLS_DEBUG_C, MBEDTLS_SSL_DEBUG_ALL and MBEDTLS_DEBUG_LOG_LEVEL defined in /WICED/security/BESL/mbedtls_open/include/mbedtls/config.h and they are disabled by default. You can enable those macros and define MBEDTLS_DEBUG_LOG_LEVEL as per the level of debugging required. Higher the level, more details can be captured in the logs. The log levels are defined as shown below:

0 No debug

1 Error

2 State change

3 Informational

4 Verbose

In addition, you also need to enable WPRINT_ENABLE_SECURITY_DEBUG in /include/wiced_defaults.h. Please note that debug printing consumes a lot of memory so you need to allocate at least 4 kB to the stack of every thread that uses debug printing.

How to debug non-responsive customer based hardware

So, you've got your custom hardware back from the build facility.  It's populated with one of those sexy Broadcom Bluetooth devices.  An exuberant crowd of managers and team leaders is milling about the lab, watching with anticipation as you attach the power source.  The gleeful moment arrives, and you flip the switch to ON -- Viola!  ...  Nothing happens.  Nada.  Zip. Nilch.   Maybe you had expected the board's LED to start pulsing indicating the application firmware (pre-programmed into the non-volatile memory) is running.   You did pre-program the EEPROM/SFLASH right?   Maybe you're just happy there was no smoke, popping sounds, or the acrid smell of "burnt Roast Beef" when the design is bad, or assembled using wrong/misplaced component(s).  With a "pat on the back" and some encouraging words, management slinks-away to perform whatever their job function is; leaving you scratching your head and saying "Huh?".  You reach for the schematics and an oscilloscope probe...    Now what do you do?

Before you post a help request on the Community Forum (Bluetooth Forums​), please consider some of the fundamental steps Broadcom recommends you try first.

We remind the reader there are three topologies in which Broadcom devices can operate which may impact how to debug the design:

1. Chip on Board or System On a Chip (COB and SOC terms can be used interchangeably) - SOC designs use discreet components and are often very similar to Broadcom's TAG3 or TAG4 evaluation boards.  In SOC designs, the (integrated) Broadcom radio and MCU is populated as one-component with additional circuitry added around it, such as the EEPROM, ferrite beads, capacitors/resistors, antenna, and (optional) 32KHz crystal.  Broadcom's Bluetooth SOC device stenciling (part number markings) DO NOT end with the letter S, L, or an E  and come in a 32pin QFN package.  SOC designs are perhaps easiest to debug because you can get a scope probe on virtually everything that can go wrong.  Note: Devices stenciled with an S, L, or an E are covered next under the SIP topology.
2. System In Package (aka SIP) - a SIP offers the majority of the necessary components all-in-one package, including the antenna.  They come with (Limited Module) FCC/UL/CE pre-certifications resulting in your company only needing to perform Spurious Emissions testing.  Certifications can save hundreds of thousands of dollars, not to mention time to market and testing hassles. Some customer designs consist of only the Broadcom SIP and a battery!   Presently, three flavors of the SIP are available and offer different features depending on the requirements (power, size, RF expertise, etc). These part numbers end with an S, L, or an E and come in a 49pin LGA package.   SIPs are rarely defective, so debugging them is usually a function of getting the on-board 64k-byte EEPROM programmed with the users application.
3. Modules - Broadcom's Partners offer world-class products and services!  Our partners offer everything from device procurement, design services, Broadcom SDK Abstraction, FCC/UL/CE certified modules, to mass production and plastics up to and including Cloud Services. If you're reading this debug Blog, chances are you are not using one of our partner's devices/services because it would already be working for you.

Debugging hardware is easier when able to perform A<->B comparison tests/measurements against a known-good design.    You can purchase a  Broadcom TAG3/TAG4/WICED-Sense evaluation board, or evaluation boards from Broadcom's partners (Partners) at this link:  Purchase a WICED Bluetooth Development Kit

Documentation for the TAG3/TAG4 (COB/SOC) eval boards, and SOC/SIP Technical Reference Manuals are found here: WICED Bluetooth Documents & Downloads​. 

While debugging, you must have access to these pins (at a minimum):   VCC/VDD/VIN, HCI_UART_TX, GND, HCI_UART_RX, RESET_N

During debug/initial programming of the NVRAM, it's strongly advised to use a USB<->RS232 serial cable (one option is model #TTL-232RG-VREG3V3-WE found here: Programming the TAG2/TAG3 Board using command line tools).

Debug steps:

1. Visual Inspection for Mechanical / Assembly problems - Grab your magnifying glass and meticulously inspect both sides of the printed circuit board (PCB). Does anything look bent, damaged, or out of place?  Are there any solder bridges, or open-connections on the fine-pitch (device) pins?   Does anything look like it has experienced high-heating duress?  Are their any cracks in the PCB?
2. 'Buzz Out' (use a Volt-Ohm meter to make resistance and continuity measurements of) the Power and Ground Rails going to each device and component that touches them.   Measure resistor values for for each resistor shown on the schematics.  Verify any diodes or resistors in the design are installed in the correct direction.
3. Verify VCC/VDD is 3.3volts.
4. Measure the amount of power the board is consuming.  Does it seem excessive, or too small?   Are any of the components hot-to-the-touch?
5. Confirm the timing of the RESET signal going to the BCM2073XX meets the timing requirements. Confirm the device is not being held in RESET which would happens when RESET_N pin is held low.
6. There are two UARTs on the device.  HCI_UART is used for programming NVRAM, and PUART is available for the users application. Upon powerup, the BCM2073XX device ROMCODE senses the HCI_UART_RXD pin to ascertain if it should enter programming mode.  If asserted HIGH, the device enters programming mode. If low, it reads a small chunk of NVRAM contents. One good way to test if the on-board ARM is running romcode is to hold HCI_UART_RXD high during the RESET pulse to force it into programming mode.  Then, execute the ~WICED-Smart-SDK/Tools/mbt/MBT.EXE utility(within the SDK) with the "reset COMxx" parameters to verify HCI Commands/Responses are working.    It is very important to get this to succeed as it confirms there are no electrical or mechanical issues causing the problem(s), and that the embedded ARM controller is indeed running firmware.
7. If MBT.EXE does not successfully run, Inspect the following areas:
   • Either chip on board design, or module/SIP designs:
     1. If your design has a 2nd microcontroller in place, verify the UART interface signals are not reversed.  In fact, you might want to isolate the Broadcom chip (cut the traces to the host MCU) to assist getting MBT.EXE to function, or to aid in programming the NVRAM with the SDK.
   • Chip on Board designs (BCM2073X):
     1. Ensure the voltage levels for LDOIN/LDOOUT/VDDVCO/VDDPLL match those found on the Broadcom Evaluation Board.
     2. Ensure the 24MHz crystal running.
     3. Ensure TMC is asserted low.
     4. Monitor the Serial Flash/EEPROM's SDA and SCL pins after the RESET is de-asserted on the BCM2073X. You should see bus activity for a short period of time as the internal ARM MCU comes out of reset (ROMCODE tries to load the application firmware from NVRAM).  Make sure you have pullup resistors on these pins.
     5. If the NVRAM has a known-good application image in it, ensure the HCI_UART_RXD pin of the 2073XX is asserted Low during powerup.
   • Module/SiP designs (BCM2073XS, BCM2073XL, BCM2073XE):
1. These designs are difficult to debug because access to the crystal and NVRAM pins are not accessable from outside the package.
2. Spend your entire effort getting Step #6 (execution of MBT.exe) functioning to ensure the issue is not a mechanical/electrical one.
3. Consider NVRAM pre-programming services from Avnet to ensure the module has a known-good application programmed prior to board manufacturing.
8. After getting MBT.EXE working, your next step is to program the NVRAM with your custom application, or a sample application from the SDK.  Refer to Programming the TAG2/TAG3 Board using command line tools\

If you find an error within this Blog, or have ideas on how to improve it, please send a Private Message to my In-Box so I can incorporate your recommendations.

Please do not post comments on this blog.

                                   

• 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

WICED Smart J-Link Debugger

The WICED Smart J-Link Debugger is a Software debugger combined with Segger J-Link Debug Probe.

1. The J-Link Debug Probe is shown below and the link is located here: SEGGER - The Embedded Experts

Figure 1: J-Link Segger Debugger

2.  Schematic of cable adapter to the J-Link 20 Pin connector:

Figure 2: J-Link Segger Debugger Interface Connector

3.  Shown below is the connection to the BCM20737TAG_Q2 Board:

Figure 3: J-Link Connection to BCM20737TAG_Q2 Board

4.  The Smart Designer J-Link setup procedure:

1. Start SDK

2. Connect USB to Top Port PC
3. BCM20737TAG_Q2 Board Switch configuration for programming:

Figure 4: Boot ROM, Reset and Switch Buttons

1. Please refer to the Quick Start Guide: http://community.broadcom.com/docs/DOC-1602

1. Configuration for Push Button Switches
   1. BOOT ROM Push Button
   2. RESET Button
2. Push Button Sequence:
   1. Press and Hold BOOT ROM Button
   2. Press and Hold RESET Button
   3. Release RESET Button
   4. Release BOOT ROM Button
3. SDK Commands
   1. Run Clean
   2. Run PWM-Tones App
4. Run Debugger:
   1. Remove USB and Insert Battery
   2. Return Switches to opposite program
   3. Connect J-Link USB Connector to PC
   4. Connect J-Link to Board - See Figure 3 above.
   5. Push Reset
   6. Run GDB Server
   7. Click OK – Observer 2 Green Lights
   8. Click Bug Icon in SDK (Top Middle Section)
   9. Click “I” Icon (Under Navigate Menu) – Instruction Mode

   Click “I” once then press F5 3 times.

Note: R3 (the 10K pulldown on RXd) must be removed for the debugger to work.

Please let us know if you have any issues.

Thanks

JT

This blog is about basic debug information and configuration details for OS X on WICED SDK 2.4.1

The video shows very basic debug details

Video Link : 1133

Before debugging always run 'Clean' from the 'Make Target' Window and not eclipse-->build-->clean

Debug Configuration on WICED SDK (2.4.1)

1) Main configuration tab

2) Debugger Tab (Make sure the 'Force thread list update on suspend' is unchecked)

3) Startup tab

4)Source tab

5) Common tab

HTH

vik86

This was taken from a previous discussion started by jasonrc with input from frankf and tek  thank you for the input...

Having trouble capturing packets to debug your application?  Here are some  tools to use: 

We recommend using a USB wireless sniffer from one of the following vendors.

AirPCAP Nx -- works with Wireshark

Good, well-priced, easy-to-use network network analyser

http://www.riverbed.com/us/products/cascade/wireshark_enhancements/airpcap.php

http://www.wireshark.org   [Win32 v1.4.14 is stable and works well]

All versions downloadable here: http://wiresharkdownloads.riverbed.com/wireshark/win32/all-versions/

Omnipeek

Full featured network analyser

http://www.wildpackets.com/products/network_analysis_and_monitoring/omnipeek_network_analyzer

AirMagnet

Full featured network analyser

http://www.flukenetworks.com/enterprise-network/wlan-security-and-analysis

Microsoft Network Monitor 3

A free tool which uses the Wi-Fi card in the laptop/PC. 

http://support.microsoft.com/kb/933741

For doing analysis of the RF/WiFi environment, the following tools are useful:

WiSpy - PC dongle to do 2.4GHz and 5GHz spectrum capture.  Can show 802.11 and non-802.11 interference.

http://www.metageek.net/products/wi-spy/

inSSIDer - Free scanning tool to show other 802.11 networks within range.

http://www.metageek.net/products/inssider/

Basic network scans are also available using the wireless utility in your PC or Mac.

Also for RF/WiFi environments if you have an iPad/iPhone/iPod Touch

WiPry - iPhone/iPad/iPod Touch dongle for 2.4GHz analysis

http://www.oscium.com/products/wipry-combo-spectrum-analyzer-and-dynamic-power-meter

The power meter function is quite handy if you want to make duty cycle measurements or measure actual TX times.

Here is another great tutorial for MACOS users...

http://wlanpros2.project.ihelphosting.com/wp-content/uploads/2013/06/Wireless-Diagnostic-Utility-in-Mac-OS-10.pdf