PSoC™ Creator & Designer Forum Discussions

Hi,

In Creator 4.0 i can do a custom component macro using UDBs (a SPI Master to be precise), this macro worked for PSoC4 and PSoC5LP devices, now after installing Creator 4.1, that macro seems like the attached image.

So to fix it now i have to add the two macros, one for PSoC4 and a copy of the macro for PSoC5LP, not very annoying but now i have to do the same changes in two files instead of just one.

i develop one project on cy8c4246 using psoc creator and trying to move variable to particular location in ram.For that i modified linker after reading some documents.But when i build code its got ram and flash overflow error this is because below line i think in .map file

 *fill*         0x200004c9 0x200004c7 

which is un wanted.i don't know how it enter in map file.here i attach my project.

I am using the Project/Build Settings dialog to try to add an additional library to my project.  Using the "Additional Libraries" and the "Additional Libraries Directories" tabs does add the items to the linker command but since the directories is added after the library is added it appears as though the library can't be found.  The linker command becomes:

-mcpu=cortex-m0 -mthumb -g -ffunction-sections -O0 -l m -l ..\..\..\Documents\MotionDriver\Arm_Source\libmplmpu -L Generated_Source\PSoC4 -L ..\..\..\Documents\MotionDriver\MPL_Libraries -Wl,-Map,${OutputDir}/${ProjectShortName}.map -T Generated_Source\PSoC4\cm0gcc.ld -specs=nano.specs -Wl,--gc-sections

​But seemingly:  -l ..\..\..\Documents\MotionDriver\Arm_Source\libmplmpu

isn't found because the directory to look in: -L Generated_Source\PSoC4 -L ..\..\..\Documents\MotionDriver\MPL_Libraries

hasn't been added to the path yet.  That's speculation on my part and I'd welcome any feedback on how to accomplish this.  The error that is thrown looks like:

arm-none-eabi-ar.exe: creating .\CortexM0\ARM_GCC_493\Debug\PSoC_4_BLE_MPU_9150.a

arm-none-eabi-gcc.exe -Wl,--start-group -o .\CortexM0\ARM_GCC_493\Debug\PSoC_4_BLE_MPU_9150.elf .\CortexM0\ARM_GCC_493\Debug\data_builder.o .\CortexM0\ARM_GCC_493\Debug\eMPL_outputs.o .\CortexM0\ARM_GCC_493\Debug\hal_outputs.o .\CortexM0\ARM_GCC_493\Debug\inv_mpu.o .\CortexM0\ARM_GCC_493\Debug\inv_mpu_dmp_motion_driver.o .\CortexM0\ARM_GCC_493\Debug\log_stm32.o .\CortexM0\ARM_GCC_493\Debug\message_layer.o .\CortexM0\ARM_GCC_493\Debug\ml_math_func.o .\CortexM0\ARM_GCC_493\Debug\mlmath.o .\CortexM0\ARM_GCC_493\Debug\mpl.o .\CortexM0\ARM_GCC_493\Debug\results_holder.o .\CortexM0\ARM_GCC_493\Debug\start_manager.o .\CortexM0\ARM_GCC_493\Debug\storage_manager.o .\CortexM0\ARM_GCC_493\Debug\uart.o .\CortexM0\ARM_GCC_493\Debug\mpu9150.o .\CortexM0\ARM_GCC_493\Debug\BLEApplication.o .\CortexM0\ARM_GCC_493\Debug\main_original.o .\CortexM0\ARM_GCC_493\Debug\motion_driver_main.o .\CortexM0\ARM_GCC_493\Debug\cymetadata.o .\CortexM0\ARM_GCC_493\Debug\Cm0Start.o .\CortexM0\ARM_GCC_493\Debug\PSoC_4_BLE_MPU_9150.a "C:\Program Files (x86)\Cypress\PSoC Creator\3.3\PSoC Creator\psoc\content\cycomponentlibrary\CyComponentLibrary.cylib\BLE_v1_10\Library\gccCyBLEStack_BLE_SOC_PERIPHERAL.a" "C:\Program Files (x86)\Cypress\PSoC Creator\3.3\PSoC Creator\psoc\content\cycomponentlibrary\CyComponentLibrary.cylib\CortexM0\ARM_GCC_493\Debug\CyComponentLibrary.a" -mcpu=cortex-m0 -mthumb -g -ffunction-sections -O0 -l m -l C:\Users\raypa\Documents\MotionDriver\Arm_Source\liblibmplmpu.a -L Generated_Source\PSoC4 -Wl,-Map,.\CortexM0\ARM_GCC_493\Debug/PSoC_4_BLE_MPU_9150.map -T Generated_Source\PSoC4\cm0gcc.ld -specs=nano.specs -Wl,--gc-sections -Wl,--end-group

ERROR: cannot find -lC:\Users\raypa\Documents\MotionDriver\Arm_Source\liblibmplmpu.a

collect2.exe: error: ld returned 1 exit status

The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.

I am working with the code example project CE210741_UART_Full_Duplex in PSoC Creator 4.0 and it is initially set to compile for a CY8C4245AXI-483. But I would like to change the settings so that I can comple it for a CY8C4247AZI–M485.

Is there any way to make that possible?

When will the USB device and USB host component be supported for the FM0+ by PSOC Creator?

How do other developers create USB enabled devices with the FM0+ uC?

I'm experiencing a problem editing datapath instructions in the UDB editor.  In the Compare Options section of the Configure Instruction dialog box, Option 1 has two choices: Config A and Config B.  Every time I try to choose Config B it accepts my choice.  However, if I try to re-edit the instruction, I find that Option 1 has reverted back to Config A.  This happens every time.

Has anyone else had this problem?  Am I missing something?

Implemented steps shown in AN97060 guidelines for adding an Upgradable Stack OTA Bootloader to my project. 
The Stack and Launcher projects copied to the workspace build with no errors.  When I build my project I get the following error. I have double checked all the steps several times.  Any ideas on what is causing this?   

arm-none-eabi-gcc.exe -c Generated_Source\PSoC4\VC1_PM.c -o .\CortexM0\ARM_GCC_541\Debug\VC1_PM.o -mcpu=cortex-m0 -mthumb -I. -IGenerated_Source\PSoC4 -Wa,-alh=.\CortexM0\ARM_GCC_541\Debug/VC1_PM.lst -g -D DEBUG -Wall -ffunction-sections -ffat-lto-objects -O0
arm-none-eabi-gcc.exe -c Generated_Source\PSoC4\cybootloader.c -o .\CortexM0\ARM_GCC_541\Debug\cybootloader.o -mcpu=cortex-m0 -mthumb -I. -IGenerated_Source\PSoC4 -Wa,-alh=.\CortexM0\ARM_GCC_541\Debug/cybootloader.lst -g -D DEBUG -Wall -ffunction-sections -ffat-lto-objects -O0
arm-none-eabi-gcc.exe -c Generated_Source\PSoC4\Bootloadable.c -o .\CortexM0\ARM_GCC_541\Debug\Bootloadable.o -mcpu=cortex-m0 -mthumb -I. -IGenerated_Source\PSoC4 -Wa,-alh=.\CortexM0\ARM_GCC_541\Debug/Bootloadable.lst -g -D DEBUG -Wall -ffunction-sections -ffat-lto-objects -O0
arm-none-eabi-as.exe -o .\CortexM0\ARM_GCC_541\Debug\CyBootAsmGnu.o Generated_Source\PSoC4\CyBootAsmGnu.s -mcpu=cortex-m0 -mthumb -I. -IGenerated_Source\PSoC4 -alh=.\CortexM0\ARM_GCC_541\Debug/CyBootAsmGnu.lst -g -W

Error: prj.M0266:
      Shared code exported by instance CyBle of component BLE_v3_30 is not identical to code expected by instance BLE of component BLE_v3_30.
     (App=psoc_creator)
--------------- Rebuild Failed: 06/24/2017 01:41:08 ---------------

Hi,

I've been trying to upgrade firmware of my CY8CKIT-044 from 2.12 to 2.18

but somehow I have not been able to do it.

I'm using

CY8CKIT-044,

PSoC Creator v4.0 Update 1

Bridge Control Panel version 1.16.0.2791

PSoC Programmer 3.26.0.2791

on Windows 7 Professional (64bit) with 8.00GB RAM

What I've been trying  is to follow the PSoC 101 Video Tutorial 10. I2C Receive  with CY8CKIT-044.

Previously I had no problem with CY8CKIT-042.

This time, after building/downloading the PSoC program,

I tried to connect it from Bridge Control Panel version 1.16.0.2791

and got following error message

===========
To update your firmware please close Bridge Control Panel and open PSoC Programmer.
Navigate to the Utilities tab and click upgrade firmware.

Failed on Close port!
===========

So I closed the Bridge Control Panel and opened PSoC Programmer 3.26.0.2791

It says 

"KitProg version Expecting 2.18, but found 2.12."

==========
This programmer is currently out of date.

To update the firmware please navigate to the
Utilities Tab and press the Update Firmware
button
==========

So I selected "Utilities" Tab and pushed "Upgrade Firmware" button.

==============
KitProg Version 2.12

Succeeded
Verifying...
Upgrading...
Initializing...
==============

The good news is that the process completed and green "PASS" is displayed.

The bad news is that the firmware version is still 2.12.

Question:

 Would someone teach me how I can update the firmware of CY8CKIT-044 from 2.12 to 2.18? 

Best Regards,

20-Jun-2017

Motoo Tanaka