PSoC™ Creator & Designer Forum Discussions
Hello,
In the code sample CE222867, TuneMagSense() function handles component bug fixes.
What is the purpose of this process?
If I want to use my own coil pattern, what code should I modify?
Regards,
Shimamrua
Show LessHello,
At first when i Build and debug the project file it was perfect. But now when i build or debug any project i am getting this error.
Build error: Hex file generation step failed, see output window for more information.
what would be the possible reason?
Show LessHello
I am using a PT500 Temperature detector.with a CY8C4125AZI-M433.
I, Psoc Creator, I see Resistance Temperature Detector Calculator (RTD), but I can't see it for PT500 Temperature detector. Is Resistance Temperature Detector Calculator (RTD) only for NTC sensors?
If someone can help me,
Thanks
Regards
Henry
Show LessI'm using a PSoC 4 device (CYBLE-212006) in combination with PSoC Creator 4.2. I have to store some data in flash. The read / write operation works but everytime when I debug the device, all stored data are overwritten. So how to exclude / protect some specific flash regions from override while programming the device?
In my example I use the last 2 flash rows (1022-1023) to store customer data.
Kind regards
Pascal
Show LessWe paid for the professional compiler CA51-LC-ND and I put the path
C:\Keil_v5\C51\BIN
in PSoC Creator 4.2's Options → Project Management → 8051 Toolchains
I set the Build Settings to DP8051 Keil Generic.
When I try to build a project I get the error message
*** ERROR L257: UNKNOWN
The command 'LX51.exe' failed with exit code '3'.
What does that mean?
Show LessSo, lets say you have a version that works and don't want to lose it. You now want to try something different, say changing/adding pins, modifying configurations of components, modifying the code, etc. There is a "save as" button in the creator, but it seems to be only for the code (??) What does "add new project" do ? I seem to have lost too many things trying to save the original.
Also: is there a way to print the pin assignments done in the cydwr section ?
Thanks. . . a newbee. . . Bob
Show LessI have installed PSoC Creator 4.2 on my 64 bit Windows 10 computer on which I have Java 1.8.0_202 64 bit installed
I want to use the Eclipse IDE with it.
According to the PSoC Creator Help at 'Integrating into 3rd Party IDEs' > 'PSoC 4 and PSoC 5 Designs' > 'Using PSoC 4/PSoc 5 Designs with 3rd Party IDEs' > 'PSoc 4/ PSoC 5 Eclipse Information' > Eclipse Installation Configuration' I am instructed to download the Eclipse software from http://www.eclipse.org/cdt. taking care to download the appropriate version (32/64 bit). I therefore downloaded and installed the 64 bit version
I am also told that I need to install the GCC ARM compiler from GNU Arm Embedded Toolchain in Launchpad following the link to GNU Toolchain | GNU Arm Embedded Toolchain – Arm Developer
Dispite listing a number of download options (Windows/Mac/Linux etc) the only options for Windows are for 32 bit windows - none for 64 bit. Having no othe option I downloaded the 32 bit version for Windows 7 and Above.
I have tried to create a project following the instructions in your help documentation. However, when I click Finish' I get an error message 'Project cannot be created. Reason: Internal Error - java.lang.nullpointerException.
Could you please help!
Should I have downloaded the 64 bit version of the GCC ARM Compiler? If so where can I download it from?
Can you suggest any other reason why I should be getting this error and not able to create a project?
Show LessI am trying to find the flow chart for the findme program by analyzing the source code files.
I was wondering what does "__enable_irq() " do in the source code main_cm4.c file?
Here, I don't see any declaration for interrupts
/*******************************************************************************
* File Name: main_cm4.c
*
* Version 1.10
*
* Description:
* This is the source code CM4 core for the BLE project (for dual cores MPN).
*
* Hardware Dependency:
* CY8CKIT-062 PSoC6 BLE Pioneer Kit
* CY8CPROTO-063-BLE PSoC 6 BLE Prototyping Kit
*
******************************************************************************
* Copyright (2018), Cypress Semiconductor Corporation.
******************************************************************************
* This software is owned by Cypress Semiconductor Corporation (Cypress) and is
* protected by and subject to worldwide patent protection (United States and
* foreign), United States copyright laws and international treaty provisions.
* Cypress hereby grants to licensee a personal, non-exclusive, non-transferable
* license to copy, use, modify, create derivative works of, and compile the
* Cypress Source Code and derivative works for the sole purpose of creating
* custom software in support of licensee product to be used only in conjunction
* with a Cypress integrated circuit as specified in the applicable agreement.
* Any reproduction, modification, translation, compilation, or representation of
* this software except as specified above is prohibited without the express
* written permission of Cypress.
*
* Disclaimer: CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH
* REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
* Cypress reserves the right to make changes without further notice to the
* materials described herein. Cypress does not assume any liability arising out
* of the application or use of any product or circuit described herein. Cypress
* does not authorize its products for use as critical components in life-support
* systems where a malfunction or failure may reasonably be expected to result in
* significant injury to the user. The inclusion of Cypress' product in a life-
* support systems application implies that the manufacturer assumes all risk of
* such use and in doing so indemnifies Cypress against all charges. Use may be
* limited by and subject to the applicable Cypress software license agreement.
*****************************************************************************/
#include "common.h"
/*******************************************************************************
* Function Name: main()
********************************************************************************
*
* Summary:
* Main function for the project.
*
*******************************************************************************/
int main()
{
/* Unfreeze IO after Hibernate */
if(Cy_SysPm_IoIsFrozen())
{
Cy_SysPm_IoUnfreeze();
}
/* Enable global interrupts */
__enable_irq();
#if(CY_BLE_CONFIG_HOST_CORE == CY_BLE_CORE_CORTEX_M4)
/* Run Host main */
HostMain();
#else
for(;;)
{
/* To achieve low power */
Cy_SysPm_DeepSleep(CY_SYSPM_WAIT_FOR_INTERRUPT);
}
#endif /* (CY_BLE_CONFIG_HOST_CORE == CY_BLE_CORE_CORTEX_M4) */
}
/* [] END OF FILE */
Show LessBasically, I have a sensor system that has various I2C sensors that can be plugged into it. I won't know at main firmware development time which I2C sensors will be plugged in, so I can't provide the code to read them at firmware development time. I would like to generate the "driver" code for the I2C sensor after the fact and load it into flash via my normal communications channel at a later time (be able to load different "driver") code at different times. The driver routine will be passed pointers to the needed functions and variables in the main firmware, so no fixup needed for that. I assume that locating this driver code in a standard address in flash will allow the main code to call it. How would one go about compiling/linking/locating this driver code so that it can be coppied directly into flash at a later time?
Show Less