On 1 November 2017 at 18:31, poxyran wrote:
>
>
> On 11/1/2017 1:07 PM, Peter Maydell wrote:
>> On 1 November 2017 at 13:34, poxyran wrote:
>>> Hi all!,
>>>
>>> I'm trying to emulate a firmware from a DLink IP camera using
>>> qemu-system-arm but I'm facing some troubles.
>>>
>>> I'm using the fo
On 11/1/2017 1:07 PM, Peter Maydell wrote:
> On 1 November 2017 at 13:34, poxyran wrote:
>> Hi all!,
>>
>> I'm trying to emulate a firmware from a DLink IP camera using
>> qemu-system-arm but I'm facing some troubles.
>>
>> I'm using the following command line:
>>
>> fastix@bulin:~/QEMU/armel$ s
On 1 November 2017 at 13:34, poxyran wrote:
> Hi all!,
>
> I'm trying to emulate a firmware from a DLink IP camera using
> qemu-system-arm but I'm facing some troubles.
>
> I'm using the following command line:
>
> fastix@bulin:~/QEMU/armel$ sudo qemu-system-arm -M versatilepb -kernel
> vmlinuz-2.
Hi all!,
I'm trying to emulate a firmware from a DLink IP camera using
qemu-system-arm but I'm facing some troubles.
I'm using the following command line:
fastix@bulin:~/QEMU/armel$ sudo qemu-system-arm -M versatilepb -kernel
vmlinuz-2.6.32-5-versatile -initrd
/home/fastix/dcs-942l/binary_blob.b
Hi all,
I'm trying to debug u-boot running as BIOS in qemu (BTW, the problem is
'trying to execute code outside RAM or ROM at 0x000a'). So I run
qemu-system-x86_64 -bios /path/to/bios.rom -s -S
and connect with gdb using
target remote localhost:1234
command. I start at 0x00
Thanks. In fact, I don't need QEMU to have realized this kind of trace
about instructions and therefore this is my ToDoList on QEMU.
Now I have made some progress and still have some problems.
So far, I have found that in the source code of
QEMU(qemu-2.7.0-rc5-5/tcg/tcg-opc.h) there are a lot of
On 1 November 2017 at 02:35, 李阳 wrote:
> Recently, I want to use QEMU to trace the instruction features of the
> specified binary.
>
> My host: X86
> Guest: ARMv8,
>
> I run the benchmark on the AArch64 Operating System in QEMU and I want to
> collect the instruction data of the binary.
> The inst
On 31 October 2017 at 22:10, William Mahoney wrote:
> But of course the code writes to the interrupt controller
> mask registers to enable and disable things. How does this
> get “wired in” to qemu? I will need to tell it “yes you can
> generate interrupt 27 now”?
>
> Just aim me at a good example
