[qemu]: How to use qemu to run 64MB bmc image?

[qemu]: How to use qemu to run 64MB bmc image?

[www]

[-- Attachment #1: Type: text/plain, Size: 225 bytes --]

Hi Joel Stanley, Andrew Jeffery, Cédric Le Goater,


How to modify it so that QEMU can run 64MB BMC image?
In addition, how to learn the source code of QEMU? Are there any guidelines and reference documents?


thanks，
Byron

[-- Attachment #2: Type: text/html, Size: 581 bytes --]

Re: [qemu]: How to use qemu to run 64MB bmc image?

[Cédric Le Goater]

Hello,

On 8/6/20 3:58 AM, www wrote:
> Hi Joel Stanley, Andrew Jeffery, Cédric Le Goater,
> 
> How to modify it so that QEMU can run 64MB BMC image?

You can increase the FW image file size with 'dd' or with :

  cat foo foo > bar

if the expected size is 128MB

C.

> In addition, how to learn the source code of QEMU? Are there any guidelines and reference documents?
> 
> thanks，
> Byron
> 
> 
>  
> 

Re: [qemu]: How to use qemu to run 64MB bmc image?

[Philippe Mathieu-Daudé]

On 8/6/20 3:54 PM, Cédric Le Goater wrote:
> Hello,
> 
> On 8/6/20 3:58 AM, www wrote:
>> Hi Joel Stanley, Andrew Jeffery, Cédric Le Goater,
>>
>> How to modify it so that QEMU can run 64MB BMC image?
> 
> You can increase the FW image file size with 'dd' or with :
> 
>   cat foo foo > bar
> 
> if the expected size is 128MB

You can use 'truncate' from coreutils:

$ truncate -s 128M image.bin

> 
> C.
> 
>> In addition, how to learn the source code of QEMU? Are there any guidelines and reference documents?
>>
>> thanks，
>> Byron
>>
>>
>>  
>>
> 
> 

Re: [qemu]: How to use qemu to run 64MB bmc image?

[Joel Stanley]

On Thu, 6 Aug 2020 at 15:12, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> On 8/6/20 3:54 PM, Cédric Le Goater wrote:
> > Hello,
> >
> > On 8/6/20 3:58 AM, www wrote:
> >> Hi Joel Stanley, Andrew Jeffery, Cédric Le Goater,
> >>
> >> How to modify it so that QEMU can run 64MB BMC image?
> >
> > You can increase the FW image file size with 'dd' or with :
> >
> >   cat foo foo > bar
> >
> > if the expected size is 128MB
>
> You can use 'truncate' from coreutils:
>
> $ truncate -s 128M image.bin

Nice tip!

(What an obvious name for a tool to extend files)

Cheers,

Joel

Re:Re: [qemu]: How to use qemu to run 64MB bmc image?

[www]

[-- Attachment #1: Type: text/plain, Size: 4251 bytes --]

hi,


Thank you for your reply. 
I mean: I've modified the OBMC project to generate 64MB of BMC image, which can run smoothly on the actual machine. I tried to run 64MB BMC image in QEMU, but failed.




I want to ask: 
1. Do I need to modify QEMU source code and recompile it?

2. How to modify it if necessary?

3. Is there any document about QEMU that can help me understand the working principle of QEMU quickly?


console log：
[    5.557654] Checked W+X mappings: passed, no W+X pages found
[    5.558203] Run /init as init process
rofs = mtd4 squashfs rwfs = mtd5 jffs2
mount: mounting /dev/loop0 on run/initramfs/ro failed: Invalid argument
[   18.297377] jffs2: Too few erase blocks (0)
mount: mounting /dev/mtdblock5 on run/initramfs/rw failed: Invalid argument


Mounting read-write /dev/mtdblock5 filesystem failed.  Please fix and run
        mount /dev/mtdblock5 run/initramfs/rw -t jffs2 -o rw
to to continue, or do change nothing to run from RAM for this boot.
Enter password to try to manually fix.
After fixing run exit to continue this script, or reboot -f to retry, or
touch /takeover and exit to become PID 1 allowing editing of this script.
Give root password for system maintenance
(or type Control-D for normal startup):


qemu log：
aspeed_soc.io: unimplemented device read (size 4, offset 0x80064)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80060)
aspeed_soc.io: unimplemented device write (size 4, value 0x47f0000, offset 0x80060)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80060)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80064)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80060)
aspeed_soc.io: unimplemented device write (size 4, value 0x4200000, offset 0x80060)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80060)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80064)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80060)
aspeed_soc.io: unimplemented device write (size 4, value 0x4000000, offset 0x80060)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80060)
aspeed_soc.io: unimplemented device read (size 4, offset 0x80064)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa0008)
aspeed_soc.io: unimplemented device write (size 4, value 0x1ff, offset 0xa000c)
aspeed_soc.io: unimplemented device write (size 4, value 0x80030800, offset 0xa0000)
aspeed_soc.io: unimplemented device write (size 4, value 0x80070800, offset 0xa0000)
aspeed_soc.io: unimplemented device write (size 4, value 0x33f, offset 0xa0020)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa0020)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa0010)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa0014)
aspeed_soc.io: unimplemented device write (size 4, value 0x7fff, offset 0xa0018)
aspeed_soc.io: unimplemented device write (size 4, value 0x7fff, offset 0xa001c)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa0030)
aspeed_soc.io: unimplemented device write (size 4, value 0x5, offset 0xa0038)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa003c)
aspeed_soc.io: unimplemented device write (size 4, value 0x9b040000, offset 0xa0034)
aspeed_soc.io: unimplemented device write (size 4, value 0x0, offset 0xa0004)
aspeed_soc.io: unimplemented device write (size 4, value 0x80070801, offset 0xa0000)
aspeed_soc.io: unimplemented device write (size 4, value 0x101cb, offset 0xa0008)




thank you,
Byron

















At 2020-08-07 06:09:26, "Joel Stanley" <joel@jms.id.au> wrote:
>On Thu, 6 Aug 2020 at 15:12, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> On 8/6/20 3:54 PM, Cédric Le Goater wrote:
>> > Hello,
>> >
>> > On 8/6/20 3:58 AM, www wrote:
>> >> Hi Joel Stanley, Andrew Jeffery, Cédric Le Goater,
>> >>
>> >> How to modify it so that QEMU can run 64MB BMC image?
>> >
>> > You can increase the FW image file size with 'dd' or with :
>> >
>> >   cat foo foo > bar
>> >
>> > if the expected size is 128MB
>>
>> You can use 'truncate' from coreutils:
>>
>> $ truncate -s 128M image.bin
>
>Nice tip!
>
>(What an obvious name for a tool to extend files)
>
>Cheers,
>
>Joel

[-- Attachment #2: Type: text/html, Size: 7597 bytes --]