PSoC™ 4 Forum Discussions
I've been running in circles trying to get an arrangement working which would allow me to send debugging information from a target board using a PSoC4 BLE chip to a laptop computer when using MINIPROG3. There are a number of comments and articles that talk about this but I've been unsuccessful at making any of them work. Further, when it seemed like I might have a solution it came at the expense of disabling the use of the regular debugging and programming functions.
Finally, I decided to set up a completely separate path from that of the MINIPROG3. The attached file is a very simple description of how this can be done along with a program that actually works in this regard. It uses an inexpensive FTDI Serial to UART converter cable available from Amazon.com. The connections and how to make it work are described at the top of the program. I have taken this approach to showing how I did it since I've often been frustrated with answers to questions that assume knowledge that I don't yet have. Perhaps this will be of help to someone else. I plan to add a two pin connector to every board I design to allow connection of the FTDI cable for future use. (At least until Cypress adds the capability to the MINIPROG3).
Dennis Coburn
Show LessHello,
Do SWDIO and SWDCLK for PSoC4/4S/4A need external pull-up resistors in case of the mass production?
And What ohms do you recommend?
Best regards,
Yocchi
Show LessHello,
I can see next in the BLE_StackGap.h file:
/* Maximum number of Remote Devices */
#define CYBLE_GAP_MAX_BONDED_DEVICE 0x04u
#define CYBLE_GAP_SIZE_OF_WHITELIST 0x08u
#define CYBLE_GAP_SIZE_OF_RESOLVING_LIST 0x08u
/* This is kept for backward compatibility, will be obsolete in future */
#define CYBLE_MAX_WHITELIST_ENTRIES 0x04u
Is it a hardware limit ? or size of lists can be increased modifying those defines ?
I'm working with CYBLE-212006-01. Is those values right for this device ?
Thanks in advance,
Asier.
Show LessSometime within the last couple of years I read that it is possible to get serial data from the Tx output of a UART in a PSoC 4 to a terminal program running on a laptop through a MINIPROG3 connected between the target and the laptop. As I recall it said to connect the UART 's Tx pin to pin 6 on the MINIPROG3's 10 pin connector and use the Bridge Control Panel on the laptop.
Has anyone ever succeeded in making this arrangement work? if so, would you be kind enough to explain to me how to make it happen?
Thanks for your help,
Dennis
Show LessHi everyone,
I wish detect the stack overflow in psoc 4 CY8C4245LQI-483.
I tried this :
1- initialize a stack pointer to the last row of SRAM (i found SRAM address range from 0x20000000 to 0x20000FFF in PSOC4 architecture TRM. The stack is in upper SRAM).
char* stackPtr = (char*) 0x20000FFF.
2- give it a value:
*stackPtr = 0xAA;
3- during execution, check for changing its value:
if(*stackPtr != 0xAA)
{
flag_stack_overflow = true;
}
It does not working.
Unfortunately I cannot use the debug mode because the used flash is over the 90% and the debug exceeds the available flash.
Thanks for your help!
Show LessCan I use Pin 11 and 12 for UART (Tx Rx) routing in IC CY8C3866LTI-068?
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 |