PSoC™ Creator & Designer Forum Discussions
text.format{('custom.tabs.no.results')}
"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...
When trying to access a specified register in GCC the syntax is given clearly. Here an example:
volatile register uint32 R2 asm ("r2");
This line gets flagged by the code-checker stating that the label "r2" is ignored because R2 is an automatic variable.
Instead declaring
static volatile register uint32 R2 asm ("r2");
is accepted and no error displayed.
But when compiled, the first declaration is error-free and the register can be accessed from C without any problems, while the second declaration is flgges as an error.
I admit that this issue will only touch the "Cracks", but the truth is: I am one.
Bob
PS: before hitting the "Post"-button everything looks nice, let's see whether the text gets clobbered.
Show LessAre there any tutorials on how to use the UDB editor? I can't even find it in Creator.
Hi, all.
I have the CY8C5868AXI-LP035, the Creator 3.0 and i use the GCC compiler.
How can i place a section (for ex MySection) to an adress 0x10000?
Thanks.
Show LessWe are getting close to finalizing the features for our new design interface - System Builder. It is an exciting new way to quickly make designs in PSoC Creator. We'd really like to get your feedback on it (I added a screenshot below, to whet your appetite).
If you want to give it a try just make sure you have PSoC Creator 3.0 and follow the instructions in the "Feedback System Builder Prototype" forum. You can post questions and suggestions in that forum and your ideas will be seen by all the engineers and marketing guys on the project.
-- mgs
Show LessI must be losing my marbles, what happend to the GCC docs that were in
Creator 2.2 documentation menu ? Eg, they are not in Creator 3.0 ?
Regards, Dana.
Show LessWhen using CyIntSetPriority() the value is checked against a #defined constant named CY_MIN_PRIORITY near line 319 in CyLib.h. CY_MIN_PRIORITY has the value 3, but it should be 7. The description of CyIntSetPriority() in "System Reference Guide" shows valid priority ranges from 0 to 7 (which is quite logical).
Bob
Show LessPSoC3 - 8 program address breakpoints, 1 memory access breakpoint and 1 watchdog trigger
breakpoint
PSoC5LP - 6 program address breakpoints and 2 literal access breakpoints