Hardware Test Method of TI-CC Chip

Sketch

The TI CHIP based test software smart RF studio is used, include CC1310, CC1311, CC1312, CC2538, CC2640, CC2642, CC1352 etc. Therefore, VCC, GND, RST, TCK, and TMS interfaces need to be reserved for the hardware. The main reason for using official tools to test is to check software factors, which can be told to the hardware reasonably. This is a hardware problem, which has nothing to do with the software.

This tool directly operates registers to control RF transceiver. In other words, it is equivalent to testing the hardware program download, clock, and RF. These are OK, so is MCU. Of course, other hardware functions can be tested separately, which has nothing to do with this article.

Get Ready

If you prefer to do hardware, you should leave a 1.25 pitch pin slot in the first version. You should either ask him to make a adapter board, or write a self testing hardware to him like me. Anyway, you don't program, so there is no reason why you won't test. If none of the above can be done, it is recommended to build a adapter board. The hardware will be reboard with a high probability, and will be thrown to you for testing again with a high probability.

Prepare two development boards of the same chip officially produced by TI. One is used as a downloader, and the other is used as a receiving and sending object, so as to eliminate redundant factors. It looks similar to the figure below. I occasionally have problems using other downloaders, but I have never had problems using the downloader on the development board.

Lead out 5 wires from VCC, GND, RST, TCK and TMS on your hardware and connect them to the USB side of the jumper cap of the development board. Then connect to the computer via USB.

Configure smart RF Studio

1 Connection chip

Check whether the device is recognized as shown in the figure

If not, check whether the downloader XDS110 is recognized, and then check whether the connection is wrong

If it is still unrecognized, plug back the original jumper cap on the development board, and then check whether the MCU on the development board can be identified. This indicates that there is a problem with the hardware download circuit.

2 Configuration Chip

Double click the identified device, as shown here in CC1312R.

The first step is to configure and select according to the hardware. If it is an official development board, you can directly select it from the drop-down menu, otherwise you need to add a new one yourself.

For example, my hardware is externally connected with a 1190, so you should add more pin descriptions when configuring. Also note that the offset of the red line, as shown in the figure, is related to the circuit, including internal offset and external offset.

The second step is to configure RF parameters to ensure consistent transmission and reception.

Step 3: Open Receive, tick Infinite, and click Start at the bottom right

The fourth step is to plug in another development board. The hardware configuration can be directly selected from the pull-down menu described in the first step. There is no need to create a new configuration. Then, the device parameters are saved as before. Select Send, check Infinite, and click Start at the bottom right

3 Observation of reception and transmission

Take your own board as the transmitter and the development board as the receiver, observe the rssi, and then reverse it to observe again

As shown in the figure, there is an antenna test result at a distance of 1 meter. It is obvious that the signal is not very good. Record the result and feed it back to the hardware.