[SOLVED] J-Link error when downloading "Could not save file [Sample_DebugFlash.jlink]"

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] J-Link error when downloading "Could not save file [Sample_DebugFlash.jlink]"

    Since updating my J-Link to v6.00f, I have noticed that every time I download to a device using J-Flash Lite, the Log window reports an error that "Could not save file [Sample_DebugFlash.jlink]. Access is denied". It continues on to download to the devices (Kinetis KL series), but then reports the programming failed (even though it appears to have successfully flashed the device, since it will then run normally).

    Has anyone else noticed this ?

  • I've updated to J-Flash 6.00g and the error remains. It occurs with multiple targets (eg Kinetis Freedom devices as well as custom bare-metal boards) and . No one else has seen this, or has suggestions for a fix ?
  • I updated to the latest J-Flash 6.00h in the hope that it would resolve the issue, but it didn't.

    I did however work out a fix.

    Given it was reporting an "Access is denied" error, I tried running J-Flash as administrator. Sure enough, the error went away. I was also then able to run J-Flash as non-administrator and the error did not re-appear so it appears to be a permanent fix.

    I also noticed that there is now a file called "Sample_DebugFlash.jlink" in the C:\Program Files (x86)\Segger\JLink_V600h directory, with a creation timestamp matching when I ran J-Flash as admin. I had searched for this file before and didn't find it. Why this file needed to be saved, and why it couldn't when run as non-admin, I cannot say.

    Hopefully this will help anyone having this issue.
  • Hi,

    Currently, J-Flash lite tries to create a settings file which may fail if admin rights are required to create the file in the active working directory. We will change this in the next version, planned to be available during this week.

    Regarding your work-around:
    Once the file is present, J-Flash lite uses it and does not longer try to create a new one and therefore does not output any errors.

    Best regards
    Erik
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.