PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
Hi,
for power saving I changed the SWD pins to GPIO like in the application note but since then psoc creator doesn't show the target MCU and not even psoc programmer can connect to it. This happend on my custom board programmed with kitprog from CY8KIT-043 and also on CY8CKIT-062-BLE Kit.
I just reproduced it with my CY8KIT-043, after flashing it with SWD pins changed to GPIO it can't be programmed..
The Kitprog doesn't seem to reset the psoc (attatched oscilloscope). Is the Kitprog not able to recover my psoc 4?
Please help, how do I recover my PSOCs?
Show LessHello everyone.
I'm using CYBLE-012011-00, can I execute software reset when the power is turned on?
I wrote program that control NAND flash memory(LSM330TR) but I couldn't execute block erase command without execute software reset, CySoftwareReset() after the power is turned on.
The NAND is in un protected mode.
Can anyone help me solve this problem?
Show LessHere we go again, another query regarding firmware versions for using Cysmart with a new Cy5677 dongle on a Windows 10 x64 machine.
PSOC Programmer initially prompted me to update to Kitprog 2.17, and I've since learned, according to the forums here, that breaks Cysmart, so I've reflashed with C:\Program Files (x86)\Cypress\CY8CKIT-042-BLE Kit\1.0\Firmware\Programmer\KitProg\KitProg.cyacd, and then with the latest Cysmart firmware from the cysmart installation, but I still get Unsupported Device (COM50) in the target selection dialog of Cysmart.
I'm using the KitProg USB-UART driver.
I've tested with the upgraded Kitprog 2.17 as well, but no change.
Any suggestions?
PSOC Programmer output:
Show Less
Program Finished at 9:35:40 AM | | Programming Succeeded | Doing Checksum | Doing Protect | Verifying of Flash Succeeded... | Verifying of Flash Starting... | Programming of Flash Succeeded... | Programming of Flash Starting... | Erase Succeeded Device set to CYBL11573-56LQXI at 9:35:15 AM | 262144 FLASH bytes Device Family set to CY8C4xxx-BLE at 9:35:15 AM | | Automatically Detected Device: CYBL11573-56LQXI Program Requested at 9:35:15 AM | Active HEX file set at 9:35:12 AM | C:\Program Files (x86)\Cypress\CySmart\1.2\dongle\CY5677\BLE_4_2_Dongle_CySmart_256K.hex | Please navigate to the Utilities tab and click the Upgrade Firmware button Port Opened with Warnings at 9:34:43 AM | KitProg version Expecting 2.17, but found 2.14. Opening Port at 9:34:42 AM | Device set to CYBL11573-56LQXI at 9:34:42 AM | 262144 FLASH bytes Device Family set to CY8C4xxx-BLE at 9:34:41 AM |
Hello,
We're using the CY5677 BLE dongle on one of our projects. It works great most of time 🙂
One issue is that sometimes it goes into a state where we cannot connect to it anymore, TryGetCySmartDongleCommunicator() returns "Not a valid CySmart dongle!".
This unfortunately is a showstopper for us because we won't have physical access to machine to press the 'reset' button or power cycle the dongle.
- Could you please share with us some insights on why/when does the dongle go into this state? Maybe we can handle those cases better from our code.
- Is there a way for us to automatically (remotely) reset the dongle when this happens?
Thank you,
Gabriel
Show LessHello,
I'm using psoc4 ble dk kit and doing some projects.
For my project, I need to get 128-bit UUID (Custom Service UUID maybe) of other BLE devices.
So my psoc4 ble needs to act as a central or an observer device.
However, in the 'Observer' examples, psoc4 ble only gets information about
-Target's addr
-Target's type(non-connectable, something like that)
Also it seems like CYBLE_GAPC_ADV_EVENT don't include 128-bit UUID data.
So is there any API or any ways to check other devices' 128-bit UUID with psoc4 ble?
Please let me know if there is a way.
Thank you.
Show LessHello!
I would like to know what I could do to connect 2 psoc cards type cy8ckit-049-42xx and send the data to the analyzer application in this case will be a message for each card.
Thank you very much for your attention, I hope your prompt response.
Show LessI am using Psoc 4 with BLE (4200).
It resets unexpectedly and on boot show reset cause : 0
0 is none of the below: it is not WDT(1) , it is not SYS (8) , it is not SW (16)
#define CY_SYS_RESET_WDT_SHIFT (0u)
#define CY_SYS_RESET_PROTFAULT_SHIFT (3u)
#define CY_SYS_RESET_SW_SHIFT (4u)
#define CY_SYS_RESET_WDT ((uint32)1u << CY_SYS_RESET_WDT_SHIFT )
#define CY_SYS_RESET_PROTFAULT ((uint32)1u << CY_SYS_RESET_PROTFAULT_SHIFT)
#define CY_SYS_RESET_SW ((uint32)1u << CY_SYS_RESET_SW_SHIFT )
can you tell me please what can it be?
Show LessHello,
I have an input pin connected to a switch. Pressing the switch enables power to the PSoC4 chip (i.e. PSoC goes through complete bootloading process and then executes the main()).
The processor is initially cut off from the power source. Pressing the button generates a rising edge which turns the processor ON, however this rising edge of the button is also being used to turn an LED ON. Since the processor is booting, this rising edge does not generate interrupt and the LED is not turned ON. This is understandable because at that very instance, the processor isn't powered. So to turn the LED ON with the same pulse, I'm using the falling edge to generate an interrupt which turns the LED ON. However, I am wondering if there is any way to capture the same rising edge, i.e. if I can add some component in my top design to delay the pulse or repeat it.
Currently, I turn the LED ON on rising edge of button press, but just for this "special case" I am using the falling edge.
I would greatly appreciate for any ideas.
Thanks,
Show LessIn Document PSoC 4100/4200 Family PSoC 4 Registers TRM ,Spec #001-85847 RevA page 474 - Chapter 19.1.11 PWR_BOD_KEY.
It is described that KEY16 shall be copied to key, but is meant with key?
Show Less