33 replies to this topic

[Chris Walker]

This post replaced by Netduino v4.2 RC3 firmware

[Dan T]

Version: 4.2.0 RELEASE CANDIDATE (version 4.2.0.0 RC1)
This firmware includes the following updates:
7. Dozens of bugfixes

Thanks! I'll let you know if this fixes my networking probs...

[Dan T]

Thanks! I'll let you know if this fixes my networking probs...

It didn't. Still can't see the network. I'll take this up in another thread.

But... It does seem to deploy VERY smoothly. And repeatedly. The one time I unplugged the USB was in a hopeful (desperate) attempt to get network access... Then deploy got stuck... then I hit Netduino's reset... then a small BSOD happened and my machine rebooted. Hmm. I'll try to repro that when I have more time and more courage.

Let me focus on the positive here: THIS FIRMWARE SEEMS TO DEPLOY MY CODE VERY SMOOTHLY AND REPEATEDLY.

[Chris Walker]

Hi Dan T, So...improvement On the network issue, can you file an official bug report ("issue") on that over on netmf.codeplex.com? State that you're using the SAM7X chip and it isn't working on your 10Mbps router (although it works on your 100Mbps router). I'd give them the model # too just in case... If you can post a link to that here, we'll take a glance to see if there's an obvious issue...perhaps in the PHY init code or MAC code from the .NET MF PK... Chris

[Valkyrie-MT]

It didn't. Still can't see the network...

If you submit an issue on codeplex, it'd be tough for the developers to figure out the difference between these 2 routers without buying them and trying to reproduce... You might want to consider using Wireshark to record the network traffic between Netduino and router A, then Netduino and Router B, and send them (or attach to the Codeplex issue) the PCAP (wireshark log) file. Also, you might be able to compare the traffic and see the difference... Then the developers know exactly where to focus their effort.

Two cents...

-Valkyrie-MT

[Robert L.]

I installed this new version last night, the upgrade went smoothly... I thought that this version was to include support for reading & writing on-board flash as well as support for Cryptography functions, such as RSA. 1) Where can I look for native flash reading/writing? Is there an example available? 2) Microsoft.Spot.Native seems to include Microsoft.SPOT.Cryptography. Any chance of getting an example of how to use this code? Can you confirm that this is available in 4.2? In the book "Expert .NET Micro Framework", it says that the keys are stored in different formats and the cipher data uses a different byte order compared with the "Full .NET" Framework. A note on Microsoft's web site seems to indicate the cipher data is in reverse order, IE swapped left to right. I plan to use the Netduino to transfer encoded RSA messages to/from a web site using PHP's gmp class.

[Chris Walker]

Hi Robert, .NET MF 4.2 added both of these new features, but both of them are traditionally targeted for modules with several megabytes of Flash/RAM. We have created a managed code AES implementation, and it's quite possible to do crypto with your Netduino. But the remote reflashing via Microbooter probably won't fit. Chris

[Robert L.]

Hi Robert,

.NET MF 4.2 added both of these new features, but both of them are traditionally targeted for modules with several megabytes of Flash/RAM.

We have created a managed code AES implementation, and it's quite possible to do crypto with your Netduino. But the remote reflashing via Microbooter probably won't fit.

Chris

Hi Chris, thanks for the quick reply. Let me clarify my need for reading and writing the embedded FLASH. I am not wanting to update the programming code, (IE make software changes) what I want to do is use a small area of FLASH (say around 4K) to store variables and parameters that would survive power cycles. I believe this can be done with an SD card, but I wonder if the native FLASH can be updated by code running on the ARM processor.

Regarding RSA, I see that 4.1 version of Microsoft.SPOT.Native includes Microsoft.SPOT.Cryptography while 4.2 RC1 does not. Is this still to come, or have I made some error in the install or my understanding?

Thanks,
Robert

[Chris Walker]

Hi Chris, thanks for the quick reply. Let me clarify my need for reading and writing the embedded FLASH. I am not wanting to update the programming code, (IE make software changes) what I want to do is use a small area of FLASH (say around 4K) to store variables and parameters that would survive power cycles. I believe this can be done with an SD card, but I wonder if the native FLASH can be updated by code running on the ARM processor.

Oh sorry, I misunderstood. That's another new feature! It's called "simple storage."

We're evaluating simple storage, and it looks like we'll be able to enable about 8KB of flash storage on the chip. I don't want to promise anything until we're done with the code (and we know it will fit for sure--right now code space is super tight on Netduino Plus with all the .NET MF 4.2 extras), but it's one of the first features we'll be adding after 4.2 is released.

Chris

[elettrozero]

Version: 4.2.0 RELEASE CANDIDATE (version 4.2.0.0 RC1)

5. IP broadcast support

Hi, what does it mean "IP broadcast" ?

[Chris Walker]

Hi, what does it mean "IP broadcast" ?

The RC1 update has bugfixes to enhance compatibility with UDP broadcast packets. There may be some glitches to work out still...not sure.

Chris

[Scott Green]

Sorry if this has been asked elsewhere, but is OneWire support included in 4.2.0 RC1 Scott...

[Stavros Tekes]

Chris do you think that with the 50% patch, will the 4.2 RC1 release more ram in the netduino plus?

[Valkyrie-MT]

Sorry if this has been asked elsewhere, but is OneWire support included in 4.2.0 RC1

OneWire support is NOT in 4.2 RC1, but Chris has previously promised a special OneWire build after the final release of 4.2. So, it's coming.

-Valkyrie-MT

[Chris Walker]

OneWire support is NOT in 4.2 RC1, but Chris has previously promised a special OneWire build after the final release of 4.2. So, it's coming.

Yup! I'm not sure if OneWire will fit in the standard firmware--but we will definitely make a special build!

Chris

[oritpro]

Hi, what does it mean "IP broadcast" ?

Let's say your network device has an IP address of 192.168.1.1/24 (24=255.255.255.0). The broadcast IP for that subnet is: 192.168.1.255

That's called a subnet directed broadcast.

There's another type of broadcast that looks like this: 255.255.255.255

That's called a zero net or global broadcast.

Broadcasts are used to send messages all devices on the same subnet or network at the same time.

[Valkyrie-MT]

When can we get the firmware source for this? I assume this was built with RVDS 4.0? -Valkyrie-MT

[Chris Walker]

Hi Valkyrie, Working on uploading it to CodePlex. Should be live sometime in the next few days [Fabien and Bertrand have been making the CodePlex site work...more on that soon.] Chris

[James]

Thanks for adding IP Broadcast support!!

[elettrozero]

Let's say your network device has an IP address of 192.168.1.1/24 (24=255.255.255.0). The broadcast IP for that subnet is: 192.168.1.255

That's called a subnet directed broadcast.

There's another type of broadcast that looks like this: 255.255.255.255

That's called a zero net or global broadcast.

Broadcasts are used to send messages all devices on the same subnet or network at the same time.

Well...does it really work with this firmware ?