Hi Mychaela,
On Thu, Sep 13, 2018 at 03:53:22PM -0800, Mychaela Falconia wrote:
Sysmocom has two of my FreeCalypso development boards,
To clarify: sysmocom != Harald.
I personally have bought one, which I have at home, and sysmocom has another one (at the sysmocom office/lab).
The board you've got set up there is the one that did get properly calibrated before being sold to Sysmocom. Like all boards from that batch, it was shipped with an official FreeCalypso firmware image in its flash - based on the date it was shipped, it was probably the 20170831 build. Do you still have that firmware image in the flash, or have you erased it?
Where is the RF from that board connected to - does it go to a sysmoBTS unit?
the way it looks, it has been connected to our osmo-gsm-tester setup, which basically is a coaxial RF distribution network to which a variety of BTSs (nanoBTS, sysmoBTS, USRP B2xx, UmTRX, ...) are connected, and where we run automatic continous tests with a set of modems against our latest "master" of the Osmocom stack.
Would it be possible for someone from Sysmocom (or someone from the community who have been set up with remote access to that board) to test and see if the FCDEV3B can successfully connect to Osmocom network using the official FreeCalypso firmware on the board, driven via AT commands?
This should all be possible. I doubt anyone has removed/erased the firmware on it.
In fact, I think that connecting the FCDEV to the osmo-gsm-tester setup might not be the best idea. It might be better to have a dedicated test setup with a single BTS and the FCDEV, to which we can then provide remote access. But let's have that discussion at https://osmocom.org/issues/2704
If Sysmocom folks are philosophically against doing any tests with FreeCalypso firmware,
I'm not sure where you would get such an idea from. We're happy to test whatever makes sense technically, and if there are any [suspected] interoperability problems with the Osmocom network-side stack, then we want to resolve those, no matter what the MS side implementation.