Smart Bluetooth Forum Discussions

I wanted to use BCM92073X_LE_KIT with I2C controlled OLED display and SPI/I2C driven Murata ZPA Series MEMS Barometric Pressure Sensors

Since I need to use two I2C ports in my design (one for OLED and other for pressure sensor) , I just wanted to confirm can I use BCM92073X_LE_KIT to connect two I2C slave devices? Can you please share the BCM92073X_LE_KIT technical reference manual?

Thanks

I want to ask if the SDK provides API so I can encrypt data for transmission.  I know that if the two nodes in the connection mode, I can use standard BLE encryption.  However, I want to ask if there is an encryption API that I can use to encrypt messages in the advertising packets?   Thank you.

Hi

I am running a WICED application with the secure OTA option.

The procedure run as expected, but I think there is some bug in the WsRsaSign utility.

As far as I understand, the utility adds the manufacturer ID and major and minor version number as a header for the image file.

I have found that no matter what i put in the minor version, it saves the major version twice.

for example:

WsRsaSign.exe rsa.pri XXXX_ota-BCM920737TAG_Q32-rom-ram-Wiced-release.ota.bin 1234 1 7

the file header output is:

The need is from this:

We soldered BCM20736S chip on the PCB. The BCM20736S wasn't changed at all after we got it from Broadcom. Then, we downloaded our application code into BCM20736S (as I understand, the code is downloaded into the internal 512k EEPROM) for some testing. Now, we need to do some tests with BCM20736S chip as it condition was as we just got it from Broadcom. We don't have time to get new chips. So we are looking for a way to restore these used BCM20736S to its factory default state in the sense of internal EEPROM.

The chapter "Appendix 😧 Recovering a Corrupt WICED Smart Tag" in <WICED-Smart-QSG202-R> shows the procedure of executing "proximity-BCM920737TAG_Q32 recover UART=COMx". However, BCM20736S loaded the application code 'proximity' after executing such recovery, which is different from its factory default state.

Does anybody know how to restore these used BCM20736S to its factory default state in the sense of internal EEPROM?

I was using the SDK make target examples to build and download the app to the tag3,while some examples cannot convert to hex. I didn't modify the source code,By the way,when I use the cgs.exe command to convert,it done.what's wrong with the SDK? it says that

Makefile:148: recipe for target 'convert_cgs_to_hex' failed

make: *** [convert_cgs_to_hex] Error 255

Hi BCM,

     We try to test the power consumption of BCM20736S, when it running in sleep or deep sleep mode.

Application I:

     ADV: OFF

     SCAN: OFF

     CONNECTION: none

     TIMER: none

     GPIO: GPIO0 output low, others disabled

     PUART: disable

     PWM: disable

     We think the BCM20736 would go to sleep automatically with above configuration.

     But the current in VBAT(3.3V) is as high as 4mA+, seems that, the BCM20736 does not enter the sleep mode after application init.

Application II:

     With the configuration of Application I, we add one function for deep sleep as below:

     Register deep sleep CB function In Application II:      devlpm_registerForLowPowerQueries(devLPM_cb,0);

     UINT32 devLPM_cb(LowPowerModePollType type, UINT32 context)

     {

          ble_trace1("low power poll type:%d",type);

          return ~0;

     }

     This function does been called by application II, but when we return ~0, the power consumption does not go down. seems that, the BCM20736 does not enter the deep sleep with above function.

     Is there any standard applications we could refer to ?? or is there any introduction or user guide documents about sleep / deep sleep controll ??

     Sincerely ~~~

Hi,

a customer like to buy IEEE addresses self and like to integrate his own addresses on a BCM20736/7 module. Is that possible?

How he can do it?

He like to use it as for a higher security level.

Thanks

BRs