I'm having message Executable_1.hzx does not exist

Comments

3 comments

  • Avatar
    Jon Elliott

    I get the same behaviour after using v3.2 and then going back to v3.0.

    It looks like there is an incompatibility with the environment settings between the two versions - after clicking Tools > Admin > Restore Default Environment Settings... in v3.0, the build works again.

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    The problem is that v3.2 is changing the Building > Parallel Building Threads environment option from it's v3.0 default value of 6 to 0 (0 means detect the number of threads in v3.2 but has the effect making the build doing nothing on v3.0).

    Changing the Building > Parallel Building Threads environment option back to it's default value of 6 in v3.0 fixes the problem.

    0
    Comment actions Permalink
  • Avatar
    Abner Barros

    Thanks for your imediately answer.

    We decided to upgrade to version 3.2 windows x86 because we realized that it still supports this microcontroller.

     
    0
    Comment actions Permalink

Please sign in to leave a comment.