<dryimpact>
Hello. The serial connection of a router I'm currently working on (mediatek), only works in u-boot. After running any firmware (including factory), stdout is empty. Like it's not printing any kernel logs, but works (at least the factory image). There haven't been any attempts to support this device yet. I'd really appreciate any tips I can get.
<dryimpact>
Sorry if this isn't the correct place to ask (I already tried the forum).
<Habbie>
any chance the baud rate changes after uboot?
<dryimpact>
I think not? The extracted fdt from the factory image doesn't note any baud rate, but there is especially no garbage text appearing. (iirc, I even checked with a logic analyzer: nothing)
<dryimpact>
I just tried the most common rates from 4800 to 921600 and input doesnt work on any of them.
<dwfreed>
is it maybe just not using the serial as console?
<dryimpact>
Sorry I cant quite follow. I did rebuild an image of a supported device with very similar specs and the behaviour was exactly the same. Do you mean that uboot does something weird?
<dwfreed>
well, possibly the device tree doesn't have the correct configuration for the serial (if you've got shell, make sure there's a tty device for it, name varies), or that the kernel parameters do not specify console=<serial tty> for the correct name
<dwfreed>
if you've got shell, you can try manually running a getty on the serial tty
<damo22>
dryimpact: the OS might not be trying to use the serial, or is misconfigured in the device tree so doesnt work correctly
<dryimpact>
Um, I think a forum member and me kind of already tried those things? We compared the uart registers and only nr.1 was active. We also tried setting console to the mmio32 address via fdt and bootargs. (https://forum.openwrt.org/t/214784). Should I try removing the console arg from fdt and uboot entirely?
<damo22>
dryimpact: if serial works in uboot, can you check which uart it is using?
<dryimpact>
There is `coninfo` which lists "serial 80000003 ...". But that doesn't map to a memory address of any of the serial ports.
<damo22>
what is the exact output of that command can you paste to a paste service?
<dryimpact>
um, my first thought was to rebuild the linksys-e8450 image with the dts modified to include these uarts. Do I need to keep the "serial@11xxxxxx"?
<dryimpact>
oh wait nvm, I think the fdt command can also write
<damo22>
im looking at uboot source code, there is :
<damo22>
&pinctrl { uart0_pins: uart0 {
<damo22>
mux {
<damo22>
groups = "uart0_0_tx_rx" ;
<damo22>
function = "uart";
<damo22>
etc
<schmars[m]>
are you trying to unbrick this e8450 from the "kiss of death"?
<dryimpact>
I just ran the new image but sadly still exact same behaviour. This is the edited dtsi if you want to check: https://0x0.st/XDDo.c I had to remove the 5th uart, otherwise the build said something about the interrupt size not being a multiple of 12.
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #openwrt-devel
<dryimpact>
schmars[m] oh sorry I missed your message. I'm actually trying to get a serial connection to openwrt of an unsupported device. Its hardware is just very similar to the linksys. (serial to uboot works)
<Habbie>
is there a ready-to-run docker image with apk? i recall grabbing something from aparcar months ago and importing it, but perhaps an easier option exists now?
digitalcircuit has quit [Quit: Signing off from Quassel - see ya!]
digitalcircuit has joined #openwrt-devel
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
minimal has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
khrbtxyz has joined #openwrt-devel
mrkiko has quit [Quit: leaving]
sorinello has quit [Ping timeout: 480 seconds]
<dryimpact>
Hello. I asked here yesterday already, but I am just really lost at this point. My mtk router boots into u-boot and the factory openwrt just fine, but the serial connection only works while in u-boot. After starting the boot process nothing is logged to the terminal, not even any kernel logs. We already checked different baudrates and the coninfo
<dryimpact>
command in u-boot suggests pinmuxing. The fdt doesn't mention anything about uart related pinmux, and it also shouldn't since the serial output doesnt work with that anyway. factory fdt: https://0x0.st/XD4z.txt ; coninfo https://0x0.st/XDGf.txt