TrendNet TEW840-APBO

For Developers
1

This is my first post on the forums, so bear with me please and thank you.

I am wanting to upgrade/replace the OpenWRT fw on this device (currently running Attitude Adjustment) wirh the current version.

This device has a QCA9886 + QCA9653 + QCA8334. It is a 5Ghz 802.11ac 2x2 MIMO PtP Bridge.

I have collected some information from ssh on this device and will add links below for the output from commands from the documentation as well as some pictures showing the device.

If anyone is able to give me some guidance or is willing to lend a hand, I am looking forward to adding these devices to the ToH.

TrendNet TEW840-APBO Images @ imgur

TrendNet TEW840-APBO - Output from SSH

2

https://openwrt.org/docs/guide-developer/add.new.device
https://openwrt.org/docs/guide-developer/adding_new_device

1 Like
3

As per your dmesg this board seems based on the AP152 reference platform. I think, there are already other supported-by-OpenWrt devices based on that, so I'd try to RAM-boot a recent initramfs-snapshot from git master from a similar AP152-device via Serial+Uboot.

Did you already discover the serial-port/uart and connect to it?

1 Like
4

Upper left side, in the 1st photo, by the "nut" ?
One square, three round holes.

2 Likes
5

I had not looked at the photos prior to writing my first post in this thread, only the text outputs.
But yes, I agree, those 4 holes look like a UART.

@kg5iru , try connecting there, and check, if you can get Bootloader output, and attempt to interact with the bootloader.

1 Like
6

Remember not to connect the (probably) 3.3v pin.

1 Like
7

I connected to the pins today and tried to connect over the console. I didn't get anything as far as output. Are there any other options?

uci>stty -F /dev/ttyS0 -a 
speed 115200 baud; rows 0; columns 0; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q;
stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 hupcl -cstopb cread clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon ixoff -iuclc -ixany -imaxbel -iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke
uci>fw_printenv
bootargs=console=ttyS0,115200 root=31:02 rootfstype=jffs2 init=/sbin/init mtdparts=ath-nor0:256k(u-boot),64k(u-boot-env),6336k(rootfs),1408k(uImage),8256k(mib0),64k(ART)
bootdelay=2
baudrate=115200
ipaddr=192.168.1.1
sn=149300467
hw_ver=1.0.0
hw_id=0101006D
pro_id=A03
op_mode=0
wlanaddr=88:DC:96:26:B8:41
dir=
lu=tftp 0x80060000 ${dir}u-boot.bin&&erase 0x9f000000 +$filesize&&cp.b $fileaddr 0x9f000000 $filesize
lf=tftp 0x80060000 ${dir}ap135${bc}-jffs2&&erase 0x9f050000 +0x630000&&cp.b $fileaddr 0x9f050000 $filesize
lk=tftp 0x80060000 ${dir}vmlinux${bc}.lzma.uImage&&erase 0x9f680000 +$filesize&&cp.b $fileaddr 0x9f680000 $filesize
factory_boot=tftp 0x3000000 ap.bin && bootm 0x3000000
ethact=eth0
serverip=192.168.1.37
bootcmd=bootm 0x9f150000
uboot_ver=1.0.1.1
ethaddr=78:2d:7e:1b:42:8a
snextra=EP2KKB8B1000111*****
domain=0
stdin=serial
stdout=serial
stderr=serial
country=000
dualpack=1
remote_sn=EP2KKA8B1000111
remote_addr=78:2d:7e:1b:42:88

Is there another way I can check that the serial port is actually enabled?