PSoC™ 4 Forum Discussions

Hi, throughout processing my project, I need to generate floating point frequency(sort of 9.091kHz) from output line. Here's some example picture for better understanding to you guys. And I know by modifing period, I can change the output freqeuncy. But I got a warning from PSoC4 creator that I can only generate integer range freqeuncy, I guess?

From seeing this warning, I just wonder is it just warning? Or I can't get floating point frefqunecy? I hope it can.

Thanks, 

Best regards,

When I try to program my CY8CKIT-041-41XX board, I get the Port acquire failed Can't open CMCIS-DAP port message and nothing else happens.

I have been searching through the forums and tried many suggestions (except the ones involving a soldering iron). So I suspect my configuration may be all messed up. None of the suggestions were specific to this board, so I may have set something wrong. However, this was the case when I first plugged the board in with a fresh install of PSoC Creator 4.4 and the CY8CKIT-041-41XX software installed.

Can someone please help me step through this? It's driving me crazy. 😐

I have updated the onboard Kitprog2 to Kitprog3.

Also tried downgrading it back to Kitprog2, but PSoC Creator complains about that, so I changed it back to 3 again.

How should I start debugging this?

Thanks in advance,

Rod.

When I update my PC, I get an error like the one attached.
Do you know the cause?
Please contact us if you need information about the version of your PC.

We were having trouble obtaining a particular PSoC 4 that we had been using, so ordered a substitute that adds an ADC that we don't need. It works fine, but it requires that I rebuild the code with that specific device specified. The only difference in the hex files is the metadata in segment 0x9050.

Since this is a bootloadable project, it includes a bootloader, which requires the same change to the device type. I notice that the silicon id actually appears somewhere in the code, so there is also a one-byte difference in the code, on top of the difference in the metadata.

Furthermore, the device type is not a build property, it's a project property.

For an automated build, this means I have to have two copies of each project, with one tiny difference between them, and run twice as many builds. I don't see any way to have two projects share the same source code and other resources, either. For manual builds, I either have to do the same thing, or I have to rename the artifacts from one set of builds, then edit the projects, then rerun the builds, then rename those artifacts under different names.

This sucks. I can probably find where in Bootloader.c it embeds the silicon id, and take that crap out. That would mean that in both bootloader and bootloadable, I'd only have a metadata difference. Is there a way to use a post-build step to modify this metadata? Everything I've tried to do manually to the hex file is rejected by the PSoC Programmer, so there's something in those last three undocumented bytes in the metadata that is foiling my attempts to make one build for two slightly different devices.

Does anyone have a solution for this?

Hello

I new to PSoC creator and I'm wondering why I cannot debug an example program after building it correctly?

I am trying to debug an example (CE214025 – Trackpad with Color Gamut) on the PSoC 4100S pioneer kit.

When I try to debug I get the following error?

here are the versions of PSoC Creator

Thanks in advance

Steve K

I am trying to use a MiniProg3 device with an ARM based Windows 11 host. I cannot get the device drivers to load for the miniprog. It is showing up as an unknown device.

I have tried removing and reinstalling the PSoC Programmer (3.29.1). I also tried manually updating the device driver by pointing the Device Manager at C:\Program Files (x86)\Cypress\Programmer\drivers\mprog3 but it says windows could not find drivers for your device.

Am wondering if I am out of luck on an ARM based PCor if that is a red herring. I have used this miniprog before on other PCs so I believe it is good.

Dear supporters,

I want to use ECO（External crystal oscillator）as clock source with PSoC4.

I'm referring to the PSoC4 Archtecture TRM(Document No. 002-32818 Rev. **), but I don't understand how to handle certain parameters, so please let me know.

According to this document, Vpp, which determines the ATRIM and WDTRIM variables, can be calculated by the following formula.

I realized that DL(Drive level ; μW),ESR(ohm),CL(pF) should be substituted with the unique values that the ECO has.

On the other hand, if you refer to the ECO datasheet, the DL value may be listed as both typ and max.

Therefore, I have two questions.

1. Are ATRIM value and WDTRIM value set to safely drive within the maximum DL rating that the ECO has?

- In TRM, we are supposed to assign the maximum value of DL, but is it possible that we don't need to care about the typ and lower limit of DL value?

2. Vpp means the voltage applied to both ends of the ECO, which is controlled by the Inverting Amplifier so that it does not exceed the DL's rating? (Fig.1)

                                            Fig.1

Regards,

Chihiro Tatebayashi

I am working on a CY8C4245AZI-483 on a legacy product.  We had to switch to CY8C4245AZI from CY8C4245AXI.  Since the the dependencies have been changed, I am trying to find bootload-able dependencies files (ELF and HEX) for the CY8C4245AZI.  Where do I get these files and if not how do I generate those?

Thanks

hello everyone   I have tried to generate a 1msec delay using a timer in the cy8c4025azi413 controller plz help me.

Thank you

Pragati