PSoC™ Creator & Designer Forum Discussions

Question: Is there a way so that I can stop generating APIs for the components for which I do not want to use them?

 Hi Everyone,

I'm fairly new to the PSoC creator. I'm working with the PSoC 5LP develeopment kit. Attached to this message is my project I am working on to use a switch to turn on a LED but to also use that same switch to turn off the LED and turn on another after holding that LED for 4 seconds. I set up a design that I'm most confident will work, with a debouncer to a counter. 

The issue I am having is with the main.c that I am building. If I use the debouncer sperately I can toggle the LED on and off with the switch easily, but with the counter connected I seem to lose this capability. Also i cannot seem to get the other LED to turn on after 4 seconds. PLS HELP. 

Hi Everyone,

I'm fairly new to the PSoC creator. I'm working with the PSoC 5LP develeopment kit. Attached to this message is my project I am working on to use a switch to turn on a LED but to also use that same switch to turn off the LED and turn on another after holding that LED for 4 seconds. I set up a design that I'm most confident will work, with a debouncer to a counter. 

The issue I am having is with the main.c that I am building. If I use the debouncer sperately I can toggle the LED on and off with the switch easily, but with the counter connected I seem to lose this capability. Also i cannot seem to get the other LED to turn on after 4 seconds. PLS HELP. 

Hi Everyone,

I'm fairly new to the PSoC creator. I'm working with the PSoC 5LP develeopment kit. Attached to this message is my project I am working on to use a switch to turn on a LED but to also use that same switch to turn off the LED and turn on another after holding that LED for 4 seconds. I set up a design that I'm most confident will work, with a debouncer to a counter. 

The issue I am having is with the main.c that I am building. If I use the debouncer sperately I can toggle the LED on and off with the switch easily, but with the counter connected I seem to lose this capability. Also i cannot seem to get the other LED to turn on after 4 seconds. PLS HELP. 

Hi Everyone,

I'm fairly new to the PSoC creator. I'm working with the PSoC 5LP develeopment kit. Attached to this message is my project I am working on to use a switch to turn on a LED but to also use that same switch to turn off the LED and turn on another after holding that LED for 4 seconds. I set up a design that I'm most confident will work, with a debouncer to a counter. 

The issue I am having is with the main.c that I am building. If I use the debouncer sperately I can toggle the LED on and off with the switch easily, but with the counter connected I seem to lose this capability. Also i cannot seem to get the other LED to turn on after 4 seconds. PLS HELP. 

 Hi Everyone,

I'm fairly new to the PSoC creator. I'm working with the PSoC 5LP develeopment kit. Attached to this message is my project I am working on to use a switch to turn on a LED but to also use that same switch to turn off the LED and turn on another after holding that LED for 4 seconds. I set up a design that I'm most confident will work, with a debouncer to a counter. 

The issue I am having is with the main.c that I am building. If I use the debouncer sperately I can toggle the LED on and off with the switch easily, but with the counter connected I seem to lose this capability. Also i cannot seem to get the other LED to turn on after 4 seconds. PLS HELP. 

Hi,

  I am new to the PSoC world.

  I have a project and wish to do current monitoring using a PSoC3.   The system is 3.3V and can drain a maximum of 1A.

  I see that the smallest range is +/-64mV which is still too high for my application.  Draining 64mV on 3.3V will affect the circuit.

  Can I add an internal op-amp to boost the voltage difference before I enter the current monitor block?  Let's say a x10 amplification would be acceptable.

Thanks

It's cool that the I2C master component supports buffer-at-a-time reads and writes with a Cypress-written builtin ISR. The only feature missing from the API is a function with a signature like:

uint8 MasterWriteReadBuf(uint8 slaveAddress, uint8* wrData, uint8 wrCnt, uint8* rdData, uint8 rdCnt, uint8 mode)

The function would write the bytes from wrData, send a restart, and then read rdCnt bytes into rdData. In other words it would be equivalent to:

status = MasterWriteBuf(slaveAddress, wrData, wrCnt, mode);
// possibly error handling based on status
return MasterReadBuf(slaveAddress, rdData, rdCnt, I2C_MODE_REPEAT_START);

except that it would be handled by the builtin ISR.

Almost all of my I2C interactions are this way: I need to write the "register address" within the device that I am interested in reading, and then read the contents of that register. Performing the transition without having  the interrupt handle it is tricky to do without spinning the processor waiting for the initial write transaction to take place at the much-slower-than-bus-clock I2C clock rate. This is a very, very common pattern of use of the I2C bus, almost every I2C device datasheet I know of works this way.

Hi Everyone,

I've been working with PSOC creator for the past 2 years.  I've recently run into an issue where I can't access the analog section of either PSOC3 or PSOC5 from the schematic level of the IDE.  The components are listed, but I'm getting an error when it tries to load the preview of the component in the bottom right hand corner of the screen.  I checked the containing directory, and everything looks like it is where it should be.

Has anyone encountered this problem before?  And if so, how have you managed to fix it?

Thanks in advance,

Jamie Mascola