10 Mar
2011
10 Mar
'11
4:09 p.m.
Hi,
I am trying to use burst_ind branch of osmocom. I have noticed that layer23 creates
bursts****.dat files when it indicates uplink. What data are written to these files and
what should I use to see its data? Thank you.
10 Mar
10 Mar
4:32 p.m.
Hi,
I am trying to use burst_ind branch of osmocom. I have
noticed that layer23 creates bursts****.dat files when it indicates uplink. What data are
written to these files
The burst raw data ... look in the sources where there are written and
you'll figure out how the data is organized.
what should I use to see its data
Nothing.
You'll have to write your own tools. (possibly derived from airprobe).
Which requires a fair understanding of how GSM works at those levels,
so it's time to read GSM 05.01 / 05.02 / 05.03
Cheers,
Sylvain
4:34 p.m.
On 03/10/2011 04:09 PM, Victor P wrote:
Hi,
I am trying to use burst_ind branch of osmocom. I have noticed that layer23
creates bursts****.dat files when it indicates uplink. What data are written
to these files and what should I use to see its data? Thank you.
These should be the 'raw' bursts on this timeslot. Reading GSM 05.02 should
get you started about the format, also airprobe should have code that can
handle raw bursts and convert them into the 'MAC' block.
6 Jun
6 Jun
5:06 p.m.
Hai list..
when I run both Mobile application and ccch_scan, the mobile application is
getting freezed... what could be the reason.
Were you able to get the raw bursts.?
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/bursts-dat-tp2660735p4025041.html
Sent from the baseband-devel mailing list archive at Nabble.com.
5:13 p.m.
when I run both Mobile application and ccch_scan, the
mobile application is
getting freezed... what could be the reason.
1) You can run two applications at the same time .... duh ...
2) The mobile application won't even work in the burst_ind branch.
only ccch_scan is usage in that branch.
5:56 p.m.
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));
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/bursts-dat-tp2660735p4025045.html
Sent from the baseband-devel mailing list archive at Nabble.com.
4349
days inactive
4803
days old
baseband-devel@lists.osmocom.org
6 comments
5 participants
participants (5)
-
Altaf -
Holger Hans Peter Freyther -
lonelysurfer -
Sylvain Munaut -
Victor P