PSoC™ Creator & Designer Forum Discussions
I have a CY8CKIT-005 kit which has a MiniProg4. I also have a C++ code that manages devices by spi and i2c and gpio. Can I implement control using MiniProg4? It is necessary that all these interfaces work simultaneously.
I also want to know if there are drivers for MiniProg4 to run it using the code in Visual Studio?
Hi,
I am having the following issue when I try to load a project workspace. Does anyone know how to resolve this?
Since the workspace it too large to zip and upload here. I uploaded it to Drive and the link is below.
https://drive.google.com/file/d/1mOJ_REM-ZL-TuTqfYy61nwrBiJB2HRkT/view?usp=share_link
Show Less
Dear Sirs and Madams,
I found a problem with the ECO settings in PSoC Creator 4.4.
IDE : "PSoC Creator 4.4 (4.4.0.80)" and "boot component V6.10"
1. Create a new "PSoC4S Plus" empty project.
2. Set the ECO from the clock tab as follows :
/**********************************************/
Desired ferq (MHz) 24
Driver level (uW) 200
Equivalent series resistance (ohm) 60
Parallel load capacitance (pF) 10
Accuracy +/- 20 ppm
/**********************************************/
3. Build this project.
4. Confirm for the "cyfitter_cfg.c" file.
/* CYREG_EXCO_ECO_TRIM0 */
0x0000001F => ATRIM 0x07, WDTRIM 0x03 (111 11b = 0x1F)
/* CYREG_EXCO_ECO_TRIM1 */
0x0000001A => GTRIM 0x01, RTRIM 0x10, FTRIM 0x10 (01 10 10b = 0x1A)
This GTRIM value is wrong.
From the formula above :
Vpp = 1.71V
So ATRIM 0x07 and WDTRIM 0x03 are correct.
gm = 2.73 mA/V
However, the GTRIM value is set to 0x01 when it should be 0x00.
5. Change the ECO setting from 10pF to 15pF and check the same.
Confirm for the "cyfitter_cfg.c" file after build.
Vpp and gm calculated from the formula are below :
Vpp = 1.14V
Set ATRIM 0x05, WDTRIM 0x03 is correct. (101 11b = 0x17)
gm = 6.14 mA/V
Set GTRIM 0x00 is incorrect. (00 10 10b = 0x0A)
The correct GTRIM calculated from the formula must be 0x01.
I think the GTIRM calculation formula of PSoC Creator 4.4 is wrong and this is a critical issue.
Could you please confirm this issue?
Regards,
Show LessEver wish you could use one of the standard 2x16 character displays across multiple ports or not have to use sequential pins? Well now you can spread the connections to your character LCD across multiple ports in any order. This new component is 100% compatible with the original Character LCD, except you can connect it any way you want. One other little feature is that you only need 6 GPIOs instead of 7. So check out the CharLCDmp. You can also use it with the standard port 2 connector, but make sure you drive the R/W pin to Vss.
The attachment contains a workspace with a demo project and a library with both the CharLCDmp component and a LCD annotation component to help you remember how to connect the two together.
Enjoy,
Mark
Show LessHello All
Referring to a similar post titled "Build process unable to delete contents of code gen dir. Error: Failed to delete...lcpsoc3" i can confirm that this appears to be a glitch on Windows 10 (10.0.16299 b16299) - unsure if the originator of the previous thread was also on a Win10 domain environment where group policy may be coming into play???
Occasionally the lcpsoc3 directory located inside codegentemp becomes inaccessible and can not be deleted - a restart of Win10 is required after which the folder is no longer present in codegentemp. This issue does not appear related to permissions as a permission change cannot be applied to the codegentemp folder - see images further down this post. Attempting to copy the entire project folder is also met an error in Win10.
The same PSoC Creator 4.1 project was previously rebuilt several times. The only change made in creator was to change clocks, example of the Output window below.
Has anyone encountered this oddity, any ideas on addressing?
Kind regards
Greg
Flash used: 11144 of 262144 bytes (4.3%).
SRAM used: 2873 of 65536 bytes (4.4%). Stack: 2048 bytes. Heap: 128 bytes.
--------------- Build Succeeded: 01/10/2018 09:10:46 ---------------
--------------- Build Started: 01/10/2018 09:23:15 Project: MB-01_Bootloadable, Configuration: ARM GCC 5.4-2016-q2-update Debug ---------------
cydsfit.exe -.appdatapath "C:\Users\greg\AppData\Local\Cypress Semiconductor\PSoC Creator\4.1" -.fdsnotice -.fdswarpdepfile=warp_dependencies.txt -.fdselabdepfile=elab_dependencies.txt -.fdsbldfile=generated_files.txt -.fdsreffile=referenced_files.txt -p "C:\Users\greg\Desktop\Motorised Bracket\PSoC\MB-01_Bootloadable.cydsn\MB-01_Bootloadable.cyprj" -d CY8C5888LTI-LP097 -s "C:\Users\greg\Desktop\Motorised Bracket\PSoC\MB-01_Bootloadable.cydsn\Generated_Source\PSoC5" -- -yv2 -q10 -ygs -o2 -v3 -.fftcfgtype=LE
Elaborating Design...
ADD: fit.M0032: warning: Clock Warning: (UART_IntClock's accuracy range '1.846 MHz +/- 5%, (1.754 MHz - 1.938 MHz)' is not within the specified tolerance range '1.843 MHz +/- 4.595%, (1.759 MHz - 1.928 MHz)'.).
* C:\Program Files (x86)\Cypress\PSoC Creator\4.1\PSoC Creator\psoc\content\CyComponentLibrary\CyComponentLibrary.cylib\UART_v2_50\UART_v2_50.cysch (Instance:IntClock)
* C:\Users\greg\Desktop\Motorised Bracket\PSoC\MB-01_Bootloadable.cydsn\MB-01_Bootloadable.cydwr (UART_IntClock)
ADD: fit.M0032: warning: Clock Warning: (RS485_IntClock's accuracy range '15 MHz +/- 5%, (14.25 MHz - 15.75 MHz)' is not within the specified tolerance range '14.746 MHz +/- 4.595%, (14.068 MHz - 15.423 MHz)'.).
* C:\Program Files (x86)\Cypress\PSoC Creator\4.1\PSoC Creator\psoc\content\CyComponentLibrary\CyComponentLibrary.cylib\UART_v2_50\UART_v2_50.cysch (Instance:IntClock)
* C:\Users\greg\Desktop\Motorised Bracket\PSoC\MB-01_Bootloadable.cydsn\MB-01_Bootloadable.cydwr (RS485_IntClock)
HDL Generation...
Synthesis...
Dependency Generation...
Cleanup...
Error: fit.M0050: The fitter aborted due to errors, please address all errors and rebuild. (App=cydsfit)
--------------- Build Failed: 01/10/2018 09:23:19 ---------------
--------------- Rebuild Started: 01/10/2018 09:23:30 Project: MB-01_Bootloadable, Configuration: ARM GCC 5.4-2016-q2-update Debug ---------------
Deleting file ".\CortexM3\ARM_GCC_541\Debug\main.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\powerstep_commands.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\cyfitter_cfg.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\cymetadata.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\CyScBoostClk.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM_INT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\UART.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\UART_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\UART_INT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\UART_BOOT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Clock_1.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\UART_IntClock.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Cm3Start.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\CyBootAsmGnu.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\CyDmac.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\CyFlash.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\CyLib.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\cyPm.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\CySpc.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\cyutils.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Up_Switch.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Down_Switch.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\RS485.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\RS485_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\RS485_INT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\RS485_BOOT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\RS485_IntClock.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\isr_RS485.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Test_Pin.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Status_Reg.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\timer_clock.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Timer_1.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Timer_1_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\timer_clock_1.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\EZI2C.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\EZI2C_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\EZI2C_INT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Timer_2.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Timer_2_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM_PV.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM_PV_PM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM_PV_INT.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\SPIM_PV_IntClock.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\isr_SysTmr.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Home_Switch.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_MISO.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_Reset.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_MOSI.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_SCK.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_SS.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\POS_DO.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\POS_PRE.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\POC_CLK.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\POS_ERR.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_LimSw.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Rx_1.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MOT_Busy.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\LED_Status.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Pin_2.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\Config.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\EEPROM.o"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MB-01_Bootloadable.hex"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MB-01_Bootloadable.elf"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\MB-01_Bootloadable.map"
Deleting file ".\MB-01_Bootloadable.rpt"
Deleting file ".\MB-01_Bootloadable_timing.html"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\.deps\SOURCE_C__ARM_GCC_GENERIC.P"
Deleting file ".\CortexM3\ARM_GCC_541\Debug\.deps\SOURCE_ASM__ARM_GCC_GENERIC.P"
Build process unable to delete contents of code gen dir. Error: Failed to delete C:\Users\greg\Desktop\Motorised Bracket\PSoC\MB-01_Bootloadable.cydsn\codegentemp\lcpsoc3: Access to the path 'C:\Users\greg\Desktop\Motorised Bracket\PSoC\MB-01_Bootloadable.cydsn\codegentemp\lcpsoc3' is denied.
--------------- Rebuild Failed: 01/10/2018 09:23:30 ---------------
Properties of the lcpsoc3 directory - shows read only
Unchecking read only and clicking apply results in the following message
Show Less
I added some LED off/on/off/on code and when I clicked Build, I get the following error message:
Build process unable to delete contents of code gen dir. Error: Failed to delete...lcpsoc3: Access to the path...lcpsoc3' is denied
I believe that I can delete it after a boot from shut down, but is there a way to delete this to allow build to proceed now rather than later?
Show LessBuild currently defines CY8C5888FNI-LP210 based on what we use\need we should also be able to use CY8C5888FNI-LP214. Tried a beta build with the only change being the LP214. The build compiled without error. It failed to flash to an LP210 hardware due to the device ID check.
Can you define two devices under the same build in Creator? We'd like to use one firmware build and seamlessly be able to flash to a LP210 or an LP214.
Show LessI've been working on a shared library of code for PSoC1/3/5 and needed to be able to reference
a shared respository of source code and include files that are located outside my project directory.
Solution description :
You have library of shared source code that you would like to re-use in several PSoC3/5 projects.
From the "Project -> Build Files -> Compiler" menu,
add your search path to the "Additional Include Directories" entry.
Use a semi-colon separated list for multiple directories..
See the attached screenshot example.
regards,
Tom Moxon
Show LessI tried to replace all the UAC1 descriptors with UAC2 descriptors, but Windows says "This device cannot start. (Code 10)" and tdd.exe says *** ERROR: Descriptor has errors! ***
For example:
Endpoint Descriptor:
------------------------------
0x09 bLength
0x05 bDescriptorType
*** ERROR: Invalid descriptor length 0x09
Hex dump:
0x09 0x05 0x86 0x03 0x02 0x00 0x1E 0x00 0x00
It looks like this was length 9 in UAC1 (Table 4-17: Standard AC Interrupt Endpoint Descriptor) but is now supposed to be length 7 (Table 4-25: Standard AC Interrupt Endpoint Descriptor). The bRefresh and bSynchAddress fields have been removed. But USBFS component does not have "Endpoint Descriptor 2.0", it just has "Endpoint Descriptor" with bRefresh and bSynchAddress fields that cannot be turned off?
It has similar errors for other interfaces and endpoints:
AS Interface Descriptor:
------------------------------
0x07 bLength
0x24 bDescriptorType
0x01 bDescriptorSubtype
*** ERROR: Invalid descriptor size 0x07
Hex dump:
0x07 0x24 0x01 0x01 0x01 0x01 0x00
Endpoint Descriptor:
------------------------------
0x09 bLength
0x05 bDescriptorType
*** ERROR: Invalid descriptor length 0x09
Hex dump:
0x09 0x05 0x01 0x05 0x86 0x01 0x01 0x00 0x88
AS Isochronous Data Endpoint Descriptor:
------------------------------
0x07 bLength
0x25 bDescriptorType
0x01 bDescriptorSubtype
*** ERROR: Invalid descriptor size 0x07
Hex dump:
0x07 0x25 0x01 0x01 0x00 0x00 0x00
Endpoint Descriptor:
------------------------------
0x09 bLength
0x05 bDescriptorType
*** ERROR: Invalid descriptor length 0x09
Hex dump:
0x09 0x05 0x88 0x11 0x03 0x00 0x04 0x03 0x00
Show Less
Hello, I'm adding my design project to Git and need some suggestion on what file type I should ignore. Can anyone suggestion what file types I should ignore for GIT?
Thank you
Show Less