Hi everybody, We have a big problem with the MDK 4.60 version. Having the same Keil version, same project, files, libraries etc... Keil generates different output files for programming the STM32F417 on two different computers.
This wouldn't be a problem, but one output file causes fault work of the uC - the UART isn't working. What could be the cause of this problem? Any suggestions?
This is one scenario where Makefile-based build system is superior to an IDE: you have complete trasparency regarding build tool settings.
How do you know the build images are different? Maybe the JTAG programmer has problems on different machines.
I compared the output hex files and the map files. My "Options for Target" are the same! Where are the deep settings?
"This is one scenario where Makefile-based build system is superior to an IDE: you have complete transparency regarding build tool settings." - Is there any workaround in this situation?
Is it possible that KEIL was not installed completely correct and this causes the problem?
Actually you can use one IDE for several compiler variants. Check also Components, Environment and Books settings on both computers.
Components, Environment and Books are also the same. Can I change the compiler just copying the .exe to the keil/ARM/ARMCC folder?
I seem to remember that the Watcom compiler would limit the extent of some optimizations depending on the amount of memory available. I doubt RealView tools would do the same, though. Why don't you use a tool like WinMerge to compare build folders on the two machines? By the way, make sure you don't embed build time into the image (through the use of __TIME__ or similar).
Thanks, I'll try it with WinMerge! Also no __TIME__.
a quick check would be if both versions of the code run as expected
I have had similar after updating the IDE e.g compile debug the system then update the Keil tool then rebuild and the embedded system does not run as expected.
remove all the IDE files apart from the uvision project file. remove all the output files
reset the flash programming algorithums in the debugging tab rebuild and reprogram the embedded system and the thing works as expected.
works for me and I do this as standard now whenever the tool is updated
"a quick check would be if both versions of the code run as expected
works for me and I do this as standard now whenever the tool is updated"
I tried it out, doesn't work :(
View all questions in Keil forum