![]() ![]() I'd sure be grateful for any advice anyone could give me on this. This despite the fact that nothing relating to BLE functions, such as bonding, has been done, except whatever the code itself does, no action on my part has been taken. However, all subsequent presses cause immediate toggling of the LEDs without the required hold time. In the situation when it's not operating properly, the first press of a button whether held or not does nothing to the LEDs and the ISR is not called. Pressing and releasing the button before the timeout period is over simply stops the timer and nothing else happens. The interrupt's ISR, based on a flag which indicates which button has been pressed, then toggles the pin driving the appropriate LED. If the button is held for more than the timeout period the timer initiates an interrupt at terminal count. ![]() Operation should be: when a PB is pressed and held a timer is started (set for a timeout of 3 seconds). If I install code to allow BLE bonding when an iPhone or iPad is very close to the EZ-BLE module the switches still work properly when in Debug mode but not when "programmed" (non-debug mode). If I program this code to the PSoC 4 without code for BLE operation installed, it works fine both when doing Debug and non-debug (program) operation. Reason and Workaround: This is because of a bug in the USBUART User module code. The response (for test purposes) should be that SW1 will toggle an output driving an LED and SW2 will do the same to another LED. Problem Description: When a packet of exactly 64 Bytes is transmitted using USBUART from PSoC to a PC and the result observed on a Terminal program, nothing is displayed on the Terminal program on the PC. Using EZ-BLE module (CYBLE-214009-00), PSoC 4 with the pioneer board I have two pushbutton switches which I want my program to respond to when either has been pressed and held for 3-4 seconds. I don't know how I can see what the BLE saw for the entered passkey to check what went wrong. When my app is prompted and I enter '1234' into the passkey entry, the connection fails for the following reason:ĬYBLE_GAP_AUTH_ERROR_CONFIRM_VALUE_NOT_MATCH I have confirmed that this is indeed the pin here:Ĭase CYBLE_EVT_GAP_PASSKEY_DISPLAY_REQUEST: When stack comes on, set correct ECO capacitance trim valueĬY_SET_XTND_REG32((void CYFAR *)(CYREG_BLE_BLERD_BB_XO_CAPTRIM), 0x9898) ĬyBle_GapFixAuthPassKey(TRUE,dataLocal.pinCode) ĬyBle_GappStartAdvertisement(CYBLE_ADVERTISING_FAST) I have set the password to '1234' using the following code: Is this right?, I am still getting weird data in some places and want to make sure this is not the reason.I am trying to have my BLE device connect to my app with a simple password setup. Struct KeyboardStruct *Keyboard = &KeyboardContent Struct KeyboardStruct ChordGeneratorContent Īnd then on the appropriate Start function I pointed the pointer to the content, as done below: Struct KeyboardStruct GlobalTuningContent So this is what I did is on my header file I declared the following: So thanks for the recommendation, I'm going to try that, thank you If I got right what you are saying to me, to use a pointer to a struct, I must declare the data as a struct and then declare a pointer that points to it?, I'm sorry for this "dumb" questions, I'm transitioning from Arduino and c++ to C (I think?), and I must re learn some of the basic stuff. Hi, thanks for your reply, I have a separate file with my structs, its a header file. AIROC™ Wi-Fi and Wi-Fi Bluetooth Combos. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |