PSoC™ Creator & Designer Forum Discussions
Does PSOC3, 4, 5 have the solution that can apply high DC voltage power line communication?
I've been finishing this proyect that was of other person who worked with me, but I has a problem when I build it
ERROR: .\CortexM0\ARM_GCC_493\Debug\Tarjeta de comunicacion PLC.elf section `.rodata' will not fit in region `rom'
ERROR: section .cyloadablemeta loaded at [00007fc0,00007fff] overlaps section .rodata loaded at [00007ad8,00008147]
ERROR: region `rom' overflowed by 0 bytes
collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
If you can give instruction for how to solve it, i will appreciate itShow Less
I'm trying to get every bit of performance possible out of my PSOC 4 BLE MCU. About the only thing I haven't tried is the newer GCC toolchain (5.4). I downloaded and installed it, and pointed to its bin directory as the GCC Generic setting under Project Management in PSOC Creator 4.
This allows me to run a build, but the linker fails with "No interrupt vector."
GCC 4.9 (default) and Keil MDK toolchains build successfully (Keil result is much slower than GCC result).
Any pointers to correct this?
I dusted off my fairly old Dev Kit today thinking I will get back to using PSoC for some smaller projects. This is the CY8CKIT-001 dev klit that came with PSoC1 and PSoC3 processor module with the promise of PSoC5 module support when it was "just around the corner".
I know I successfully used it in the past.
I downloaded PSoC Creator 4.0 from Cypress web site and tried running one of the example programs. Once the project builds and go to program it, the Miniprog3 does see the module but with a "i" symbol on it saying "Module was recognized but PSoC Creator does not support it at this time."
Has the CY8CKIT-001 been duplicated? They seem to still sell them on the site. Do I need a new firmware for it or something?
Via GDB on Eclipse it is possible to use the JLink debugging adapter. The Cypress MiniProg3 causes a lot of trouble. Most of the times the connection to the PSOC fails. Yes, I have tried very short wires and capacitors between VCC and GND. I spend a lot of hours trying to get this adapter working.
The main advantage of the PSoC Creator is that the components could be added via drag and drop. The Creator would be the tool of my choice. But for now I have to export my solution each time to Eclipse after changing the components. This is a bit frustrating.
Would it be possible to integrate the JLink nativly into PSoC Creator? The PSoC Creator is a very good IDE, but this is my only wish.Show Less
In light of recent acquisitions, new CEO and inclination towards IoT, Cypress needs to re-evaluate their stance on Windows only treatment to PSoC creator.
The locked-in clients might be happy with the existing offerings. But given the current stage of IoT, the early adopters, hackers and innovators would rather go with something that provides deterministic and cleaner workflow instead of click and drag approach of PSoC creator. Blink a LED should be as easy as plug board the board and run a script (see arduino, rpi).
May be publish a simple plain text DSL for UDB configuration and release a binary that would do all routing and assembly of ARM and UDB components. I think PSoC is itself using GCC for ARM part. IDE could be second thought.Show Less
I have a block diagram for PSOC5. Now, I want to transfer from PSOC5 to PSOC4. However, there are some errors which said incompatible for certain block. May I know how can I solved this? I am new with this PSOC software. Thank you very much.Show Less
I'm trying to find out if this is the correct operation of PSoC Creator or not.
I've included screenshots for visual confirmation.
I start a new project and choose CY8C4248BZI-L489.
I add 2 output pins, 2 logic level sources, an OR gate and a NOT gate, wire them up to the output pins, etc.
Build and compile. Go to the pin editor and a bunch of ports are missing... So how do I use the headers on the kit board?
I ran into this problem when I "ported" an existing product to the chip, so I decided to start from scratch and no matter what I did, ports when missing from the pin editor.
I'm upgrading from PDL v2.0 to 2.1 (precisely PDLSetup_2.1.0_8-16-16.exe as of Oct 20, 2016). I compile with:
arm-none-eabi-g++.exe (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release) [ARM/embedded-5-branch revision 237715]
In the hope that they'll be gone with the next release, I'd like to provide some patches to fix harmless warnings such as:
- wrong #include path
- missing quotes around #error message string
- -Wparentheses (because of v = v & ~x | y which becomes v = (v & ~x) | y)