PSoC™ 5, 3 & 1 Forum Discussions
text.format{('custom.tabs.no.results')}
Hi,
We are using PSoC LP 5. Some pins are working differently from others and it confused me.
One pin, pin18 (P5-2, GPIO) drive mode is set to resistive pull up, initial value high, and it stays high; while another pin 29(P12-6, SIO) has the same drive mode and initial value, but it stays low. There is nothing different from both HW and SW perspective in our design. What is the internal difference between these two pins?
Regards,
Winston
Show LessHello.
An error occurred while using MiniProg4.
phenomenon
We have continuously updated the firmware of the EVK board.
After some successful updates, I suddenly get a Fail message as shown in the picture below and I can't update the EVK board.
I want to know the solution.
Already applied method
Voltage change, J6 connection check of EVK board
thank you.
Show LessWhere can I find the drivers for Miniprog 3?
On the web page for the device there is no link to download???
Why is this made so difficult? A direct link to the drivers should be on the page.
Show LessSo I've got a really weird issue with USBFS on PSoC5LP. Currently trying to determine if it's something on the PSoC side or an issue with the HID API I am using on the PC side.
I've got the PSoC acting as a 64-byte Generic HID:
- EP1 IN, 10ms, 64-bytes, INT
- EP2 OUT, 10ms, 64-bytes, INT
The issue looks to be on EP2, where I have the following code to handle the endpoints. This is called regularly every time through the main loop for as long as the USB device is connected. It follows for the most part the same pattern for servicing the endpoints as laid out in AN82072 Appendix A (pg 58) :
void Process_USB (void){
static bool is_connected = false;
is_connected = USB_UpdateConnection(); //Are we connected to a host?
if (is_connected){
/*IN Buffer is data going IN to Host PC*/
if (USBFS_bGetEPState(USBFS_EP1) == USBFS_IN_BUFFER_EMPTY){
USBFS_LoadInEP(USBFS_EP1, USB_HIDInBuffer, 64);
memset(USB_HIDInBuffer,0x00,64);
USBFS_EnableOutEP(USBFS_EP2);
}
/*OUT Buffer is data coming OUT of Host PC*/
if (USBFS_bGetEPState(USBFS_EP2) == USBFS_OUT_BUFFER_FULL){
USBFS_ReadOutEP(USBFS_EP2, USB_HIDOutBuffer, 64);
/*Incoming data processing SNIPPED*/
memset(USB_HIDOutBuffer,0x00,65);
USBFS_EnableOutEP(USBFS_EP2); //Re-Arm the OUT Endpoint
}
}
}
What I'm seeing is that on typical USB 2.0 ports, there's no problem, endpoint data gets across fine, and when data is received by the PSoC, the (USBFS_bGetEPState(USBFS_EP2) == USBFS_OUT_BUFFER_FULL) evaluates to true and the processing code is entered where a message is queued to be sent back on EP1.
What I'm seeing though, is that when connected to a USB3 port, the device is recognized properly by windows and enumerates, but the processing code never fires since bGetEPState(USBFS_EP2) never evaluates to USBFS_OUT_BUFFER_FULL when a command is sent.
I have a USB protocol analyzer I hooked up to see if I could find anything out and I can see the OUT EP with the command (0x05 0x06) makes it out onto the EP, but why is it not being properly seen by the PSoC? I have no idea why this is the case, or why it seems to only happen with USB3 ports (tested on 2 different PCs)?
On USB 2 Port you can see the OUT EP carrying the command 0x05 0x06 and the PSoC response on EP1 shortly after:
On USB 3 Port you can see the OUT EP carrying the command 0x05 0x06, but the PSoC never responds:
Has anyone seen anything like this in their experience? I'm willing to believe it could be something with the HID API I am using on the PC side (HidSharp), but I want to rule out anything on the PSoC side as well if I can. The fact that I can actually see the data coming from the PC through the Analyzer (A Beagle 12, FWIW) makes me lean toward something on the PSoC side not properly recognizing that data has come in through EP2. Anything like a USBFS status register I could look at to maybe provide a clue as to what's happening here?
As far as I know, a USB2 cable/device connected to a USB3 port should just behave as a USB2 port would. The port is physically designed to only connect VUSB/D+/D-/GND when a 2.0 cable is plugged in so the issue tracking only with USB3 ports is really strange.
Any thoughts are appreciated! Thanks!
Show LessI wrote a blog post on programming the KitProg finger stub board on the CY8CKit-059. I chopped a USB Extender cable and use one additional 30 gauge wire to allow for the reset, and was able to load arbitrary code into the finger stub's PSOC5LP.
I also covered using fw-loader to upgrade the firmware on KitProg2 and KitProg3.
The article is here: https://socmaker.com/?p=1108
Show Less
Our products have always used PSOC5lp but we are hit hard with the shortage. We procured 3000 chips but need more for expansion but only have some coming in 52 weeks from Arrow. Is there a secret stash Cypress can help me out with? We are willing to redesign the firmware for something along the lines of CY8C5468AXI in 100 qfp. Thanks for any leads.
Show LessHello Community,
I have been working on a project, and with some help from people here, I have been able to get it together almost completely (which is basically a temperature monitoring system and logging this data to the SPI-connected SD card with a few other functions).
The issue where I am stuck right now is to figure out a way (or if it is even possible) to store a continuous stream of temperature data onto a network location or a folder on the PC (with the help of ESP!!! MAYBE??) to enable the logging of said, temperature data, can be stored in a file on the network location or folder on the PC...
I have been searching for ways on how this can be searching for ways this can be achieved, but haven't been successful in getting something meaningful to work with.
So, now, I am here in the community, looking to see if anyone can help figure out how (or if even) this can be done!!!
Any help would be greatly appreciated.
PS: I have seen ways of uploading this data to Google Sheets using NodeMCU, but couldn't quite figure out how the entire process is working to even try to adapt to the PSOC, since the process is implemented using libraries.
Thanks and Regards,
Yash
Hi, I am wondering how to transition a design from the PSoC 5LP to the PSoC 3 with the minimal amount of changes possible (not having to redesign the hardware and software). I am wondering if there are any notable changes I must be aware of besides the specs difference. Of course, a simple change of device and copy and paste will not build or compile successfully. Any helpful information will suffice. The reason I am downgrading to an older chip is because there is a massive chip shortage with a year lead time on a 5LP chip that is currently being used in the design.
Show Less問題:
MinProg3からターゲットボードに電源を供給できない。
状況:
PsocProgrammerを起動し、HEXファイルを読み込みターゲットボードにプログラミングする際
MinProg3から電源をターゲットボードに供給できるような説明はあるのですが
実際はできません(設定がみつからない?)
ターゲットボード側の電源を入れれば正常にプログラミングはできている。
PSoC Creator 4.3からプログラミングする際はMinProg3の電源(Target power LED点灯)をターゲットボードに供給でき正常にプログラミングはできている。
以上 宜しくお願い致します。
Show Less
Hello community.
I'm hopeless in the titanic task of find some stock of CY8C5888AXI chips we have being produced a lot of prototypes in the past year and now we want to ramping up production but we got stuck in this shortage...
So, I would like to know if someone in the community can help us to find some stock or an available replacement microcontroller...
Thank you so much!
Show Less