PSoC 5, 3 & 1 MCU

Can someone please tell me what this means?

this happens when i add ist module and connect it to uart tx_en port

im really bad at this, just trying to follow a video lecture

hope someone helps me..

We have been using CyUSB.DLL with our VC# program that interfaces with our product using a PSoC5.  We are using Generic HID.  Now the Cyber Cops are telling us we need a signed DLL.  Considering CyUSB is so old, is there another option that is already signed?

Mike.

hello,

I have a couple of CY8CKIT-059 boards. I broke the kitprog off of one of them and have been using it to program things. I want to use its virtual com port uart capability with 12.6 and 12.7 on J9 of the kitprog. however, it never enumerates as a virtual com port. I plugged in a non-separated cy8ckit-059 and the virtual com port appears in my device manager and terminal program. then, I went to the PSOC Programmer program (version 3.27.1) and the broken-off kitprog shows up in there as "KitProg (CMSIS-DAP/251530)" with a version of "CMSIS-DAP VERSION 1.0" while the non-broken-off one shows up as "KitProg/0f20183201324400" and says it is using kitprog version 2.20.

why is this separated kitprog acting different/weird? how can I get it back to a regular kitprog?

Hi,

I was using the PSoC 5LP Verilog Generate when I am declaring the memory register(array of register with the command line)reg [7:0] registers[255:0] so I was creating 256 registers with width of 8, the error it's showing is:

that memory declaration is not supported. Any idea/approach what to do next.

Any another approach with how to write/read into registers, please give me the full detailed solution with your code, if possible.

My customer, Christie Digital, uses an old PSOC1 in their KVM project.  However, they copied and pasted this design into a newer design and now they want to update the FW in the PSOC1 and do debug.  But, I don't think they have the old PSOC1 ICE-cube and the cable to do the work :-(.  I think they wanted this old Eval board: CY3215A-DK In-Circuit Emulation Lite Development Kit.  But, I don't think this is made anymore.  This from the customer:

CY3215A-DK In-Circuit Emulation Lite Development Kit has an ICE-cube that could be directly plugged into our CY8C28 Processor Module that comes with CY8CKIT-001. Even though the processor numbers do not match, CY8C28 is still a member of PSOC1 family, so we could utilize it to do checks with CY8CKIT-001 (then there is no need to soldering a pod on the PCB of our product). Someone at Cypress probably has them in some dusty boxes somewhere.  We also need the flat cable (from the CY8CKIT-001 User Manual) 

Hello,

I am trying to read data from ADC. If I probe signal lines with a logic analyzer, I can see actual samples (with their respective headers). If I look at data read by SPI slave peripheral using a debugger, I just see some meaningless numbers. Do I have a mismatch on CPOL/CPHA?

CY_ISR_PROTO(RxC1);
CY_ISR_PROTO(RxC2);
void SendData();

uint8_t Data1[32] = {0};
uint8_t Data2[32] = {0};
uint8_t Ptr1 = 0;
uint8_t Ptr2 = 0;
volatile uint8_t Ready1 = 0;
volatile uint8_t Ready2 = 0;
uint32_t Channels[10] = {0};
uint8_t Usb[40] = {0};

void ADCData_Init()
{
    Data1_RxC_StartEx(RxC1);
    Data2_RxC_StartEx(RxC2);
    SpiData1_Start();
    SpiData2_Start();
}

CY_ISR(RxC1)
{
    while(SpiData1_ReadRxStatus() & SpiData1_STS_RX_FIFO_NOT_EMPTY)
    {
        uint8_t dummy;
        if(Ptr1 < 32)
        {
            Data1[Ptr1++] = SpiData1_ReadByte();
        }
        else
        {
            dummy = SpiData1_ReadByte();
            if(dummy < 0xFF)
            {
                Data1[0] = dummy;
                Ptr1 = 1;
            }
        }
        if(Ptr1 == 32)
        {
            Ptr1++;
            Ready1 = 1;
            if(Ready2)
            {
                Ready1 = 0;
                Ready2 = 0;
                SendData();
            }
        }
    }
}
CY_ISR(RxC2)
{
    while(SpiData2_ReadRxStatus() & SpiData2_STS_RX_FIFO_NOT_EMPTY)
    {
        uint8_t dummy;
        if(Ptr2 < 32)
        {
            Data2[Ptr2++] = SpiData2_ReadByte();
        }
        else
        {
            dummy = SpiData2_ReadByte();
            if(dummy < 0xFF)
            {
                Data2[0] = dummy;
                Ptr2 = 1;
            }
        }    
        if(Ptr2 == 32)
        {
            Ptr2++;
            Ready2 = 1;
            if(Ready1)
            {
                Ready1 = 0;
                Ready2 = 0;
                SendData();
            }
        }
    }
}

It seems everyone, mostly, agrees that DFB assembler is super hard and not to be tinkered with.

Some dedicated hobby hackers don't take no for an answer, and given that the assembler is documented in the manuals, together with a DFB asm block containing both an assembler and a simulator showing how data flows through the unit, I decided that to give it a go. The real reason for not using the filter block was that I want real time update of filter coefficients, actually just a simple PID regulator as a filter. The filter component also don't like the unstable character of PID regulators.

My findings are described at:

http://arttools.blogspot.se/2016/02/psoc-5lp-dfb-assembler.html

Comments and corrections are welcome, my time for this is limited so I cannot guarantee any fast responses, but I figure it could be helpful to collect some more help and instructions about DFB asm programming.

Regards

Magnus