Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - kena

#1
Hi Andy,

It was my error. The command line I was using was _not_ the same as the one generated by the GUI via "save directives", as you were hinting. "Fill unused flash" was not selected in the GUI but in my command line version I was specifying 'FILL'. So it was

FM COM(3, 57600) DEVICE(LPC1788, 0.000000, 0) HARDWARE(BOOTEXEC, 50, 100) ERASE(DEVICE, PROTECTISP) HEXFILE(test.hex, NOCHECKSUMS, FILL, PROTECTISP)

versus

FM COM(3, 57600) DEVICE(LPC1788, 0.000000, 0) HARDWARE(BOOTEXEC, 50, 100) ERASE(DEVICE, PROTECTISP) HEXFILE(test.hex, NOCHECKSUMS, NOFILL, PROTECTISP)

Sorry for the confusion, and thanks for the help.

KenA

#2
The difference was 'FILL' vs 'NOFILL' :-)

Thanks Andy!
#3
Hi,

I am using both the GUI and command line to upload a hex file. To attempt to ensure both operations are the same I use the 'File->Save Command Line Directives' command. The command line is:

FM "COM(3, 57600) DEVICE(LPC1788, 0.0, 0) HARDWARE(BOOTEXEC, 50, 100) ERASE(DEVICE, NOPROTECTISP) HEXFILE(test.hex, NOCHECKSUMS, FILL, NOPROTECTISP)"

Using the GUI the operation takes about 1 minute. Using the command line it takes 6.5 minutes.

Is there any explanation for the difference? Why is the command line version so slow?

Thanks,

KenA