PSoC™ Creator & Designer Forum Discussions

Dear Cypress Developer Community,

I am trying to do a simple application using the PSoC 6 BLE Pionner Kit (CY8CKIT-062-BLE) & PSoC Creator 4.3 (+ CyDWR) in which a distance sensor should trigger an interrupt when the value read is above a certain value, meaning the distance sensor is measuring a very short distance, let´s say, for example, 3 cm.

The distance sensor is working fine, I can read the value that it returns in volts and I can turn it into distance.

Unfortunately, I am not capable of correctly setting the interrupt limits and I am not sure how to do it. I found plenty of examples about interrupts, but none with this specific one. I am also following the instructions and information on the SAR ADC Component Datasheet and AN217666, but without success.

As soon as the debugger passes the NVIC_EnableIRQ line, the code jumps into the ISR_1_handler() function regardless of the position of the distance sensor or anything else, as the line Cy_SAR_GetResults16() comes later. In the ISR_1_handler() function, at the moment, I just blink a LED (and call the NVIC_ClearPendingIRW), so I guess it is just the setting of the ADC that it is wrong.

I also tried different “compare modes” and “low” and “high” values and checked the register values in ADC.h, but nothing seems to change. Sorry if the question seems too obvious, but any ideas on what could be wrong in here? Any example/sample code or description available?

Attached are pictures showing the CyDWR setting of the ADC, that I would expect to trigger the interrupt if the value read is above 1.65 V and some lines of code.

Many thanks,

Juan

Trying to create a basic SIPO 64 bit shift register.

I am a newbee to Verilog, and this error causing me grief. I thought that

you can declare a wide output in Module naming, then in body declare it as a

reg so it picks up symbol name of output in order to bring out to pins.

Error occurs on line shown -

Regards, Dana.

Hello

when the update manger pops up, or if i open it, there is a list of installed software.

right now, there are:

5 versions of the Peripheral Driver Library, 3.0.1, 3.0.3, 3.0.4, 3.1.0, and 3.1.1 (download)

2 versions of PSoC Creator, 4.2 and 4.3 (download)

1 version of PSoC Programmer 3.28.5 (update)

1 version of CY8CKIT-059 PSoC 5LP Prototyping Kit 1.0 Rev *A

i cannot find the memo, so:

1) do i need all 5 version of the Peripheral Driver Library?

if not, what is the best way to safely remove prior version and all of their parts?

and all the registry connections they make that would be extraneous after removal?

2) what happens when i click the update button for PSoC programmer

i think its safe to say it updates, but what happens to the old version?

does it get removed? do i have to remove it? is it safe to remove it?

3) what does the configure button do?

why is the configure button live for all of the installed software?

4) when i click on the microsoft flag and expand the cypress section,

there are several things that look like duplication(s), such as:

4 API Reference Documentation

4 PDL Release Notes

4 User Guides

plus one each of a bunch of stuff

my question here is what do i need, what can i get rid of, (safely, etc)

does cypress provide a clean up of cypress software, so that the

duplicates and out of dates, and etc can be easily cleaned up?

and i guess one other thing, when i do an update, can i make the update process

include removal of old stuff, assuming it isn't needed anymore?

thank you

Hello,

We can find CY8C6245AZI-S3D72(100-TQFP) or CY8C6245LQI-S3D72(68-QFN).

https://www.cypress.com/part/cy8c6245azi-s3d72

https://www.cypress.com/part/cy8c6245lqi-s3d72

But we can not find them in "Target device" of PSoC Creator.

We can not see "Find new devices" on "Tools".

How can we select them?

Best regards,

Yocchi

(FYI, I am doing PSoC 101 Lesson 4 and 5 with the -044 dev kit. instead of the -042 kit)

P6.5 is connected to the blue led on the board as well as a pin on the J2 Arduino header. To this novice, it should be usable and route-able.... because Cypress connected it in 2 places.

When trying to control this pin (p6.5) via hardware ( ie. SW2 and P0.7), strange things happen.

1.  The pin list on the cydwr does not always show p6.5.

2.  The program button on Creator (ctrl + F5) works but terminates with fit.m0049 and then says p6 can not be used for routed connections.

So I ask why? And did I miss a clue that would have saved me chasing this round and round for a couple days?

Regards

Tim Miner

I upgraded to 3.1.1 PDL and PSoC 4.3 the other day. Now PSoC 4.3 tells me it does not like the firmware release of the KitProg 3. I cant run at the kitProg 3 Version 1.20.x like I used too Now, having updated to kitProg3 using fw-loader and running the programmer, I used to be able to "load from device" That just hangs the programmer now... So now I have to go to Utility and reflash the kit programmer to Version 1.08 or something old like that...

Hello Cypress Members,

I have been reading these documentation for a while,https://www.cypress.com/file/385706/download and https://www.cypress.com/file/385706/download.

I  am confused with the plethora of information there. All I want is to generate a .cyacd2 file for my psoc 6 to update the whole firmware on my kit via Bluetooth using PSoC Creator v4.3. I have added the bootloader service on the kit and I can access it through CySmart App on Android. Just a note that both CM0 and CM4 core are utilized to do different tasks in my firmware. BLE component is present in the Top Design and contains several services for my application. I want to include any added services during the update as well.

So what is missing is to generate the .cyacd2 to update the firmware as I do when flashing a .hex file to update the firmware. I am not interested into patching process at the moment as it will take time to actually do all the minor editing for the new memory locations in the Flash RAM.

Thank you for your time.

I upgraded to PSoC Creator 4.3 a few days ago and it was working fine.

Today, I tried to open a project from an SVN repository that I had created using PSoC Creator 4.2.   Creator displayed an error (which I did not record) as I opened the project (something to do with permissions to run code).  I terminated the process and then went to go open the 4.3 projects that I had just previously been working on.  Ever since then, every time I try to open any of my (v4.3) projects, I get an error dialog:

I have tried Rebooting, "Repairing" and total re-installation of PSoC creator, PDL's, Programmer, with the exact same results.

I am in the middle of a project and this is urgent, so any advice would be GREATLY appreciated!  🙂

Out of the blue, my Creator software (including 4.2 and 4.3) can no longer build because it seems not to have the proper permissions.  I'm seeing things like:

--------------- Rebuild Started: 05/31/2020 19:23:01 Project: LED_Driver, Configuration: ARM GCC 5.4-2016-q2-update Debug ---------------

Build process unable to delete contents of code gen dir.  Error: Failed to delete D:Firmware\LED_Driver\LED_Driver\LED_Driver.cydsn\codegentemp\bitstream.txt: Access to the path 'D:\Firmware\LED_Driver\LED_Driver\LED_Driver.cydsn\codegentemp\bitstream.txt' is denied.

--------------- Rebuild Failed: 05/31/2020 19:23:01 ---------------

I'm also seeing an error for "UnauthorizedAccessException" as shown in the attached screen shot.

I suspect this is a Windows problem more than a Creator problem, per se.  But I've done everything I could think of to give the software the permissions it seems to have needed, and I've gotten nowhere with that.  I've even done a full uninstall/reinstall of Creator 4.3 (and completely removed my old Creator 4.2, which I'm not using anymore), and I have the same problem.  In fact, I've replaced the physical hardware for my "D:" disk drive (where I store data), since it was due for it and was starting to sputter in other ways.  But reloading a few known-good workspaces off the backup server and running them on the new "D:" drive produced the same problem.  And these all worked before.

Any suggestions where to go with this would be helpful.  If I move these files over to my "C:" (system) drive, everything cleans correctly and builds correctly, so I do suspect it is a permissions issue of some kind.  I just don't know where it's buried.