Hello,
Thanks it worked nicely, adding theIn addition I enjoyedsince it made the pico to wait until I open the connection ![:-)]( "Smile")
Picotool.exe now works.
From an include point of view, there is onlyincluded.
Without stdio.h it throws
" include '<stdio.h>' or provide a declaration of 'printf' "
From this perspective, I can't really follow the discussion, although I feel that I have to because I need to include some less trivial libraries, such as
hardware_pwm\include\hardware\pwm.h>
hardware_adc\include\hardware\adc.h>
hardware_sync\include\hardware\sync.h>
I think that dealing with errors caused by incompatible libraries is one of the most frustrating tasks. Libraries with the same name in different locations, which are hidden by other libraries, could be an excellent prerequisite for this if you are not sufficiently aware of it.
But for now, it's working—thanks to everyone!
Martin
Thanks it worked nicely, adding the
Code:
# enable usb output, disable uart output pico_enable_stdio_usb(blink 1) pico_enable_stdio_uart(blink 0)Code:
#if LIB_PICO_STDIO_USB while (!stdio_usb_connected()) { sleep_ms(100); } #endif
Picotool.exe now works.
From an include point of view, there is only
Code:
#include <stdio.h>#include "pico/stdlib.h"Without stdio.h it throws
" include '<stdio.h>' or provide a declaration of 'printf' "
From this perspective, I can't really follow the discussion, although I feel that I have to because I need to include some less trivial libraries, such as
hardware_pwm\include\hardware\pwm.h>
hardware_adc\include\hardware\adc.h>
hardware_sync\include\hardware\sync.h>
I think that dealing with errors caused by incompatible libraries is one of the most frustrating tasks. Libraries with the same name in different locations, which are hidden by other libraries, could be an excellent prerequisite for this if you are not sufficiently aware of it.
But for now, it's working—thanks to everyone!
Martin
Statistics: Posted by MartinHill — Fri Jan 30, 2026 7:48 pm