PSoC™ Creator & Designer Forum Discussions

I'm italian freelance. I receved a to develop firmware for the cypress MCU. Being new, I need help to start. I have several question

1) As written in the title...what are the difference between the varius PSoC development tools?

2) How does the cypress PSoC work? and How can I program them.

3) How many different PSoC family exist and what the difference between them?

Are there old releases of the kitprog firmware and is there an easy way to load them into a kitprog adapter?

New CY8CKIT-059 boards are shipping with version 4.19, the GUI tool will only write 4.18; but, I can only get version 4.11 working under Linux with openocd.  I may be able to use something between 4.11 and 4.18, I just know that 4.11 works and 4.18/4.19 don't.

Thanks

Mike

Hi,

I'm using printf with a variable of type uint32_t. Variables of this type have a fixed with of 32 bits, so this equals to long int in C. Is this true?

So, for printf, the correct format string is:

printf("%lu", Var);     //%lu => long unsigned

Now, it's getting strange: If I use %lu, I get no error in the notice list after a build, but a error indicator in the corresponding line of the source editor window, saying "format specifies type 'unsigned long', but the argument has type 'uint32_t' (aka 'unsigned int')".

If I use %u, the error indicator in the source editor window wents away, but after a build a warning is shown in the notice list: "format '%u' expects argument of type 'unsigned int', but argument 2 has type 'uint32_t {aka long unsigned int}"

This is confusing. I know I can use

printf("%lu", (long int)Var);

which eliminates both error indicators, but I wonder why there are errors different positions (source code window vs. notice list), and why %lu gives an error - %lu should be right IMHO.

Is the behaviour regarding the error messages a bug of PSoC Creator? Should I file a case about it?

Regards,

Ralf

Is there a way to prevent the Emulated EEPROM component API from generating a Doxygen mainpage?  This page, while interesting, is not the first thing I want readers of my documentation to see.  Here is the offending code, from the generated file cy_em_eeprom.h:

/*******************************************************************************

* \file cy_em_eeprom.h

* \version 2.0

*

* \brief

*  This file provides the function prototypes and constants for the Emulated

*  EEPROM middleware library.

*

********************************************************************************

* Copyright 2017, Cypress Semiconductor Corporation.  All rights reserved.

* You may use this file only in accordance with the license, terms, conditions,

* disclaimers, and limitations in the end user license agreement accompanying

* the software package with which this file was provided.

*******************************************************************************/

/**

* \mainpage Cypress Em_EEPROM Middleware Library

*

* The Emulated EEPROM provides an API that allows creating an emulated

* EEPROM in flash that has the ability to do wear leveling and restore

* corrupted data from a redundant copy. The Emulated EEPROM library is designed

* to be used with the Em_EEPROM component.

...

I need to make a custom build of Capsense_P4Library_GCC.a library. Where can i download the source code that builds to create this library? I did not find it in the PSoC Creator 4.2 installation. I need to do this for CY8C4147-S455 part.

Hello everyone,

                      how to interface  i2c  with psoc board by using verilog... anyone please give me idea about this.

Hello,

  Like in topic :

  Is it possible to add cyprimitives : cy_clock_v2.0 into Psoc Creator V4.0 ?

Best regards,

Piotr.