PSoC™ 6 Forum Discussions

Hi. 
I started to use PSoC Programmer 3.29.0 which is installed by PSoC creator. When I tried to connect to the board, it showed a message about firmware version mismatch and that I should upgrade the firm by going to Utilities->Upgrade Firmware. 
I did so, and went through the update and finished (It might had failed at the end, coz I remember that when it was about to finish, all usb ports got restarted and my keyboard, mouse and usb headset stopped working for a few seconds.) 
After that neither PSoC programmer nor PSoC creator are able to connect to the device. 
In my PC's device manager I can see the following devices:

Twice I held SW3 and connected the usb cable and I saw that PSoC programmer can detect the KitProg3 bootloader and I followed the instruction to upgrade the firmware again. but no luck:

Disconnected at 1:14:27 PM | Bootloader device
Firmware Update Finished at 1:14:25 PM |
| Succeeded
| Verifying...
| Upgrading...
| Initializing...
Firmware Upgrade Started at 1:14:12 PM |
Firmware Upgrade Requested at 1:14:12 PM |
Connected at 1:13:55 PM | KitProg2/KitProg3 bootloader devices are detected
| Please close all ports, then navigate to the Utilities tab and click the Upgrade Firmware button to recover Bridge

Hi community,

I am trying to configure the pin P0_4 as a high-Z, but I am having trouble since I don't see any changes in the oscilloscope. I want to know if this pin works as an output since the eval kit has the SW2 connected. I removed the solder from the SW2 in case it caused any interference. 

This is how I am initializing the pin:

cyhal_gpio_init(PS_POR_B, CYHAL_GPIO_DIR_INPUT, CYHAL_GPIO_DRIVE_NONE, LOW);

Any help is welcome!

Regards,

Luis Flores

Hello,

In the Modus Toolbox 3.1 "Security App" Example, the CM0+ linker scripts for TARGET_CY8CPROTO-062-4343W are missing the "shared_ram" section.

./shared/linker_script/TARGET_CY8CPROTO-062-4343W/TOOLCHAIN_GCC_ARM/COMPONENT_CM0P/cy8c6xxa_cm0plus_btldr.ld
./shared/linker_script/TARGET_CY8CPROTO-062-4343W/TOOLCHAIN_GCC_ARM/COMPONENT_CM0P/cy8c6xxa_cm0plus.ld

Please see attached picture.  Hope you can correct them.

Thanks,

SK

Hello,

I started a new application by creating a custom BSP (MPN - CY8C6347BZI-BLD53) and started a Hello World example.

I then added the necessary libraries to get bluetooth working. But the callback BTM_ENABLED_EVT isnt occuring.

When I pause the application, this is where it is stuck at. PFA image for the debug info.

I can see that rtos is working as I have an LED task that is working fine.

How do I fix this issue?

Thanks!

Hi, 

I am trying to include mbedtls library for an example project called "Cryptography_AES_Demonstration" (Available in MTB Examples). 

But when I try to build the project 

make[1]: *** Waiting for unfinished jobs....

bsps/TARGET_APP_CYSBSYSKIT-DEV-01/config/GeneratedSource/cycfg_system.c:117:28: error: initializer element is not constant

117 | .enableOutputDiv = true,

| ^~~~

bsps/TARGET_APP_CYSBSYSKIT-DEV-01/config/GeneratedSource/cycfg_system.c:117:28: note: (near initialization for 'srss_0_clock_0_fll_0_fllConfig.enableOutputDiv')

bsps/TARGET_APP_CYSBSYSKIT-DEV-01/config/GeneratedSource/cycfg_system.c:170:19: error: initializer element is not constant

I know it works with the other mtb examples where mbedtls is already added into its project. 

Expectation: Steps to include the mbedtls library to the project and build without an error.. 

Your prompt response will be greatly appreciated.. 

Hello, I am looking for an example for reading the on-chip temperature sensor on a PSOC6 device:
Device: CY8C6137BZI-F14 (124-BGA)
IDE: Modus Toolbox 3.1, Device Configurator 4.10.0.959
We have A2D code running reading of P10

I can't figure out how to get Device Configurator to select the internal temperature sensor as an input to the 12 bit SAR ADC

Hello -

We recently modified our code to use PILO internal clock instead of the external WCO, because of some WCO startup issues at cold temps (and we don't really need the WCO).  Following the docs/forum posts I could find, it seems I want to "trim" the PILO periodically (which involves measuring the current clock frequency).

I added the code to measure the clock/adjust the PILO trim.  I then found that (occasionally, not always), a Cy_Flash_WriteRow() call would fail with CY_FLASH_DRV_IPC_BUSY.  This is in completely unrelated flash writing code that I haven't touched in months (or years).

I narrowed it down to having an 'active' clock measurement going on (I have called Cy_SysClk_StartClkMeasurementCounters , but Cy_SysClk_ClkMeasurementCountersDone  is still returning FALSE (the measurement isn't complete)).  If I call Cy_Flash_WriteRow during this time, I will get that IPC failure.

I noticed that Cy_SysClk_ClkMeasurementCountersGetFreq (which you call after the "done" call returns TRUE) has a warning about a possible '0' return value, if "during measurement device was in the Deep Sleep or partially blocking flash operation occurred".  This sort-of implies that a flash operation may interrupt a clock measurement, not that a clock measurement would cause flash write API failures.

So, I changed my code to wait for  Cy_SysClk_ClkMeasurementCountersDone  to return TRUE before I do any flash write.  That seems to have 'fixed' it.  Side note: there doesn't seem to be any way to 'abort' a clock measurement - you must wait for it to complete (and, that can take some time, depending on how many clock cycles you are counting)

Is this the expected behavior?  Is it known that starting a clock measurement will cause flash functions to return the IPC busy failure?

Is there any way to 'interrupt/abort' an existing clock measurement (rather than waiting for it to complete)?

This is on a CY8C6247BZI-D54 PSoC 6, using PSoC Creator 4.3.

Thanks for any help on this

I have the CY8CPROTO-062-4343W board. I broke all the capturable components and reconnected the Kitprog and microphone. First, I noticed that the board was no longer being powered from the USB via Kitprog. So I powered the board from another USB, which seemed to work. But I could not program the board. It fails at the last step, it seems:

...
Info: vTarget = 3.319 V
Info: kitprog3: Getting device (mode: reset) ...
Error: kitprog3: unable to acquire device




Message: clock speed 2000 kHz


Error:
Error while connecting DP: Unable to read IDR Error: Error while connecting DP: Unable to read IDR
Error: Error while connecting to DP: Unable to read IDR Error: DAP 'psoc6.cpu' initialization failed (check if connection, power, transfer, DAP is enabled, etc.) ** Failed to initialize OpenOCD ** Shutdown command called ** Program operation failed ** srst_on




ly split srst_gates_jtag srst_open_deassert_srst
Error: Error connecting to DP: Unable to read IDR
Error: Error connecting to DP: Unable to read IDR Error: Error connecting to DP: Unable to read IDR
Error: Error connecting to DP: Unable to read IDR
DP
Error: Error connecting DP: IDR cannot be read
Error: Error connecting DP: IDR cannot be read Error: Error connecting DP: IDR cannot be read
Error: Error connecting DP: IDR cannot be read Error: Error connecting DP: IDR cannot be read Error:
Error conne Message: psoc6.dap: Powering down debug domain... cting DP: Unable to read IDR Error: [psoc6.cpu.cm0] DP initialization failed Error: Error connecting DP: Unable to read IDR Error: Error connecting DP: Unable to read IDR WARNING
Error: Cannot power off debug domain

What's going on here?

smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-6/%E8%BF%98%E6%9C%89%E4%B8%80%E4%B8%AA%E8%AF%9D%E9%A2%98-kitprog3-%E6%B2%A1%E8%83%BD%E8%8E%B7%E5%BE%97%E8%AE%BE%E5%A4%87/td-p/634899