RouterBOARD Groove Series User's Manual
5
RouterBOARD$Groove$series$devices$are$compatible$with$non‐standard$(passive)$Power$over$Ethernet$injectors$
(except$power$over$data$lines)$and$accept$powering$over$up$to$100m$(330$ft)$long$Ethernet$cable$connected$to$
the$Ethernet$port$(J4).$The$board$does+not$work$with$IEEE802.3af$compliant$48V$power$injectors.$
Expansion&Slots&and&Ports&
1. Built$in$2GHz$802.11b/g$wireless,$1x1$MIMO,$station$mode$
2. One$10/100$Ethernet$port,$supporting$automatic$cross/straight$cable$correction$(Auto$MDI/X),$so$you$
can$use$either$straight$or$cross‐over$cable$for$connecting$to$other$network$devices.$The$Ethernet$port$
accepts$8‐30V$DC$powering$from$a$passive$PoE$injector.$
Buttons&and&Jumpers&
•RouterOS$reset$jumper$hole$(no$direct$access,$board$has$removed$from$case)$–$resets$RouterOS$
software$to$defaults.$Must$short$circuit$the$metallic$sides$of$the$hole$(with$a$screwdriver,$for$example)$
and$boot$the$device.$Hold$screwdriver$in$place$until$RouterOS$configuration$is$cleared.$$$
•RouterBOOT$reset$button$(access$through$the$plastic$door)$has$two$functions:$
oHold$this$button$during$boot$time$until$LED$light$starts$flashing,$$
release$the$button$to$reset+RouterOS+configuration+(same$result$as$with$reset$hole)$
oHold$this$button$during$boot$time$longer,$until$LED$turns$off,$$
then$release$it$to$make$the$device$look+for+Netinstall+servers.$
Booting&options&
$
In$case$you$wish$to$boot$the$device$from$network,$for$example$to$use$MikroTik$Netinstall,$hold$the$RESET$
button$of$the$device$when$starting$it$until$the$LED$light$turns$off,$and$Groove$will$start$to$look$for$Netinstall$
servers.$
Onboard&NAND&Storage&Device&
The$RouterBOARD$may$be$started$from$the$onboard$NAND$storage$chip.$As$there$is$no$partition$table$on$the$
device,$the$boot$loader$assumes$the$first$4MiB$form$a$YAFFS$filesystem,$and$executes$the$file$called$“kernel”$
stored$in$the$root$directory$on$that$partition.$It$is$possible$to$partition$the$rest$of$the$medium$by$patching$the$
kernel$source.$
Booting&from&network&
Network$boot$works$similarly$to$PXE$or$EtherBoot$protocol,$and$allows$you$to$the$device$from$an$executable$
image$stored$on$a$TFTP$server.$It$uses$BOOTP$or$DHCP$(configurable$in$boot$loader)$protocol$to$get$a$valid$IP$
address,$and$TFTP$protocol$to$download$an$executable$(ELF)$kernel$image$combined$with$the$initial$RAM$disk$
(inserted$as$an$ELF$section)$to$boot$from$(the$TFTP$server's$IP$address$and$the$image$name$must$be$sent$by$
the$BOOTP/DHCP$server).$
To$boot$the$RouterBOARD$computer$from$Ethernet$network$you$need$the$following:$
•An$ELF$kernel$image$for$the$loader$to$boot$from$(you$can$embed$the$kernel$parameters$and$initrd$image$
as$ELF$sections$called$kernparm$and$initrd$respectively)$
•A$TFTP$server$which$to$download$the$image$from$
•A$BOOTP/DHCP$server$(may$be$installed$on$the$same$machine$as$the$TFTP$server)$to$give$an$IP$address,$
TFTP$server$address$and$boot$image$name$