Just flashed OpenWrt 24.10.1 r28597-0425664679 / LuCI (HEAD detached at 2ac26e56) branch 25.103.51521~2ac26e5. The blinking issue is now fixed. I think I was running a snapshot before.
@blogic Sorry for the late reply, somehow I did not get any notifications. I used 115200, when I use 54600, it just outputs the same thing, only slower. I also tried 9600 and the same output. Not sure what I shoudl think about at, apart from this it is bricked.
I initially used USB A and not USB-C cable but now I am using the correct charger.
I tried writing to Software conservancy twice but they never replied. Is there really nobody behind this and I can just throw it in disused electronics then?
@felagund if you believe that the unit is broken, you should contact the shop that you bought it from and ask for a refund or replacement
What baud rate have you set in the the terminal program that you are using to view the output? That has to match the baud rate set in the router. This is set to 115200 by default and is quite difficult to change!
The mere fact that you are seeing something in the terminal program means that your unit is not bricked.
Terminal settings of 115200 8 data bits 1 stop bit No parity and XON/XOFF flow control work for me.
I have been using
sudo screen /dev/ttyUSB0 115200
It worked previously, until I connected the 65W charger: with that charger, the unit worked for 5 minutes and then bricked - no lights, no nothing. Cannot this gibberish be just some signal noise? I guess I should stress that the � come quite slowly - less then one a second. (I havebeen trying this with NOR boot selected - I should have seen something meaningful on the serial console then, no?)
What does lsusb show while it is plugged in.
It should have a line like this.
Bus 001 Device 010: ID 04d9:b534 Holtek Semiconductor, Inc. LGT8F328P Microprocessor
Pull it out and plug it back in again. dmesg should show something like this.
[ 5057.106709] usb 1-11.1: USB disconnect, device number 9
[ 5077.246831] usb 1-11.1: new full-speed USB device number 10 using xhci_hcd
[ 5077.336808] usb 1-11.1: New USB device found, idVendor=04d9, idProduct=b534, bcdDevice= 2.10
[ 5077.336823] usb 1-11.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5077.336830] usb 1-11.1: Product: OpenWrt One
[ 5077.336834] usb 1-11.1: Manufacturer: OpenWrt
[ 5077.336839] usb 1-11.1: SerialNumber: 0000
[ 5077.346572] cdc_acm 1-11.1:1.0: ttyACM0: USB ACM device
[ 5077.346722] usbhid 1-11.1:1.2: couldn't find an input interrupt endpoint
[ 5223.764407] usb 1-11.1: USB disconnect, device number 10
[ 5228.800355] usb 1-11.1: new full-speed USB device number 11 using xhci_hcd
[ 5228.890091] usb 1-11.1: New USB device found, idVendor=04d9, idProduct=b534, bcdDevice= 2.10
[ 5228.890106] usb 1-11.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5228.890113] usb 1-11.1: Product: OpenWrt One
[ 5228.890117] usb 1-11.1: Manufacturer: OpenWrt
[ 5228.890122] usb 1-11.1: SerialNumber: 0000
[ 5228.899773] cdc_acm 1-11.1:1.0: ttyACM0: USB ACM device
This is with NAND selected. I am running Ubuntu 24.0.4.2. The device is detected as a CDC device and mapped to /dev/ttyACM0.
If there is nothing meaningful in the dmesg log then the device is dead. A lot these GAN PSUs that have hit the market recently are rubbish (IMHO). So it may be that it has overloaded the router. I do not know what over volt protection is on the board.
dmesg:
[433366.780508] usb 1-2: USB disconnect, device number 43
[433366.780938] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[433366.780990] cp210x 1-2:1.0: device disconnected
[433368.220484] usb 1-2: new full-speed USB device number 44 using xhci_hcd
[433368.400421] usb 1-2: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[433368.400435] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[433368.400442] usb 1-2: Product: CP2102 USB to UART Bridge Controller
[433368.400447] usb 1-2: Manufacturer: Silicon Labs
[433368.400451] usb 1-2: SerialNumber: 0001
[433368.410221] cp210x 1-2:1.0: cp210x converter detected
[433368.411553] usb 1-2: cp210x converter now attached to ttyUSB0
lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 04f2:b67c Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 029: ID 0451:82ff Texas Instruments, Inc.
Bus 001 Device 030: ID 17ef:6123 Lenovo USBC Wired OpticalMouse
Bus 001 Device 028: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 026: ID 0451:8442 Texas Instruments, Inc.
Bus 001 Device 044: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 001 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
This is with the device connected over serial USB converter (which is lighter, unlike hte OpenWRT one), did I get it right you meant that and not trying to connect over USB to the power connector? If not, when plugged into the computer (both USB-C and USB-A), is says: [433666.117664] usb usb2-port2: over-current condition
which sounds like indeed a powersurge was the problem. Now the thing I do not know is if the unit should be able to handle that or not? I have definitely charged my phone (several ones, probably) and a computer with this charger without issue, I bought it for travelling as it was light and now it was sittting unused.
To clarify. The usb connection I was referring to was the USB C one on the front of the device.
The only thing that should be plugged into the USB C connection on the rear of the device is a USB C power supply that is capable of the supplying 15v DC on request by the router. Plugging a cable from this socket into a USB A socket on your computer will certainly result in a an over current warning. Plugging it into a USB C connector on your computer will probably do the same as it is very unlikely that these sockets will be able to power 15v at the correct current. You are basically asking your computer to act as a power supply.
I am also confused by "This is with the device connected over serial USB converter (which is lighter, unlike hte OpenWRT one)," Any connections from the console USB C port on the router should go directly into a USB port on your computer without any intermediate hardware.
Ah, I see, then it indeed gives:
438237.284456] usb 1-2: USB disconnect, device number 46
[438256.560312] usb 1-2: new full-speed USB device number 47 using xhci_hcd
[438256.720835] usb 1-2: New USB device found, idVendor=04d9, idProduct=b534, bcdDevice= 2.10
[438256.720850] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[438256.720856] usb 1-2: Product: OpenWrt One
[438256.720861] usb 1-2: Manufacturer: OpenWrt
[438256.720865] usb 1-2: SerialNumber: 0000
[438256.724387] cdc_acm 1-2:1.0: ttyACM0: USB ACM device
[438256.724660] usbhid 1-2:1.2: couldn't find an input interrupt endpoint
lsusb gives the same devices as before, minus the UART bridge (that is what I was trying).
However, does this really mean that the device is not bricked? Anything I do (trying the NOR switch, pressing the front button etc. does not indicate any LED activity. When I connect the UART bridge, I always get a blink on the dongle itself every two seconds corresponding to one either a space or � in the console.
This indicates that the hardware is basically OK. What you need to do next is to connect your terminal emulator to /dev/ttyACM0, and press the return key a few times. I think you have probably lost the bootloader and need to restore that. I am not to be around for a few hours now. Feel free to PM me if you wish.
No rush, it has been dead for a month :-).
When I run
sudo screen /dev/ttyACM0 115200
I get:
Cannot exec '/dev/ttyACM0': No such file or directory
So the hypothesis is that a power charge somehow wiped out bootloader? When this happened, I was happily running it in production and was not fiddling with it in any way. It just died sitting there.
I concur the hardware looks OK, but still hard to say. Either way, you might want to follow this thread. It is condensed in the device wiki as well.
Worst case scenario would be following the wiki to restore the NOR/NAND.
Hm, so it is possible the unit produces no blinking through the diods and is still fine hardware-wise, ie all the diods are software controlled?
When I plug in the router into power and connect the front USB-C port to a USB-C port on my computer, I get the /dev/ttyACM0
device.
However, running:
sudo ./mtk_uartboot --aarch64 \
--brom-load-baudrate 115200 \
--bl2-load-baudrate 115200 \
-s /dev/ttyACM0 \
-p ./mt7981-ram-ddr4-bl2.bin \
-f ./openwrt-mediatek-filogic-openwrt_one-nor-bl31-uboot.fip \
&& screen /dev/ttyACM0 115200
I get:
mtk_uartboot - 0.1.1
Using serial port: /dev/ttyACM0
Handshake...
I cannot run it with the device without power, as then I do not have the ACM0 device - what I tried was pluggin it in, running the comand and then unplugging and replugging., but same result.
Also, is it normal that when I touch the chassis with the cable it produces little electrical arcs, like this: https://youtu.be/FS-c_akRbr8 ?
That puts a different turn on things. NO. Logically sparks jumping between cable and chassis could only come from the cable source.
Have you tried another C-C cable.
Edit: Tagged the wrong person. In reply to @felagund.
What about live neutral reversal on the mains and bad chassis isolation.
So, the arcs only happen when I connect my computer with OpenWRT One with USB-C cable. When I unplug the cable (from the front of OpenWRT One), the asrcs stop. This applies both when the front lid is removed and when it is attached. So somehow it seems some electricity from my computer gets to the chasis? I have only a vague notion how electricity works, so I am quite in the dark. Can anyone reproduce this?
I don't think anyone will want reproduce this!
It indicates that you have a major earth or neutral fault either in somewhere in the chain from the electricity company supply tails through to your pc. This could either be a wiring fault, a insulation failure, or a component breakdown.
I meant to ask by that whether it was common. I take that as a no.
It is actually my external monitor - when it is plugged into my computer (via DP over USB-C) and my computer is connected with OpenWRT One, the arcs are there. When I disconnect the monitor from my computer, they go away. When I connect the monitor through usb-A to C cable to OpenWRT one, the arcs come back. when I unplugg the monitor from mains elecricity, they go away.
How dangerous is this? How come I am not electrocuted when I touch the OpenWRT one case? Is it because the voltage is so low due to USB-C?
However, what does this mean for OpenWRT one? Note that it faile in altogether different flat than I am now in, so I am not sure it has anything to do with that. So my original question still stands:
Hm, so it is possible the unit produces no blinking through the diods and is still fine hardware-wise, ie all the diods are software controlled?
As I said above, when I try to run mtk_uartboot
, it never gets beyond listening.
Looks like your monitors power supply has had an insulation breakdown. Disconnect it and do not use it until it is repaired or replaced. It is potentially very dangerous as it may cause a fire or give you a severe electric shock.
Moving forward you have to find a way to connect something to the console port on the router that you can type stuff into and see if there is a response.
Plugging things that spark into the router does not sound good.
As far as I remember the low level pre boot loader responds to "at" commands so typing "at" followed by return may solicit something.
Best of luck.