PSoC™ 5, 3 & 1 Forum Discussions

Hi folks,

I have this PSoC 5LP project that's acting a bit weird. Basically, when I read data from port 3 (8-bit bus with 3.0 - 3.7), things work fine as long as 3.7 is low. When 3.7 goes high, it seems like 15.4, or my Pin_RW logical connection, is always being pulled high as well.

The PSoC in this case is on a CY8CKIT-059. I have removed the LED, CMOD cap, and SAR caps. The device is emulating RAM to interface with an old CPU (LH5801). I see the issue when I try to POKE values > 127 into the MCU. Value below 128 work fine, and I no problem reading any data value from the MCU. Addresses also don't have problems with the upper bit. When I try to write data > 127, though, the MCU acts as if R/W never went low. No write occurs.

I did also check resistance between 3.7 and 15.4. It's about 3 MOhms.

It's a bit tricky to troubleshoot, because the system needs all its clock cycles to work properly. Debug makes it too slow.

Any ideas on what might be happening here?

Thanks,
Paul

Hi folks,

considering setup of PSoC3/DelSig i was wondering, if how to interpret voltage range setup vs. effective resolution.

Assume neg. input of ADC is put on ground and Vref is setup external along with 1.024V generated externally. Additionally selected Level Shifted buffer mode, resolution 20Bit.

If I went to setup range as follows:

-Input ADC +/-Vref2

Which voltage range is to be choosen for calculation of resolution??

Case 1:

(Vref*2)/2^20

Comment:

• Does it mean, an Offset has to be added to result provided by DelSig, as we're not able to get values <-100mV but range has been setup as defined above?

Case 2:

(abs(-100mV)+Vref)/2^10

Comment:

• abs(-100mV) is minimum possible voltage for ADC

Case 3:

Choosing Rail to Rail buffer mode actually expecting this:(Vref-100mV)/2^10

I'm a little bit confused, thanks for  your efforts in advance!

Joe

Hi

Greetings of the day!!!

We are using  CY8C3866AXI-039 from PSoC 3 family in one of our product. But due to limitation of code memory we have to move to another chip (CY8C5867AXI-LP024) from PSoC5 family.  

The application code written for PSoC 3 family chip is working fine. And we are using same application code for PSoC5 famiy chip.

We have created new project with CY8C5867AXI-LP024 chip and added peripherals like ADC,LCD and I2C and used same application code written for PSoC 3.

With this we are able to get LCD display working,but ADC and I2C is not working. We have tested I2C waveform on oscilloscope as well and found that there is no response from I2C slave (DS1307 and EEPROM).

Are there any modificatons we need to in existing application code of PSoC 3 to get it work on PSoC5 chip.

Kindly advice how to proceed ahead.

Thanks & Regards,

Purushottam

HI.

Sorry but my english is little, and I started witch psoc ...    how to correctly read data from pcf8583 ???

#include "project.h"
#include "tm1637.h"
//#define PCF8583_ADDR 0xA0        // gdy A1 --> GND
#define PCF8583_ADDR 0xA2        // gdy A1 --> VCC
uint8 czas[4];
uint8 ss=4, mm=3, hh=2, day, month;
//==================================================================================================================================
//==================================================================================================================================
int main(void),
{
    CyGlobalIntEnable; /* Enable global interrupts. */
    I2C_1_Start();
    /* Place your initialization/startup code here (e.g. MyInst_Start()) */
    
    
    
      
    
    for(;;)
    {
    SENDnumber(4523);                       //TM1637
        
    I2C_1_MasterSendStart(PCF8583_ADDR, 0);
    I2C_1_MasterWriteByte( PCF8583_ADDR );
    I2C_1_MasterWriteByte( 0x02 );
    I2C_1_MasterWriteByte( PCF8583_ADDR+1);
    I2C_1_MasterSendStart(PCF8583_ADDR, 0);
    ss = I2C_1_MasterReadByte(I2C_1_ACK_DATA);
    mm = I2C_1_MasterReadByte(I2C_1_NAK_DATA);
    I2C_1_MasterSendStop();
    
    
        
        
        
        
        SENDnumber( ss);
           CyDelay(500);
        SENDnumber( mm );
           CyDelay(500);
         SENDnumber( hh );
           CyDelay(500);
        
    }
}

    to check i2c function i used led and variable ct but the max val is 1 😕

for(;;)
{
SENDnumber(ct++);                   
//TM1637
I2C_1_MasterSendStart(PCF8583_ADDR, 0);
SENDnumber(ct++);                   
//TM1637
I2C_1_MasterWriteByte( PCF8583_ADDR );
SENDnumber(ct++);                   
//TM1637
I2C_1_MasterWriteByte( 0x02 );
SENDnumber(ct++);                   
//TM1637

Our current design connects an external clock crystal to P12[0].  The clock does not seem to be working when used with any of the chip resources.  In fact, even if I route that back to an output pin, it is just sitting high.  When wiring this clock to a P3 pin, I am able to use it just fine.   I understand that the P12 pins are SIO...do they require some special type of setup?  I read in another post that there was an issue if the input buffer was not enabled for the pin.  When I corrected that, I was able to see the clock on the P3 pin, but still no dice on the P12 pin.  I currently have the pin set up as a digital input, hw connection, high impedance digital.  I also have CMOS threshold and input buffer enabled.

Any idea what the problem might be?

I'm new to SPI and have run into a snag. I have a a PCB with a PSoC 3 trying to communicate to an nRF24L01+. With PsoC Creator, I have added an SPI mater to the project and have a simple loop where, after I do a "SPIM_Start()" I try to do some simple register write/read on the slave. I have a logic analyzer showing me the SPI data that is being transfered. It appears as though my write to say register 0 is working .. I basically do a "SPIM_WrtieTxData(<addr>+32)"  ( register write requires bit 6 to be a "1" to indicate a register write, so register "0" if the value == 32), then I do another SPIM_WrtieTxData(<value>) to write the data to that register. So far so good, and the analyzer shows the xfer. But, when I try to read the register; I send "SPIM_WrtieTxData(<addr>)" (bit 6 is clear for a read, so just the reg addr is needed) then another write ("SPIM_WrtieTxData(0xFF)") with bugus data, which gives the slave the clock cycles it needs to shift the return value out  (verified with analyzer), I then do a "temp = SPIM_ReadRxData()" to read what I would think would be the slave return data but the value returned is NOT what is expected (nor what the analyzer shows). So, I must be missing some simple step before I should read the slave data.

Here is a simple example of my code.. and a snapshot of the analyzer output (attached)

My guess is I'm missing some Tx and/or Rx status checks but I'm not sure what and why?

Any suggestions?

main() {

  uint8 addr, val;

  SPIM_Start();

  for (;;) {

     addr = 32;     // Set bit 6 to write to a register (i.e.  001a aaaa ..  "aaaaa" is the register address). So reg "0" here.

      SPIM_WriteTxData(addr);   // Tx addr to slave device

      SPIM_WriteTxData(0x1E);  // Write 0x1E (to register 0 .. just an xfer test, not tryiing to set anything, yet).

      CyDelayUs(10u);   // Give small delay for the xfer

     addr = 0;                    // Now read regsiter 0. A read operation is just the address (i.e. 000a aaaa)

     SPIM_WriteTxData(addr);     // Tx addr to slave

     SPIM_WriteTxData(0xFF);    // Tx bogus data to give slave the clock cycles it needs to shift out register 0 contents

     CyDelayUs(10u);   // Give small delay for the xfer

     val = SPIM_ReadRxData();     // We should see 0x1E, but we val == 0x00 (analyzer shows 0x1E).

  }

}

Hello,

PSoC1 CY8C29466-24PVXI operates at supply voltage 3.0V to 3.6V or 4.75V to 5.25V.

On the other hand, looking at DC Programming Specifications in the data sheet,

Vddp: VDD for programming and erase requires min 4.5V / max 5.5V.

Customers use PSoC at Vdd=3.3V. Even in this case, is 5V different from Vdd=3.3V needed for on-board programming?

Best Regards,

Naoaki Morimoto