Gauss

Hi Gauss,

 

I have written some code to use a queue, but have yet to try it out properly.

Your post triggered me to run it up.

 

I am using a Netduino plus v1 with .netmf v4.2.

 

I put a break point on the line:

messageQueue = new Queue();

Before the line executes, I confirmed that the messageQueue variable appears as "null" when the mouse hovers over it.

After stepping over the line, the variable appears as "Count = 0" instead, and I can click a "+" to see more internal data.

 

The queue is a private member of a class that is created by the main program.

It is new'd when the class constructor runs.

 

What hardware and framework combination do you have?

 

Hope this is of some help - Paul

I have a Netduino Plus v1 with .NET MF v4.2

I found out that its actually putting the Queue in there, but apparently some of the functions are timing out during debug... Very weird.

Mario, thank you for your response.

I was actually just reading your blog on performance metrics with code in the .Net Micro Framework.

Ok, I'm not sure what exactly is going on here...

So I have updated my Netdunio Plus (v1) to the TinyBooter 4.2.0.1

After following these steps (http://wiki.netduino...ep-by-step.ashx) this is what I get in MFDeploy:

 

 

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

 

The problem comes when I try to send the ER_FLASH and ER_CONFIG files.

It just hangs on the 'Chk' step, I never get 'Chk Signature... Signature Passed!'

And when I cycle power on the device and ping, this is all I get:  

 

Pinging... TinyCLR

 

No version, no updates after that (which seems atypical given every guide I've read on this). However, 'Device Capabilities...' nets:  

 

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

 

Any ideas? Could it be related to what I believe to be random disconnects (the Blue LED on my Netdunio Plus will turn off at a certain point in time).

You are correct: SDA is A4 and SCL is A5.

 

You'll probably need pull-up resistors for both SDA and SCL if your LCD module doesn't have them on the board.

 

Plenty of us have driven similar LCD modules through I2C but the bus isn't nearly as fast as SPI. I'd probably buy a cheaper board (you can get a 20x4 module with I2C for $12 @ Amazon) rather than the Adafruit model but you'll interact with them the same. AxelG wrote a great library that will jump start you as well.

 

Good luck!

Thanks for the info.

I was actually considering the Adafruit shield because it includes the buttons, I felt the package was nicer. I'll have to see if there is a quicker way to sneak in some buttons. It'll have to be enclosed anwyay.