PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
Hi there,
this is my 2nd discussion and as I asked a bit too unprecisely in my 1st one, I want to make it better now.
I am trying to implement a lux sensor on my psoc 4 ble kit but I just don't understand how to implement the services and how to start the main.c program.
At the moment I am trying to understand the API's for the BLE module but some are just unclear and not really documented in the documents where they should be.
So can some please give some advice and help on my way to get this thing done.
I am currently putting 6-7 hours a day into this project but without help I am lost.
Thanks
Chris
Show LessHi,
Can I get a simple firmware (without UART or button) for testing FCC for allowing the following changes to BLE? We are using CY8C4248LQI-BL583 with customized PCB.
- Frequency channels (low/mid/high)
- Highest Modulation
Thanks
Show LessI am programming external programmer with CY8C4248lqi_bl583.
According to AN84858, after I call SetIMO48Mhz(), I receive the system call status code 0xF0000013.
What does it mean this code?
Cypress document doesn't explain this code.
Thanks
Justin
Show LessHellow,
The following SWD interface is used to use the debugging function of CY8C4024LQI-S411.
SWDCK (P3_3 pin)
SWDIO (P3_2 pin)
XRES
Q1.
Could you provide me with the recommended pin processing information for these debug pins?
*
For example, the following information:
1)The pull-up resistors of SWDIO and SWDCK must be in the range of 1 k to 100 k ohms
2)XRES does not require pull-up processing
Best regards,
Harukawa
Show LessI have created a peripheral board using the BLE module. If I have two of my peripheral boards with the same firmware, how can the Central determine which board to connect to? Since it is my understanding that each board would have the same BLE address and the Central connects by specifying the BLE address.
Show LessiPhone X running Bluetooth 5 cannot pair with my Bluetooth low energy device with the chip CYBLE-214009-00 running Bluetooth 4.1. Other iPhone models works fine. I even upgraded to iOS 12 beta with no luck.
Here is the log:
CYBLE_EVT_GATTS_READ_CHAR_VAL_ACCESS_REQ: handle: 3
CYBLE_EVT_GAP_AUTH_FAILED, reason: AUTHENTICATION_TIMEOUT
CyBle_PulseCtrlSendNotification API Ok: 0
CyBle_PulseCtrlSendNotification API Ok: 0
CYBLE_EVT_GATT_DISCONNECT_IND
CYBLE_EVT_GAP_DEVICE_DISCONNECTED, reason: 13
Any clue will be much appreciated. Thanks in advance!
Show Less
Could I get a real clear example of how to do read only BLE call, I have read through 10 app notes and my code does not function.
My code is at the end of this tread.
Re: CYBLE_EVT_GATTS_READ_REQ - Identify which characteristic was read
Show LessDoes the BLE stack create or update a value when a non bonded device pairs?
In other words, when a device pairs, how do you know if you should store it, or if it already stored?
Show LessHi,
The problem is that when I use the Bootloader Host to program my prototype board, the Bootloader Host reports as such
05:56:14 PM - program Started
05:56:16 PM - program Finished Successfully
05:56:16 PM - program completed in 1430 ms.
Except the code that I am attempting to program into it does not seem to write to the prototype board.
The code I am using are the bootloader and blinking LED bootloadable projects that come with the kit. The blinking LED comes on to indicate that the prototype board is running the bootloader. However, upon "successful" programming, instead of the LED blinking at a slower rate, the LED simply shuts off.
I have double checked the HEX and ELF dependencies
I have tried this on two separate Prototype Boards, and on different computers and I still have the same issue. There are no errors to help give a direction to troubleshoot.
Has anyone heard of this problem before?
-Thanks for your time
Show LessHi, I'm starting to learn the PSoC hardware, I'm using the LED blinking + UART bootloader examples code for the CY8CKIT-049-41xx board kit Setup File package . I'm able to change the PWM parameters of the LED blinking application that runs when not pressing the button, build and use the bootloader host to download the firmware to the board, confirmed by the different times the led is on and off. However I've tried to change the PWM parameters of the faster LED blinking in the UART Bootloader side, rebuilding all the files and then downloading the firmware again but no matter the changes I do, it appears the bootloader host is only rewriting the LED blinking side, since the LED time of the Bootloader app remains always the same. It is my guess that the bootloader app is only writing the memory blocks of the LED Blinking app, but not it's own section. It was my understanding that the boot loader host sent the full memory contents to the bootloader app and reflash the full memory, is this suposition correct? How could I perform any other changes to the bootloader app in that case? What if I wanted to change it to communicate by I2C then? That's why so far I've only tried the led time change, in case something else fails. Also, when I used the example code for the first time, the compiling failed saying the bootloader components were a previous version (1.3). I used project->update components to repair it (version1.6) and it built successfully. Then I had the issue mentioned above. Not sure if it could be related but worth mentioning. I'm attaching the workspace files as suggested by user_242978793 in a similar post. Thanks a lot for cheking it!
Show Less