Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I am building for PSoC 6, and PSoC Creator 4.4 insists on generating IAR and MDK files which I have no use for - and just clutter up an already very c...
I am building for PSoC 6, and PSoC Creator 4.4 insists on generating IAR and MDK files which I have no use for - and just clutter up an already very cluttered Workspace explorer. The only message I could find about this is: https://community.cypress.com/t5/PSoC-Creator-Designer-Software/code-setup/td-p/129401?start=0&tstart=0 Which does NOT resolve or fix the problem. If the only possible solution is to recreate a very complex workspace from scratch, I won't bother. My project is (at present) 002-16767_CE216767 PSoC 6 MCU Bluetooth Low Energy (BLE) Device Firmware Update (DFU).zip, so please DO NOT ask me to upload my project - you already have access to it. Here is my build settings, so you don't have to ask for it:
And here is an obvious example of the problem: PSoC Creator generates 3 new files (for 3 IDEs) for each of two projects within the workspace:
OK, now just to reiterate, so I don't get the standard non-answers: You already have access to my complete project, BECAUSE IT IS ONE OF YOUR EXAMPLES, and I have provided a screen shot of my Build Settings, SO PLEASE DO NOT ASK FOR IT.
I recently started working with a PSoC 6 development kit (CY8CPROTO-063-BLE). As I was familiar with PSoC Creator for PSoC 5LP, I started deve...
I recently started working with a PSoC 6 development kit (CY8CPROTO-063-BLE). As I was familiar with PSoC Creator for PSoC 5LP, I started developing simple projects targeted to PSoC 6 devices using PSoC Creator 4.4.
The problem is that the build and programming steps are painfully slow on my machine, while being very fast when using PSoC 5LP as target device. Do any of you know what could be the cause of this behaviour?
I am attempting to incorporate the Renesas ZMOD4410 IAQ functionality into a PSOC 4200M project. Calls to some of the floating point functions in newl...
I am attempting to incorporate the Renesas ZMOD4410 IAQ functionality into a PSOC 4200M project. Calls to some of the floating point functions in newlib libm and libgcc consistently cause a hard fault. I have been working with Renesas support to resolve the issue and they suggested a possibility that there is a mismatch between either the version of the GNU compiler or command line flags between the IAQ libraries and the PSOC libraries.
Last details sent to Renesas:
I did some testing and have attached some screenshots of the details of the failure with the configuration included in the optimization, linker, and Stack/Heap configuration shown in the screenshots. The bl_dmul screenshot shows the instruction that causes the hard fault and the stack_trace screenshot shows the stack at the beginning of the error handler (handler.jpg). This set of traces are for no optimization and the fault consistently occurs on the d_mul instruction.
I found that changes to the optimization level changes the actual instruction (which is still consistent for each optimization level) that causes the fault. No matter what the optimization levels, the instruction that cause the error is always in the libgcc or libm floating point routines resulting from a call from calc_iaq_2nd_gen_internal().
I have attached screenshots with additional details.
Last details from Renesas
Here is the details that Renesas provided on the compilation of the IAQ library.
Compiler version: We use 7-2018q2 version. Can you check for an update of your compiler?
Our additional/differing flags are: -static -O3 -std=gnu11 -fsigned-char -fdata-sections; We do not use -ffat-lto-objects. On the description of the options I don't see any issues with the different options
I have the following wires connected from the MiniProg3 to my target board: VTARG to my 3.3V rail (PSoC supply). No other power applied to the board. There is no other significant load on this rail, maybe 30mA. GND to GND of course SCLK to PSoC pin 1 (P3_1) SDAT to PSoC pin 8 (P3_0)
The programmer cannot connect. It takes a long time, like 30 seconds, then shows the target as "Cortex-M0", but won't connect. Sometimes it doesn't even show that.
Put a scope on VTARG and it is slowly cycling on and off to 3.3V.
I have changed the chip, same result.
I have had similar issues with the standard 5 pin programming interface before, but only when I have needed to put wires to extend the programming interface. I have found that it will NOT detect the target if those wires are more than maybe 2" long. So in this case, because I have wires, they are about 1 inch long.