Hello,

I'm currently struggling with two similar Microtik routers: RB433L , RB433UAHL.

I was trying hard to run my RB433GL version.
The "L" versions have a lot of small, but hard to use differences.

They are the Lite version of the well-known rb433, with a lower power consomption.
It seems to be rather "Low cost", not "Low power",  whatever doc says.

Their amusing property is that the serial port seems present (RX/TX pads) but not initialized at boot, neither by Linux kernel or by the bootloader, which make debugging difficult (On the TX pad, I just get a suspicious periodic square signal after boot)
Generally net-boot works, console also works fine after small patch.


See my posts:
 https://forum.openwrt.org/viewtopic.php?id=42410
 https://forum.openwrt.org/viewtopic.php?id=42298



I can't get any of them boot an OpenWRT image (trunk of today) using the netboot procedure described here:
http://wp.ayufan.eu/2013/02/the-rb951g-and-openwrt/ (and elsewere).

The router does bootp + tftp procedure.... and seems to ignore the ELF file I give it
(I tried all of
openwrt-ar71xx-mikrotik-vmlinux.elf
openwrt-ar71xx-mikrotik-vmlinux-initramfs.elf
openwrt-ar71xx-mikrotik-vmlinux-initramfs-lzma.elf
openwrt-ar71xx-mikrotik-vmlinux-lzma.elf )

Please set correct file name in your DHCP server.

The netboot procedure does work since I could send the microtik's NPK upgrade package and the routeur did flash itself.
Try ask on mikrotik forum
Apparently, one person did success in booting a kernel https://forum.openwrt.org/viewtopic.php?id=41490 , but no specific details on the file used not the procedure.
I would be very happy to just get to the "kernel boot" point.

Does anyone did play with  this kind of hardware ?

My "L" board is ot of order now, and I've decided not to by more...

Main problem with all "L" versions is developing NAND driver.

Best regards.
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to