richhas

Hi all,

Swapping back in an N+2 project from months ago...

Can someone tell me if remote debugging via VS of N+2 apps is possible over a tcp/ip network?

Thanks,

Rich

Dear SL folks,

Background: I have spent a good deal of time messing around with various GCC versions and trying to get clean 4.2 PK builds with SL's corresponding FW bits. I'm building a custom lighting and controls system around extended I2c buses and such and attempting to use ND2+ as part of this system - I must be able to debug, support, and extend the native bits that SL ships.

I'm currently using CooCox (CoIDE), GCC 4.8.3,  ST-LinkV2 under windows 7 64-bit as a dev env. All this works great for bottoms up native dev just using the various ARM CMCIS-based sources and my code. The problem is of course when I want to pull in the NETMF PK work. It is a tangled mess because of the of all the various runtime targets and compilers that MS and the NETMF community are trying to support - all understood. But here I am just trying to focus on your product and my application of it and I must try and sort out all this PK and tool chain stuff. Can something better be done...

A few questions and then a suggestion...

1) Does SL verify/test their released (firmware) extensions to the PK with a given GCC tool chain?

2) Do you prescribe a workable version of a GCC tool chain?

3) If you do either, could you freeze a workable tool set when you guys ship new bits that will 100% work and build the PK+your bits? IOWs consider this aspect as part of your product.

4) Can you tell us exactly what your internal tools chain is that you guys use?

And now a suggestion...

A profiled down PK+SL set of bits and build-ware as a supported "product" is worth some money - I would have spent a couple hundred just for the SL-guarantee. Such a hassle-free NetPK-SL package would be very useful and would go a long way in opening up your products to much deeper application IMHO.

Just some thoughts... And I've been a fan for several years and own many of your boards.

If I could figure out how to send a PM to Chris, I would have done that. A bit new to the forum.

Thanks,

Richard Hasha

(richhasha@gmail.com; richhas@microsoft.com)