Smart Bluetooth Forum Discussions

Hello,

I made my own board with a BCM20732S module version B1 and when I try to use it for the first time I can't either program it or recover it with the reference images. It seems that it can't erase the chip. I use the SDK 1.1. I don't know if it can impact the programation but the I2C line is loaded by 2 devices : LIS3DH and AT30TS75A. I checked the RX and TX signals with an oscilloscope and they look good.

This is my download.log when trying to recover:

Download minidriver successfully had written 64 bytes to address 0x0020AF00

Download minidriver successfully had written 64 bytes to address 0x0020AF40

Download minidriver successfully had written 64 bytes to address 0x0020AF80

Download minidriver successfully had written 64 bytes to address 0x0020AFC0

Download minidriver successfully had written 64 bytes to address 0x0020B000

Download minidriver successfully had written 64 bytes to address 0x0020B040

Download minidriver successfully had written 64 bytes to address 0x0020B080

Download minidriver successfully had written 64 bytes to address 0x0020B0C0

Download minidriver successfully had written 64 bytes to address 0x0020B100

Download minidriver successfully had written 64 bytes to address 0x0020B140

Download minidriver successfully had written 64 bytes to address 0x0020B180

Download minidriver successfully had written 64 bytes to address 0x0020B1C0

Download minidriver successfully had written 64 bytes to address 0x0020B200

Download minidriver successfully had written 64 bytes to address 0x0020B240

Download minidriver successfully had written 64 bytes to address 0x0020B280

Download minidriver successfully had written 64 bytes to address 0x0020B2C0

Download minidriver successfully had written 64 bytes to address 0x0020B300

Download minidriver successfully had written 64 bytes to address 0x0020B340

Download minidriver successfully had written 64 bytes to address 0x0020B380

Download minidriver successfully had written 64 bytes to address 0x0020B3C0

Download minidriver successfully had written 64 bytes to address 0x0020B400

Download minidriver successfully had written 64 bytes to address 0x0020B440

Download minidriver successfully had written 64 bytes to address 0x0020B480

Download minidriver successfully had written 64 bytes to address 0x0020B4C0

Download minidriver successfully had written 64 bytes to address 0x0020B500

Download minidriver successfully had written 64 bytes to address 0x0020B540

Download minidriver successfully had written 64 bytes to address 0x0020B580

Download minidriver successfully had written 64 bytes to address 0x0020B5C0

Download minidriver successfully had written 64 bytes to address 0x0020B600

Download minidriver successfully had written 64 bytes to address 0x0020B640

Download minidriver successfully had written 64 bytes to address 0x0020B680

Download minidriver successfully had written 64 bytes to address 0x0020B6C0

Download minidriver successfully had written 64 bytes to address 0x0020B700

Download minidriver successfully had written 64 bytes to address 0x0020B740

Download minidriver successfully had written 64 bytes to address 0x0020B780

Download minidriver successfully had written 64 bytes to address 0x0020B7C0

Download minidriver successfully had written 64 bytes to address 0x0020B800

Download minidriver successfully had written 64 bytes to address 0x0020B840

Download minidriver successfully had written 64 bytes to address 0x0020B880

Download minidriver successfully had written 64 bytes to address 0x0020B8C0

Download minidriver successfully had written 64 bytes to address 0x0020B900

Download minidriver successfully had written 64 bytes to address 0x0020B940

Download minidriver successfully had written 64 bytes to address 0x0020B980

Download minidriver successfully had written 64 bytes to address 0x0020B9C0

Download minidriver successfully had written 64 bytes to address 0x0020BA00

Download minidriver successfully had written 64 bytes to address 0x0020BA40

Download minidriver successfully had written 64 bytes to address 0x0020BA80

Download minidriver successfully had written 64 bytes to address 0x0020BAC0

Download minidriver successfully had written 64 bytes to address 0x0020BB00

Download minidriver successfully had written 64 bytes to address 0x0020BB40

Download minidriver successfully had written 64 bytes to address 0x0020BB80

Download minidriver successfully had written 64 bytes to address 0x0020BBC0

Download minidriver successfully had written 64 bytes to address 0x0020BC00

Download minidriver successfully had written 64 bytes to address 0x0020BC40

Download minidriver successfully had written 64 bytes to address 0x0020BC80

Download minidriver successfully had written 64 bytes to address 0x0020BCC0

Download minidriver successfully had written 64 bytes to address 0x0020BD00

Download minidriver successfully had written 64 bytes to address 0x0020BD40

Download minidriver successfully had written 64 bytes to address 0x0020BD80

Download minidriver successfully had written 64 bytes to address 0x0020BDC0

Download minidriver successfully had written 64 bytes to address 0x0020BE00

Download minidriver successfully had written 64 bytes to address 0x0020BE40

Download minidriver successfully had written 64 bytes to address 0x0020BE80

Download minidriver successfully had written 64 bytes to address 0x0020BEC0

Download minidriver successfully had written 64 bytes to address 0x0020BF00

Download minidriver successfully had written 64 bytes to address 0x0020BF40

Download minidriver successfully had written 64 bytes to address 0x0020BF80

Download minidriver successfully had written 64 bytes to address 0x0020BFC0

Download minidriver successfully had written 64 bytes to address 0x0020C000

Download minidriver successfully had written 64 bytes to address 0x0020C040

Download minidriver successfully had written 64 bytes to address 0x0020C080

Download minidriver successfully had written 64 bytes to address 0x0020C0C0

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- loading minidriver

Download minidriver successfully had written 64 bytes to address 0x0020C100

Download minidriver successfully had written 64 bytes to address 0x0020C140

Download minidriver successfully had written 64 bytes to address 0x0020C180

Download minidriver successfully had written 64 bytes to address 0x0020C1C0

Download minidriver successfully had written 64 bytes to address 0x0020C200

Download minidriver successfully had written 64 bytes to address 0x0020C240

Download minidriver successfully had written 64 bytes to address 0x0020C280

Download minidriver successfully had written 64 bytes to address 0x0020C2C0

Download minidriver successfully had written 64 bytes to address 0x0020C300

Download minidriver successfully had written 64 bytes to address 0x0020C340

Download minidriver successfully had written 64 bytes to address 0x0020C380

Download minidriver successfully had written 64 bytes to address 0x0020C3C0

Download minidriver successfully had written 64 bytes to address 0x0020C400

Download minidriver successfully had written 64 bytes to address 0x0020C440

Download minidriver successfully had written 64 bytes to address 0x0020C480

Download minidriver successfully had written 64 bytes to address 0x0020C4C0

Download minidriver successfully had written 64 bytes to address 0x0020C500

Download minidriver successfully had written 64 bytes to address 0x0020C540

Download minidriver successfully had written 64 bytes to address 0x0020C580

Download minidriver successfully had written 64 bytes to address 0x0020C5C0

Download minidriver successfully had written 64 bytes to address 0x0020C600

Download minidriver successfully had written 64 bytes to address 0x0020C640

Download minidriver successfully had written 64 bytes to address 0x0020C680

Download minidriver successfully had written 64 bytes to address 0x0020C6C0

Download minidriver successfully had written 64 bytes to address 0x0020C700

Download minidriver successfully had written 64 bytes to address 0x0020C740

Download minidriver successfully had written 64 bytes to address 0x0020C780

Download minidriver successfully had written 64 bytes to address 0x0020C7C0

Download minidriver successfully had written 64 bytes to address 0x0020C800

Download minidriver successfully had written 64 bytes to address 0x0020C840

Download minidriver successfully had written 64 bytes to address 0x0020C880

Download minidriver successfully had written 64 bytes to address 0x0020C8C0

Download minidriver successfully had written 64 bytes to address 0x0020C900

Download minidriver successfully had written 64 bytes to address 0x0020C940

Download minidriver successfully had written 64 bytes to address 0x0020C980

Download minidriver successfully had written 64 bytes to address 0x0020C9C0

Download minidriver successfully had written 64 bytes to address 0x0020CA00

Download minidriver successfully had written 64 bytes to address 0x0020CA40

Download minidriver successfully had written 64 bytes to address 0x0020CA80

Download minidriver successfully had written 64 bytes to address 0x0020CAC0

Download minidriver successfully had written 64 bytes to address 0x0020CB00

Download minidriver successfully had written 64 bytes to address 0x0020CB40

Download minidriver successfully had written 64 bytes to address 0x0020CB80

Download minidriver successfully had written 64 bytes to address 0x0020CBC0

Download minidriver successfully had written 64 bytes to address 0x0020CC00

Download minidriver successfully had written 64 bytes to address 0x0020CC40

Download minidriver successfully had written 64 bytes to address 0x0020CC80

Download minidriver successfully had written 64 bytes to address 0x0020CCC0

Download minidriver successfully had written 64 bytes to address 0x0020CD00

Download minidriver successfully had written 64 bytes to address 0x0020CD40

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- loading minidriver

Download minidriver successfully had written 64 bytes to address 0x0020CD80

Download minidriver successfully had written 64 bytes to address 0x0020CDC0

Download minidriver successfully had written 64 bytes to address 0x0020CE00

Download minidriver successfully had written 64 bytes to address 0x0020CE40

Download minidriver successfully had written 64 bytes to address 0x0020CE80

Download minidriver successfully had written 64 bytes to address 0x0020CEC0

Download minidriver successfully had written 64 bytes to address 0x0020CF00

Download minidriver successfully had written 64 bytes to address 0x0020CF40

Download minidriver successfully had written 64 bytes to address 0x0020CF80

Download minidriver successfully had written 64 bytes to address 0x0020CFC0

Download minidriver successfully had written 64 bytes to address 0x0020D000

Download minidriver successfully had written 64 bytes to address 0x0020D040

Download minidriver successfully had written 64 bytes to address 0x0020D080

Download minidriver successfully had written 64 bytes to address 0x0020D0C0

Download minidriver successfully had written 64 bytes to address 0x0020D100

Download minidriver successfully had written 64 bytes to address 0x0020D140

Download minidriver successfully had written 64 bytes to address 0x0020D180

Download minidriver successfully had written 64 bytes to address 0x0020D1C0

Download minidriver successfully had written 64 bytes to address 0x0020D200

Download minidriver successfully had written 64 bytes to address 0x0020D240

Download minidriver successfully had written 64 bytes to address 0x0020D280

Download minidriver successfully had written 64 bytes to address 0x0020D2C0

Download minidriver successfully had written 64 bytes to address 0x0020D300

Download minidriver successfully had written 64 bytes to address 0x0020D340

Download minidriver successfully had written 64 bytes to address 0x0020D380

Download minidriver successfully had written 64 bytes to address 0x0020D3C0

Download minidriver successfully had written 64 bytes to address 0x0020D400

Download minidriver successfully had written 64 bytes to address 0x0020D440

Download minidriver successfully had written 64 bytes to address 0x0020D480

Download minidriver successfully had written 64 bytes to address 0x0020D4C0

Download minidriver successfully had written 64 bytes to address 0x0020D500

Download minidriver successfully had written 64 bytes to address 0x0020D540

Download minidriver successfully had written 64 bytes to address 0x0020D580

Download minidriver successfully had written 60 bytes to address 0x0020D5C0

Download minidriver successfully had written 8 bytes to address 0x0020D904

Launch minidriver at 0x0020AF00 succeeded

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Executing -- erasing chip

Downloaded 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%). Verified 0 code bytes ( 0.0%) and 0 data bytes ( 0.0%).   Current state: Terminated with error

Chip erase timeout (nLastProgressReportTime)

Do you have any idea or suggestion to check/test?

Kind regards

Daniel

I found there's strength PWM output on 20737S, could someone help to check?

I test again with pwm_tones demo project in SDK2.0, and get the following signal:

The 1st picture is a cycle of PWM signal, and the 2nd picture is a zoom out that shows there is another "big" cycle to generate.

The output tone is periodically "bi", "bi" .... around around 1 sec. period. I think this is not the normal PWM. Then I test following simple code again in Hello project, but get similar strange result.

    aclk_configure(512000, ACLK1, ACLK_FREQ_24_MHZ);
    pwm_start(0, PMU_CLK, 0x2FF, 0x200);   

    gpio_configurePin(26 >> 4, 26 & 0x0F, GPIO_OUTPUT_ENABLE, 0);

To support older, pre 2013 smart phones, can our peripheral advertise original Bluetooth (3.0) and same time, or alternating with advertising Bluetooth Low Energy (4.0)?

Peripheral will only connect with BLE central, and should ignore connection attempt by original Bluetooth central.

Is there a limit on the number of times we can use bleprofile_NVRAM_Write() to the same address?

That is, if it's writing to an eeprom, is there some limit on the order of 100K or 1M writes before it wears out?

Hello,

A customer of mine is looking to develop a beacon based on the Beacon ref design.

I have these questions, could you please help

•     Can we setup
UUID, Major and Minor values?

•     Can we change
the frequency (e.g. send signal every 1 second or every 500ms…)?

•     Can we change
the transmit power (to limit the range of the beacon)?

•     Can it
broadcast its battery level?

thanks

Mark

We want our central to continuously advertise, so other computers in the system can read telemetry in its advertisement data.

Meanwhile, central is making connections and communicating with slave devices.

Will this work?

In BLEPROFILE_DB_PDU, there is a field called 'header'. I looked through several sample codes, but did not find any use of header. Could anyone explain what does this 'header' filed do? Thanks !

Hi,

Our customer asked if peripheral device can advertise ADV packet while its device is in connection state.

Even if I know that BCM20736/20737 supports Master / Slave simultaneously in SDK 2.x, As I know, state machine from connection to advertising is not possible. Am I right?

Otherwise, it is possible in SDK 2.x, could you let me know how I should fix hello_sensor application in order to verify this scenario?

Thanks,

SM

I had been assuming that NVRAM was resident in EEPROM, and thus would persist after power is removed from the system.

Is this correct, or does it get cleared when power is removed completely (vs just going to HIDoff)?

From what I can see it seems to get cleared.