TinyCLR OS Seventh Release: CAN and Interops

Today we are excited to release the seventh preview of our TinyCLR OS. This release adds CAN support to many devices and has fixed the issue in the latest Visual Studio 15.5 update that prevents projects from building. There’s also an improved API for working with native interops.

As before, you can find all downloads in their respective sections on the downloads page. There are no new bootloader releases this time. Just download the new installers and NuGet packages to get going. You don’t even need to download the firmwares since you can use the update firmware feature in TinyCLR Config to automatically download them for you.

In case you missed it, take a look at the recent announcement detailing our road to 1.0 for TinyCLR OS.

TinyCLR OS Downloads: http://docs.ghielectronics.com/tinyclr/downloads.html
TinyCLR OS Release Notes: http://docs.ghielectronics.com/tinyclr/release_notes.html


great news
could you please add a CAN section as part of Tutorials ?
i dont think one of us would find CAN/CANBUS within UWP documentation on docs.microsoft.com


Hey, can you give some sample code regarding that part. #Thanks

First try with brainpad without issues:

1 Like

http://docs.ghielectronics.com/tinyclr/porting/native_interops.html has a small example that shows basic use. We will be producing more examples as time goes on, but if you have a specific scenario you’re wondering how to implement, I can give a quick example for it. A good starting point is to look at the members available in TinyCLR.h.

We will be adding a CAN tutorial shortly. In general you will get a CAN controller object just like you do SPI or I2C, except you won’t need to create a specific bus device. The timings and message objects function similarly to how they did in our NETMF API.

Happy New Year 2018 GHI Electronics Team with TinyCLR OS v0.7.0 on BrainPad and Stepper click.


I gave up on my tinyclr OS 0.6 attempts to use PWM (two motor controller modules driving 4 wheels) on the Fez Reaper.

I consistently got bizarre results and was 75% convinced either the motor controllers were damaged somehow, or there were some serious bugs in the PWM/pin code (25% I was just not figuring it out)

Is it reasonable to think that 0.7 might have addressed issues in this area, or is this likely a “just couldnt figure it out” thing?

Did you read the fix list? https://github.com/ghi-electronics/TinyCLR-Ports/issues/37 on Cerb family was addressed, could that have been your scenario?

As @Brett mentioned, the release notes have a lot of detail on which bugs were fixed and which remain. We did resolve a number of issues around PWM but there are still some we have not had a chance to get to yet.