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

 找回密码
 立即注册
楼主: zyz2000

[智能音箱] 小爱音箱1.62.8版拦截器+修改固件

  [复制链接]

65

主题

853

帖子

3044

积分

论坛元老

Rank: 8Rank: 8

积分
3044
金钱
2184
HASS币
40
发表于 2021-3-30 21:31:25 | 显示全部楼层
本帖最后由 plutosherry 于 2021-3-30 21:32 编辑

拦截词的语法格式是什么样的?
是这样么?其中:
192.168.1.10 是nodered的地址
user:pass 分别改成nodered设置的用户名和密码?如此可否?
切灯|curl --insecure -u user:pass –connect-timeout 2 -m 4 -s --data asr=$asr --data res=$res https://192.168.1.10:1880/endpoint/miai|

回复

使用道具 举报

0

主题

43

帖子

150

积分

注册会员

Rank: 2

积分
150
金钱
107
HASS币
0
发表于 2021-4-5 16:50:22 | 显示全部楼层
本帖最后由 mu0lang 于 2021-4-5 17:17 编辑

http://192.168.0.156:7373 ,IP替换成你的音箱地址,这个网址打不开啊,我的192.168.1.126:7373,7373端口是真的打开了么?

终于能上传了,可是出现点上传一会儿后显示  192.168.1.126
未发送任何数据。,我把名字中1.68.2去掉也不行。。

回复

使用道具 举报

0

主题

43

帖子

150

积分

注册会员

Rank: 2

积分
150
金钱
107
HASS币
0
发表于 2021-4-5 17:02:23 | 显示全部楼层
把xiaoai和keywords放到data目录后可以手动运行,,,怎么手动运行??
回复

使用道具 举报

1

主题

24

帖子

762

积分

高级会员

Rank: 4

积分
762
金钱
738
HASS币
0
发表于 2021-4-21 08:26:23 | 显示全部楼层
"http://192.168.2.7:22222/要说的话"

为啥TTS后,还会自己说一段英文
回复

使用道具 举报

1

主题

24

帖子

762

积分

高级会员

Rank: 4

积分
762
金钱
738
HASS币
0
发表于 2021-4-21 13:38:13 | 显示全部楼层
大佬,你的小爱拦截器有源码么,现在遇到了一些问题,想看看源码修一下。
回复

使用道具 举报

0

主题

15

帖子

44

积分

新手上路

Rank: 1

积分
44
金钱
28
HASS币
0
发表于 2021-5-29 21:55:28 | 显示全部楼层
大佬,我的小爱变砖了,主要是想让他能用。现在已经通过ttl的方式刷了ROM,刷完后经常性的死机,是什么原因呢?接下来该怎么处理?死机的时候xhshell上也没啥日志输出。
回复

使用道具 举报

4

主题

23

帖子

900

积分

论坛技术达人

积分
900
金钱
867
HASS币
50
 楼主| 发表于 2021-5-30 07:03:46 来自手机 | 显示全部楼层
ghoust 发表于 2021-5-29 21:55
大佬,我的小爱变砖了,主要是想让他能用。现在已经通过ttl的方式刷了ROM,刷完后经常性的死机,是什么原因 ...

按理说Linux的系统不容易死机。
死机的时候语音还能唤醒吗?
回复

使用道具 举报

0

主题

15

帖子

44

积分

新手上路

Rank: 1

积分
44
金钱
28
HASS币
0
发表于 2021-5-30 17:29:46 | 显示全部楼层
zyz2000 发表于 2021-5-30 07:03
按理说Linux的系统不容易死机。
死机的时候语音还能唤醒吗?

就是放着歌,一首歌完了之后就没声了,没有固定频率,有时能放半天,有时几首就不行了,唤不醒,按键也没反应,只能拔掉电源。连续插拔几次,感觉系统又被还原了,因为启动的时候会提示连接WIFI,并且登录root需要也需要密码了,连上WIFI后问题依旧。刷ROM前的症状是,一直转圈,唤不醒,按键没反应,反复拔电也没用。
回复

使用道具 举报

0

主题

15

帖子

44

积分

新手上路

Rank: 1

积分
44
金钱
28
HASS币
0
发表于 2021-5-30 17:40:45 | 显示全部楼层
唤不醒的时候,通过串口发reboot指令,出现S12A login:,输入root后还会显示SN,感觉系统还在运行着的。
回复

使用道具 举报

0

主题

15

帖子

44

积分

新手上路

Rank: 1

积分
44
金钱
28
HASS币
0
发表于 2021-5-30 17:49:56 | 显示全部楼层
刚刚启动试了下,报这个错了,一直转圈。

AXG:BL1:d95c53:a4926f;FEAT:E0DC318C:2000;POC:F;EMMC:800;NAND:0;READ:0;0.0;CHK:0;
sdio debug board detected 
TE: 23344

BL2 Built : 18:30:39, Aug 28 2018. axg g56303a2-dirty - liang.yang@droid11-sz

set vcck to 1140 mv
set vddee to 1070 mv
Board ID = 2
CPU clk: 1200MHz
DDR low power enabled
DDR3 chl: Rank0 16bit @ 792MHz
bist_test rank: 0 2e 08 55 33 11 56 29 03 4f 37 15 5a 00 00 00 00 00 00 00 00 00 00 00 00 625   - PASS
Rank0: 256MB(auto)-2T-11
AddrBus test pass!
NAND init
page0 page0->bbt:
0000000000000000000000000000000000000000000000000000000000000000
page0 bbt:
0000000000000000000000000000000000000000000000000000000000000000
Load FIP HDR from NAND, src: 0x0000c000, des: 0x01700000, size: 0x00004000
Load BL3x from NAND, src: 0x00010000, des: 0x01704000, size: 0x00080000
NOTICE:  BL31: v1.3(release):a1a8551
NOTICE:  BL31: Built : 15:59:55, Nov  9 2017
NOTICE:  BL31: AXG normal boot!
NOTICE:  BL31: BL33 decompress pass
[Image: axg_v1.1.3268-b93dd79 2017-12-01 14:22:18 huan.biao@droid12]
OPS=0x42
4e 29 b0 92 d4 20 54 14 9b 78 15 fb bl30:axg ver: 9 mode: 0
bl30:axg thermal0
[0.014613 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2015.01 (Dec 24 2019 - 07:00:02), Build: jenkins-Mico_s12a_ota_publish-379

DRAM:  256 MiB
Relocation Offset is: 0ef17000
register usb cfg[0][1] = 000000000ff89690
NAND:  nand id: 0x98 0xda 
256MiB, SLC, page size: 2048, OOB size: 64
NAND device id: 98 da 90 15 f6 16 
NAND device: Manufacturer ID: 0x98, Chip ID: 0x98 (Toshiba A revision NAND 2Gib TC58BVG1S3HTA00 )
oob avail size 6
Creating 1 MTD partitions on "A revision NAND 2Gib TC58BVG1S3HTA00 ":
0x000000000000-0x000000200000 : "bootloader"
A revision NAND 2Gib TC58BVG1S3HTA00  initialized ok
nand id: 0x98 0xda 
256MiB, SLC, page size: 2048, OOB size: 64
NAND device id: 98 da 90 15 f6 16 
NAND device: Manufacturer ID: 0x98, Chip ID: 0x98 (Toshiba A revision NAND 2Gib TC58BVG1S3HTA00 )
PLANE change!
aml_nand_init :oobmul=1,oobfree.length=8,oob_size=64
oob avail size 8
bbt_start=20 env_start=24 key_start=32 dtb_start=40
nbbt: info size=0x800 max_scan_blk=24, start_blk=20
nbbt : phy_blk_addr=20, ec=0, phy_page_addr=0, timestamp=1
nbbt free list: 
blockN=21, ec=-1, dirty_flag=0
blockN=22, ec=-1, dirty_flag=0
blockN=23, ec=-1, dirty_flag=0
aml_nand_scan_rsv_info 1251: page_num=1
aml_nand_scan_rsv_info 1254
nbbt valid addr: 280000
aml_nand_bbt_check 1389 bbt is valid, reading.
aml_nand_read_rsv_info:397,read nbbt info to 280000
nenv: info size=0x10000 max_scan_blk=32, start_blk=24
aml_nand_read_page_hwecc 2978 read ecc failed here at at page:1664, blk:26 chip[0]
blk check good but read failed: 340000, -74
aml_nand_read_page_hwecc 2978 read ecc failed here at at page:1696, blk:26 chip[0]
blk check good but read failed: 350000, -74
ECC error, scan ONE block exit
nenv : phy_blk_addr=24, ec=2, phy_page_addr=0, timestamp=426
nenv free list: 
blockN=25, ec=1, dirty_flag=1
blockN=27, ec=0, dirty_flag=1
blockN=28, ec=-1, dirty_flag=0
blockN=29, ec=-1, dirty_flag=0
blockN=30, ec=-1, dirty_flag=0
blockN=31, ec=-1, dirty_flag=0
aml_nand_scan_rsv_info 1251: page_num=32
aml_nand_scan_rsv_info 1254
nenv valid addr: 310000
nkey: info size=0x8000 max_scan_blk=40, start_blk=32
nkey : phy_blk_addr=33, ec=0, phy_page_addr=0, timestamp=2
nkey free list: 
blockN=32, ec=0, dirty_flag=1
blockN=34, ec=-1, dirty_flag=0
blockN=35, ec=-1, dirty_flag=0
blockN=36, ec=-1, dirty_flag=0
blockN=37, ec=-1, dirty_flag=0
blockN=38, ec=-1, dirty_flag=0
blockN=39, ec=-1, dirty_flag=0
aml_nand_scan_rsv_info 1251: page_num=16
aml_nand_scan_rsv_info 1254
nkey valid addr: 420000
ndtb: info size=0x20000 max_scan_blk=44, start_blk=40
ndtb : phy_blk_addr=41, ec=5, phy_page_addr=0, timestamp=12
ndtb free list: 
blockN=40, ec=5, dirty_flag=1
blockN=42, ec=-1, dirty_flag=0
blockN=43, ec=-1, dirty_flag=0
aml_nand_scan_rsv_info 1251: page_num=64
aml_nand_scan_rsv_info 1254
ndtb valid addr: 520000
tpl: off 8388608, size 8388608
 NAND bbt detect factory Bad block at c000000 
 NAND bbt detect factory Bad block at c020000 
Creating 6 MTD partitions on "A revision NAND 2Gib TC58BVG1S3HTA00 ":
0x000000800000-0x000001000000 : "tpl"
0x000001000000-0x000001800000 : "boot0"
0x000001800000-0x000002000000 : "boot1"
0x000002000000-0x000004000000 : "system0"
0x000004000000-0x000006000000 : "system1"
0x000006000000-0x000010000000 : "data"
 NAND bbt detect factory Bad block at c000000 
 NAND bbt detect factory Bad block at c020000 
A revision NAND 2Gib TC58BVG1S3HTA00  initialized ok
aml_key_init 170
MMC:   
uboot env amlnf_env_read : ####
aml_nand_read_rsv_info:397,read nenv info to 310000
In:    serial
Out:   serial
Err:   serial
[store]To run cmd[amlnf dtb_read 0x1000000 0x20000]
sub cmd dtb
new argv[1] dtb_read
do_dtb_ops(): argc 4
arg 0: amlnf
arg 1: dtb_read
arg 2: 0x1000000
arg 3: 0x20000
do_dtb_ops() read
amlnf_dtb_read: ####
aml_nand_read_rsv_info:397,read ndtb info to 520000
do_dtb_ops(): 131072 bytes read : OK
      Amlogic multi-dtb tool
      GZIP format, decompress...
      Multi dtb detected
      Multi dtb tool version: v2 .
      Support 5 dtbs.
        aml_dt soc: xiaomi platform: s12a variant: v01
        dtb 0 soc: xiaomi   plat: s12   vari: v1
        dtb 1 soc: xiaomi   plat: s12a   vari: v01
        dtb 2 soc: xiaomi   plat: s12c   vari: v01
        dtb 3 soc: xiaomi   plat: s12c   vari: v02
        dtb 4 soc: xiaomi   plat: s12c   vari: v03
      Find match dtb: 1
amlkey_init() enter!
amlnf_key_read key data len too much
aml_nand_read_rsv_info:397,read nkey info to 420000
[EFUSE_MSG]keynum is 4
InUsbBurn
noSof
Hit Enter or space or Ctrl+C key to stop autoboot -- :  0 
HAVE SN Code ...
Saving Environment to aml-storage...
uboot env amlnf_env_save : ####
aml_nand_save_rsv_info:656, nenv: valid=1, pages=32
release_free_node 61: bitmap=fffff
release_free_node 74: bitmap=ffff7
aml_nand_save_rsv_info:716,save info to 320000
env free blk erase failed -5
aml_nand_save_rsv_info:656, nbbt: valid=1, pages=1
aml_nand_save_rsv_info:716,save info to 280800
aml_nand_write_rsv:520,write info to 280800
blk check good but write failed: 280800, -5
update nand env FAILED!
[burnup]Rd:Up sz 0x3ac440 to align 0x1000
save_power_post ...
## Booting Android Image at 0x01080000 ...
reloc_addr =f0348e0
copy done
load dtb from 0x1000000 ......
      Amlogic multi-dtb tool
      Single dtb detected
   Uncompressing Kernel Image ... OK
   kernel loaded at 0x01080000, end = 0x017a7808
   Loading Ramdisk to 0eea7000, end 0f004b82 ... OK
   Loading Device Tree to 000000000ee9c000, end 000000000eea6807 ... OK

Starting kernel ...

uboot time: 1842977 us
domain-0 init dvfs: 4
[    0.278138@0] ff803000.serial: clock gate not found
get key is 0x00 , curr_boot is boot1
Booting from boot1
/dev/mtdblock5 is ready now.
[    0.813860@2] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)
[    0.813983@2] i2c i2c-1: token 1, master_no(1) 300K addr 0x3c
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
Please press Enter to activate this console.
[    4.775123@0] cyttsp 0-0008: Failed to request firmware touch.cyacd
[    4.775751@0] cyttsp 0-0008: Failed to update firmware;
[    6.761488@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 395:2048, written 0 bytes
[    6.774444@2] ubi0 error: do_sync_erase: cannot erase PEB 395, error -5
[    6.775536@2] ubi0 error: __erase_worker: failed to erase PEB 395, error -5
[    6.776648@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 396:2048, written 0 bytes
[    6.779499@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 397:2048, written 0 bytes
[    6.780233@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 333:112640, written 0 bytes
[    6.789982@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 398:2048, written 0 bytes
[    6.800302@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 399:2048, written 0 bytes
[    6.810043@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 400:2048, written 0 bytes
[    6.819684@0] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 401:2048, written 0 bytes
[    6.820454@0] UBIFS error (ubi0:0 pid 934): ubifs_leb_write: writing 2048 bytes to LEB 16:108544 failed, error -5
[    6.820620@0] UBIFS error (ubi0:0 pid 934): do_commit: commit failed, error -5
[    6.820674@0] UBIFS assert failed in ubifs_tnc_close at 2886 (pid 934)
[    6.873347@2] ubi0 error: ubi_io_mark_bad: read-only mode
[    6.878671@2] ubi0 error: do_work: work failed with error code -30
[    6.884795@2] ubi0 error: ubi_thread: ubi_bgt0d: work failed with error code -30
[    7.672230@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 395:2048, written 0 bytes
[    7.684705@1] ubi0 error: do_sync_erase: cannot erase PEB 395, error -5
[    7.685820@1] ubi0 error: __erase_worker: failed to erase PEB 395, error -5
[    7.686932@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 396:2048, written 0 bytes
[    7.689773@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 397:2048, written 0 bytes
[    7.690504@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 333:112640, written 0 bytes
[    7.700347@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 398:2048, written 0 bytes
[    7.710122@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 399:2048, written 0 bytes
[    7.719912@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 400:2048, written 0 bytes
[    7.729643@3] ubi0 error: ubi_io_write: error -5 while writing 2048 bytes to PEB 401:2048, written 0 bytes
[    7.730413@3] UBIFS error (ubi0:0 pid 948): ubifs_leb_write: writing 2048 bytes to LEB 16:108544 failed, error -5
[    7.730583@3] UBIFS error (ubi0:0 pid 948): do_commit: commit failed, error -5
[    7.730634@3] UBIFS assert failed in ubifs_tnc_close at 2886 (pid 948)
[    7.783642@1] ubi0 error: ubi_io_mark_bad: read-only mode
[    7.788981@1] ubi0 error: do_work: work failed with error code -30
[    7.795110@1] ubi0 error: ubi_thread: ubi_bgt0d: work failed with error code -30
[    7.875745@1] name: mac_wifi, size 17
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

Archiver|手机版|小黑屋|Hassbian

GMT+8, 2024-11-16 19:47 , Processed in 0.384067 second(s), 30 queries .

Powered by Discuz! X3.4

Copyright © 2001-2021, Tencent Cloud.

快速回复 返回顶部 返回列表