15:45 <ahdeb[m]> Would love a blog post with 2023 recap and 2024 predictions if you dare! Is this the year we'll see complex rust drivers being mainlined?

15:45 <entourloop> Hi everyone, I hope this is the right channel. I have a question about debug_putc() in the code. When EARLY_UART_BASE is specified (which happens by declaring TARGET in config.h), it's supposed to emit characters through the UART channel. The thing is, those characters don't seem to ever appear on the USB-C serial channel, whereas printf() calls work fine using the same interface (after initializing

15:46 <entourloop> the ADT and grabbing uart0's address, of course). Is there a specific way to display those characters?

15:47 <sven> sounds like whatever you use to mux out the serial lines isn't quite ready that early

15:47 <j`ey> my guess is that it work(ed) with the fusb32/hardware serial?

15:48 <sven> when the SBU lines aren't muxed to UART RX/TX those chars will just go to nowhere

15:55 <entourloop> So if I issue a VDM serial command (using macvdmtool instance) and then chainload m1n1 after the RELEASE m1n1, SBU 1/2 should be muxed to the UART channel, right? The question being: is it a matter of getting the right USB-C cable or do I need to prepare a breakout board + an Arduino to issue VDM commands?

15:56 <entourloop> (And to read characters from debug_putc(), I mean)

15:57 <sven> yeah, if you chainload and can see serial over the SBU1/2 lines before that chainload you should be able to see them

15:57 <j`ey> entourloop: and youve set the TARGET variable when building?

16:00 <entourloop> Yes

16:00 <entourloop> OK, thanks for your help. I'll try to get that output :)