PSoC™ 5, 3 & 1 Forum Discussions

Hi everyone,

I'm currently looking into safety-critical related HW options in the PSoC5lp.

NMI seems to be only pendable by software, however the PSoC5lp Registers TRM states that when the NMI_SRCSEL bit of the PANTHER_WAITPIPE register is set to 1, the NMI line is fed with DSI_01_OUT_P_11 signal. What is this signal ? Is it routable through UDB/datapath blocks ?

I also read the "Definitive Guide to the ARM Cortex-M3" book by Joseph Yiu and was wondering how the LOCKUP signal (section 12.5) is used in the PSoC5lp. Does it trigger a SystemReset ?

Regards,

Cédric

Hi all,

I'm still new to PSoC (and PSoC Creator) world: I would like to port some libraries that I wrote for STM32 MCU to PSoC, but I have some doubts about it.

The libraries that I wrote are intended to be used with MEMS sensors (temperature, pressure, and humidity) which communicate with the MCU over I2C. When I wrote them for STM32 MCU, I wanted them to be independent of the I2C interface chosen (I2C1, I2C2, I2C3,..), so that the programmer could choose which I2C to be used. Therefore, my code looked like this:

// Function prototype - I2C_TypeDef pointer
void readTemperature(I2C_TypeDef *I2C, SensorStruct sensor);
int main(void)
{
     SensorStruct mySensor;
     I2C_Init(I2C1);
     
     while(1)
     {
          read_temperature(I2C1,&mySensor);
          // Do some stuff
     }
}

In PSoC, can I do something similar? My problem right now is that, if I write a library, I'll need to use some I2C methods, but these methods have to be called with the name of the component. So if I change the name of the component, I need to change it everywhere in my code, as follows:

// Programmer used I2C component naming it I2C
I2C_MasterSendStart(SLAVE_ADDRESS, READ);
// Programmer used I2C component naming it I2C_1
I2C_1_MasterSendStart(SLAVE_ADDRESS, READ);

What kind of approach do you suggest me?

Thank you in advance,

Davide

Hello everyone. I'm currently using cy8c5888lti-lp097. I've already separated KitProg section from Cypress board, connected them with jumpers and successfully supplied the board from external source (I didn't remove diode D1). My question is, can I flash the board through KitProg section but without VTARG connection and supply Cypress board form external source at the same time? Because as I know, it's forbidden to connect more that one power supply source at the same time. Thanks!

Hello,

I'm having issues flashing a PSoC 5 LP device using SEGGER J-Link. If I flash the same .hex using PSoC Programmer and MiniProg it works.

If I use PSoC Programmer and MiniProg to read out the memory, I can see that the only difference in the two cases is that when flashing with MiniProg 'Config Flash Area' address 0x0400 contains some data (roughly between 0x0400 and 0x0f80).

- What is this data?

- Where does it come from?

- How can I flash it using J-Link?

Thanks, Jacob

Hi,

I'm a seasoned PSoC application designer.  I'm using a PSoC 5LP.  I have an application that uses the OpAmp v1.90.

Most of the time I need to configure the OpAmp with a mode = OpAmp.  The '-' input is routed to an external pin of a current sense resistor.  However due to the < 1Meg ohm input impedance (observed but not specified in the datasheet), I cannot resolve to < 30uA of current due to the extra draw and resultant noise.

If I "hard" configure the mode = Follower, I can resolve very low currents to ~ 1uA with much lower noise.

I want to configure the OpAmp to mode = OpAmp in the TopDesign and switch to mode=Follower in the code at run0time when needing to resolve to 1uA.  I can operate at the register level if needed but it would be nice if there were some API calls to provide this.

Note:  I tried using a analog mux external to the OpAmp to perform this desired function.  I noticed many problems doing this successfully and had to abandon the attempt.

Thanks for the help in advance.

Len

I'm trying to use the bus/memory/usage fault handlers to create simple exception logs.

So I have defined the following bus/memory/usage fault handlers and enabled the corresponding register flags:

CyIntSetSysVector(CY_INT_BUS_FAULT_IRQN, faultHandler);
CyIntSetSysVector(CY_INT_MEM_MANAGE_IRQN, faultHandler);
CyIntSetSysVector(CY_INT_USAGE_FAULT_IRQN, faultHandler); 
SCB->SHCSR |= SCB_SHCSR_USGFAULTENA_Msk | SCB_SHCSR_BUSFAULTENA_Msk | SCB_SHCSR_MEMFAULTENA_Msk; // enable Usage-/Bus-/MPU Fault

To verify the proper functioning of the bus fault handler, I've implemented the following code, according to an example project:

const uint32_t makingFault = 0u;
uint32_t *ptrFault = (uint32_t *) &makingFault;
*ptrFault = 100u;

However, this code does not lead to a bus or memory management fault. Is it due to the reason that there is no MPU available in PSoC5? Or did I miss something else?

Hello,

I would like to setup a PLC System on DC bus.

The LV Evaluation kit is obsolete, is there any suitable product available, if there is only a power supply of 24V?

Thanks and kind regards

Chris