See also forum for installation instructions.
If you flash OpenWrt from NetBoot facility, you will lose your RouterOS licence.
The installation of OpenWrt on this board is only possible by using the NetBoot facility - you will boot into the RAMdisk version of OpenWrt and use it to flash the permanent OpenWrt image into NAND. You will need:
Connect your RouterBoard using both ethernet and null modem cable to a PC.
See official howto for more info.
If you select the squashfs image, it may take quite a few minutes for the device to power on.
You will have to run the building process twice, because you will need both RAMdisk image and stock OpenWrt kernel+rootfs.
Build profile should be:
To install openwrt on mikrotik rb133c a serial null modem cable is required on the local machine , an Ethernet cable , in addition to the proper functioning of a tftp and dhcp server on the local machine .
If the rb133c has already mounted openwrt you can directly go to the “ Writing nand ”
Once you have connected the serial cable and ethernet between rb133c and the local PC and you enable the tftp and dhcp server , copy the vmlinux file in the appropriate TFTP server root and start the serial console .
minicom -d / dev / ttyUSB0 115200
then access to the serial console terminal , connect the rb133c power and press any key to blocccare the boot sequence .
RouterBOOT booter 2.18 RouterBoard 133C CPU frequency : 175 MHz Memory size: 16 MB ... Press any key within 2 seconds to enter setup. ... your choice: e - format nand Do you realy want to format your nand? that would result in losing all your data type "yes" to confirm: yes formatting nand... done! ... your choice: p - boot protocol Choose which boot protocol to use: 1 - bootp protocol 2 - dhcp protocol your choice: 2 - dhcp protocol ... your choice: o - boot device Select boot device: e - boot over Ethernet n - boot from NAND, if fail then Ethernet 1 - boot Ethernet once, then NAND o - boot from NAND only b - boot chosen device your choice: n - boot from NAND, if fail then Ethernet ... your choice: x - exit setup ... trying dhcp protocol.... OK resolved mac address 00:26:B9:03:BC:3B Gateway: 10.42.0.1 transfer started .............................. transfer ok, time=2.47s setting up elf image... OK ...
If you already have in rb133c openwrt you can upgrade the firmware via ssh , or even by serial console .
root@OpenWrt:/# mkdir /mnt/kernel ; mount /dev/mtdblock2 /mnt/kernel yaffs: dev is 32505858 name is "mtdblock2" yaffs: passed flags "" yaffs: Attempting MTD mount on 31.2, "mtdblock2" root@OpenWrt:/# mkdir /mnt/rootfs ; mount /dev/mtdblock3 /mnt/rootfs yaffs: dev is 32505859 name is "mtdblock3" yaffs: passed flags "" yaffs: Attempting MTD mount on 31.3, "mtdblock3" root@OpenWrt:/# passwd Changing password for root New password: Retype password: Password for root changed by root
Now back to your local machine , disable the DHCP server , then :
sudo ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up scp openwrt-adm5120-rb1xx-vmlinux.elf email@example.com:/mnt/kernel/kernel scp openwrt-adm5120-rb1xx-rootfs.tar.gz firstname.lastname@example.org:/mnt/rootfs
Then return in the serial console to decompress the rootfs and restart the rb133c .
root@OpenWrt:/# cd /mnt/rootfs/ root@OpenWrt:/mnt/rootfs# gunzip openwrt-adm5120-rb1xx-rootfs.tar.gz root@OpenWrt:/mnt/rootfs# tar xf openwrt-adm5120-rb1xx-rootfs.tar root@OpenWrt:/mnt/rootfs# rm openwrt-adm5120-rb1xx-rootfs.tar root@OpenWrt:~# reboot
At this point the rb133c should listen to telnet to 192.168.1.1 .
Disable ANY firewall on your PC.
Atheros-based card are supported. The device doesn't work with Broadcom cards, since kmod-ssb causes kernel panic at startup.
|Vendor||MikroTik, ADMtek (Infineon)|
|System-On-Chip||ADM5120 (Little Endian)|
|CPU Speed||175 Mhz|
|Flash size||64/128 MiB|
|RAM||32 MiB SDRAM (16 MiB on RB133C)|
|Wireless||3x Type III miniPCI slot (1x on RB133C)|
|Ethernet||3 x 10/100 Base-TX Ethernet Ports (with Auto MDI/MDIX) (1 on RB133C)|