I need to connect my small base station (6670), which has a GC5330 chip, to the RF via TSW 3725, however I do not have any idea how to initialize TSW3725 board. I have a few ideas on how to initialize GC5330 but I am totally stuck related to TSW3725, especially cause in the user guide only the stand alone model is explained. Thanks in advance.
Are you using the SCBP from Azcomm or have you developed your own small cell basestation to talk to the TSW3725?
I would recommend the following. In the User's guide on page 32-33 there is a discussion about the LOG SPI button on the TSW3725 GUI. If you click the LOG SPI button in stand alone mode and select PROGRAM ALL, then all the SPI commands used to initialize the board in stand alone mode will be recorded to a .csv file. At that point you will have all the command necessary to initialize the TSW3725 with the settings in the stand alone mode. You can also change individual settings on the GUI and the LOG SPI will record those also.
Page 51 of the TSW3725 user guide provides the device ID for each part on the board. After that you'll need to refer to those device datasheets.
Page 11 of the TSW3725 user's guide discusses how to switch the hardware between stand alone mode and SCBP mode.
Does this help?
Firstly, I am using the SCBP from Azcomm, and I am willing to talk to TSW3725 for RF transmission.
It has been beneficial for me to learn that I need to use the GUI to program the TSW3725 even though I am going to use it in the SCBP mode. But would you be kind to guide me through the SCBP mode of TSW3725. As I mentioned the user guide is all about the stand alone mode. For the SCBP mode should I just configure the hardware (as explained in page 11) and then wait for the TSW3725 to perform? I am quite new to the RF boards of TI so excuse my lack of knowledge.
OK, I think its good you are using the Azcom SCBP as a lot of the work should be done already by Azcom. My understanding is Azcom has some command line code that loads the a TSW .csv file into the SCBP and then at that point the SCBP will program the TSW3725 (when its in SCBP mode - page 11). Once that is done the TSW3725 should be ready to go.
Azcom supports the SCBP, can you contact them to see how this is done. (email@example.com ). I'm not sure, but Azcom may even supply the TSW .csv file for you. If this is the case you may not need to use the stand alone mode of the TSW3725 to generate a .csv.
I have contacted Azcom, and they do supply a config file. I have used the configuration they have supplied but the leds that should be illuminated regarding the user guide are off (which I have stated below). Does the fact that these leds are not on imply that the setup is not done correctly?
When programming is complete, verify that the following LEDs on the TSW3725 HW are illuminated. Ifthey are, then the TSW3725 was programmed correctly. If they are not, then start over at step 1.(a) D3 POLLOCK: green (confirms CDC chip is locked)(b) D4 LD: green (confirms TRF3720 for TX and Feedback paths is locked)(c) D5 LD: green (confirms TRF3720 for RX path is locked. Note: on Rev A hardware, this LED isunder the RX RF Shield; this LED was moved outside of the RX RF Shield on Rev B hardware.)
Thanks in advance.
Yes, this implies something is wrong. The 3 LEDs listed confirm frequency locks for the 3 PLLs on the TSW3725. Here are some thoughts on debugging this
1) Confirm D14 is blinking (i.e. not D11). See page 11 of the TSW3725 of user guide. D14 confirms you are in SCBP mode, in this mode the SCBP can write to the TSW3725. If D11 is blinking the SCBP can not write to the TSW3725.
2) If D14 is blinking. This implies that either the SCBP is not programming it correctly or something broke on the TSW3725. To rule out the TSW3725 is broken, I would switch to TSW3725 standalone mode (see page 11 of TSW325 user guide). D11 should be blinking at this point Connect the USB cable to the TSW3725 and yoru computer. Bring up the TSW3725 GUI and then select the yellow 'Program All' button on the TSW3725 GUI. Wait ~30seconds for the TSW3725 programming to complete. At this point the 3 LEDs should be lit up. If they are lit then this implies the TSW3725 is functional and the issue is more on the SCBP programming side
3) If #1 and #2 pass, then we'll need to get someone else involved that understands how the SCBP is programming the TSW3725 and see where the disconnect is.
4) also remember to switch back to SCBP mode (D14 blinking) when connecting to the SCBP
First of all I'd like to thank you for your continuous support. I have debugged the situation step by step as you described and I have observed that the LEDs are on when I program the TSW 3725 in stand alone mode. Thus, the problem seems SCBP programming related (I am switching back to SCBP mode when connecting to SCBP).
Can you provide me some insight on how to program the TSW 3725 in SCBP mode? I have been trying to configure it via the MATLAB GUI, but it seems it was not the right thing to do. I know that I can record the SPI commands using Log SPI button in the GUI. How can I use this .csv file to program the TSW 3725?
It has been my pleasure.
At this point, it sounds like Azcom needs to take over as it sounds like your SCBP is not programming the TSW3725 correctly. The SCBP is their responsibility and I personally do not have the knowledge on how to program the TSW3725 with the SCBP. Wish I could help more.
I may have spoke to soon. There does seem to be a piece of software that converts the TSW3725 .csv to SCBP code that is not supported by Azcom.
Do you have access to any TI DSP resources (WBI customer support), they maybe able to help you?
I'll contact the local TI support to ask if they could help me related to this. Do you have any idea how much the software costs, or if it is free is it protected by NDA? Thanks for your help, you've been the best.
Since the software would be coming froma different division of TI, I hesitate to speak for them on the cost.
I do appreciate the kind words and hope you get it running soon.
I am using Azcom's SCBP with TSW3725 and I am having similar problems than Ilke:
- Programing in standalone mode (D11 blinking, Matlab GUI): I get D4 and D5 on, but D3 off
- Programing in SCBP mode (D14 blinking, tswconfig): D3, D4, D5 off (nothing happens).
What could be wrong?
Thank you in advance.
D3 will tell you if the CDCE72010 chip is locked or not. THe CDCE72010 sends clock signal to two TRF3720's. If these TRF3720's lock than D4 & D5 will light up. So if the CDCE72010 chips is not locking (D3), than there is a chance D4 and D5 may not. So lets concentrate on D3.
Can you verify the following for me
- Does the CDCE72010 readback the correct information when the DISPLAY button is selected?- Can you measure the reference input frequency/power at R370 (0 ohm resistor near pin 59 of CDCE72010 device). There should be a 30.72M signal present.- Verify you have 3.3V at the 3.3V_CDC_VCC test point (exposed gold area - labeled with silk screen)- What serial number are you having this problem with?
When you are measuring the board in stand alone mode, is it connected to the SCBP at that time?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.