Howie Goodell

...
I wonder who's bright idea it was to name that assembly "TinyCore"? Whoever it was, I'm sure they're still giggling.

Mark

George Orwell's. Right after he wrote http://en.wikipedia....een_Eighty-Four where the "Ministry of Truth" wrote propaganda and changed records to match the current Party line, and the "Ministry of Love" tortured and brainwashed you ;-)

Have a good weekend!
Howie

Hi Paolo,

It's a standard MiniJTAG port (Cortex Debug Port to be exact).

You can debug using the STLink/V2 and TI MDL-ADA2 JTAG to MiniJTAG adapter. $41.25 for the set, which is ridiculously inexpensive.

We use these instead of our $2000+ ARM RVICE hardware. It works beautifully and supports quite a few breakpoints. We debug C# code, step into native code (alt+tab) and back and forth. It's pretty awesome.

And for those who want a really really nice Cortex-M4F devboard for C/C++ code...Netduino Plus 2 does that really well too. Arduino shield compatibility is a big bonus there too.

Chris

Hi Chris,

All purchased and on my desk. However, there is a teensy problem. The mini JTAG cable Mouser sent us with the TI MDL-ADA2 JTAG to MiniJTAG adapter is female-to-female, but the mini-JTAG connection on the Netduino Plus 2 requires pins on the connector. Are your mini-JTAG connectors male-to-female, or are you doing something else you didn't mention in your post? Two possibilities:

• You bought a male-to-male mini-JTAG adapter.
• If the orientation of the pins works, you removed the RESET button from the mini-JTAG adapter and pushed its pins through the board with no cable.

Example of #1: in Mouser's "customers also purchased" box, I found a 20-pin male-to-male connector that might work sawed in half. Let us know!

Thanks!
Howie

Hi Chris,

I finally am trying to upgrade my Netduino plus to this version, after encountering various problems trying to compile and deploy the 4.1.0.6 firmware.

My goal in switching to the latest version was to make my mistakes where they would be more useful. It seems I am already succeeding.

When I ran the Atmel SAM-BA utility and looked for the TinyBooterDecompressor.bin file, it was already selected. Gullible me: I thought by un-installing all the 4.1 SDKs etc. and re-installing 4.2 versions, it had selected the new version. Nope -- it was showing me the 4.1 version I had compiled yesterday, deep in the hierarchy of the 4.1 Porting Kit output directories (which uninstalling doesn't remove). Turkey!

I flashed the new version downloaded with the 4.2.0.1 firmware using SAM-BA. Now I can deploy the firmware, and it pings -- TinyCLR. Yah!

Howie