From: Andy I. <ad...@he...> - 2008-06-29 00:39:41
|
Hi list, I have a Verdex XM4-BT using a Breakout-VX for console and power. root@gumstix-custom-verdex:~$ cat /etc/gumstix-version Revision 318M Built on Mon May 12 10:24:06 PDT 2008 Build machine: otto Target machine: gumstix-custom-verdex libc: glibc The bluetooth is failing to initialize with a different failure mode than I've seen in the mailing list archives; I modified hciattach to print out the HCI packet contents ("<" or ">" to show direction, "[%d]" for number of bytes, then the bytes in hex) and this is what I see: Starting 32kHz clock...Settled Starting Bluetooth subsystem: gumstix Trying baud rate 921600... gumstix No response after reset > [4] 01 01 10 00 gumstix No response from BT module gumstix Trying baud rate 921600... gumstix No response after reset > [4] 01 01 10 00 gumstix No response from BT module gumstix Trying baud rate 115200... gumstix No response after reset > [4] 01 01 10 00 < [5] 04 ff 02 05 01 Read wrong response size: 5 0x04 0xff 0x02 0x05 0x01 gumstix Trying baud rate 57600... gumstix No response after reset > [4] 01 01 10 00 >From what I can see "04 ff" indicates that it's an Infineon-specific response code? But it doesn't seem to be the same problem that Steve Sakoman fixed in Svn mods r303-r307 -- and I'm running with that fix, anyways. Doing root@gumstix-custom-verdex:~$ rmmod i2c_dev i2c_pxa tsc2003 i2c_core doesn't change the behavior; hciattach still gets the same 04 ff 02 05 01 response when it probes at 115200. My bluetooth module has its markings scribed on the metal case; it says PBA31308 V1.01 G0718/D 5N731004 root@gumstix-custom-verdex:~$ cat /proc/gpio/* GAFR0_L: 800c0000 GAFR0_U: a5254010 GAFR1_L: 69908012 GAFR1_U: aaa5a8aa GAFR2_L: 4aaaaaaa GAFR2_U: 01010000 GAFR3_L: 54041000 GAFR3_U: 00001409 GPDR0: c182ba18 GPDR1: fc9faaa1 GPDR2: 1001bfff 0 GPIO in set 1 GPIO in set 10 GPIO in clear 100 GPIO in clear 101 GPIO in set 102 AF1 out set 103 GPIO in clear 104 GPIO in set 105 AF1 out set 106 GPIO in set 107 GPIO out set 108 GPIO in set 109 AF1 out set 11 GPIO out set 110 AF1 out set 111 AF1 out set 112 AF1 out set 113 AF2 out set 114 GPIO in set 115 GPIO in set 116 GPIO in set 117 AF1 in set 118 AF1 in set 119 GPIO in set 12 GPIO out set 120 GPIO in set 121 GPIO in clear 122 GPIO in clear 123 GPIO in clear 124 GPIO in clear 125 GPIO in clear 126 GPIO in clear 127 GPIO in clear 13 GPIO out clear 14 GPIO in set 15 AF2 out set 16 GPIO in set 17 GPIO out clear 18 AF1 in set 19 GPIO in set 2 GPIO in set 20 GPIO in set 21 GPIO in set 22 GPIO in set 23 AF1 out clear 24 AF1 out clear 25 AF1 in set 26 AF2 in clear 27 GPIO in clear 28 AF1 in set 29 AF1 in set 3 GPIO out set 30 AF2 out clear 31 AF2 out clear 32 AF2 out clear 33 GPIO in set 34 AF1 in set 35 GPIO in set 36 GPIO in set 37 GPIO out set 38 GPIO in set 39 AF2 out clear 4 GPIO out clear 40 GPIO in set 41 GPIO out clear 42 AF1 in set 43 AF2 out set 44 AF1 in clear 45 AF2 out set 46 AF2 in set 47 AF1 out set 48 AF2 out set 49 AF2 out set 5 GPIO in set 50 AF2 out set 51 AF2 out set 52 GPIO out clear 53 AF2 in set 54 AF2 in set 55 AF2 out set 56 AF1 in set 57 AF1 in set 58 AF2 out clear 59 AF2 out clear 6 GPIO in set 60 AF2 out clear 61 AF2 out clear 62 AF2 out clear 63 AF2 out clear 64 AF2 out clear 65 AF2 out clear 66 AF2 out clear 67 AF2 out clear 68 AF2 out clear 69 AF2 out clear 7 GPIO in set 70 AF2 out clear 71 AF2 out clear 72 AF2 out clear 73 AF2 out clear 74 AF2 out clear 75 AF2 out clear 76 AF2 out clear 77 AF2 out clear 78 GPIO in set 79 AF1 out set 8 GPIO in set 80 GPIO out set 81 GPIO in set 82 GPIO in set 83 GPIO in set 84 GPIO in set 85 GPIO in set 86 GPIO in set 87 GPIO in set 88 AF1 in set 89 GPIO in set 9 AF3 out clear 90 GPIO in set 91 GPIO in set 92 AF1 out set 93 GPIO in set 94 GPIO in set 95 GPIO in clear 96 GPIO in set 97 GPIO out clear 98 GPIO in set 99 GPIO in set GPLR0: 327ddbef GPLR1: 03efedfe GPLR2: 7fffc000 -andy |
From: Steve S. <sa...@gm...> - 2008-06-29 16:37:33
|
Andy, This code indicates that the module has detected an issue with its eeprom. The module is most likely defective. I suggest you contact sa...@gu... for an RMA. Steve On Sat, Jun 28, 2008 at 5:39 PM, Andy Isaacson <ad...@he...> wrote: > Hi list, > > I have a Verdex XM4-BT using a Breakout-VX for console and power. > > root@gumstix-custom-verdex:~$ cat /etc/gumstix-version > Revision 318M > Built on Mon May 12 10:24:06 PDT 2008 > Build machine: otto > Target machine: gumstix-custom-verdex > libc: glibc > > The bluetooth is failing to initialize with a different failure mode > than I've seen in the mailing list archives; I modified hciattach to > print out the HCI packet contents ("<" or ">" to show direction, "[%d]" > for number of bytes, then the bytes in hex) and this is what I see: > > Starting 32kHz clock...Settled > Starting Bluetooth subsystem: > gumstix Trying baud rate 921600... > gumstix No response after reset >> [4] 01 01 10 00 > gumstix No response from BT module > gumstix Trying baud rate 921600... > gumstix No response after reset >> [4] 01 01 10 00 > gumstix No response from BT module > gumstix Trying baud rate 115200... > gumstix No response after reset >> [4] 01 01 10 00 > < [5] 04 ff 02 05 01 > Read wrong response size: 5 > 0x04 0xff 0x02 0x05 0x01 > gumstix Trying baud rate 57600... > gumstix No response after reset >> [4] 01 01 10 00 > > >From what I can see "04 ff" indicates that it's an Infineon-specific > response code? But it doesn't seem to be the same problem that Steve > Sakoman fixed in Svn mods r303-r307 -- and I'm running with that fix, > anyways. > > Doing > root@gumstix-custom-verdex:~$ rmmod i2c_dev i2c_pxa tsc2003 i2c_core > doesn't change the behavior; hciattach still gets the same 04 ff 02 05 > 01 response when it probes at 115200. > > My bluetooth module has its markings scribed on the metal case; it says > > PBA31308 V1.01 > G0718/D 5N731004 > > root@gumstix-custom-verdex:~$ cat /proc/gpio/* > GAFR0_L: 800c0000 > GAFR0_U: a5254010 > GAFR1_L: 69908012 > GAFR1_U: aaa5a8aa > GAFR2_L: 4aaaaaaa > GAFR2_U: 01010000 > GAFR3_L: 54041000 > GAFR3_U: 00001409 > GPDR0: c182ba18 > GPDR1: fc9faaa1 > GPDR2: 1001bfff > 0 GPIO in set > 1 GPIO in set > 10 GPIO in clear > 100 GPIO in clear > 101 GPIO in set > 102 AF1 out set > 103 GPIO in clear > 104 GPIO in set > 105 AF1 out set > 106 GPIO in set > 107 GPIO out set > 108 GPIO in set > 109 AF1 out set > 11 GPIO out set > 110 AF1 out set > 111 AF1 out set > 112 AF1 out set > 113 AF2 out set > 114 GPIO in set > 115 GPIO in set > 116 GPIO in set > 117 AF1 in set > 118 AF1 in set > 119 GPIO in set > 12 GPIO out set > 120 GPIO in set > 121 GPIO in clear > 122 GPIO in clear > 123 GPIO in clear > 124 GPIO in clear > 125 GPIO in clear > 126 GPIO in clear > 127 GPIO in clear > 13 GPIO out clear > 14 GPIO in set > 15 AF2 out set > 16 GPIO in set > 17 GPIO out clear > 18 AF1 in set > 19 GPIO in set > 2 GPIO in set > 20 GPIO in set > 21 GPIO in set > 22 GPIO in set > 23 AF1 out clear > 24 AF1 out clear > 25 AF1 in set > 26 AF2 in clear > 27 GPIO in clear > 28 AF1 in set > 29 AF1 in set > 3 GPIO out set > 30 AF2 out clear > 31 AF2 out clear > 32 AF2 out clear > 33 GPIO in set > 34 AF1 in set > 35 GPIO in set > 36 GPIO in set > 37 GPIO out set > 38 GPIO in set > 39 AF2 out clear > 4 GPIO out clear > 40 GPIO in set > 41 GPIO out clear > 42 AF1 in set > 43 AF2 out set > 44 AF1 in clear > 45 AF2 out set > 46 AF2 in set > 47 AF1 out set > 48 AF2 out set > 49 AF2 out set > 5 GPIO in set > 50 AF2 out set > 51 AF2 out set > 52 GPIO out clear > 53 AF2 in set > 54 AF2 in set > 55 AF2 out set > 56 AF1 in set > 57 AF1 in set > 58 AF2 out clear > 59 AF2 out clear > 6 GPIO in set > 60 AF2 out clear > 61 AF2 out clear > 62 AF2 out clear > 63 AF2 out clear > 64 AF2 out clear > 65 AF2 out clear > 66 AF2 out clear > 67 AF2 out clear > 68 AF2 out clear > 69 AF2 out clear > 7 GPIO in set > 70 AF2 out clear > 71 AF2 out clear > 72 AF2 out clear > 73 AF2 out clear > 74 AF2 out clear > 75 AF2 out clear > 76 AF2 out clear > 77 AF2 out clear > 78 GPIO in set > 79 AF1 out set > 8 GPIO in set > 80 GPIO out set > 81 GPIO in set > 82 GPIO in set > 83 GPIO in set > 84 GPIO in set > 85 GPIO in set > 86 GPIO in set > 87 GPIO in set > 88 AF1 in set > 89 GPIO in set > 9 AF3 out clear > 90 GPIO in set > 91 GPIO in set > 92 AF1 out set > 93 GPIO in set > 94 GPIO in set > 95 GPIO in clear > 96 GPIO in set > 97 GPIO out clear > 98 GPIO in set > 99 GPIO in set > GPLR0: 327ddbef > GPLR1: 03efedfe > GPLR2: 7fffc000 > > -andy > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Andy I. <ad...@he...> - 2008-06-30 23:17:22
|
On Sun, Jun 29, 2008 at 09:37:42AM -0700, Steve Sakoman wrote: > Andy, > > This code indicates that the module has detected an issue with its > eeprom. The module is most likely defective. > > I suggest you contact sa...@gu... for an RMA. Thanks for the advice, Steve. Unfortunately it took me more than 30 days to confirm that it wasn't a software issue (I thought I was just having issues with OE, especially since the module was not unresponsive!) and the feedback I got from sales@ is that an RMA is not available. Is there any chance I could salvage the bluetooth module by fixing the eeprom? I'm fairly comfortable with JTAG if there's any way to get into the module through that route. Of course a method involving Infineon_Manufacturer_Mode would be even better. :) Thanks, -andy |
From: Steve S. <sa...@gm...> - 2008-07-01 03:20:49
|
Andy, Sadly, I'm not aware of any method to fix this issue. Steve On Mon, Jun 30, 2008 at 4:17 PM, Andy Isaacson <ad...@he...> wrote: > On Sun, Jun 29, 2008 at 09:37:42AM -0700, Steve Sakoman wrote: >> Andy, >> >> This code indicates that the module has detected an issue with its >> eeprom. The module is most likely defective. >> >> I suggest you contact sa...@gu... for an RMA. > > Thanks for the advice, Steve. Unfortunately it took me more than 30 > days to confirm that it wasn't a software issue (I thought I was just > having issues with OE, especially since the module was not > unresponsive!) and the feedback I got from sales@ is that an RMA is not > available. > > Is there any chance I could salvage the bluetooth module by fixing the > eeprom? I'm fairly comfortable with JTAG if there's any way to get into > the module through that route. Of course a method involving > Infineon_Manufacturer_Mode would be even better. :) > > Thanks, > -andy > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |