PSoC™ 6 Forum Discussions

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.

Best Regards,

Mike Roberts

Arrow Infineon Specialist

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.

Are there any library functions in the Creator ecosystem for extracting year, month, day, hours, minutes, seconds from a 32-bit unix time?

Thanks,

Ed H.

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:

Battery/Super Capacitor backup power / RTC

VBackup and Super Cap for RTC to work

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 Trommer

Hello,

We would like to select one MCU Part Number which has minimum below configurations set.

Digital Input/output Pin (GPIO): 45 Pins

Analog Input Pins: 20

No of UART Communication: more than 4

No of SPI Communication: more than 2

No of 16-bit/32-bit Timers: more than 7

No of edge interrupts: more than 1

No of Input Capture Pins: more than 1

Watchdog Timer: YES

Code guard security: YES

CPU Speed: more than 50 MIPS

Flash Memory: more than 512 KB

CRC Module: YES

Architecture: 16-bit / 32-bit RISC architecture

Programming Language: C & C++

No of Pin counts: more than 80

Note: 1) Above pin requirements are not included programming pins and power supply pins, so consider it separately

                2) Consider each requirement pin as separate pin

Please suggest us suitable part number for same.

We already go through to your parametric search results but we need more help on this so we generated this query.

Thanks, and Best Regards,

Dutt Panchal

I am trying to reuse some tasks/files from my main app (App1-Main) in a second stand alone app that will be used during manufacturing to store bits maps in the system flash (AppX-BitmapUtility). But... the linker insists that SpiMasterTaskHandle is undefined even though: 1) it is defined in main_cm4.c and 2) it shows up in the linker map file.

It MAY have something to do with the fact that the main_cm4.h is defined up in App1-Main, but for the life of me I can't see why that should make any difference. I have been trying to find a work-around for this issue for a couple of days to no avail.

In the attached workspace, most of App1-Main has been stripped out for propriety reasons and it will not build successfully, but that shouldn't matter. I still get he same error in my complete system.

Any recommendations would be greatly appreciated.

Ed H.

I have a application that requires continuous execution from the CM4. Occasionally data is placed into flash by the CM0 , which blocks code execution by the CM4 during the flash write, even during a non-blocking flash write. Is there any way to have CM4 code execution continue uninhibited during the CM0  flash storage event?