Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| network_protocol_programming_lab:15.3_4_exercise [2020/05/13 09:01] – [4. Exercise: Packet Transmission] rathke | network_protocol_programming_lab:15.3_4_exercise [2021/04/19 12:38] (current) – [Requirements] rathke | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| Most protocol in communication networks are packet oriented. To send a packet, all user data stored in the TX FIFO will be send. To store data in TX FIFO, function cc1200_reg_write will be used. As address parameter the address 0x3F will be provided and the data to store. After the TX FIFO has been filled. The CC1200 has to be switched into sending mode. | Most protocol in communication networks are packet oriented. To send a packet, all user data stored in the TX FIFO will be send. To store data in TX FIFO, function cc1200_reg_write will be used. As address parameter the address 0x3F will be provided and the data to store. After the TX FIFO has been filled. The CC1200 has to be switched into sending mode. | ||
| - | In sending mode, CC1200 will prepend the data to send with a programmable preamble and a sync word. After the data of the TX FIFO has been sent, an optional CRC will be calculated and also been sent. After the packet | + | In sending mode, CC1200 will prepend the data to send with a programmable preamble and a sync word. After the data of the TX FIFO has been sent, an optional CRC will be calculated and also been sent. After sending a packet, CC1200 will go back to idle mode. The mode to enter after sending a packet can be changed by programming the '' |
| The aim of this exercise is to send fixed length packets and variable length packets. | The aim of this exercise is to send fixed length packets and variable length packets. | ||
| Line 11: | Line 11: | ||
| This task requires | This task requires | ||
| - | * a ready BeagleBone Black equipped with the CC1200 | + | * a ready BeagleBone Black equipped with the CC1200. |
| - | * one TI Development Kit for the CC1200 | + | * 4C attached to a second BeagleBone Black equipped with the CC1200. |
| - | * Smart RF Studio. | + | |
| ===== Tasks ===== | ===== Tasks ===== | ||
| - | * connect the TI Development Kit to your computer and execute | + | * connect the first BeagleBone Black to your computer and install, |
| - | * open the CC1200 panel and select “Symbolrate 38.4kbps, 2-GFSK, RX BW 100kHz, ETSI Standard (868MHz)” in the typical settings part | + | * open " |
| - | * press the button “Packet | + | |
| * in the option '' | * in the option '' | ||
| - | * now, choose an appropriate length of the '' | + | * enter charters in the the text window. You will see, that '' |
| * export all registers to a file. This means 208 registers must be exported. | * export all registers to a file. This means 208 registers must be exported. | ||
| - | * connect | + | * login to the second |
| - | * copy the export file from SmartRF | + | * copy the export file from 4C Studio to the BeagleBone Black |
| * import the export file into your program and initialize the registers according the values of the export file. | * import the export file into your program and initialize the registers according the values of the export file. | ||
| * verify that the registers have been written correctly. | * verify that the registers have been written correctly. | ||
| * Read chapter 8 about the packet handling of the [[http:// | * Read chapter 8 about the packet handling of the [[http:// | ||
| - | * Bring SmartRF | + | * Bring 4C Studio in “RX Packet Mode", change the '' |
| - | * start the transmitter. At the receiver | + | * start the transmitter. At the receiver, you should now receive the packets |
| If you are able to transmit packets in fixed length mode, the next step will be to transmit packets in variable length mode: | If you are able to transmit packets in fixed length mode, the next step will be to transmit packets in variable length mode: | ||
| - | * go back to SmartRF Studio | + | * go back to 4C and change the '' |
| * look, which registers have been changed. | * look, which registers have been changed. | ||
| * modify the changed registers in your program. You do not need to reexport the complete registers. | * modify the changed registers in your program. You do not need to reexport the complete registers. | ||
| Line 40: | Line 37: | ||
| ===== Hints ===== | ===== Hints ===== | ||
| - | * keep in mind, that SmartRF Studio receiver will expect a CRC. | + | * same hints as by receiving packets. |
