Dasaita PX6 Wifi and Bluetooth connection issues

[Al_79]

Hi all,

I'm hoping someone can help with a Android 10 Dasaita PX6 that has wifi and bluetooth issues. In only about 1 in every 10 start ups does the unit seem to even turn on wifi and BT. On the other 9 occasions it doesn't even let me switch on wifi manually and BT can neither find nor be found.

I've changed the BT settings from fsc-bw124 in the factory settings to every other option and none of them have a different result with most not connecting at all. I've updated MCU all the way up to 3.8 in increments with the files from Dasaita and I've moved from MAX to VIVID to HAL and no difference in performance. Though I have to say Hal just looks better that the others.

When it does connect it works without issue or interruption until powered off then its a lottery again.

Any help would be greatly appreciated

 

[marchnz]

What has been identified from reading the forums and tried.

 

[Al_79]

Dasaita and forums I've seen recommended using newer MCU and I updated from 3.6 up to newest 3.8 through each version in-between.
Also updated MAX10 to newest version then swapped to vivid then Hal.
Factory reset before Hal.
Tried different phones. Tried to pair from the settings menu not the bt apps.
Tried changing to all the BT modules in the factory settings.
The forums I've seen all look to be variations on these themes. If you can point in the right direction that would be awesome.

 

[Al_79]

What has been identified from reading the forums and tried.

Is there any resource for troubleshooting that I've missed or can I provide anything more?

 

[Bob_Sanders]

Do you have your head unit's wifi bubble turned on? You can't run wifi and wifi bubble at the same time.

 

[Al_79]

Yup that's off should have mentioned that in the troubleshooting that I've done.

 

[Bob_Sanders]

If you have done software updates with no success then it stands to reason it's a hardware error. Check for loose connections on the bt/wifi board. Wiggle it around a little.

 

[EGIS K]

Hi. I have the the same problem... Work everything fine for half year... No is no way to turn WiFi on...

 

[Al_79]

Hi, no unfortunately I still don't have a fix. Dasaita also told me to change to the Bluetooth chip setting but that hasn't worked either. With out Bluetooth or wifi it's just a bad radio i was better off with the stock one.

 

[EGIS K]

Hi, no unfortunately I still don't have a fix. Dasaita also told me to change to the Bluetooth chip setting but that hasn't worked either. With out Bluetooth or wifi it's just a bad radio i was better off with the stock one.

Yes agree with you... Without these options this radio doesn't worst a that money.... I'm looking probably to sent it back, as my one still have a manufacture warranty

 

[EGIS K]

Yes agree with you... Without these options this radio doesn't worst a that money.... I'm looking probably to sent it back, as my one still have a manufacture warranty

Just another question is in what to change this one for Nissan X-Trail?

 

[EGIS K]

Just another question is in what to change this one for Nissan X-Trail?

Hi. I did sort my problem... I did pull out the radio, checked and reconnect the wiring.... Unplug power cable from stereo, plug it back.... Wi-Fi com on itself.... Now second day using stereo, and is no any problem so far... Maybe this helps for you as well...

 

[Xoubir]

Hi there,
Wondering if either of you @EGIS K or @Al_79 have managed to resolve the problem ?

(Im having the problem about ~30% of the times the wifi cant be turned on ( bluetooth is always working though). A simple reboot resolves the issue. I have a (1 week old) dasaita px6 running MTCH_HA_V3.80_1

 

[EGIS K]

Hi there,
Wondering if either of you @EGIS K or @Al_79 have managed to resolve the problem ?

(Im having the problem about ~30% of the times the wifi cant be turned on ( bluetooth is always working though). A simple reboot resolves the issue. I have a (1 week old) dasaita px6 running MTCH_HA_V3.80_1

Hi. I think i resolve my problem... I did update for the system and looks that the wi-fi stays on for all the time... I only nearly a week, after update, but looks it works so far...

 

[Xoubir]

Thanks @EGIS K for the update I'll post here if I make any progress

 

[EGIS K]

Thanks @EGIS K for the update I'll post here if I make any progress

New message from: dasaita-official-store-america (117 )​

Hi there, You can try to update the system: https://www.dropbox.com/s/z2cau61xdme5nbc/HA3_rk3399_10.0_ota(20220120)升级包.zip?dl=0 Download the file in an empty USB driver, connect to the radio and choose updating the system in settings.‌‌‌‍‌‌‍‌‍‍‌‌‍‌‍‍‍‍‌‍‍‍‍‍‌‍‍‌‌‌‍‌‍‌‍‌‌‌‌‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‌​

 

[EGIS K]

​

New message from: dasaita-official-store-america (117 )​

Hi there, You can try to update the system: https://www.dropbox.com/s/z2cau61xdme5nbc/HA3_rk3399_10.0_ota(20220120)升级包.zip?dl=0 Download the file in an empty USB driver, connect to the radio and choose updating the system in settings.‌‌‌‍‌‌‍‌‍‍‌‌‍‌‍‍‍‍‌‍‍‍‍‍‌‍‍‌‌‌‍‌‍‌‍‌‌‌‌‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‌​

This one done a job for me... So far everything works how it's should... After this update...

 

[Al_79]

I thought I'd fixed it with an external USB Bluetooth and wifi dongle but after withing fine all day it's back to the same issue again.

 

[Al_79]

What has been identified from reading the forums and tried.

@marchnz I noticed on px5 threads there was a shell script that delayed wifi/bt initialisation to resolve a similar issue. Would you know if there is something like this floating around for the px6?

 

[Xoubir]

I think have isolated the corresponding errors for the wifi chip activation in the dmesg log file :

Error is that one (rtl88x2cs being the driver for the RTL8822CS wlan/bt chip) :

[  845.098810] rtl88x2cs mmc0:0001:1: rtw_sdio_raw_write: sdio write failed (-110)
[  845.098817] rtl88x2cs mmc0:0001:1: rtw_sdio: WRITE use CMD53
[  845.098822] rtl88x2cs mmc0:0001:1: rtw_sdio: WRITE to 0x00014, 4 bytes
[  845.098826] rtw_sdio: WRITE 00000000: 07 07 01 00
[  845.098992] WARNING: CPU: 5 PID: 101 at drivers/net/wireless/rockchip_wlan/rtl8822cs/os_dep/linux/sdio_ops_linux.c:1329 rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[  845.098995] Modules linked in: 8822cs aic8800_bsp
[  845.099003] CPU: 5 PID: 101 Comm: kworker/5:2 Tainted: G        W         4.19.111+ #271
[  845.099006] Hardware name: Rockchip RK3399 HCT  Board (DT)
[  845.099014] Workqueue: events_freezable mmc_rescan
[  845.099019] pstate: 60400005 (nZCv daif +PAN -UAO)
[  845.099088] pc : rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[  845.099158] lr : rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[  845.099162] sp : ffffff800a92b7e0
[  845.099165] x29: ffffff800a92b7e0 x28: <private info omitted>0 
[  845.099169] x27: <private info omitted>1 x26: ffffffc04489a000 
[  845.099174] x25: <private info omitted>0 x24: ffffffc07237f980 
[  845.099178] x23: <private info omitted>4 x22: ffffffc07237f980 
[  845.099182] x21: <private info omitted>4 x20: ffffffc022245800 
[  845.099187] x19: <private info omitted>4 x18: ffffffffffffffff 
[  845.099191] x17: <private info omitted>0 x16: <private info omitted>0 
[  845.099195] x15: ffffff800974da48 x14: ffffff8089908e6f 
[  845.099199] x13: ffffff8009908e7d x12: ffffff80099092ba 
[  845.099203] x11: ffffff800976e000 x10: 0000000005f5e0ff 
[  845.099208] x9 : 00000000ffffffd0 x8 : 2d2d2d2d2d2d2d2d 
[  845.099212] x7 : <private info omitted>0 x6 : 0000000000000fbe 
[  845.099216] x5 : <private info omitted>0 x4 : <private info omitted>0 
[  845.099221] x3 : ffffffffffffffff x2 : 4b5c3a83ba8c4f00 
[  845.099224] x1 : <private info omitted>0 x0 : <private info omitted>4

Corresponding kernel call stack :

[  845.100519] Call trace:
[  845.100588] rtw_sdio_raw_write+0x1b0/0x2dc [8822cs]
[  845.100656] sdio_io+0x88/0x138 [8822cs]
[  845.100722] rtw_sdio_write_cmd53+0x14/0x1c [8822cs]
[  845.100794] _halmac_sdio_reg_write_32+0x4c/0x68 [8822cs]
[  845.100862] reg_w32_sdio_8822c+0x160/0x188 [8822cs]
[  845.100930] mac_pwr_switch_sdio_8822c+0x200/0x2c4 [8822cs]
[  845.101011] rtw_halmac_poweron+0x4c/0xd0 [8822cs]
[  845.101086] rtl8822c_power_on+0x48/0x98 [8822cs]
[  845.101165] rtw_hal_power_on+0x20/0x58 [8822cs]
[  845.101243] rtw_hal_read_chip_info+0x44/0x90 [8822cs]
[  845.101320] rtw_sdio_primary_adapter_init+0x110/0x15c [8822cs]
[  845.101396] rtw_drv_init+0x8c/0x160 [8822cs]
[  845.101407] sdio_bus_probe+0x108/0x130
[  845.101420] really_probe+0x200/0x2b0
[  845.101431] driver_probe_device+0x58/0x100
[  845.101442] __device_attach_driver+0x90/0xc0
[  845.101454] bus_for_each_drv+0x70/0xc8
[  845.101465] __device_attach+0xdc/0x138
[  845.101476] device_initial_probe+0x10/0x18
[  845.101488] bus_probe_device+0x94/0xa0
[  845.101499] device_add+0x428/0x6d8
[  845.101507] sdio_add_func+0x60/0x88
[  845.101511] mmc_attach_sdio+0x1b4/0x370
[  845.101516] mmc_rescan+0x298/0x388
[  845.101521] process_one_work+0x1a0/0x418
[  845.101526] worker_thread+0x4c/0x3e0
[  845.101530] kthread+0x12c/0x158
[  845.101534] ret_from_fork+0x10/0x18

My specs : PX6 (Dasaita's MTCH)

[    0.000000] Linux version 4.19.111+ (chun@r930) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-2017.05)) #271 SMP PREEMPT Sat Jan 8 17:33:05 CST 2022
[    0.000000] Machine model: Rockchip RK3399 HCT  Board

Not sure though if this points towards a software or hardware issue though :s