apokryphus

Finally figured out - but still now knowing why - what the solution to the debugging problem is - i just have to toggle a different pin than the onboard LED.

Of course the clr is still overwritten (Base address 0x08000000) and therefore the Netduino+2 is not available as an USB-Device (but still in Bootloader mode) but the debugger is now always resetting and loading the file to the net+2 and jumps directly to the routines or whereever the breakpoints are.

However i now can start to learn C/C++ on that tiny device and use hopefully the whole bench of Arduino Shields ...

Hey CW,

thank you for your response.

Yes, i guess you are right, i am probably overwriting the tinyclr when writing my code to 0x08000000 - since this is the address i figured out from the tinyclr.hex file.

as i said, i am new to this business and learn it by myself via trial and error, therefore your help is very much appriciated. =)

Delivered and soldered...

I was able to build and deploy via Visual Studio 2012 and VisualGDB a small blinky written in C to the NET+2 - the program is running fine at all, but a lot of work have probably to be done now, since it is a bigger workaround the reflash/debug it again.

The Problem:

When i deploy via ST-Link V2 and the TI ADA2 converter everything works fine but and i even can set some breakpoints in main.c - another breakpoint in a called function is not being triggered - but then the NET+2 disappears.

I have to flash the *.hex via the ST32 ST-Link Utility to get it back in either bootloader or standard mode.

I really could need some help - if anybody wants to investigate, please write me a PM.

oh yes, you are right - but i am also waiting for the1,27 mm pin connectors