Smart Bluetooth Forum Discussions

My company is currently having an issues with quite a few of our devices that use the BCM20736s BLE controller. The controller on each device was programmed one time successfully. After we discovered that the radios were not communicating, wireless or UART via traces, we attempted to reprogram the controller and failed.

These devices were programmed via the WICED IDE. The make target used was mistakenly for the 20737 platform instead of the 20736 platform. The crystal warm up time of the 20737 platform was left at the default value of 2800.

I have attempted to recover the radios using the following procedure with no success:

Power off the device

Short SDA to GND

Connect the HCI UART to the PC

Power up the device

Reset the controller for ~3s

Disconnect SDA from GND

Attempt to program by replacing 'download' with 'recover' in the make target. (I've also tried using Chipload.exe using -nodlminidriver)

All of these devices appear to function when made with the 20736 platform with the crystal warm up time set to 5000.

Is there anyway I may be able to salvage these chips?

I purchased BCM92073X_LE_TAG4.  I downloaded the WICED smart SDK and was able to download hello_sensor and communicate with the Windows 10 client example provided in the SDK.  Now I am unable to download anything.  I get the following console output:

20:43:59 **** Build of configuration Release for project WICED-Smart-SDK ****

"C:\\Users\\RothsMark\\Documents\\WICED\\WICED-Smart-SDK-2.2.3\\WICED-Smart-SDK\\make.exe" hello_sensor-BCM920736TAG_Q32 download

Linking target ELF

OK, made elf.

Call to hello_sensor_spar_crt_setup @ 00206195

OK, made C:/Users/RothsMark/Documents/WICED/WICED-Smart-SDK-2.2.3/WICED-Smart-SDK/Wiced-Smart/spar/../../build/hello_sensor-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor-rom-ram-spar.cgs. MD5 sum is:

1180812d92f07aac93b91d5b37fcf8bd *../../build/hello_sensor-BCM920736TAG_Q32-rom-ram-Wiced-release/A_20736A1-hello_sensor-rom-ram-spar.cgs

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

Patches start at                  0x00204568 (RAM address)

Patches end at                    0x00205988 (RAM address)

Application starts at             0x00205554 (RAM address)

Application ends at               0x00206191 (RAM address)

Patch size (including reused RAM)       5152 bytes

Patch size                              4076 bytes

Application size                        3133 bytes

                                      ------

Total RAM footprint                     7209 bytes (7.0kiB)

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

Converting CGS to HEX...

Conversion complete

Creating OTA images...

Conversion complete

OTA image footprint in NV is 9394 bytes

Detecting device...

Device found

Downloading application...

****Download failed - Press the reset button on the device and retry ****

20:44:02 Build Finished (took 3s.137ms)

Pressing what I assume is 'reset', a button labeled 'sw3', has no effect on the problem.

In Windows device mgr I see that connecting the TAG4 board creates 2 COM ports, COM3 and COM4 which are set to 9600 baud.  that seems slow...

Not sure how to debug at this point.  My kit did not contain either a cable or a 'getting started' guide that supposedly come with the board.  But it did work fine but now it fails to download.  If anyone has a soft copy of the 'getting started' guide I would appreciate them sending it to me.

I'm using:

WICED Smart IDE - Eclipse IDE for C/C++ Developers 2.2.3

Version: Juno Service Release 2

Build id: 20130225-0426

hello,

I download application of SDK 4.0 by WICED Client Control to ram.

the error:

but the SDK 1.33 is OK.

I don't what is the difference between the SDK 4.0 and SDK 1.33.

What are the differences between Tag3 and Tag4 eval kits as general purpose standalone Devkit for BCM2073X products?

Hi,

We're using an external 32KB EEPROM to store our code and data. It's almost out of space.

Is it possible to use Internal ROM to store code and data?

Thank you.

Dear community,

I use a BCM20713 in a product. During bluetooth test performed in a shielded chamber with a Bluetooth protocol analyzer I found that in more or less 20% of products there are a spike in the BT modulation in time domain. This noise makes that you are unable to perform the measurement properly. In particular the instrument says me that the packet is incorrect.

In detail, I'm try to performs a transmit test from the DUT to the instrument using EDR BT technology.

the spike seems happens at the transmitter turn-on.

In annex a snapshot of that.

Could you please let me know what can generate this behaviour and how I can try to solve it?

thanks a lot,

BR,

Giordano

Hi,

we are working on the BCM20736 sleep with RTC sample, please see below example.

My question is it seems reset when it goes into deep sleep with wake after 5s. we set the wake time is 5 seconds, the program goes to rtc_sample_create() function again when the timer is out, is it normal?

Also what does the current consumption should be when set it to sleep mode(DEV_LPM_DISC_LOW_POWER_MODES_SLEEP), in our test, it seems the current is more than 3 mA using sleep mode, is it correct?

@

/******************************************************

*               Variables Definitions

******************************************************/

// Following structure defines UART configuration

const BLE_PROFILE_PUART_CFG rtc_sample_puart_cfg =

{

    /*.baudrate   =*/ 115200,

    /*.txpin      =*/ GPIO_PIN_UART_TX,

    /*.rxpin      =*/ GPIO_PIN_UART_RX,

};

/******************************************************

*               Function Definitions

******************************************************/

// Application initialization

APPLICATION_INIT()

{

    bleapp_set_cfg(NULL, 0, NULL, (void *)&rtc_sample_puart_cfg, NULL, rtc_sample_create);

}

// Create the RTC sample.

void rtc_sample_create(void)

{

    RtcTime current_time;

  char buffer[64];

    ble_trace0("rtc_sample_create()\n");

    if (!mia_isResetReasonPor())

    {

    ble_trace0("Waking from deep sleep because the timer went off or a GPIO triggered while waiting for timer to expire.");

    }

    else

    {

    ble_trace0("Not a timed wake.");

    }

    // Always clear interrupts on P39, which is the interrupt pin used by the wake-from-deep-sleep HW block.

    gpio_clearPinInterruptStatus(GPIO_PIN_P39 / GPIO_MAX_NUM_PINS_PER_PORT, GPIO_PIN_P39 % GPIO_MAX_NUM_PINS_PER_PORT);

    blecm_configFlag |= BLECM_DBGUART_LOG;

    bleprofile_Init(bleprofile_p_cfg);

  // If we need to use the external 32K, then configure the reference

  rtcConfig.oscillatorFrequencykHz = RTC_REF_CLOCK_SRC_32KHZ;

  // Since the 32K external LPO is connected tp P10, P11, P12, P26 and P27,

  // input and putput disable all 5 GPIOs.

  gpio_configurePin(0, 10, GPIO_INPUT_DISABLE, 0);

  gpio_configurePin(0, 11, GPIO_INPUT_DISABLE, 0);

  gpio_configurePin(0, 12, GPIO_INPUT_DISABLE, 0);

  gpio_configurePin(1, 10, GPIO_INPUT_DISABLE, 0);

  gpio_configurePin(1, 11, GPIO_INPUT_DISABLE, 0);

    // Initialize the RTC.

    rtc_init();

    memset(buffer, 0x00, sizeof(buffer));

  ble_trace0("Time base is:");

  // RtcTime of 0x00 is the start of RTC time.

    memset(&current_time, 0x00, sizeof(current_time));

  rtc_ctime(&current_time, buffer);

  ble_trace0(buffer);

  // Let year = 2014.

  current_time.year = 2014;

  // Let month = july = 6 (jan = 0)

  current_time.month = 6;

  // Let day = 1st.

  current_time.day = 15;

  // Let current time be 12:00:00 Noon.

  current_time.hour = 12;

  current_time.minute = 00;

  current_time.second = 0x00;

  // If this is a power-on reset, we need to set up the reference time.

  if (mia_isResetReasonPor())

  {

  // Now set the on-chip RTC.

  if(rtc_setRTCTime(&current_time))

  {

  memset(buffer, 0x00, sizeof(buffer));

  ble_trace0("Power-on reset, set current time to:");

  rtc_ctime(&current_time, buffer);

  ble_trace0(buffer);

  }

  else

  {

  ble_trace0("Unable to set time.");

  }

  }

  else

  {

  // Set up the original reference time instead of using 01/01/2010, 00:00:00 as the reference

  // because this is a wake from deep sleep. The HW clock keeps running in deep sleep so when

  // we wake up, the FW needs to know what was used as the original reference time.

  rtc_setReferenceTime(&current_time);

  }

    bleprofile_regTimerCb(rtc_sample_fine_timeout, rtc_sample_timeout);

    bleprofile_StartTimer();

    // Since we have an external 32 KHz LPO, switch to using this during sleep

    // because this will give us a more accurate sleep clock (lower drift than the

    // internal LPO, so the uncertainty window during a receive will be narrower).

    // In general, base sleep current will be lower too.

    // Switching to the external 32K with bleapputils_changeLPOSource without having

    // initialized the RTC, the high-z'ing bonded GPIOs and not having the 32KHz oscillator physically

    // connected to the chip will invoke undefined behavior.

    bleapputils_changeLPOSource(LPO_32KHZ_OSC, FALSE, 250);

    // Trace out number of bytes free.

    ble_trace1("Number of free bytes in RAM: %d",  cfa_mm_MemFreeBytes());

}

// One second timer expired. Read the time from RTC and print.

void rtc_sample_timeout(UINT32 arg)

{

  RtcTime current_time;

  UINT32 seconds_since_time_base;

  char buffer[64];

  tRTC_REAL_TIME_CLOCK raw_clock;

  memset(buffer, 0x00, sizeof(buffer));

  // Get and print current time.

  rtc_getRTCTime(&current_time);

  ble_trace0("Current date/time is:");

  rtc_ctime(&current_time, buffer);

  ble_trace0(buffer);

  // Get and print time since time base in seconds.

  rtc_RtcTime2Sec(&current_time, &seconds_since_time_base);

  ble_trace1("Its been %d seconds since bigbang.", seconds_since_time_base);

  // Get and print the raw 48 bit clock value.

  rtc_getRTCRawClock(&raw_clock);

  ble_trace2("Upper and lower 32 bit values: 0x%08X, 0x%08X\n", raw_clock.reg32map.rtc32[1], raw_clock.reg32map.rtc32[0]);

#ifdef RTC_SAMPLE_ENTER_DEEP_SLEEP_AND_ENABLE_TIMED_WAKE

  {

  static UINT32 num_timeouts_since_boot = 0;

  // Demo going into deep sleep with wake after 5s.

  if (num_timeouts_since_boot++ >= 10)

  {

  // If its been ~10s of ADV, configure timed wake and

  // enter deep sleep right now.

  ble_trace0("Entering deep sleep.");

  gpio_configurePin(0, 0, 0x100, 0);

  // Configure the low power manager to enter deep sleep.

  devLpmConfig.disconnectedLowPowerMode = DEV_LPM_DISC_LOW_POWER_MODES_HID_OFF;

  // Configure the wake time in mS.

  devLpmConfig.wakeFromHidoffInMs = 5000;

  // Configure the reference clock to use.

  // Use the external 32k.

  devLpmConfig.wakeFromHidoffRefClk = HID_OFF_TIMED_WAKE_CLK_SRC_32KHZ;

  gpio_configurePin(0, 0, 0x100, 0);

  // Enter deep-sleep now. Will not return.

  devlpm_enterLowPowerMode();

  }

  }

#endif

}

void rtc_sample_fine_timeout(UINT32 arg)

{

}

Hi all,

we use 20736 to connect sensor, sometimes it disconnected quickly with reason 0x3E when connected, what is the '0x3E' means, after that we did a retry to connect, but unfortunately sometimes can work, sometimes not work, still disconnect. we want to know what is reason will cause.

[10/19/16 10:50:23:236] BTOP: Start Connect(3 1 2 4C55CC142E95)
[10/19/16 10:50:23:231] BLE: -->Rev(6) (F1 01 00 E1 01 03)
[10/19/16 10:50:23:227] BLE: F1 S0 Cmd Success
[10/19/16 10:50:23:224] BLE: E1 scan result(3-High Scan) req(0 0) total(0 2)
[10/19/16 10:50:23:220] BLE: -->Rev(15) (E1 01 00 E4 09 00)
[10/19/16 10:50:23:216] BLE: E1 scan result(0-NO Scan) req(0 0) total(0 2)
[10/19/16 10:50:23:212] BLE: E4 CONNECTED(4C55CC142E95)TP(0)HD(0x41)Role(0)
[10/19/16 10:50:23:207] BLE: MATCH CONNECTED
[10/19/16 10:50:23:114] BLE: -->Rev(5) (E5 03 41 00 3E 00)
[10/19/16 10:50:23:110] BLE: E5 DISCONNECTED:HD(0x41) Reason(0x3E)

Thanks,

Lei