3 replies to this topic

[Spork]

Back in February, Chris announced plans to roll out "Runtime Native Code Interop". I can't find any recent updates on the topic. Anybody know where it's at?

I have an N+ and am unwilling to pay $6000 for a tool like RVDS. If existing methods require the firmware to be rebuilt, I guess that means I'm out of luck. Will "Runtime Native Code Interop" make low-cost native development possible? Are there other, existing, low-cost alternatives?

[CW2]

Are there other, existing, low-cost alternatives?

You can still use GCC to compile the firmware, but you'd need to exclude most of the features so the final binary fits into the flash. The issue is the size of C/C++ Runtime Libraries, namely implementation of s/printf-family functions, it has been discussed for example in Extended GCC Support topic.

Also please note the current Netduino boards do not expose JTAG, so their debugging/troubleshooting capabilities are basically pin toggling and diagnostic messages. To develop a non-trivial firmware feature, you'd probably need a AT91SAM7X development board and JTAG debugger.

[Chris Walker]

Hi Spork, Runtime interop would provide a way to deploy native code with your app instead of building it into the firmware. It would basically be a more limited version of what is already available today...but would make it simpler for non-native-programmers to deploy native+managed code components. As CW2 mentioned, you can use GCC to compile the firmware today and integrate your own native code features. The one limitation is that the lwIP networking stack is a bit big...so you may need the optimized Keil/RVDS compiler if you want to include all the features we currently include in the firmware and still make everything fit on a Netduino Plus. Chris

[Spork]

Maybe I'll just pick up a regular N for this custom firmware project and leave my N+ the way it is. The project will probably use Bluetooth (BlueSMiRF) for comm, so I won't need the networking stack. GCC still produces 4.2 firmware that will fit on the regular N, right? Chris: Can you comment on where runtime interop fits into the Netduino development road map? Has anything happened since you first talked about it in February?