Specifying binary start address with CF Flasher when using command line mode

[armistej]

Hi

Using the latest CF Flasher 3.1.6 (which in the Help still says is version 3.1.5), I am trying to program my EVB from a CMD prompt / BAT file.

I can specify everything using CFFLASHER.EXE command line options, except the start address for the BIN file.

This seems to be completely missing from the command line help, i.e. CFFLASHER -h

If this is truly missing, can it be added to CFFLASHER's enhancement request list ?  Then, the Windows GUI functionality and the command line functionality would be equivalent.

If it's not missing, can someone explain how to do this ?

For various reasons, my toolchain is developing BIN files and not S19 files.  I would prefer not to have to change this behaviour.

Regards

Jason

[Joe_LMI]

Hi,

    I have been trying to get CF FLASHER to work from the command line as well.  I was able to determine the undocument command for the starting address of a binary file is -start   followed by the address as 8 hexadecimal characters such as "-start FE000000".

    I believe this works since I can see it show up in the echoing of the progress, however I have not been able to program flash from the command line. I keep getting a timeout error.  I have been able to erase it only if I run the Windows IDE of CFFLASHER first and perform some operation. After that I can run a command line erase operation but not a program operation. 

   I am using CF Flasher V-3.1.8. and a parallel port P&E BDM.

   If any body has any hints I would like to hear them.

   Thanks.

Joe

[RufusVS]

Over 2 years later and this is still a problem.

I can't get it to program from the command line either.

[armistej]

I agree with you RufusVS !

This is not a very difficult programming task.  It makes me wonder if anyone from the CF Flasher support team views these forums or not.  I'd be embarassed to have his issue in an "open" state for so long !

Maybe Freescale should just make CF Flasher an Open Source tool, and let the ColdFire user community provide the fix ?