Smart Bluetooth Forum Discussions

Hi I would like to connect a Murata piezo buzzer on a 20736 SOC

But I am using

3 Channels to drive LED

W

hat are my option ?

Which pin can I use to rive the piezo

Can I use PWM2_OUTPUT_ENABLE_P28 ?

// Port = P#/16 and PIN = P# % 16

#define LED_RED    26

#define LED_GREEN  14

#define LED_BLUE   13

#define GPIO_PORT(x)  (x/16)

#define GPIO_PIN(x)   (x%16)

#define GPIO_PIN_28   28

/*

enum

{

/// PWM0 Output enable on P26

PWM0_OUTPUT_ENABLE_P26  = GPIO_OUTPUT_ENABLE,

/// PWM1 Output enable on P27 N/A MOSI

PWM1_OUTPUT_ENABLE_P27  = GPIO_OUTPUT_ENABLE,

/// PWM2 Output enable on P28

PWM2_OUTPUT_ENABLE_P28  = GPIO_OUTPUT_ENABLE,

/// PWM2 Output enable on P6 N/A

PWM2_OUTPUT_ENABLE_P6   = (GPIO_OUTPUT_ENABLE | (1 << 4)),

/// PWM2 Output enable on P14

PWM2_OUTPUT_ENABLE_P14  = (2 << 4),

/// PWM3 Output enable on P29 N/A

PWM3_OUTPUT_ENABLE_P29  = GPIO_OUTPUT_ENABLE,

/// PWM3 Output enable on P13

PWM3_OUTPUT_ENABLE_P13  = (2 << 4)

};

*/

#define ENABLE_LED_RED    PWM0_OUTPUT_ENABLE_P26

#define ENABLE_LED_GREEN  PWM2_OUTPUT_ENABLE_P14 // PWM3_OUTPUT_ENABLE_P13

#define ENABLE_LED_BLUE   PWM3_OUTPUT_ENABLE_P13 // PWM2_OUTPUT_ENABLE_P14

1    P27   MOSI

36  P25   MISO

37  P24   SCK

30  P3     CS_TC1

31  P2     CS_TC2

## UART ##

18           RX

19           TX

ADC

35  P8   Battery Voltage Monitoring

Hello,

During debug, my WICED Sense2 became a brick.

I tried to recover with WICED Sense Recovery Procedure Video.

However I can't find a boot button on the board and following recover command fails.

wiced_sense2-BCM920737TAG_Q32 recover UART=COMxx

**** Recovery failed - retry ****

How can I recover WICED Sense2?

Best regards,

Nori Shinozaki

I'm trying to reference directly to the assigned mac address of the device, and I couldn't figure out where a defined constant of its location is at, i'm sure it is somewhere. I was going to try and reference to where it says it is at in the hex file, but that location was 0xFF000015, which isn't a valid memory location on this chip, or at least it appears to hard fault when I try to access it. I did find a list of defined address locations for configurations in the patch sysmdefs file, and all of those addresses are more in the range of 0x20000. I'm assuming that 0xFF000000 translates to somewhere in that range.

Hi there,

I am trying to set a static random address on a BCM20737S device using the API-call: blecm_set_static_random_bd_addr()

I´ve seen several threads which describe this procedure. I did it like this:

• Added APP_PATCHES_AND_LIBS += bd_addr_control.a to my project makefile
• Included #include "blecm_set_static_bd_addr.h" in my project
• Called blecm_set_static_random_bd_addr(new_bd_addr) at the end of my app_create()-function, with new_bd_addr as a UINT8 array of size 6
• Downloaded the binary with setting BD_ADDR to 0xFFFFFFFFFFFF

After starting advertising, the address 0xFFFFFFFFFFFF is always the same. Cycling power or resetting the device does not change anything.

I tried it my own application and also with the my_beacon sample application. Both not working.

What am I missing?

BR,

Alex

Hi,

We have gotten too frequently programming failure and recover them with recovery option on our custom board, so we have 2 questions about recovery option.

1. what different between usual programming and recovery option one from device behavior perspective?

2. is there any side effect expected when using recovery option as usual programming procedure in line?

Thank you,