10 replies to this topic

[CW2]

I have noticed that firmware source archives include version of SecretLabs_NETMF_Hardware_SecretLabs_NETMF_Hardware_PWM.cpp which contains no PWM code, the PWM::PWM_xxx(...) function bodies are empty. This causes problems with custom firmware builds, where PWM code does not work. Would it be possible to have the PWM code in the firmware source releases? Perhaps the firmware source patch is created from wrong branch or so.

[Chris Walker]

Hi CW2, The PWM code is technically beta/pre-release (the final version with full features is coming in v4.1.1). We normally don't publish beta code (to minimize confusion and to help us keep costs down). Perhaps we should publish the pre-release PWM code in the forums so that advanced users can integrate it into custom builds? It'll take a few hours (read: over a few days) to run it through our publishing/commenting/approval process but we can certainly do it. [It would push back other projects a few days--unless we combined it with the final Netduino Plus build process later this month.] Chris

[CW2]

The PWM code is technically beta/pre-release (the final version with full features is coming in v4.1.1). We normally don't publish beta code (to minimize confusion and to help us keep costs down).

Chris, thanks for the explanation.

Perhaps we should publish the pre-release PWM code in the forums so that advanced users can integrate it into custom builds? It'll take a few hours (read: over a few days) to run it through our publishing/commenting/approval process but we can certainly do it. [It would push back other projects a few days--unless we combined it with the final Netduino Plus build process later this month.]

IMHO it would be nice to have firmware source even though it includes pre-release code, it can be labeled as such - the problem now is, that the published firmware source looks like to be the same from which the official firmware binaries are compiled, but it is not. I am tracking the history of changes and till now I hope I am able to keep up with the differences (e.g. to let testers know that feature X does not work and bugfix Y is not included yet), but it can become a bit complicated with increasing number of firmware revisions.

I can certainly wait for PWM (or any other) code to be published later, I don't really want to be blamed for causing delays with other projects :-) I would be very happy developer if I could download the firmware source after a new version of binaries is published (be it retail, beta etc.), compile it and have only minor diff-s (timestamps and such, assuming the same compiler).

[Chris Walker]

Hi CW2, It's actually the same source we build the published binaries from (with the exception of swapping out the pre-release PWM code for the stub file). Looking into the best publication options... Chris

[sweetlilmre]

Hi CW2,

It's actually the same source we build the published binaries from (with the exception of swapping out the pre-release PWM code for the stub file).

Looking into the best publication options...

Chris

Hi Chris,

I'd also like the PWM code, but not in a manner that would cause delays for any of your projects.
The people testing beta firmware that I have compiled will have to live without the PWM capabilities for now

Ultimately it would be awesome if you would publish the firmware source to GitHub (or host your own Git master repo) that people like CW2 and myself can pull from for our experiments. This would also help to smooth the jump between firmware versions and allow us to push upstream our changes for your consideration.

Then again I realise that this would take some considerable time to set up and you have a million things on the go, I do this for fun, you for a living!

-(e)

[Chris Walker]

sweetlilmre, We've registered the netduino.codeplex.com project (using Mercurial) and hope to publish the v4.1.0.6 or v4.1.1 there. I'll make sure we include the PWM code as it comes out of beta sa well. Would that work well? Chris

[CW2]

We've registered the netduino.codeplex.com project (using Mercurial) and hope to publish the v4.1.0.6 or v4.1.1 there. I'll make sure we include the PWM code as it comes out of beta as well.

Would that work well?

Awesome!

Thanks Chris, keep up the good work.

[sweetlilmre]

sweetlilmre,

We've registered the netduino.codeplex.com project (using Mercurial) and hope to publish the v4.1.0.6 or v4.1.1 there. I'll make sure we include the PWM code as it comes out of beta sa well.

Would that work well?

Chris

Brilliant
Thanks for all your hard work.

-(e)

[georgejh]

Is it possible and how can PWM be generated at 1 microsecond or less (1MHz+)?

[Chris Walker]

Is it possible and how can PWM be generated at 1 microsecond or less (1MHz+)?

Possible with a firmware update. We're working with Microsoft on a new "unified" PWM design for .NET MF, and will be trying to bring this ".NET MF 4.2" feature to Netduino early. Hopefully soon, but not yet.

Chris

[tibel]

Hi Chris,

what is with netduino.codeplex.com ???

As the community is growing I think it would be great to have a public repository so that we can try out stuff and even contribute.
This way it would also be possible to release new firmware version faster.