PSoC™ Creator & Designer Forum Discussions

I'm getting "No Input Errors" across one page of my project.
The other pages build just fine.
I tried to clean and build but no luck.
I can't figure out what's going on and any help would be appreciated.

Starting with the Example program UART_Tx01 I successfully printed its output to a Teraterm window. I used an FTDI USB to TTL Serial Cable.

But I would like to print floating point numbers to the terminal using printf. The project build okay using:
 printf("Test printf function. float:%f \n",f);
where f is a float variable. But nothing prints on the terminal.
The LCD_Char_1_PrintInt8(count); function works fine but I want to format floating point output.

I am using the CY8KIT-050 and PSoC Creator 3.3

Hi,

I've a problem with a simple comparison of two variables. Both are of type uint8_t, one contains the bitwise inversion of the other (0x80 and 0x7F). The comparison is 'if(A == ~B) {...}. I'd expect true as result of the comparison. However, debbuging the disassembly shows that the result of ~B is 0xFFFFFF80 is stored in the register, therefore the compare instruction fails.

IMHO this is a bug, because both variables are of type uint8_t, so the result of the inversion should be stripped down to 8 bit. Used PSoC Creator version is 3.3 CP3 & 4.0, GCC for both Creator installations is 'ARM GCC 4.9-2015-q1-update'. Used hardware is a CY8CKIT-059.

Attached is a simple project to show the behaviour. If the variables are made non-volatile, the optimization level must be set to 'none', otherwise the test loop would be optimized out.

Regards,

Ralf

I am going through the PSoC 101 Video Tutorials and have reached Lesson 4 and am unable to find the NOT gate in my component library.  I am using the PSoC 4200 BLE Kit, so component CY8C4247LQ*-BL483 is what I'm programming to.  There are only 197 components loaded in the library.

I have tried going to Tools>Options>Design Entry>Component Catalog and activated "Show Hidden Components".  This does make a plethora of additional components appear, including the NOT gate and all the logic gates, but attempting to add the NOT gate into the schematic failes with the error:

Multiple drivers on signal "Net_25", bit(s) "0".

Every signal bit must have exactly one driver (e.g., connected to one schematic input terminal or one instance output terminal). The given bits have more than one driver each. Remove the extra drivers on the indicated signal.

I then tried downloading and installing the PSoC 4200 BLE RDK (although I may likely have already had it).  This made no discernable difference.  Still 197 components and the not gate not one of them.

Is the PSoC 4200 BLE Kit simply not compatible with logic gates?

In the video for the Basic Counter tutorial 6 for the PSOC 101, it appears that the first condition for the 4-state LED is "off" (which is then followed by the combo of blue and red, then blue, then red, then off, all depending if red is the 0 bit bus or blue).

This implies that the basic counter, after receiving the bit signal from the open switch (which starts out as HIGH 1, notted to produce LOW 0) should not turn on in its initial state.  I was able to see results like this when I used the flip-flop state control from the previous tutorial.

However, for my scenario, whichever LED receives the bit 1 bus happens to trigger first (the one I've been using was blue = 1, red = 0).  This implies that even though the clock initially receives a 0 bit when the switch hasn't been pressed, the counter still triggers an event.  My enable is set to 1 and reset is 0.

I've attached the project bundle.  Let me know if the blue-red-off-combined state is the correct order or if I'm doing something incorrectly to not produce the off-combined-blue-red state.  If the order is the one I'm currently producing, could someone explain how the 0 LOW initial signal triggers the counter?  Is there any initial condition in the hardware that I'm not understanding (I've triple-checked the documentation and found nothing besides how the counter will get triggered when the first HIGH state is received.)

- Anthony

Hi,

I'm following the develop of a custom component and i would like to add a customizer to it, i had search here on the forum and founded how to import a component customizer into Visual Studio, change it and saw the changes reflected into the customizer running in PSoC Creator.

Also found an SimpleDialog customizer example on the Creator installation directory.

What i haven't found is if it's possible to develop the customizer in VS and then import it to the custom component, i'm new to VS and C# and i think this issue is more related to VS than to Creator.

Has somebody developed a customizer for a custom component already?

Carlos

Hi,

Just to play with Creator 4.0 i did installed the newest GNU ARM Toolchain (Version 5-2016-q3-update at the moment) [1], and went to Tools > Options > Project Management > ARM Toolchains, set Default Toolchain to ARM GCC Generic and the place the path to the bins of the newest toolchain on the dedicated place.

Being able to compile, generate the bin files and program the PSoC device as usual (usual meaning using the toolchain provided with Creator) but i'm not able to Debug, there's a couple of errors:

- "There was an unhandled error during the debug session. This has forced the debugger to shutdown. Try again."

- "The request to start the debugger failed. Make sure that all files with debugging information are available."

Don't know if it's related to the toolchain used, is possible to do a debug session with the default toolchain provided with Creator (both projects builded in Debug mode).

I can work with the default toolchain but i would like to know if it's possible to fix the issue.

Thanks in advance

Carlos

[1] https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads

Hi. I'd like to use "#pragma once" in my .h files instead of the old fashioned #ifndef __FOO.H include guards,

It seems to work, but I get the warning symbol and the complaint "#pragma once in main file" in the left margin of the editor, although there are no actually compiler warnings.

Anyone know if this is OK to use, and if so, how to get rid of the warning in the editor?

Thanks!