FCDEV3B bring-up status

Serg l serg at tvman.us
Mon Apr 17 13:34:44 UTC 2017

You mentioned running Slackware. Personally I have no specific preference,
so if you would share dev host details,like distro version, kernel version
and etc. I can just follow known good configuration. At this stage I'm not
into reinventing the wheel.

I also like FT2232D option as it supports SPI on the port A, something I
will definitely explore later on.

On Apr 17, 2017 3:25 AM, "Mychaela Falconia" <mychaela.falconia at gmail.com>

> Hi Serg,
> > Just a quick report that I received the board and was able to load a
> fresh
> > build of magnetite from the repo into xram.
> Awesome!
> > The next step would be to perform calibration.
> Have fun! :-)
> > I see that in order to run high baud rate of the serial interface a
> driver
> > patch is needed.
> Either that, or use a CP2102 adapter on which you would only need to
> program the EEPROM once.  I use FT2232D because for my area of interest
> (full classic modem functionality) I would like to connect both UARTs
> and using a single USB device for the two UARTs is better for sanity,
> but if you only need to connect one UART (for what you are doing having
> just RVTMUX should be sufficient), then CP2102 becomes an attractive
> option.
> If you would like to try the CP2102 route, there are CP2102 adapters
> sold on ebay with the 3.3V serial interface brought out on male header
> pins, so you would connect that adapter to FCDEV3B in exactly the same
> way as how you must have done it with the FT2232D adapter board I sent
> you.  You would need to program the CP2102 EEPROM per the instructions
> in OsmocomBB wiki.
> > I have my dev environment set up on Ubuntu 16 LTS, however
> > it would be nice to establish some sort of a common baseline.
> > Build host Linux distro and version
> > No automatic updates, toolchain should provide reliable and predictable
> > environment. List of software packages installed along with their
> versions.
> > This will make troubleshooting much easier.
> >
> > Should we consider hosting of the GCC based build environment in the
> repo,
> > just like Wine stuff? KVM or virtual box images? Or maybe builtroot with
> > selfhosted sources, so it can be rebuilt in a canonical way from scratch
> if
> > needed.
> If you send me your ssh public key and your preferred username, I'll
> create you an account on the freecalypso.org server that comes with a
> member web directory where you can upload stuff you'd like to publish:
> anything you upload to /var/www/members/<your_username> will appear on
> the web server under /members/<your_username>/.  You can then create
> whatever packages you like in whatever format you like, upload them
> there, and share the URL with the community.
> M~
> _______________________________________________
> Community mailing list
> Community at freecalypso.org
> https://www.freecalypso.org/mailman/listinfo/community

More information about the Community mailing list