PSoC™ Creator & Designer Forum Discussions

Hi All,

I am up to my elbows in a design project and so far have found PSoC Creator to be fairly productive (actually it's better than any other programmable logic vendor software I have EVER used in most respects).

I am very experienced with much more capable design tools (Altium Designer - in the interest of full disclosure I work for Altium during the day, but this post is purely to get some help with my current PSoC4 project).

I must admit I am finding the schematic editor quite limited and difficult to work with. I did eventually by trial an error figure out how to change the template to be 11x17 which is much better.

But I still have a few newb questions (hopefully there's a good answer!):

    
• Is it possible to have multiple sheets in one project? I cannot seem to create any other sheets but the top level.
    
• Why are some document parameter fields read only? (eg. Created By - I started my design from a reference design which was created by cypress, but it's evolved to the point where I feel I can truly call it my own but I am unable to edit this field).
    
• Is it possible to use an external schematic tool like Altium Designer which I am already very experienced with in order to be more productive, and then bring this in as a Verilog netlist for the project as an alternative to using the Cypress schematic editor which, to be honest, is a bit like having one hand tied behind my back?
    
• What is the file format of the Psoc creator schematic editor? If it's based on ViewLogic or Mentor Logic I might be able to translate back and forth between PSOC creator and Altium Designer...
    
• Does Cypress ever plan to build a plugin for AD to link it's schematic editor with PSoC Creator? (no need to answer this - it's a gentle suggestion).
   

Thanks!

Ben J.

Hi All,

I am up to my elbows in a design project and so far have found PSoC Creator to be fairly productive (actually it's better than any other programmable logic vendor software I have EVER used in most respects).

I am very experienced with much more capable design tools (Altium Designer - in the interest of full disclosure I work for Altium during the day, but this post is purely to get some help with my current PSoC4 project).

I must admit I am finding the schematic editor quite limited and difficult to work with. I did eventually by trial an error figure out how to change the template to be 11x17 which is much better.

But I still have a few newb questions (hopefully there's a good answer!):

    
• Is it possible to have multiple sheets in one project? I cannot seem to create any other sheets but the top level.
    
• Why are some document parameter fields read only? (eg. Created By - I started my design from a reference design which was created by cypress, but it's evolved to the point where I feel I can truly call it my own but I am unable to edit this field).
    
• Is it possible to use an external schematic tool like Altium Designer which I am already very experienced with in order to be more productive, and then bring this in as a Verilog netlist for the project as an alternative to using the Cypress schematic editor which, to be honest, is a bit like having one hand tied behind my back?
    
• What is the file format of the Psoc creator schematic editor? If it's based on ViewLogic or Mentor Logic I might be able to translate back and forth between PSOC creator and Altium Designer...
    
• Does Cypress ever plan to build a plugin for AD to link it's schematic editor with PSoC Creator? (no need to answer this - it's a gentle suggestion).
   

Thanks!

Ben J.

We discussed this a while back ....

Where on this website can we announce PSoCentric hardware products? Robyn and others post entries to their blogs on products they review.

A few minutes ago we released initial information on our j1Pub Component Library. This is a gift to the PSoC community.

We also are announcing our first two PSoCentric hardware products available for immediate order.

SAK-PROTO - a versatile PSoC 5LP development board that includes a 2.8" TFT LCD w/Touch, microSD, microUSB and many user defined I/O pins.

HY28B Adapter - the same 2.8" TFT LCD w/Touch module adapted to replace the Character LCD on a PSoC 5LP Development board. Other uses, such as connecting to other boards via a ribbon cable, can be implemented.

Complete information and pricing is available in the PSoCentric section of our website. Cruise over and take a look.

www.j1sys.com/products/psoc

-Ed

<p>We are pleased to release our j1Pub Component Library</p>

<p>j1Pub is our component library containing all
of our public components. Simply install the library somewhere on your system and add j1Pub to your project dependencies and you will have access
to all of our components. There are software library and hardware oriented components for use with our development and production hardware.</p>
<p>All components have been tested on PSoC Creator 3.1 SP2. Most software only components should work on PSoC 4 and PSoC 5LP. Only tested on PSoC 5LP.
The hardware oriented components only support PSoC 5LP at this time. We will be enhancing them for PSoC 4 support soon.</p>
<p><hr></p>
<p><b>All components offered AS-IS with no warranty expressed or implied. Please use at your own risk.</b></p>
<p><hr></p>
<table cellpadding=2px>
<tr><td colspan=2>Components:</td></tr>
<tr><td>   j1Console v1.1</td><td>Simple serial console functions</td></tr>
<tr><td>   j1Conversion v3.0</td><td>Our standard binary to text and text to binary conversions</td></tr>
<tr><td>   j1ENC424 v1.0</td><td>Hardware driver for ENC424 Ethernet chip</td></tr>
<tr><td>   j1FAT32 v1.0</td><td>FAT32 library functions (read-only)</td></tr>
<tr><td>   j1FreeRTOS_8_2_1 v1.1</td><td>FreeRTOS 8.2.1 ported to a PSoC component</td></tr>
<tr><td>   j1FS v1.0</td><td>A simple linear memory read-only file system</td></tr>
<tr><td>   j1Get v1.0</td><td>Simple buffered character input functions</td></tr>
<tr><td>   j1GFX v1.1</td><td>Device independent small graphics library</td></tr>
<tr><td>   j1HY28B v1.5</td><td>HY28B LCD driver component</td></tr>
<tr><td>   j1microSD v1.0</td><td>microSD driver component</td></tr>
<tr><td>   j1MINIZ v1.0</td><td>Simple porting of the MINIZ.c zlib source file</td></tr>
<tr><td>   j1Put v1.2</td><td>Common device independent simple formatted output functions</td></tr>
<tr><td>   j1SpiFlash v1.0</td><td>SPI driver for external flash storage</td></tr>
<tr><td>   j1Types v3.0</td><td>Our standard data types header</td></tr>
<tr><td>   j1UBL_ProjectDesign v1.2</td><td>A containerized project design for a complete j1UBL</td></tr>
<tr><td>   j1UBL v1.2</td><td>Our enhanced bootloader based on Cypress bootloader component</td></tr>
<tr><td>   j1UBL_XML v1.1</td><td>XML dictionary and functions for j1UBL XML manipulation</td></tr>
<tr><td>   j1XML v1.1</td><td>Table driven XML parser</td></tr>
</table>
<p><hr></p>
<p>j1Pub is released as a compressed minimal workspace archive from PSoC Creator. It should be unzipped at a user selected location.
To use the component library you will just need to add a dependency to the library in your application project.</p>

<p>For more information and to download the library please visit the PSoCentric section on our website.</p>

<a href="http://www.j1sys.com/products/psoc">http://www.j1sys.com/products/psoc</a>

In Creator 3.1, it introduces a new option. (See Pic)

This option has some problem at current version(3.1.0.1570), user should use '-u _printf_float' command in Linker Command Line as a replacement.

In addition, due to sprintf function needs a big heap size, user may get a wrong result with default heap size(0x80). user should increase the heap size at .cydwr > system > Heap Size(byte). It will be enough to change to 0x200.

I am getting this message when I try to click on any tnformation. Failed to open the webpage "http://www.cypress.com/?rID=107124&cache=0&source=creatorStartPage" in your default web browser: (http://www.cypress.com/?rID=107124&cache=0&source=creatorStartPage: No application is associated with the specified file for this operation) How do I fix this issue.

 Hello everybody,

I would like to create a PWM signal ( so with the PWM function in PSoC Designer) with a potentiometer at the entrance (to modify the duty cycle of this signal). Everything works fine but I have a little problem: I would like a minimum value for the duty cycle. And when i see the signal at the exit, it's very strange ! It's not smooth. You can see it on the picture.

 <a href="http://www.casimages.com/i/150417102525799789.png.html" title="Problem PSoC">Lien vers mon image</a>

Can you help me please ? I send you the code too.

 <a href="http://www.casimages.com/i/150417102706438332.png.html" title="code">Lien vers mon image</a>

Thank you.

 I built and tested a bootlaoder/bootloadable that uses the USBUART in the bootalable on a Windows 7 64 bit laptop using PSoC Creator 3.1. The code worked correctly -  bootloader runs as USB HID for 5 seconds then USBUART pops up in the Device Manager Ports list and the seria lcommands to the PSoC 5LP worked as expected.

When I tried to move the design file directory  to a second Win 7 64 bit laptop I moved the directory to the new laptop and then used the Bootlader Host to download the Bootlaodable  to PSoC 5LP that had the bootoader preinstalled. All seemed to work properly, the programming worked and the PSoC 5 now appears to runs correctly, it powers up in bootloader then transitions to the bootloadable ( I can tell this by LED state). The problem is that I can't now get Windows 7 of the new machine  to accept the proper driver , USBUART_1_cdc.inf when I point to it as described below.

I open the properties dialog of the Unknown Device entry in the Device Manager's Universal Serial Bus controllers list, choose 'Update Driver Software', choose  "Browse my computer for driver software', choose ' Let me pick from a list of device drivers on my computer, click 'Have Disk' then I select the directory that contains USBUART_1_cdc.inf. The result is I get popup that says :

" The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."

I can't get past this. It seems the .inf should be fine since I was using Windows 7 64 bit machine when I generated the design files in PSoC Creator 3.1 on the other machine and everything worked fine.

Any suggestions greatly appreciated. I am stuck.

-Alan

Hi, 

I am a complete newbie to PSoC 3, so I apologize in advance for my ignorance and if I have no provided the necessary information. I have successfully created a custom printed circuit board for the PSoC 3 AXI-040 for a course that I am taking. I would like to figure out how to display the ADC readings from an Ultrasonic sensor (that is hardwired to my custom PCB) and display these readings to Putty (or something else?) through UART so that I can interpret/debug my ultrasonic sensor code while connected to my PCB.

I did something similar last semester using the PSoC 4 Dev Kit, where the flex sensor readings from the ADC were sent via UART to a Putty window. But again, this was on the dev kit and not a custom PCB. Still, it made my life so much easier for debugging/tuning the code so that I could send accurate information to the actuators. I need to do something very similar again this semester, but I have no idea where to start since I am using a custom printed circuit board and MiniProg3. 

I already wrote the ultrasonic sensor code using the PSOC 3 dev kit and had it display the ADC values to the LCD so that I could verify that the sensor is working correctly. My next step is to move to my custom printed circuit board and make sure that the ultrasonic sensor is working on it. The best way for me to do this is to have it display the values from the ADC through a terminal window like Putty. Using the MiniProg3 and the PSoC Programmer IDE, I have managed to successfully program the chip using the code for the sensor. Or at least it says it was successful. I have also programmed the chip on my PCB using PSoC Creator. It also said it was successful. The problem is, I have no idea if it is actually working on my custom PCB since I cannot see any sort of output from the sensor (custom PCB does not have LCD connections, so I can't use that). Additionally, I have no way of further debugging my code (when I incorporate the sensor with machine vision and actuators) since I cannot see what the ADC readings are for the sensor.

So, how can I display the values from the ultrasonic sensor (ADC) to Putty or something else through UART? Or is there some other way that this can be achieved that I don't know about? I am getting concerned because I have read a lot online that states that it is not possible to do this since the COM port for Putty is using the MiniProg 3 already. Is this true? Is there no work around?

Thank you all for your time and assistance. 

Start your update managers and update your Creator software to service pack 2.

Happy coding

Bob