PSoC™ 5, 3 & 1 Forum Discussions
Hey,
I am new to development on the PSoC platform and I am attempting to configure UART on this device. It is a PSOC5LP - 050 board. I'm unable to configure the COM port I am supposed to read it on, because it does not show anything on device manager about which virtual COM port I should connect.
I am able to program other components and I have already worked on a few applications which are working fine. Sending a screenshot of my device manager. On PSOC programmer also, the Upgrade firmware option is 'greyed-out'. Any advice is appreciated.
EDIT: I have checked the example documentation and connected the RS-232 with the related Pinouts to the Rx and Tx pin and still nothing appears on my COM port.
Show LessI have many kitprog (ver1) from ther CY8CKIT-059, These have been broken off from the kit. The kitprog does not have connectivity to the SWD or JTAG pins, so the only method of programming the kitprog is by using the bootloader installed from the programmer. As custom bootloader may resolve my issue below but I can't change the bootloader.
The issue is I can successfully bootload host a custom program many times successfully, but then later when adding functionality to the bootloadable program I get an bootloader host downloading issues that prevent downloading.
I am assuming the original kitprog has not been verified correctly and there is an incompatibility. I do have a couple questions that maybe someone can answer that has been though this issue,
I am using the kitprog hardware (not 2) with the latest software 2.2.1 The cy9ckit-059 says this needs to be 2.20 or later. The documents for the original kitprog user manual (ver-I 2018) says the bootloadable needs to start its program at 0x0002800. However the newest kitprog2 user manual has the starting address for bootloadables at 0x0003200. Is it possible to findout the flash size of the locked part for kitprog and kitprog2?
This value is need to use the kitprog for custom applications, but only cypress has accessibility to the kitprog and kitprog2 source.
Brian
Show Less
We have a design that is based off the CY8CPROTO-062-WiFi board. Our board has a built-in KitProg3 just like the the proto board. We need to program the CY8C5868LTI-LP039 with the KitProg3 firmware. What tool should we use to do this? Does the PSOC5 come from the factory programmed with a bootloader that will accept the KitProg3 image via USB?
I was able to program a KitProg3.hex file into real KitProg3 board by connecting a MiniProg4 to the PSOC5 XRES, P1.0 and P1.1 pins. Unfortunately, the manufacturer failed to route those pins on our board. Our only option to program the PSOC5 is with USB. Is it possible?
Thanks in advance.
Show Less
Hi,
Could you please help me with Schematic and firmware design support to drive Segment LEDs using the PSoC 5LP chip?
We have to drive a seven-digit seven segment display with various segment current from 16-bit serial input.
Regards,
Mari
Show Less
Hi all,
Could someone please offer a good tutorial on how to port the FreeRTOS library onto the CY8C5888LTI-LP097 microcontroller? I was given one previously, however I was missing one file.
Show Lessi got a note from net,(AN2163), i want to get temp by ds18b20, onewire bus ,but the note said need two pins ,i want to make sure ,this Method is right
my cpu is cy8c27443,my sch pin1 and pin2 can be use , that ok? thank you
Show LessHi All,
I am Using cy8ckit-059 kit. I want to read/write data from a file present in the SD card. for that I am using FATfs file system.
I am trying one example from here
https://github.com/hackingchips/PSoC_FatFs/tree/master/Examples/PSoC5LP_FatFs
But I am getting this error
error: (FR_NOT_READY) sdcard not ready.
has anyone used FATfs library for ( micro SD card ~8gb) ? or is there any working example available with Fatfs file system
Please suggest me to resolve this error.
Thanks
Show Less
Hi,
Is it possible to run CY8Ckit-059 with 3.3V at the pins? Right now the voltage is 4.8V.
Hi Gents,
This question is in reference to https://www.cypress.com/documentation/application-notes/an60317-psoc-3-and-psoc-5lp-i2c-bootloader
When I try and run the provided API it errors on the Bootloader Version replied back by the PSOC3 we use.
The PSOC3 is replying back with the bytes 60,1,1. Whereas, the API is looking for 0x000000 :
int CyBtldr_StartBootloadOperation_PSoC3(unsigned long expSiId, unsigned char expSiRev, unsigned long* blVer)
{
const unsigned long SUPPORTED_BOOTLOADER = 0x000000;
[...]
}
Why is the API looking for 0x000000 when the PSOC3 bootloader is hardcoded with 60,1,1 ?!
Show Less
I walked into a PSOC 5LP design where it was assumed the SAR was running a full 12-bit unsigned resolution in single ended mode. This didn't appear to be the case and after struggling with settings both high level as well as low level register settings I can't seem to make it work as a 12-bit single-ended unsigned ADC. Is this possible with this device? If so, please tell me how to use it that way. Also, please add this question to the list of FAQs for these devices.
Show Less