You could set UART1 to output on those pins. What will happen is that it will take over the Tx from UART0, but the Rx of UART0 will still be connected; not sure if that is what you want. I don't exactly know how your unit tests work, so I can't comment on that.

Still on the roadmap, but I'm afraid that still is all I can officially say about this.

There's no explicit reason why those two can't work together... not really more we can say unless we see your code.

It depends on the speed you want to run SPI on. The docs have some more info on that.

You certainly can go faster than that. Check the 'iperf' example, it has settings that are optimized for max throughput, but honestly, even without much optimization you should be able to get faster rates than 30KB/sec. If you can post your code here, we can see if there's something weird going on, ...

So, the thing is, by changing these Menuconfig options, you change the baud rate and flow control of the logging uart, the one that normally the debug messages go to. In other words: you will see the main output on the USB port until your app starts up, and from then on the output is directed to UAR...

Are you using mqtt in one of your components (that is, not the 'main' component)? In that case, you need to add it to the REQUIRES section. See the docs for more info.

Okay, clear, all separate modules. What may be happening here is that the impedance between battery, AMS1117 and ESP32 is too high because you e.g. use jumper wires. Could you try connecting the batteries directly to the 'V5' input on that devboard? The devboard already has a built-in LDO and that w...

Yes, you can, the code you put in there will write the first integer in data_buf to the serial port as four binary bytes, little-endian. You'd need to change the last parameter of uart_write_bytes to sizeof(int)*10 to output all of them. Or did you want to output them as ASCII characters? In that ca...

Yes, you can.