PSoC™ 4 Forum Discussions
Using the Peripheral and Central Profiles of the UART to BLE in conjunction to CoolTerm (Terminal Program which allows you to Send Strings) I am running into a couple issues. If my strings are relatively short (65 bytes or so), the system is happy. I can send the string repeatedly and the peripheral device responds accordingly. When I increase the string a bit more, to around 90 bytes, while the string shows up on the terminal window, communication locks up If I increase the string length to the full desired length (204 bytes), I get the first few characters of the string, and of course the system is hosed after that. I made certain my payload is set to about 256 bytes for both transmit and receive for the peripheral device. My UART buffers are also ample on both central and peripheral devices (1024 bytes). Any ideas why I be running into issues with these larger payload sizes?
Show LessI am using the UART-BLE program for central and peripheral devices, and noticed the use of the friendly name "BLE_Serial" for setting up advertising packets in the peripheral device in the GUI that is provided. However, if I search for BLE_Serial programmatically, I don't see it in any of the files. I assume this is how the devices pair automatically, be see it neither in the set of files for peripheral or central devices. Thinking instead they are using the public address to pair, I also search for either of these identifiers but don't seem them codified either. Not certain therefore why 1) these values are found in the gui but no where to be seen in the code, and 2) what exactly is the central device receiving that lets it know it automatically wants to pair and communicate with the peripheral device.
Show LessI have an advertiser that is generating advertising packets every 50ms. My observer has scan window and interval of 30ms. I'm watching the CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT and for some reason it occurs 9 times and then just stops.
Shouldn't I be able to get an interrupt every time the 50ms advertising packet and the scan window overlap?
There is no CYBLE_EVT_GAPC_SCAN_START_STOP or CYBLE_EVT_TIMEOUT occurring.
I don't think it is the advertiser because every time I reset the observer I get the same 9 packets.
Any ideas?
Show LessI Have Problem Related with Write And Read Data From App Using BLE CYBL-10161
In My Project I use The Third Party App, When I Connect The BLE to App It Get Connected Successfully,And After That App Shows "" Reading System Please Wait.."".
This means that App Asking For Or Wants To Read Some Attributes From BLE( I'm Replacing Previous BLE with CYBL-10161 BLE With Same App),
So Can I know that Exactly Which Attribute App Ask Or Want's To Read.
And I Also Wants To Know Exactly Which Event Occur When App Ask Or Wants To Read Attribute
My Project Stuck Here
""When BLE Wants To Write Data On App And When App Wants To Read Data From BLE"".
I'm New To Cypress BLE's.
Please Give Your Valuable Response To me.
Show LessHi,
Hi we want to configure a CYBLE-014008-00, using EZ-serial as a GAP central, but before buy anything we want to know if the ez-serial-firmware. can be connected up to 7 pheripheral devices at the same time.
And we want to know if ussing this firmware, the module can be configured at the same time as a GAP central and iBeacon.
Thanks!
Hello,
I have problem with mentioned devices. HC-SR501 motion sensor is always high when there is also a Wi-Fi module ESP8266 connected to my board. What could be the issue?
Show Lessplease help
project is attached. when i connect the programmer and program the chip or put in debug mode LCD_Char_PrintString() works.
if i removed the programmer and connected to power supply; LCD_Char_PrintString() doesn't show anything or if i put in debug without programming few LCD_Char_PrintString() doesn't show anything mostly first line.
working on 3.1 but my other program works which are using the same sub routines?
i found in lcd.c char8) '\0' = 0x00
void LCD_Char_1_PrintString(char8 const string[])
{
uint8 indexU8 = 1u;
char8 current = *string;
/* Until null is reached, print next character */
while((char8) '\0' != current)
{
LCD_Char_1_WriteData((uint8)current);
current = string[indexU8];
indexU8++;
}
}
** this problem may be similar as per page 58 HD44780 on CY8CKIT-049 of our forum.
Show LessI'm working with a CYBLE-022001-00 PROC module and have been struggling trying to solve a problem where I can't get the CPU to wake from deep sleep with a GPIO interrupt.
With the following code, I have an input configured to interrupt on falling edge, and have the pin configured with a pullup. There's also a pin configured as an output and I toggle its state in the ISR...watching it on a scope.
With the following code, the output toggles each time I ground the input which shows me the ISR is working as expected.
However, if I change the CySysPmSleep() to CySysPmDeepSleep(), it stops working. It's not waking from deep sleep. Can anyone confirm that this can be done on this module?
CY_ISR(wakeup_isr)
{
if(out_on == 0)
{
OutPin_Write(1);
out_on = 1;
}
else
{
OutPin_Write(0);
out_on = 0;
}
isr_1_ClearPending();
}
int main()
{
OutPin_Write(0);
isr_1_StartEx(&wakeup_isr);
CyGlobalIntEnable;
for(;;)
{
CySysPmSleep();
}
}
Hi, my question is if I can use the UART v2.50 module with the Bootloader instead of using the SCB module in PSoC 4. I understand I must use the "Custom Interface" option in the Bootloader parameters and the CyBtldrComm* APIs, but I´m no really sure how to use them.
Do I need to write code for the APIs, or is there written code already? Thanks.
Show Less