Order by
Group by
Topic

Looking for all posts by John_ghielectroncs

Page 1 of 133 out of 2,656 messages.

RE:PWMInput in TinyCLR by John_ghielectroncs on Jul 18, 2017 at 9:23am

@Brett and opiswahn - SignalCapture exists in TinyCLR as well, under GHIElectronics.TinyCLR.Devices.GpioChangeReader. The API is the same as NETMF for now.

RE:TINYCLR - How to use more than one SPI device on a bus ? by John_ghielectroncs on Jul 17, 2017 at 3:07pm

@Bec a Fuel - It's a known issue in the current release. MSB/LSB is determined by the specific SPI provider. So for STM32F4, the order is whichever the datasheet for the specific processor specifies. The HAL driver in the ports repo just writes/reads the entire 8/16 bit value to/from the DR register.

RE:TinyCLR and windows 7 by John_ghielectroncs on Jul 17, 2017 at 9:21am

@MNO - If you can email the project you're using to support at ghi... and reference this thread, we will test it here.

RE:TinyCLR and windows 7 by John_ghielectroncs on Jul 14, 2017 at 3:39pm

@MNO - In the new project, did you use the same code?

RE:TinyCLR and windows 7 by John_ghielectroncs on Jul 14, 2017 at 9:14am

@MNO - Can you try to reflash the firmware, create a new project to test, and reinstall the VSIX?

RE:App Available Memory Size Difference Between NETMF and TinyCLR OS by John_ghielectroncs on Jul 13, 2017 at 9:48am

@B5 Fan - There is currently no way to get the amount of heap space free unfortunately. We are looking into it for a future release. Doing the subtraction yourself would get you a rough number at least.

RE:TinyCLR and windows 7 by John_ghielectroncs on Jul 13, 2017 at 9:10am

@MNO - What behavior specifically are you seeing that's failing? Are there any errors shown anywhere?

RE:App Available Memory Size Difference Between NETMF and TinyCLR OS by John_ghielectroncs on Jul 13, 2017 at 9:09am

@B5 Fan - One other thing to keep in mind is that System.GC.GetTotalMemory returns the amount of memory used unlike the NETMF method that returned the amount free.

RE:TinyCLR and windows 7 by John_ghielectroncs on Jul 12, 2017 at 10:34am

@MNO - So you can deploy an app like blink LED and if you just power the board it works, but when you try to start the VS debugger with the same program, it doesn't?

RE:NETMF 4.3 Maximum Assemblies by John_ghielectroncs on Jul 12, 2017 at 9:18am

@Skewworks - In NETMF there is a maximum of 64 assemblies: https://github.com/NETMF/netmf-interpreter/blob/dev/CLR/Include/TinyCLR_Runtime.h#L1474

A quick look at app domain unload doesn't look like it lowers the count but I'm not 100% positive.

RE:TinyCLR - Finding Version Number by John_ghielectroncs on Jul 12, 2017 at 9:06am

@Drovers_Dog - Take a look at System.Runtime.InteropServices.DeviceInformation

RE:TinyCLR and windows 7 by John_ghielectroncs on Jul 12, 2017 at 9:04am

@MNO - Step by step?

RE:TinyCLR OS Register Access for STM32F427 (Quail) by John_ghielectroncs on Jul 10, 2017 at 10:47am

@B5 Fan - I'm not sure what you're asking. The Marshal class is a more general and complete replacement for the old Register class we had in NETMF.

RE:TinyCLR OS Memory Map by John_ghielectroncs on Jul 10, 2017 at 9:59am

@Innovactive and B5 Fan - All of that information is now managed by the device itself. All TinyCLR needs to know is where the deployment is. You can put the deployment anywhere you want as long as you satisfy the deployment provider requirements: at least one memory range that can be read, written, and erased with optional XIP. The firmware itself can go anywhere, it doesn't need to know where it's executing from.

RE:TinyCLR OS Register Access for STM32F427 (Quail) by John_ghielectroncs on Jul 7, 2017 at 8:17pm

@B5 Fan - Take a look at the Marshal class. It has functions to read and write memory.

https://msdn.microsoft.com/en-us/library/system.runtime.interopservices.marshal(v=vs.110).aspx

Fifth Preview of TinyCLR OS Core Features and Porting by John_ghielectroncs on Jul 7, 2017 at 10:55am

A TinyCLR OS outbreak is heading your way!

Starting today, TinyCLR OS is going to start infecting a lot of hardware you already own and other hardware around the world. Today's Tech Talk is all about that and we cover some questions below as well.


https://www.youtube.com/watch?v=pQKLpAZFSDo


What is TinyCLR OS?
It is a modern operating system that runs .NET programs on your embedded devices. Take a look at the docs to see what's changed and what's coming!

How do I use TinyCLR OS?
Get the latest Visual Studio 2017, install the TinyCLR OS extension (it's less than 1MB!) and now you can load and debug programs on your hardware with just a USB cable. Get going today!

Which hardware does TinyCLR OS support?
TinyCLR OS is easily portable. We have put all the complex interpreter work into a single library that we manage. Then this library uses some peripheral drivers to run on specific hardware. We are starting with example ports for G30, G80, FEZ, BrainPad, FEZ Cerberus, STM32F411-DISCO, STM32F407G-DISCO, netduino 3, and Quail. Yes, you heard that right, netduino 3 and Quail boards now work with Visual Studio 2017 and TinyCLR! And this is just a starting point. We are already working on many other boards.

How do I help?
Everything you need is on the TinyCLR GitHub. You can start helping out today. The current supported devices still need work.

What tools do I need to port TinyCLR OS?
Nothing but free tools: Visual Studio 2017 Community and GCC. Just follow the porting instructions. These are the same tools we use internally so you will get the exact same results.

Where is the TinyCLR OS support for G120 and G400?
They'll be back in the next release.

Is there RLP/Native code in TinyCLR?
Yes! Even better: you can add your own native interops! You can extend TinyCLR anyway you like, just like we do.
See the docs to get started.

Who has used TinyCLR OS?
We have been working close with many commercial users and community members. In fact, we hope to see videos showing community members with TinyCLR OS running on their hardware.

Do I see a new documentation system?
Yes! We are excited about moving all our documentation to GitHub and DocFX. It is in progress still, so please be patient and feel free to contribute.

What is FEZ?
It is the official reference board for TinyCLR OS. More on this later!

RE:G400 RLP Delay function does not work by John_ghielectroncs on Jun 30, 2017 at 10:32am

@Daiz - Assuming you tested with the correct address of 0x16FFFFC, for us to be able to test it, you'll have to get a sample working with the toolchain and process mentioned on https://www.ghielectronics.com/docs/50/rlp. If using the steps on that page works but your IDE doesn't, something isn't working quite right in the IDE you use. If you have a sample that fails using the system on that page, we can take a look at it.

RE:G400 RLP Delay function does not work by John_ghielectroncs on Jun 26, 2017 at 4:41pm

@Daiz - 0x16FFFFC is the correct value for the 2016 R1 and 2015 R1 SDKs, not 0x17FFFFC. 0x17FFFFC is only for before 2015 R1.

RE:G400 RLP Delay function does not work by John_ghielectroncs on Jun 26, 2017 at 3:55pm

@Daiz - How do you compile the RLP image?

Page 1 of 133 out of 2,656 messages.