『瀚思彼岸』» 智能家居技术论坛

标题: orvibo vs30zw 网关折腾刷机教程 [打印本页]

作者: zhang00963 时间: 2025-6-19 15:33
标题: orvibo vs30zw 网关折腾刷机教程
本帖最后由 zhang00963 于 2025-6-20 10:47 编辑

本次折腾的 vs30zw 网关，为去年12月在淘宝捡垃圾购入，单价10元，算是电子垃圾在利用，凑巧那段时间在研究手搓智能家居，应淘友要求所以有了本教程。（虽然拖了几个月）

一、设备照片：
配置：
MT7628AN+EM3581+WM8960G方案
RAM：64MByte
Flash：16MByte
[attach]71338[/attach][attach]71339[/attach]
[attach]71340[/attach][attach]71341[/attach]

二、拆机方法：
如下图，箭头所指位置有卡扣，用2个撬棒配合就能撬开。
[attach]71342[/attach]

撬开后的样子
[attach]71343[/attach]

主板背面  （有接口定义，单纯刷机的话不用拆出主板）
[attach]71344[/attach]

三、刷机操作：
①、连接TLL线：注意此接口为3.3V电平，连接错误的电平可能会烧坏芯片IO与USB转TTL工具
②、打开终端软件：波特率为：57600，如果连接正确会看到设备的启动信息（个人喜欢使用MobaXterm ，就以此工具为例）
[attach]71345[/attach]

③、备份固件，有2种方法：使用Flash编程器或者命令行进行备份（这里只讲命令行备份的方法）
a、等待系统启动完成，按回车激活终端
[attach]71346[/attach]

b、使用 sed 命令修改 “/etc/wpa_supplicant.conf” 中的WiFi名称与密码，命令： sed -i -e '/ssid/s/="[^"]*"/="你的新SSID"/' -e '/psk/s/="[^"]*"/="你的新密码"/' /etc/wpa_supplicant.conf
如：sed -i -e '/ssid/s/="[^"]*"/="Office"/' -e '/psk/s/="[^"]*"/="p@ssw0rd"/' /etc/wpa_supplicant.conf ，修改完后使用cat命令确认一下是否修改正确。
[attach]71349[/attach]

c、使用命令：reboot 重启设备或使用命令 wpa_supplicant -B -i rai0 -c /etc/wpa_supplicant.conf 连接你的WiFi
执行ifconfig 命令确认WiFi是否连接成功，在执行 /etc/init.d/firewall stop 关闭防火墙
[attach]71350[/attach]

d、访问获取到的IP地址，这里会有2种情况，rooot无密码和有密码，如遇有密码的情况可以使用 passwd 命令重新设置密码，修改密码后就可以用新设置密码登录
[attach]71351[/attach]
[attach]71352[/attach]

e、备份原始固件：这里有2种方法：使用Flash编程器与命令行备份，这里使用命令行进行备份操作
使用命令 dd if=/dev/mtd0 of=/tmp/firmware_backup.bin  备份整个Flash，命令中的mtd0 来至 /proc/mtd
[attach]71353[/attach]
新建一个终端，使用 cd Desktop 进入当前win桌面，使用命令  scp -r [email protected]:/tmp/firmware_backup.bin ./ 将备份好的固件上传到桌面。
[attach]71354[/attach]

f、更新固件：进入原始固件的更新界面，选择新的固件并取消勾选 Keep settings  ，点击固件更新按钮上传固件进行固件更新。并等待设备重新启动（重启过程中会红灯闪烁，也可以通过串口终端查看启动状态）

[attach]71355[/attach]
[attach]71356[/attach]
[attach]71358[/attach]

g、重新配网：这里有2种方式进行配网，设备刷完固件默认为STA模式
一是通过 uci 命令重新配网，
使用 uci show wireless 命令查看默认无线配置，只需关注 wireless.wlan.xxxx 部分
[attach]71359[/attach]
使用  uci set wireless.wlan.ssid='你的新SSID'  uci set wireless.wlan.key='你的新密码' 其中的encryption值视情况修改。
使用  uci commit wireless 命令提交修改，在使用 wifi reload .  命令重新加载WiFi配置进行WiFi连接，在使用 ifconfig 命令查看WiFi连接情况
[attach]71360[/attach]
[attach]71361[/attach]

二是通过设备上按键的方式，
长按设备正面配网按键大于 10S 后松手，当设备闪烁紫色状态时，就可以连接设备发出名为Zigbee_Gateway_xxxxxx 的WiFi ，xxxxxx 为设备MAC地址后3个Byte
然后使用浏览器访问默认IP地址：192.168.100.1 ，进入无线配置选型卡对默认为New_WiFi 的客户端配置进行修改
[attach]71362[/attach]
在下面2个选项卡中配置您要连接的WiFi名称与加密方式与密码，配置完成后点击页面底部的保存及保存并应用按钮。
[attach]71363[/attach]
配置保存完成后可快速双击设备正面的配网按钮，重新切换为STA模式，将自动连接配置好的目标WiFi，连接成功后为蓝灯闪烁。

访问从终端或上级路由后台获取到的设备IP，无root密码可直接进入，下图就是刷好的系统web界面，到这里刷机配网就完成了。
[attach]71357[/attach]

四、ZigBee模块固件更新  (推荐使用 jlink 进行刷新固件，Python脚本方式不可靠，脚本只用于工作模式探测)
更新固件过程将借助一款名为 Serial.Port.Redirector 的网口转串口工具与名为 Elelabs_EzspFwUtility 的Python脚本和 Simplicity Commander 工具及 JFlash。
a、Serial.Port.Redirector 工具配置在安装完成后添加新的客户端，IP为您设备的IP 端口默认为5001
[attach]71364[/attach]
如下图：5001 端口后面带有RFC2217 字样就是配置好了
[attach]71365[/attach]

b、进入设备终端，可以是串口或者ssh连接，执行命令 zigbee_module_upgrade boot 使模块进入 boot 模式
[attach]71366[/attach]

c、进入 Elelabs_EzspFwUtility  脚本目录执行 python Elelabs_EzspFwUtility.py probe -p com100  命令对zigbee模块进行探测，正常输出如下图（其中的com100 为 Serial.Port.Redirector 工具中配置的虚拟串口号）
[attach]71367[/attach]

d、备份&更新固件（使用 jlink jflash工具进行备份，）注意要正确链接对应SWD接口线路。
按下图进行行固件备份，要选好对应CPU型号后在操作全片读，然后在将读出的固件进行保存。注意读取操作只能在boot模式进行

[attach]71372[/attach]

打开 Simplicity Commander 工具在Select kit中选择jlink 选择Device info 查看芯片是否识别正确，
[attach]71373[/attach]
在Flash选项中选择对应固件，点击下方的flash按钮进行固件烧录。
[attach]71374[/attach]

烧录完成后在设备终端执行 zigbee_module_upgrade app 命令  在执行 python Elelabs_EzspFwUtility.py probe -p com100 进行探测，当出现下图信息时，则表示zigbee固件更新完成
[attach]71375[/attach]

五、ZHA 或 Z2M 接入
HA中的ZHA集成参考下面的图片进行添加，选择设备类型：EZSP  路径填：socket://192.168.172.62:5000 其中的IP修改为您的设备IP。在Z2M中的配置类似就不在贴图了。
[attach]71368[/attach]
[attach]71369[/attach]
[attach]71370[/attach]

六、相关固件和工具下载链接
用到的固件与工具均通过网盘共享：

通过网盘分享的文件：vs30zw 资料
链接: https://pan.baidu.com/s/1uscSQD8DHGccZHpU1tguUQ?pwd=73yt 提取码: 73yt

风险说明：
   ① 刷机有风险，注意备份！！
   ② 刷机操作需要一定动手能力且有相关基础知识，如：焊接/Flash编程/TLL串口连接/终端软件操作/Linux基础命令交互等。。。
   ③ 教程虽尽量简化，但仍有一定操作门槛，请评估是否可独立完成。

作者: zhang00963 时间: 2025-6-20 14:02
关于设备的USB 为HOST模式可以使用下图的转接线，用来连接USB外设，如：USB网卡/USB串口USB
[attach]71386[/attach]
[attach]71387[/attach]

作者: wbdownn 时间: 2025-6-20 16:02
太厉害了，玩不来。谢谢分享

作者: zhang00963 时间: 2025-6-26 12:23

wbdownn 发表于 2025-6-20 16:02
太厉害了，玩不来。谢谢分享

其实也不难，有一定动手能力就可以搞定，回头有空在写个这玩意op固件是咋编译的教程

作者: mikebai521 时间: 2025-6-29 20:40
正好手里有个一样的网关，今天尝试刷机，刷完OPENWRT固件之后能联WIFI，但是联上WIFI以后几分钟就PING不通了，不知道为什么，蓝色的一直灯闪烁，ping不通就进行不了下一步

作者: zhang00963 时间: 2025-6-29 21:07

mikebai521 发表于 2025-6-29 20:40
正好手里有个一样的网关，今天尝试刷机，刷完OPENWRT固件之后能联WIFI，但是联上WIFI以后几分钟就PING不通 ...

有可能是因为AP与STA模式切换导致的IP变动，可以看看串口上或者你路由后台分配的IP，ping不通也不影响刷zigbbe的固件，可以开启AP模式连设备WiFi来检查zigbee模块的状态

作者: mikebai521 时间: 2025-6-30 08:14
IP未变，ping不通的时候openwrt的设置页面也打不开，另外手里有个STM32开发板被我刷成了JLINK，之前用来给亿百特的EFR32刷固件好用，这次拿出来忘记哪个是SWD和SWC了，欧瑞伯网关上标记的应该是JCLK对应SWC，SWDIO对应SWD?

作者: zhang00963 时间: 2025-7-1 11:31

mikebai521 发表于 2025-6-30 08:14
IP未变，ping不通的时候openwrt的设置页面也打不开，另外手里有个STM32开发板被我刷成了JLINK，之前用来给 ...

是的，JCLK对应SWC，SWDIO对应SWD ，IP问题就要用串口看看了，看是WiFi断了还是防火墙问题

作者: mkopl545 时间: 2025-7-2 16:11
op固件更新后的登陆密码是多少

作者: CharlesMichael 时间: 2025-7-2 16:48
技术超强~~~

作者: zhang00963 时间: 2025-7-4 21:37

mkopl545 发表于 2025-7-2 16:11
op固件更新后的登陆密码是多少

没有密码，直接点登录就行

作者: mkopl545 时间: 2025-7-14 20:51
本帖最后由 mkopl545 于 2025-7-14 20:53 编辑

zhang00963 发表于 2025-7-4 21:37
没有密码，直接点登录就行

按教程完成了就是连不上HA

[2025-07-14 20:34:50] [color=var(--success-color)]info: z2m: Logging to console, file (filename: log.log)
[2025-07-14 20:34:50] [color=var(--success-color)]info: z2m: Starting Zigbee2MQTT version 2.4.0 (commit #unknown)
[2025-07-14 20:34:50] [color=var(--success-color)]info: z2m: Starting zigbee-herdsman (4.1.0)
[2025-07-14 20:34:51] [color=var(--success-color)]info: zh:zstack:znp: Opening TCP socket with 192.168.31.131:5000
[2025-07-14 20:34:51] [color=var(--success-color)]info: zh:zstack:znp: Socket connected
[2025-07-14 20:34:51] [color=var(--success-color)]info: zh:zstack:znp: Socket ready
[2025-07-14 20:34:51] [color=var(--success-color)]info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[2025-07-14 20:34:52] [color=var(--success-color)]info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-07-14 20:35:10] [color=var(--error-color)]error: z2m: Error while starting zigbee-herdsman
[2025-07-14 20:35:10] [color=var(--error-color)]error: z2m: Failed to start zigbee-herdsman
[2025-07-14 20:35:10] [color=var(--error-color)]error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-07-14 20:35:10] [color=var(--error-color)]error: z2m: Exiting...
[2025-07-14 20:35:10] [color=var(--error-color)]error: z2m: Error: Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:114:27)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
at Zigbee.start (/app/lib/zigbee.ts:71:27)
at Controller.start (/app/lib/controller.ts:102:13)
at start (/app/index.js:149:5)

作者: zhang00963 时间: 2025-7-18 20:15

mkopl545 发表于 2025-7-14 20:51
按教程完成了就是连不上HA

看您 Zigbee2MQTT log，您没有正确配置适配器类型，这个设备是EZSP 类型的并非ZNP；Elelabs_EzspFwUtility 已经可以通过网络检测到正确的版本，证明固件是运行正常的，需检查您配置的适配器类型与ZHA/Z2M是否可访问设备网络地址

作者: mkopl545 时间: 2025-7-19 16:30

zhang00963 发表于 2025-7-18 20:15
看您 Zigbee2MQTT log，您没有正确配置适配器类型，这个设备是EZSP 类型的并非ZNP；Elelabs_EzspFwUtilit ...

现在日志显示协调器固件版本不兼容是不是我升级没成功
[2025-07-19 16:26:08] info: z2m: Logging to console, file (filename: log.log)
[2025-07-19 16:26:09] info: z2m: Starting Zigbee2MQTT version 2.5.1 (commit #unknown)
[2025-07-19 16:26:09] info: z2m: Starting zigbee-herdsman (4.3.1)
[2025-07-19 16:26:09] info: zh:ember: Using default stack config.
[2025-07-19 16:26:09] info: zh:ember: ======== Ember Adapter Starting ========
[2025-07-19 16:26:09] info: zh:ember:ezsp: ======== EZSP starting ========
[2025-07-19 16:26:09] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-07-19 16:26:09] info: zh:ember:uart:ash: Socket ready
[2025-07-19 16:26:09] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-07-19 16:26:11] info: zh:ember:uart:ash: ======== ASH connected ========
[2025-07-19 16:26:11] info: zh:ember:uart:ash: ======== ASH started ========
[2025-07-19 16:26:11] info: zh:ember:ezsp: ======== EZSP started ========
[2025-07-19 16:26:11] error: z2m: Error while starting zigbee-herdsman
[2025-07-19 16:26:11] error: z2m: Failed to start zigbee-herdsman
[2025-07-19 16:26:11] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-07-19 16:26:11] error: z2m: Exiting...
[2025-07-19 16:26:11] error: z2m: Error: Adapter EZSP protocol version (8) is not supported by Host [13-17].
at EmberAdapter.emberVersion (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1416:19)
at EmberAdapter.initEzsp (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:669:9)
at EmberAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1547:24)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:133:29)
at Zigbee.start (/app/lib/zigbee.ts:68:27)
at Controller.start (/app/lib/controller.ts:101:13)
at start (/app/index.js:149:5)

作者: zhang00963 时间: 2025-7-19 23:04
本帖最后由 zhang00963 于 2025-7-19 23:10 编辑

mkopl545 发表于 2025-7-19 16:30
现在日志显示协调器固件版本不兼容是不是我升级没成功
[2025-07-19 16:26:08] info: z2m: Logging to ...

应该是你Z2M版本太高了对zigbee固件不兼容，我现在还是用的2.1.3 版本，您可以试试降低版本

[attach]72163[/attach]
[attach]72164[/attach]

如果用ZHA的话，可以参考下图 HA版本信息：Core 2025.5.3 /Frontend 20250516.0

[attach]72165[/attach][attach]72166[/attach]

作者: Awe7 时间: 2025-7-24 19:29
老哥，整了一个设备，插上rx tx直接用ttl的3.3供电没反应，网关蓝灯不亮，拔掉ttl直接用供电蓝灯一直长亮。我是不是翻车了0.0

作者: Awe7 时间: 2025-7-24 19:50
本帖最后由 Awe7 于 2025-7-24 23:38 编辑

Awe7 发表于 2025-7-24 19:29
老哥，整了一个设备，插上rx tx直接用ttl的3.3供电没反应，网关蓝灯不亮，拔掉ttl直接用供电蓝灯一直长亮。 ...

刷进去了也能开机进入系统，但我这个主板有个毛病，断电重启开机会一直亮蓝色灯，无法进入系统。但是我在亮蓝灯的大概5秒内插上ttl，主板就会灭蓝灯，进去系统。太奇怪了

作者: zhang00963 时间: 2025-7-24 23:23
本帖最后由 zhang00963 于 2025-7-24 23:31 编辑

Awe7 发表于 2025-7-24 19:29
老哥，整了一个设备，插上rx tx直接用ttl的3.3供电没反应，网关蓝灯不亮，拔掉ttl直接用供电蓝灯一直长亮。 ...

又没让你接3.3V

，只接tx/rx/gnd就可以了，蓝灯常亮要看串口打印，但根据经验来看是硬件问题，大概率是主控或者内存颗粒虚焊，当然也可能是固件问题，具体问题还是要看串口打印

作者: zhang00963 时间: 2025-7-24 23:25

Awe7 发表于 2025-7-24 19:50
openwrt-ramips-mt76x8-orvibo_vs30zw-16m-squashfs-sysupgrade_2 这个固件能直接编程器烧进机器吗？ ...

这个是升级专用的，不是编程器用的

作者: Awe7 时间: 2025-7-24 23:43

zhang00963 发表于 2025-7-24 23:23
又没让你接3.3V，只接tx/rx/gnd就可以了，蓝灯常亮要看串口打印，但根据经验来看是硬件问题，大概率是主控 ...

作者: Awe7 时间: 2025-7-24 23:46
本帖最后由 Awe7 于 2025-7-24 23:51 编辑

zhang00963 发表于 2025-7-24 23:23
又没让你接3.3V，只接tx/rx/gnd就可以了，蓝灯常亮要看串口打印，但根据经验来看是硬件问题，大概率是主控 ...

老哥，这个问题只会出现在第一次上电的时候，进去系统后重启也能正常进入系统，但只要一断电后重新上电就会卡蓝灯0.0

以下是启动日志

root@Zigbee_Gateway_B0AAC6:/#
root@Zigbee_Gateway_B0AAC6:/# reboot
root@Zigbee_Gateway_B0AAC6:/# [  122.100998] device eth0 left promiscuous mode
[  122.109733] br-lan: port 1(eth0) entered disabled state
[  126.638017] reboot: Restarting system
[04030C0E][04030D07]
DDR Calibration DQS reg = 00008988

U-Boot 1.1.3 (Mar 22 2018 - 15:51:37)

Board: Ralink APSoC DRAM:  64 MB
relocate_code Pointer at: 83fb8000
******************************
Software System Reset Occurred
******************************
flash manufacture id: ef, device id 40 18
find flash: W25Q128BV
============================================
Ralink UBoot Version: 4.3.0.0
--------------------------------------------
ASIC 7628_MP (Port5<->None)
DRAM component: 512 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 64 MBytes
Flash component: SPI Flash
Date:Mar 22 2018  Time:15:51:37
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768

##### The CPU freq = 575 MHZ ####
estimate memory size =64 Mbytes
RESET MT7628 PHY!!!!!!
3: System Boot to system code via Flash.
## Booting image at bc050000 ...
Image Name: MIPS OpenWrt Linux-5.15.173
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 2310646 Bytes =  2.2 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, 64
gpio_mode : 0
data : 28623
key:: 64
222222222222222222222222222222

Starting kernel ...

linux_env :
memsize=64 initrd_start=0x00000000 initrd_size=0x0 flash_start=0x00000000 flash_size=0x1000000 console=
[ 0.000000] Linux version 5.15.173 (zhang@zhang) (mipsel-openwrt-linux-musl-gcc (OpenWrt GCC 12.3.0 r24149-125a2e1311) 12.3.0, GNU ld (GNU Binutils) 2.40.0) #0 Fri Dec 27 12:18:24 2024
[ 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 MT7628AN ver:1 eco:2
[ 0.000000] printk: bootconsole [early0] enabled
[ 0.000000] CPU0 revision is: 00019655 (MIPS 24KEc)
[ 0.000000] MIPS: machine is ORVIBO VS30ZW V1.1 (RAM:64Mbyte ROM:16Mbyte)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000003ffffff]
[ 0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 16240
[ 0.000000] Kernel command line: console=ttyS0,57600 rootfstype=squashfs,jffs2
[ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 0.000000] Writing ErrCtl register=00013d80
[ 0.000000] Readback ErrCtl register=00013d80
[ 0.000000] mem auto-init: stack

ff, heap alloc

ff, heap free

ff
[ 0.000000] Memory: 56024K/65536K available (5589K kernel code, 601K rwdata, 1200K rodata, 1176K init, 208K bss, 9512K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS: 256
[ 0.000000] intc: using register map from devicetree
[ 0.000000] CPU Clock: 575MHz
[ 0.000000] timer_probe: no matching timers found
[ 0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6647862422 ns
[ 0.000002] sched_clock: 32 bits at 287MHz, resolution 3ns, wraps every 7469508094ns
[ 0.015462] Calibrating delay loop... 380.92 BogoMIPS (lpj=1904640)
[ 0.087617] pid_max: default: 32768 minimum: 301
[ 0.097923] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.112280] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.137723] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.157089] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.170759] pinctrl core: initialized pinctrl subsystem
[ 0.183057] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.220618] clocksource: Switched to clocksource MIPS
[ 0.232292] NET: Registered PF_INET protocol family
[ 0.242166] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.257314] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.273997] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.289225] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.304372] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.318299] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.331064] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 0.343941] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 0.358191] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.369422] PCI: CLS 0 bytes, default 32
[ 0.382031] workingset: timestamp_bits=14 max_order=14 bucket_order=0
[ 0.402062] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.413544] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.436926] mt7621_gpio 10000600.gpio: registering 32 gpios
[ 0.448308] mt7621_gpio 10000600.gpio: registering 32 gpios
[ 0.459648] mt7621_gpio 10000600.gpio: registering 32 gpios
[ 0.471405] Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
[ 0.485373] printk: console [ttyS0] disabled
[ 0.493867] 10000c00.uartlite: ttyS0 at MMIO 0x10000c00 (irq = 28, base_baud = 2500000) is a 16550A
[ 0.511688] printk: console [ttyS0] enabled
[ 0.511688] printk: console [ttyS0] enabled
[ 0.528157] printk: bootconsole [early0] disabled
[ 0.528157] printk: bootconsole [early0] disabled
[ 0.547893] 10000d00.uart1: ttyS1 at MMIO 0x10000d00 (irq = 29, base_baud = 2500000) is a 16550A
[ 0.567312] spi-mt7621 10000b00.spi: sys_freq: 191666666
[ 0.599530] spi-nor spi0.0: w25q128 (16384 Kbytes)
[ 0.609198] 5 fixed-partitions partitions found on MTD device spi0.0
[ 0.621838] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[ 0.636371] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[ 0.651332] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[ 0.665897] OF: Bad cell count for /palmbus@10000000/spi@b00/flash@0/partitions
[ 0.680736] Creating 5 MTD partitions on "spi0.0":
[ 0.690243] 0x000000000000-0x000001000000 : "ALL"
[ 0.703873] 0x000000000000-0x000000030000 : "Bootloader"
[ 0.715819] 0x000000030000-0x000000040000 : "Config"
[ 0.729141] 0x000000040000-0x000000050000 : "factory"
[ 0.740825] 0x000000050000-0x000001000000 : "firmware"
[ 0.754437] 2 uimage-fw partitions found on MTD device firmware
[ 0.766261] Creating 2 MTD partitions on "firmware":
[ 0.776189] 0x000000000000-0x000000234236 : "kernel"
[ 0.786047] mtd: partition "kernel" doesn't end on an erase/write block -- force read-only
[ 0.804895] 0x000000234236-0x000000fb0000 : "rootfs"
[ 0.814828] mtd: partition "rootfs" doesn't start on an erase/write block boundary -- force read-only
[ 0.834356] mtd: setting mtd6 (rootfs) as root device
[ 0.845638] 1 squashfs-split partitions found on MTD device rootfs
[ 0.858057] 0x000000840000-0x000000fb0000 : "rootfs_data"
[ 0.904162] rt3050-esw 10110000.esw: mediatek esw at 0xb0110000, irq 25 initialized
[ 0.920542] mtk_soc_eth 10100000.ethernet eth0: mediatek frame engine at 0xb0100000, irq 5
[ 0.939748] NET: Registered PF_INET6 protocol family
[ 0.957087] Segment Routing with IPv6
[ 0.964542] In-situ OAM (IOAM) with IPv6
[ 0.972551] NET: Registered PF_PACKET protocol family
[ 0.982718] 8021q: 802.1Q VLAN Support v1.8
[ 0.993759] clk: Disabling unused clocks
[ 1.008416] VFS: Mounted root (squashfs filesystem) readonly on device 31:6.
[ 1.028945] Freeing unused kernel image (initmem) memory: 1176K
[ 1.040726] This architecture does not have kernel memory protection.
[ 1.053493] Run /sbin/init as init process
[ 1.691774] init: Console is alive
[ 1.699216] init: - watchdog -
[ 3.264575] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 3.356385] usbcore: registered new interface driver usbfs
[ 3.367502] usbcore: registered new interface driver hub
[ 3.378185] usbcore: registered new device driver usb
[ 3.397561] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 3.415090] fsl-ehci: Freescale EHCI Host controller driver
[ 3.428510] ehci-platform: EHCI generic platform driver
[ 3.449529] phy phy-10120000.usbphy.0: remote usb device wakeup disabled
[ 3.462848] phy phy-10120000.usbphy.0: UTMI 16bit 30MHz
[ 3.473203] ehci-platform 101c0000.ehci: EHCI Host Controller
[ 3.484619] ehci-platform 101c0000.ehci: new USB bus registered, assigned bus number 1
[ 3.500461] ehci-platform 101c0000.ehci: irq 26, io mem 0x101c0000
[ 3.540633] ehci-platform 101c0000.ehci: USB 2.0 started, EHCI 1.00
[ 3.554366] hub 1-0:1.0: USB hub found
[ 3.562835] hub 1-0:1.0: 1 port detected
[ 3.582539] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.596750] ohci-platform: OHCI generic platform driver
[ 3.607715] ohci-platform 101c1000.ohci: Generic Platform OHCI controller
[ 3.621266] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2
[ 3.637190] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000
[ 3.715902] hub 2-0:1.0: USB hub found
[ 3.724424] hub 2-0:1.0: 1 port detected
[ 3.742420] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 3.767535] init: - preinit -
[ 5.019322] random: jshn: uninitialized urandom read (4 bytes read)
[ 5.205237] random: jshn: uninitialized urandom read (4 bytes read)
[ 5.241727] random: jshn: uninitialized urandom read (4 bytes read)
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 7.778960] jffs2: notice: (301) jffs2_build_xattr_subsystem: complete building xattr subsystem, 7 of xdatum (0 unchecked, 2 orphan) and 8 of xref (2 dead, 0 orphan) found.
[ 7.811750] mount_root: switching to jffs2 overlay
[ 7.826202] overlayfs: upper fs does not support tmpfile.
[ 7.844802] urandom-seed: Seeding with /etc/urandom.seed
[ 8.016467] procd: - early -
[ 8.022699] procd: - watchdog -
[ 8.822930] procd: - watchdog -
[ 8.829920] procd: - ubus -
[ 8.948561] random: ubusd: uninitialized urandom read (4 bytes read)
[ 8.964485] random: ubusd: uninitialized urandom read (4 bytes read)
[ 8.983520] random: ubusd: uninitialized urandom read (4 bytes read)
[ 9.004552] procd: - init -
Please press Enter to activate this console.
[ 10.099800] random: jshn: uninitialized urandom read (4 bytes read)
[ 10.190845] random: ubusd: uninitialized urandom read (4 bytes read)
[ 10.231657] random: ubus: uninitialized urandom read (4 bytes read)
[ 10.478910] kmodloader: loading kernel modules from /etc/modules.d/*
[ 11.253179] i2c_dev: i2c /dev entries driver
[ 11.284074] ralink_gdma: module is from the staging directory, the quality is unknown, you have been warned.
[ 11.321628] gdma-rt2880 10002800.gdma: revision: 3, channels: 16
[ 11.406238] i2c-mt7621 10000900.i2c: clock 400 kHz
[ 11.443777] ralink-i2s 10000a00.i2s: mclk 480MHz
[ 11.552933] Loading modules backported from Linux version v6.1.110-0-g5f55cad62cc9d
[ 11.568197] Backport generated by backports.git v6.1.110-1-0-g965f73fc
[ 11.657961] usbcore: registered new device driver r8152-cfgselector
[ 11.670674] usbcore: registered new interface driver r8152
[ 11.722723] usbcore: registered new interface driver rtl8150
[ 11.772244] usbcore: registered new interface driver usbserial_generic
[ 11.785419] usbserial: USB Serial support registered for generic
[ 11.823558] usbcore: registered new interface driver cdc_xr_usb_serial
[ 11.836611] xr_usb_serial_common: Exar USB UART (serial port) driver
[ 11.883885] usbcore: registered new interface driver asix
[ 11.913267] usbcore: registered new interface driver ax88179_178a
[ 11.942881] usbcore: registered new interface driver cdc_ether
[ 11.973922] usbcore: registered new interface driver cdc_ncm
[ 12.133963] usbcore: registered new interface driver ch341
[ 12.145071] usbserial: USB Serial support registered for ch341-uart
[ 12.192626] usbcore: registered new interface driver cp210x
[ 12.203919] usbserial: USB Serial support registered for cp210x
[ 12.243495] usbcore: registered new interface driver ftdi_sio
[ 12.255129] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 12.625764] mt76_wmac 10300000.wmac: ASIC revision: 76280001
[ 12.662633] mt76_wmac 10300000.wmac: Firmware Version: 20151201
[ 12.674456] mt76_wmac 10300000.wmac: Build Time: 20151201183641
[ 12.730629] mt76_wmac 10300000.wmac: firmware init done
[ 12.922053] mt76_wmac 10300000.wmac: registering led 'mt76-phy0'
[ 13.233302] usbcore: registered new interface driver pl2303
[ 13.244531] usbserial: USB Serial support registered for pl2303
[ 13.404629] PPP generic driver version 2.4.2
[ 13.442227] NET: Registered PF_PPPOX protocol family
[ 13.473245] usbcore: registered new interface driver ti_usb_3410_5052
[ 13.486211] usbserial: USB Serial support registered for TI USB 3410 1 port adapter
[ 13.501563] usbserial: USB Serial support registered for TI USB 5052 2 port adapter
[ 13.691252] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 13.851126] random: jshn: uninitialized urandom read (4 bytes read)
[ 14.771293] urngd: v1.0.2 started.
[ 19.270169] random: crng init done
[ 19.276999] random: 45 urandom warning(s) missed due to ratelimiting
[ 37.383870] br-lan: port 1(eth0) entered blocking state
[ 37.394349] br-lan: port 1(eth0) entered disabled state
[ 37.405103] device eth0 entered promiscuous mode

BusyBox v1.36.1 (2024-12-27 12:18:24 UTC) built-in shell (ash)

______    _                   ___    _
/ _  (_) __ _| |__ ___  ___    / _ \__ _| |_ _____    ____ _ _ _
\// /| |/ _` | '_ \ / _ \/ _ \ / /_\/ _` | __/ _ \ \ /\ / / _` | | | |
/ //\ | (_| | |_) |  __/  __/ / /_\\ (_| | ||  __/\ V  V / (_| | |_| |
/____/_|\__, |_.__/ \___|\___|___\____/\__,_|\__\___| \_/\_/ \__,_|\__, |
      |___/             |_____|                               |___/
-----------------------------------------------------
OpenWrt 23.05-SNAPSHOT, r24149-125a2e1311
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@Zigbee_Gateway_B0AAC6:/#

如果接gnd rt xt 后再上电，主板无法亮蓝灯。也无法开机，目前我找出的办法是先给板子上电接板上面的gnd rt  板亮起蓝灯后再把xt接上，ttl会闪以下灯后板上的蓝灯会熄灭，正常开机闪红灯后正常进入系统.

作者: Awe7 时间: 2025-7-25 01:50

Awe7 发表于 2025-7-24 23:46
老哥，这个问题只会出现在第一次上电的时候，进去系统后重启也能正常进入系统，但只要一断电后重新上电就 ...

测试了五次，通过短接主板的3.3与rt在上电能正常开机，但是不清楚长时间板会不会烧0.0

作者: zhang00963 时间: 2025-7-25 21:38

Awe7 发表于 2025-7-24 23:43
刷进去了也能开机进入系统，但我这个主板有个毛病，断电重启开机会一直亮蓝色灯，无法进入系统。但是我 ...

这个应该是原机uboot有问题，换一个就行

作者: Awe7 时间: 2025-7-25 21:51

zhang00963 发表于 2025-7-25 21:38
这个应该是原机uboot有问题，换一个就行

我直接硬改了，把前面按钮直接接3.3和rt了开机按着上电，等待蓝灯灭后放开. 话说换启动怎么整？直接op内升级换吗？还是ttl

作者: zhang00963 时间: 2025-7-25 22:01
本帖最后由 zhang00963 于 2025-7-25 22:05 编辑

Awe7 发表于 2025-7-25 21:51
我直接硬改了，把前面按钮直接接3.3和rt了开机按着上电，等待蓝灯灭后放开. 话说换启动怎么整？直接op ...

用编程器换，替换原固件的0x000000000000-0x000000030000区域

作者: Awe7 时间: 2025-7-25 23:19

zhang00963 发表于 2025-7-25 22:01
用编程器换，替换原固件的0x000000000000-0x000000030000区域

感谢大佬，用WinHex替换原固件的启动区域可以上电自启了，还有个问题正面的按键只有op配网ap的作用吗？

作者: zhang00963 时间: 2025-7-26 00:34
本帖最后由 zhang00963 于 2025-7-26 00:45 编辑

Awe7 发表于 2025-7-25 23:19
感谢大佬，用WinHex替换原固件的启动区域可以上电自启了，还有个问题正面的按键只有op配网ap的作用吗？ ...

能用就行，正面按键的话只做了配网，正面按键的可以修改 etc/rc.button/config 实现其它功能，背面的复位按键对应 etc/rc.button/reset 也可以修改， config 那个写了注释，会脚本应该可以看懂逻辑

还有就是设备的三色LED，也可以自行指定
[attach]72397[/attach][attach]72398[/attach]

作者: Cacan 时间: 2025-9-11 10:41
openwrt刷好了，但是卡在zigbee更新上了...

用Elelabs_EzspFwUtility脚本输入命令探测不到zigbee模块，后来放弃更新尝试直接使用发现不能在ZHA上使用，直到看到某宝的追评

“对了，em3581的固件需要更新一下才能正常在ZHA或Z2M上使用，可以串口更新也可以jlink烧写”
除了jlink烧写还有其他办法吗

作者: Cacan 时间: 2025-9-11 10:45

Cacan 发表于 2025-9-11 10:41
openwrt刷好了，但是卡在zigbee更新上了...用Elelabs_EzspFwUtility脚本输入命令探测不到zigbee模块，后来 ...

对了，老五那里还有em3585模块，可以把这个网关的em3581换成em3585吗

欢迎光临『瀚思彼岸』» 智能家居技术论坛 (https://bbs.hassbian.com/)