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 08:53] – rathke | network_protocol_programming_lab:15.3_4_exercise [2021/04/19 12:38] (current) – [Requirements] rathke | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 4. Exercise: Packet Transmission ====== | ====== 4. Exercise: Packet Transmission ====== | ||
| - | 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 | + | 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 |
| - | 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. |
| - | | + | ===== Tasks ===== |
| + | * connect the first BeagleBone Black to your computer and install, execute 4C. | ||
| + | * open "TX Packet Mode" in test window. Some registers in the register view will change their value. | ||
| + | * in the option '' | ||
| + | * enter charters in the the text window. You will see, that '' | ||
| + | * export all registers to a file. This means 208 registers must be exported. | ||
| + | * login to the second BeagleBone Black as superuser. | ||
| + | * 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. | ||
| + | * verify that the registers have been written correctly. | ||
| + | * Read chapter 8 about the packet handling of the [[http:// | ||
| + | * Bring 4C Studio in “RX Packet Mode", change the '' | ||
| + | * start the transmitter. At the receiver, you should now receive the packets by 4C. | ||
| + | |||
| + | 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 4C and change the '' | ||
| + | * look, which registers have been changed. | ||
| + | * modify the changed registers in your program. You do not need to reexport the complete registers. | ||
| + | * now, implement variable length packets and test it. | ||
| + | |||
| + | ===== Hints ===== | ||
| + | |||
| + | * same hints as by receiving packets. | ||
