• State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 22 subscribers
  • Views 6313 views
  • Users 0 members are here
Options
Related
How was your experience today?
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

Keil error filename.axf, cannot find path, echo off

sok tafel

When I click on build I get the following error:

C:\Users....STM32F4x>echo off The system cannot find the given path "..... filename.axf" Target not created

In the Output tab of Options for Target I have checked the boxes 1. Debug information 2. Create HEX file 3. Browse information

What is the problem here?

  • 0

    The project may have a user command before project is even built that has a path to a *.axf file that has not been created yet. This happens after a call to "echo off" in the command line or in a batch file.
    Check Options for Target (magic blue wand) => User tab => Before Compile... => Run...

    The *.axf file is generated after a successful build process.

    What is the full build output from the IDE?
    Are you looking at an example?

  • 0 in reply to Zack Havens

    Run 'After-Build' Conditionally is unchecked, I also tried checking that box and building it again.

    Build target 'BLDC_F401RE_USART'
    Before Build - User command #1: .\Common\buildsteps.bat 0
    C:\Users\PersonalComputer\Desktop\uVision5\STM32F4x>echo off
    Het systeem kan het opgegeven pad niet vinden.
    ".\Demo\BLDC.axf" - 1 Error(s), 0 Warning(s).
    Target not created.
    Build Time Elapsed: 00:00:00

    Hope you can help me out.

  • 0 in reply to sok tafel

    *Before-Build*, the script here doesn't appear to be functioning correctly, you'll need to look at what the batch file is doing, and where it fails. You could start by not turning the echo off, so you can see the progress.

    The error suggests there is an expectation for other tools/application to have been installed, either at specific paths, or findable via the PATH environment variable.

    Review the installation notes or read me file associated with the project.

  • 0 in reply to sok tafel

    Hello sok,

    The batch file, ".\Common\buildsteps.bat", runs before the automated build. It may contain an invalid path. You can "follow the error" and check if it contains valid paths.

    It looks like the project might be trying to run two separate, sequential builds.

    I recommend starting without a batch file, especially if this is your first project.
    You can later use "Create Batch File" to automatically generate a batch file, by enabling it in Options for Target => Output tab. The user should either use a build button or use a batch file to start the build, but they probably don't want to do both.

    Thanks,
    Zack