Let's keep the public conversation, there are no secrets, right? ;)
Here is the pcap attached and here is the osmo-nitb log https://pastebin.com/NJa0YU08
here is the osmo-bts log https://pastebin.com/RZ0au5yA
hope you know what is wrong. Thanks
Have a look at the following log lines:
trx_if.c:217 Enqueuing TRX control command 'CMD NOHANDOVER 0 0' ... trx_if.c:371 Response message: 'RSP NOHANDOVER -1' trx_if.c:403 transceiver (phy0.0) rejected TRX command with response: 'RSP NOHANDOVER -1' bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
For some reason, the OsmocomBB transceiver rejects the command. Despite it's implemented and should work as expected.
Let's look at the source code (trx.c:400 _trx_ctrl_cmd_(no)handover):
int n, tn, ss = 0;
n = sscanf(args, "%d %d", &tn, &ss);
if ((n < 1) || (tn < 0) || (tn > 7) || (ss < 0) || ((ss > 8))) return _trx_ctrl_send_resp(trx, cmd, "%d %d %d", -1, tn, ss);
// ...
Try to debug this condition on your side. I cannot reproduce your problem...
With best regards, Vadim Yanitskiy.
OK, Thanks alot Vadim. :-) will try to debug and will keep report.
Thanks. DUO
On Tue, Jan 9, 2018 at 12:32 AM, Vadim Yanitskiy axilirator@gmail.com wrote:
Let's keep the public conversation, there are no secrets, right? ;)
Here is the pcap attached and here is the osmo-nitb log https://pastebin.com/NJa0YU08
here is the osmo-bts log https://pastebin.com/RZ0au5yA
hope you know what is wrong. Thanks
Have a look at the following log lines:
trx_if.c:217 Enqueuing TRX control command 'CMD NOHANDOVER 0 0' ... trx_if.c:371 Response message: 'RSP NOHANDOVER -1' trx_if.c:403 transceiver (phy0.0) rejected TRX command with response: 'RSP NOHANDOVER -1' bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
For some reason, the OsmocomBB transceiver rejects the command. Despite it's implemented and should work as expected.
Let's look at the source code (trx.c:400 _trx_ctrl_cmd_(no)handover):
int n, tn, ss = 0;
n = sscanf(args, "%d %d", &tn, &ss);
if ((n < 1) || (tn < 0) || (tn > 7) || (ss < 0) || ((ss > 8))) return _trx_ctrl_send_resp(trx, cmd, "%d %d %d", -1, tn, ss);
// ...
Try to debug this condition on your side. I cannot reproduce your problem...
With best regards, Vadim Yanitskiy.
Dear Vadim, just FYI, the jolly branch stuck and cannot sync to BTS on my side. I was using Sylvain branch for the test.
Thanks.
DUO
On Tue, Jan 9, 2018 at 12:42 AM, Sandi Suhendro djks74@gmail.com wrote:
OK, Thanks alot Vadim. :-) will try to debug and will keep report.
Thanks. DUO
On Tue, Jan 9, 2018 at 12:32 AM, Vadim Yanitskiy axilirator@gmail.com wrote:
Let's keep the public conversation, there are no secrets, right? ;)
Here is the pcap attached and here is the osmo-nitb log https://pastebin.com/NJa0YU08
here is the osmo-bts log https://pastebin.com/RZ0au5yA
hope you know what is wrong. Thanks
Have a look at the following log lines:
trx_if.c:217 Enqueuing TRX control command 'CMD NOHANDOVER 0 0' ... trx_if.c:371 Response message: 'RSP NOHANDOVER -1' trx_if.c:403 transceiver (phy0.0) rejected TRX command with response: 'RSP NOHANDOVER -1' bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
For some reason, the OsmocomBB transceiver rejects the command. Despite it's implemented and should work as expected.
Let's look at the source code (trx.c:400 _trx_ctrl_cmd_(no)handover):
int n, tn, ss = 0;
n = sscanf(args, "%d %d", &tn, &ss);
if ((n < 1) || (tn < 0) || (tn > 7) || (ss < 0) || ((ss > 8))) return _trx_ctrl_send_resp(trx, cmd, "%d %d %d", -1, tn, ss);
// ...
Try to debug this condition on your side. I cannot reproduce your problem...
With best regards, Vadim Yanitskiy.
Dear Vadim, I tried to install Jolly branch many times and this is the debug result which always stop when sync to BTS.
when I flashing my C117 https://pastebin.com/mGGFzmrE then I start transceiver https://pastebin.com/GYeyiKrJ
I was thinking the package is broken? testing with sylvain is work, just like yesterday my registering still problem. but this Jolly branch even cannot produce sync.
looks like its not connected at all.
please help to look. Thanks.
Thanks, DUO
On Tue, Jan 9, 2018 at 1:11 AM, Sandi Suhendro djks74@gmail.com wrote:
Dear Vadim, just FYI, the jolly branch stuck and cannot sync to BTS on my side. I was using Sylvain branch for the test.
Thanks.
DUO
On Tue, Jan 9, 2018 at 12:42 AM, Sandi Suhendro djks74@gmail.com wrote:
OK, Thanks alot Vadim. :-) will try to debug and will keep report.
Thanks. DUO
On Tue, Jan 9, 2018 at 12:32 AM, Vadim Yanitskiy axilirator@gmail.com wrote:
Let's keep the public conversation, there are no secrets, right? ;)
Here is the pcap attached and here is the osmo-nitb log https://pastebin.com/NJa0YU08
here is the osmo-bts log https://pastebin.com/RZ0au5yA
hope you know what is wrong. Thanks
Have a look at the following log lines:
trx_if.c:217 Enqueuing TRX control command 'CMD NOHANDOVER 0 0' ... trx_if.c:371 Response message: 'RSP NOHANDOVER -1' trx_if.c:403 transceiver (phy0.0) rejected TRX command with response: 'RSP NOHANDOVER -1' bts.c:208 Shutting down BTS 0, Reason TRX-CTRL-MSG: CRITICAL
For some reason, the OsmocomBB transceiver rejects the command. Despite it's implemented and should work as expected.
Let's look at the source code (trx.c:400 _trx_ctrl_cmd_(no)handover):
int n, tn, ss = 0;
n = sscanf(args, "%d %d", &tn, &ss);
if ((n < 1) || (tn < 0) || (tn > 7) || (ss < 0) || ((ss > 8))) return _trx_ctrl_send_resp(trx, cmd, "%d %d %d", -1, tn, ss);
// ...
Try to debug this condition on your side. I cannot reproduce your problem...
With best regards, Vadim Yanitskiy.
-- best regards, Krazy Sandi Blue Soho Recordings Number One Recordings
Hi,
I tried to install Jolly branch many times and this is the debug result which always stop when sync to BTS.
I was thinking the package is broken? testing with sylvain is work, just like yesterday my registering still problem. but this Jolly branch even cannot produce sync.
Hmm, I just found out that both handover related commands are implemented in jolly/testing, but not in sylvain/testing:
http://git.osmocom.org/osmocom-bb/tree/src/host/layer23/src/ transceiver/trx.c?h=jolly/testing#n440
http://git.osmocom.org/osmocom-bb/tree/src/host/layer23/src/ transceiver/trx.c?h=sylvain/testing#n369
You can implement a dummy command handler for sylvain/testing. Or use jolly's branch. But as I remember, there was a problem with some firmware images:
http://osmocom.org/projects/baseband/wiki/Toolchain
note: as of 2013-10-20, if you use a toolchain with gcc >=4.8, the firmware can be compiled, but will hang as soon as you want to sync to an ARFCN. This issue has been fixed in master.
http://cgit.osmocom.org/osmocom-bb/commit/ ?id=a903b3c1ee27047c79728b18ff6340d23d1aad2e
I think this information is enough to solve your problem. And moreover, we are using the openbsc mailing list, while there is a dedicated one. Let's finish this thread here.
And good luck!
With best regards, Vadim Yanitskiy.
Ok. Thanks Vadim.
really helpfull. :-)
DUO
On Wed, Jan 10, 2018 at 12:47 AM, Vadim Yanitskiy axilirator@gmail.com wrote:
Hi,
I tried to install Jolly branch many times and this is the debug result which always stop when sync to BTS.
I was thinking the package is broken? testing with sylvain is work, just like yesterday my registering still problem. but this Jolly branch even cannot produce sync.
Hmm, I just found out that both handover related commands are implemented in jolly/testing, but not in sylvain/testing:
http://git.osmocom.org/osmocom-bb/tree/src/host/layer23/src/ transceiver/trx.c?h=jolly/testing#n440
http://git.osmocom.org/osmocom-bb/tree/src/host/layer23/src/ transceiver/trx.c?h=sylvain/testing#n369
You can implement a dummy command handler for sylvain/testing. Or use jolly's branch. But as I remember, there was a problem with some firmware images:
http://osmocom.org/projects/baseband/wiki/Toolchain
note: as of 2013-10-20, if you use a toolchain with gcc >=4.8, the firmware can be compiled, but will hang as soon as you want to sync to an ARFCN. This issue has been fixed in master.
http://cgit.osmocom.org/osmocom-bb/commit/ ?id=a903b3c1ee27047c79728b18ff6340d23d1aad2e
I think this information is enough to solve your problem. And moreover, we are using the openbsc mailing list, while there is a dedicated one. Let's finish this thread here.
And good luck!
With best regards, Vadim Yanitskiy.