Actually we are using bit older version of coreboot (pre fmap
implementation) So we took intel help and they provided us base location
(in RAM) where coreboot is loaded and then we calculated as follows which
is working for me.
ptr = *(grub_uint32_t *)(LOADING_BASE + COREBOOT_ROM_SIZE - 4);
On Sat, Mar 25, 2017, 00:40 Andrei Borzenkov wrote:
> 25.03.2017 10:22, Vladimir 'phcoder' Serbinenko пишет:
> > On Sat, Mar 25, 2017, 00:16 Andrei Borzenkov
> wrote:
> >
> >> 24.03.2017 21:38, Gailu Singh пишет:
> >>> This is how it is calculated in coreboot
> >>>
> >>>
> >>
> https://review.co
25.03.2017 10:22, Vladimir 'phcoder' Serbinenko пишет:
> On Sat, Mar 25, 2017, 00:16 Andrei Borzenkov wrote:
>
>> 24.03.2017 21:38, Gailu Singh пишет:
>>> This is how it is calculated in coreboot
>>>
>>>
>> https://review.coreboot.org:4430/cgit/coreboot.git/tree/src/lib/cbfs.c?id=refs/heads/maste
On Sat, Mar 25, 2017, 00:16 Andrei Borzenkov wrote:
> 24.03.2017 21:38, Gailu Singh пишет:
> > This is how it is calculated in coreboot
> >
> >
> https://review.coreboot.org:4430/cgit/coreboot.git/tree/src/lib/cbfs.c?id=refs/heads/master#n268
> >
> > ___FMAP__COREBOOT_BASE and ___FMAP__COREBOOT_S
24.03.2017 21:38, Gailu Singh пишет:
> This is how it is calculated in coreboot
>
> https://review.coreboot.org:4430/cgit/coreboot.git/tree/src/lib/cbfs.c?id=refs/heads/master#n268
>
> ___FMAP__COREBOOT_BASE and ___FMAP__COREBOOT_SIZE are based on values
> available in fmd files (depending on 8MB
This is how it is calculated in coreboot
https://review.coreboot.org:4430/cgit/coreboot.git/tree/src/lib/cbfs.c?id=refs/heads/master#n268
___FMAP__COREBOOT_BASE and ___FMAP__COREBOOT_SIZE are based on values
available in fmd files (depending on 8MB/16Mb coreboot).
#grep -r FMAP__COREBOOT_BASE s
24.03.2017 20:32, Gailu Singh пишет:
>>> Could you please reference the solution for future users with the same
> problem?
> Sure. Infect I should have detailed it without asking. Sorry for that.
>
> Solution can be referenced to following thread in coreboot mailing list
> that provide details of
>>Could you please reference the solution for future users with the same
problem?
Sure. Infect I should have detailed it without asking. Sorry for that.
Solution can be referenced to following thread in coreboot mailing list
that provide details of memory mapping on the board answered by Adrian
h
On Fri, Mar 24, 2017, 10:17 Gailu Singh wrote:
> It was indeed the ROM mapping issue. solved now. Thank you so much Andrei.
>
Could you please reference the solution for future users with the same
problem?
>
> On Fri, Mar 17, 2017 at 7:29 PM, Gailu Singh wrote:
>
> >>Any chance ROM is mapped so
It was indeed the ROM mapping issue. solved now. Thank you so much Andrei.
On Fri, Mar 17, 2017 at 7:29 PM, Gailu Singh wrote:
> >>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
> wrote:
>
>> On
>>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
wrote:
> On Fri, Mar 17, 2017 at 4:24 PM, Gailu Singh wrote:
> > @Vladimir
> > I do not have serial console (board has memory mapped uart not support in
On Fri, Mar 17, 2017 at 4:24 PM, Gailu Singh 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
> an
@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
On Thu, Mar 16, 2017, 22:30 Gailu Singh 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 /
On Fri, Mar 17, 2017, 00:01 Andrei Borzenkov wrote:
> On Fri, Mar 17, 2017 at 9:19 AM, Gailu Singh wrote:
> >>>What address it prints?
> >
> > I followed suggested steps and I see following print
> >
> > fs/cbfs.c:347: head=0x
> >
>
> Then you need to contact coreboot developers and disc
On Fri, Mar 17, 2017 at 9:19 AM, Gailu Singh wrote:
>>>What address it prints?
>
> I followed suggested steps and I see following print
>
> fs/cbfs.c:347: head=0x
>
Then you need to contact coreboot developers and discuss it. GRUB
looks at predefined location at address of cbfs. If this l
>>What address it prints?
I followed suggested steps and I see following print
fs/cbfs.c:347: head=0x
On Fri, Mar 17, 2017 at 8:57 AM, Andrei Borzenkov
wrote:
> 16.03.2017 22:43, Gailu Singh пишет:
> >>> Try insmod cbfs
> >
> >>
> > Trieed, it does not help. BTW cbfs is already inclu
16.03.2017 22:43, Gailu Singh пишет:
>>> 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 pa
On Thu, Mar 16, 2017, 12:43 Gailu Singh 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='l
>>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
On Thu, Mar 16, 2017, 12:18 Gailu Singh 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) (ah
21 matches
Mail list logo
