57 replies to this topic

[Chris Walker]

Hi Dave,

In truth, personally, I'd prefer to not be constrained to OTP MAC address. Or more precisely, I'd prefer to have the ability to override the OTP setting, something logically like this pseudocode:

effectiveMAC = ( 0 == configMAC ) ? otpMAC : configMAC

Agreed. If we can get the MAC address into OTP, that would just be a convenience item. You'd still be able to change the MAC address via MFDeploy or code.

Chris

[Chris Walker]

Hi mobilegamer999,

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.

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

[mobilegamer999]

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

[Lunddahl]

SecretLabs.NETMF.IO,4.2.0.0

This looks different than mine, should SecretLabs.NETMF.IO be there at all ?

- Ulrik Lunddahl

[DaylightMisery]

Hi guys, After the firmware 4.2.1. update i dont save network configuration. Error message content is "unable to erase configuration sector memory". on my computer installed mf sdk 4.3 . I tried dhcp enble or disable, diffenrt dns address, valid mac address but same error. Have any ideas ? Thanks..

[Martin Ayotte]

I'm glad to having installed this upgrade ! I've hooked up an MCP23017 on the I2C to control a very old IEE parallel LCD (25 years old, but pinouts/registers compatible with today's version). At the begining, I didn't realize about I2C saga, and I was still at 4.2.0.1, it wasn't working. I've test my soft with the SoftwareI2C workaround, it was working ... I've then realized ... I've upgraded to 4.2.1.2, and it works ! Better speed then Soft workaround ... :-) ... btw, about Mac scheme, I agree : OTP if CustomConfig not valid ...

[Chris Walker]

Hi DaylightMisery,

After the firmware 4.2.1. update i dont save network configuration. Error message content is "unable to erase configuration sector memory".
on my computer installed mf sdk 4.3 .

I tried dhcp enble or disable, diffenrt dns address, valid mac address but same error.

Have any ideas ?

There are some known connectivity issues with MFDeploy in the .NET MF 4.3 beta; not sure if they all got fixed for RTM or not. There were a lot of internal changes to the timing mechanisms of MFDeployEngine in the new SDK, designed to provide an enhanced debug experience. We're currently researching the issue.

For now I would recommend sticking with the .NET MF 4.2 QFE2 SDK until we have NETMF 4.3 firmware for Netduino Plus 2. Or you can set the MAC address and IP settings from code using the NETMF NetworkInterface class.

Chris

[Kevgor]

Version: 4.2.1 Update 2 (version 4.2.1.2)

To flash this firmware:
1. Detach your Netduino
2. Press and hold your Netduino's pushbutton while plugging it in via USB; this will put it in bootloader mode.
3. Erase the firmware on your Netduino using the STDFU Tester application
> a. Select the "Protocol" tab
> b. Press the "Create from Map" button
> c. Select the "Erase" radio button option
> d. Press the "Go" button
> e. Wait for erase process to complete
4. Flash the attached .DFU file using the ST DfuSe Demonstrator application (included with STDFU Tester)
> a. Locate the "Upgrade or Verify Action" pane (bottom-right pane)
> b. Press "Choose..." and select the attached DFU file
> c. Check the "Verify after download" option
> d. Press "Upgrade". It will take a few minutes to update your Netduino.
> e. Detach and reattach your Netduino (power cycle) or press "Leave DFU mode"

After flashing, to set your network settings using MFDeploy:
1. Select the Target > Configuration > Networking menu. Re-enter your IP address settings and MAC address.

Enjoy, and please let us know if you run into any troubles.

Chris

Hi there, I am having trouble with these steps. In steps 3 c,d,e, does the STDFU Utility give any feedback or display any messages to say that firmware is being erased?

Also, in step 4d, the "Upgrade" button is greyed out.

Let me know if anything comes to mind.

Thanks
Kevgor

[Gino Geusens]

Hi there, I am having trouble with these steps. In steps 3 c,d,e, does the STDFU Utility give any feedback or display any messages to say that firmware is being erased?

Also, in step 4d, the "Upgrade" button is greyed out.

Let me know if anything comes to mind.

Thanks
Kevgor

Hello,

I just had the exact same problem.

i fixed it by installing the 64 bit version of the dfu program.

It seems that if you install the 64 bit version of the framework, you will also need to install the 64 bit version of the program ?

[Chris Walker]

Hi Kevgor,

Hi there, I am having trouble with these steps. In steps 3 c,d,e, does the STDFU Utility give any feedback or display any messages to say that firmware is being erased?

Can you verify that the device ("ST DFU...") appears in the pull-down at the top of the STDFU Tester application?

If so, could you please take a screenshot (shift+prtscr) after selecting 'Erase' and pressing 'Go' and attach it to a reply to this thread?

Chris

[iReplicate]

Hi Kevgor,


Can you verify that the device ("ST DFU...") appears in the pull-down at the top of the STDFU Tester application?

If so, could you please take a screenshot (shift+prtscr) after selecting 'Erase' and pressing 'Go' and attach it to a reply to this thread?

Chris

Having same issue as Kevgor.
No devices in the pull-down
I'm on a 64-bit machine.
Heres the device capabilities:

HalSystemInfo.halVersion:               4.2.0.0
HalSystemInfo.halVendorInfo:            Netduino Plus (v4.2.0.1) by Secret Labs LLC
HalSystemInfo.oemCode:                  34
HalSystemInfo.modelCode:                177
HalSystemInfo.skuCode:                  4097
HalSystemInfo.moduleSerialNumber:       00000000000000000000000000000000
HalSystemInfo.systemSerialNumber:       0000000000000000
ClrInfo.clrVersion:                     4.2.0.0
ClrInfo.clrVendorInfo:                  Netduino Plus (v4.2.0.1) by Secret Labs LLC
ClrInfo.targetFrameworkVersion:         4.2.0.0
SolutionReleaseInfo.solutionVersion:    4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
SoftwareVersion.BuildDate:              Sep 19 2012
SoftwareVersion.CompilerVersion:        410894
FloatingPoint:                          True
SourceLevelDebugging:                   True
ThreadCreateEx:                         True
LCD.Width:                              0
LCD.Height:                             0
LCD.BitsPerPixel:                       0
AppDomains:                             True
ExceptionFilters:                       True
IncrementalDeployment:                  True
SoftReboot:                             True
Profiling:                              False
ProfilingAllocations:                   False
ProfilingCalls:                         False
IsUnknown:                              False

[korbai]

Hello, I have an application which works well with Netduino Plus. I tried to upgrade to Plus 2 but I have problem with I2C. I use 6 PCF8574 i/o expander which does not work with Plus 2. I tried the dedicated SC/SD pin (and tried the old A4/A5). The I2C works well with DS1307 on Plus and Plus2, too. But the PCF8574 works only on Plus. Does anybody use PCF8574 with success? What should I try? I use the latest firmware: Netduino Plus 2 (v4.2.1.2) (I tried the previous one, the result is the same.) Zoltan

[Chris Walker]

Hi iReplicate,

Having same issue as Kevgor.
No devices in the pull-down

Please try pressing and holding the onboard pushbutton while powering up your Netduino Plus 2. It should start up in bootloader mode instead of NETMF mode.

Chris

[Chris Walker]

Hi Zoltan,

The I2C works well with DS1307 on Plus and Plus2, too.
But the PCF8574 works only on Plus. Does anybody use PCF8574
with success? What should I try?

Do you have a logic analyzer by any chance? So we can see the data?

Alternatively--do you have a link to the part and a simple code sample which reproduces the issue?

Chris

[korbai]

Hi Zoltan, Do you have a logic analyzer by any chance? So we can see the data? Alternatively--do you have a link to the part and a simple code sample which reproduces the issue? Chris

Hi Chris,

 

I organized a test only with 1 PCF8574 and a very simple test program

for reproducing the issue and woohoo: it works. So the error will be on my side.

It is strange that PCF8574 in my application works with netduino, netduino plus but not with plus 2.

The other parts e.g. DS1307 works in all. It need further investigation.

 

Thanks,

Zoltan

[Chris Walker]

Hi Zoltan,

 

I organized a test only with 1 PCF8574 and a very simple test program

for reproducing the issue and woohoo: it works. So the error will be on my side.

It is strange that PCF8574 in my application works with netduino, netduino plus but not with plus 2.

The other parts e.g. DS1307 works in all. It need further investigation.

 

When you find out what the issue in the larger application, please let us know.  We'd love to learn more about your scenario and see if there are ways to make board upgrades even more seamless for others.

 

Thank you for the update,

 

Chris

[NooM]

any chance for a serialport version? (deploy, debug) ... com2 or something like that (not com1 please ..)

[JeffJohnson]

Hi,

 

I just got a Plus 2 for Xmas and I'm having trouble with PWM.  I got it working and wrote a little led blinker, which worked fine.  Then I started playing with PWM, and things went south.  It failed to deploy and crashed VCS2010.  I restarted it, tried to run the simple blinker again...still not deploying.  In fact, now it isn't communicating using MFDeploy.

 

My USB driver is dated 4/10/12.  Is there a newer one?

 

Was there a bug in PWM that was fixed?  I flashed the latest firmware (I think, can't verify that currently).

 

Thanks,

 

Jeff

[iReplicate]

Hi iReplicate, Please try pressing and holding the onboard pushbutton while powering up your Netduino Plus 2. It should start up in bootloader mode instead of NETMF mode. Chris

Yes i did press and hold. MFdeploy responds to ping with

Pinging... TinyBooter Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC

 

The DFU Tester v3.0.1 shows no devices.

 

Is this update only for Plus 2 ??

 

If only for Plus 2 is there an update 2 for regular old netduino Plus as i'm hoping the

receive UDP broadcast is fixed

and dhcp only works on boot is fixed  

[Chris Walker]

Hi Jeff,

 

I just got a Plus 2 for Xmas and I'm having trouble with PWM.  I got it working and wrote a little led blinker, which worked fine.  Then I started playing with PWM, and things went south.  It failed to deploy and crashed VCS2010.  I restarted it, tried to run the simple blinker again...still not deploying.  In fact, now it isn't communicating using MFDeploy.

...

Was there a bug in PWM that was fixed?  I flashed the latest firmware (I think, can't verify that currently).

 

When you plug in your board, does it show up in Device Manager?  Under USB, as a Netduino?

 

If not, please try erasing and re-flashing your board to get it back into a known-good-state.  Instructions are in the firmware sticky at the top of the forum.

 

BTW, what does your PWM code look like?

 

Chris