resources.conf: Set UHD identifiers on B200 devices
osmo-trx-uhd uses these args during device search/selection process. As those were not set until now for B200, it means when a B200 was used by osmo-gsm-tester any UHD device could be picked up and used by UHD. That was actually happening since inclusion of UmTRX devices in Prod setup, when running tests against desired B200, actually the UmTRX device was being used. Change-Id: I696bbc800b05fdd9a68a77f363d76dcc53ef24ee
This commit is contained in:
parent
9ea9c65b39
commit
5686602a98
|
@ -31,6 +31,7 @@ bts:
|
|||
launch_trx: true
|
||||
remote_user: jenkins
|
||||
trx_ip: 10.42.42.116
|
||||
dev_args: "type=b200,serial=306BD11"
|
||||
clock_reference: external
|
||||
multi_arfcn: true
|
||||
|
||||
|
@ -45,7 +46,7 @@ bts:
|
|||
launch_trx: true
|
||||
remote_user: jenkins
|
||||
trx_ip: 10.42.42.118
|
||||
dev_args: addr=10.42.42.130,pa=NONE,pa_power_max_dbm=23,fifo_ctrl_window=0,status_port=12345
|
||||
dev_args: "addr=10.42.42.130,pa=NONE,pa_power_max_dbm=23,fifo_ctrl_window=0,status_port=12345"
|
||||
clock_reference: internal
|
||||
|
||||
- label: LimeSDR-USB
|
||||
|
|
|
@ -32,6 +32,7 @@ bts:
|
|||
multi_arfcn: true
|
||||
remote_user: jenkins
|
||||
trx_ip: 127.0.0.1
|
||||
dev_args: "type=b200,serial=30A9FFB"
|
||||
ciphers: [a5_0, a5_1]
|
||||
|
||||
- label: NanoBTS-ONW-1900
|
||||
|
|
Loading…
Reference in New Issue