PSoC™ Creator & Designer Forum Discussions
I have about 800 Mb of files saved under directory PSoC Creator on my local drive.
I want to move all of it to the company server (sort of server - it is actually dropbox) .
windows 10 will let me drag and drop said files, but i am concerned that
whatever links and relationships there are between them, produced by PSoC Creator,
will disappear with the net result that all will be lost and unre-coveable
is there a procedure to move said files and not lose the (presumed) links and relationships,
so that the files behave the same, open the same, and save as when they are local?
Show LessWhen i Try to Use the feature "Find All Active References" in PSoC Creator I get this error:
Unhandled Exception has occurred in a component in your Application. ..... File format is not valid.
************** Exception Text **************
System.ArgumentException: File format is not valid.
at System.Windows.Forms.RichTextBox.StreamIn(Stream data, Int32 flags)
at System.Windows.Forms.RichTextBox.StreamIn(String str, Int32 flags)
at System.Windows.Forms.RichTextBox.set_Rtf(String value)
at CyDesigner.Framework.FindReplace.CyFindResultsToolWindow.UpdateDisplay(Boolean scrollToEnd)
at CyDesigner.Framework.FindReplace.CyFindResultsToolWindow.ForceDisplay(Boolean scrollToEnd)
at CyDesigner.Common.Editors.CyFileEditor.FindAllReferencesDoneCallback(CyRsltOrErr`1 result)
at CyDesigner.Common.Editors.ClangDetail.CyClangRequest`1.<>c__DisplayClass2`1.<CallbackInvoker>b__0(Object obj)
This fail is present both in version 4.3 and 4.4
The rest of the details are attached.
Show LessWe intend to use Cypress PSoC Creator 4.3 and CYBLE-214015-01 in a medical device development according to IEC 62304 and FDA guidances.
The medical device has moderate level of concern (FDA) and software safety class B (IEC 62304).
- Do you have a validated/certified PSoC Creator according to IEC 62304 and FDA guidances?
- Do you have a basic documentation for the sources generated by PSoC Creator?
- Do you have a basic documentation for the standard library functions like memcpy, etc.
A basic documentation means an answer to the following questions:
- Identification of the OTS / SOUP Software
- Title
- Manufacturer and Country of Origin
- Version Level
- Release Date
- Patch Number
- Upgrade Designation
- Retrieved from
- Digital Signature or Checksum
- Reference Documentation
- Known Bugs
- Availability as Source Code
- Access to Updates
- Hardware and Software Requirements
- Actions Required by End Users
- License Information
- Copyright Information
- Expected Design Limitations
- Description of the OTS / SOUP Functions
Hi all, I hope this is OK for me to post and is the correct place to post this question.
I have a HOTAS PC joystick game controller (Hand On Throttle And Stick) which uses a Cypress CY8C24894. Unfortunately, the throttle stopped being recognised by windows via USB. Apparently this is very common and sourcing a repolacement PCB direct from Thrustmaster is the fix. I've contacted Thrustmaster and hopefully I'll get a replacement PCB soon.
However, being somewhat of a electronics hobbiest, I started to wonder how easy it would be to source a new chip. I've soldered many small SMD packages before. So I ordered a couple of CY8C24894 chips and I've since replaced the defective chip with a new one.
Now, obviously this chip is brand new and has nothing on it. Obviously the proprietary Thrustmaster firmware updater app doesn't recognise it. I'm assuming I need to get a bootloader onto the chip via the I2C interface? But, even then, will the Thrustmaster updater app recognise it?
Anyway, no great shakes if I can't do anything. Hopefully a replacement PCB will arrive from TM soon. I was just curious, I like a challenge and I'm always up for learning something new.
If anyone can provide any information on how to get the TM firmware onto the new cyrpess chip, I would be very grateful to you.
Many thanks in advance.
Show LessHi, i have gotten some problems when i try to start on my psoc creator 4.4, because it doesn't begin and windows show up a compatibility problem, i have been using psoc creator since july with out problems, but on the last week appeare the problem.
I appreciate any help or advice, thanks.
Show Less
Greetings,
My project has a warning (see below) saying that the clock accuracy is not within the specified tolerance range. What are the implications of this warning? Any suggestions on how to fix it?
Thanks in advance!
Show LessAn earlier discussion, C8CKIT-059 does not appear in target device, a response says:
PSoC Creator has knowledge of PSoC devices such as the CY8C5888LTI-LP097 but does not have knowledge of the Cypress Kits.
OK, but that seems unfortunate. The pinout displayed when I select device type CY8C5888LTI-LP097 shows the pinout of the PSOC chip, rather than the kit's pinout, I think that's what @SKDK_4669631 was posting about.
What I want to know is if a PSOC Creator feature to add knowledge of a kit (in particular the pinout of the kit) to be displayed in place of the chip's pinout. Is there such a thing as a device template that can replace the the PINS diagram with something like this:
rather than this:
The CY8C5888L-LP097 diagram may be correct at one level, but it's not the level that someone working with the prototyping kit needs. Instead a diagram that line-up with the board being used would be more helpful.
Show LessDoes anyone have the problem? I just upgraded PSOC Creator from 4.3 to 4.4. My workspace/projects are on a network drive (mapped to my W: drive). It was fine in 4.3 to open the projects. However, I could not find any mapped drive in 4.4's file open dialog. How to solve the issue? Thanks in advance.
Show LessHi,
I'm trying to do some very advanced things with Component Customizers. I'm hoping someone can help me.
My successes
- I have imported the WaveDAC8 component into a project.
- I have loaded the C# customizer code pieces into Visual Studio 2019 (VS).
- I can see the GUI objects of the designer.cs and .resx in VS.
- I can modify the GUI objects from VS.
- I have modified the component customizers and can see the changes reflected in the "new" component (Customizer builds work).
My Goals
For all intents and purposes, I should be happy with these successes. There are MANY things I can do at this point by modifying code in VS or Creator.
In the future hope of creating new components and their customizers, I'd like to hook the customizer builds into the VS environment more completely.
The next step I'm trying to achieve is to make calls to the CyCustomizer methods and properties from within VS. This would allow two advances:
- A VS build will allow the GUI layout to be executed in this tool.
- If I can execute a VS compatible version of the customizer, I would have better debugging ability to correct issues that might show up in Creator after a customizer build.
In the successes I list above, any modifications I make are very difficult to debug should exceptions occur.
I attempted to execute the CyCustomizer function EditParams() from the Form1.cs initialization method. See code below.
public partial class Form1 : Form
{
public Form1()
{
ICyInstEdit_v1 edit;
ICyTerminalQuery_v1 termQuery;
ICyExpressMgr_v1 mgr;
CyCustomizer customizer = new CyCustomizer();
InitializeComponent();
customizer.EditParams(edit, termQuery, mgr);
}
}
It fails because the parameters edit, termQuery and mgr are not initialized.
What am a missing?
Is there a better way to achieve my goals?
Is there a way to debug the customizers in Creator with source code?
Your help is appreciated.
Len
Show Less