PSoC Creator & Designer Software

I'm using Creator 4.4 in a PSoC4 project.
For best size optimization, under "Build Settings" I enabled "Link Time Optimization".
For maximum gain I also added "-fwhole-program" as Custom Flag for both Compiler and Linker.
With the above options there are compilation errors caused by removal of some global symbol.

After debugging I found that the following changes are required into file ".\Generated_Source\PSoC4\Cm0plusStart.c".

//!void Reset(void)
void __attribute__((externally_visible))Reset(void)

//!cyisraddress CyRamVectors[CY_NUM_VECTORS];
cyisraddress __attribute__((externally_visible)) CyRamVectors[CY_NUM_VECTORS];

//!const cyisraddress RomVectors[CY_NUM_ROM_VECTORS] =
const cyisraddress __attribute__((externally_visible)) RomVectors[CY_NUM_ROM_VECTORS] =

The GCC attribute "externally_visible" correctly prevents the optimization on these symbols.
With the above fix I was able to test a working application and save quite Flash space thanks to LTO.

I hope this could be of interest to someone.
I suggest to file an enhancement request so that this fix could be included in a future revision of cy_boot component.

Regards,
Giuliano

Hi All,

I'm working with Creator 4.4 on a bootloader project for PSoC4 (component Bootloader_v1_60)
I experimented that enabling LTO (Link Time Optimization) on bootloader breaks its functionality.
I've done that to save flash space, but BootloaderHost gives error: "The flash row is not valid for the selected array".
I have known this problem since PSoC Creator 3.1.

This time I've spent quite some effort in searching for solutions and directly debugging the code.
I've finally found the reason and a solution that I want to share.

The reason is that one of LTO optimizations is a global constant propagation across all the linked objects.
In case of bootloader, the bad effect is the removal of pointers variables "Bootloader_1_SizeBytesAccess" and "Bootloader_1_ChecksumAccess",  preventing the usage of the correct values for "SizeBytes" and "Checksum".
GCC LTO forced constants because it doesn't know that the values are overwritten by the toolchain directly into HEX file.
Because of this the host command "REPORT_SIZE" always gets "startRow=0x0200", causing the error in BootloaderHost, as the Flash appears already full.

As effective workaround I modified Bootloader_1.h as follows:

//!extern const uint8  CYCODE Bootloader_1_Checksum;
//!extern const uint8  CYCODE  *Bootloader_1_ChecksumAccess;
extern const uint8  CYCODE __attribute__((externally_visible)) Bootloader_1_Checksum;
extern const uint8  CYCODE __attribute__((externally_visible)) *Bootloader_1_ChecksumAccess;

//!extern const uint32 CYCODE Bootloader_1_SizeBytes;
//!extern const uint32 CYCODE *Bootloader_1_SizeBytesAccess;
extern const uint32 CYCODE __attribute__((externally_visible)) Bootloader_1_SizeBytes;
extern const uint32 CYCODE __attribute__((externally_visible)) *Bootloader_1_SizeBytesAccess;

The GCC attribute "externally_visible" correctly prevents the optimization on these symbols.
I tried also the usage of attribute "used", but without success because it is skipped by compiler.

With the above fix I was able to test a working bootloader and save 768 bytes of flash (-16%) thanks to LTO.

I hope this could be of interest to someone.
I suggest to file an enhancement request so that this fix could be included in a future revision of Bootloader component.

Regards,
Giuliano

I'm working on a Bootloader project using PSoC Creator 4.4.
I have a unique workspace for both the bootloader and bootloadable projects.
If I change the workspace configuration from "Debug" to "Release" and viceversa, then the two projects are compiled with that configuration, but...
.... I noted that the "Bootloadable Dependencies" don't automatically adapt to the actual configuration and there is need of manual editing every time.

I tried using a path with variable expansion in the same way as used in "Build Settings" for "Output Directory" of compiler:
${ProjectDir}\${ProcessorType}\${Platform}\${Config}
Unfortunately this doesn't work because the variable expansion is not applied by the building process.

Is there another way?
Is it possible to file an enhancement request in order to support this functionality?

Thanks and Regards,

Giuliano

Hi All,

I'm using PC 4.4 under Windows 10 with a workspace placed in a share folder (filesystem on local network).
In PSOC4 projects I'm experimenting that after a successful "Clean&Build" , if I edit a source file correctly listed in source tree (i.e. main.c) then a following "Build" doesn't regenerate a new linked HEX file.
The same if I edit a source file in "Generated_Source".
The modified source is recompiled, but there is no relinking.
An output message says: "The link step is up to date, no work needs to be done".
I checked that the timestamps of main.c, main.o, main.lst are newer than application .A, .ELF, .MAP, .HEX.
I also tried to force timestamps from cmd shell in several ways, but same result.
If the same workspace is copied into a local folder (C:\...)  it works as expected, with "Build" that regenerates HEX after a source change.

Any idea?

Giuliano

Using  PSoC Creator 4.2 for  the PSoC 5. I am monitoring a thermoelectric cooler (TEC) controller that reports both positive and negative currents and voltages.  As long as everything is positive I'm ok. I'm taking an ascii string representation of hex numbers and converting it to a long that is stored in a uint32. If I get a negative number and apply the following, I always get 0x7FFFFFFF.

h2 is a global uint32 (hex 2 byte)

h2 = strtol(cbuf, (char**)NULL, 16); // create the uint32 from the payload

I'm sure there is an easy way to do this without having to write a bunch of low level code to sort the sign bit, exponent and mantissa.  Should I cast h2 as float  and use atof to convert it? Somebody has surely done this.

Thank you,

Nick

Hi all.

I have a project with BLE v3.66 component built in and I would like to update it to v4.2.

I used automatic update component and the .cysch file already shows the Bluetooth Smart 4.2 symbol.

Is there a way to automatically go from 3.66 to 4.2?

Thanks,

Best regards.

Hi Cypress team,

I use the example project below in PSOC4:
https://github.com/cypresssemiconductorco/PSoC-4-BLE/tree/master/100_Projects_in_100_Days/Day015_Bonding
I made following modifications:
TopDesign > BLEcomponent > GapSettings>Security : 
Security level: set to Unauthenticated pairing with encryption 
I/O capability changed: set to No Input No Output 

With those setting I am having following problem:
When connecting from an Android smart device the pairing pop up appears twice on the Android equipment and I have to validate twice that I accept the pairing.

Please let me know if you have any clue on how to solve this issue.
Thank you,
Regards,
Marlene

I am relatively new to coding and I am trying to write a bus write and bus read function for my BNO055 Sensor. While debugging, I am getting these error codes for my I2CMasterSendStart and I2CMasterWriteByte functions but I don't understand what they mean. Could anyone guide me to understanding these errors and how I should fix them?