• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 100 subscribers
  • Views 825 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WinCE6R3 demo NK.bin use with C#

richard neveau
Prodigy 100 points
Other Parts Discussed in Thread: AM3517

As far as I can tell none of the new (or old) demo NK.bin's for AM3517 EVM support code development with C#.  

Looks like the cab file with .NETCF 3.5 update doesn't work when Visual Studio tries to load it and it is not part of the build.  I have Active Sync working and device setup done. Just looks like only C++ development is supported.

1) is this correct or am I making some mistake ?

2) are there any notes (like in user guide) on what catalog items, etc.  are needed to make sure C# code can run on the EVM ?

I'm asking as I have errors when building the AM35x_OSDesign so can't generate my own NK.bin right now and wanted to allow other developers to use some of the AM3517 EVM kits before I figure out the problem with building NK.bin.

  • 0
    TI__Mastermind 44306 points

    Richard,

    I got this to work in the past by adding the .NET compact framework to NK.bin by selecting the appropriate catalog options. The framework is not part of the demo NK.bin as far as I can remember, probably just due to the size. Don't forget we are just providing a BSP and application development and needed resources are a level above that. But that should be generic for any WinCE development.

    I haven't tried the specific .NETCF 3.5 but I assume the provided .CAB files are too device specific and as such don't run on our platforms. That is why you get the whole BSP as source so you are able to build a configuration that suites your needs.

    So I would suggest you fix your NK.bin build issues and then you should be able to add the .NETCF support easily. If not it is a Microsoft issue...

    Regards.

  • 0 in reply to Frank Walzer
    Prodigy 100 points

    Oh I know it's my problem (some sort of variation on a thick head I'm sure).

    I just uninstalled EVERYTHING to start over trying to build my own NK.bin. I was getting  - 1 - error in final result string every time I built it / rebuilt it / cleaned and rebuilt it / kicked PC and rebuilt it - but .err file was empty or unhelpful every time so hope starting over will make it work. I assume others have this working so some problem with my environment.

    Next step will be try a PC not controlled by our IT department so ONLY VS2005 and Platform Builder are installed on fresh XP SP3 load.

    I was hoping I had overlooked some demo I could let others use while I pull my hair out.

     

  • 0 in reply to richard neveau
    Genius 5470 points

    Note, if you want to do C# 3.5 compact framework  "device development" you will probably also want Visual Studio 2008 installed.

    I.E. Visual Studio 2005  ... for CE 6 Platform Builder and Compact Framework 2.0 "device development".

         Visual Studio 2008 ... for Compact Framework 3.5 "device development".

    I know its confusing but it does work. I use CF 3.5 on a 35XX device pretty much everyday.

    If possible, its best to dedicate one development machine with just VS2005 and Platform Builder installed as the "image generation" station and another with VS2008 installed as the "apps" development machine. Both VS2005, VS2008 and platform builder can be installed on the same machine but you have to becarefull of the install order and you can run into some subtle debugging issues that are hard to diagnose if you screw it up.

  • 0 in reply to DavidVescovi
    Prodigy 100 points

     

    Finally got my WinCE NK.bin built by switching to a completly different PC - NOT under control of our IT department - and installing from scratch.

    I got the idea from someone else who had to do the same (switch to a new PC)  to get Platform Builder to work correctly.

    The error we both had was platform builder completed with 1 error but nothing showed up in .err file or on Visual studio output.

    I'm suspecting some evil SW installed by the IT department.

    Since I am building my own NK.bin I just included all the .netcf catalog items so C# development works fine.  Still takes 30 days <g> to build but completes with only warnings and not errors.

    BTW - I had no WinXP machines laying around so got it working on Win7 (32 bit) PC.  Just added the 'Vista' SP1 for VS2005 and run  as administrator. Maybe that's why I still have so many warnings but it works better than my company PC did !

    Thanks for all the suggestions.