Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.

kiwi65

Member Since 11 Sep 2014
Offline Last Active Jun 03 2016 12:50 AM
-----

Topics I've Started

NetMF 4.2 and PKI

19 July 2015 - 08:07 AM

Has anyone had experience/success getting PKI encryption working on a Mini? 

 

It seems like the Mini's version of NetMF has classes like 'System.Security.Cryptography.X509Certificates.X509Certificate2' and 'Microsoft.SPOT.Cryptoki.Session' pretty much stubbed out.

 

Any time these are invoked they generate:

 

An unhandled exception of type 'System.NotSupportedException' occurred in Microsoft.SPOT.Security.PKCS11.dll

 

Any takes? Any example code?

 

Thanks in advance :)


Netduino Mini not playing nicely with SAM-BA 2.15

09 April 2015 - 07:54 AM

Ive run into a wall attempting to upgrade my Netduino Mini from NetMF 4.1 to 4.2.

 

I've learned that the bootloader will need to be updated before upgrading from NetMF 4.1. I learned Ill need to use SAM-BA to install the bootloader, and I can only flash the Mini over its RS232 serial interface (not its TTL interface)

 

The theorys great, but things seem to come unstuck for me when I try to use SAM-BA.

 

I followed these setup steps:

  1. Completely reset the Mini with 5v to the tiny reset pad for ~1 second. 
     
  2. My laptop does not have native serial RS232 so Ive set up for the bootloader flash with a USB->RS232 FTDI breakout board. Board RX connected to Mini TX. Board TX connected to Mini RX. Board Gnd connected to Mini Gnd. My setup looks pin perfect to Frodes.
     
  3. Powered up the Mini with 9v to pin24 and Gnd to pin23. The obligatory breadboard LED glows to confirm that I had indeed provided power to the device
     
  4. Checked all the COM settings were good, 115200 8 N 1
     
  5. Run SAM-BA 2.15, selected the FTDI-presented COM port (the only COM port listed), selected AT91SAM7X512-EK, and hit Connect

Theres a flurry of TX/RX traffic on the FTDI LEDs and then SAM-BA returns a dialog titled Invalid Chip ID. I get the same dialog when any AT91 device is selected in step 5.

 

Thinking that my Mini could be dead, I lifted it from the ZIF socket and tried again checking the RX/TX LEDs. This time there was no RX traffic, which Ive interpreted as meaning the Mini is alive and can respond to SAM-BA when I click the Connect button.

 

Ive googled until Chrome shows every  relevant link in purple (been there, read that!).. so now Im kinda stuck.

 

Id be stoked to hear anyones wisdom on this topic. Thanks in advance!


Netduino 2 and Dfrobot GSM/GPS Shield

11 September 2014 - 02:59 AM

Greetings! This is my first post here, and as a Netduino newbie I'm looking forward to learning and sharing.

I'm working on a Netduino project which includes a Dfrobot GSM/GPS shield. I've completed the obligatory 'blinky' application and can edit and deploy code successfully from Visual Studio across the USB cable to my Netduino 2.

 

I've now added the the GSM/GPS shield, and have hit a wall. Specifically, I'd like to use a Windows 8 terminal program to send AT commands to the GSM/GPS shield via the Netduino 2, but there are no COM ports (physical or virtual) showing in Windows Device Manager, so none of the terminal programs work.

 

Can the PC->Netduino USB connection be used for serial comms to the shield, or do I need a FTDI Serial 232 USB Cable to wire directly onto the shield? Is there a better way to accomplish this?

 

Of course, in time the Netduino application will be sending the AT commands to the dfrobot shield, but for now I'd like to 'play' a bit using a terminal program

 

Any help/suggestions gratefully received.

 

Attached File  Netduino2.JPG   104.38KB   1 downloads


home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.