Smart Bluetooth Forum Discussions

Our project need an accurate 600Hz PWM output,599.9~600.1 is allowed.

But we tried several ways,and failed to get it.

1.

aclk_configure(512000, ACLK1, ACLK_FREQ_24_MHZ);

adjust pwm initail value to get 600Hz,

pwm_start(ID, PMU_CLK, toggle_value, 155);    ~600.4

pwm_start(ID, PMU_CLK, toggle_value, 154);    ~599.7

2.

aclk_configure(307200, ACLK1, ACLK_FREQ_24_MHZ);

adjust pwm initail value to get 600Hz,

pwm_start(ID, PMU_CLK, toggle_value, 0x200);   ~600.9

pwm_start(ID, PMU_CLK, toggle_value, 0x1FF);   ~599.8

3.

I tried to modify input clock of PWM slightly,but it seems the output frequency is not modified.

aclk_configure(307308, ACLK1, ACLK_FREQ_24_MHZ);

pwm_start(ID, PMU_CLK, toggle_value, 0x1FF);   ~599.8

How can I get an accurate PWM output frequency?

In the Consol Debug Viewer, there is a message, "Trace Decoding Error - Could not find line number 314", appear by app of "hello_sensor" example code.

Another app such as "automation_io_server" or "heart_rate_monitor" are all appear with this message.

It show out after function call, "..._create()", executed completely. Simply, It's no way to trace back or debug it. 

So, at this moment, I don't know how to find the reason out.

Even create a new APP by 'WICED Smart Designer" appeared with the message.

Have you know:

  What is its bad effect?

  How could we tracking the reason? and,

  How to solve it?

Thanks,

Best Regards,

Joy Sun

I am currently adding the ability to update the BCM module's firmware via the puart from our main system micro to enable in field programming of firmware updates.  This is based on the example project, "uart_firmware_upgrade".  A question that arises is that of MAC address after the update.

I've seen other threads that indicate that the MAC address can't be set at runtime via an API call -- that it has to be added to the binary file via an external tool. The issue that I'm trying to determine how to address is that a single binary image will be sent to all devices in the field for the purpose of field firmware upgrade.  It seems this will result in all upgraded devices having the same MAC address.

Is there a solution to this problem that doesn't require a unique file to be built for every device in the field?

Thank you,

David

Based on various parameters in my application, I would like to switch between timed and untimed DEEP SLEEP.  I am always using an interrupt to wake up on, sometimes combined with a timer and other times without a timer.  The first DEEP SLEEP after a POWER ON RESET, always results in a DEEP SLEEP without a timer.  Afterwards, based on parameters set at connection, I attempt to use the DEEP SLEEP with a timer, but the CHIP never wakes up with the timer once I use it without the timer.   If i always set the timer (make sure secs < SLEEP_MAX), then the CHIP will wakeup with the timer without issue over and over again.  Can someone tell me what I should be doing different, after a DEEP SLEEP without a timer, that will allow the CHIP to wake up with the TIMER as expected?

-----snip-----

void

app_enter_deep_sleep_with_timer(int secs)

{

     ble_trace0("+Entering deep sleep");

     devLpmConfig.disconnectedLowPowerMode = DEV_LPM_DISC_LOW_POWER_MODES_HID_OFF;

     miaDriverConfig.delayAfterEnteringHidOffInUs= 30000000; // 700000;

     devLpmConfig.wakeFromHidoffRefClk = HID_OFF_TIMED_WAKE_CLK_SRC_128KHZ;

     if (secs < SLEEP_MAX){

       devLpmConfig.wakeFromHidoffInMs = secs * 1000;

       ble_trace1("LPM timer secs %d", secs);

     } else {

         devLpmConfig.wakeFromHidoffInMs = 0;

     }

     gpio_inputDisableAll();

     gpio_configurePin(GPIO_PIN_P0 / 16, GPIO_PIN_P0 % 16, GPIO_INPUT_ENABLE | GPIO_PULL_UP, 0);

     mia_enableLhlInterrupt(1);

     gpio_configurePin(GPIO_CAP_BUTTON / 16, GPIO_CAP_BUTTON % 16, GPIO_INPUT_ENABLE | GPIO_EN_INT_BOTH_EDGE, 0);

     devlpm_enableWakeFrom(DEV_LPM_WAKE_SOURCE_GPIO);

     bleprofile_PrepareHidOff();  // Puts device into Deep Sleep ~1.33uA

}

-----snip-----

I am working with a new PCB design using the BCM20736S. I am trying to verify that BLE communications are working between the board and a Windows 8.1 PC. I am using the 2.2.1 SDK's unmodified Heart Rate Monitor application to do this test. "Heart Rate Monitor" shows up on Windows Bluetooth scan, but I am not able to pair with the board.

Although I compile for the 20736, I understand that this same code works on the 20737 part.  So I do the following without changing the firmware.... On the same PC I am able to download the firmware onto an Anaren board (Dev Kit A20737A-MSDK1 with module base on BCM20737) and the "Heart Rate Monitor" shows up on Windows Bluetooth scan. I am then able to pair with the device without any issues.

Another symptomatic difference between these is that the BCM20736S-based device will only show up on Windows' discovery screen for 8-12 seconds.  The Anaren-based device will appear on Windows' discovery screen for 40 or more seconds.

I repeated these tests with the Speed Test and several other SDK apps, and I get the exact same results.

So is there any firmware/compiler reason that the Anaren board would work in this case, but my PCB with the BCM20736S would not pair?  Does this point towards a hardware issue on my PCB, or are there possible software reasons for this issue?

Thanks,

     Aaron