PSoC™ Creator & Designer Forum Discussions

All,

background: you can only use PSoC Designertogether with a PSoC 1 in mind. It is possible to evaluate the user interface of Designer without hardware but you will get stuck sooner or later.

On the other hand, when you are using PSoC 1, you will use PSoC Designer by definition because it is the only tool to configure the hardware of PSoC 1

Because these subjects, PSoC Designer and PSoC 1 are so closely related, we are discussing to merge the content of both forums and call it a PSoC 1   --  Hardware  --  Software  --  DevKits Forum

You feedback is greatly appreciated and if we get a number of votes, it will have a strong impact on the decision.

Please post your opinion in this thread.

Cheers, Robert

possible answers could be:

    
1. Great, we can see all related topics
    
2. Please don't do this, I would like to see these topics separated
    
3. Either one is fine with me
    
4. Other: ________________________
   

Hello fellow PSoCers

Following on from my previous posting on the subject of workspaces (http://www.cypress.com/?app=forum&id=2492&rID=50054), I also have some issues about the usability of 5.1

(1) Stability. It seems to me that this version is much less stable than the previous Designer that I have used for a few years (4.2). Irritatingly often it seems to lose connection with the pod (or the ICECube -it's hard to tell where the problem is), requiring one to restart the program or plug the ice in and out to get it going again. Worse, it hangs up completely quite often (with an hourglass that never goes away - for example when the Reset icon is clicked - see below). Another manifestation is when stepping, the execution point is shown as being at the beginning of a source file (not a valid code line) and the program just hangs.

(2) Reset. Version4 (in particular 4.2 that I used) had the property that when one is debugging a program, if you click the Reset icon, the program simply resets back to the start; then you can do normal debugging again, without having to relead the program. This is something that one does a *lot* while debugging with an ICE. In particular it allows one to debug what happens when the target is powered on or reset. (NB The program may have written something in Flash!)

Very annoyingly, 5.1 does not seem work like this. It requires you to reload the program! Doing this once or twice is a minor irritant - doing it dozens of time in a hard day's debugging is enough to drive you to drink (:  I suppose this may be just one of the ways that the program reveals its instability rather than the intended behaviour.  If this *is* the intended behaviour (surely it can't be) - it would be impossible to debug resets.

In summary - (1) and (2) render 5.1 almost unusable in my view.

3. Shared files. When one is working with multiple projects that share some of their headers and code (e.g. in my projects the inter-processor communication data structures and code is common to a number of projects), what one does *not* want to do is have multiple copies of ostensibly identical source files - you want to literally use the same files in all the projects. With version 4 I could do this, as follows.

(a) By having a line like this in local.mk "INCLUDE_PATH:=$(INCLUDE_PATH);../../../myIncludeDir".

Then by having source files containing lines like this: #include "sharedSrcFolder/sharedThing.c", where sharedSrcFolder is in myIncludeDir, one is using the shared code files. And, of course, header files can also be shared.

(b) The files included in this fashion are listed in the project explorer in the External Headers folder, making it possible to set breakpoints in included code files.

Now the bad news: version 5.1 supports (a) but *not* (b). This is a serious handicap.
 

Of course, some or all of the above might be related to my particular setup. I am working on a brand new Windows 7 Pro (x64) machine with lots of RAM and fast processor.

I am very interested to find out if other users have had similar experiences; and, if there is (a) any substance to my problems, then (b) is there any likelihood that Cypress will do anything about it?

Regards, Tim

On prior embedded projects, I would debug some code, and get some bit of it working--and save a copy of that.  That way, if something broke, no matter how many changes I had made since the last "version" I could always roll back.  I would do this by basically doing a "save copy as", in which I would take the file name and append "_v1.3" or somesuch to it.  [That way, the working file would stay as it is, and I would not have to changing any linking.]

I don't see a "save copy as", though; just "save as".  Which brings me to question #2: can my main program file be something other than "main.c" or is it stuck with that as the main file?  Software is not my forte, and I haven't a real clue how other C projects are done.  If "main.c" could be anything, I could just keep updating this file name, and look back if necessary to other files if I made some mistake.

Thanks

Shawn

All,

background: you can only use PSoC Creator together with a PSoC 3 or PSoC 5 in mind. It is possible to evaluate the user interface of Creator without hardware but you will get stuck sooner or later.

On the other hand, when you are using PSoC 3 or PSoC 5 you will use Creator by definition because it is the only tool to configure the hardware of PSoC 3/5

Because these subjects, PSoC Creator and PSoC 3/5 are so closely related, we are discussing to merge the content of both forums and call it a PSoC 3   --  Hardware  --  Software  --  DevKits or similarly a PSoC 5   --  Hardware  --  Software  --  DevKits forum

You feedback is greatly appreciated and if we get a number of votes, it will have a strong impact on the decision.

Please post your opinion in this thread.

Cheers, Robert

possible answers could be:

    
1. Great, we can see all related topics
    
2. Please don't do this, I would like to see these topics separated
    
3. Either one is fine with me
    
4. Other: ________________________
   

When I create a new project, "error1.PNG" pops up

When I click Yes in that and go on and click on the design area, I get "error2.png" popup .. This doesn't end. When I try to exit  PSoC designer error2.PNG pops up again.

Both the error images which I get are in the attached zip folder. Please help me out.

I am openning a special post for implementing CAN Bus in PSoC 3 and 5.

Please check the attached link for a report that explain the procedures (step by step) of implementing CAN bus.

The report include a link for video demonstration, also a link for the project files.

ia700402.us.archive.org/2/items/CanBusInPsoc5_482/CanBusInPsocReport.pdf

If you need any information or help about this topic, you can ask me.

I'm not much of a software guy.  My method of debugging code is to always have some open I/O bits, and I will strobe them at various times, as necessary, to figure out what is wrong.  [Then again, I don't do much code in general.]  I don't use debuggers.  Just load the program, and run it--at full speed.

I just got the PSOC development board going, with the PSOC5 module (CY8C55).  The basic LED PWM program worked, so I went to the first example in which one writes something (Sample Projects, Section 3.3, of "CY8CKIT-001_PSoC_Development_Kit_Guide.pdf").  For some reason, the software LED portion would not blink for me; then I went and duplicated the PWM portion onto LED2, just to continue to learn.  This time I did get both LED's to blink.

However, they blink at about 2 to 3 times slower than I'd expect--ILO divided by 10 and 20, to the PWM with a count of 100 (for reset) should give me 1Hz and 0.5Hz blink rates.  And with a half-on, half off for illumination.  Instead I get like 0.3Hz and half that; and a very fast blink.

Is there "stuff" running in the background, for debug purposes?

Thanks

Shawn