Recent Posts

Pages: [1] 2 3 ... 10
1
General Discussion / Re: Starting FlashMagic 12.70 by double-clicking .fmx-file
« Last post by Andy Ayre on January 24, 2020, 12:20:21 pm »
This is fixed in version 12.75.

Andy
2
General Discussion / Re: Starting FlashMagic 12.70 by double-clicking .fmx-file
« Last post by Andy Ayre on January 17, 2020, 09:22:42 am »
Thanks for reporting this - we will look into it. Andy
3
General Discussion / Starting FlashMagic 12.70 by double-clicking .fmx-file
« Last post by Werner on January 16, 2020, 03:18:11 am »
Hi,

When I start FlashMagic by double-clicking an .fmx-file a message comes up ("The project has been modified. Do you want to save it?"). I have to click "No", then the settings of the double-clicked .fmx-file are loaded. Is this the wanted behavior of FlashMagic? Older versions of FlashMagic worked well by double-clicking the old .fms-file.

Best regards
Werner
4
General / Re: Parentheses in path for command-line execution
« Last post by FlashMagicUser on May 07, 2019, 07:47:43 am »
Thank you for your answers.

Is it possible to export the command line directive from GUI V12?
5
General / Re: Parentheses in path for command-line execution
« Last post by Andy Ayre on May 07, 2019, 07:29:27 am »
Parentheses are not allowed inside path names. Page 57 of the manual lists what is allowed. The V12 command line is all-new and doesn't have this restriction.

Andy
6
General / Re: Parentheses in path for command-line execution
« Last post by FlashMagicUser on May 07, 2019, 07:24:30 am »
This is the entire command line directive:
Code: [Select]
COM(6, 115200)
DEVICE(LPC2368, 4.000000, 0)
HARDWARE(BOOTEXEC, 50, 100)
ERASE(DEVICE, PROTECTISP)
HEXFILE(C:\Program Files (x86)\My Company\My Software\myfile.hex, NOCHECKSUMS, NOFILL, PROTECTISP)

Just to clarify: this is the exact same string I get if I export Command Line Directive from the Flash Magic GUI software.
Just to clarify more: if I use any other path without parentheses (even with spaces, but no parentheses), the command executes fine.
7
General / Re: Parentheses in path for command-line execution
« Last post by Andy Ayre on May 07, 2019, 07:16:11 am »
Please post the entire HEXFILE directive you are using.

Andy
8
General / Re: Parentheses in path for command-line execution
« Last post by FlashMagicUser on May 07, 2019, 07:08:37 am »
Oh, the irony.
I setup via GUI my desired function and it works fine.
But if I export the command line directives, I see that the string is exactly the same  as the one that gives me the error.
9
General / Re: Parentheses in path for command-line execution
« Last post by Andy Ayre on May 07, 2019, 06:39:10 am »
Export the command line directives from the GUI version (File menu). That will show you the valid syntax.

Andy
10
General / Re: Parentheses in path for command-line execution
« Last post by FlashMagicUser on May 07, 2019, 06:30:55 am »
I already tried with
  • Double slashes
  • Quotes around the path
  • Double quotes around the path
  • Replacing spaces with slashes (i.e.: "C:\Program\Files\(x86)\...")
And I always get the same error.


I also just noticed that I get the error:
Code: [Select]
ERROR: Invalid parameters for HEXFILE directive: HEXFILE(C:\Program
Files
(x86)

But the exit code is
Code: [Select]
0
It would be great if we could at least catch the error via exit code.
Pages: [1] 2 3 ... 10