In order to reduce the interference, I try to control the channel mapping.

Once the device is connected, try to execute the following. 

But sometime it will failed report HCI 0x28 instant change.

So how to improve this? 

  case CYBLE_EVT_GAP_DEVICE_CONNECTED:
     DBG_PRINTF("CYBLE_EVT_GAP_DEVICE_CONNECTED: %x \r\n", cyBle_connHandle.bdHandle);
     //CyBle_GapAddDeviceToWhiteList(&peerAddr[deviceN]);
            
     if(channelMap==0){
          uint8 b[]={0xffu,0xffu,0x0u,0x0u,0x10u};  
          CyBle_GapcSetHostChannelClassification(b);               
     }else{
          uint8 b[]={0x1u,0x0u,0xffu,0xffu,0x10u};  
           CyBle_GapcSetHostChannelClassification(b);               
     }

We are looking where to get best prices for moderate MoQ (1k-2k pieces per order) to buy Cypress' CYBLE-012011-00? We are now waiting for Mouser to get the stock and they offer best prices we have been able to find on the market (4.29EUR w/o VAT for MOQ=1k on date: 16.12.2016).

Have anyone spotted better prices from any other reseller? We prefer EU reseller/distributer.

I'm still learning the in's and out's of C programing so this maybe a very obvious question. I have a Timer that calls an ISR. In my ISR I have this code: 

clockCounter++;
    
    if (clockCounter == 1600) {
        Increment_Quadrant_LED_OFF_Timer();
        Increment_Quadrant_Reset_Timer();
        Increment_Power_Off_Timer();
        clockCounter = 0;
    }

So that every second it calls those three methods to increment some other timer counters. My though process is that this is the cleanest way to handle keeping track of the timers in the appropriate other classes. 

Here is what my Increment_Quadrant_LED_OFF_Timer() function looks like: 

void Increment_Quadrant_LED_OFF_Timer()
{    
    if (!quadrant_LED_OFF_timer_ENABLED) { 
        return; 
    }

    quadrant_LED_OFF_timer_counter++;
    if (quadrant_LED_OFF_timer_counter >= (QUADRANT_LED_OFF_TIMER_DURATION / DEBUG_DIVIDER)) {
        Quadrant_LED_OFF_Timer_Did_Expire();
    }
}

Where quadrant_LED_OFF_timer_ENABLED variable and Quadrant_LED_OFF_Timer_Did_Expire() are defined in a class call app_Timers. So this works fine the first time that quadrant_LED_OFF_timer_ENABLED is set to 1 from my main.c.

Here is what my Quadrant_LED_OFF_Timer_Did_Expire() method looks like: 

void Quadrant_LED_OFF_Timer_Did_Expire()
{
    UART_UartPutString("Quadrant_LED_OFF_Timer_Did_Expire \n\r ");
    
    quadrant_LED_OFF_timer_ENABLED = 0;
    quadrant_LED_OFF_timer_counter = 0;
}

So you can see that I set my quadrant_LED_OFF_timer_ENABLED to 0 here.

If I debug and check quadrant_LED_OFF_timer_ENABLED after it has been set it's correct at 0.  However, continuing in debug if I check quadrant_LED_OFF_timer_ENABLED in this function Increment_Quadrant_LED_OFF_Timer() it's set back to 1. 

So just to clarify: 

void Increment_Quadrant_LED_OFF_Timer()

void Quadrant_LED_OFF_Timer_Did_Expire()

int quadrant_LED_OFF_timer_ENABLED

int quadrant_LED_OFF_timer_counter

Are all declared and defined in app_Timers.c and Increment_Quadrant_LED_OFF_Timer() is being called from Cook_Timer_ISR.c

My questions are: 

    
1. What my take away from the debugging and my other programming experience is that the ISR is calling Increment_Quadrant_LED_OFF_Timer() from a different thread? Which is guess it's not technically a different "thread" but some other location in memory? However if this was the case I'm not sure how I'm getting proper UART output. 
    
2. Is calling external methods like this to increment other counters the proper way to do this from an ISR? Or should I have a separate ISR for each timer that I need? It seems logical to have one counter that counts every 1 second then just piggy back off that one. Maybe not. 
   

Thanks for any help! 

I have an application needs to measure the pulse width. I used the demo code PWMexample as a start. I added a TCPWM counter component to try to measure the pulse width of the PWM signal. Hope that the counter will start at the rising edge and capture at the falling edge so by reading the capture register I can get the pulse width. But the problem here is: whenever I added start or reload input to the component, the capture won't trigger the interrupt.

Does anyone knows what I missed? 

Hi,

I have a proximity sensor which consists of a PCB trace of around 15cm diameter. There is a crosshatch shield electrode on the bottom layer of the board, and I want to use this shield electrode to give directionality to the sensor as described in the application notes.

Without the shield electrode connected, I get a proximity sensing distance (SNR>5) of around 140mm. When I connect the shield electrode this drops to around 80mm, and there is very little effect on the directionality of the proximity sensing.

Has anyone else tried to produce a directional proximity sensor using a shield electrode?

I have attached a trace of the Sense and Shield signals. The signals are in phase, but the pulse widths are not stable, is this normal?

Device: CY8C4248LQI-BL583

Regards,

Andy

Hi All,

I have made a pressure sensor which is basically a capacitor. I just need to get the absolute capacitance (or raw count) value using CSD widget. I don't need any other feature for now, but just the absolute value. Can you guys help me use CSD widget to find capacitance of a capacitor?

I am using PROC module provided with BLE Pioneer Kit. I'll move to another module but I want to get familiar with CSD widget. As far as I understand I'll be using Mutual Capacitance (CSX), and it would be great if you could help me specifically with that.

I tried to go over code examples and documentation but they mostly talk about touch buttons, proximity sensing, etc. Your help will be much appreciated.