while for dynamic linking, those are just symbols and so long as the correct version (normally simply a same or later version) of libc dll is found on the system, it would simply work. while libc deals with the interface between itself and the kernel which can be different on different systems
note that libc and the kernel has tight linkage and that libc and the kernel is normally build in a rather elaborate 'sandboxing' process so that it makes a particular libc works with a particular kernel and all other apps can be dynamically linked to the libc (normally on the major version). and those same apps would work on a different platform / distribution / kernel version as long as the same libc dll version is there
upload-reset sends a 'DTR pulse' on usb-serial and then send the text '1EAF'
http://docs.leaflabs.com/static.leaflab ... 3-rev5-dfu
hence runningThe IDE performs this reset automatically by performing a special sequence of changes on the USB serial port:
- Pulse DTR (high and then low, so that you’ve created a negative edge)
- Write “1EAF” in ASCII over the serial pipe.
This will cause Maple to reset. Only the first 4 bytes after a negative edge of DTR are checked for this command, so it’s important you actually create a negative edge, rather than just ensuring DTR is low.
Code: Select all
this means that it would be the same whether you run the command manually or that arduino ide does it.
the rest of the reset is actually done by the sketch itself (in the usb-serial driver routines)
but i think it is quite possible the 'driver codes' may have some 'bug' or that certain cases is not catered
just 2 cents