From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr =?iso-8859-2?Q?=A9tetiar?= Date: Mon, 22 Nov 2010 10:14:22 +0100 Subject: [ath9k-devel] ath9k_htc, 2.6.36 and "Target is unresponsive" error In-Reply-To: References: <20101119110559.GO15069@ibawizard.net> Message-ID: <20101122091422.GD2530@ibawizard.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Mohammed Shafi [2010-11-22 11:15:17]: > On Fri, Nov 19, 2010 at 4:35 PM, Petr ?tetiar wrote: > > > > 1. line 128 in htc_drv_init.c time_left = > > wait_for_completion_timeout(&priv->htc->target_wait, HZ); > Can you please try out .. htc_drv_init.c time_left = > wait_for_completion_timeout(&priv->htc->target_wait, HZ/4); this should > obviously fail I'll try that later today, but it I think, that it will fail also. > htc_drv_init.c time_left = > wait_for_completion_timeout(&priv->htc->target_wait, 30*HZ); I've even tried 100*HZ, but it fails anyway and I think, that the root of the problem is somewhere else. This point is just the consequence of the failure in htc_process_target_ready(), so even adding the 1000*HZ wouldn't help it much :-) As I understand it, host downloads the firmware to the MCU with FIRMWARE_DOWNLOAD, then if it's sending of the firmware complete the host sends FIRMWARE_DOWNLOAD_COMP and then MCU should respond with HTC_MSG_READY_ID, but it didn't in my case for some reason. It's responding with msg 0x18 on USB endpoint 0x1, instead of msg 0x1(HTC_MSG_READY_ID) on USB endpoint 0. I don't have the sources of the firmware, so I don't know how it works internally, but maybe it's just wrong timing assumption somewhere or something similar. That ARM board I'm using is kind of slow, it's like 200MHz(99 Bogomips), so everything takes quite longer time to complete, than on one is used on desktop PC. -- ynezz