PSoC™ Creator & Designer Forum Discussions
Hi,
in my current installation (4.1. Update 1, build 3210), there are some defective examples in the examples overview:
- CE215883_MFT_Two_PWMs
- CE216686_Base_Timer_with_ADC
Seems that those examples don't exist on the examples server. Additionally, the inbuilt PDF documentation preview window doesn't work if a PDF viewer other than Adobe Acrobat is installed.
Regards,
Ralf
Show LessForum,
Two days ago I downloaded PSoC 4.1. When I created new header files and tried to link in new libraries, the IDE was never able to find the files during build.
I never had this problem with the IDE before this.
All the header files per 4.0 work as expected. I, however, have not been about to add any new files or libraries. I have used New Build several time--same errors.
John
Show LessWhen editing symbol parameters and tweaking the parameter type, the expanded list opens with "int" on the top, leaving bool and float hidden. No doubt this benefits the users of the ADC... in the title , but when I think about it, a large portion of the parameters I have ever created are bool type and had to scroll to look for it. Wouldn't it make sense to open that list at the very top ?
Tony -- Just a usability though
Show LessI have been working on a component that has a significant number of parameters and find this "feature" a mean torture. Anytime you try to do something on a parameter on the bottom of a long list and then touch a nearby one, the list scrolls back to the top, lossing focus on the one just touched.
I invite you to try this: Make a dummy component and create a few parameters A1, B1,C1... Then select all of them, copy and then paste multiple times, lets say 5 times. Then try to rename the ones in the bottom of the list to make An instead of A1_n...
Lets say the bottom one is D1_5. Rename it to D6 and touch the previous row name to proceed with it. Too bad, the list is gone to the top!
Show LessHi,
it seems that disabling a component in the schematic doesn't disable its corresponding outputs. So, PSoC Creator will throw an error regarding multiple drivers if you connect the related signals to other outputs and therefore, the project can't be build.
I wonder if this is intended behaviour. For a electronic circuit layout software, you can give no error markers, for example. Or you can state that only one of those devices will be fitted.
Now, I don't know if this should be also the case from a hardware design language point of view. Therefore I want to ask you what you think about having the outputs really disabled for disabled components. Depending on you opinion we can file a support case to change this behavior.
I know that I can work with virtual (de-)muxers, however, if you want to try something out (and this maybe quick-n-dirty), you don't want to additionally use those muxers in the schematic. That's why I think that disabled components should also disable the outputs.
Regards,
Ralf
Show Less
I want configure Cypress MBR3116 by using Renesas R8C tiny (R8C25276) controller I2C. I have designed code according to the I2C host protocol in Cypress MBR3xxx datasheet.
The issue is MBR3116 is sometimes getting configured and sometimes it is not .I need to make multiple attempts to configure it and reset the MBR device manually. I have checked delay & i2c routine & also i referred cypress mbr3116 troubleshoot guide but didn't got any solution. I have attached HEW workspace and text files of this project.Please check it and tell me if there is any correction and what is a solution for this issue.
Where can I find a source code example of HID report processing for the host ?
I looked at AN57294 USB 101: An Introduction to Universal Serial Bus 2.0 but it mentions the install
of Cypress CyUSB.sys driver which is not what I have installed. I have a CY8ckit-059 PSOC 5LP
which uses KitProg(1.2.3.3) windows driver.
Show LessHi,
I recently installed PSoC Creator 4.1 and see errors on startup:
An important piece of PSoC Creator has a problem and may not work correctly. Please restart PSoC Creator.
This error shows up when the following are being initialized:
CyDesigner.Common.Db.DeviceDb.Catalog.CyDcPlugin
CyDesigner.Common.ProjMgmt.CyPrjMgr
CyDesigner.Common.Db.CyS3Db.CyS3DbFactory
CyDesigner.Device.FitterPSoC.CyFitterPSoCPlugin
CyDesigner.Device.FitterFM.CyFitterFmPlugin
Additionally, when closing PSoC Creator, I get this error (and others which are similar):
This product had trouble launching on your computer. Technical error reason: An exception was thrown when trying to fully close plugin 'FM Fitter:a7614a5f-f176-4ec2-b000-98356a8f3dc8'. Exception Message: Object reference not set to an instance of an object..
I've tried to do a fresh reinstall several times, as well as uninstalling other PSoC packages. I had a version of PSoC Creator in the 3.X series working earlier in the week without these issues, so I'm not sure how to fix this. Does anyone have any suggestions?
I'm using macOS 10.12.6 (Sierra) with Parallels 13 and Windows 10.
Thanks!
Joey
Show LessHi,
I have built an ELF file using the startup code generated by the PSoC Creator Project, Using a custom Makefile. I have never been able to flash this ELF file via the PSoC Creator, since i cannot select the files in IDE.
Question 1. Is there a way this can be done via PSoC Creator?
I have tried seeing through build steps for generating the ELF file for this cypress part, The PSoC Creator uses this file CyComponentLibrary.a. Is it generated from the Source code generated by the PSoC Creator.?
Question 2. What does CyComponentLibrary.a file do? Do i always need it? Be it debugging or general BSP kinda thing?
Regards,
Vikram
Show LessI just updated Creator 4.1.
The device on my CY8CKIT-042 Pioneer kit will not program. The target shows as "CMSIS-DAP/248683 -->PSoC4200 CY8C4245AX*-483", protocol = SWD. Prior to the update the target was the KitProg. When I go to the device manager, the KitProg does not appear in the COM port section.
Very disconcerting. This was working perfectly yesterday before I updated Creator 4.1 and now it's not working at all.
I have just now uninstalled update 1 and re-installed Creator 4.1.0.2686. The KitProg is still not showing up.
Any suggestions?
Show Less