MarkNic

Over in the Netduino/N2 forum several of us have been trying to get an Adafruit NFC shield working with Netduino using I2C.  After a lot of iterations it looks like there was success getting it working on a N+ board.  I, however, have a N+2 and cannot get the same source code to work (after changes made to reference the appropriate Netduino base assembly).

 

The other thread is @: http://forums.netdui...uit-nfc-shield/

 

We're hoping someone can provide some insight as to why the I2C code will work on the N+ board but not on the N+2.

 

Any help would be appreciated,

 

Mark

I'm creating a fairly complex application using multiple classes to describe objects that I'm controlling through Netduino.  When you create public/private/static fields or properties that are input or output ports and hit a breakpoint in a debug session, and look at the values within the class, fields show up as "?" question marks with no values.

 

Simple example:

public class PortTest {

  public string AName { get; set; }

  public InputPort MyPort { get; set; }

  public PortTest() {

  MyPort = new InputPort(Pins.GPIO_PIN_D0, false, Port.ResistorMode.Disabled);

  AName = "testing";

  }

}

 

public static void Main() {

  var myport = new PortTest();

}

 

Set a breakpoint on the curly brace at the end of Main, run then look at myport.  You should see the AName property with the value of "testing".  After that, you should see just a "?".

 

Now, if you change the name of the AName property to Name in the class, you should see 2 "?".  You won't see Name because the values are shown alphabetically and anything after the port property isn't shown.

 

If you remove the line of code that actually new's up the input port, you will see MyPort = null and Name = "testing"

 

I've tested with N+ and N+2 on Windows 7 and Windows 8.

 

Is this a known issue or is there something I can do to make values show in debugging?  Now, I could prefix all my port field names with "Z" so they show up after all the other fields and I'll be able to see values while debugging - doable but clearly not that convenient.

 

Thanks,

 

Mark

 

 

 

 

 

I did a search and found other topics on TinyCore where the use of it balloons the size of the deployed application by 60+K. Looked like all the other threads were discussing the use on pre-N+2 boards which were smaller and therefore could not handle that much code. I just finished testing an app that I am trying to port from Gadgeteer over to the N+2. It should be able to handle the app because of the increased memory and speed. However, TinyCore is giving it problems. If you create a blank app and add a reference to TinyCore you should see the size jump to around 64K (even with no application code added) and when you try to deploy and run you'll see the error: Resolve: unknown type: Microsoft.SPOT.Touch.TouchGestureEventArgs Error: ff000000 It should also be around 64K - again, without adding any application code. Adding the Touch assembly to try to resolve the type only adds to the deployment size. I can't seem to find a way to get around the type resolution error. BTW, I'm not trying to use any of the touch or wpf features - just DispatcherTimer. I'm going to create a work around since this is a stopping point AND adding that much size to the app just for a timer doesn't make sense. It took me a while to figure out that the unknown type issue was simply the use of TinyCore so thought I would post here just in case someone else runs into a similar situation. Thanks, MarkNic

Background: Own 2 N+ boards and have been working with them for quite a while. New N+2 and tried to load a simple app to do nothing more than read a couple digital pins. When I run it, VS starts to deploy and start the debugger but before any breakpoint is hit the app freezes. After that MFDeploy can see the board but when I ping: "Error: No response from device". Power off/on does not change things. Only recourse is to redo the firmware with DFU tools. That part works fine and I've done it over a dozen times trying to get the board to go but no joy. I initially thought the problem to be that I was running from Windows 8 so I moved over to a Win7 (32bit) machine but freezes just the same. ClrInfo.clrVersion: 4.2.0.0 ClrInfo.clrVendorInfo: Netduino Plus 2 (v4.2.1.0) by Secret Labs LLC ClrInfo.targetFrameworkVersion: 4.2.0.0 SolutionReleaseInfo.solutionVersion: 4.2.1.0 SolutionReleaseInfo.solutionVendorInfo: Netduino Plus 2 (v4.2.1.0) by Secret Labs LLC SoftwareVersion.BuildDate: Nov 7 2012 I tried both USB drivers but MFUSB is currently installed. I can't get any further with it. Anyone with ideas or similar situations? Thanks, Marknic