How to CreateHexFile?

[rales]

How do you configure LabVIEW Embedded for ARM to generate an Intel Hex file?

There is a CreateHexFile variable in the LABVIEW.uvprog file in the ..\Project directory.  I suspect this needs to be set from a "0" to something else?  When it is turned on, where is the .hex file saved? 

Thanks,

Rick

[rales]

Can I add a command in the "Extra Linker flags" textbox under Advanced Compling Options of the Build Specification?

Thanks,

Rick

[G-Money]

rales,

       The LabVIEW Embedded interface compiles the LabVIEW code into an efficient C code and then manipulates the MicroVision software at a low level to deploy the code. You could use MicroVision to create the Hex code yourself by point the the C code that is generated after you select "Build" in your project, but this is something that National Instruments would not support. The Embedded Module Interface was developed in conjunction with Keil to create and deploy the most efficient code with the least amount of user work. You could definitely do this yourself but you would have to consult the Keil support files to find out more information. 

       As far as the Extra Linker Flags in the Build Properties, consult the Embedded Help (http://zone.ni.com/reference/en-XX/help/372459A-01/lvarmdialog/arm_build_spec_adv_db/).

Please let me know if there is anything else I can help with. Thanks!!

[rales]

Grant your answer was of NO help.

Let me ask the question another way.  How do you propose to field program a product that was developed using LV Embedded?    The answer can not be: "Send a Kiel ULink 2 and LV Embedded licnese to every service tech?"  Is there a reference that describes how to distribute code somewhere?  I could not find one?  One might want to do this over, USB, a COMM port or maybe even the Internet?

The obvious answer is distribute a hex file with a flash download application, ie Flash Magic which is supported by Kiel.  What I need to accomplish this most basic task is to get the LV development tool to create the hex file (Intel, S-record other, does't matter).  In the LABVIEW.proj file there is a CreateHexFile variable that is set to 0.  Would it be this variable would cause the Kiel linker to produce the hex file if it were enabled?  If so what is the appropriate setting.

Thanks,

Rick

[NicB]

Are you looking for this?

Just check it!

Message Edited by NicB on 02-19-2010 02:03 PM

[G-Money]

Rick,

          Please remember that this is a community. We will try our best to help but if our answers are of no help then please help us by steering us in the right direction. 

Message Edited by G-Money on 02-19-2010 02:02 PM

[G-Money]

Rick,

         I had this exact issue last July and the answer I got from our R&D developers was that it wasn't supported. I will ask again to see if things have changed but in the mean time mabye NicB can say where that options window is located? 

[NicB]

I'm sure rales is able to find it.

[G-Money]

Thanks Nick!! You're the man!! Have a great weekend!!

[rales · Accepted solution]

Found it!