From: "Cedric GROSS" <cg@cgross.info>
To: <linux-wireless@vger.kernel.org>
Subject: Firmware error for Centrino N 2230
Date: Sat, 13 Jul 2013 12:12:17 +0200 [thread overview]
Message-ID: <001a01ce7fb1$75bfdc10$613f9430$@info> (raw)
Hello,
Im trying to adapt current freebsd driver for supporting my 2230 NIC.
I try to follow ucode command order defined in kernel 3.2 but I reach some
difficulties because firmware raise error.
Runtime uCode is alive. So far I sent calib result (cmd xB0), configured
advanced BT coexistence (cmd x9B,xCC and xCD) running runtime calib (cmd
x65) but the command configuring valid chain (cmd x65) failed as the result
below :
CSR values: (2nd byte of IWN_INT_COALESCING is IWN_INT_PERIODIC)
IWN_HW_IF_CONFIG: 0x00800302 IWN_INT_COALESCING: 0x0000ff40
IWN_INT: 0x04000000
IWN_INT_MASK: 0x00000000 IWN_FH_INT: 0x00000000 IWN_GPIO_IN:
0x00000000
IWN_RESET: 0x00000000 IWN_GP_CNTRL: 0x080403c5 IWN_HW_REV: 0x000000c8
IWN_EEPROM: 0x08450ffd IWN_EEPROM_GP: 0x90000801 IWN_OTP_GP:
0x00030001
IWN_GIO: 0x00080044 INW_GP_UCODE: 0x00000004 IWN_GP_DRIVER:
0x00000080
IWN_GP1_DRIVER: 0x00000000 IWN_UCODE_DRV_GP2: 0x00000000 IWN_LED:
0x00000018
IWN_DRAM_INT_TBL: 0x880b76e5 IWN_GIO_CHICKEN: 0x29800200 IWN_ANA_PLL:
0x00000000
IWN_HW_REV_WA: 0x0001001a IWN_DBG_HPET_MEM: 0xffff0000
firmware error log:
error type = "UNKNOWN" (0x00001987)
program counter = 0x000179B4
source line = 0x00000167
error data = 0x0000000000000000
branch link = 0x0001798200017982
interrupt link = 0x0000EC7A00000000
time = 46566
What Im missing ?
What is meaning of firmware error ?
Many thanks for your help.
Best regards
Cedric
next reply other threads:[~2013-07-13 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 10:12 Cedric GROSS [this message]
2013-07-13 11:03 ` Firmware error for Centrino N 2230 Sedat Dilek
2013-07-13 11:15 ` Cedric GROSS
2013-07-13 11:26 ` Sedat Dilek
2013-07-14 5:03 ` Emmanuel Grumbach
2013-07-14 9:47 ` Cedric GROSS
2013-07-14 10:51 ` Johannes Berg
2013-07-15 8:21 ` Cedric GROSS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001a01ce7fb1$75bfdc10$613f9430$@info' \
--to=cg@cgross.info \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).