no awnser yet hum
well here is an update 1st i was able to mcGyver a console cable ( took the opportunity to make it fully null modem with hardware flow control support that way just need to shut down the flow control software wise) for those who wonder : pinout for RJ45 looking from top ( LCD side) pin #1 is on the right . then the rest goes to DB9 . if your cable is tia-368/ A or B (orange on the side) it will look like this
RJ =>db9
w/or,w/br =>1,6 => 4
or => 2 =>3
w/gr =>3 =>2
bl =>4 =>1,6
w/bl =>5 =>5
gr =>7 =>8
br =>l8 =>7
now for the matter at hand : with console calbe i was able to get the output witch basicaly tells me the device ends in a terrible kernel panic and halts i was able to see that it does try to go into bootp but somhow fails ( with netinstall program running and all) not only that i noticed the eth1 is up from the get-go ( i tought that all the ports where dead . )
now i went and looked at the manual(wiki) and it says that there should be opportunity in the boot sequence to go into the bios . on mine with putty it dosent seam to work .
now i opened a ticket by sending an email to mikrotik but so far only thing i received as a reply was a automated email with the ticket number hope i will get a reply this week because so far not impressed if you ask me ...
here is the output from the device
===============================================================
RouterBOOT booter 3.0
RouterBoard 2011UAS-2HnD
CPU frequency: 600 MHz
Memory speed: 225 MHz
Memory size: 128 MB
Press any key within 2 seconds to enter setup..
trying bootp protocol......... failed
kernel loading failed
loading kernel from nand... OK
setting up elf image... OK
jumping to kernel code
Oops[#1]:
Cpu 0
$ 0 : 00000000 00000001 c7d2e284 00000000
$ 4 : c03790fc 00000cc9 ffffffff c03c1bac
$ 8 : c03c5c7f c03c5c7f 00000008 2d646972
$12 : 6e672074 c0312401 000000a6 6f206164
$16 : c7d2e264 c7d28364 c7d2e284 00000001
$20 : c7c21c40 00000004 ffffffff c0345ebc
$24 : 00000018 00000056
$28 : c7c20000 c7c21c10 c0380000 c01e1c80
Hi : 00000009
Lo : 00000009
epc : c01e1d08 yaffs_AddObjectToDirectory+0x114/0x188
Not tainted
ra : c01e1c80 yaffs_AddObjectToDirectory+0x8c/0x188
Status: 1000c203 KERNEL EXL IE
Cause : 0080000c
BadVA : 00000004
PrId : 0001974c (MIPS 74Kc)
Process init (pid: 1, threadinfo=c7c20000, task=c7c1c000, tls=00000000)
Stack : c7c0d000 c7d2e264 00000003 00000000 c7c0d000 00000000 00000000 c01e4980
c7d01efc 00000000 00000000 00000000 ffffffff 0000001c 00000919 00000909
00006180 21800014 00000000 00000000 00000000 0000122b 00000000 c7c0d000
c7d2e250 c7d2e264 c7c0d000 c7c0d000 0000000a 0000001c c7d01efc 00000000
00000000 00000000 7fe7a870 c01e7dbc c7c21d60 c0216fa4 c0338cbd c020bd2c
...
Call Trace:
[<c01e1d08>] yaffs_AddObjectToDirectory+0x114/0x188
[<c01e4980>] yaffs_CheckpointRestore+0x1f4/0x42c
[<c01e7dbc>] yaffs_GutsInitialise+0x4f4/0x1e94
[<c01e10b8>] yaffs_internal_read_super+0x6e8/0x828
[<c01e1238>] yaffs_internal_read_super_mtd+0x14/0x2c
[<c018d9d4>] get_sb_bdev+0x138/0x1b0
[<c01de724>] yaffs_read_super+0x20/0x2c
[<c018ca34>] vfs_kern_mount+0x68/0x11c
[<c018cb40>] do_kern_mount+0x48/0x100
[<c01a5214>] do_mount+0x620/0x694
[<c01a55c4>] sys_mount+0x8c/0xf0
[<c010d524>] stack_done+0x20/0x3c
Code: ae00001c 8e230068 26020020 <ac620004> ae030020 26230068 ae030024 ae220068 8e020008
---[ end trace 5217b01dc2c4aeda ]---
Kernel panic - not syncing: Attempted to kill init!
======================================================