PSoC™ Creator & Designer Forum Discussions
Hi All,
Firstly, apologies if I'm posting in the wrong section...
I'm working my way through the PSOC 101 tutorial videos and am having a bit of trouble on the "extension" task of video 6 which uses a series of toggle flip flops to cycle through led colours.
Initially I followed the task with two flip flops as explained and had no problems, but when I tried to add a third some unusual things came up.
Assuming it's a positive edge flip flop, in my configuration as far as I can tell the order should be: off, white, magenta, yellow, red, cyan, blue, green, off, etc...
I don't seem to have a consistent order, and whats more it seems to be often changing colour when I release the switch as well as pressing it. I've uploaded the project, so if anyone's got a few minutes, do they mind taking a quick look?
Thanks in advance,
Rob
edit - Here's the link to the video if that helps - http://www.cypress.com/training/psoc-101-video-tutorial-series-how-use-arm-cortex-m0-based-psoc-4
Show LessHi all
I'm experimenting with the bootloader component to distribute software updates over a CANbus link using cyflash as host tool. I've found what I believe is a glitch in bootloader components v1.40 and 1.50.
First of all we're talking about GET_METADATA command.
The documentation states that response packet data should be 56 bytes. In bootloader v1.30 implementation we can see that after the memcpy() we have a rspSize = 56u. v1.40 and v1.50 have a rspSize = <INSTANCE_NAME>_RSP_SIZE_GET_METADATA which is a #define Bootloader_RSP_SIZE_GET_METADATA (0x56u) in <INSTANCE_NAME>_PVT.h (note the 0x). Seems to me that an unwanted hex has slipped in in v1.40 and v1.50 and now we're getting invalid GET_METADATA responses.
Am I missing something?
Show LessI have a project that uses almost all of the PSoC 5LP UDB's. It uses multiples of a number of components.
I was needing a decent size counter but the 24-bit and 32-bit UDB counters used so much of the digital resources, but I wanted the higher counter in hardware. I had used the datapath for another part of the project and thought it might work great for that. I saw some mention in the TRM of time-multiplexing the datapath, but couldn't find any good examples. So I took a stab at a time-multiplexed datapath counter and thought I would share. For my purpose the counter did not have to run at the absolute fastest speed of the device.
It is still rough now(it seems to be working but no detailed testing yet), and I am sure there are cases where things don't work as they should, but thought I would throw it out to the community anyway. Maybe some folks will have some comments or more efficient ways to do things to make the component better. As of right now there is no documentation other than what is in this post.
Basic functionality- The down counter is a 23bit Down Counter that uses 1 8bit datapath, 1 count7(or control register) and some PLD cells. I am sure the state machine could be simplified more by someone more experienced with them and probably use less resources.
To use-
The clock should be set to 3 times the rate of the counter(so if you want 1MHz counter set clock input to 3MHz). Remember the datapath is time-multiplexed to use less resource(basically using the datapath like a simple CPU) so will not run at full clock speed.
The lowest 7 bits are set via the count7 write_period, usually default 127 is fine(because if you needed 7bit or less counter you probably wouldn't be using this component)
CY_SET_REG8(<datapath_F0_PTR>) for the middle 8 bits
CY_SET_REG8(<datapath_F1_PTR>) for the upper 8 bits
would better to eventually have a .h file that does this for you in one call.
Hope someone find it useful. Any additions are great too.
Thanks,
Chris
Is there any way of continue running the program after reaching a breakpoint without having to disable it?
I want to check my values in a loop and stop every time it reaches the breakpoint.
But right now I have to:
* disable the breakpoint
* set a new secondary breakpoint one further in the code
* run the code to it
* re-enable my original breakpoint
* disable the secondary breakpoint
* finally, run the code to stop where I really want !
It must be a better way of doing that!
Show LessAttached is a component that I created for the Color Graphics LCD shield based on the Nokia 6100 display. They can be found at Sparkfun and other web sites such as ElecFreaks and even Ebay. There are two versions of the display, one with a Philips controller and another with an Epson controller. I tested the one with the Philips controller, but could not find one with the Epson controller test it. If anyone knows where I can get one with a Epson controller, let me know and I'll test it and make updates if needed.
It is hardware compatible with the new (Arduino hardware compatible) PSoC 4 CY8CKIT-042 board as well as the FreeSoC Explorer board that uses the PSoC 5LP. The component of course supports both PSoC 4 and PSoC 5LP and has been optimized for a 32-bit controller. You can also easily wire it to one of the other Cypress Development boards with a few jumper wires.
Below is a couple of places you can get the display shield. The one from ElecFreaks is very bright, but you need to add one more signal to drive the backlight control, (D10 Arduino) or P3[4] high on the PSoC 4 CY8CKIT-042 board. The display I purchased from Ebay also work right out of the box.
The attached file contains the component library and a simple program that provides example code for most of the functions. I plan to post a PSoC4 and PSoC 5LP waveform display project in a week or two as well, that uses this same display if there is any interest. The example project is for a PSoC4, but it can be changed to a PSoC 5LP as well.
Best regards,
Mark
Show LessHi.
There is #include <cytypes.h> in my source code,
and #include "cyfitter.h" in the "cytypes.h".
but I can not find cyfitter.h anywhere.
how can I find it ??
Thanks.
Show LessIs it possible with psoc creator to debug without hardware present, like an instruction set simulator? What is the "Debug without programming" option do in psoc creator?
Does imagecraft offer this option as a stand alone product? I think that IAR offers this...
many thanks
Show LessHi,
perhaps a dumb question, but does anybody know to which interfaces the STDIN, STDOUT and STDERR streams are going on PSoC? Is this documented anywhere?
Regards,
Ralf
Show LessHi,
I'll make a bootloader for the PSOC 4 BLE. I have a workspace with 2 project example BLE_Shared_Memory_Bootloader and Bootloadable.
It works well with BootloaderHost tool. But I would like to debug my bootloadable app with PSoC Creator 3.2 SP1. In the project Bootloadable I can not Debug (F5).
How to debug without going back each time by BootloaderHost?
Thanks,
Eric