FCDEV3B bring-up status

[Serg l]

I'm pretty sure that I saved it with me 102 and me 103, or at least I
issued commands. I used gta02 load agent for x-ram boot, don't really see
how it may affect ffc. The only explanation is that I done something stupid
like misconfig or fatfingered something.


It booted fine in mode 1, and sure thing it was rebooting without disabling
sleep mode, even being connected to 5W linear PSU with highly stable 3.3V
output

I will check out new ffs.

On Tue, May 2, 2017 at 11:48 PM, Mychaela Falconia <
mychaela.falconia at gmail.com> wrote:

> Hi Serg,
>
> > Another report. I flashed the image built by Mychaela, booted from it and
> > re-entered VCXO calibration values into FFS via tmsh.
>
> Re-entered via fc-tmsh?  Why were they not already in the non-volatile
> FFS?  Perhaps you forgot to save them in the flash with me 102 and
> me 103 commands the first time?  If so, it would surely explain why
> you were previously unable to lock onto a cell...
>
> > The MS registered with the network in one shot without any problems.
> > I was able to make and receive calls and SMS. I concluded this test by a
> > shot of whiskey in order to celebrate this milestone of the project.
>
> Yay!
>
> By the way, is your board booting fine from flash in mode 1, or did you
> have to use the flash boot mode 0 workaround?
>
> > The next step would be to try Citrine with the same FFS content.
>
> See the latest commit I just pushed into freecalypso-citrine, adding
> feature fcfam-ffs.  It has the same end effect as feature aftermarket-ffs,
> but is arguably cleaner when the hardware target is our own rather than
> aftermarket.
>
> M~
> _______________________________________________
> Community mailing list
> Community at freecalypso.org
> https://www.freecalypso.org/mailman/listinfo/community
>