2ABU6-G1
Project: 2ABU6-G1 | |
---|---|
Featured: | Yes |
State | Active |
Members | User:Da Syntax, User:Xopr |
GitHub | No GitHub project defined. Add your project here. |
Description | Minew BLE/Wifi Gateway |
Picture | |
No project picture! Fill in form Picture or Upload a jpeg here |
A.K.A. Minew, MS93MFZ_V1.0, MS93MF6_V1.2, MT7628, Thingoo, 2ABU6-G1 Thanks to Monadnock for a lot of the pin labels
Contents
connecting UART
/!\ don't connect PoE and UART, you will fry the main board; there is a 43v difference in ground planes.
use 3.3V logic to be safe
For best results (prevent console glitches and boot loops), disconnect UART VIN and connect regular (micro) USB power
Run terminal client in 56k 8N1:
minicom -D/dev/ttyUSB0 -b57600 -o
And make sure Hardware Flow Control is off: Ctrl+a, o, choose Serial port setup
, f
install secure shell daemon
gain root access by #updating firmware and run the following:
opkg update opkg install openssh-server vi /etc/ssh/sshd_config
make sure PermitRootLogin yes
is set for (ch)easy login
/etc/init.d/sshd restart
updating firmware
- login to the router (http)
- go to tab
Other
(the last tab) - scroll to
FIRMWARE UPGRADE
- either choose USB and put the firmware as
thingoo-upgrade.bin
on the root of a USB stick - or choose put the firmware on a (local) webserver and fill in its URL
- either choose USB and put the firmware as
troubleshooting
ModemManager
Some Linux distro's hijack the serial port for modem usage; when you're experiencing problems, try and disable the ModemManager service:
systemctl disable ModemManager.service systemctl stop ModemManager.service
Hardware flow control
If your serial is working intermittently, make sure Hardware flow control is off; for minicom it's: Ctrl+a, o, choose Serial port setup
, f
If your terminal glitches or if you have boot loops, make sure you have a proper power supply and don't mix several supplies (i.e. PoE, USB, UART)
pins and connectors
J1
SoM row near the UART (J8) header
- USB D-
- USB D+
- GND
- SD_D2 (MDI_TN_P4)
- SD_D3 (MDI_TP_P4)
- SD_CMD (MDI_RN_P4)
- SD_CLK (MDI_RP_P4)
- SD_CD (MDI_TN_P3)
- SD_WP (MDI_TP_P3)
- SD_D0 (MDI_RN_P3)
- SD_D1 (MDI_RP_P3)
- ETH TXON0 (MDI_TN_P0)
- ETH TXOP0 (MDI_TP_P0)
- ETH RXIN0 (MDI_RN_P0)
- ETH RXIP0 (MDI_RP_P0)
- GND
- UART_RXD0 (GPIO#13)
- UART_TXD0 (GPIO#12)
- PWM_CH0 (GPIO#11, testpoint T11)
J1
SoM row near the SD card slot
- I2C_SD (GPIO#5)
- I2C_SCLK (GPIO#4)
- I2S_CLK (GPIO#3)
- I2S_WS (GPIO#2)
- I2S_DO (GPIO#1)
- I2S_DI (GPIO#0)
- GND
- UART_RXD1 (GPIO#46)
- UART_TXD1 (GPIO#45)
- WLED_N (GPIO#44)
- LINK0 LED1 (GPIO43, active high)
- LINK3
- LINK4
- WPS_RES_PBC
- REF_CLKO (GPIO#38)
- GND
- GND
- VDD (3.5v, testpoint T2)
- VDD (3.5v, testpoint T2)
J8
UART, presumably 3.3v
- Vin (tied to U10-8, EML3276 near SW2, also to testpoint DC4.5V=T20 via switch J13 in on-position)
- RxD
- TxD
- GND
J12
related to nRF52
- GND
- V (3.3v, same potential as T23)
- D ?
- C ?
- Reset?
CON1
IPEX/UFL for Bluetooth, connected to the middle antenna
CON2
Ribbon connector to WS2812 LEDs, flip up to release
also see
- product page
- Monadnock consultancy community blog
- FCC entry
- reference designs compared to the FCC internal pictures and Monadnock's pinout