FCDEV3B bring-up status
Serg l
serg at tvman.us
Thu May 4 04:35:38 UTC 2017
Didn't have chance to test this, but seems like FLASH2_BASE_ADDR is not
defined anywhere, but I guess it should be 0x01800000 ?
struct dev_s dev = {
.base = (char *) FLASH2_BASE_ADDR +
CONFIG_AFTERMARKET_FFS_START * 0x40000,
.manufact = MANUFACT_AMD,
.blocksize = 0x40000,
.blocksize_ld = 18,
.driver = FFS_DRIVER_AMD,
.numblocks = CONFIG_AFTERMARKET_FFS_NBLOCKS,
};
On Wed, May 3, 2017 at 11:50 PM, Serg l <serg at tvman.us> wrote:
> Didn't dig to much, but trying aftermarket-ffs or fcfam-ffs when
> Citrine is loaded via fc-xram results in following error from fc-fsio
>
> fsio> ls /
> opendir: FFS error 1 (EFFS_NODEVICE: flash device unknown)
>
> Rebooted into magnetite from flash shows normal content
> fsio> ls /
> .journal
> gsm
> pcm
> sys
> mmi
> var
> aud
> etc
>
> Startup log fragment
> RV 00010001 3 RVM: SWE list built success
> RV 00010001 3 RVM: trying to launch SWE 0x000A0010
> RV 00010001 5 RVM: SWE memory bank allocation success
> RV 000A0010 5 SPI : spi_set_info: try to init GLOBAL INFO SPI structure ...
> RV 00010001 5 RVM: SWE set info functions called
> RV 00010001 5 RVM: Created task nb 0x00000003
> RV 000A0010 5 SPI_task: Initialization
> RV 00010001 5 RVM: Resumed task nb 0x00000003
> RV 00010001 5 RVM: Resumed SWE 0x000A0010
> RV 00010001 5 RVM: SWE initialization success
> RV 00010001 3 create_RVtasks: SPI (0x000a0010) started
> RV 00010001 5 RVM: SWE START REQUEST 0x001E0004
> RV 00010001 2 rvm.SweHndlr.resolve_t2_grouping(), SWE Not type 2:
> 0x001E0004
> RV 00010001 3 RVM: SWE list built success
> RV 00010001 3 RVM: trying to launch SWE 0x001E0004
> RV 00010001 5 RVM: SWE memory bank allocation success
> RV 00010001 5 RVM: SWE set info functions called
> RV 00010001 5 RVM: Created task nb 0x00000004
> RV 00010001 5 RVM: Resumed task nb 0x00000004
> RV 00010001 5 RVM: Resumed SWE 0x001E0004
> RV 00010001 5 RVM: SWE initialization success
> RV 00010001 5 RVM: Resumed SWE 0x001E0004
> RV 00010001 5 RVM: SWE initialization success
> RV 00010001 3 create_RVtasks: ETM (0x001e0004) started
> RV 00010001 5 RVM: SWE START REQUEST 0x000A0002
> RV 00010001 2 rvm.SweHndlr.resolve_t2_grouping(), SWE Not type 2:
> 0x000A0002
> RV 00010001 3 RVM: SWE list built success
> RV 00010001 3 RVM: trying to launch SWE 0x000A0002
> RV 00010001 5 RVM: SWE memory bank allocation success
> RV 000A0002 3 RTC : rtc_set_info: try to init GLOBAL INFO RTC structure ...
> RV 00010001 5 RVM: SWE set info functions called
> RV 00010001 5 RVM: Created task nb 0x00000005
> RV 00010001 5 RVM: Resumed task nb 0x00000005
> RV 00010001 5 RVM: Resumed SWE 0x000A0002
> RV 00010001 5 RVM: SWE initialization success
> RV 000A0002 3 RTC: Initialization
> RV 00010001 3 create_RVtasks: RTC (0x000a0002) started
> GPF sysprim id=B7 ts=00000025 SYST->TST "IS_STACK_TIME"
> GPF trace id=A7 ts=00000025 SYST->PCO "&0"
> RV 000A0004 2 ffs_init() 0
> RV 000A0004 2 FFS revision: 0x5056
> RV 000A0004 2 FFS device, driver: 0x01, 0x0000, 2
> RV 000A0004 2 FFS base, blocks: 0x1800000, 8
> RV 000A0004 2 FFS format read, write: 0x210, 0x210
> GPF trace id=A7 ts=00000098 SYST->PCO tc=05 "pei_init: no trace mask in
> FFS"
> GPF trace id=A7 ts=0000013A SYST->PCO "L1:em_l1_sem_index cleared"
> GPF trace id=A7 ts=0000013A SYST->PCO "DL version is FreeCalypso"
> GPF trace id=A7 ts=0000013A SYST->PCO "DL:em_dl_sem_index cleared"
> L1: > CPU 3 4
> L1: TST_C 3 TCS_2.1.1.14_L1_1454_0 FreeCalypso DSP:3606h DYN:6840h
> CHECKSUM:d278h
> RV 00010001 3 MEM STAT: Total memory required 0x00003CD0
> RV 00010001 3 MEM STAT: Total memory obtained 0x00003DD8
> RV 00010001 3 MEM STAT: Total memory used 0x00004690
> RV 00010001 3 MEM STAT: Mem usage ratio : 098.779419%
> RV 00010001 3 *** START DUMPING MEMORY BANK ***
> RV 00010001 3 **MB_NAME* Id Used_mem Watermark Limit Peak Nb_buff
> Avg_buf_size
> RV 00010001 3 RVM_PRIM 0 360 5900 6000 548 0
> 67
> RV 00010001 3 RV_TRACE 59 952 25000 25000 3740 0
> 64
> RV 00010001 3 RVM_STACKS 6 7248 7948 7948 7248 0
> 1208
> RV 00010001 3 RVM_SYS 7 1976 8900 9000 1976 0
> 93
> RV 00010001 3 RVM_TIMER 8 0 2500 3000 0 0
> 0
> RV 00010001 3 RVM_NOTIFY 9 0 2500 3000 0 0
> 0
> RV 00010001 3 FFS_PRIM 10 48 6216 9216 96 0
> 48
> RV 00010001 3 SPI_PRIM 11 24 200 256 24 0
> 24
> RV 00010001 3 ETM_PRIM 12 8 1024 1024 48 0
> 32
> RV 00010001 3 RTC_PRIM 13 20 80 100 20 0
> 10
> RV 00010001 3 TOTAL: ******** 10732********** 64544 13700
> RV 00010001 3 *** START DUMPING MEMORY ***
> RV 00010001 3 Total memory available 0x000138AC
> RV 00010001 3 Memory currently in use 0x00003168
> RV 00010001 3 *** START DUMPING TASKS ***
> RV 00010001 3 *TASK_NAME Id Stack_size Used_stack
> RV 00010001 3 RVM 0 1500 792
> RV 00010001 3 TRACE 1 2000 276
> RV 00010001 3 FFS 2 1024 296
> RV 00010001 3 SPI 3 1000 224
> RV 00010001 3 ETM 4 1024 252
> RV 00010001 3 RTC 5 700 224
> RV 00010001 3 RV_START 29 1024 456
> GPF trace id=A7 ts=00000163 SYST->PCO "RR:em_rr_sem_index cleared"
> GPF trace id=A7 ts=00000163 SYST->PCO tc=05 "All tasks entered main loop"
> L1: ADC_R 28
> RV 000A0010 5 SPI: ADC are on
> L1: ADC :101 0
> L1: > CPU 95 35
>
> And here I connect fsio
>
> *** Client program connected
> L1: ADC :2447 0
> RV 000A0010 5 IQ EXT: ADC End
> L1: ADC :2549 0
> RV 000A0010 5 IQ EXT: ADC End
> L1: ADC :2651 0
> RV 000A0010 5 IQ EXT: ADC End
> L1: ADC :2753 0
> L1: > CPU 2747 35
> RV 000A0010 5 IQ EXT: ADC End
> L1: ADC :2855 0
> RV 000A0010 5 IQ EXT: ADC End
> Sent 14 07 6F 02 2F 00 45
> TM: 07 01 06
> RV 001E0004 2 ETM: _error_packet_send: Module(0x7) ERROR(-1)
> TM: 07 01 06
> RV 001E0004 2 ETM: _task: mid(0x7) ERROR(-1)
> L1: ADC :2957 0
> RV 000A0010 5 IQ EXT: ADC End
>
> build config
>
> target fcdev3b
> feature gsm
> feature at-rvtmux
>
> feature etm
> feature aftermarket-ffs 0 8
>
> Thanks,
> -Serg
>
> On 5/3/17, Serg l <serg at tvman.us> wrote:
> > BTW, I created Slackware 13.37 build system and it produced binary
> > identical Magnetite image to what Mychaela sent to me earlier. If anybody
> > wants a VMWare Player image, just let me know and I will make a copy.
> >
> > On Wed, May 3, 2017 at 12:24 AM, Serg l <serg at tvman.us> wrote:
> >
> >> 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
> >>>
> >>
> >>
> >
>
More information about the Community
mailing list