[OSMO_PCU] EGPRS

[Andrey Lavrukhin]

Hi

I'm using latest versions of osmo-pcu, osmo-bts, openbsc:
osmo-pcu Change -Id: Ib39e4424f73c677b34f921917440f211e400e14f
osmo-bts Change-Id: Id505594b9f224567566caac84dae2e2ae4477fae
openbsc Change-Id: Id5678a74504b4456aba0438ccc34731770801128

Hardware: octasic OCTBTS3500, API version OCTSDR-2G-02.11.00-B1927-ALPHA.
I'm using phones HTC Desire 601 and BlackBerry Z10. They both support EDGE.

As I see, in the osmo-bts/src/osmo-bts-octphy field
rach_ind_param.burst_type is not modified anywhere.
I tried to add next code to osmo-bts/src/osmo-bts-octphy/l1_if.c in
function handle_ph_rach_ind:


@@ -1207,6 +1368,22 @@ static int handle_ph_rach_ind(struct octphy_hdl *fl1,
        else
                rach_ind_param.acc_delay = ra_ind->MeasurementInfo.sBurstTiming;

+LOGP( DL1C, LOGL_ERROR, "===> ra_ind->burstType=%u\n", ra_ind->ulBurstType );
+    switch (ra_ind->ulBurstType) {
+    case cOCTVC1_GSM_BURST_TYPE_ENUM_ACCESS_TRAINING_0:
+        l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_ACCESS_0;
+        break;
+    case cOCTVC1_GSM_BURST_TYPE_ENUM_ACCESS_TRAINING_1:
+        l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_ACCESS_1;
+        break;
+    case cOCTVC1_GSM_BURST_TYPE_ENUM_ACCESS_TRAINING_2:
+        l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_ACCESS_2;
+        break;
+    default:
+        l1sap->u.rach_ind.burst_type = GSM_L1_BURST_TYPE_NONE;
+        break;
+    }
+
        /* msgb_trim() invalidates ra_ind, make that abundantly clear: */
        ra_ind = NULL;


But PCU is logging only "===> ra_ind->burstType=0", i.e
cOCTVC1_GSM_BURST_TYPE_ENUM_SYNC


чт, 28 мар. 2019 г. в 14:58, Harald Welte <laforge at gnumonks.org>:

> Hi Andrey,
>
> in general, as Max stated, you have to use 'gprs mode egprs' if you want
> EGPRS.
>
> OsmoPCU implements only either GPRS or EGPRS.  So as soon as you activate
> EGPRS,
> you cannot use GPRS-only phones anymore.  All your phones have to support
> EGPRS
> or will not be able to use PS services.
>
> Free Software lives by contributions, and OsmoPCU is unfortunately not
> receiving many.  Please feel free to join our project and help us with
> contributing the features that you need. Thanks :)
>
> Regards,
>         Harald
> --
> - Harald Welte <laforge at gnumonks.org>
> http://laforge.gnumonks.org/
>
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                   (ETSI EN 300 175-7 Ch.
> A6)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20190401/08262c0b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-bts0.cfg
Type: application/octet-stream
Size: 1198 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20190401/08262c0b/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-pcu0.cfg
Type: application/octet-stream
Size: 1607 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20190401/08262c0b/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-nitb.cfg
Type: application/octet-stream
Size: 1712 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20190401/08262c0b/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-pcu0.log
Type: text/x-log
Size: 6085 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20190401/08262c0b/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: osmo-bts0.log
Type: text/x-log
Size: 8320 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20190401/08262c0b/attachment-0001.bin>