PSoC™ 5, 3 & 1 Forum Discussions

Hey,

I am new with PSOC so please bare with me. I tried to find an answer by myself but so far I am not able to. I come from embedded C and ARM Cortex-M background with extensive experience.

I was exploring PSOC for a new project, what I want to do is to control the route of some digital signals. The board will have 2 connectors, and I want to route signals from one connector to the other based on user's configuration. The user will connect signals to some GPIO pins, using PSOC I want to re-route these signals to other GPIO pins. Prior to user configuration I do not know which Pin will be connected to which and whether the signal is input or output. To rephrase, there is a data bus connected to some pins; using the PSOC I want to reroute these signals to other pins. The problem is I cannot make this decision while using the PSOC creator, it needs to be done in the field.

Example:

In the field the user will decide to connect J1.1 to J2.3, later he will decide to connect J1.1 to J2.4 etc... The user can be asked to select if the signal is input or output in the field.

1. Is it possible to control the hardware blocks using the C code instead of the PSOC creator schematic ? e.g connect P0[3] to P0[5] using C instead of schematic design
2. Is there a way to implement the above using control registers and other blocks?

I tried to use back to back mux with bidirectional pins but at build time I get the below errors.

Thank you for any help

Hello,

I would like to be able to permanently store data to flash of my PSoC5 processor and being able to retrieve it after rebooting the processor.  I found sample project "Flash Example" that seems to be doing just that.

This is the code snippet how they store data to flash:

...             CySetTemp();             returnValue = CyWriteRowData(ARRAY_ID, ARRAY_ID_ROW_ADDR, rowPattern);             /* Check if operration is successful */             if (returnValue != CYRET_SUCCESS)             {                 LED_Error_Write(LIGHT_ON);                 CyHalt(0x00u); ...

It writes data to the flash and then immediately reads it and matches to what was stored.  Everything works fine here.  But if I modify this code such that when it runs first time it ONLY writes the data and the second it ONLY reads the data then the stored data is lost.  So it looks like the stored data didn't survive the reboot OR reprogramming of the chip (I had to do it to comment out the code that writes data to flash).

Is there a way to burn something to flash so it stays there until explicitly erased?

Thanks!

Nikolay

Hello. We have an existing design from ~10 years ago, using a CY8C27443 SO28. We're looking to see if it's possible to update this part to a new ARM based part, in the same footprint so as to not have to re-spin the board.

I fumbled through the product selector, but can't figure a way to look for pin compatible parts. Thanks

I am a bit confused regarding use of the flags when sending SPI data and seem to get back wrong data from my device

I have a SPIM component set up and started and can see activity on CS, Miso, Mosi and Sck but get wrong data back.

Is my code below correct to send a command byte (read command and register ID) and then read back the expected bytes?

Header length is number of command bytes and header buffer is buffer passed to routine containing command bytes.

readlenth is number of bytes to read and they are passed back in readBuffer.

int readfromspi(uint16 headerLength, const uint8 *headerBuffer, uint32 readlength, uint8 *readBuffer)

{

CS_Write(0);

    for(i=0; i<headerLength; i++)

    {

    SPIM_WriteTxData(headerBuffer);

        while(!(SPIM_ReadTxStatus() & SPIM_STS_SPI_DONE)){};

      readBuffer[0] = SPIM_ReadRxData() ; // Dummy read as we write the header

    }

    for(i=0; i<(int)readlength; i++)

    {

        SPIM_WriteTxData(0x00);  //dummy write

        while(!(SPIM_ReadTxStatus() & SPIM_STS_SPI_DONE)){};

      readBuffer = SPIM_ReadRxData() ; // SPI_receive_data

    }

    CS_Write(1);

    return 0;

}

Dear Sirs,

I'm facing some problems with a device I've designed based on PSoC5 implementing a USB HID mouse in particular:

initial condition is with the host PC off and with the mouse already connected into an USB port, then when the PC is powered on at the startup of the Operating System (Red Hat 7 Update 1) the mouse doesn't work, the pointer isn't moving on the screen when the user try to.

The device is present in the connected peripherals, but doesn't not send "events".

If the device is disconnected and reconnected to a USB port with the PC switched on then it is operative and it works. This same behavior has also been verified with the Windows operating system.

Moreover although it is recognized at runtime (thus connecting it to the PC already on), under the graphics interface (X) of Red Hat 7 Update 1 there is no movement but only the left button seems to work. Instead, under Windows, the device is seen as a mouse and it works ok.

The device descriptor is based on CE195394 - USB HID Mouse with PSoC 3/ PSoC 5LP with the remote wakeup enabled.

Can you please provide me some information to solve this issue?

Best Regards