PSoC™ Creator & Designer Forum Discussions
I am trying to control a digital multiplexer based on input from a serial command. I can't figure out how to command the multiplexer selection through the software (main.c). How do I do that? What document should I be looking at to determine this?
Show LessIs it possible to simulate the design and view the simulation results in PsoC creator?
There should be a popup warning when user has GPIO set to Global in
and then tries to set it also as a Pullup or Pulldown, ie. that it cannot be done.
Also seems ap notes do not cover this, line AN2094.
This also should be modified as it implys one could have a PU/PD on a global
net in, pic below. Same with TRM pictoral.
Regards, Dana.
Show Less
I work for a company that sells products in the real world. It is our livelihood. We have developed a new line that must behave like our legacy products only in a smaller physical package. The PSoC 3 was chosen by the hardware developer. The hardware developer has a one sub-routine test program that verifies the hardware. My job is to write the product program that interfaces to customer machines and their programs.
Much of the code has been re-used and has been working across 3 different microcontrollers and 3 different compilers.
I used the PSoC 3 Developer Kit (CY8CKIT-030) to write my program while the hardware designer worked on the first pass hardware. I began using PSoC Creator 1.0 and eventually both the hardware developer and I got on the same page using 2.0 and then 2.2. I integreted his code with mine and we proceeded to release prototypes to our customers for evaluation. We are mid stream in the development.
The hardware engineer upgraded to PSoC 3.0 and I attempted to do the same. To be on the safe side, I do my development on a laptop but keep a desktop computer in sync with the laptop in the event that the laptop crashes. When I tried to compile the program that compiled with no errors or warnings in 2.2, there were 2 days worth of work in clearing up the warnings and ultimately, the program ceased to work in our product.
That you must recast a stack variable as a const on a stack is the least of my worries at this time. The point is, Cypress and their partner Keil have collapsed legacy code AT A RANDOM POINT IN TIME WITH NO FOREWARNING.
The changes to make the warnings stop increased the code slightly, so the argument that after all this time, compilers need to be produce tighter, more efficient code doesn't apply to PSoC 3.0 and Keil's latest version therein.
Show LessCan we develop our own bootloader component withour having communication interace code inbuilt in it?
If yes then what is best way to start for creating using Creator ide?
Show LessI've tried to read through all the posts in the forum that appear to discuss the UDB Editor in PSOC Creator 3.0
I didn't "reply" to any of them, since no ONE has been designated a central clearinghouse for trouble reports on the UDB Editor.
I apologize for the post, please delete if wrong type/format.
I've seen posts from some about specific problems and some requests of "how do we report problems". I'm not sure I, or others, understand any tracking or support procedure for something like this. I don't think we need to open a "MyCase" for each individual problem and I know of no way of seeing all open or closed bug reports to avoid duplication. If you want to post them to this thread for Robyn to forward to Development team or for Nick (NSF-Cypress?) to reply to.
I've seen some posts by Dana, psoc73, bob, nick, spider... etc but think most of my issues/questions have not been addressed.
I came late to PSOC Creator 3.0 (PC 3.0)because we are primarily working with Christmas Lighting products and my busy season has just ended. I couldn't take a chance of working with a new environment with my production code late in the season.
All in all I think PC 3.0 is a VAST improvement and applaud Cypress on this major release.
Once over the learning curve I find the UDB Editor to be a great tool in the making. I don't think it is there yet, but hopefully the development team can finish it up soon.
In the tutorials they talk about "advanced features can then be added by copying the verilog ..." or something close to that. But they never discuss what they are calling advanced.
Here is a short list of the 'problems' I'm having so far:
1) I can't locate any way to control most of the features of the FIFOs. I see several FIFO properties but can't find the way to change the FIFO to input vs output (bus vs udb sourcing). Am i overlooking something. Having to copy the verilog and modify it will be a development headache.
2) If you add a control or status register to the USB Design DON'T delete the unused bits for 'cleanliness'. If you do you will get a 'Net_1' undefined message. Just leave unused bits there.
3) If you add a Count7 register I can set some of the inputs (reset, enable, etc.) but can't set the clock, and more importantly I can find no way to USE the Count7_tc output. I believe the verilog is being generated correctly. It makes a wire and adds it to the Count7 module definition but if I try to use the signal as part of ANY expression then I get an error saying it doesn't exist and, of course, the verilog becomes non-generated. Take out the expression and the verilog comes back. So I think it is an internal table lookup problem and not a real generation of verilog problem.
#1 is major IMHO, #2 is cosmetic, #3 is major. Altogether I don't see how I can use the UDB Editor for production code until these types of problems are fixed. I've invested a lot of time over the holidays learning the GUI and visually designing the state machines and examining the generated verilog to see how they do it. It is BEAUTIFUL and VERY powerful, and I want it to work soon!!!
-Ed
Show LessWhen programming in C we sometimes use struct and union. While structures are displayed perfectly, a union within a struct does not show its actual values, although the naming of the components is shown correctly.
Bob
Show Less"Filter_ADC_VDAC Example Project"
When it is built shows error on line 40 in main(), but project reports as building
successfully ?
OHx51.exe Filter_ADC_VDAC01.omf HEXFILE(Filter_ADC_VDAC01.ihx)
c8051-elf-omf2elf.exe Filter_ADC_VDAC01.omf Filter_ADC_VDAC01.elf
cyhextool -o .\DP8051\DP8051_Keil_951\Debug\Filter_ADC_VDAC01.hex -f .\DP8051\DP8051_Keil_951\Debug\Filter_ADC_VDAC01.ihx -prot .\Generated_Source\PSoC3\protect.hex -id 1E028069 -a EEPROM=90200000:800,PROGRAM=00000000:10000,CONFIG=80000000:2000,PROTECT=90400000:40 -meta 0301 -cunv 00004004 -wonv BC90ACAF -ecc .\Generated_Source\PSoC3\config.hex
Flash used: 10195 of 65536 bytes (15.6 %).
SRAM used: 137 of 8192 bytes (1.7 %).
--------------- Build Succeeded: 01/06/2014 06:35:30 ---------------
Regards, Dana.
Show LessBob Marlowe pointed out in this thread -
http://www.psocdeveloper.com/forums/viewtopic.php?f=42&t=11410
A way user could view in debug EEPROM data.
Why not a tab in the debug memory viewer that would show E2PROM, just like RAM and FLASH
tabs are done.
Make it painless for user.
Regards, Dana.
Show LessI am not sure if this is the place to post this question so let me know if I need to post it somewhere else. I am interfacing an accelerometer with an 8k PSoC1 via i2c. I need to cacluate a specific angle from the accelerometer data without using the <math.h> library. I know the value of two sides and could use arctan to get that angle but when i include <math.h> I run out fo code space. Is this a possibility? If so how can I do this?
Thanks...