PSoC™ Creator & Designer Forum Discussions
Hi, is there any way to change the "Desired Frequency" of the WS2812 component?, i'm using the component on a design with the 5LP P.K., fist @ 24 MHz and it runs very good, but if i change my design to run @ 48 MHz the led's are all white.
Checking other designs (at the left on the image attached) with the same component the "Desired Frequency" is setup @ 48 MHz, i'm unable to find the way to change that parameter and i'm afraid that is what i'm missing to make it work well.
Show LessI want basically the same thing, except with asynchronous set from input, and then output is ORed with input so the output pulse length is at least 1 clock cycle, up to the input pulse length. There's probably a simpler circuit with a flip-flop or something but I couldn't think of it. Similar to a retriggerable monostable multivibrator
Show LessFor the SAR ADC example, where an ADC is used with an analog input pin, just a simple question:
Why do we have to assign a physical pin to both the ADC and the analog input pin? Doesn't the ADC "not" need a pin, because we are connecting it to the analog pin? It would seem to me that the connection between the ADC and the pin would be internal...
-RT
Edit: just for clarity sake, here's what the lab 4 manual says:
map the “ADC_SAR_Seq_1:Bypass” pin to P1[7], and “Pin_1” to P2[0]
Show LessI moved some of the generic functions and modules to a static library.
My application does not have problem linking the library and seems running fine. I can even trace into the functions in the library and do step-by-step debugging. But I can not set breakpoints inside library functions. It shows a hollow circle on the leftmost column instead of a solid circle. The breakpoint is completely ignored. (see attached).
I can go step-by-step and get there and make a stop on that statement.
I believe there is a bug that the debugger can not locate the source for BREAKPOINTS. The debugger finds the source if it moves into the library step-by-step.
What do you think? Are there workaround ?
Thanks
Gregory
Show LessPardon the ignorant question. I'm attempting to introduce myself to PSOC UART programming by studying the document entitled, "Simple 8-Bit UART Communication Example – PSoC® 3 / PSoC 5," at link, http://www.cypress.com/file/50321/download. I have one simple question: Where exactly can I find the code examples that it is referring to, such as in the Design Wide Resources section of page 3, which says to " Refer to the Example_UART.cydwr file for the settings," or under the Operation section of the same page, which says, "In this example a flag, ‘flag_keyPress’ is set inside ISR_UART.c."?
The answer must be obvious, but I'm pulling my hair out trying to find this example code, which is not included in the document. This is totally new to me so I was hoping to study an existing code example this document is referring to.
Thank you.
Show LessHi,
Just wondering, has anybody tried to use PSoC Creator with a newer arm-none-eabi-gcc version? I think the actual Creator (3.3) use version 4.9 while the "stable" version is 5.4 [1].
So, what advantages can i get if i get a newer version of arm-none-eabi-gcc? My projects are not big or complex enough to see a significant difference (i think).
Also i saw the PSoC roadmap and there's a PSoC 6 (ARM Cortex M4 + ARM Cortex M0 dual core) in development, and a PSoC 7 (ARM Cortex M7 core) in concept phase, i think those will get bigger advantage of the newer versions of arm-none-eabi-gcc.
Thanks in advance 🙂
Carlos
[1] https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads
Show LessHi Everybody,
for a project i have to send a data request string via the SCB (in UART mode) to a serial device.
My problem is, that this request string has a 0x00 Char in it. Example: char rp[] = {0x64, 0x65, 0x00, 0x64, 0x65 };
If I monitor the output with a terminal program, the transmission via UartPutString stops before 0x00 because of the string termination.
The receiver only accepts/understands the request paket, when he receives it as a string at once.
( I tried UartPutChar and transmit every single char, but it fails...)
Any idea how I can fix that problem?
Device: CY8C4125AXI-483, PSocCreator 3.3
Show LessI am trying to print to the terminal using teh printf() function. I am able to print using UART_UartPutString() but the printf function doesnt work. I did include the file to assign _write() function of GCC.
Kindly have a look at the attached project here and tell me where I am going wrong.
Thanks
Show LessKaspersky antivirus detects Creator 3.3SP2 as malware and kills the process.
It also looks for files touched by that software and reverts them. It deletes entries in the registry.
I first noticed this behavior several weeks ago in 3.3CP2; I reported it both here and via a service ticket. I was told it would be fixed in SP2 but it clearly hasn't been.
This needs to be addressed. It's been weeks since I've been able to work on my primary PC due to this bug.
Maybe if there were some way to tell Creator *not* to send usage statistics in, that would be something at least; it seems to be a phone-home type of operation that Kaspersky objects to.
Show LessHi All,
I've been working on a project using EZ-BLE modules and CY8KIT-042 pioneer kit and somehow things have gotten messed up. I don't know why but some typedefs aren't working within the generated source.
For example, I look at BLE_StackGatt.h, scroll through and see an error "unknown type name 'CYBLE_API_RESULT_T'.
In BLE_StackGattDb.h I get the same as above and also "unknown type name 'CYBLE_GATT_ERR_CODE_T'
And same for:
CYBLE_GATT_HANDLE_VALUE_PAIR_T
CYBLE_CONN_HANDLE_T
CYBLE_GATT_DB_ATTR_HANDLE_T
There is probably the same issue elsewhere that I haven't seen.
The files declaring these typedefs are all present and appear correct, they're included in project.h
Not sure what's going on..
I've tried deleting all generated source and rebuilding. I've tried opening the workspace on a different PC. I've tried changing target devices.
Can anyone suggest what may have gone wrong please?
Thanks,
George