PSoC™ 4 Forum Discussions

hello, we develop a project with CY8C 4149 and project go very well, we switch the chip cy8c4149 to cy8c4148 and program cyc84148, it got failure. we understand the cy8c4148 has flash memory of 256kb, our firmware size is 235kb, it should allow to be programmed in cy8c4148. following image is the programmer programming result.

Could  you help me out to successfully program in cy8c4148

Thank you

Hello,

I would like to receive DMX512 signals for lighting control.
Is there any sample code for DMX512 on PSoC 4100S Plus?

Regards,
Kawata

hi, Im music developer try to create new instrument basic on Eastern instrument ,i start my prototype with Arduino board .

 I want to change for Infineon microprocessor ,I need same touchkeys function in this link .

- different dimensions  keys board

- Bluetooth MIDI/OSC  transmit messages controller 

- 156 touch switch

- 26 touch keys with full midi/osc controller function 

-OLED display 

((My main question is which microprocessor i need to start with .))

Hi,

When we compared samples of the CY8C4124AXI-443T  produced at different dates and factories, the differences detailed below were detected

In order to understand which of these differences in top marking and lead frames are correct, we need your official statements that we can use.

Reverse Logo colors, different alignment and size

TWNxxxx   vs      xxxx (There is no any Country Code. PHI or TWN)

Different Lead Frames (X-ray image)

Are there any official statements about these differences?

Ever see and ADC input that changes if it's watched?

I have an ADC battery monitor that works as expected, ONLY IF you touch it ONE time after startup with anything, like a scope probe or even tweezers.  Unless you do this,  it reads a very high, impossible high value, as if the VSS is -3.3V. 

I realize there is a pin usage error that might cause this, and even though I will probably change it, I just want to understand why it works this way. The error is that Pin 5.1 is OVT tolerant, but P1.6 is not.  Even if P1.6 is left low it acts this way, so perhaps when the device is off, the pin protection is latching. 

If there is a software fix for this I would be interested in knowing, just because I despise ghosts in the machine. 

Thanks.  

int32_t MeasD=0;
int32_t retval=0;
VBAT_ADC_Start();
CyDelay(1);
VBAT_ADC_StartConvert();
VBAT_ADC_IsEndConversion(VBAT_ADC_WAIT_FOR_RESULT);
MeasD=(int32_t) VBAT_ADC_GetResult16(0); // Channel
VBAT_ADC_Stop();

Simplified Schematic