This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[参考译文] CC3301:使用一个生产日期代码生成的新电路板上出现 WiFi 问题、替换为不同的生产日期代码时也能正常工作

Guru**** 2478765 points
Other Parts Discussed in Thread: CC3301

请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1418462/cc3301-wifi-issues-on-new-boards-made-with-with-one-date-code-that-work-when-replaced-with-a-different-date-code

器件型号:CC3301

工具与软件:

尊敬的 TI:

我们有一个带有 CC3301的定制 AM62X 板。  我们刚刚获得了新的电路板构建、并且在检测时遇到了问题。  我想验证是否没有会影响我们的器件更改、或者是否需要其他 devicetree 更改。

使用 buildroot (大约离一个月前的主分支机构)

Linux 版本:6.1.80 (ti-linux-09.02.00.009)

U-Boot:2024.01 (ti-u-boot-2024.01)

CC3301驱动器:1.0.0.6

GCC:12.4.0

我们的开发板附带生产日期代码。  CC3301 ENJA TI 418 AZ0Y G4

我们以前的工作板带有生产日期代码:CC3301 ENJA TI 3A8 AN25 G4

在3个新电路板上、下面是我们的调试步骤:

提出了新的电路板-不能用的无线网络

我们移除了418 AZ0Y G4、对418 AZ0Y G4进行了清理和返工-所有3个功能不全的 WiFi

我们移除了418 AZ0Y G4、对3A8 AN25 G4进行了清理和返工-所有3个产品均正常工作

我们已验证这些新电路板上的 WiFi 周围没有任何 PCB 更改、但我们将深入检查 PCB

dmesg 比较:

两个开发板都完全初始化 BLE

 Bluetooth: Core ver 2.22
 NET: Registered PF_BLUETOOTH protocol family
 Bluetooth: HCI device and connection manager initialized
 Bluetooth: HCI socket layer initialized
 Bluetooth: L2CAP socket layer initialized
 Bluetooth: SCO socket layer initialized
 Bluetooth: [bt sdio] BLE SDIO init module
 Bluetooth: [bt sdio] PROBE vendor=0x97, device=0x4077, class=255, fn=1 0xffff0000018de400
 Bluetooth: [bt sdio hci] btti_hci_add_sdio_dev
 Bluetooth: [bt sdio hci] Starting work thread...
 Bluetooth: [bt sdio] TI cc33xx BLE-over-SDIO driver is up and running!
 Bluetooth: [bt sdio hci] work thread is started
 Bluetooth: [bt sdio hci] work thread is sleeping...
 Bluetooth: [bt sdio] PROBE vendor=0x97, device=0x4077, class=255, fn=2 0xffff0000018de800
 cc33xx_sdio mmc2:0001:2: Using SDIO in-band IRQ

以前的非功能电路板替代了3A8 AN25 G4并使其可以正常工作

 cc33xx_driver cc33xx.2.auto: Direct firmware load for ti-connectivity/cc33xx-nvs.bin failed with error -2
 wlcore: Wireless driver version 1.7.0.126
 wlcore: Wireless firmware version 1.7.0.185
 wlcore: Wireless PHY version 1.2.39.5.42.67
 wlcore: loaded
wlan0     Link encap:Ethernet  HWaddr 34:68:B5:89:86:43
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

配备418 AZ0Y G4的非功能 WIFI 板:

 cc33xx_driver cc33xx.2.auto: Direct firmware load for ti-connectivity/cc33xx-nvs.bin failed with error -2
 wlcore: ERROR FW is stuck, triggering recovery
 wlcore: ERROR boot IRQ timeout
 wlcore: ERROR FW download failed
ifconfig: wlan0: error fetching interface information: Device not found

从我们的 DTS (我也会在这里附上整个 DTS):

&sdhci2 {
	/* CC3301 */
	status = "okay";
	vmmc-supply = <&wlan_en>;
	pinctrl-names = "default";
	pinctrl-0 = <&wifisdio_pins_default>;
	bus-width = <4>;
	non-removable;
	ti,fails-without-test-cd;
	cap-power-off-card;
	keep-power-in-suspend;
	ti,driver-strength-ohm = <50>;
	assigned-clocks = <&k3_clks 157 158>;
	assigned-clock-parents = <&k3_clks 157 160>;

	#address-cells = <1>;
	#size-cells = <0>;
	wlcore: wlcore@2 {
		compatible = "ti,cc33xx";
		reg = <2>;
		// 
		// pinctrl-names = "default";
		// pinctrl-0 = <&wifi_irq_pins_default>;
		// interrupt-parent = <&main_gpio0>;
		// interrupts = <72 IRQ_TYPE_EDGE_RISING>;
	};
	
	// TI-BLE-SDIO interface
    btti: btti@1 {
        compatible = "ti,cc33xxbt";
        reg = <1>;
    };
	
};



	wifi_rst_pins_default: wifi-rst-pins-default {
		pinctrl-single,pins = <
			AM62X_IOPAD(0x0124, PIN_OUTPUT_PULLDOWN, 7) /* (A23) MMC2_SDCD.GPIO0_71 */
		>;
	};
	wifi_irq_pins_default: wifi-irq-pins-default {
		pinctrl-single,pins = <
			AM62X_IOPAD(0x0128, PIN_INPUT_PULLDOWN, 7) /* (B23) MMC2_SDWP.GPIO0_72 */
		>;
	};

	wifisdio_pins_default: wifisdio-default-pins {
		pinctrl-single,pins = <
			AM62X_IOPAD(0x0120, PIN_INPUT, 0) /* (C24) MMC2_CMD */
			AM62X_IOPAD(0x0118, PIN_OUTPUT, 0) /* (D25) MMC2_CLK */
			AM62X_IOPAD(0x011C, PIN_INPUT, 0) /* () MMC2_CLKLB */
			AM62X_IOPAD(0x0114, PIN_INPUT, 0) /* (B24) MMC2_DAT0 */
			AM62X_IOPAD(0x0110, PIN_INPUT, 0) /* (C25) MMC2_DAT1 */
			AM62X_IOPAD(0x010c, PIN_INPUT, 0) /* (E23) MMC2_DAT2 */
			AM62X_IOPAD(0x0108, PIN_INPUT, 0) /* (D24) MMC2_DAT3 */
		>;
	};
	

我需要在软件中进行任何问题或更改?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    编辑了第一个帖子-我在几个地方的生产日期代码被颠倒了

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Bryce、

    感谢您报告这一点、这当然很奇怪。 尽管我们确实在1.0.0.6版本中发现了与固件下载相关的错误、但我想知道它是否与您的案例相关。 您能否进行以下更改:在 drivers/net/wireless/ti/cc33xx/cmd.c 中、将"#define CC33XX_reboot_timeout_msec"从"100"更改为"200"、然后重新测试。  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Sabeeh:

    我将包含的1.0.0.6 cc33xx_kernel.patch 更改为#define CC33XX_reboot_timeout_msec 200

    还建议更改我们的 DTS

    AM62X_IOPAD (0x0118、PIN_OUTPUT、0)/*(D25) MMC2_CLK */至 AM62X_IOPAD (0x0118、PIN_OUTPUT_PULLDOWN、0)/*(D25) MMC2_CLK */

    我仍然遇到问题。   这是第4块未改动的新电路板。

    [    2.051653] sdhci: Secure Digital Host Controller Interface driver
    [    2.058109] sdhci: Copyright(c) Pierre Ossman
    [    2.067869] sdhci-pltfm: SDHCI platform and OF driver helper
    [    2.098749] mmc0: CQHCI version 5.10
    [    2.103029] mmc2: CQHCI version 5.10
    [    2.148504] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
    [    2.156069] mmc2: SDHCI controller on fa20000.mmc [fa20000.mmc] using ADMA 64-bit
    [    2.169004] sdhci-am654 fa20000.mmc: card claims to support voltages below defined range
    [    2.190915] mmc2: new high speed SDIO card at address 0001
    [    2.281709] mmc0: Command Queue Engine enabled
    [    2.286293] mmc0: new HS200 MMC card at address 0001
    [    2.292626] mmcblk0: mmc0:0001 S40004 3.64 GiB 
    [    2.301865]  mmcblk0: p1 p2
    [    2.306809] mmcblk0boot0: mmc0:0001 S40004 4.00 MiB 
    [    2.318995] mmcblk0boot1: mmc0:0001 S40004 4.00 MiB 
    [    2.333661] mmcblk0rpmb: mmc0:0001 S40004 4.00 MiB, chardev (242:0)
    [    2.546904] EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!
    [    2.576094] EXT4-fs (mmcblk0p1): mounted filesystem with journalled data mode. Quota mode: none.
    [    2.618533] loop0: detected capacity change from 0 to 16
    [    2.723825] loop0: detected capacity change from 0 to 108376
    [    2.754083] loop1: detected capacity change from 0 to 16
    [    2.834357] loop1: detected capacity change from 0 to 864
    [    2.848189] device-mapper: verity: sha256 using implementation "sha256-sa2ul"
    [    2.863217] /dev/mapper/lower: Can't open blockdev
    [    2.883002] /dev/mapper/lower: Can't open blockdev
    [    2.889576] /dev/mapper/lower: Can't open blockdev
    [    2.936448] loop2: detected capacity change from 0 to 20000
    [    2.966625] loop3: detected capacity change from 0 to 16
    [    3.137106] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Quota mode: none.
    [    3.194645] loop3: detected capacity change from 0 to 16
    [    3.528532] EXT4-fs (dm-3): mounted filesystem with journalled data mode. Quota mode: none.
    [    5.192216] tty0tty: loading out-of-tree module taints kernel.
    [    5.245755] tty0tty null modem driver v1.2
    [    5.762232] random: crng init done
    [    9.806928] cc33xx_sdio mmc2:0001:2: Using SDIO in-band IRQ
    [   10.324225] cfg80211: Loading compiled-in X.509 certificates for regulatory database
    [   10.465726] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
    [   10.481766] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
    [   10.790683] cc33xx_driver cc33xx.2.auto: Direct firmware load for ti-connectivity/cc33xx-nvs.bin failed with error -2
    [   10.928796] usbcore: registered new interface driver usbfs
    [   10.944888] usbcore: registered new interface driver hub
    [   10.964895] usbcore: registered new device driver usb
    [   11.027627] xhci-hcd xhci-hcd.3.auto: xHCI Host Controller
    [   11.052822] xhci-hcd xhci-hcd.3.auto: new USB bus registered, assigned bus number 1
    [   11.074614] xhci-hcd xhci-hcd.3.auto: USB3 root hub has no ports
    [   11.095517] xhci-hcd xhci-hcd.3.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000008000010010
    [   11.124297] xhci-hcd xhci-hcd.3.auto: irq 476, io mem 0x31000000
    [   11.147270] hub 1-0:1.0: USB hub found
    [   11.162373] hub 1-0:1.0: 1 port detected
    [   11.177485] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller
    [   11.194853] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 2
    [   11.219128] xhci-hcd xhci-hcd.4.auto: USB3 root hub has no ports
    [   11.236615] xhci-hcd xhci-hcd.4.auto: hcc params 0x0258fe6d hci version 0x110 quirks 0x0000008000010010
    [   11.285237] xhci-hcd xhci-hcd.4.auto: irq 477, io mem 0x31100000
    [   11.311863] hub 2-0:1.0: USB hub found
    [   11.329034] hub 2-0:1.0: 1 port detected
    [   11.604787] usb 2-1: new full-speed USB device number 2 using xhci-hcd
    [   12.049918] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
    [   12.067728] cdc_acm 2-1:1.2: ttyACM1: USB ACM device
    [   12.083464] usbcore: registered new interface driver cdc_acm
    [   12.100679] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
    [   16.257171] NET: Registered PF_INET6 protocol family
    [   16.301786] Segment Routing with IPv6
    [   16.310289] In-situ OAM (IOAM) with IPv6
    [   17.367583] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:01] driver [TI DP83825S] (irq=POLL)
    [   17.456955] am65-cpsw-nuss 8000000.ethernet eth0: configuring for phy/rmii link mode
    [   19.332479] ------------[ cut here ]------------
    [   19.337132] WARNING: CPU: 0 PID: 19 at drivers/net/wireless/ti/cc33xx/sdio.c:94 cc33xx_sdio_raw_read+0x118/0x1c0 [cc33xx_sdio]
    [   19.348540] Modules linked in: ipv6 cdc_acm xhci_plat_hcd xhci_hcd usbcore cc33xx mac80211 libarc4 cfg80211 rfkill dwc3 cc33xx_sdio crct10dif_ce mcrc dwc3_am62 k3_j72xx_bandgap optee_rng rng_core tty0tty(O) sa2ul sdhci_am654 cqhci mmc_block sdhci_pltfm sdhci mmc_core
    [   19.372234] CPU: 0 PID: 19 Comm: kworker/0:1 Tainted: G           O       6.1.80 #1
    [   19.379877] Hardware name: LandisGyr TI SOM (DT)
    [   19.384487] Workqueue: events request_firmware_work_func
    [   19.389808] pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
    [   19.396758] pc : cc33xx_sdio_raw_read+0x118/0x1c0 [cc33xx_sdio]
    [   19.402675] lr : cc33xx_sdio_raw_read+0x90/0x1c0 [cc33xx_sdio]
    [   19.408505] sp : ffff800008f73bc0
    [   19.411808] x29: ffff800008f73bd0 x28: 0000000000000000 x27: 0000000000000000
    [   19.418937] x26: ffff800008dcd000 x25: ffff0000038c4b80 x24: 0000000000000000
    [   19.426065] x23: ffff0000038c7800 x22: 0000000000000100 x21: ffff000003a13810
    [   19.433194] x20: 000000000000bffc x19: ffff0000018de800 x18: 0000000000000000
    [   19.440322] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
    [   19.447449] x14: 00000000000002c7 x13: 0000000000000000 x12: 0000000000001d28
    [   19.454577] x11: 0000000000000001 x10: 00000000000009b0 x9 : ffff800008f737e0
    [   19.461704] x8 : ffff00000011a690 x7 : ffff00001d93adc0 x6 : 0000000000000001
    [   19.468832] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff000001814374
    [   19.475959] x2 : 0000000000000000 x1 : ffff000000119c80 x0 : 00000000ffffff92
    [   19.483089] Call trace:
    [   19.485530]  cc33xx_sdio_raw_read+0x118/0x1c0 [cc33xx_sdio]
    [   19.491100]  wlcore_raw_read+0x4c/0xb0 [cc33xx]
    [   19.495750]  wlcore_irq+0xe4/0x230 [cc33xx]
    [   19.499989]  wait_for_boot_irq.constprop.0+0x30/0xe0 [cc33xx]
    [   19.505789]  cc33xx_init_fw+0xec/0x370 [cc33xx]
    [   19.510377]  wlcore_nvs_cb+0x220/0xc70 [cc33xx]
    [   19.514965]  request_firmware_work_func+0x54/0xb0
    [   19.519662]  process_one_work+0x1d0/0x330
    [   19.523673]  worker_thread+0x6c/0x430
    [   19.527331]  kthread+0x108/0x110
    [   19.530556]  ret_from_fork+0x10/0x20
    [   19.534130] ---[ end trace 0000000000000000 ]---
    [   20.714109] cc33xx_sdio mmc2:0001:2: sdio read failed (-110)
    [   20.735567] wlcore: ERROR IO error during core status read
    [   22.756818] wlcore: ERROR boot IRQ timeout
    [   22.764938] wlcore: ERROR FW download failed

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Bryce、

    我想检查"AZ0Y"部件的加电状态。 您是否能够使用 Simplelink WiFi Toolbox 从 CC3301的记录器引脚收集日志?  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Sabeeh:

    我要和我们的硬件工程师(Kevin)确认他周一回来的情况。  看起来我们至少有一个 TP。  我们是否将 UART Rx 连接到它以接收数据?  我们是否需要打开任何其他调试功能?

    布莱斯

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Bryce、

    是的、您目前应该只需要一个 UART RX 连接到这个引脚。  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Sabeeh:

    该工具应该使用的波特率是多少?  我和凯文都尝试连接到 logger 引脚,但看不到任何东西在 Wireshark 中出来。  是否默认设置为3000000?应使用什么?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Sabeeh:

    Kevin 拍摄了一些示波器照片、并看到记录器的电压为1.8V、这就解释了为什么我们在3.3V TTL UART 电缆上看不到任何内容。  我订购了一些可以提供1.8V 电压的器件、明天我就可以获得日志。

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Bryce、

    抱歉、如果这之前不清楚。 CC33x 上的所有数字 I/O 均为1.8V。  

    我将继续等待这些固件日志。  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Sabeeh:

    我收到了1.8V usbttl 器件、但仍然存在问题。

    首先、我正在使用一个已知良好的设备、在该设备中、WiFi 按预期正常运行。  我可以在示波器上看到信号、当数据传入时、usbttl 上的 LED 也亮起。  

    该 COM 端口启动 SimpleLink WiFi 工具箱时看到的内容。  我没有看到任何显示内容。

    如果我断开 wifi 工具箱并使用 putty 连接到该 COM 端口、我可以在屏幕上看到一组数据(可能是二进制数据)

    2024-10-03 14:19:12,072: Searching for free port ...
    2024-10-03 14:19:12,072: Free port found at 7779
    2024-10-03 14:19:12,103: Starting WebServer...
    2024-10-03 14:19:12,150: Serving on http://127.0.0.1:7779
    2024-10-03 14:19:13,110: Starting UI ...
    2024-10-03 14:19:15,822: Logger Version : 2.1.4
    2024-10-03 14:19:17,475: Starting wLogger with command :
     C:\ti\simplelink_wifi_toolbox_2_2_4\wlogger\bin\wlogger.exe --conf_file C:\ti\simplelink_wifi_toolbox_2_2_4\wlogger\tmp\wlogger_config.json --auto_start
    STDOut and STDErr will logged into C:\Users\johnsonb\AppData\Local\Temp\_MEI4642\wlogger.log
    Staring named pipe
    Starting Wireshark: "C:\Program Files\Wireshark\Wireshark.exe" -i "\\.\pipe\wlogger"   -k
    
    
     ** (wireshark:30824) 14:19:20.088418 [Capture MESSAGE] -- Capture Start ...
    Named pipe ready
    Cleaning socket before start lisen
    
    
     ** (wireshark:30824) 14:19:20.203572 [Capture MESSAGE] -- Capture started
     ** (wireshark:30824) 14:19:20.204000 [Capture MESSAGE] -- File: "C:\Users\johnsonb\AppData\Local\Temp\wireshark_wloggerKYJ1U2.pcapng"
    Starting Socket Listener
    
    Starting logger CC3301 with command:
     C:\ti\simplelink_wifi_toolbox_2_2_4\wlogger\loggers\cc33xx_logger\bin\cc33xx_logger.exe --com_port COM8 --log_dir C:\ti\simplelink_wifi_toolbox_2_2_4\wlogger\logs\2024_10_03_14_19_18\CC3301 --bin_file C:\ti\simplelink_wifi_toolbox_2_2_4\radio-tool\binaries\CC3301\logger.bin --baud_rate 3000000 --max_log_size 12 --stream_id CC3301 --max_bytes_per_packet 200
    
    Successfully connected to COM8 ...
    Successfully created database from binary ...
    Start parsing messages ...
    

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    此外、如果我将 wifi 连接到 AP 并执行一些 ping 或 iperf 测试、我会看到更多消息。  但 Wireshark 中没有显示任何消息

    Successfully connected to COM8 ...
    Successfully created database from binary ...
    Start parsing messages ...
    2024-10-03 14:31:07,577: Task queue depth is 1
    2024-10-03 14:31:09,235: Task queue depth is 2
    2024-10-03 14:31:18,859: Task queue depth is 2
    2024-10-03 14:31:20,614: Task queue depth is 2
    2024-10-03 14:31:30,041: Task queue depth is 3
    2024-10-03 14:31:31,135: Task queue depth is 2
    2024-10-03 14:31:39,471: Task queue depth is 2
    2024-10-03 14:31:45,460: Task queue depth is 2
    2024-10-03 14:31:58,190: Task queue depth is 2
    2024-10-03 14:31:58,826: Task queue depth is 2
    2024-10-03 14:31:59,810: Task queue depth is 2
    2024-10-03 14:32:11,307: Task queue depth is 2
    2024-10-03 14:32:18,804: Task queue depth is 3
    2024-10-03 14:32:21,485: Task queue depth is 2
    2024-10-03 14:32:27,136: Task queue depth is 2
    2024-10-03 14:32:37,139: Task queue depth is 2
    2024-10-03 14:32:42,393: Task queue depth is 2
    2024-10-03 14:32:43,575: Task queue depth is 2
    2024-10-03 14:32:53,323: Task queue depth is 3
    2024-10-03 14:33:01,978: Task queue depth is 2
    2024-10-03 14:33:05,748: Task queue depth is 2
    2024-10-03 14:33:07,143: Task queue depth is 2
    2024-10-03 14:33:24,398: Task queue depth is 3
    2024-10-03 14:33:24,713: Task queue depth is 2
    2024-10-03 14:33:30,204: Task queue depth is 2
    2024-10-03 14:33:33,229: Task queue depth is 2
    2024-10-03 14:33:49,219: Task queue depth is 3
    2024-10-03 14:33:52,405: Task queue depth is 2

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Bryce、  

    这很奇怪。 从上面我可以看到、您使用的是1.0.0.6 CC33xx Linux 软件包、从日志中可以看到、您使用的是工具箱2.2.4、应该会匹配。  

    波特率应该是自动的、所以希望你不会改变那个值。  

    也许、您可以删除记录器插件并尝试从 Logger 工具重新安装它吗?

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    尊敬的 Sabeeh:

    我仔细检查了我使用的是1.0.0.6 Linux 软件包。  我没有改变波特率-它是在300,000、并使用示波器验证了这一点。

    然后完全删除工具箱和 Wireshark 并重新安装所有内容、重新启动计算机。

    仍然一样、Kevin 今天也遇到同样的问题。

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好、Bryce、

    我不确定在 Wireshark 卸载过程中文件夹"C:\Program Files\Wireshark \plugins"是否会被删除。 您能否确认最近安装了"wlogg_disector.lua"文件? 或者也可以删除它,让 Logger 工具重新安装它。  

  • 请注意,本文内容源自机器翻译,可能存在语法或其它翻译错误,仅供参考。如需获取准确内容,请参阅链接中的英语原文或自行翻译。

    你好, Sabeeh,我删除了整个文件夹后。  WiFi-tool 还要求我在重新安装后再次为 Dissector 进行复制。  

    但只是为了确保我今天上午删除它并重新安装。  我再次尝试,没有得到任何东西。  Wireshark 4.4.0是否可以使用?