So there is no console output? It's not necessarily RouterBOOT -- Is it not safe to assume it is uboot?
From ROS
[admin@MikroTik] > /system routerboard settings set boot-device=try-ethernet-once-then-nand; /system reboot; put y
From Laptop
docker run --privileged -it --rm --net=host -v /dev/shm/pixie:/image andyshinn/dnsmasq -i asix0 --dhcp-range=192.168.1.100,192.168.1.200 --dhcp-boot=vmlinux --enable-tftp --tftp-root=/image -d -p0 -K --log-dhcp --bootp-dynamic
...
dnsmasq-dhcp: 3204143508 available DHCP range: 192.168.1.100 -- 192.168.1.200
dnsmasq-dhcp: 3204143508 vendor class: ARM__boot
dnsmasq-dhcp: 3204143508 tags: bootp, asix0
dnsmasq-dhcp: 3204143508 BOOTP(asix0) 192.168.1.115 b8:69:f4:87:b0:a1
dnsmasq-dhcp: 3204143508 bootfile name: vmlinux
dnsmasq-dhcp: 3204143508 next server: 192.168.1.2
dnsmasq-dhcp: 3204143508 sent size: 4 option: 1 netmask 255.255.255.0
dnsmasq-dhcp: 3204143508 sent size: 4 option: 28 broadcast 192.168.1.255
dnsmasq-dhcp: 3204143508 sent size: 4 option: 3 router 192.168.1.2
dnsmasq-tftp: sent /image/vmlinux to 192.168.1.115
Does uboot use the same vendor/client during pxe/netboot?
dnsmasq-dhcp: 3204143508 vendor class: ARM__boot
Current ipq44xx support found for these targets (c97c672f9b213)
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-rt-ac58u.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-nbg6617.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4029-mr33.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4029-gl-b1300.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4028-wpj428.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1.dtsi
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1-c1.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4019-a62.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-wre6606.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-jalapeno.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-fritz4040.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-ex61x0v2.dtsi
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-ex6150v2.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-ex6100v2.dts
target/linux/ipq40xx/files-4.14/arch/arm/boot/dts/qcom-ipq4018-a42.dts
What are the other methods of enabling console? There's really no console output at all? Isn't there a way to hard reset by putting a screw driver on the jumper-reset hole?
I'm also unsure if the stock 'routerboot' settings are misleading
[admin@MikroTik] > /system routerboard settings print
auto-upgrade: no
boot-device: nand-if-fail-then-ethernet
cpu-frequency: 716MHz
boot-protocol: bootp
silent-boot: no
protected-routerboot: disabled
reformat-hold-button: 20s
reformat-hold-button-max: 10m