>>Any chance ROM is mapped somewhere else in your case? I need to check, this may be a case.
On Fri, Mar 17, 2017 at 7:16 PM, Andrei Borzenkov <arvidj...@gmail.com> wrote: > On Fri, Mar 17, 2017 at 4:24 PM, Gailu Singh <gail...@gmail.com> wrote: > > @Vladimir > > I do not have serial console (board has memory mapped uart not support in > > grub) to capture memory details. Also on graphics console I can not give > > commands from usb keyboard to dump memory because USB port on board are > 3.0 > > and USB 3.0 is not supported in Grub. Any other thing I could try? > > > > @Andrei > > What is the expected address supposed to be printed for successful > > identification of CBFS. > > > > GRUB reads 4 bytes at offset 0xffffffc0. All ones likely means that > this address simply is not valid. > > According to https://github.com/mrnuke/coreboot/blob/master/ > documentation/cbfs.txt, > "A pointer to the location of the header will be located at offset -4 > from the end of the ROM. This translates to address 0xFFFFFFFC on a > normal x86 system." Any chance ROM is mapped somewhere else in your > case? > > > I am building coreboot image myself and stitching with other intel > firmware > > as documented by Intel. > > > > On Fri, Mar 17, 2017 at 12:45 PM, Vladimir 'phcoder' Serbinenko > > <phco...@gmail.com> wrote: > >> > >> > >> > >> On Thu, Mar 16, 2017, 22:30 Gailu Singh <gail...@gmail.com> wrote: > >>> > >>> Please find coreboot image attached. Zipped it to reduce size > >> > >> This image is actually fine and is read correctly by fstest. Apparently > >> for some reason reading image at the end of 4GiB doesn't work. Can you > try > >> dumping last 8M before 4G mark from /dev/mem ? > >>> > >>> > >>> On Fri, Mar 17, 2017 at 1:19 AM, Vladimir 'phcoder' Serbinenko > >>> <phco...@gmail.com> wrote: > >>>> > >>>> > >>>> > >>>> On Thu, Mar 16, 2017, 12:43 Gailu Singh <gail...@gmail.com> wrote: > >>>>> > >>>>> >>Try insmod cbfs > >>>>> > >>>>> > >>>>> Trieed, it does not help. BTW cbfs is already included in my grub elf > >>>>> image so I don't think I need to do insmod. > >>>>> > >>>>> ./grub-mkstandalone --grub-mkimage=./grub-mkimage -O i386-coreboot -o > >>>>> default_payload.elf --modules='ls ahci pata ehci uhci ohci > usb_keyboard > >>>>> usbms part_msdos ext2 fat at_keyboard part_gpt usbserial_usbdebug > cbfs' > >>>>> --install-modules='linux search configfile normal cbtime cbls memrw > iorw > >>>>> minicmd lsmmap lspci halt reboot hexdump pcidump regexp setpci > lsacpi chain > >>>>> test serial multiboot cbmemc linux16 gzio echo help syslinuxcfg xnu > affs afs > >>>>> bfs btrfs cbfs cpio cpio_be exfat ext2 fat hfs hfsplus iso9660 jfs > minix > >>>>> minix2 minix2_be minix3 minix3_be minix_be newc nilfs2 ntfs odc > procfs > >>>>> reiserfs romfs sfs squash4 tar udf ufs1 ufs1_be ufs2 xfs zfs > password_pbkdf2 > >>>>> ' --fonts= --themes= --locales= -d grub-core/ > >>>>> /boot/grub/grub.cfg=./coreboot.cfg > >>>>> > >>>>> This must be something else. AFAIK memdisk itself resides in CBFS, > >>>>> Strangely ls comman shows memdisk but not cbfsdisk > >>>> > >>>> Please share your coreboot image. > >>>>> > >>>>> > >>>>> > >>>>> On Fri, Mar 17, 2017 at 12:52 AM, Vladimir 'phcoder' Serbinenko > >>>>> <phco...@gmail.com> wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> On Thu, Mar 16, 2017, 12:18 Gailu Singh <gail...@gmail.com> wrote: > >>>>>>> > >>>>>>> Hi Experts, > >>>>>>> > >>>>>>> I am using grub2 with coreboot and configured with > >>>>>>> --with-platform=coreboot. > >>>>>>> > >>>>>>> I am able to load grub2 from coreboot. However when I run ls > command, > >>>>>>> I do not see cbfsdisk. ls only shows > >>>>>>> > >>>>>>> (memdisk) (ahci0) (ahci0,msdos1) (ahci0,msdos2) > >>>>>>> > >>>>>>> I have added file in the cbfs as follows and need to access it but > >>>>>>> when I try (cbfsdisk)/myfile I get error disk 'cbfsdisk' not found. > >>>>>>> > >>>>>>> build/util/cbfstool/cbfstool build/coreboot.rom add -f myfile -n > >>>>>>> myfile -t raw > >>>>>>> > >>>>>>> Any idea how to access myfile on cbfsdisk? > >>>>>> > >>>>>> Try insmod cbfs > >>>>>>> > >>>>>>> > >>>>>>> Thanks. > >>>>>>> _______________________________________________ > >>>>>>> Grub-devel mailing list > >>>>>>> Grub-devel@gnu.org > >>>>>>> https://lists.gnu.org/mailman/listinfo/grub-devel > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Grub-devel mailing list > >>>>>> Grub-devel@gnu.org > >>>>>> https://lists.gnu.org/mailman/listinfo/grub-devel > >>>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Grub-devel mailing list > >>>>> Grub-devel@gnu.org > >>>>> https://lists.gnu.org/mailman/listinfo/grub-devel > >>>> > >>>> > >>>> _______________________________________________ > >>>> Grub-devel mailing list > >>>> Grub-devel@gnu.org > >>>> https://lists.gnu.org/mailman/listinfo/grub-devel > >>>> > >>> > >>> _______________________________________________ > >>> Grub-devel mailing list > >>> Grub-devel@gnu.org > >>> https://lists.gnu.org/mailman/listinfo/grub-devel > >> > >> > >> _______________________________________________ > >> Grub-devel mailing list > >> Grub-devel@gnu.org > >> https://lists.gnu.org/mailman/listinfo/grub-devel > >> > > > > > > _______________________________________________ > > Grub-devel mailing list > > Grub-devel@gnu.org > > https://lists.gnu.org/mailman/listinfo/grub-devel > > > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel >
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel