Re: Ast2600 emulation

2022-01-26 Thread abhijeet inamdar
How do we implement Hardware Semaphore (HSEM) in QEMU for this type? Any suggestions. BR. Abhijeet. On Wed, 15 Dec, 2021, 23:20 Philippe Mathieu-Daudé, wrote: > On 12/15/21 23:10, abhijeet inamdar wrote: > > Thanks, I'll check it out. > > > > Can we do full system m

Re: QOM

2021-12-21 Thread abhijeet inamdar
Hi, How did we decide the NUM_IRQ_LINES 64 for stellaris? BR. Abhijeet. On Tue, 21 Dec, 2021, 13:22 abhijeet inamdar, wrote: > As we have almost 80 irq lines and 40-45 NVIC_irq's. > > Where can I define them? > > BR. > Abhijeet. > > On Tue, 21 Dec, 2021

Re: QOM

2021-12-21 Thread abhijeet inamdar
As we have almost 80 irq lines and 40-45 NVIC_irq's. Where can I define them? BR. Abhijeet. On Tue, 21 Dec, 2021, 13:18 abhijeet inamdar, wrote: > Oh, > > In that case I have to define my irq set for a machine to handle the > exception and interrupts. > > BR. > Abhijee

Re: QOM

2021-12-21 Thread abhijeet inamdar
Oh, In that case I have to define my irq set for a machine to handle the exception and interrupts. BR. Abhijeet. On Tue, 21 Dec, 2021, 12:59 Philippe Mathieu-Daudé, wrote: > Hi Abhijeet, > > On 12/21/21 12:27, abhijeet inamdar wrote: > > Hi, > > > > 1)What does QO

QOM

2021-12-21 Thread abhijeet inamdar
Hi, 1)What does QOM stand for? 2)Can anyone tell what this error means? (qemu) Unexpected error in object_property_find() at /home/ocp/vcpu-playground/vcpu_on_qemu/qemu-4.2.0/qom/object.c:1177: qemu-system-arm: Property '.sysbus-irq[0]' not found Aborted (core dumped). Thanks for the help.

Re: Exception return

2021-12-16 Thread abhijeet inamdar
, Dec 16, 2021 at 9:02 PM abhijeet inamdar < abhijeetinamdar3...@gmail.com> wrote: > I made some changes to the code in qemu : > https://github.com/qemu/qemu/blob/stable-6.0/target/arm/cpu.c#L339 . I > have commented out the variable vecbase and directly given the address of >

Re: Exception return

2021-12-16 Thread abhijeet inamdar
. On Thu, Dec 16, 2021 at 7:47 PM Peter Maydell wrote: > On Thu, 16 Dec 2021 at 17:44, Philippe Mathieu-Daudé > wrote: > > > > Cc'ing qemu-arm developers. > > > > On 12/16/21 18:31, abhijeet inamdar wrote: > > > Hi, > > > > > > I was r

Re: Exception return

2021-12-16 Thread abhijeet inamdar
What might be the problem? or reasons for this error? BR. Abhijeet. On Thu, 16 Dec, 2021, 18:31 abhijeet inamdar, wrote: > Hi, > > I was running my .elf file on my custom machine(CM3) and was hit with this > error when debugging and had the required -d flags and sin

Exception return

2021-12-16 Thread abhijeet inamdar
Hi, I was running my .elf file on my custom machine(CM3) and was hit with this error when debugging and had the required -d flags and single stepping. IN: Hal_MemFault 0x7004e794: 4770 bx lr Trace 0: 0x7f4faa471100 [/7004e794/0x312000c1] Hal_MemFault R00=7004938d

Re: Ast2600 emulation

2021-12-15 Thread abhijeet inamdar
Thanks, I'll check it out. Can we do full system mode or qemu-sytem-arm ? BR. Abhijeet On Wed, 15 Dec, 2021, 22:38 Philippe Mathieu-Daudé, wrote: > On 12/15/21 22:24, abhijeet inamdar wrote: > > Hi, > > > > I was going through the aspeed ast2600(not evb) it

Ast2600 emulation

2021-12-15 Thread abhijeet inamdar
Hi, I was going through the aspeed ast2600(not evb) it has Dual-core Arm A7 and embedded M3. How can extend it/implementation in the existing one. 1) Is it possible ? 2) How can I do it? BR. Abhijeet.

Re: qemu: fatal: lockup...

2021-12-14 Thread abhijeet inamdar
t; On Fri, 10 Dec 2021 at 15:44, abhijeet inamdar > wrote: > > > > Hi, > > > > In the Qemu monitor: > > > > (qemu) info qom-tree > > /machine (vcpu-machine) > > /peripheral (container) > > /peripheral-anon (container) > > /unattached

Re: qemu: fatal: lockup...

2021-12-10 Thread abhijeet inamdar
github.com/qemu/qemu/blob/stable-4.2/target/arm/cpu.c#L1928-#L1929 > . > > Anyways I will use the newer Qemu but curious was this a problem in my > building? > Please let me know so that I can move forward. It's really important for > me. > > BR. > Abhijeet. > > On W

Re: qemu: fatal: lockup...

2021-12-08 Thread abhijeet inamdar
, 2021 at 3:11 PM abhijeet inamdar < abhijeetinamdar3...@gmail.com> wrote: > I will look into the latest one. Can you elaborate on that please! > > And I'm running a test.elf for the similar machine which I'm building. It > runs test only if the given size of the flash

Re: qemu: fatal: lockup...

2021-12-08 Thread abhijeet inamdar
to be changed or I wandering I'm doing something wrong? BR. Abhijeet. On Wed, 8 Dec, 2021, 12:30 Peter Maydell, wrote: > On Wed, 8 Dec 2021 at 10:45, abhijeet inamdar > wrote: > > > > Hi, > > > > Are these lines to be changed accordingly for my compatible > https://git

Re: qemu: fatal: lockup...

2021-12-08 Thread abhijeet inamdar
Hi, Are these lines to be changed accordingly for my compatible https://github.com/qemu/qemu/blob/stable-4.2/target/arm/helper.c#L9842-#L9852 or is it fixed? BR. Abhijeet. On Tue, 7 Dec, 2021, 13:29 abhijeet inamdar, wrote: > The only difference I found is that at the 0x0 we have

Re: qemu: fatal: lockup...

2021-12-07 Thread abhijeet inamdar
Peter Maydell, wrote: > On Tue, 7 Dec 2021 at 09:23, abhijeet inamdar > wrote: > > > > And we have two memory map one at the boot time and other is the normal > memory map. There is slight chance in the size/addresses. My doubt is which > do mapping do we usually follo

Re: qemu: fatal: lockup...

2021-12-07 Thread abhijeet inamdar
And we have two memory map one at the boot time and other is the normal memory map. There is slight chance in the size/addresses. My doubt is which do mapping do we usually follow? BR. Abhijeet. On Mon, 6 Dec, 2021, 17:10 abhijeet inamdar, wrote: > I have searched in all the reference man

Re: qemu: fatal: lockup...

2021-12-06 Thread abhijeet inamdar
I have searched in all the reference manual but we don't have Flash memory as such but we have NOR and NAND Flash memory address. BR. Abhijeet. On Mon, 6 Dec, 2021, 15:16 Peter Maydell, wrote: > On Mon, 6 Dec 2021 at 13:30, abhijeet inamdar > wrote: > > > > How to find

Re: qemu: fatal: lockup...

2021-12-06 Thread abhijeet inamdar
How to find out where actually the hardware is expecting the initial VTOR? Mine is a Cortex-M3 machine. But not entirely it's a combination of two cores A7 and M3. Any tips! BR. Abhijeet. On Mon, 6 Dec, 2021, 12:06 Peter Maydell, wrote: > On Sun, 5 Dec 2021 at 17:16, abhijeet inam

Re: qemu: fatal: lockup...

2021-12-05 Thread abhijeet inamdar
So the solution would be placing the vector correctly and mapping to the right address for Flash/RAM...? BR. Abhijeet. On Sun, 5 Dec, 2021, 17:59 Peter Maydell, wrote: > On Sat, 4 Dec 2021 at 23:06, abhijeet inamdar > wrote: > > I'm getting this error. There is no hit for th

qemu: fatal: lockup...

2021-12-04 Thread abhijeet inamdar
Hi, I'm getting this error. There is no hit for this in google as most are on Hardfault. The error is : "Taking exception 18 [v7M INVSTATE UsageFault] ...BusFault with BFSR.STKERR ...taking pending nonsecure exception 3 qemu: fatal: Lockup: can't take terminal derived exception (original

DeviceState definition

2021-11-30 Thread abhijeet inamdar
Hi, What difference does it make to define: DeviceState *nvic; nvic = qdev_create(NULL, TYPE_ARMV7M); vs DeviceState *armv7m; armv7m = DEVICE(>armv7m); Can you please explain me because I'm confused between two machines which I want to adapt for my custom machine which is based on

Re: Memory Initialization

2021-11-19 Thread abhijeet inamdar
And it's QEMU-4.2.0 and even parallely trying on QEMU-6.0.0. BR. Abhijeet. On Fri, 19 Nov, 2021, 13:02 abhijeet inamdar, wrote: > Hi, > > 1) I have a total of four memories: RAM, Flash, DDR and Shared. I > initialised the flash and ram like the follows: > > MemoryReg

Memory Initialization

2021-11-19 Thread abhijeet inamdar
Hi, 1) I have a total of four memories: RAM, Flash, DDR and Shared. I initialised the flash and ram like the follows: MemoryRegion *flash = g_new(MemoryRegion, 1); int flash_size = board->flash_size_kb * 1024; memory_region_init_ram(flash, NULL, "machine.flash", flash_size, _fatal);

Re: Add Custom Machine in Qemu-4.2.0 or newer

2021-11-05 Thread abhijeet inamdar
Hi, I found my machine to be as to be similar to one of the stm32 implementations but in the list of machines which one to select? BR. Abhijeet. On Thu, 4 Nov, 2021, 13:10 abhijeet inamdar, wrote: > Can I know exactly which board is it?! Would be helpful for me to look > into. &g

Re: Add Custom Machine in Qemu-4.2.0 or newer

2021-11-04 Thread abhijeet inamdar
Can I know exactly which board is it?! Would be helpful for me to look into. BR. Abhijeet. On Thu, 4 Nov, 2021, 12:15 Peter Maydell, wrote: > On Wed, 3 Nov 2021 at 14:04, abhijeet inamdar > wrote: > > In a machine definition can there be a two different "cpu-type" >

Re: Add Custom Machine in Qemu-4.2.0 or newer

2021-11-03 Thread abhijeet inamdar
Hi, In a machine definition can there be a two different "cpu-type" ( say ARM M or A or R)that can be emulated ? (if it make sense). BR. Abhijeet. On Tue, 2 Nov, 2021, 15:49 Peter Maydell, wrote: > On Tue, 2 Nov 2021 at 14:39, abhijeet inamdar > wrote: > > > > C

Re: Add Custom Machine in Qemu-4.2.0 or newer

2021-11-02 Thread abhijeet inamdar
? BR. Abhijeet. On Tue, Nov 2, 2021 at 2:24 PM Peter Maydell wrote: > On Tue, 2 Nov 2021 at 13:15, abhijeet inamdar > wrote: > > > > Hi, > > > > I have a hardware which I want to emulate on QEMU based on arm Cortex > M3. I tried to follow the examples like mps2

Add Custom Machine in Qemu-4.2.0 or newer

2021-11-02 Thread abhijeet inamdar
Hi, I have a hardware which I want to emulate on QEMU based on arm Cortex M3. I tried to follow the examples like mps2 or stellaris. I'm finding it really hard to figure out how can I test the devices/peripherals I add to the machine. As the binary which I have contains all major protocols like

Re: qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)

2021-09-30 Thread abhijeet inamdar
The above is when I load the .bin instead of ELF in the machine. On Thu, Sep 30, 2021 at 1:33 PM abhijeet inamdar < abhijeetinamdar3...@gmail.com> wrote: > Actually the ELF generates the .bin file which is being used to run on the > target (hardware). It's address starts from zer

Re: qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)

2021-09-30 Thread abhijeet inamdar
= R11= R12= R13=c0dec0b8 R14=fff9 R15= XPSR=8003 N--- A handler FPSCR: Thank you, Abhijeet. On Thu, Sep 30, 2021, 10:57 Peter Maydell wrote: > On Thu, 30 Sept 2021 at 07:17, abhijeet inamdar > wrote: > > > > But this very ELF file

Re: qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)

2021-09-30 Thread abhijeet inamdar
But this very ELF file runs on the target(real hardware) perfectly. So how different should it be to emulate? Thank you, Abhijeet. On Wed, Sep 29, 2021 at 10:31 PM Peter Maydell wrote: > On Wed, 29 Sept 2021 at 16:24, abhijeet inamdar > wrote: > > > > I tried to add

Re: qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)

2021-09-29 Thread abhijeet inamdar
How can I proceed? Thank you, Abhijeet. On Fri, Sep 17, 2021 at 11:11 AM Peter Maydell wrote: > On Thu, 16 Sept 2021 at 20:13, abhijeet inamdar > > wrote: > > > > Is there any way/s to check where actually is it failing or point which > file? > > Use the usual deb

Re: qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)

2021-09-16 Thread abhijeet inamdar
Is there any way/s to check where actually is it failing or point which file? Thank you, Abhijeet. On Thu, Sep 16, 2021 at 8:49 PM Peter Maydell wrote: > On Thu, 16 Sept 2021 at 19:46, Peter Maydell > wrote: > > > > On Thu, 16 Sept 2021 at 17:52, abhijeet inamdar > >

qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)

2021-09-16 Thread abhijeet inamdar
Hi, How do I fix it ? it's for cortex-m3 and the below is the gdb trace when I load ELF. qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1) R00= R01= R02= R03= R04= R05= R06= R07= R08= R09=

Re: Emulate custom machine on qemu-4.2.0

2021-09-15 Thread abhijeet inamdar
You mean hw/arm/msp2.c ? On Wed, Sep 15, 2021, 13:55 Peter Maydell wrote: > On Wed, 15 Sept 2021 at 12:13, abhijeet inamdar > wrote: > > > > Now there are some many UART implemented in the hw/char. What should we > look for or how do you choose which one to use? or i

Re: Emulate custom machine on qemu-4.2.0

2021-09-15 Thread abhijeet inamdar
15, 2021, 10:58 Peter Maydell wrote: > On Wed, 15 Sept 2021 at 08:23, abhijeet inamdar > wrote: > > > > Hi, > > > > As my custom machine is based on cortex-m3 I checked the stellaris.c > https://github.com/qemu/qemu/blob/stable-4.2/hw/arm/stellaris.c#1384,1

Re: Emulate custom machine on qemu-4.2.0

2021-09-15 Thread abhijeet inamdar
be appreciated. Thank you Abhijeet. On Tue, Sep 14, 2021 at 2:55 PM Peter Maydell wrote: > On Tue, 14 Sept 2021 at 13:51, abhijeet inamdar > wrote: > > > > Is there any example for UART being added to the machine in 4.2.0? > > Lots of machines have UARTs. Look at almost any Arm board. > > -- PMM >

Re: Emulate custom machine on qemu-4.2.0

2021-09-14 Thread abhijeet inamdar
Is there any example for UART being added to the machine in 4.2.0? Thank you, Abhijeet. On Tue, Sep 14, 2021, 12:26 Peter Maydell wrote: > On Tue, 14 Sept 2021 at 11:21, abhijeet inamdar > wrote: > > > > My question is that can we see the list of devices for say any &g

Re: Emulate custom machine on qemu-4.2.0

2021-09-14 Thread abhijeet inamdar
: > On Tue, 14 Sept 2021 at 10:58, abhijeet inamdar > wrote: > > Is there anything in qemu to check for a machine which all > > devices are added or working? Can we do that!? > > I dunno what you're asking for; could you elaborate ? > In general each machine has a different s

Re: Emulate custom machine on qemu-4.2.0

2021-09-14 Thread abhijeet inamdar
Hi, Is there anything in qemu to check for a machine which all devices are added or working? Can we do that!? Thank you, Abhijeet. On Tue, Sep 14, 2021, 11:23 Peter Maydell wrote: > On Tue, 14 Sept 2021 at 09:52, abhijeet inamdar > wrote: > > I was trying to emulate a machine i

Emulate custom machine on qemu-4.2.0

2021-09-14 Thread abhijeet inamdar
Hi, I was trying to emulate a machine in qemu-4.2.0 but was getting an error message: Unexpected error in qemu_chr_fe_init() at /home/qemu-4.2.0/chardev/char-fe.c:220: qemu-system-arm: Device 'serial0' is in use I tried to apply this patch

Re: Blank screen for hello world qemu-4.2.0

2021-07-27 Thread abhijeet inamdar
Hi, I was trying to use gdbstub what does vmlinux mean here? Then launch gdb on the ‘vmlinux’ executable: > gdb vmlinux Is it my executable file or ? On Mon, Jul 26, 2021, 15:44 abhijeet inamdar wrote: > Hi, > > Is there any particular Flash and RAM length for qemu to semi

Re: Blank screen for hello world qemu-4.2.0

2021-07-26 Thread abhijeet inamdar
Hi, Is there any particular Flash and RAM length for qemu to semihosting. I'm using q2-update-2017 tool chain and 16.04 Ubuntu. On Fri, Jul 23, 2021, 14:16 Peter Maydell wrote: > On Fri, 23 Jul 2021 at 13:05, abhijeet inamdar > wrote: > > > > Means the memory mapping is

Re: Blank screen for hello world qemu-4.2.0

2021-07-23 Thread abhijeet inamdar
= R07= R08= R09= R10= R11= R12= R13=07e0 R14=fff9 R15=0572 XPSR=6103 -ZC- T handler Until i kill it. On Fri, Jul 23, 2021 at 12:47 PM Peter Maydell wrote: > On Fri, 23 Jul 2021 at 11:41, abhijeet inamdar > wrote: >

Re: Blank screen for hello world qemu-4.2.0

2021-07-23 Thread abhijeet inamdar
e0 R14=fff9 R15=0572 XPSR=6103 -ZC- T handler Thank you, Abhijeet. On Fri, Jul 23, 2021 at 11:07 AM Peter Maydell wrote: > On Thu, 22 Jul 2021 at 22:27, abhijeet inamdar > wrote: > > > > Hi, > > > > I downloaded the qemu-6.0.0. When I did ./configur

Re: Blank screen for hello world qemu-4.2.0

2021-07-22 Thread abhijeet inamdar
Hi, I downloaded the qemu-6.0.0. When I did ./configure inside qemu-6.0.0 directory it say ERROR: Cannot find ninja wherein I did install pip3 install Ninja. What should I do? Thank you, Abhijeet. On Thu, Jul 22, 2021, 15:26 Peter Maydell wrote: > On Thu, 22 Jul 2021 at 13:57, abhij

Blank screen for hello world qemu-4.2.0

2021-07-22 Thread abhijeet inamdar
Hi, I have been trying to create my own machine and execute a hello_world on QEMU-4.2.0. I created mymachine.c in hw/arm and have my hello_world.c, mymachine.ld and startup_ARMCM3.S in qemu-4.2.0/proj. So, firstly after adding mymachine.c in hw/arm I did "make" in the build directory and it

ARMCM3 startup and linker

2021-07-12 Thread abhijeet inamdar
Hi, I was using startup_ARMCM3.S (v2.0.0 by CMSIS) for my custom machine in qemu-2.10. Now, I updated my qemu-2.10 to qemu-4.2.0 and used the same startup script for my custom machine but it wont work. It is giving me a blank screen. I have tried with all the new scripts (both .ld and .S) on my

Re: GDB for qemu-system-arm

2021-07-08 Thread abhijeet inamdar
:36 Peter Maydell wrote: > On Thu, 8 Jul 2021 at 11:23, abhijeet inamdar > wrote: > > > > I tried -D but the log.txt which got created is empty. > > -D just says "log debug information to this file". You need to also > pass some kind of -d option to turn on whatever logging you wanted. > > -- PMM >

Re: GDB for qemu-system-arm

2021-07-08 Thread abhijeet inamdar
I tried -D but the log.txt which got created is empty. Thanks, Abhijeet. On Thu, Jul 8, 2021, 10:05 abhijeet inamdar wrote: > Hi, > > I'm using Ubuntu 16.04 and qemu-4.2.0. I have compiled and generated a > .axf file but I'm not able to run. > > The command I used is

GDB for qemu-system-arm

2021-07-08 Thread abhijeet inamdar
Hi, I'm using Ubuntu 16.04 and qemu-4.2.0. I have compiled and generated a .axf file but I'm not able to run. The command I used is qemu-system-arm -M mymachine -cpu cortex-m3 -kernel main.axf -monitor none -serial studio -semihosting -nographic Thanks, Abhijeet.

Re: Qemu-4.2.0

2021-07-07 Thread abhijeet inamdar
Hi, I have a .axf file how to debug it using gdb for qemu-system-arm? Thanks, Abhijeet. On Wed, Jul 7, 2021, 12:09 abhijeet inamdar wrote: > I rectified it. Some headers were missing. > > Thanks, > Abhijeet. > > On Wed, Jul 7, 2021, 11:24 abhijeet inamdar > wr

Re: Qemu-4.2.0

2021-07-07 Thread abhijeet inamdar
I rectified it. Some headers were missing. Thanks, Abhijeet. On Wed, Jul 7, 2021, 11:24 abhijeet inamdar wrote: > Hi, I tried to implement from the example of stellaris.c but I'm getting > some more warnings as follows: > > warning: implicit declaration of function 'qdev_pro

Re: Qemu-4.2.0

2021-07-07 Thread abhijeet inamdar
T); Thanks, Abhijeet. On Tue, Jul 6, 2021, 17:35 Peter Maydell wrote: > On Tue, 6 Jul 2021 at 16:14, abhijeet inamdar > wrote: > > > > The warnings are as follows: > > > > warning: implicit declaration of function 'armv7m_init' > [-Wimplicit-function-declaration] &

Re: Qemu-4.2.0

2021-07-06 Thread abhijeet inamdar
In addition to this in armv7m.c warning: no previous prototype for 'armv7m_init'[-Wmissing-prototypes] DeviceState *armv7m_init(Memory region *system_memory, int mem_size, int num_irq, Thanks, Abhijeet. On Tue, Jul 6, 2021, 17:14 abhijeet inamdar wrote: > The warnings are as foll

Re: Qemu-4.2.0

2021-07-06 Thread abhijeet inamdar
] qdev_connect_gpio_out_named(nvic, "SYSRESETREQ", 0, qemu_allocate_irq(_sys_reset, NULL, 0)); Thanks, Abhijeet. On Tue, Jul 6, 2021, 16:59 Peter Maydell wrote: > On Tue, 6 Jul 2021 at 15:48, abhijeet inamdar > wrote: > > > > Hi, > > > > I am tryi

Re: Qemu-4.2.0

2021-07-06 Thread abhijeet inamdar
functions are they updated or still can be worked? Thanks, Abhijeet. On Mon, Jun 28, 2021, 16:05 Peter Maydell wrote: > On Mon, 28 Jun 2021 at 14:57, abhijeet inamdar > wrote: > > > > I sorted the MachineState error. We checkout the commit for serial_hds(). > > > > Can

Re: Qemu-4.2.0

2021-06-28 Thread abhijeet inamdar
Maydell wrote: > On Mon, 28 Jun 2021 at 13:40, abhijeet inamdar > wrote: > > > > I didn't do any changes in the QEMU source code but added new for the .c > and .h files for the custom machine. > > That *is* changing the QEMU source code :-) Sorry, I'd missed you > were

Re: Qemu-4.2.0

2021-06-28 Thread abhijeet inamdar
How else you add a custom machine?? BR. Abhijeet. On Mon, Jun 28, 2021, 14:40 abhijeet inamdar wrote: > I didn't do any changes in the QEMU source code but added new for the .c > and .h files for the custom machine. > > BR. > Abhijeet. > > On Mon, Jun 28, 2021, 14:35 P

Re: Qemu-4.2.0

2021-06-28 Thread abhijeet inamdar
I didn't do any changes in the QEMU source code but added new for the .c and .h files for the custom machine. BR. Abhijeet. On Mon, Jun 28, 2021, 14:35 Peter Maydell wrote: > On Mon, 28 Jun 2021 at 13:04, abhijeet inamdar > wrote: > > > > It is showing errors for serial_hds(

Re: Qemu-4.2.0

2021-06-28 Thread abhijeet inamdar
It is showing errors for serial_hds() and MachineState so what specific .h files I should add? BR. Abhijeet. On Mon, Jun 28, 2021, 13:57 abhijeet inamdar wrote: > Hi, > > I have built custom hardware which is based on arm-m3 in qemu-2.10. It > works fine for Hello_world.c a b

Re: Qemu-4.2.0

2021-06-28 Thread abhijeet inamdar
. Abhijeet. On Thu, Jun 24, 2021, 10:43 Peter Maydell wrote: > On Wed, 23 Jun 2021 at 10:23, abhijeet inamdar > wrote: > > > > Hi, > > > > I want to know how to get the difference for an machine(ex: Akita) from > qemu-2.10 to qemu-4.2.0. > > > > What a

Qemu-4.2.0

2021-06-23 Thread abhijeet inamdar
Hi, I want to know how to get the difference for an machine(ex: Akita) from qemu-2.10 to qemu-4.2.0. What all changes I should make for being compatible for it to be working in qemu-4.2.0 !? Best regards, Abhijeet.