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.

mobilegamer999

Member Since 15 Nov 2012
Offline Last Active Jan 20 2013 02:32 AM
-----

Posts I've Made

In Topic: Netduino Plus 2 I2C Issues

14 January 2013 - 03:36 AM

My netduino seems to be working fine in my circuit for the most part. I did notice one odditity however and that is when using an ADXL345 breakout board along with both resistors, the chip 'hangs' on boot up and the blue LED never goes away, however if I only bring up the SCL line with 3.2k resistor and leave the SDA line with no pullup except for the one the breakout has built in(or so i assume it has one built in) the chip functions correctly.


In Topic: Netduino Plus 2 I2C Issues

11 January 2013 - 05:24 PM

Hi mobilegamer999, What value of pull-up resistors are you using? If you connect GND to pin SDA/SCL, do you see your scope's reading move to 0V? Also, can you try using a speed of 100,000 Hz and see if that changes anything? And pass in your full ReadAccel array instead of using the first element in the array? Finally...please try updating to the 4.2.2 firmware release. We haven't changed anything I2C related in the new release...but it will make sure that any diagnostics from our end match your configuration.

 

I had 5k pullups but just now switched to 3.2k pullups. At the same time I also upgraded to 4.2.2 and flashed the code that you posted. It looks like one of the many things that were done seemed to have fixed the issue. I will re-enable the I2C code in my main project and see if I can replicate my success. Thank you.


In Topic: Netduino Plus 2 I2C Issues

11 January 2013 - 05:03 AM

I am just trying to get a single pin state change on the SDA/SCL lines to show up on my scope, but I have yet to see either pin change it's state ever, always staying at 3.3v.

I am not using A4/A5 nor am I going to any device, I am currently just feeding the output into a scope to examine the voltage levels.

Also, software I2C is out of the question because it is not fast enough.


In Topic: Netduino Plus 2 Firmware v4.2.1 (Update 2)

05 December 2012 - 01:17 PM

Hi mobilegamer999,



What version of the DLL are you using? Can you double-check and make sure that you're running the 4.2.1 SDK (i.e. with a 4.2.1.0 version)?

Chris


I do have the right version loaded (4.2.1.0 for NETMF.Hardward.Netduino) here is information from MFDeploy, it looks like there might be a version mis-match between some of the assemblies however.

DeviceInfo:
  HAL build info: 4.2.0.0, Netduino Plus 2 (v4.2.1.2) by Secret Labs LLC
  OEM Product codes (vendor, model, SKU): 34, 177, 4102
  Serial Numbers (module, system):
    00000000000000000000000000000000
    0000000000000000
  Solution Build Info: 4.2.1.2, Netduino Plus 2 (v4.2.1.2) by Secret Labs LLC
  AppDomains:
    default, id=1
  Assemblies:
    mscorlib,4.2.0.0
    Microsoft.SPOT.Native,4.2.0.0
    Microsoft.SPOT.Hardware,4.2.0.0
    Microsoft.SPOT.Net,4.2.0.0
    System,4.2.0.0
    Microsoft.SPOT.Hardware.SerialPort,4.2.0.0
    Microsoft.SPOT.IO,4.2.0.0
    System.IO,4.2.0.0
    Microsoft.SPOT.Hardware.PWM,4.2.0.1
    Microsoft.SPOT.Hardware.Usb,4.2.0.0
    SecretLabs.NETMF.Diagnostics,4.2.0.0
    SecretLabs.NETMF.Hardware.Netduino,4.2.1.0
    Microsoft.SPOT.Hardware.OneWire,4.2.0.0
    Microsoft.SPOT.Time,4.2.0.0
    QCController,1.0.0.0
    SecretLabs.NETMF.IO,4.2.0.0
    SecretLabs.NETMF.Hardware,4.2.0.0

EDIT:
Looking into the crash further, It turns out just having the I2CBus class anywhere was enough to cause it to create it's own instance, so I removed that code and there was no longer a crash because there was no double-assigning of the I2CDevice class anymore. However it still reads all 0's. Attached is the extent of my code for I2C, note that the Read() function is called in a loop one level above this class.

Link to code

In Topic: Netduino Plus 2 Firmware v4.2.1 (Update 2)

04 December 2012 - 05:36 PM

In Visual Studio, expand the references branch. For the ND+2 you should be referring to SecretLabs.NETMF.Hardware.Netduino instead of SecretLabs.NETMF.Hardware.NetduinoPlus. If you are seeing SecretLabs.NETMF.Hardware.NetduinoPlus, just click it and delete it, then choose "Add Reference" and add the SecretLabs.NETMF.Hardware.Netduino.dll version 4.2.1.0.


It is only referencing the SecretLabs.NETMF.Hardware.Netduino dll.

EDIT:
For further clarification,
I tried the NetduinoPlus dll just to see what would happen and it does not crash and the pin states DO change, but there is no data that is being read in/out;
And with the Netduino dll (not plus) it crashes when I attempt to instantiate a I2CDevice instance.

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.