PSoC™ 4 Forum Discussions
Hello,
I have CY8CKIT-042 PSoC® 4 Pioneer Kit. I need to configure this kit as master with SPI mode and need to drive some slave device.
I have got some example code from code samples, which used SCB1 configured as SPI(master) and have tested loopback(MOSI to MISO) which worked fine.
Now I need to configure SCB1_SPI as master which drives 24MHz to slave, as below.
But I am unable to do it. I have configured SPI as below. As per the TRM, this configuration must produce 24MHz clock for SPI but it is driving only 4MHz.
But in the clock section, I can see 24MHz for SPIM_SCBCLK.
Why there is a difference in SPIM_SCBCLK(24MHz) and SPIM:sclk_m(4MHz) which is driving?
Any other configurations, which are affecting the desired frequency of SPI? Please suggest.
Any suggestion should be grateful.
Show Less@ll FORTH programmers and those who want to become:
From 17. August to 18. August 2019 is the Maker Faire in Hannover. In this Time will the German FORTH-Gesellschaft show all implementations of Mecrisp-Stellaris-FORTH on PSoC4 and PSoC5*. FORTH is a compiler language with an interpreter and make interactive C possible. You can see the whole workflow to programming PSoC4/5 in FORTH combined with C-API's. For more Information search to 'FORTH' on this page or follow this link: https://sourceforge.net/projects/mecrisp/files/Cypress/
Klaus
*Mecrisp-Stellaris-FORTH is available for following Eva-Kits:
Board: PSoC:
CY8CKIT-043 -> cy8c4247azi
CY8CKIT-046 -> cy8c4248bzi
CY8CKIT-049 -> cy8c4245axi
CY8CKIT-050 -> cy8c5868axi
CY8CKIT-059 -> cy8c5888lti
FreeSoC2 -> cy8c5888axi
Show LessHello all,
I am using cyble-014008-00 and I have a characteristic with notify property: when the characteristic is written a notification with the response is sent back
I am using cysmart to connect and read/write
Here you can find that notify is disabled, but the notification is received:
read Client Characteristic Configuration (ccc)
[15:20:11:337] : 'Read Characteristic Descriptor' request sent
[15:20:11:337] : Attribute Handle: 0x0010
[15:20:11:338] : 'Command Status' event received
[15:20:11:338] : Status: BLE_STATUS_OK
[15:20:11:356] : 'Read Characteristic Descriptor Response' event received
[15:20:11:356] : Value: [00:00]
[15:20:11:374] : 'Command Complete' event received
[15:20:11:374] : Status: BLE_STATUS_OK
write
[15:20:26:790] : 'Write Characteristic Value' request sent
[15:20:26:790] : Attribute Handle: 0x000E
[15:20:26:790] : Value: [7B:22:54:53:22:3A:31:31:7D]
[15:20:26:791] : 'Command Status' event received
[15:20:26:791] : Status: BLE_STATUS_OK
[15:20:26:808] : 'Command Complete' event received
[15:20:26:808] : Status: BLE_STATUS_OK
notify
[15:20:26:836] : 'Characteristic Value Notification' event received
[15:20:26:836] : Attribute Handle: 0x000E
[15:20:26:836] : Value: [7B:22:52:43:22:3A:30:2C:22:54:53:22:3A:31:31:2C:22:4D:50:56:22:3A:22:32:2E:33:22:7D]
It seems that CyBle_GattsNotification does not check ccc
How can I read ccc and send the notify only if it is enabled?
Show LessPlease answer below.
The same question is written in English and Japanese.
・English
What can I do with "Unprotected" (U) and "Full Protection" (W)?
think as follows. Is this correct?
"Unprotected" (U) → bootloader, self-rewritable
"Full Protection" (W) → bootloader, self-rewriting not possible
・Japanese(日本語)
“Unprotected”(U)、“Full Protection”(W)はどのようなことができる設定ですか?
以下、理解で間違いないでしょうか?
“Unprotected”(U)→bootloader,自己書き換え可能
“Full Protection”(W)→bootloader,自己書き換え不可能
Regards
Show LessHi,
I'm using host processor communicates via i2c to configure CY8CMBR3116 device. After sending 128bytes of configuration, I send command 0x02 to CTRL_CMD register. Documentation says that write operation takes 220ms, and after this time there should be 0x00 in CTRL_CMD register. I get 0x00 but after about 600ms. After this, device works correctly. Is this correct behavior? Mayby I should not check CTRL_CMD register for 0x00, only wait 250 ms and check CTRL_CMD_STATUS?
Show LessHi,
Following on from this thread: How do you determine brown out detection event?
How do you actually detect the brown out? It appears that when the MCU enters hibernate and then comes out, that this flag is set.
Is there a pattern for accurately detecting a brown out, as the simple pattern of checking if key==0x3A71 doesn't always indicate a brown out?
Thanks, Dave
Show LessDear community,
We are using CY5677 to connect with a BLE amplifier.
The amplifier is controlled by a uC which also manages all the communication. Unfortunately, I don't have access to the FW.
The idea is to stream data from the BLE amplifier to the PC.
The manufacturer of the amplifier worked with CySmart app and the streaming is possible in the following manner:
1. Discover all attributes.
2. Write 0x01 to Characteristic Handle 0x026.
3. Data appears and updates asynchronously at Characteristic Handle 0x02C. Its length is fixed.
(No CCCD Handle is used here! I mean, that the streaming also works even if notifications were not enabled in CySmart GUI!)
There is another handle (0x033 in my case) that provides battery & temperature status every 5 seconds~.
To receive these updates asynchronously I do need to enable notifications for this characteristic (it's CCCD handle is 0x034).
What we want to do is this:
1. Create a small app that will automatically connect to the BLE amplifier.
2. Start streaming data upon request into a textbox (let's start with that).
The attached VS solution is based heavily on this: How to send Scan_Request's from CY5677 Dongle with the C# API from Cypress
What we have accomplished thus far and is implemented in the attached solution:
1. Connect to the dongle.
2. Scan and connect to the device using its hardware address.
3. Read a characteristic value.
4. Write to a characteristic value.
5. Enable and receive notifications by writing 0x0100 to the CCCD handle 0x034 to see the battery & temperature data from characteristic handle 0x033 (using the OnCharacteristicChanged callback).
However, I do not receive any updates from 0x026 if I write 0x01 to characteristic handle 0x02C. Additionally, I lose the ability to read/write characteristic values.
The steps to solve this so far were:
1. Debug the above solution.
2. Try to locate the thread/method which is locked or stuck after I write 0x01 to char. handle 0x026 and try to figure out why I don't get the OnCharacteristicChanged callback.
So, streaming works with CySmart app but does not work with the attached simplified example. Question is why?
What am I missing? What are your suggestions?
Thankfully,
Stas
Show LessI was doing some searching on how to route the internal 1.024V VREF to an external pin 1[7] and found a link to an old blog that is now dead. Any pointers would be appreciated.
Dead link: ...cypress.com/blog/psoc-hacker-blog/connect-vref-pin-psoc4
Show LessHello,
I refer the section of 5.3.2.2.1 Sense Clock Related Parameters.
it describe that the typical value of the GPIO resistance is 500 Ω.
Please tell me the spec of min/max of GPIO resistance.
If there is no specification about it, what % of error should I assume?
PSoC® 4 and PSoC 6 MCU CapSense® Design Guide
Document Number. 001-85951 Rev. *W
https://www.cypress.com/file/46081/download
Best Regards,
Naoaki Morimoto
PSoC® 4 and PSoC 6 MCU CapSense® Design Guide
Document Number. 001-85951 Rev. *W
https://www.cypress.com/file/46081/download
Show LessHello,
i have some issues with my coding. I used the RTD Measure Example and changed it for my CY8CKIT-042-BLE. The values are changing but not as expected
I don't know where my mistake is. Could you give me support?
Thanks
Show Less