PSoC™ 6 Forum Discussions

Hello.

Customer evaluations both CYB0644ABZI-S2D44 and CYB0644ABZI-S2D44ES2.

“Provisioning” of CYB0644ABZI-S2D44 was successful without any problems.

CySecuretools version is 2.1.0.

However, “Provisioning” of CYB0644ABZI-S2D44ES2 failed under same conditions.

“Provisioning” of CYB0644ABZI-S2D44ES2 do not run.

Below is error message when “Provisioning” failed.

=======================

2021-06-14 11:00:36,022 : C : ERROR : Engineering Sample version of PSoC64 detected, the current version of CySecureTools is incompatible. Please contact Cypress to receive production versions of PSoC64 Silicon.

Check the log for details

=======================

Below link describes “Provisioning” of Engineering Sample.

https://community.cypress.com/t5/Knowledge-Base-Articles/Software-Support-for-PSoC-64-Engineering-Samples-KBA230748/ta-p/253322

They installed CySecuretools version 1.4.1 according to this explanation.

The installation itself was successful, but Cysecuretools could not be started and provisioning was not performed.

Please give us some advice for success of “Provisioning” of CYB0644ABZI-S2D44ES2?

Best Regards.

Yutaka Matsubara

I found that an LPComp gave me correct results with a common mode voltage below ground. The datasheet clearly states that the input voltage range does not extend below ground - but in practice, how bad is it to use it down there, within the clamping diode range?

Hello,

I try to get know if it is possible to scan Bluetooth devices around from CYBLE 416045  module when it is set as Bluetooth Hid mouse?

Mani idea is that Bluetooth mouse scan Bluetooth devices around and if found device with given name/mac it try to connect/pair.

If someone has got knowledge about it. I will be glad for some information.

Regards,

Bartek 

Sorry to disturb everyone.

I encountered a very difficult problem.

The chip I use is CY8C614ABZI-S2F04.

I configured the AD pin and used AMUXA and AMUXB. The code is as follows:

Cy_GPIO_Pin_FastInit(GPIO_PRT9, 3,CY_GPIO_DM_ANALOG, 1, P9_3_AMUXA);
Cy_SAR_SetAnalogSwitch(SAR, CY_SAR_MUX_SWITCH0,
(uint32_t)(SAR_MUX_SWITCH0_MUX_FW_AMUXBUSA_VPLUS_Msk), CY_SAR_SWITCH_CLOSE);
Cy_SAR_SetSwitchSarSeqCtrl(SAR, (uint32_t)(SAR_MUX_SWITCH_SQ_CTRL_MUX_SQ_CTRL_AMUXBUSA_Msk), CY_SAR_SWITCH_SEQ_CTRL_ENABLE);
SAR->CHAN_CONFIG[IO_AD_CH8] = (uint32_t)(config_IO_AD_CH8);

But the problem appeared, always generating DSI interrupt, causing the program to enter CY_HALT(). I don't know where the problem is.

Please help, thank you very much.

Hello,

I want to use CY8C6145AZI-S3F02 and CY8C6148AZI-S2F44.

1. Should I use miniprog4 instead of miniprog3 for debugging and programming?

2. Should I use modus toolbox? I can't find both devices on PSoC Creator 4.4.

I am trying to set up CE217639 Heart Rate Client, and Heart Rate Server examples.

Only modification is I changed the Device to CY8C6347BZI-BLD54. When I run either example it gets stuck on Cy_BLE_Start(NULL); in main_cm0p.c

Chasing it down it goes into BLE.c, and gets stuck on the function apiResult = Cy_BLE_Enable();

This goes to cy_ble.c and gets stuck in apiResult = Cy_BLE_StackInit(&stackInitParam);

I have also tried CE217643 BLE Temperature Measurement and it gets stuck in the same place.

Any ideas why these examples are not working for me?

Hello All,

In my latest project I have implemented a bootloader using the DFU source code. I have changed from using a UART/SPI to some NVM that requires a PLL in order to copy my app1 onto the flash and this part of my project works well. My issues arises once I switch into my app1.  I use the Debug-> Attach to running target in order to test my app1. It seems to be getting stuck in the ClockInit function in cyfitter_cfg.c where it does:

status = Cy_SysClk_PllManualConfigure(1u, &pllConfig);

I have found a small patch for my issue by adding in:

Cy_SysClk_PllDisable(1u);

Onto the line directly before configure line and this seems to fix my problem. However, this is from the PSoC generated source (I believe) so if any top design changes are made I would have to re-enter this line to allow my code to work again. I know there is the CyClockStartupError function which contains 

CY_CFG_Clock_Startup_ErrorCallback();

Which looks like a possible solution to my problem but I have no clue how to implement that functionality there or if it is the correct spot.

To summarize:

When I use a PLL on app0 and app1, app1 will lock unless I disable the PLL before starting it. I have tested it and the patch works but I don't know how to implement it such that it doesn't disappear when I need files regenerated.  Could anybody give me some advice or direction as to how I should proceeded or what documentation to look at in order to implement this correctly?

Thanks!

I have code that runs just fine with 2 tasks for a random amount of time and then I get a UsageFault. The time to the fault ranges from a few minutes to a few hours, so is very hard to determine what is causing the fault. Any suggestions on how to figure out what is wrong? Stack trace attached. Thanks!