PSoC 5, 3 & 1 MCU

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();
            }
        }
    }
}

私はPSOC5LPにてSDカードを使用したプログラムを書いています。

emfileとFS.hを使用しています。

できる限り省電力にしたいため、SDカードの電源も制御しようとしています。

そのため4端子の3.3Vレギュレータを用いてsleep前にSDカードの電源を切っています。

また、SPIのCS端子もLOWに設定するようにプログラムを書きました。

#include <project.h>
#include <FS.h>
#include "stdio.h"

FS_FILE * pFile;

int main()
{
    CyGlobalIntEnable; /* Enable global interrupts. */
    CONS_Start();
    FS_Init();
    while(1){
        SD_Power_Write(1);
        emFile_SPI0_CS_Write(1);
        pFile = FS_FOpen("\\data\\4.csv", "a");
        if(pFile)
        {
            if(0 == FS_FClose(pFile))
            {
                CONS_PutString("File was closed\r\n");
            }else
            {
                CONS_PutString("Failed to close\r\n");
            }
        }else{
            CONS_PutString("Failed to write file\n");
        }
        SD_Power_Write(0);
        emFile_SPI0_CS_Write(0);
        CyDelay(5000);
    }
    return 0;
}

 こちらのプログラム実行結果が下記の内容です。

Start
File was closed
Failed to write file
Failed to write file
Failed to write file
Failed to write file
Failed to write file
Failed to write file

 電源を一度切るとその後はファイルを開くことができません。

電源を切る前に実行すべきメソッドがあるのでしょうか？

それともそもそも電源を切ってはならないのでしょうか？

追記：

回路図と使用部品を記します。

microSDソケット：https://akizukidenshi.com/catalog/g/gK-05488/

SD電源用4端子レギュレータ：https://akizukidenshi.com/catalog/g/gI-09261/

主電源DCDC(3.3V出力)：https://strawberry-linux.com/catalog/items?code=12060

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

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

I just inherited code that sets a reserved bit that does make a difference in a capsense measurement.   When the reserved bit is set I get "proper behavior" .    I did not set this bit in a test and the capsense was reading out raw data at 255 range  when it should have been reading 0.  To get this design to work this bit has to be set.   What does this bit do and how in the world could of my predecessor known to set it???? 

This bit is bit 7 in CS_CR3 that is being set by the following code segment.

CS_CR3 |= 0x90; // Reference buffer to drive the analog global bus. Bit 7 is not used so why was it set? Reserved bits should not be set. Without it the raw capsense value reads 255 instead of 0
// CS_CR3 |= 0x10; // Reference buffer to drive the analog global bus.  Causes 255 to be read in raw value instead of 0 . 

Then the capsense code below this.

The datasheet says that the comparators may be preceded by a low pass filter.  A low pass filter appears on the analogue routing diagram.  The lime green is my addition.  It's greyed-out.

There is no LPF in the comparator config and there isn't a LPF in the component catalogue.

How do I get my mitts on this component?  It seems tantalisingly out of reach.

I bet I'm doing something silly.

PSoC Creator 4.4, Win 10, CY8C5666AXI-LP001