ARM9 based dev board for LabVIEW?

[Ho Nam]

Hi Micheal,

I just read your post about BSP required. Can you tell me which specific features the BSP should include in order to make a proper LabVIEW embedded target?

I was looking at a Jennic wireless network microcontroller (JN-5139R1). Jennic provides a simple scheduler called BOS and a Zigbee stack.

From their manual,

"The BOS is a simple task scheduler.  It is not pre-emptive - tasks run until complete
and each task has the same level of priority.  The lack of context switching between
tasks removes the need for individual stacks and saves on memory space.  
Event mechanisms are provided to allow communication between tasks.  The
passing of data between tasks is achieved using a simple messaging mechanism."  

I found that this scheduler does not provide mutex, semaphore functionality etc. Does it mean that this chip is not a good LabVIEW Embedded target?

Regards,

Ho Nam

[Michael.Phillips]

Hi Ho Nam,

This is a good question: How much OS functionality does the LabVIEW C Generator need? The answer depends on how much LabVIEW functionality you want, and how much you are willing to work with the LabVIEW runtime library to make it work with your OS. 

For seamless integration with LabVIEW (support of all LabVIEW features), your operating system needs to provide access to the following features:

• Prioritized pre-emptive multitasking thread scheduler
• Semaphores
• Critical Sections
• OS Wait (ms)
• OS timer access (ms resolution)
• Allocator
• Atomic compare and exchange instruction

If your operating system lacks one of these features, it cannot fully support LabVIEW. There are caveats to that statement, so let me know if you have an OS that fulfills most of these and I will let you know what effect it might have. Based on what you said about the BOS, I do not think it would be a good fit for LabVIEW.