PSoC™ 5, 3 & 1 Forum Discussions

Thanks 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

While 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.

 I am trying to find any reference on how to use SWV on PSoC3 but I cannot find anything on this site.

Can someone point me to the right direction?

For my PSoC challenge project, I need to sample a GPIO port (to have a logic analyzer). I encountered some strange behaviors when doing that. I'm using a combination of LUTs for the trigger logic, which are driven by 2 registers (one for the bit mask, one for the compare values). My test circuit is a 8-bit-counter, running with about 6 kHz. The port I'm trying to sample is P3 (since it is available on the prototyping area).

My first version was using DMA for the GPIO data to memory. When doing so, only the bits which are not selected for trigger comparision are transferred properly - all other bits are set to the trigger compare value. To make it even more strange - the counter output seems to be distributed to the non-masked bits (meaning the the first bit not selected for trigger gets counter Q0, the second non-selected gets Q1 and so on) - which clearly isn't how I have connected the wires.

When I replace all the DMA logic with just a simple PWM timer to generate interupts, and sample via a Port_Read() call, these problems go away, but all bits are inverted.

In both cases I have routed the internal signals back to another port, and connected another logic analyzer. These signals are always fine (not inverted, not mixed up).

Has someone an idea what might happen here?

I want to use the Delay10msTimes function from the article here http://www.cypress.com/?id=4&rID=47960 .

I unzipped the delay.asm and delay.h files and included them in my project.  I included the .h file using the "#include <delay.h>" line of code.

The code in the "delay.h" won't compile.  I get the following warnings & errors:
WARNING: DELAY.H:12: unknown #pragma, line ignored
WARNING: DELAY.H:13: unknown #pragma, line ignored
WARNING: DELAY.H:14: unknown #pragma, line ignored
ERROR: DELAY.H:19: syntax error near 'Multiple', expected ')'
ERROR: DELAY.H:20: syntax error near 'TenMstimes', expected ')'

I want to create a 1 second pulse on a pin.  I was going to do this with the following code:

Timer_Reset_1_Write(1);  //Set the PIN High
Delay10msTimes(100);     //Wait 1 second
Timer_Reset_1_Write(0);  //Set the PIN Low
 

Hi All

My first post and I hope this is the right section.

I'm using a CY3209 Dev Board designing a USB to SPI interface bridge. I programmed CY8C24894 to be my SPIM and CY8C29666 as my SPIS.

After a few questions with the technical team, I had a project example from this link: http://www.cypress.com/?rID=34330. I cloned this project but selected the chipsets that I will be using accordingly. Additionally, I routed a few of the onboard LEDs to the MOSI/MISO,SS and SCLK signal bus so that I would be able to know that data is transferring between the master and slave.

However, as I'm not very strong in my C program, I'm not too sure of what modifications I had to make in order for it to work proper. As a result, using the software provided in the link, USB to SPI.exe, I am unable to get the results as indicated in the pdf that came with the link too.

Attached in the zip file is my screenshot and program.

Looking at the main.c file of the SPIM, i spotted this syntax which assigns the Slave Select to a register for CY8C24894. Under the comments, the slave select pin is P0[2]. However, on the schematic of the CY8C24894, Slave Select pin is P0[7] instead.

//Set the SlaveSelect pin P0[2] to high.
    //(Since SlaveSelect is Active Low)
    PRT0DR |= SLAVE_SELECT;

What needs to be changed for this?

Is there anything else that I need to take note or possibly a good reference that I can used?

Thank you!

 Hi!

   I have a problem with counter interrupt. I write simple program in C and now I want use it in the counter interrupt. So, what I should do to use C function in .asm file?? 

P.S. I'm sorry about my English

Hello,

I'm using a CY8C3446AXI-098 PSoC 3, which according to the datasheet has two USBIOs on pins P15[6] and P15[7] which can be used to either provide connection for a USB data bus or be used as general DIO pins.  However, what the datasheet didn't specify, and what I didn't find out until trying to build my design, is that the DIO pins can only be configured to one of two drive modes, Strong Drive, and Open Drain Drives low.

I was hoping to use these pins as general purpose digital input pins.  It seems logical enough to think that the pins could be configured in Open Drain, Drives low drive mode, and simply held in the high-Z state to be capable of sensing any input voltage on the pin.  However, if this is the case I would expect to be able to configure the pins as a high impedance digital input drive mode so there would be no confusion.  Must the software ensure that the pin is always held in high-Z state when configured as an input, or is this done automatically by PSoC creator?

I just want to verify that a pin configured as Open Drain, Drives low can be used as a digital input equivalent to a high impedance digital input pin with no extra external circuitry or software so that I don't end up building the board and realize these two DIO pins don't act as I'd expect.

Thank you!

John