PSoC™ 5, 3 & 1 Forum Discussions
text.format{('custom.tabs.no.results')}
Hello,
when placing hardware output on UART receive that toggles with T-FF , we see that sometimes the interrupt happens after 1 byte and sometimes after 2 bytes, how we make it interrupts always after 2bytes, or make it interrupt always on a single byte ?
Thank you
Guez Segev, BSc.
Software engineer
CI Semi - A division of CI Systems
Migdal HaEmek 10551, Israel
Tel: +972-4-644-8873
Show Less
I am trying to follow the PSoC Component Object Model Interface Guide making a C# project. But when I do exactly as described i get this error massage. Does anyone know what that mean
Show Less
Analog Devices defines a no_os_spi.h file that allows spi communications to many of their devices. https://github.com/analogdevicesinc/no-OS/blob/master/include/no_os_spi.h
I am trying to use an ADXL362 accelerometer with a cy8c5888LTI-LP097. Does anyone have an implementation of no_os_spi.c? Alternately, I could use a library for the 5LP that interfaces to the ADXL362 or ADXL363. I'm looking for c functions such as:
Hello,
I'm currently working with the PSoC 5LP (CY8C5868AXI-LP035 100-TQFP on the kit CY8CKIT-050) and I am trying to access the capture register of UDB timer with DMA. I found the address of said register and I think I set everything as it should be but the nrq output never trigger the interrupt.
If someone has an idea of what I did wrong I would be grateful.
(here is the problematic part)
Thanks in advance,
j_sim
Show LessMy original question was going to be "Why does using the example program with PSoCProgrammerCOM 41.0 Type Library 3.5 times slower than when programming from the PSoC Programmer Application (~160 seconds vs ~45 seconds)?"
I rewrote the C# example in VB.NET, using PSoCProgrammerCOM 41.0 as a reference, and it took ~160 seconds to program and verify. I am using a PSoC MiniProg and a CY8C29466.
On a hunch, I removed the reference to version 41.0, and added PSoCProgrammerCOM 9.0. When I ran the program, I got an error from .OpenPort() and did a Debug.Print() and got this: "Error: -2147483647, MINI version Expecting 1.79, but found 1.80". So I switched back to version 41.0, but I still get the error. I never got this before, but now it never goes away.
On another hunch, I decided to ignore the error and let the program continue execution. Now it programs and verifies the PSoC (CY8C29466) in only 56 seconds. I don't know if I should complain or just count my blessings. However, things that fix themselves usually break again.
New Question: Is there any explanation for this odd behavior from the COM library? Also, I read on another post that PP_COM_Wrapper is obsolete. Also, it does not show up in Visual Studio as a COM reference. Is it truly obsolete/discontinued?
Show LessHello,
I have been flashing this PSoC5LP MCU with no issues until I starting flashing this particular firmware. After flashing several times with this firmware and any other, I am unable to re-flash the device, and PSoC programmer fails to acquire. This has happened with 3 different boards, using two different programmers (MiniProg4). I tried using PSoC programmer 3.29.1 and 3.29.5, with Programming mode reset (external VDD) and Power Cycle. I am using GND, SWDIO, SWDCLK, XRES and VDD signals.
I noted that this firmware has enabled SWD Debug and in the hardware, this pin is connected to GND via a resistor and a diode. Is this an issue?
Hello. I am currently working on LP5 PSoC and using I2S PSoC Creator Component (v2.70). I get the first interrupt, read the status register, successfully read the I2S_ReadByte bytes, as I see in the component debugger window, RX_STATUS_0_REG sets the value from 0x83 to 0x00, but after exiting the IRQ handler, it doesn't get it again. It looks like I should reset the interrupt flag, but how? CONTROL_REG is 0x06 all the time, the logic analyzer shows that the data is constantly flowing.
Show LessHello,
I 've been using PSoC Creator 4.2 since several years, but in the last weeks I noted that when I launch the Builder, on the Output tab there is no more the information regarding the FLASH USED.
Does someone know the reason and know how to restore this information?
Thanks
Show LessAbout 20 years ago I built a PSoC programmer equipped with AT90S8515. The programmer used to communicate with the computer via COM port. The schematic I found then on the Cypress internet page. Unfortunately I can not find the software anymore and I need it urgently. If anyone can help me, please drop it here or send it directly to me; my address is g_plesoianu (at) hotmail.com
Thanks!
Show Less