Hi,
I'm using the sylvain/burst_ind branch and ccch_scan. this produces bursts files.
with which application can i view them? what is the format of these dat files?
i cannot open them with wireshark...
any hints?
kind regards
with which application can i view them? what
None. You have to write a custom application to use them however you want to use them ...
is the format of these dat files?
See the l1ctl_burst_ind structure definition in the code.
They're raw bits from the air with a small header, if you haven't read and understood the GSM 05.03 specs, they'll be pretty useless for you.
i cannot open them with wireshark...
They're at a much lower level of the protocol stack than what wireshark can display.
Cheers,
Sylvain
Is this the structure of the dat files?
struct l1ctl_burst_ind { uint32_t frame_nr; uint16_t band_arfcn; /* ARFCN + band + ul indicator */ uint8_t chan_nr; /* GSM 08.58 channel number (9.3.1) */ uint8_t flags; /* BI_FLG_xxx + burst_id = 2LSBs */ uint8_t rx_level; /* 0 .. 63 in typical GSM notation (dBm+110) */ uint8_t snr; /* Reported SNR >> 8 (0-255) */ uint8_t bits[15]; /* 114 bits + 2 steal bits. Filled MSB first */ } __attribute__((packed));
what does packed mean?
----- Oorspronkelijk e-mail -----
Van: "g roelant" g.roelant@telenet.be Aan: "osmocomBB" baseband-devel@lists.osmocom.org Verzonden: Maandag 10 december 2012 12:36:49 Onderwerp: bursts dat files
Hi, I'm using the sylvain/burst_ind branch and ccch_scan. this produces bursts files. with which application can i view them? what is the format of these dat files? i cannot open them with wireshark... any hints? kind regards
Hi,
Is this the structure of the dat files?
Yes.
If you had read the code that write those files, you would have known that already.
struct l1ctl_burst_ind { uint32_t frame_nr; uint16_t band_arfcn; /* ARFCN + band + ul indicator */ uint8_t chan_nr; /* GSM 08.58 channel number (9.3.1) */ uint8_t flags; /* BI_FLG_xxx + burst_id = 2LSBs */ uint8_t rx_level; /* 0 .. 63 in typical GSM notation (dBm+110) */ uint8_t snr; /* Reported SNR >> 8 (0-255) */ uint8_t bits[15]; /* 114 bits + 2 steal bits. Filled MSB first */ } __attribute__((packed));
what does packed mean?
http://lmgtfy.com/?q=__attribute__%28%28packed%29%29%3B&l=1
Cheers,
Sylvain
it means that no padding is used to align struct field on word boundaries. This is a normal way to do things when a struct is to be written in a file or any other data stream.
Regards Sebastien
Le 10/12/2012 14:46, g.roelant@telenet.be a écrit :
Is this the structure of the dat files?
struct l1ctl_burst_ind { uint32_t frame_nr; uint16_t band_arfcn; /* ARFCN + band + ul indicator */ uint8_t chan_nr; /* GSM 08.58 channel number (9.3.1) */ uint8_t flags; /* BI_FLG_xxx + burst_id = 2LSBs */ uint8_t rx_level; /* 0 .. 63 in typical GSM notation (dBm+110) */ uint8_t snr; /* Reported SNR >> 8 (0-255) */ uint8_t bits[15]; /* 114 bits + 2 steal bits. Filled MSB first */ } __attribute__((packed));
what does packed mean?
*Van: *"g roelant" g.roelant@telenet.be *Aan: *"osmocomBB" baseband-devel@lists.osmocom.org *Verzonden: *Maandag 10 december 2012 12:36:49 *Onderwerp: *bursts dat files
Hi,
I'm using the sylvain/burst_ind branch and ccch_scan.
this produces bursts files.
with which application can i view them? what is the format of these dat files?
i cannot open them with wireshark...
any hints?
kind regards
On Mon, Dec 10, 2012 at 02:46:26PM +0100, g.roelant@telenet.be wrote:
} __attribute__((packed));
what does packed mean?
http://gcc.gnu.org/onlinedocs/gcc-4.7.1/gcc/Type-Attributes.html#Type-Attrib...
baseband-devel@lists.osmocom.org
-
g.roelant＠telenet.be -
Holger Hans Peter Freyther -
Sebastien Lorquet -
Sylvain Munaut