1 of 1 people found this helpful
Yes, you can. You have to make sure that you configure the ACLK to a frequency that can be divided down to generate both frequencies you need.
Here is an example to generate 1K and 8K on the two channels.
// Configure ACLK for 512KHz.
aclk_configure(512000, ACLK1, ACLK_FREQ_24_MHZ);
// Configure channel0 for 1.01KHz.
pwm_start(PWM0, PMU_CLK, 0x2FF, 0x200);
// Enable Output on P26 == PWM0.
gpio_configurePin((26) / 16, (26) % 16, GPIO_OUTPUT_ENABLE, 0);
// Configure channel1 for ~8KHz
pwm_start(PWM1, PMU_CLK, 0x3E0, 0x3BF);
// Enable Output on P27 == PWM1.
gpio_configurePin((27) / 16, (27) % 16, GPIO_OUTPUT_ENABLE, 0);
The max value the PWM HW will count to before starting from init value is always 0x3FF. The counts are incremented at the ACLK edges starting at init value. When the count reaches toggle value, the PWM channel output is inverted and when the count reaches 0x3FF, the output is inverted again and the count wraps around to init value and so on.
If you need a 50% duty cycle, make sure that the init value is the same distance from the toggle value as toggle value is from 0x3FF.
Thanks, I got everything up and running with your help!
my gpio config is
const BLE_PROFILE_GPIO_CFG hello_sensor_gpio_cfg =
GPIO_PIN_WP, // This need to be used to enable/disable NVRAM write protect
GPIO_PIN_BUTTON, // Button GPIO is configured to trigger either direction of interrupt
GPIO_PIN_LED, // LED GPIO, optional to provide visual effects
GPIO_PIN_BATTERY, // Battery monitoring GPIO. When it is lower than particular level, it will give notification to the application
GPIO_PIN_BUZZER, // Buzzer GPIO, optional to provide audio effect
-1,-1, -1, -1, -1, -1, -1, -1, -1, -1, -1 // other GPIOs are not used
0,0, 0, 0, 0, 0, 0, 0, 0, 0, 0
the GPIO_PIN_BUZZERis 28;
if GPIO_PIN_BUZZERis 28 ,means I use PWM2 is ritght?
this function bleprofile_BUZBeep() use PWM2 to driver buzer?
why i config the pwm2 like this:
But it does not work well,why??
Please have a look at the PWM sample app called pwm_tones in SDK 2.0.1 for an example for how to configure and use the PWM block. This sample will work with SDK 1.1.0 too.
why i can`t measure the 24 MHz Ref Xtal when it work?
I use BCM920732TAG_Q32 board!
You should be able to measure the 24MHz xtal with an oscilloscope at one of the terminals of Y1. Since this is turned off in sleep, you will see it oscillating only when the chip is awake.
> why i can`t measure the 24 MHz Ref Xtal when it work?
I don't understand the question. Could you please explain what you are trying to do?
when i call bleprofile_PWMBUZFreq(PWMBUZ_2000,0,0) in hello_sensor_create(void), why it does not work well?
I got same issue on calling bleprofile_PWMBUZFreq() to change the frequency periodically.
I will ask the developers to respond as it appears that 2 of you are experiencing the same issue with bleprofile_PWMBUZFreq(), one of you on an older TAG2 20732 based board, while the other is on the newer TAG3 20737 based board.
1 of 1 people found this helpful
Can you try disabling sleep using the callback registered with devlpm_registerForLowPowerQueries(see uart_firmware_upgrade/ws_upgrade_uart.c for example)? This function uses the PMU clock as the reference which will be shut down in sleep. There are some posts that list the options you have - disable sleep or use the LHL clock as the reference and provide your own implementation of controlling the buzzer.
I'm using 20732 as well for PWM testing. And just tried disabling sleeping, but it was still failed that only around 4.7 kHz square pulse is generated no matter what *preset* is set to function 'bleprofile_PWMBUZFreq'.
Have you tried bleprofile_PWMBUZFreq(PWMBUZ_FREQ_MANUAL, init_value, toggle_value)? The bleprofile_PWM* API uses the aux clock at 256KHz and so this is what will be divided down to the PWM frequencies. If you want higher or more control, you should use your own methods to control the PWM using the sample in the first response above (or look at pwm_tones sample app).