PSoC™ Creator & Designer Forum Discussions
Hi,
I have two CY8C3666LTI-201 projects which are almost identical. However, in one project, it won't let me use pin 13 (p1[2]) as a GPIO. In the other project, it does let me. And I can't for the life of me work out why. The DWR System settings are identical between the projects. I tried copying the .cydwr file from the good project to the bad project, but that didn't help.
How can I unreserve that pin?
Please see attached image for details.
Hugo
Show LessLast week I attempted to install the PSoC creator software. However, the first installation failed and every subsequent attempt gets stuck at the same spot. When I try to remove the corrupted installation files, it says that the PSoC creator isn't currently installed, which is correct, but I need a way to reverse whatever changes were made during the initial attempt and do a full reinstallation. Has anyone run into this issue before?
Show LessI have two versions of a project -SC5, and the later version SC6. They both contain the same Bootloader Project. The target project (SC5/SC6) differs slightly.
I program each board with the bootloader via the kitprog module, then program the application via a direct USB cable and the Bootloader Host (tools > Bootloader host... from PCoC Creator 4.2.
The SC5 version programs fine with no problems. However, in attempting to program the SC6 version in Bootloader Host I get the error message:
"The bootloader reported error 'Command not recognized: the supported commands are defined in the Bootloader section of the System Reference Guide'."
In the SC6 module Bootloadable component Dependencies I have set the path to the bootloader hex file to:
..\Bootloader.cydsn\CortexM3\ARM_GCC_541\Debug\Bootloader.hex and the bootloader elf file to
..\Bootloader.cydsn\CortexM3\ARM_GCC_541\Debug\Bootloader.elf in the SC6 workspace. The Bootloader Host path to the file is set to:
..\SC6\SC6_1.cydsn\CortexM3\ARM_GCC_541\Debug\SC6_1.cyacd.
If I point Bootloader Host to the same file in the SC5 workspace the board is programmed fine with no problem except that it has been programmed with the SC5 softwar, not the SC6 software.
I'm sure I am missing somethin but can't see what. I can't see anything in the bootloader component to specify the target. Only the dependencies in the target to specify the bootloader
Can anyone help please?
Show LessI've just done my third install, this time on a completely fresh Windows 10 install, to try to figure out why the static timing analysis report appears to be corrupt, yet nobody else seems to be having the problem.
It seems that if the destination directory is one of the parallels shared folders (in my case my Documents folder) then the creation of the static timing analysis report gets corrupted and won't render at all in any browser.
If the destination (i.e. workspace location) is on the normal C: drive, then all is fine.
I presume the software that writes the timing analysis uses some kind of filesystem feature that isn't implemented in the Parallels remote filesystem mechanism (I saw a similar thing with the Xilinx tools some time ago) ... everything else works perfectly, it's only the timing analysis.
At least now I have a workaround when I need to do some timing work (i.e. copy everything to the C: drive), but it would be good if this was resolved.
Regards,
Lee.
Show LessHi there,
Anybody from cypress could clarify what kind of checksum is stored in ".cymeta" section by cyelftool, and what does it checksum?
It seems to change the third dowrd, the one at 0x90500008, from 0 to some 32bit number.
Regards
Show LessHello,
I would like to update a project which was created with PSoC Creator V3.2 to new version PSoC Creator V4.2. The project uses 2 UARTS + 1IC2 Interface on processor CY8C4246AZI-M443 48-LQFP.
On Version PSoC Creator V3.2 no error message appeared when compilating the project.
The UART1 was assigned to P4[0] (RX) and P4[1] (TX)
The UART1 was assigned to P7[1] (RX) and P7[1] (TX)
I"C was assigned to P0[4] and P0[5]
Now with new version of PSoC Creator V4.2 I can create only one UART and one I2C Interface.
What's the problem?
Thanks for any help
Show LessI recently upgraded my PSoC Programmer 3.24.2. I started very consistently receiving the "Blue Screen of Death" when using the CY8CKIT-059.
After constructing a DoE here is the summary of the results:
CY8CKIT-059 Plugged in … | Power Mode Change | "Blue Screen of death" | |
after Sign in | before Power Mode Change | ||
no | no | Sign off | no |
yes | no | Sign off | no |
yes | yes | Sign off | no |
no | no | Log off | no |
yes | no | Log off | no |
yes | yes | Log off | no |
no | no | lock | no |
yes | no | lock | no |
yes | yes | lock | no |
no | no | shutdown | no |
yes | no | shutdown | no |
yes | yes | shutdown | no |
no | no | restart | no |
yes | no | restart | no |
yes | yes | restart | no |
no | no | sleep | no |
yes | no | sleep | no |
yes | yes | sleep | YES |
no | no | hibernate | no |
yes | no | hibernate | no |
yes | yes | hibernate | YES |
I've recently upgraded my PC from a Win 7 laptop to a Win 10 laptop. Nothing else has changed. (same miniprog 3, cables, target board, etc.) It's loaded up with the same version of PSOC Creator (PSoC Creator 4.2 (4.2.0.641)). My application software source is checked out from SVN compiles the same .hex file.
I've verified that:
- I'm set to SWD debugging in the system settings
- The debugger settings (SWD, 1.5 MHz, Reset, 10-pin, etc.) match my old PC.
Both computers load my application software with either the standalone programmer or PSoC Creator, but only the Win 7 computer will break in main(), sync up the debugger to source code. The Win 10 PC will do neither.
I've run the range of miniprog 3 frequencies and the best I was able to do is to get it to halt a the reset point after loading and it would only display in the disassembly tab.
I've surveyed old community posts, but I see nothing new to try. What else can be done?
Show LessI couldn't make ftoa work and I wanted to control the display format and rounding - then I came across this code snippet and adapted it but it's still not quite what I need.
Can someone please help me tweak it to add a significant digit parameter so that I can specify how many digits after the decimal point?
Here is the routine
//*****************************************************************************
// TM convert float to string
// tested and working on PSoC6
//*****************************************************************************
void tmFtoStr(char* p, float x)
{
int n,i=0,k=0;
n=(int)x;
while(n>0)
{
x/=10;
n=(int)x;
i++;
}
*(p+i) = '.';
x *= 10;
n = (int)x;
x = x-n;
while((n>0)||(i>k))
{
if(k == i)
k++;
*(p+k)='0'+n;
x *= 10;
n = (int)x;
x = x-n;
k++;
}
/* Null-terminated string */
*(p+k) = '\0';
}
I call it like this
int main(void)
{
float flt1;
char myString[20]={};
flt1 = 3.142;
tmFtoStr(myString, flt1);
printf("%s\n", myString);
.......
}
but the print out from the above is like this...
3.141999721527
I think I know what to do but I am scared that I'll break it - I want to add a sigDig parameter so I call it like this...
tmFtoStr(myString, flt1, 3);
and get 3.142 - ideally doing rounding if possible. Any help would be appreciated.
Also, is the problem above because of the inability of floats to store precisely?
Ted
Show LessHi Guys,
I am trying to build binary for CYBL10563-56LQX1 processor with came with came with CY8CKIT-042-BLE PIONEER KIT.
I managed to generate the a make file from the PSoC Creator and use it to build the application under Ubuntu Linux.
But the hex file created by the objcopy does not work. I mean the PSoC Programmer does not load.
The command I used to generate the hex file is as follows:
arm-none-eabi-objcopy -j .text -j .data -O ihex "$1" output/debug/bin.hex
I have compared the binary produced by objcopy and cyelftool.exe with a hex editor and found that the format is completely different.
Clearly the linux command is not doing the job.
Anyone knows how I can generate the correct hex file for the KIT? Or may be load the objcopy hex file?
Your help will be much appreciated.
Thanks in advance.
Show Less