PSoC™ 6 Forum Discussions
I am using PSOC6 CY8C6137BZI. I want to have connect total 16 device which are controlled by SPI. There are two options available for that,
1. Since there are 9 SCB in it I can use 4 SPI with 4 slave select signals. But I am unsure that whether I can change the Slave Select frequently in the program using Cy_SCB_SPI_SetActiveSlaveSelect(SPI_1_HW, CY_SCB_SPI_SLAVE_SELECTx) or not. Does anyone knows about it?
I dont have the development kit to test it.
2. Second way is I use 1 SPI module with 1 slave select and pass it through demux having 16 channel. But in that case I am unable to build it. Error comes fit:m0049:Pin guidance unavailable: Invalid connection for output "\SPI_1:SCB\:spi_select_0" connected to "Net_116:main_0". What is the issue I am not able to understand. I did pass through the not gate but I failed.
I am uploading the workspace for reference.
I get following error message when trying to build the project:
The given PDL path '' is invalid. Unable to find required PDSC file.
What does this mean and how to fix it?Show Less
I have used these 2 code examples to download a large firmware image from a host to PSoC63 using Creator 4.3
It downloads only 1 page and stops.
I am looking for how to download multiple pages to the exreranal flash.
My firmware image is over 10 MBytes
======================== Test Cases =================================================
CE213903 – PSoC 6 MCU Basic Device Firmware Update (DFU)
CE220959 – PSoC 6 MCU Bluetooth Low Energy (BLE)Device Firmware Update (DFU) with External Memory
I appreciate your feedback
This is using CE213903
Trying to download a .cyacd2 using the Bootloader Host tool in Creator 4.3
08:49:18 PM - program Started
08:49:19 PM - The operation has timed out.
08:49:19 PM - Communication port reported error 'Unable to read data from the target device'.
08:49:19 PM - program failed in 1005 ms.Show Less
We are providing 1.8V on pin VBACKUP during main power loss and have a 32.768 kHz crystal on pins P0.0 and P0.1 of a CY8C6247BZI-D54. We have used the example RTC code, set the time and then removed main power. Verified VBACKUP is still present and the crystal is oscillating. Left alone for about an hour. Restored main power and read the RTC over UART. It jumped back about a day.
Any explanations for this?
Another question is, could we provide the clock using a digital oscillator instead of a crystal?
Thank you in advance for any help.Show Less
We need to add another I2S component.
So I followed the KBA229971
And I could manage to generate an I2S v2.70 in UDB
But as I don't want to corrupt this project, I duplicated the project using Copy and Paste
Then I tried to rename the project something else
After the project was renamed, the symbol of I2S component does not seem to be happy.
I think that probably I missed something in the KBA or some additional protection/modification is required for the component.
Could someone teach us how to avoid or fix this problem?
I see that the SCB in UART mode can be set up to talk to an SD Card in ISO7815 mode. I want to put it on product that plugs into and Smart Card slot so I want it to act like an SD Card.
Is that possible?
This is a PSOC6 application.
Arrow Infineon SpecialistShow Less
Hi there, I am new to development with the PSoC 6 hardware.
I am using a CY8CKIT-062-BLE Rev B and following along with the PSoC 6 101 lessons. I am currently on PSoC 6 101: Lesson 1-3 Hello World. My problem is that the LED will not blink after the board is programmed. I have followed the instructions exactly and have made sure the board is set up. I have gone through the kit datasheets to make sure all the onboard switches are set properly.
Where can I start troubleshooting? I don't know what else I can do here.Show Less
Are there any library functions in the Creator ecosystem for extracting year, month, day, hours, minutes, seconds from a 32-bit unix time?
Ed H.Show Less
I have been trying to get the RTC on the CY8CKIT-062-WiFi-BT to retain time over power cycles, though with no success this far.
I have found suggested solutions in these discussions which I tried to reproduce:
though still had no success in getting it to work. Some of the proposed solutions refer to settings in PSoC Creator. I'm, however, using ModusToolbox. This means I had to try to recreate the (assumed) behavior of these solutions using the SysPm PDL.
Starting from the RTC Basics example in MTB, here is what I tried:
1. Comment out
in cyhal_rtc_init() to prevent the clock from being reset after a power cycle
2. Charge SuperCap using Cy_SysPm_BackupSuperCapCharge(CY_SYSPM_SC_CHARGE_ENABLE); (and pre-charged using a 100 Ohm resistor). Supercap reads 1.6V.
3. It is suggested to change the vBackupSource to dedicated supply in the accepted answer to the first discussion. I'm not sure how to achieve the same thing using SysPm. Cy_SysPm_BackupSetSupply(CY_SYSPM_VDDBACKUP_VBACKUP); seems like the best candidate for this?
4. Explicitly enable PMIC as suggested for PSoC Creator in one of the discussions:
(This should be the default configuration anyway and does not change anything about the observed behaviour)
5. Set SW7 to SuperCap position
The board power seems to glitch immediately as soon as I set SW7 to the supercap position. I can only fix it by setting SW7 back to the KitProg position.
I assume this is because the PMIC circuitry is supposed the disable Vddd on power loss but somehow shorts it to VBackup instead?
The board is Rev.10, if that makes a difference.
EDIT: Hardware Revision is actually Rev.04, not 10.
Nachricht geändert durch Elias TrommerShow Less