PSoC™ 4 Forum Discussions

I'm trying to build a device which has a single device SPI plus I2C devices. I want to use the CYBLE-224116-01 module (BLE 4.2 + PA/LNA) -- but what I say below also applies to the BLE 4.1 version, CYBLE-224110-00. I'd like to have SWD available for programming and debugging.

But I don't see how to make it work. Because:

1. SCLK 0 is only available on p0.7, which is needed for SWD, or p1.7, which doesn't come out of the module.

2. And you can't use SPI on SCB1 at all, since SCB1 MOSI does not seem to come out of the module on ANY pin.

To get around this, I'd have to add jumpers for "programming mode" in order to program, and wouldn't be able to use the debugger while keeping SPI live. This seems like a serious oversight, and will both make production programming and development more annoying than necessary.

Could things really be this screwed up? 

The only way to program the module is the PSoc Creator? I need that a user can change the bluetooth name without use the PSoc Creator.

Is it possible? How can ask at bluetooth module to change the name?

Hello,

Can some one explain to me how exactly can I create the following behavior?

I want that any client that wants to connect to a peripheral, server device to be asked a password provided in advance and only when the correct password is given to connect, see the profile,etc.  Next I want that the client to be able to make a pair action to the device  and every time the device is near to connect automatically to it. I know that some parts of this behavior should be accomplish by the client like the automatically connection to the device but I am aware that something should also be done in peripheral which is a PSOC 4.

I already go through the examples like privicy(017), oob pairing(032) and bonding (015) but somehow I cannot fully understand them to implement my scenario. Also it would be great if you can also explain the state(event) in which a particular action should take place. For example I used  CyBle_GapFixAuthPassKey (1, 123456); in CYBLE_EVT_STACK_ON and I was able to pair in CYSmart with this code but I am not sure this is all. My Ble is set as Mode 1 security Authenticated pairing with encryption and I/O capabilities KeyBoard and Display(even if my device doesn't have such, I personally am not sure why are those used) and Bonding.

Thank you!

We are using a CYBLE-022001-00 module and I need 2 ADC SAR on the design. However, when I perform a build the error indicates 2 clocks are required and 1 is available.

Any way around this?

I am not sure about how this works. I have never tried to run a program with BLE before I think.

I have a program which I have to update. I modify some things (nothing related with ble behaviour). things like: now this sketch controls 5 motors and it has to control 10, not i has 2 force sensors and it has to control 3... This kind of stuff. BLE file is almost equal.  I just add notifications for new variables.

I have a problem when I try to run the program in my pioneer development board (ble version). It hangs and gives an error:

"Debugger exited unexpectedly during run. Encountered error (Target disconnected See output window for more information.)"

Clicking over Show more details" gives:

"There was an unhandled error during the debug session. This has forced the debugger to shutdown. Try again."

I am testing it without anything connected. Just to see if it works. So maybe this is the problem and I need to connect everything to make it working.

As soon as main function starts, InitializeSystem is called:

void InitializeSystem(void)
{
    CyGlobalIntEnable;                //Activate mask of interrupts
    CyBle_Start(CustomEventHandler);  //Init BLE and set event handler function
    ADC_IRQ_StartEx(ADC_ISR);         //Interrupt for reading ADC
    isr_button_StartEx(MyISR);
    /*Set vector for WDT interrupt to desired function. This function will be in charge of updating values to be sent by BLE*/
    CyIntSetVector(WATCHDOG_INT_VEC_NUM, &WDT_INT_Handler); 
    InitializeWatchdog();
    OPA_Start();                     //Start OPA
    OPA_Enable();
    ADC_Start();                     //Start ADC
    ADC_StartConvert();
    //CyDelay(1000);
}

I have read on other post about in the latest version of BLE watchdog is not used. It is used something called BLESS??. Maybe this is the problem. The current version of my software was built with an older version of PSOC and components. And now I updated the whole project to the latest one.

My problem is that if I set watchdog as active (in Initialize function), that function never ends. And in case it does, something goes wrong and it crashes.

I would want the code to reach this line in main():

for(;;) {       
        CyBle_ProcessEvents();

        ...

I am developing a pcb to keep all my stuff there but unitl I have it printed, I have to test my code in this board.