I forgot to mention that the code used to read the RTC is the sample code of the I2Cm datasheet.
I have a project that is close to the 32K FLASH limit, and can no longer debug it with ICE
Cube, it returns crazy values when debugging. Code still seems to run fine, just cannot
debug. Ii is at ~ 30.5K this happens.
I am not using I2C or BL however.
Do you know what is the cause? Would it be a stack overflow or a compiler problem? Did you dig to find out was the cause?
I experieced weird things with the ICECUBE and low flash space too!
Another thing you might look into is your stack usage. If you are using Flashwrites and a 256B RAM type, make sure the stack never gets higher as 0xF7 (the SSC parameter block is located at 0xF8). Test your RAM usage by filling the complete RAM with for example 0x5A and halt your debugger to see how much ram is used.
I succeeded to fix the problem with the help of cypress support. My problem was the drive mode of the I2C pin. I used a line in my program to alter the drive mode to High Z as expected by the user module. Unfortunately for me this line caused I2C reset. Thanks for your help.
I just have to make sure that when I put back the BootLdrI2C UM, I reajust the drive mode to high Z in the pinout editor and everything will be fine.