16 replies to this topic

[seascan]

Hi. I saw the advertisement for the NetDuino in Make magazine and started to look into it. I was hooked when I saw that VB.NET is supported! I have VB Express 2010 installed. I downloaded and installed the 4.2 .NetMicroFramework RTM and the NetDuino SDK. Unlike C#, when I load VB I do not see a option for a .NetMicro Application. I can reference Microsoft.SPOT but not Microsoft.SPOT.Hardware (as I have seen in some online examples). I tried doing a console app and referencing Microsoft.SPOT but, I do not see the option to set the complitation to target an emulator or hardware. Am I missing something fundamental? I am going to order a netduino board later today... is it a problem to not have the board connected when developing? Thanks! terry

[Thonord]

Hi. I saw the advertisement for the NetDuino in Make magazine and started to look into it. I was hooked when I saw that VB.NET is supported!

Me too:) Sorry, unfortunately I have no answers - just questions. I have not yet received my Netduino board, so I thought i'd give the samples a try and use the emulator.
Everthing works according to the book until "F5" and then the exceptions "roll" inn. I'm using VB2010 Express.

I am not trying to hijack this thread. I just didn't see any reason to open a new one.

Tom

[seascan]

Hi. I saw the advertisement for the NetDuino in Make magazine and started to look into it. I was hooked when I saw that VB.NET is supported!

I have VB Express 2010 installed. I downloaded and installed the 4.2 .NetMicroFramework RTM and the NetDuino SDK.

Unlike C#, when I load VB I do not see a option for a .NetMicro Application. I can reference Microsoft.SPOT but not Microsoft.SPOT.Hardware (as I have seen in some online examples).

I tried doing a console app and referencing Microsoft.SPOT but, I do not see the option to set the complitation to target an emulator or hardware.

Am I missing something fundamental?

I am going to order a netduino board later today... is it a problem to not have the board connected when developing?


Thanks!
terry

Has anyone else seen this problem?

[MDalton]

Did you install the netduino SDK and the MicroFramework? http://www.netduino.com/downloads/ If you're using VB make sure to use the 4.2v MicroFramework http://forums.netdui...?showtopic=2769 And update the firmware http://wiki.netduino...ep-by-step.ashx I think that is all.

[MDalton]

Actually, I can't find VB template either. C# ones worked though..

[MDalton]

Sorry I can't edit my posts because I don't have enough posts. If you install the beta netduino SDK you should get the VB templates http://forums.netdui...mework-v42-sdk/ 1st heading link 2.

[seascan]

Great Call! Now (using NetDuino 4.2) I have the templates. I just received my first NetDuino Plus... Early Christmas present to myself. I am trying the Blinky program but am getting the following: Error 1 Cannot deploy the base assembly 'mscorlib', or any of his satellite assemblies, to device - USB:NetduinoPlus twice. Assembly 'mscorlib' on the device has version 4.1.2821.0, while the program is trying to deploy version 4.2.0.0 Any ideas how I can install the newer mscorlib?

[Stefan]

Any ideas how I can install the newer mscorlib?

Hi Seascan!

You need to upgrade to 4.2. This requires two parts:
- Update the TinyBooterDecompressor
- Update the firmware

[seascan]

Thanks Stefan: Blinky Works!! I did upgrade to Visual Studio Professional last week so I am unsure if my original issues with VB express are fixed... But, I am very happy that I am able to get my "Hello World" program working. IT IS ALIVE.

[seascan]

Stefan, I should have mentioned: I started to upgrade the firmware before I saw your post. I did NOT do the TinyBootDecompressor... everything seems to be working fine. Is this okay?

[Stefan]

Stefan,

I should have mentioned: I started to upgrade the firmware before I saw your post. I did NOT do the TinyBootDecompressor... everything seems to be working fine. Is this okay?

Hmm it could work, but I believe there were some changes in the TinyBootDecompressor as well. So if you encounter any problem, try upgrading it as well

[seascan]

Hmm it could work, but I believe there were some changes in the TinyBootDecompressor as well. So if you encounter any problem, try upgrading it as well

What exactly is the TinyBootDecompressor? What does it do?

Thanks,
Terry

[seascan]

Stefan, I noticed in the tutorial for the TinyBootDecompressor calls for a hardware reset using 3.3V but the picture shows using the /Reset pin... Does it matter which pin? Also, do I need as external power supply when doing a deep reset or can I use the USB? The reason I ask is that the tutorial mentions connecting to the PC AFTER the reset. Thanks Again, Terry

[Stefan]

What exactly is the TinyBootDecompressor? What does it do?

If I'm correct it's a boot loader, not much different from the MBR on a PC. I'm no expert on that though, so I could be wrong.

[Stefan]

I noticed in the tutorial for the TinyBootDecompressor calls for a hardware reset using 3.3V but the picture shows using the /Reset pin... Does it matter which pin?

It must be the 3V3 pin. I looked at the pictures again and I've put it in 3V3.

Also, do I need as external power supply when doing a deep reset or can I use the USB? The reason I ask is that the tutorial mentions connecting to the PC AFTER the reset.

You can do it on USB power, just make sure you unplug/plug it back in after reset, so the PC detects the right device driver.

[seascan]

It must be the 3V3 pin. I looked at the pictures again and I've put it in 3V3.

It was the angle that threw me... I counted the ports and it was on the 3.3!

[CW2]

If I'm correct it's a boot loader

Yes. On devices with small memory, such as Netduino, the actual bootloader TinyBooter is compressed and included in TinyBooterDecompressor, to save space. TinyBooterDecompressor is executed after power up or reset, decompresses TinyBooter into RAM (hence the name) and executes it. TinyBooter checks the state of the on-board switch to determine whether to stay in 'boot mode' used to flash the firmware, or to execute TinyCLR (the .NET runtime), which in turn searches for an application and executes it, if found.