We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I use an Infineon C165-LM with an external Flash (AM29F200BB) and I had a project which worked with uVision1. I imported it into uVision2 (version 2.38) and I checked the target options (C166, L166 and A166) like on uVision1 but my program doesn't work the same way : my part concerning the save of information in the Flash doesn't work any more : the information are wrong after switching my device off although all was ok with uV1. So are there some options in uV2 which add something in comparison to uV1 that I don't know ? Thank you for helping me.
If your flash write routine uses software timing tricks these could have been screwed up by newer and better compiler optimisation? Stefan
To avoid some possible confusion about Stefan's reply: what he's hinting at is that the problems are most likely to be with the newer compiler version you'll be using now, not with uVision itself.
That's still a bit confusing: I mean to say that the newer compiler may do a better job of optimising some of your timing critical code thereby changing the timing, rather than implying that there is anything *wrong* with the compiler. Stefan
He probably just meant that the problems may be due to the new compiler having (slightly) different behaviour, rather than the new compiler itself actually having problems?
"He probably just meant that the problems may be due to the new compiler having (slightly) different behaviour, rather than the new compiler itself actually having problems?" Speaking on behalf of everybody in this thread: Yes. Stefan