**** BEGIN LOGGING AT Wed Feb 09 02:59:57 2011
Feb 09 22:59:52 <Jason_> v0.4 under windows, trying to run flash load_image, getting strange results.
Feb 09 22:59:59 <Jason_> Called through script that used to work under 0.3.1
Feb 09 23:00:08 <Jason_> I note addition of an extra parameter - offset, but it still fails.
Feb 09 23:00:15 <Jason_> response:
Feb 09 23:00:42 <Jason_> auto erase enabled
Feb 09 23:00:43 <Jason_> auto unlock enabled
Feb 09 23:00:43 <Jason_> Command handler execution failed
Feb 09 23:00:43 <Jason_> in procedure 'flash' called at file "command.c", line 650
Feb 09 23:00:43 <Jason_> called at file "command.c", line 361
Feb 09 23:10:37 <roxfan> try to turn on more debugging
Feb 09 23:12:16 <Jason_> did, makes no sense
Feb 09 23:14:03 <Jason_> There is something wrong with the new parser
Feb 09 23:14:28 <Jason_> If i put a full path I get "command hander execution failed"
Feb 09 23:14:44 <Jason_> if I put a filename with no spaces in it I get  error -1401
Feb 09 23:15:12 <Jason_> Historically, if I put quotes round paths, problems with spaces went away.
Feb 09 23:28:13 <Jason_> A little more info:
Feb 09 23:29:11 <Jason_> If I do dump_image q:test.img 0 256 I get a file written correctly (where q is a subst driveletter)
Feb 09 23:30:10 <Jason_> yet it fails if I do flash write_image erase q:test.img 0 hex (where q:test.img is an output file)
Feb 09 23:31:55 <Jason_> ok, if I do flash write with a binary file (the one i just saved)  it works, so it is the intellec hex file format it is having problems with - strange that used to work.
Feb 09 23:34:51 <Jason_> Sussed it!!!   in v<0.4 the format was 'hex', now it's changed to 'ihex' but the instructions have not been updated.
Feb 09 23:37:59 <Jason_> why it could not simply say "bad file type in command", would have saved 4 hours......
**** ENDING LOGGING AT Thu Feb 10 02:59:57 2011