PSoC™ 5, 3 & 1 Forum Discussions
I made a 'hardware only' enabled UDB timer that flashes an LED according to the attached schematic. The main() routine contains nothing but an endless loop. I can't get this to work unless I put 'Timer_1_Start()' in the main routine. According to the data sheet this should not be necessary. Any suggestions?
Show LessCan any one tell how can we place resistor and capacitor and configure thier values in the PSOC design in the workspace of psoc creator so that we can add them to other blocks.????
Show LessIs it possible to change the drive mode of a certain PIN at runtime for C Code.
In my application I have defined P3[7] as "Pull Up" in the IDE, I want to change it to "Pull Down" at runtime.
My best guess how to do this is code like this ...
PRT3DM1 |= 0x80 PRT3DM0 |= 0x80
In other examples I've seen stuff about 'disconnect from global bus', would I need to do this as well?
Show LessHallo,
I have a doubt about handling a communication with a couple of I2C slaves. If I usually perform:
a write on the first slave, a read from the first slave, a write to the second slave, a read from the second slave
If one of that functions takes too much time I simply skip on the next task simply clearing the read/write status.
The question is: "I have to send a stop the the slave before dropping the task I was executing with him"?
Show LessHi All,
This should be a very basic question, so forgive me. I'm trying to detect a voltage on a PSoC pin. It's either going to be 3V or 0V. The pin I am using is currently P0[0] and I have its drive set as Pull Down. I initialize the PRT0DR bit to 0, but I never read a high value when the voltage is 3V. Is there something that I am doing wrong?
Essentially I want the PSoC to read a high value when a voltage is applied and a low value when the pin is floating.
Show LessThanks to Uday I've got some SPI transmission working, but I'm seeing a very strange problem with the transmission speed on SPI.
My device is a CY8C3866-ES3. I'm using a SPIM Mode 0 @ 2.5 MBit, tx/rx buffer set to 96 bytes. I fill TX with 80 bytes using SPIM_PutArray and then watch the transmission using my scope.
What I see is 8 bits getting clocked out in about 3.2 microseconds, then a 17 uSec gap before the next byte starts to transmit.
I have two interrupts enabled besides the default: IRQ on Tx FIFO empty and IRQ on Rx FIFO full.
What could be stalling the SPI hardware to take this long before sending another byte? This effectively is limiting my SPI transmission to under 1Mbit when I should be going 2-3 times faster.
Thanks,
Louis
Show LessWhile using PSOC5 i notice the device doesn't crash when I access out of bound array.
#define MAX_ARRAY 16
int array[MAX_ARRAY];
int a = [array MAX_ARRAY]; //array should be in range 0 - 15
I'm using PSOC creator with GCC compiler in debug mode.
Show Less