Jump to content

Embedded Development


SteveG50

Recommended Posts

Looking for any experiences with the new Embedded Development Module to a non-NI target board/processor, such as an Intel-based PC/104 board. Is there anybody out there doing this? If so, what is your take on the process of configuring your "tool chain" (compiler, target O/S, target processor and drivers)? Also, any other ideas or feedback?

Link to comment
Looking for any experiences with the new Embedded Development Module to a non-NI target board/processor, such as an Intel-based PC/104 board. Is there anybody out there doing this? If so, what is your take on the process of configuring your "tool chain" (compiler, target O/S, target processor and drivers)? Also, any other ideas or feedback?

You are not very specific. With Intel based do you mean some Pentium CPU board or an Intel ARM CPU? In the first case you would just install normal LabVIEW.

I have looked into the Embedded developer module but haven't found time to really do anything with it yet. It definitely is not just doing one day of work to support a new target. Even if you can use an existing target and adapt it to your new one (depends of course both on the CPU as on the actual OS you will use) can you expect to spend at least a week or more before you get your first VIs properly downloaded and running. For an entirely new target I would guess this can take easily months depending on your familiarity with the actual tool chain you need to use for that target.

Rolf Kalbermatter

Link to comment
You are not very specific. With Intel based do you mean some Pentium CPU board or an Intel ARM CPU? In the first case you would just install normal LabVIEW.

We would like to use enough processing power to run our app, but not much more, in order to keep the heat down. However, we do like to have a math coprocessor. An Intel '486 might do the job, with an inexpensive and simple ROM DOS. We've used a Pentium for something similar, but many of the single board computer mfrs tend to ratchet up the performance (most people want this) and you get a lot more heat.

I agree it could take months, but we've used the "tool chain" before while doing the line-by-line coding method of software development. We were hoping that experience would help streamline the initial development of the "tool chain"

Steve G.

Link to comment
  • 2 weeks later...
I agree it could take months, but we've used the "tool chain" before while doing the line-by-line coding method of software development. We were hoping that experience would help streamline the initial development of the "tool chain"

Steve G.

The more experience you have with the existing C based tool chain, the easier the port. The Embedded module has some good examples that might match what you need.

It also depends upon the functionality you want exposed that is particular to your target.

-erik

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.