Ah, I was mistaken, then, about 4.3 and Gadgeteer, then.
It also strikes me that the DISCOVERY boards are the ideal platform for debugging the PK as well, given the onboard STLink. Has anyone put together a step by step guide to seeing up the environment, building, and then debugging using OpenOCD?
That right there I think would be a huge value to potential contributors.
The porting ebook explains how to set the environment and compile already. Not sure if porters used it and find it useful.
Iāve read the book, and it left me scratching my head with lots of open questions. Itās a good thing to start with, but I think itās time for a 2nd edition 
For me the biggest problem is the huge entry cost. I peek to the NETMF source code from time to time, but without extensive documentation why things are done as they are done, Iām feeling totally helpless. I probably need to look at the source for 3 months to just start grasping on thingsā¦
1 Like
Iāve never been a C/C++ programmer. Never sat in a C/C++ class, never had a 30 minute lesson, etc. I was able to download the PK and GCC then start compiling within days. Iāve even added a blistering fast font rendering routine, modified the SPI library to work properly with my ADCs busypin and enabled the watchdog. If I can do it, anyone can.
Letās just say that you might be wrong on this one. But you sure sound like a cool guy!
Donāt sell yourself short. If you wanted to, you could learn it. If you can write code in C#, you can write it in C or C++.
Have you not seen his avatar? The dude sits on the side of mountains at sunset contemplating C pointers and how they can change the world. He must be cool!
Iāve been to school to learn C/C++ and I still find it confusing at times. Definitely a smart guy.
Have to agree that the our porting guide needs an update.
Nevertheless, I think most of you on this Forum could use it successfully!!
The problem comes at the modification stage. If the part you want to change, for example something in the debugger interface code, and your area of expertise is down at the MCU interface level; youāve got a problem. Most of us could probably hack at the kit on one layer or another, but I know that Iād have to do [em]a lot of work[/em] to tackle some portions.