Attention is currently required from: osmith, pespin.

fixeria has posted comments on this change by fixeria. ( 
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/41899?usp=email )

Change subject: bts: TC_rsl_chan_initial_ta: fix sporadic failures
......................................................................


Patch Set 1:

(1 comment)

File bts/BTS_Tests.ttcn:

https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/41899/comment/f839e8ff_b87abf1a?usp=email
 :
PS1, Line 3894:         /* tell trxcon to use a given TA for UL bursts */
> a lot of trxcon blackmagic which is need to "set TA on trxcon"


"set TA on trxcon" is a simplification. This concept of separate TA existed 
even before trxcon: there's TA that's actually used on the radio interface (set 
via `f_L1CTL_PARAM()`) and TA indicated to the network in UL SACCH (set via 
`f_send_meas_rep()`). This is related to the "fake TA" feature of the mobile 
app. The firmware behaves this way and trxcon replicates that. This is why we 
do it this way.

The testcase API can be improved in a separate patch. I believe it's a good 
idea to do `f_send_meas_rep()` in `f_est_dchan()` before calling 
`f_l1ctl_est_dchan()`. This way we make sure that trxcon always indicates 
expected/known values in the L1 SACCH header.



--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/41899?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings?usp=email

Gerrit-MessageType: comment
Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-Change-Id: Iebb043ccc710750dff937e2281c23d343b85bda1
Gerrit-Change-Number: 41899
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <[email protected]>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: osmith <[email protected]>
Gerrit-Reviewer: pespin <[email protected]>
Gerrit-Attention: osmith <[email protected]>
Gerrit-Attention: pespin <[email protected]>
Gerrit-Comment-Date: Thu, 22 Jan 2026 10:00:15 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <[email protected]>
Comment-In-Reply-To: fixeria <[email protected]>

Reply via email to