Debug Interface:USB-C for UART - MatchX Community - MatchX

× This is the optional category header for the Suggestion Box.

Debug Interface:USB-C for UART

More
1 month 3 weeks ago #139 by didebuli
didebuli created the topic: Debug Interface:USB-C for UART
Hi All,

Did any of you try to connect to Debug/UART USB-C Port of MatchX (MX1701) ?

I did try connecting it using a new and tested USB-C cable to 3 different computers but got error about not functioning USB device from Windows and also Linux. On linux errors look like:
--
[126538.523933] usb 3-1: new low-speed USB device number 2 using xhci_hcd
[126538.859992] usb 3-1: device descriptor read/64, error -71
[126539.095986] usb 3-1: device descriptor read/64, error -71
[126539.815929] usb 3-1: new low-speed USB device number 3 using xhci_hcd
[126539.943986] usb 3-1: device descriptor read/64, error -71
[126540.179988] usb 3-1: device descriptor read/64, error -71
[126540.287969] usb usb3-port1: attempt power cycle
[126540.939921] usb 3-1: new low-speed USB device number 4 using xhci_hcd
[126540.940360] usb 3-1: Device not responding to setup address.
[126541.148352] usb 3-1: Device not responding to setup address.
[126541.355920] usb 3-1: device not accepting address 4, error -71
[126541.483918] usb 3-1: new low-speed USB device number 5 using xhci_hcd
[126541.484354] usb 3-1: Device not responding to setup address.
[126541.692346] usb 3-1: Device not responding to setup address.
[126541.899912] usb 3-1: device not accepting address 5, error -71
[126541.899961] usb usb3-port1: unable to enumerate USB device
[126543.511911] usb 3-1: new low-speed USB device number 6 using xhci_hcd
[126543.639914] usb 3-1: device descriptor read/64, error -71
[126544.083929] usb 3-1: device descriptor read/64, error -71
[126544.319890] usb 3-1: new low-speed USB device number 7 using xhci_hcd
[126544.447906] usb 3-1: device descriptor read/64, error -71
[126544.687923] usb 3-1: device descriptor read/64, error -71
[126544.795928] usb usb3-port1: attempt power cycle
--

I tried MANY different USB 2.0 and USB 3.0 ports but on none of them USB device was recognized.


USB-C cable works with other devices so should also not be an issue..


Firmware on GW is 0.0.2 and I can currently not access/configure/upgrade GW from cloud (see "Gateway VPN" thread)..
Also no response yet from support regarding root password.
Did hope to see something through Debug/UART interface but also here no luck yet..

Thanks in Advance !

Regards,
Alexander

Please Log in or Create an account to join the conversation.

More
1 month 2 weeks ago #213 by christinematchx.io
christinematchx.io replied the topic: Debug Interface:USB-C for UART
Dear Alexander,

USB-C port on MatchX gateway has only debugging purpose and does not provide the USB signaling. The UART port is available on the connector and can be used with external USB to UART converter.

UART0_TX and UART0_RX are on A7/B7 and A6/B6 pins of USB-C connector respectively.


Thank you very much!

Christine Yen

Please Log in or Create an account to join the conversation.

More
1 month 2 weeks ago #214 by didebuli
didebuli replied the topic: Debug Interface:USB-C for UART
Thank you very much Christine for this helpful information.
It would be great if this can be mentioned in future versions of MatchX User Guide :-)


By connecting serial RX/TX to USB Port D+ D- pins (and GND to USB GND) and using Baud rate 115200 I could monitor boot process and also log in to system using root password I received from MatchX support team .

This UART access to HLK-7688A might be helpful for recovery in some corner cases..

Please Log in or Create an account to join the conversation.

More
1 month 2 weeks ago #215 by didebuli
didebuli replied the topic: Debug Interface:USB-C for UART
If someone is interested... Here some of output I got on UART:
---
DDR Calibration DQS reg = 00008988

U-Boot 1.1.3 (Feb 28 2017 - 17:05:15)

Board: Ralink APSoC DRAM: 128 MB
relocate_code Pointer at: 87f64000
flash manufacture id: ef, device id 40 19
find flash: W25Q256FV
*** Warning - bad CRC, using default environment

============================================
Ralink UBoot Version: 4.3.0.0
ASIC 7628_MP (Port5<->None)
DRAM component: 1024 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: SPI Flash
Date:Feb 28 2017 Time:17:05:15
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

##### The CPU freq = 580 MHZ ####
estimate memory size =128 Mbytes
RESET MT7628 PHY!!!!!!

Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.

3: System Boot system code via Flash.
## Booting image at bc050000 ...
Image Name: MIPS OpenWrt Linux-3.18.29
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1139208 Bytes = 1.1 MB
Load Address: 80000000
Entry Point: 80000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
No initrd
## Transferring control to Linux (at address 80000000) ...
## Giving linux memsize in MB, 128

Starting kernel ...

[ 0.000000] Linux version 3.18.29 (vadik@mbox) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r49363) ) #25 Mon Aug 13 16:29:52 CEST 2018
[ 0.000000] Board has DDR2
[ 0.000000] Analog PMU set to hw control
[ 0.000000] Digital PMU set to hw control
[ 0.000000] SoC Type: MediaTek MT7688 ver:1 eco:2
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 00019655 (MIPS 24KEc)
[ 0.000000] MIPS: machine is BOX-MX1701
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 08000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
...
...
[ 46.630000] random: nonblocking pool is initialized


MXxxxxxxx login: root
Password:

BusyBox v1.23.2 (2018-05-23 13:46:57 CEST) built-in shell (ash)

--

Note:
I did find some interesting information about MatchX GW hardware on page:
www.cnx-software.com/2017/11/30/matchbox...boxing-and-teardown/

Please Log in or Create an account to join the conversation.

Time to create page: 0.132 seconds