It appears the 'beacon' is their service:
strings on beacon got a lot... what makes me feel this is their 'stuff':
could not read eth0 IPv4...
beacon.api.meetlima.com
/home/denis/lima/git/lima-wanserr-firmware/openwrt/staging

A quick look it appears that

pin signal
9 TX
8 RX
7 gnd

This is the unpopulated set of through-hole pads on the daughter card near the RJ45 end of the card. With jtagulator connected

  • 0 - 10
  • 1 - 9
  • 2 - 8
  • GND - 7

jtagulator says:

  • TXD: 1
  • RXD: 2
  • Baud: 115200
  • Data: 0xf5../bin/ash: [ 30 78 66 35 0D 0A 2F 62 69 6E 2F 61 73 68 3A 20 ]

So I think we may have a serial console.

root@OpenWrt:/# uname -a
Linux OpenWrt 2.6.37.6 #1 Wed Feb 5 15:39:35 CET 2014 i486 GNU/Linux
root@OpenWrt:/# ps -elf
PID USER VSZ STAT COMMAND
1 root 988 S init
5 root 0 SW [kworker/u:0]
6 root 0 SW 7 root 0 SW [kworker/u:1]
25 root 0 SW [sync_supers]
27 root 0 SW [bdi-default]
29 root 0 SW 62 root 0 SW [kswapd0]
115 root 0 SW [mtdblock0]
120 root 0 SW [mtdblock1]
125 root 0 SW [mtdblock2]
133 root 0 SW [kworker/0:1]
276 root 0 SW [flush-mtd-unmap]
278 root 0 SWN [jffs2_gcd_mtd1]
299 root 0 SW [khubd]
313 root 1012 S /bin/sh /etc/init.d/rcS S boot
314 root 984 S /bin/ash --login
316 root 980 S logger -s -p 6 -t sysinit
328 root 992 S syslogd -C16
330 root 972 S klogd
344 root 576 S /sbin/hotplug2 --override --persistent --set-worker
416 root 984 S udhcpc -t 0 -i eth0 -H Lima -b -p /var/run/dhcp-eth0
474 root 984 S /sbin/watchdog -t 5 /dev/watchdog
513 root 632 S beacon
519 root 624 S beacon
522 root 996 S crond -c /etc/crontabs -l 5
533 root 780 S /usr/sbin/dropbear -P /var/run/dropbear.1.pid -s -p
535 root 2160 S fwupdater
540 root 976 S telnetd -l /bin/login.sh
574 root 980 R ps -elf

Thanks for the teardown and openwrt info. Should CGC have started honest and kept to honesty then what I' have in my hands would be what I backed rather than this debacle. Honest, clear, transparent, and correct communication failed with CGC. Their continuation along the path toward misinformation and misrepresentation escalated. Yes, sometimes an ernest representation of the truth can appear rude.
mount -t jffs2 /dev/mtdblock1 /overlay
gets you the overlay partition

Thanks - please post the pics publicly and also be certain to show the pads (unpopulated solder places where devices could be attached). If I see something that looks like it could be a serial or JTAG connector then I may follow suit and attach my ejagulator and see if I can find a way to talk to the console or JTAG interface. Then we can share notes and possibly make this hardware useful without the undocumented, hidden, unreviewed, proprietary stuff.

What I see as a definition of what will be useful using this hardware:

  • OpenWRT with ipsec (complete with the administration server interface)
  • bt_sync - node (so we can use the open source bt_sync app rather than Lima stuff)
  • includes FAT, extfs, and maybe ntfs_3g, HFS+ file system support
No