Hi,
>I wasn't aware that such a command exists. However, the --run option
>seems to call the script "runimage". You might want to take a look at
>the options being set or maybe simply retrieve the qemu command line
>created by it (if that's not how you created your first command line).
>Sorry to
On Fri, Mar 1, 2024 at 6:48 PM Faiq Ali Sayed wrote:
>
> Hi Clément,
>
> So the output of the command
> | $ qemu-system-aarch64 -M xlnx-zcu102 -m 4G -no-reboot -nographic
> -kernel qnx.img
> is
>
> $ pulseaudio: set_sink_input_volume() failed
> $ pulseaudio: Reason: Invalid argument
> $ pulseaudi
Hi Clément,
So the output of the command
| $ qemu-system-aarch64 -M xlnx-zcu102 -m 4G -no-reboot -nographic
-kernel qnx.img
is
$ pulseaudio: set_sink_input_volume() failed
$ pulseaudio: Reason: Invalid argument
$ pulseaudio: set_sink_input_mute() failed
$ pulseaudio: Reason: Invalid argument
I
Hi Faiq,
On Fri, Feb 23, 2024 at 3:55 PM Faiq Ali Sayed wrote:
>
> So as far as my understanding, we provide these binaries using Qemu command
> as depicted in the example you provided and there is no way I found to put
> them into a single image.
> Regarding the overlapping space, I don't have
So as far as my understanding, we provide these binaries using Qemu command
as depicted in the example you provided and there is no way I found to put
them into a single image.
Regarding the overlapping space, I don't have much idea but I think we
could provide a starting address separately to thes
Peter Maydell writes:
(adding the other ZyncMP maintainers to the CC)
> On Wed, 21 Feb 2024 at 18:20, Faiq Ali Sayed wrote:
>>
>>
>>>
>>> This is also useful information. I would suggest you look
>>> at what the difference is between the image that boots and
>>> the one that doesn't: is it the
On Wed, 21 Feb 2024 at 18:20, Faiq Ali Sayed wrote:
>
>
>>
>> This is also useful information. I would suggest you look
>> at what the difference is between the image that boots and
>> the one that doesn't: is it the same format (and what format
>> is that)? is the way it is loaded on the real har
> This is also useful information. I would suggest you look
> at what the difference is between the image that boots and
> the one that doesn't: is it the same format (and what format
> is that)? is the way it is loaded on the real hardware the
> same, or different?
I am not able to distinguish b
On Tue, 20 Feb 2024 at 22:22, Faiq Ali Sayed wrote:
>
> The real hardware ( xlnx-zcu102 ) is being used for our software. The
> software is in the development phase, and for that, I need to create a VM for
> simulation purposes.
> Qemu has a machine type (-M xlnx-zcu102) which is supported with
Hi Alex,
I have created a new QNX image, particularly for Qemu, and still, both the
prompts are hanging without any further details.
Please have a look at the results of both terminals below
qemu-system-aarch64.exe -M xlnx-zcu102 -m 16G -serial mon:stdio -display
none -device loader,file="C:ifs.b
The real hardware ( xlnx-zcu102 ) is being used for our software. The
software is in the development phase, and for that, I need to create a VM
for simulation purposes.
Qemu has a machine type (-M xlnx-zcu102) which is supported with the
board/hardware.
I have two more images for the same hardware
On Tue, 20 Feb 2024 at 20:56, Faiq Ali Sayed wrote:
>
> The image I am using is currently in use for real hardware, and
> I received it from a third party/vendor.
OK, so what exactly is the real hardware it's for?
> Could you please suggest to me what I can do now?
If QEMU has a model of the ha
The image I am using is currently in use for real hardware, and I
received it from a third party/vendor.
Could you please suggest to me what I can do now?
br!
Faiq
On Tue, Feb 20, 2024 at 6:14 PM Alex Bennée wrote:
> Faiq Ali Sayed writes:
>
> > Alex thanks for the reply,
> >
> > I don't kno
Faiq Ali Sayed writes:
> Alex thanks for the reply,
>
> I don't know what the debug symbol is, but my target system is QNX aarch64
> below are the configuration of GDB,
>
> (gdb) show configuration
> This GDB was configured as follows:
>configure --host=x86_64-pc-linux-gnu --target=aarch64-u
Alex thanks for the reply,
I don't know what the debug symbol is, but my target system is QNX aarch64
below are the configuration of GDB,
(gdb) show configuration
This GDB was configured as follows:
configure --host=x86_64-pc-linux-gnu
--target=aarch64-unknown-nto-qnx7.1.0
--with-
Faiq Ali Sayed writes:
> Hi everyone,
> I am facing an issue during booting QNX VM using Qemu,
> I have an image to Boot the VM. and when I trigger a Qemu command to create a
> VM it is stuck.
> I also used a debugger to investigate but I can not see any result by GDB.
>
> Here is the output of
Hi everyone,
I am facing an issue during booting QNX VM using Qemu,
I have an image to Boot the VM. and when I trigger a Qemu command to create
a VM it is stuck.
I also used a debugger to investigate but I can not see any result by GDB.
Here is the output of first windows
qemu-system-aarch64 -M x
17 matches
Mail list logo
