This is a postprocessing utility which converts bsim Phy dumps of the Tx
activity of 1 or several devices into the import format for the Ellisys
Bluetooth Analyzer SW (.bttrp).
This way the BLE standard traffic (and some industry propietary extensions)
can be analyzed by this Ellisys tool.

You can call it for example as:
  components/ext_2G4_phy_v1/dump_post_process/csv2bttrp results/<sim_id>/d_2G4*.Tx.csv > ~/Trace.bttrp

This trace can then be *imported* into the Ellisys SW:
  File > Import ; Select Bluetooth packets ; Click Next ; Click Browse ; and select/open the file.

Note that all packets which are not BLE modulated won't be coverted (will be ignored).

Note that the Ellisys analyzer SW is _very_ picky, and ignores many packets which are
in some way malformed.

Note: convert_results_to_ellisys.sh is deprecated, please use csv2bttrp (or convert_results_to_ellisysv2.sh) instead.

These are postprocessing utility scripts which convert
the phy dumps in csv format to pcap (or pcapng) files.
This way the BLE & 15.4 traffic can be analyzed by Wireshark and other tools.

Currently the following scripts exist:
* csv2pcap         : Encapsulate bsim BLE traffic into pcap format
* csv2pcap_15.4.py : Encapsulate bsim 15.4 traffic into pcap format
* csv2pcapng       : Encapsulate bsim traffic (all types) into pcapng format

To merge the TX activity from all devices into a single pcap trace do:

$ dump_post_process/csv2pcapng -o mytrace.pcap results/<sim_id>/d_2G4*.Tx.csv

Replace paths as necessary.

Alternatively one can merge RX and TX activity from a single device
to get a trace as seen by that device:

$ dump_post_process/csv2pcapng -o mytrace.pcap results/<sim_id>/d_2G4_00.{Rx,Tx}.csv

However be careful not to merge Rx and Tx files from different devices
or you'll get duplicated records.