LPCXpresso IDEのトピックRe: Plain executable file

Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:46 GMT

Content originally posted in LPCWare by rkiryanov on Sat Dec 12 00:52:25 MST 2009
Hello!

I didn't find options in IDE to generate plain executable files (to upload via UART). Please prompt me, where it is.

Thanks.

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:47 GMT

Content originally posted in LPCWare by CodeRedSupport on Sat Dec 12 07:23:39 MST 2009
I assume you mean a binary file. This is described in the Getting Started.

You select the .axf file in the Prject Explorer, right-click and select Binary Utilities->Create binary

You can change the options used to create the binary file on the Windows->Preferences, LPCXpresso/Utilites preference page,,,,.

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:47 GMT

Content originally posted in LPCWare by CodeRedSupport on Sat Dec 12 10:26:56 MST 2009
There are also some related FAQ entries for this on the Code Red LPCXpresso site.

http://lpcxpresso.code-red-tech.com/LPCXpresso/node/34
http://lpcxpresso.code-red-tech.com/LPCXpresso/node/32

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:48 GMT

Content originally posted in LPCWare by NXP_USA on Sun Dec 13 12:24:26 MST 2009

Quote: rkiryanov
Hello!

I didn't find options in IDE to generate plain executable files (to upload via UART). Please prompt me, where it is.

Thanks.

Hello,

It is possible to generate a .bin file within LPCXpresso today, but it will not have the correct checksum for USB ISP. A command-line program will be distributed with the next version of LPCXpresso (to be released December 15th) which can be set up to post-process the .bin file and add the checksum. In the mean time, it can be done with a .hex editor. Here is a short description of the algorithm which is documented in the LPC1343 User's Manual:

The long integers 0-7 in the binary file must sum to zero. Long int 7 is unused and open for the checksum to be inserted. 2’s complement is pretty standard… I think it is done like so: f[7] = (~(f[0] + f[1] + f[2] + f[3] + f[4] + f[5] + f[6])) + 1;

-NXP

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:49 GMT

Content originally posted in LPCWare by ktownsend on Tue Jan 12 13:10:02 MST 2010
Was this updated in the latest release (and if so what is the command-line utility called)? I'm trying to create a binary file to deploy via the USB bootloader, but every time I deploy it it clearly isn't working. It's rather time consuming to have to manually calculate/edit every time.

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:49 GMT

Content originally posted in LPCWare by NXP_USA on Tue Jan 12 13:25:25 MST 2010

Quote: KTownsend
Was this updated in the latest release (and if so what is the command-line utility called)? I'm trying to create a binary file to deploy via the USB bootloader, but every time I deploy it it clearly isn't working. It's rather time consuming to have to manually calculate/edit every time.

The utility is called Checksum.exe and should be located in C:\nxp\lpcxpresso_3.1\bin. It has one required argument, the path to the binary file to have the checksum inserted. LPCXpresso V3.1 was released December 15th, 2009.

-NXP

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:50 GMT

Content originally posted in LPCWare by ktownsend on Tue Jan 12 14:08:17 MST 2010
Thanks ... I just tested it and it works fine. I'm assuming it doesn't matter what you pass into the -p (processor) argument? I've been supplying lpc1343, but apparently it doesn't really matter. Just curious if I need to provide a different argument for the LPC1114, for example.

Re: Plain executable file

lpcware — Thu, 16 Jun 2016 00:48:50 GMT

Content originally posted in LPCWare by ktownsend on Tue Jan 12 14:10:14 MST 2010

Quote: KTownsend
Thanks ... I just tested it and it works fine. I'm assuming it doesn't matter what you pass into the -p (processor) argument? I've been supplying lpc1343, but apparently it doesn't really matter. Just curious if I need to provide a different argument for the LPC1114, for example.

Or perhaps I'm just trying to be too smart for my own good ... since after two seconds thought this is really only an issue with the USB-enabled LPC1343. :rolleyes:
If anyone wants to automate the binary conversion and checksum update process, here's a simply blog post on adding the appropriate post-build steps: http://www.microbuilder.eu/Blog/10-01-12/Creating_Valid_LPC1343_Binaries_in_LPCXpresso.aspx