PSoC™ 4 Forum Discussions
Hi,
I m new with BLE and totaly stupid about it. I would like to know how to use the PA integrated for more range(db power).
thanks in advance
Show LessI'm using BLE_Temperature_Measurement example at BLE 012011-00.
I want to hold measurement interval value that enter from CySmart -> Health Thermometer Service -> Measurement interval -> ASCII data at a variable.
Briefly,
a variable = measurement interval value ;
Show LessI just designed in a CYBLE-014008-00 on a 5V supply, and I haven't been able to recognize the device in PSOC Creator. After confirming my pin connections over and over again, I was trying a few things and found that it WOULD recognize the device if I used a 3.3V supply on this. Has anybody else seen this? / How can I get it to work with my 5V supply? Thanks.
Show LessI am making development board of CYBLE - 214009 - 00 that can be connected to breadboard.
Because it is high at the agency, I would like to purchase CYBLE - 214009 - 00 at the Cypress Store.
However, Cypress Store does not know how to purchase CYBLE - 214009 - 00.
Is there anyone who knows how to purchase?
私はブレッドボードに接続できるシンプルなCYBLE - 214009 - 00のボードを作っています。
CYBLE - 214009 - 00は代理店では値が張るので、サイプレスストアで購入したいと考えています。
しかしながらサイプレスストアでのCYBLE - 214009 - 00の購入の仕方が分かりません。
誰か購入方法を知っている人はいませんか?
Show LessHello,
The DTM/HCI example works fine for speeds up to 115200 baud.
However for higher speeds the systems fails due to improper clock setup.
How to setup the clock for e.g. 460800 baud?
At 24Mhz and divider 3 i get: 8Mhz which is a bit from the optimal 7.373 which will give bit errors once in a while (and it does).
Changing the IMO to 30Mhz gives a nicer 7,5Mhz.... but then it stops working all together. Not sure why. Should work better, but the entire system seems to stop working.
It is a bit unfortunate that the DTM does not work out-of-the-box with anything above 115200. At 115200 it is a bit hard to use the "data packet length extension" for anything as that would require much higher bandwidth at full speed.
How do i resolve this, so i can run faster on the UART in the DTM/HCI example? Is this a bug and/or missing feature?
/pedro
Show LessHello,
I have a project where I am attempting to use SPI to transmit information between two PSOC devices. The device on the white circuit board is a CY8C4245PVI-482.
The black circuit board is a CY8CKIT-059.
The CY8CKIT-059 is a SPI master that requests information be sent from the CY8C4245PVI-482 slave upon a string command. The data request is terminated by a line break.
As my code stands now, the data request arrives from the master intact and successfully executes the command parse routine in the firmware for the CY8C4245PVI-482 slave. The slave is then supposed to send a serial number back to the master. The characters "ABC\n" never arrive back reliably or intact to the master.
I checked activity on the MISO and all the lines. It all looks OK, so I think there is some poor code practice I am using. Please assist me in resolving the data transfer issue I am having back from the slave to the master. I have the project files attached for both the slave and master. hopefully what I am doing hardware wise and my code is self-explanatory.
Thanks
Show LessHi I have a strange issue.
I have a fairly simple psoc4 (cy8c4248 44 tqfp) design that is adapted from the motor drive reference (cy8ckit-042) and it's been working OK until under load. Under load, there have been a few tearful moments, exploding FETs etc, and I've not been able to put my finger on how and why.
One things that is consistently happening (other than smoke) is the the xres pin drives LOW, like the psoc4 is actively driving it. The parts aren't dead, and if I short xres to 3.3V they seem to work, I can talk to them using I2C and the bridge control software when xres shorted to 3.3V. This has happened on perfectly good units that have not leaked smoke from the h-bridge fets, and on ones that have suffered damage on the power drive stages. It seems to happen after a period of use/testing, never straight up.
So I'm thinking that the xres problem, might be causing a chip reset at a bad time, tristate drive, destroying my fets which aren't turning off gracefully. (I'm correcting that on next pcb rev of course but still need to hunt down this problem.) That was different to my initial thought that the even that killed the fets, also killed the psoc and xres low was chip damage.
The impedance of the low drive is strong but not short circuit, < 1k, probably less. A short to 3.3V does not make anything hot, I see now permanent issue. When I short xres to 3.3V up to 35mA can run (!) but then decays to 0. The xres pin has a top and tail BAT54 for a little more protection, and no capacitor.
Any ideas? POR, BOD? damage to the device? System sees 24V for testing, has been tested for a short period with 42V.
What kind of failure modes are there that look similar? Any errata? Or is there something like the p1[6] pin xres behaviour on psoc 4000 parts?
A lot of thanks in advance for your help.
Show LessOn boot up we are calling CyBle_GapRemoveOldestDeviceFromBondedList if the number of current bonded devices = 4, to allow rolling use of the last three bonded devices.
We do this curing CYBLE_EVT_STACK_ON. We get the number of bonded devices by calling CyBle_GapGetBondedDevicesList, and then remove the oldest if equal to four.
This works most of the time. We have experienced a number of times in testing when some number of different devices (more than 4) have been bonded. When in this state, we get CYBLE_EVT_GAP_DEVICE_DISCONNECTED with an event reason of 0x16. Once this occurs, we can only connect to the last three bonded devices. Our CYBL11573 based device stays in this state -- only connecting with last 3 bonded, 0x16 error if attempting to connect/bond to a 4th until we reflash the firmware.
CYBL11573 running BLE stack V3.10.
Show LessHello colleagues,
Event CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT is never generated. CYBLE_EVT_STACK_ON, CYBLE_EVT_GAPP_ADVERTISEMENT_START_STOP, CYBLE_EVT_GAP_DEVICE_CONNECTED and CYBLE_EVT_GAP_DEVICE_DISCONNECTED are generated correctly but not CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT. From the BLE Datasheet, I learned that probably I need to invoke the function CyBle_GapcStartScan(ScanType) but that is not recognized by PSoC Creator. What can I do to solve the issue?
Below is a piece of my code with all the events:
case CYBLE_EVT_STACK_ON:
CyBle_GappStartAdvertisement(CYBLE_ADVERTISING_FAST);
UART_PutString("Enter in Stack ON\r\n");
break;
case CYBLE_EVT_GAPP_ADVERTISEMENT_START_STOP:
UART_PutString("Enter in Start Stop\r\n");
break;
case CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT:
UART_PutString("Enter in Scan Progress\r\n");
break;
case CYBLE_EVT_GAP_DEVICE_CONNECTED:
UART_PutString("Enter in Device Connected\r\n");
break;
case CYBLE_EVT_GAP_DEVICE_DISCONNECTED:
UART_PutString("Enter in Device Disconnected\r\n");
If I set ScanInfo->scanType=0x01 (being CYBLE_GAPC_DISC_INFO_T *ScanInfo;) in the main, then the Stack is not started and CYBLE_EVT_STACK_ON event is not generated,
Peter
Show Less