This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Same Keil version, different output files

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?

Parents
  • 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

Reply
  • 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

Children
  • "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"

    I tried it out, doesn't work :(