Re: Osmo-pcu error: PCU interface version number of BTS (7) is different (9).
Sorry forgot to reply-all and didn't send original mail to ML, re-sending now. On 9/14/18 3:25 PM, Pau Espin Pedrol wrote:
Hi Rafael,
You may want to check at PCU_IF_VERSION in both osmo-pcu.git and osmo-pcu.git
It seems that you are running a recent osmo-pcu together with a quite old osmo-bts (from at least Feb 28 2018, see osmo-bts.git 4046e3b3dd0cffd53d8d0d1f3e1bf9d0dec83ede), and they are not protocol compatible.
So you need to either use a newer osmo-bts (preferred I guess) or switch to an older osmo-pcu which uses PCU_IF_VERSION 7.
If you are using NuRan original firmware, you either ask them to update their stuff or your are pretty much on your own to build new images (with non-upstream osmocom versions afaik).
At sysmocom we maintain meta-sysmocom-bsp [1] which together with system-images [2] and osmocom's meta-telephny [3] allows to build firmware for both sysmobts and litecell 1.5 machines, together with SDKs to compile software for them.
I think generated images are not available publicly, but I guess you can either attempt building them yourself or perhaps ask sysmocom customer support to have access to it.
[1] https://git.sysmocom.de/poky/meta-sysmocom-bsp/ [2] https://git.sysmocom.de/poky/system-images/ [3] https://git.osmocom.org/meta-telephony/
Regards, Pau
-- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
Hi again, I forgot to say, if you look at those repositories, you need to check either branch "201705" (pointing to latest releases, similar to "latest" debian osmocom repo), or branch laforge/nightly, which points to osmocom master (similar o "nightly" from osmocom debian repos). -- - Pau Espin Pedrol <pespin@sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte
Thanks Pau! I'll ask NuRan to check if they can provide me a newer BTS software. If not, I understand I can compile stuff for the LC 1.5, but how about the closed source firmware / software, how can I create an image for the board without these proprietary pieces? Rafael Diniz On 09/14/2018 10:26 AM, Pau Espin Pedrol wrote:
Sorry forgot to reply-all and didn't send original mail to ML, re-sending now.
On 9/14/18 3:25 PM, Pau Espin Pedrol wrote:
Hi Rafael,
You may want to check at PCU_IF_VERSION in both osmo-pcu.git and osmo-pcu.git
It seems that you are running a recent osmo-pcu together with a quite old osmo-bts (from at least Feb 28 2018, see osmo-bts.git 4046e3b3dd0cffd53d8d0d1f3e1bf9d0dec83ede), and they are not protocol compatible.
So you need to either use a newer osmo-bts (preferred I guess) or switch to an older osmo-pcu which uses PCU_IF_VERSION 7.
If you are using NuRan original firmware, you either ask them to update their stuff or your are pretty much on your own to build new images (with non-upstream osmocom versions afaik).
At sysmocom we maintain meta-sysmocom-bsp [1] which together with system-images [2] and osmocom's meta-telephny [3] allows to build firmware for both sysmobts and litecell 1.5 machines, together with SDKs to compile software for them.
I think generated images are not available publicly, but I guess you can either attempt building them yourself or perhaps ask sysmocom customer support to have access to it.
[1] https://git.sysmocom.de/poky/meta-sysmocom-bsp/ [2] https://git.sysmocom.de/poky/system-images/ [3] https://git.osmocom.org/meta-telephony/
Regards, Pau
I want to add that I asked Rafael to take a quick look at the performance of the Nuran supplied osmo-pcu on the LC 1.5, given that he has one to hand and I don't. :) This is partly in relation to this ticket: http://osmocom.org/issues/2603 titled "Review the various incomplete and never merged changes in radisys branch" Having taken a look at those branches, I noted that the most recent commit there (in the egprs_features branch) is quite old, from December 2016, and that this same commit appears in the nuran open access lc15 branch https://gitlab.com/nrw_noa/osmo-pcu/commit/f9bc46bf13028cc21763e56a0be41d85e... although this particular commit is not is osmo master branch. Si, it seems some of the radisys work made it back into osmo master (via nrw_noa) at some point, but then the two diverged again. I did ask Nuran about this last year and I was told the "there's not always time/resources to pursue code review" answer. There is currently quite a large set of differences between https://gitlab.com/nrw_noa/osmo-pcu/commits/nrw/litecell15 and osmo master. A small amount of it is LC15 specific, but most is not. As Rafaels feedback about the quick functionality test of EGPRS was good, I want to take a closer look at this. My prime motivation is the somewhat broken unknown TA handling in current osmo-pcu master that Max worked on: http://osmocom.org/issues/1526 It seems from a few quick glances that a lot of what is in the radisys branches is in the noa repo and also in osmo-pcu master. I wonder if it's worth assuming that anything useful there made it's way into the noa branch and it would be better to work from there? I'd appreciate some guidance on how to go about that. If I find things that look useful, cherry pick them into osmo master and test and all looks good, should I propose them verbatim on gerrit for review? Should I keep the orginal commit messages and author, even if I were to make small changes, in the case i should spot something that I know would help with passing code review? Thanks! K.
participants (3)
-
Keith -
Pau Espin Pedrol -
Rafael Diniz