PSoC™ Creator & Designer Forum Discussions
I'm attempting to update the cy_boot component from 5.4 to 5.81 in PSoC Creator 4.2. The machine I'm working with cannot be connected to the internet. Is there a way to update the cy_boot component without internet connectivity?
I have tried using a separate computer that is connected to internet and downloading the cy_boot update. I then copied the contents in Documents\PSoC Creator\4.2\Downloads ( 4.2).cylib to the matching directory in the offline machine. However, I still do not see the option for cy_boot 5.81 when attempting to update the component in my project.
Show LessHi, i'm using a miniProg4 and PSOC programmer version: 3.28.7.4504
The target device is: CYBLE-222005-00
The option to select either the 5pin or 10 pin connector is not available - it is greyed out.
For me this is OK but my colleague has the same setup and his is stuck in the 10pin.
We've tried different settings but cannot seem to enable this option.
Any advice on how we can enable this option would be appreciated.
Kind regards,
Damian
Show Less
In PSoCCreator, (4.1)
after an internet access problem (security access problem)
the lot of examples are not visible (all the examples with the web link to download disapeared)
reinstall, desinstall, reinstall ...
always the same problems : just 10 examples in the list
TR
Show LessI decided to develop in the PSoC creator environment and wanted to install it. But the download link does not open, although I am logged in to the site. Do I need to buy a subscription to PSoC creator?
Show LessI am trying to use a Timer v2.70 component in on a PSoC4L (CY8C4248LTI-L485) and it does not seem to consistently respond to the Capture wire. Has anyone else experienced this?
Show LessThis post describes how to add the ability to change the interrupt priority mask level within the PSOC5 family using the functionality of the basepri register and normally provided by the CMSIS function __set_BASEPRI(priority) even though the PSOC software library does not define this function.
I suggest that Cypress/Infineon software team members update the PSOC Creator system and libraries to make these functions available on the ARM M3 core products. I am sharing my work-around for others in the meantime.
Background:
In a project that I have been developing using the CY8C5888LTI (PSOC-5), I had the need to selectively raise the interrupt mask level to protect linked list structures which are manipulated both within interrupt service routines and non-interrupt code. I could not use the typical CyEnterCriticalSection() / CyExitCriticalSection() functions which mask ALL interrupts due to the fact that I am using the SPI interface with software buffers. The SPI API for the software buffers utilizes DMA and it is necessary to permit these interrupts to continue to function while blocking lower urgency (higher interrupt priority number) interrupts.
Unfortunately, the PSOC API's do not include the standard CMSIS functions __get_BASEPRI() and __set_BASEPRI(priority). While these function can be found within the PSOC generated source file cmsis_gcc.h, they are wrapped within a #ifdef that only makes the functions visible for 7M and 8M ARM architecture chips. Yet the ARM M3 core upon which PSOC5 is based does include the basepri register and these functions do work.
Details:
An excellent treatise on ARM interrupt priorities can be found here: Cutting Through the Confusion with ARM Cortex-M Interrupt Priorities « State Space
Solution:
Rather than simply copying the unavailable inline function definitions for __get_BASEPRI() / __set_BASEPRI() from within cmsis_gcc.h and placing them within a new header.h file, I chose to implement more human readable functions getInterruptMask() and setInterruptMask(level). These functions return and set (respectively) the integer interrupt level, whereas the CMSIS functions return and pass a value that is the actual interrupt level shifted into the most significant 3 (or 4) bits of the basepri register.
The attached file intmask.h defines these always inline functions for use in projects that need this capability. Note that it is left to the user to appropriately manage the interrupt priority levels used by the various hardware elements of their project!
Regards, Doug Bartlett
Show LessUsing ISSP program, the checksum test passed. If using MiniProg3 program, it would say "erased successful, programmed successful, verified successful, checksum failed".
Question: Does MiniProg3 use a different algorithm than ISSP's to generate checksum value?
Thanks
Show Less