PSoC™ Creator & Designer Forum Discussions
Just a thought Cypress, but that label in config tool is very misleading,
especially in light of the fact you graphically show it as not being R-R.
Show Less
A feature to add to Creator. A menu item that will download
all datasheets for a specific family, eg. CY8C38**, and ability
to detect older datasheet and download latest version, and
placing old rev datasheet in a tool archive folder.
Regards, Dana.
Show LessQuestion: - I have installed eclipse plugin available at link http://www.cypress.com/psoccreator/ to configure PSoC Creator compiler in my Eclipse (Juno, Kepler) version. I am able to install the Eclipse plugin properly, and there is no error message while installing. But plugin is not working. What to do?
Answer:-
Eclipse plugin available in link sepcified above only works with JRE7. If you have JRE6 installed in your machine then use the plugin attached with this post. This should work properly.
-Rave
Show LessThis problem can occur while installing PSoC Creator, PSoC Designer or PSoC Programmer. When CyInstaller rollback without showing any error message, follow these steps to find the root cause:-
1) First of all, go to “Event Viewer” in Windows
a. Go to “Control Panel”
b. Select “Administrative Tools”
c. Open “Event Viewer”
2) On the right pane, click on Windows, and select Application
3) Search for the Information about CyInstaller and check the reason for abrupt rollback of Installer available in Details tab.
4) If error is because of unavailability of some font like Arial, than copy the Arial font or that particular font from internet in your Windows Control panel in Font section.
5) Now start the installation again.
Show LessRecently a group of Cypress Employees started to flood the forums with unasked-for contributions. This WILL make user-questions difficult to detect and follow-up because they are vanishing in the huge amount of these CDC-entries.
I do not question the correctness and value of the contents supplied, but in my opinion of what a community / forum is, they are completely mis-placed.
As a matter of fact I do not see a place of discussing, improving and exchanging experiences in the CDC any more and so I will not post (or even read) contributions here.
Thank you, folks! It has been a splended time watching our knowledge about PSoCs to grow and prosper!!!
Season greetings
Bob
Hello,
Many times we face issues in programming. Some issues can be solved on our own. So if you are unable to program the chip, then ensure the following,
1. Proprer device is selected in the device selector window. Creator->Project->Device Selector.
2. The power supply jumpers in the board are present.
3. After powering the board, check the voltage at Vcc pins. This is regulated voltage and it should be ideally 1.8V. If it is not, then it could be some power supply issues.
4. Capacitors on the supply pins has to be as close as possible to the supply pins. The capacitor values recommended can be found in thr device Architecture TRM-> Power Supply and Monitoring section.
5. If the power supply is from MiniProg, then VDDD and VDDA lines has to be connected to VTARG of MiniProg. In PSoC 3/5LP development board, this short is not present. Hence either external power supply is required or VDDD and VDDA lines has to be shorted.
6. In the Device manager, you can check if the device is getting recognised or not. If it getting recognised as a unknown device, then there are issues with the drivers.
7. If you are using MiniProg3 then to choose the appropriate programmming settings, go to Creator->Tools->Program/Debug->Port Configuration->MiniProg3 and choose the appropriate settings.
If you are supplying power using external power supply, then Power Supply mode of programming cannot be done because MiniProg cannot control the power. Only reset mode of programming has to be done.
If anyone has more to add, kindly add to the post.
Keerthi
Show LessHello Everyone
I am stumbling on a Building project.
I am using my component, however there are these API routines in the project but
UNDEFINED REFERENCE ERROR had occure.
API routines have prefix of instance name of module.
Until now, this project was build successfully but
I had make some changes, after then the problem has become happening.
Device is PSoC5LP, Creator 2.2sp1
Someone have any suggestion, please let me know.
--------------- Build Started: 09/22/2013 13:09:46 Project: P5LP_BL, Configuration: ARM GCC 4.4.1 Debug ---------------
The code generation step is up to date.
arm-none-eabi-gcc.exe -I. -Wno-main -I./Generated_Source/PSoC5 -mcpu=cortex-m3 -mthumb -Wall
-g -D DEBUG -Wa,-alh=.\CortexM3\ARM_GCC_441\Debug\main.lst -O2 -ffunction-sections -c .\main.c -o .\CortexM3\ARM_GCC_441\Debug\main.o
arm-none-eabi-ar.exe -rs .\CortexM3\ARM_GCC_441\Debug\P5LP_BL.a .\CortexM3\ARM_GCC_441\Debug\LED1.o .\CortexM3\ARM_GCC_441\Debug\LED2.o
.\CortexM3\ARM_GCC_441\Debug\LED4.o .\CortexM3\ARM_GCC_441\Debug\LED8.o .\CortexM3\ARM_GCC_441\Debug\GND1.o
.\CortexM3\ARM_GCC_441\Debug\GND2.o .\CortexM3\ARM_GCC_441\Debug\GND4.o .\CortexM3\ARM_GCC_441\Debug\GND8.o
.\CortexM3\ARM_GCC_441\Debug\Bootloadable.o .\CortexM3\ARM_GCC_441\Debug\core_cm3.o .\CortexM3\ARM_GCC_441\Debug\CyBootAsmGnu.o
.\CortexM3\ARM_GCC_441\Debug\CyDmac.o .\CortexM3\ARM_GCC_441\Debug\CyFlash.o .\CortexM3\ARM_GCC_441\Debug\CyLib.o .\CortexM3\ARM_GCC_441\Debug\cyPm.o
.\CortexM3\ARM_GCC_441\Debug\CySpc.o .\CortexM3\ARM_GCC_441\Debug\cyutils.o .\CortexM3\ARM_GCC_441\Debug\ControlReg.o
.\CortexM3\ARM_GCC_441\Debug\DDS_DDS.o .\CortexM3\ARM_GCC_441\Debug\PinSignal.o .\CortexM3\ARM_GCC_441\Debug\DDS_StatusPhase.o
.\CortexM3\ARM_GCC_441\Debug\DDsClock.o .\CortexM3\ARM_GCC_441\Debug\DDS_iDAC.o .\CortexM3\ARM_GCC_441\Debug\DDS_iDAC_PM.o
.\CortexM3\ARM_GCC_441\Debug\DDS_ControlPhase4.o .\CortexM3\ARM_GCC_441\Debug\DDS_ControlPhase3.o .\CortexM3\ARM_GCC_441\Debug\DDS_ControlPhase2.o
.\CortexM3\ARM_GCC_441\Debug\DDS_ControlPhase1.o .\CortexM3\ARM_GCC_441\Debug\DDS_ControlStrobe.o .\CortexM3\ARM_GCC_441\Debug\cyfitter_cfg.o
arm-none-eabi-ar.exe: creating .\CortexM3\ARM_GCC_441\Debug\P5LP_BL.a
arm-none-eabi-gcc.exe -mthumb -march=armv7-m -mfix-cortex-m3-ldrd -T .\Generated_Source\PSoC5\cm3gcc.ld -Wl,-Map,
.\CortexM3\ARM_GCC_441\Debug\P5LP_BL.map -Wl,--start-group -o .\CortexM3\ARM_GCC_441\Debug\P5LP_BL.elf .\CortexM3\ARM_GCC_441\Debug\main.o .\CortexM3\ARM_GCC_441\Debug\Cm3Start.o
.\CortexM3\ARM_GCC_441\Debug\P5LP_BL.a "D:\Program Files\CyPRESS\PSoC Creator\2.2\PSoC Creator\psoc\content\cycomponentlibrary\CyComponentLibrary.cylib\CortexM3\ARM_GCC_441\Debug\CyComponentLibrary.a" -Wl,--end-group
.\CortexM3\ARM_GCC_441\Debug\P5LP_BL.a(DDS_DDS.o): In function `DDS_SetFrequency':
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:26: undefined reference to `DDS_ControlStrobe_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:30: undefined reference to `DDS_ControlPhase1_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:31: undefined reference to `DDS_ControlPhase2_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:32: undefined reference to `DDS_ControlPhase3_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:33: undefined reference to `DDS_ControlPhase4_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:35: undefined reference to `DDS_ControlStrobe_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:37: undefined reference to `DDS_ControlStrobe_Write'
.\CortexM3\ARM_GCC_441\Debug\P5LP_BL.a(DDS_DDS.o): In function `DDS_Start':
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:9: undefined reference to `DDS_ControlStrobe_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:10: undefined reference to `DDS_ControlPhase1_Write'
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:11: undefined reference to `DDS_ControlPhase2_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:12: undefined reference to `DDS_ControlPhase3_Write'
H:\Desktop\@PSoC3\@P4\P5LP_BL\P5LP_BL.cydsn/.\Generated_Source\PSoC5/DDS_DDS.c:13: undefined reference to `DDS_ControlPhase4_Write'
collect2: ld returned 1 exit status
--------------- Build Failed: 09/22/2013 13:09:54 ---------------
// sorry for long listing ///
Show Less
These steps are applicable on ARM GCC compiler. Use the following steps to use C99 coding standards with PSoC 5LP parts in Creator: -
1. Open the project in Creator in which you want to use C99 coding standards.
2. Right click on the name of project.
3. Select Build Settings.
4. Expand the Compiler node in the settings tree.
5. Select the Command Line node.
6. In the Custom Command Line property add "-std=gnu99".
Attaching the screenshot showing the steps.
After this Creator will use C99 coding standard for that partcular project.
-Rave
Show Less