One Cypress emplyee mentioned a problem with PSoC5 compiler issue.
Could Cypress engineer confirm this?
Whip up a test case in PSOC Crator, this should take 5 minutes, just
a thought. Creator and all modern tools allow for quick test case creation,
and this is not a HW issue meaking it even easier.
I did not have THAT problem, so could not submit a case.
It is just that we are going to release a product using PSoC5 when a Cypress employee claiming a fault of the compilier.
While I think it is most likely a user's issue, I would like to know if Cypress knew of such case.
Apologize for not clarifying things here earlier. You have nothing to worry about PSoC 5 compiler. Later figured out that I was doing something wrong in my code . I was doing some wrong arithmetic operations on the array pointer for accessing the array elements which ended up in accessing memory locations beyond the array boundary. Bottom line - Take special care while dealing with pointers in your code!!