45964 Discussions
22811 Members
26557 Solved
Hi
I found a strange problem. The ifclk pin of cy7c68013A has output working with the driver of CY3684 EZ-USB FX2LP Developmeng kit(the chip VID is 04B4 PID is 8614, same as in inf file), while ifclk pin has no output when I install the driver of cyusb3.sys(the VID and PID is modified as 04B4 8614 in cyusb3.inf).
Is appears that the iclk pin has output when the chip is powered on(VID 04B4 PID 8614), and no installing cyusb3.sys, if the driver of cyusb3.sys is installed, the output will be disappeared after a few seconds. Is there any limition in cyusb3.sys? How to fix it?
Show Less
Hi All,
Merry Christmas and happy holidays. My professional development project has hit a block.
Purchased a CY8CKIT-064S0S2-4343W kit and am working with ModusToolbox v2.2.0.
I have hit an issue when trying to provision the device. I get the following error when I try to do the provisioning as spelt out in the the Provisioning Guide documentation.
Everything seems to be ok but it fails with this error message
"
2020-12-29 14:24:59,073 : C : ERROR : Early Production Units detected, please get earlier version of tools by running 'pip install --upgrade --force-reinstall cysecuretools==2.1.0'. Check the log for details
Error: Failed processing! "
This error is also returned if I try and run the entrance-exam command.
Based on the responses, I am sure that the hardware is communicating with my pc. I can't actually run the earlier version of cysecuretools as when I try that, I get a stack of python errors about being unable to build the wheel for cryptography which use PEP 517 and cannot be installed directly.
So I would like to get things working with all the current versions of ModusToolbox etc. Please help, it seems to be a pretty pathetic way to be failing as I am just trying to get the demo code to work at this stage 😞
Here is the response to entrance-exam.
"
I:\Foundry\Project\S1000072_AWS\FreeRTOS\vendors\cypress\MTB\psoc6\psoc64tfm\security>cysecuretools -t cy8ckit-064s0s2-4343w entrance-exam
2020-12-29 14:24:58,260 : C : INFO : Target: cy8ckit-064s0s2-4343w
2020-12-29 14:24:58,292 : P : INFO : Target type is cy8c64xa_cm4_full_flash
2020-12-29 14:24:58,306 : P : INFO : DP IDR = 0x6ba02477 (v2 rev6)
2020-12-29 14:24:58,308 : P : INFO : AHB-AP#0 IDR = 0x84770001 (AHB-AP var0 rev8)
2020-12-29 14:24:58,312 : P : INFO : AHB-AP#2 IDR = 0x24770011 (AHB-AP var1 rev2)
2020-12-29 14:24:58,318 : P : INFO : AHB-AP#0 Class 0x1 ROM table #0 @ 0xf1000000 (designer=034 part=102)
2020-12-29 14:24:58,322 : P : INFO : AHB-AP#2 Class 0x1 ROM table #0 @ 0xe00ff000 (designer=034 part=102)
2020-12-29 14:24:58,329 : P : INFO : [0]<e0080000:CTI class="9" designer=43b part=906 devtype=14 archid=0000 devid=40800:0:0>
2020-12-29 14:24:58,331 : P : INFO : [3]<e008e000:TPIU-M3 class="9" designer=43b part=923 devtype=11 archid=0000 devid=ca1:0:0>
2020-12-29 14:24:58,341 : P : INFO : [4]<e007f000:ROM class="1" designer=034 part=102>
2020-12-29 14:24:58,342 : P : INFO : AHB-AP#2 Class 0x1 ROM table #1 @ 0xe007f000 (designer=034 part=102)
2020-12-29 14:24:58,356 : P : INFO : [0]<e000e000:SCS-M4 class="14" designer=43b part=00c>
2020-12-29 14:24:58,358 : P : INFO : [1]<e0001000:DWT class="14" designer=43b part=002>
2020-12-29 14:24:58,369 : P : INFO : [2]<e0002000:FPB class="14" designer=43b part=003>
2020-12-29 14:24:58,371 : P : INFO : [3]<e0000000:ITM class="14" designer=43b part=001>
2020-12-29 14:24:58,380 : P : INFO : [4]<e0042000:CTI class="9" designer=43b part=906 devtype=14 archid=0000 devid=40800:0:0>
2020-12-29 14:24:58,382 : P : INFO : [5]<e0041000:ETM-M4 class="9" designer=43b part=925 devtype=13 archid=0000 devid=0:0:0>
2020-12-29 14:24:58,393 : P : INFO : CPU core #1 is Cortex-M4 r0p1
2020-12-29 14:24:58,396 : P : INFO : FPU present: FPv4-SP
2020-12-29 14:24:58,409 : P : INFO : 4 hardware watchpoints
2020-12-29 14:24:58,410 : P : INFO : 6 hardware breakpoints, 4 literal comparators
2020-12-29 14:24:58,423 : C : INFO : Use system AP
2020-12-29 14:24:58,428 : P : INFO : Clearing TEST_MODE bit...
2020-12-29 14:24:58,434 : C : INFO : Probe ID: 19111301a419041100a4190400000000000000002e127069
2020-12-29 14:24:58,435 : C : INFO : Secure Flash Boot version: 4.0.1.1089
2020-12-29 14:24:58,862 : C : INFO : Device CyBootloader version: unknown
2020-12-29 14:24:58,863 : C : INFO : Package CyBootloader version: 2.0.0.3345
2020-12-29 14:24:59,067 : C : INFO : Chip protection state: Secure
2020-12-29 14:24:59,073 : C : ERROR : Early Production Units detected, please get earlier version of tools by running 'pip install --upgrade --force-reinstall cysecuretools==2.1.0'. Check the log for details
Error: Failed processing!
"
The response when attempting to provision is similar.
"
I:\Foundry\Project\S1000072_AWS\FreeRTOS\vendors\cypress\MTB\psoc6\psoc64tfm\security>cysecuretools --policy ./policy/policy_multi_CM0_CM4_tfm.json --target CY8CKIT-064S0S2-4343W provision-device
2020-12-29 14:22:50,975 : C : INFO : ######################################################################
2020-12-29 14:22:50,975 : C : INFO : Provisioning packet is created
2020-12-29 14:22:50,976 : C : INFO : ######################################################################
..... "
The rest of the provisioning response is the same as for the entrance-exam.
Thanks in advance for any help. Cheers!
Peter
Show LessI have a Windows 10 machine and am logged in as Administrator, and I get to the end of what appears to be the complete installation of the ModusToolbox, pressing finish, but I get an error message: Unable to execute file. ShellExecuteEx failed: code 5, access denied
Show LessHi,
Could you please help me with Schematic and firmware design support to drive Segment LEDs using the PSoC 5LP chip?
We have to drive a seven-digit seven segment display with various segment current from 16-bit serial input.
Regards,
Mari
Show Less
Hi Gents,
This question is in reference to https://www.cypress.com/documentation/application-notes/an60317-psoc-3-and-psoc-5lp-i2c-bootloader
When I try and run the provided API it errors on the Bootloader Version replied back by the PSOC3 we use.
The PSOC3 is replying back with the bytes 60,1,1. Whereas, the API is looking for 0x000000 :
int CyBtldr_StartBootloadOperation_PSoC3(unsigned long expSiId, unsigned char expSiRev, unsigned long* blVer)
{
const unsigned long SUPPORTED_BOOTLOADER = 0x000000;
[...]
}
Why is the API looking for 0x000000 when the PSOC3 bootloader is hardcoded with 60,1,1 ?!
Show Less
Hi,
I worked through the UVC example and got video streaming working. I then worked through the GpifToUsb example and got data read out working. Now I am trying to merge them and continuously read out data from an ADC without dropping data. To do this, I began with the GpifToUsb example and added a simple GPIF project with two threads (0,1):
Next, I added a MANY_TO_ONE auto DMA channel to GpifToUsb:
//try creating a many to one dma channel
CyU3PDmaMultiChannelConfig_t dmaMultiConfig;
CyU3PMemSet ((uint8_t *)&dmaCfg, 0, sizeof (dmaMultiConfig));
dmaMultiConfig.size = CY_FX_DMA_BUF_SIZE;
dmaMultiConfig.count = CY_FX_DMA_BUF_COUNT;
dmaMultiConfig.validSckCount = 2;
dmaMultiConfig.prodSckId [0] = (CyU3PDmaSocketId_t)CY_U3P_PIB_SOCKET_0;
dmaMultiConfig.prodSckId [1] = (CyU3PDmaSocketId_t)CY_U3P_PIB_SOCKET_1;
dmaMultiConfig.consSckId [0] = (CyU3PDmaSocketId_t)(CY_U3P_UIB_SOCKET_CONS_0);
dmaMultiConfig.prodAvailCount = 0;
dmaMultiConfig.prodHeader = 0; /* 12 byte UVC header to be added. */
dmaMultiConfig.prodFooter = 0; /* 4 byte footer to compensate for the 12 byte header. */
dmaMultiConfig.consHeader = 0;
dmaMultiConfig.dmaMode = CY_U3P_DMA_MODE_BYTE;
dmaMultiConfig.cb = NULL;
dmaMultiConfig.notification = 0;
//dmaMultiConfig.notification = CY_U3P_DMA_CB_CONS_SUSP; // CY_U3P_DMA_CB_PROD_EVENT | CY_U3P_DMA_CB_CONS_EVENT;
//dmaMultiConfig.cb = GpifToUsbDmaCallbackMulti;
apiRetStatus = CyU3PDmaMultiChannelCreate (&glDmaChHandleMulti, CY_U3P_DMA_TYPE_AUTO_MANY_TO_ONE,
&dmaMultiConfig);
if (apiRetStatus != CY_U3P_SUCCESS)
{
/* Error handling */
CyU3PDebugPrint (4, "DMA Channel Creation Failed, Error Code = %d\n", apiRetStatus);
CyFxAppErrorHandler (apiRetStatus);
}
The result is:
USB event: 11 0
About to connect to USB host
USB event: 0 1
CY_U3P_USB_EVENT_CONNECT detected
CyFxApplnInit complete
USB event: 8 0
USB event: 5 1
setting up dma
DMA Channel Creation Failed, Error Code = 64
Any idea what I'm doing wrong?
Show LessAbout CX3 Control center
Hi,
I'm using ADC component of CYBLE-416045-02 MCU. I have 4 analog pins which needs to be attached on 4 separate ADC channels but its showing me analog internal routing error. For the time being I'm using an internal mux like shown in the picture, but i want to use 4 different channels of the ADC and not through internal mux.Please help.
Show Less
Hello,
when i am building project in Psoc Creator 4.4, i am getting an error as given below..
# An internal error occurred in the fitter: (System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.).
Need help for same..!
Thank you.
Show LessIf I config SAR for Vref, external bypassed, that commits P1_7 as a pin
on pioneer board. But no pin icon is shown on schematic.
If I then place a pin, config it as analog, P1_7, will that enable me to route
the Vref on the pin internally to other analog, like a OpAmp or comparator ?
Does that still satisfy the SAR Vref route to the pin ?
Regards, Dana.
Show LessEsteemed Contributor II
Esteemed Contributor
Employee
Employee
Honored Contributor II
Employee
Honored Contributor
Honored Contributor
Employee