PSoC™ 4 Forum Discussions
I am having loads of trouble getting the ADC working on my PSoC 4 Pioneer board..
The values coming out of it are all wrong.. I am feeding in 3.9V and I am getting out 2047.. or sometimes other values..
3.9 if my calulation is right should be
3.9/(5V/4096) = 3194..
I have noticed that if I feed in about 2.5V and below that my 2047 value starts changing and it gets lower and lower the lower voltage I put in so it is tracking the input.. but as soon as I go over 2.5V it locks on at 2047.. I have checked and I have the channel set up for single input, and it says 0-5V on the ADC config page..
I really would like just the absolute most bare bones basic project which has a single input and an ADC which is set up to give 4096 for 5V (12 bits) and 0 for 0V..
All of the example ADC stuff supplied by Cypress is 0-1.024V which is useless for me..
Does anyone have an example project pretty please?
Show LessJust a quick question.
I am using one of the new CY8CKIT-042 PSoC4 Pioneer Kits.
There are some things that I am not able to get working on it (like a simple 16x2 LCD display), even though I have tried everything that I know to try.
I am no expert using Creator (3.0), or the PSoC, or the 'kit', but I am really reaching the end of things to try.
As a last resort, I got out my magnifier and read the Part Number on the PSoC4 chip. It is...
CY8C4245AXI-483ES
My question... What does the 'ES' stand for?
If it is what I think it means, then I am using an 'Engineering Sample' part on this board. (Or trying to use one.)
Can someone shed some light on this? If it _is_ an Engineering Sample (and I have purchased two (2) Pioneer Kits - both have 'ES' parts on them), then this may explain why I am having difficulties.
Thanks.
James
Show LessThis one may be a simple question to answer. I am interested in generating tones, much like notes on a piano, that I can use in a program that I am writing.
I am not asking anyone to write the code for me, just point me in the right direction - using Creator 3.0 - and off I will go, writing code and making beautiful (hopefully) noises from a PSoC4.
If it works with the PSoC4 Pioneer Kit - even better, because that's what I am using for my 'dev kit'.
Thanks.
James
Show LessAfter purchasing three Pioneer kits (early summer) I needed a better way to quickly prototype projects. This included having an LCD display and a breadboard similar to lot of the Cypress Kits like the CY310-PSoC EVAL1.
I produce 12 PCB for personal use. The PCB layout uses a separate voltage regulator, 16x2 LCD module using theHD44780 5V controller with lack light, and jumpers to select several ways to connect power. The shields can be configured to use a breadboard or wire wrap terminals.
I’ve had no problems with LCD issues as indicated in thread CY8CKIT-042 PSoC 'ES'. The shield works with the LUMEX LCM SO 1602DSR/A LCD module (used in Cypress kits) with no back light. However, I have not tried it with a 3.3V module using the SPLC780D controller. That particular controller uses an extra 8 pin IC soldered on the back of the LCD board. Data sheets indicate that the SPLC780D controller is compatible with the HD44780. However, the power up timing/initialization may be different.
See attached file of shield with breadboard.
James B
Show LessBefore I brick any of my devices, does anyone have thoughts on self writing of flash with security enabled? I don't want anyone to hack my device, but my device must be able to re-write it's own flash, whether in bootloader mode or in the user application. I understand the certain security bits remove the ability to debug/program using SWD, but do they remove the ability to self write? From the TRM (which isn't specific enough in this case):
- PROTECTED mode: The user may change the mode from OPEN to PROTECTED. This disables all debug access to user code or memory. Only access to user registers is still available; this prevents debug access to reprogram flash. The mode can be set back to OPEN but only after completely erasing the flash.
- KILL mode: The user may change the mode from OPEN to KILL. This removes all debug access to user code or memory, and the flash cannot be erased. Only access to user registers is still available; this prevents debug access to reprogram flash. The part cannot be taken out of KILL mode; devices in KILL mode may not be returned for failure analysis.
Flash cannot be erased because debug hardware is disabled or Flash cannot ever physically be erased because of something at the flash controller level?
Show LessWhat can we do to test linearity (INL) of 12bit SAR ADC with sinusoidal signal source which has only 10bit DAC ?
Simply put how can i increase linearity performance of 10bit DAC source?
Appriciate your comments
Thanks
Show LessHi,
I'm working in a project where I need to connect sensors with diferent interfaces, but I would like to use the same connector for all of them with the minimum number of pins possible. So what I thought of doing is to have the ADC, SPI, and I2C sharing some pins. To do that I think the only option that might work is using an analog MUX and then dynamically choose which of the outputs connect and also change the pin configuration from analog to digital and vice versa.
I haven't test it yet because I found a problem with the I2C component. The only master I2C component that creator gives you is one that uses SBC and you don't have the pins available to do what I want.
Anyone have any idea of how I could do what I want witout using more components?
I've attached an image of how I'm trying to do it.
Thanks in advance.
Show LessHello,
I'm trying to blink an LED to learn about PSoC, using Pioneer Kit, and Creator 3.0.
I know there are easier ways to do this...
I'm using a Counter component.
Clock_1, 12 MHz, connected to Counter_1 clock input
Clock_2, 128 Hz, connected to Counter_1 count input
Counter_1 comp output connected to Digital Ouput pin Pin_Green (P0[2])
When I attempt to 'Generate Application' I get the following errors:
mpr.M0119:Invalid connection for clock "Clock_2" connected to "\Counter_1:CounterUDB:count_enable\:main"
mpr.M0119:Invalid connection for clock "Clock_2" connected to "\Counter_1:CounterUDB:count_stored_i\:main"
The datasheet for the Counter_v2_40 states that "You can connect any digital signal from any source to the clock/count input.
Are there some other rules about signal connections between components that I need to refer too?
Any help would be appreciated.
Thanks,
Jeff
Show Less