PSoC™ 4 Forum Discussions
Hello,
in the attached project I try to adjust the brightness of the onboard LED with a Rotary Encoder
Question 1: If I enable line 27 ("LED_BLUE_Write(0u);") by the removing the comment signs
the rest of the code does not work as I aspect. Turning the Rotary Encoder has no effect!
Why is this so? (with the line disabled it works as I aspect!)
Question 2: What do I have to change that the code from line 47 to 69 is executed in an interrupt routine, where the interrupt routine is initiated every time the Rotary Encoder is operated?
Thanks in advance,
Giel Peters
Hello,
I successfully programmed the kit along with the bootloader and found it to be working satisfactorily. I am using the serial port program mode as I do not have Mini Programmer. I even power cycled it multiple times and it was working fine.
If I switch on the power after a day, the kit automatically goes in to bootloader mode and the main program does not work.
I anticipate that the bootloader is working fine however the main program is getting corrupted. Any pointers in this regards will be helpful.
Thank you in advance.
Kuldeep
Show LessHello, I'm trying to connect keypad, but I have problems even with creating of circuit.
I have errors like this - " Two or more connected terminals have mismatching types. All connected terminals must have the same type (i.e., all analog or all digital). Remove the incorrect terminal(s) and replace them with the correct type"
I'm newbie in this and rly hope for your help.
Here is scrshot of my project.
Show LessHi,
I am using the prototyping kit do control two stepper motors.
The motor drivers need a short pulse of a few microseconds to make a step. In my project there are 2 digital output pins, both set to "strong drive", connected to the same control register. One is routed to P0.1, the other is routed to P1.7. Both are wired to the "step" input of two identical motor drivers.
When I make a short pulse by writing to the control register, P0.1 rises immediately and drops immediately, creating a nice rectangular pulse. P1.7 stays at 0V.
Then I introduced a delay of 100us between the rise and fall commands. P0.1 still shows a nice rectangular pulse, but P1.7 needs about 50us to rise to 5V, then stays at 5V, after 100us it falls to 0V immediately.
I swapped the motor controllers, still the same behaviour.
Then I changed the pin mapping from P1.7 to P0.2, rewired my board. Now both pins show the same nice rectangular signals.
What is the difference between P0.1 and P1.7? Is P1 "weaker" than P0? I can not find anything in the data sheets.
Best regards,
Turtle
Show Lesssoftware : Psoc Creator3.3
Sample code :BLE Heart rate sensor
Hardware :CY5671 Proc BLE Module, Mini Prog3
The sample code is programmed into CY5671 to connect to cysmartApp When you get an error.
Error Display: The connection has timed out unexpectedly
Cause I do not know.
Please help me.
Hello, I am wondering if someone could help me clarify the expected behaviour when disabling interrupts as I can’t quite get my head around it at the moment.
I have setup a falling edge interrupt on a digital input pin, and have an ISR that clears the interrupt and sets a flag. This all works as expected, however after the interrupt has been triggered once I expect a series of falling edges so would like to disable the interrupt until these have finished. I’ve tried using the _stop() and _disable() interrupt API commands and while these do prevent the interrupt from firing whist it is disabled, as soon as I use the _start()/ _enable() commands the ISR is triggered again. I have tried using the _ClearInterrupt() and _ClearPending() commands just before I re-enable the interrupt but this makes no difference. I realise that I haven’t disabled the interrupt signal from the digital pin, but would have thought that using _disable() would mean that this signal is ignored, or at the very least using the ClearInterrupt just before re-enabling the Interrupt would mean that any pending interrupts would be cancelled. Can anyone explain why the ISR is still being triggered please?
Thanks in advance.
Show LessPlease can somebody on this list enlighten me on the following problem:
New to the PSoC devices I am trying to understand how they work.
Made a simple program (software) to blink two LEDS where one LED is on the other is off.
This worked as I aspect.
Then I wanted to do the same in hardware (no programming involved)
Put two dividers in serial, connected one LED directly on the output of the second divider.
In front of the other LED I put an NOT gate and connected the input of the NOT gate also
with the output of the second divider.
Expected behavior: One LED on the other LED off and vice versa.
But both LEDS blink at the same time (LED 1 on = LED 2 on etc.)
See schematic attached,
Thanks in advance for any entlightment,
Giel Peters
Show LessHi all,
I am developing an application with a PRoC BLE as a Peripheral, where I would like to support pairing with a Central device using a fixed 6-digit passkey, ie. not a randomly generated one. Is that possible?
My device does not have display capabilities and a very limited keyboard that is not sufficient for entering all 10 digits. If I set the I/O capabilities in the GAP security settings to 'Display Only' then the stack will generate CYBLE_EVT_GAP_PASSKEY_DISPLAY_REQUEST event for displaying a randomly generated pin. There does not seem to be a way for setting a fixed passkey.
Thank you,
Stathis
Show LessHi all,
I have tried to implement this in a P4200 Kit, but with no success.
http://www.cypress.com/file/136326/download
Question, is it possible with a PSoC4? If yes, how?
Thanks
Franz
Show Less