Well, good luck with it! Yes, you seem in the right track for UART and getting the output you need.
I am still learning a lot also, and there is a lot to learn! The comments in the above example refernces the GPIO muxing table in the datasheet, but did not mention that this would be the rp2040 datasheet. The table 2.19.2 function select seems to show a lot more choices than the Pico board has, I'm sure due to the design choices made.
FWIW, I got the debug probe, and I really like it for the ease of use. UART serial goes into it, as well as SWD from the Pico. I can use the one USB from the dongle to my PC with OpenOCD to send .elf code files and not have to mess with the bootsel button. Previously I used an FTDI on UART0 and USB to program, which also works fine.
Not trying to spam, but I really like my workflow using this, especially using little bash shell scripts to automate the programming command. It can be used to debug too, but I'm still learning that using gdb for ARM.
https://www.raspberrypi.com/products/debug-probe/
I am still learning a lot also, and there is a lot to learn! The comments in the above example refernces the GPIO muxing table in the datasheet, but did not mention that this would be the rp2040 datasheet. The table 2.19.2 function select seems to show a lot more choices than the Pico board has, I'm sure due to the design choices made.
FWIW, I got the debug probe, and I really like it for the ease of use. UART serial goes into it, as well as SWD from the Pico. I can use the one USB from the dongle to my PC with OpenOCD to send .elf code files and not have to mess with the bootsel button. Previously I used an FTDI on UART0 and USB to program, which also works fine.
Not trying to spam, but I really like my workflow using this, especially using little bash shell scripts to automate the programming command. It can be used to debug too, but I'm still learning that using gdb for ARM.
https://www.raspberrypi.com/products/debug-probe/
Statistics: Posted by breaker — Tue Sep 24, 2024 10:40 pm