PSoC™ 5, 3 & 1 Forum Discussions
Hello everybody,
Im trying to do a basic power up sequence (using LP5) that combines both HW signals and SW signals and i cannot find a valid method for doing it using UDBs and digital logic.
Basically, on HW signal change (low to high) this timer/counter/etc shall start counting specific delay before activating a power circuitry enable pin. Later on, the same sequence shall work but in this case, the inputs are both HW and SW signals for enabling different circuitry peripheral.
I tried with both timers and counters, none of them seems to work.
Can your experience help me through this?
Appreciate your support.
BestRegards
Show LessI am trying to use two pins to test the phase difference of two input signals.
It is fine I can test the signal's period and duty cycle, but I can't get a correct phase difference. The value of phase difference is much large than signal period! Is there someone can help out?
I attached my project files which can be run in CY8CKIT-059 Kit. Pin1.6 and pin1.7 are connected; Pin0.6 and pin0.7 are connected
Show LessI need to add two TIMER16 units in a solution that already includes, among other things, one SMBusSlave block and when I try to Generate/Build the project I got the following error:
LMM info: area 'UART_RAM' item of 1 bytes allocated in SRAM page 1
LMM info: area 'data' item of 1 bytes allocated in SRAM page 1
!E smbslvint.asm(1192): {linker} INDEX instruction to area/symbol 'lit' out of range
make: *** [output/BatteryManager.rom] Error -1
I'm using the latest version of PSOC Designer. The project is based on a CY8C29566-24AXI micro.
How can I fix this?
I'm attaching the project showing this issue.
Best regards,
Michele Santucci
Show LessThe I2C component in PSoC4 was able to write the contents of a modest OLED display (1kB data) in one transaction, easily. It is not possible with a PSoC5. Both are 'fixed function' SCB resources.
The PSoC4 component datasheet quotes the following API for the write:
uint32 SCB_I2CMasterWriteBuf(uint32 slaveAddress, uint8 * wrData, uint32 cnt, uint32 mode)
Description:
Automatically writes an entire buffer of data to a slave device. Once the data transfer is initiated by this function, further data transfer is handled by the included ISR.
Enables the I2C interrupt and clears SCB_ I2C_MSTAT_WR_CMPLT status.
Parameters:
uint32 slaveAddress: Right-justified 7-bit Slave address (valid range 8 to 120).
uint8 wrData: Pointer to buffer of data to be sent.
uint32 cnt: Number of bytes of buffer to send.
Now my project doesn't fit in a PSoC4M anymore, so I 'upgraded' to a PSoC 5LP. Everything seemed bigger and better, except that my display code was buggy.
The PSoC5 component datasheet says:
uint8 I2C_MasterWriteBuf(uint8 slaveAddress, uint8 * wrData, uint8 cnt, uint8 mode)
Description:
This function automatically writes an entire buffer of data to a slave device. After the data transfer is initiated by this function, the included ISR manages further data transfer in byte-by-byte mode. Enables the I2C interrupt.
Parameters:
uint8 slaveAddress: Right-justified 7-bit slave address (valid range 0 to 127).
uint8 wrData: Pointer to the buffer of the data to be sent.
uint8 cnt: Number of bytes of the buffer to send.
This seems like an enormous retrograde step. I was under the assumption the 5LP was designed to be technically superior to the PSoC 4 series. What is the reason for going from 32-bit capability to 8 on such a common interface? If there is an option to specify the size of this buffer in the 5LP I2C component configurator I haven't found it.
Interestingly the return value of this API function also has been reduced, as has the 'mode' parameter type. Both the PSoC4 and 5LP return values (from this particular API function) require 3 bits. The PSoC4 expects uint32, and the PSoC 5LP expects uint8. Eight bits for this is reasonable; was the change of cnt to uint8 possibly a mistake made while rationalising the API return value (and 'mode' parameter) type?
Any explanation or suggestion for a workaround with 5LP would be really appreciated.
Paul
Show LessI want to integrate the programming of the IC to be driven from my test application. Is there a driver I can integrate into the application to accomplish this?
Show LessI have been using both the USB port and the MiniProg 3 without any problems programing the CY8_KIT-050 until today. I can acquire the USB port DVKProg5 v1.2 and MiniProg3 v 2.05 but not able to acquire the Target PSoC Device using PSoC Creator 4.2.
I do not have a problem programing the CY8_KIT-042 with the USB port or the MiniProg3. And, not having a problem programing the FreeSoC2 kit (PSoC 5888AXI LP096) from Sparkfun using the the USB port with PSoC Creator 4.2.
At this point my CY8KIT-050 is out of commission. Any suggestions.
Thanks, Mike
Show LessIs is possible to create multiple digital designs and switch between them during program execution? I need to communicate with a device that supports multiple protocols, and I need to switch protocols when a command is received via USB. There is not enough capacity for a design that can support all those protocols.
Show LessHi,
I'm just rebuild the sample project CE58352. It's a FIR Filter 8 - Bit. I think i can transfer the values form the AD converter to the filter, but i don't get a DMA request from the Filter_1 to the VDAC. I tried to debug the project with the UART interface and the code never gets a Status_Reg_2_Read() == true.
I think there is a problem with the DMA configuration. I'm the DMA configuration with the DMA wizzard like the description in the cypress document CE58352
Perhapse someone has an idea what i have made wronge.
Have a nice day
bye by
Show Less