Hello,
I'm unable to communicate with pan1325 module. I supplied 3.3V to pin 11(CL1.5_LDO_IN) and 15(MLDO_IN), 1.8V to pin 22(VDD_IO), provide 32k clock to pin 8(SLOW_CLK_IN), drive pin 16(nSHUTD) high and pin 3(CTS) low. I'm using linux blueZ uart stack (hciattach /dev/ttyUSB0 any 115200 flow) and modified bt stack from LUFA library but I'm unable to get anything from the device. No activity on device's TX pin.
What can be possibly wrong?
Fero
Fero,
Do you see any activity on the RX pin?
Gustavo
---------------------------------------------------------------------------------------------------------Please click the Verify Answer button on this post if it answers your question.---------------------------------------------------------------------------------------------------------
Yes, I can see bytes I send through the uart interface with oscilloscope. It is request to reset device.
Frantise,
Could you take a snapshot of what's being sent to the CC256x using the oscilloscope and post it?
Here are couple of comments you should take into consideration:
a) PAN1315 Power Up Sequence: Power Supply (3.3v and1.8V) and Slow Clock should be available and stable before asserting nSHUTD line. If this sequence is followed correctly, the HCI UART RTS line will go low after approx 100ms from the nSHUTD assertion. This action indicates a proper device boot up. Otherwise, the device did not boot up due to invalid power up sequence.
b) BlueZ HCI Driver: The HCI driver provided for the ARM Processors do support the PAN13xx; however, the provided SDKs do not support currently the PAN13xx modules due to missing Service Pack. Please contact your local TI representative for more information on how to obtain this Service Pack. BTW, the command is hciattach /dev/ttyS1 texas 3000000.
Regards,
Miguel,
Thanks for your answer, the device did boot up correctly but i am still unable to get any answer. What is default hci speed of module? Your answer suggest 3M but in datasheet is default speed 115200.
Regards
Frantisek,
The device boots up at 115200 but then switches to a higher speed mode after the SP is downloaded.
how important the SP is? Where can I get it? Can I redistribute the SP (We are creating development platform)?
The SP is essential to be able to use the bluetooth chipset. As for your second question, I am looking for those answers and me or someone else will let you know.
Please contact Dana Myers: dmyers@ti.com
Let her know your application and she will discuss with you possible options for obtaining and using the Service Pack.
Regards,Gustavo
I am in a similar situation -- have the PAN1315 attached to my board via a UART , and can bring the module up -- "hciconfig -a" proves this much. However, a "hcitool scan" never returns anything. Running Linux 2.6.31 and the BlueZ (4.96) stack.
Don,
Which version of the PAN1315 module do you have?
~Miguel
PAN1315ETU (Rev 1.1)
MIguel
As a follow up - I know I can communicate with the module since I see this output :
root@freescale ~$ hciconfig -ahci0: Type: UART BD Address: C0:E4:22:8D:4D:2D ACL MTU: 1021:4 SCO MTU: 180:4 UP RUNNING PSCAN ISCAN RX bytes:1501 acl:0 sco:0 events:30 errors:0 TX bytes:621 acl:0 sco:0 commands:27 errors:0 Features: 0xff 0xff 0x2d 0xfe 0x9b 0xff 0x79 0x83 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: MASTER Name: 'PDK' Class: 0x100100 Service Classes: Device Class: Computer, Uncategorized HCI Ver: (0x4) HCI Rev: 0x0 LMP Ver: (0x4) LMP Subver: 0x191f Manufacturer: Texas Instruments Inc. (13)
However, scan never return anything, as seen :
root@freescale ~$ hcitool scanScanning ...
Tried both the older default BlueZ 2.25 and the newer BlueZ 4.96 stacks, and neither have any results.
don
Thanks for the info. I think that the SP is not being loaded to the device during initialization. Unfortunately, we don't have the package with the CC256x SPs available to the public yet. We are working on that currently. In the meantime (as a workaround), you can download any WL1271 package from this site and grab the TIInit_7.2.31.bts from it. Change the name to TIInit_6.2.31.bts and place it under your ./lib/firmware directory. Try to initialize the device again and let me know how it goes.
Miguel
Found the file -- no effect. Everything is the same. Got it transferred over to the dev board, and it didn't even acknowledge the file. I tried running it by hand and got a cannot execute binary file error -- wasn't sure if I was supposed to do that or not, but figured it couldn't hurt.
Just to make clear, I am NOT using the MSP430F5438 Experimenter Board -- we are using the Freescale iMX25 PDK boards. The ETU board is attached via a UART.. Not sure if that makes a difference with that file or not.